CN108777871B

CN108777871B - Method for realizing next generation sensor network communication system

Info

Publication number: CN108777871B
Application number: CN201810915614.0A
Authority: CN
Inventors: 王晓喃; 秦湘萍; 闫海英
Original assignee: Changshu Institute of Technology
Current assignee: Changshu Institute of Technology
Priority date: 2018-08-13
Filing date: 2018-08-13
Publication date: 2021-01-08
Anticipated expiration: 2038-08-13
Also published as: CN108777871A

Abstract

The invention provides a method for realizing a next generation sensor network communication system, wherein the next generation sensor network comprises a central controller, more than two local controllers and sensor nodes; the sensor nodes are divided into fixed sensor nodes and mobile sensor nodes; the central controller and the local controllers are routers, the central controller is used for managing the local controllers, and the local controllers are used for managing the sensing nodes; the network can rapidly acquire network data through the implementation method provided by the invention, shorten the routing delay, reduce the data packet loss rate and improve the service quality.

Description

Method for realizing next generation sensor network communication system

Technical Field

The invention relates to an implementation method, in particular to an implementation method of a next generation sensor network communication system.

Background

The next generation sensor network is a novel communication network, and can realize multi-hop wireless communication between nodes. With the continuous development of network technology and the continuous emergence of various new applications, there is an urgent need to improve network performance.

At present, researchers have proposed a mode for acquiring network services through a next generation sensor network and defined a corresponding protocol stack, but the existing network service acquisition method has some limitations because the architecture of the next generation sensor network is different from that of the traditional network. Therefore, it is necessary to provide a low-delay next-generation sensor network implementation method, so as to improve the service quality.

Disclosure of Invention

The purpose of the invention is as follows: the invention provides a method for realizing a next generation sensor network communication system aiming at the defects of the prior art.

The technical scheme is as follows: the invention discloses a method for realizing a next generation sensor network communication system, wherein the next generation sensor network comprises a central controller, more than two local controllers and sensor nodes; the sensor nodes are divided into fixed sensor nodes and mobile sensor nodes; the central controller and the local controllers are routers, the central controller is used for managing the local controllers, and the local controllers are used for managing the sensing nodes;

the central controller is provided with more than two wired interfaces, one wired interface is uniquely identified by one interface ID, and each wired interface is connected with a local controller link; a local controller is provided with a wired interface and a wireless interface, the wired interface is connected with the central controller link, and the wireless interface is connected with the fixed sensing node link; the fixed sensing node and the mobile sensing node are provided with a wireless interface;

the sensing node or the local controller is uniquely identified by an address, and the address consists of a local prefix, a fixed prefix and a mobile prefix; the fixed prefix and the mobile prefix of the local controller address are both 0, and the mobile prefix of the fixed sensing node address is 0;

each fixed sensing node stores an upstream table, and each upstream table item comprises a local address domain, an upstream address domain, a distance domain and a life cycle domain; the local address field stores the address of the local controller, the upstream address field stores the address of the upstream node, the distance field value is the hop number reaching the local controller, and the life cycle is the effective time of the upstream table entry;

after the local controller LC1 starts, the following operations are periodically performed to build the upstream table:

step 101: starting;

step 102: the local controller LC1 constructs an address, the local prefix of the address is the hardware ID of the local controller LC1, for example, the MAC address, the fixed prefix and the mobile prefix are both 0, the parameter d1 is set, the initial value of the parameter d1 is 0, a release message is sent from the wireless interface, the source address of the release message is the constructed address, the destination address is a broadcast address, namely, the address with each bit being 1, and the load is the parameter d1 and the constructed address;

step 103: judging whether the mobile sensing node or the fixed mobile node receives the release message, if so, executing step 104, otherwise, executing step 105;

step 104: the mobile sensing node receiving the publish message discards the publish message, and step 112 is executed;

step 105: after receiving the publish message, the fixed mobile node increments the parameter d1 in the publish message load by 1 and checks an upstream table to determine whether an upstream table entry exists, wherein the local address of the upstream table entry is equal to the address in the publish message load and the distance domain value is smaller than the parameter d1 in the publish message load, if yes, step 106 is executed, otherwise, step 107 is executed;

step 106: the fixed sensing node receiving the publication message discards the publication message, and executes step 112;

step 107: after receiving the release message, the fixed mobile node checks the upstream table, and determines whether there is an upstream table entry, where the local address of the upstream table entry is equal to the address in the release message load, the distance domain value is equal to the parameter d1 in the release message load, and the upstream address domain value is equal to the source address of the release message, if yes, step 106 is executed, otherwise step 108 is executed;

step 108: after receiving the release message, the fixed mobile node checks the upstream table, and determines whether there is an upstream table entry, where the local address of the upstream table entry is equal to the address in the release message load, the distance domain value is equal to the parameter d1 in the release message load, and the upstream address domain value is not equal to the source address of the release message, if yes, step 109 is executed, otherwise step 110 is executed;

step 109: the fixed mobile node receiving the release message creates an upstream table entry, the local address of the upstream table entry is equal to the address in the load of the release message, the distance domain value is equal to the parameter d1 in the load of the release message, the upstream address domain value is equal to the source address of the release message, and the life cycle is set to the maximum value, for example, 500 ms; the fixed mobile node constructs an address, the local prefix and the mobile prefix of the address are 0, the fixed prefix is equal to the hardware ID of the fixed mobile node, the source address of the received release message is updated into the constructed address, the release message is forwarded, and step 103 is executed;

step 110: the fixed mobile node receiving the release message checks the upstream table; judging whether an upstream table entry exists, wherein the local address of the upstream table entry is equal to the address in the load of the release message, and the distance threshold value is greater than the parameter d1 in the load of the release message, if so, executing the step 111, otherwise, executing the step 109;

step 111: the fixed mobile node receiving the release message selects an upstream table entry, the local address of the upstream table entry is equal to the address in the release message load, the distance domain value is greater than the parameter d1 in the release message load, the upstream address of the upstream table entry is updated to the source address of the release message, the distance domain value is updated to the parameter d1 in the release message load, and the life cycle is set to the maximum value; the fixed mobile node constructs an address, the local prefix and the mobile prefix of the address are 0, the fixed prefix is equal to the hardware ID of the fixed mobile node, the source address of the received release message is updated into the constructed address, the release message is forwarded, and step 103 is executed;

step 112: finishing;

and if the fixed sensing node detects that the life cycle attenuation of one upstream table entry is 0, deleting the upstream table entry.

The local controller establishes an upstream table at each fixed sensing node through the process, so that each fixed sensing node can acquire the address of the local controller, communication with the local controller is realized, and meanwhile, the fixed sensing node also acquires the distance from the local controller and the address of the upstream node, so that the fixed sensing node can select an optimal path to realize communication with the local controller through the upstream node, and communication delay is greatly reduced.

In the method, a central controller stores a local table, and a local table item comprises an interface ID domain, a local address domain and a life cycle domain;

after the local controller LC1 is started, the following operations are periodically performed to establish a local table:

step 201: starting;

step 202: the local controller LC1 creates an address, the local prefix of the address is the hardware ID of the local controller LC1 sends a local release message from the wired interface of the local controller LC1, the source address of the local release message is a constructed address, the destination address is empty, and the load is empty;

step 203: after receiving the local release message from the interface f1, the central controller checks the local table, judges whether a local table entry exists, if so, updates the local address of the local table entry to the source address of the local release message, and sets the life cycle to the maximum value, wherein the interface ID of the local table entry is equal to f 1; otherwise, the central controller creates a local table entry, the interface ID of the local table entry is equal to f1, the local address is the source address of the local release message, and the life cycle is set to the maximum value;

step 204: finishing;

if the central controller detects that the life cycle attenuation of one local table entry is 0, the local table entry is deleted.

The local controller establishes the local table entries in the central controller through the process, so that the central controller can acquire the address and interface information of each local controller, thereby realizing correct forwarding of the message.

In the method, a fixed sensing node sends a beacon message periodically, the source address of the beacon message is the address of the fixed sensing node, the local prefix and the mobile prefix of the address are both 0, the fixed prefix is the hardware ID of the fixed sensing node, the destination address of the beacon message is a broadcast address, and the load is an upstream table of the fixed sensing node;

each local controller stores a path table, and each path table item comprises an address set domain and a life cycle domain;

if the fixed sensing node FN1 receives the beacon messages of all the neighbor fixed sensing nodes, comparing the upstream table of the fixed sensing node with the upstream tables in all the beacon message loads; if the fixed sensing node FN1 has an upstream table entry E1, the local address domain value of the upstream table entry is LA1 and the distance domain value is not greater than the distance domain value of the upstream table entry whose local address domain value is LA1 in all other upstream tables, the fixed sensing node FN1 performs the following operations to establish a path table:

step 301: starting;

step 302: the fixed sensing node FN1 selects all upstream table entries with local address domain values of LA1 from the upstream table of the fixed sensing node; aiming at each selected upstream table entry, a fixed sensing node FN1 constructs an address FA1, wherein a local prefix in the address FA1 is equal to a local prefix in an address LA1, the fixed prefix is a hardware ID of the fixed sensing node, a mobile prefix is 0, an address set variable A1 is set, and an initial value of the address set variable A1 is { FA1 }; the fixed sensing node FN1 sends a path message, wherein the source address of the path message is an address FA1, the destination address is the upstream address of the selected upstream table entry, and the load is an address LA1 and an address set parameter A1;

step 303: judging whether the destination local controller or the destination fixed sensing node receives the path message, namely the local controller with the address equal to LA1, if the destination local controller is the local controller, executing step 305, otherwise executing step 304;

step 304: after a destination fixed sensing node with the hardware ID equal to the fixed prefix of the destination address of the path message receives the path message, an address is constructed, the local prefix of the address is the local prefix of an address LA1, the fixed prefix is equal to the hardware ID of the destination fixed sensing node, and the mobile prefix is 0; adding the constructed address to the parameter A1 in the path message load as the last element; the destination fixed sensing node selects all upstream table entries with local address domain values of LA1 from its own upstream table, and for each selected upstream table entry, the destination fixed sensing node updates the destination address of the path message to the upstream address of the upstream table entry, forwards the path message, and executes step 303;

step 305: after receiving the path message, the destination local controller adds its own address to the parameter A1 in the path message load and uses it as the last element; the destination local controller checks the path table, judges whether a path table item exists, the address set domain value of the path table item is equal to the parameter A1 in the path message load, if yes, the life cycle of the path table item is set to be the maximum value; otherwise, the destination local controller creates a path table entry, the address set domain value of the path table entry is equal to the parameter A1 in the path message load, and the life cycle is set to the maximum value;

step 306: and (6) ending.

The fixed sensing node establishes a routing path to the local controller through the process, so that the fixed sensing node can realize communication with the local controller without establishing a route, and the cost and delay of data communication delay are greatly reduced. Because the process is realized by the upstream table, the routing path from the fixed sensing node to the local controller is optimal, and the data communication delay and cost are further reduced.

In the method, under the condition that a mobile sensing node MN1 is connected with a fixed sensing node FN1 through a link, the address is MA1, the local prefix of the address MA1 is the hardware ID of a local controller LC1, the address of the local controller LC1 is LA1, the fixed prefix is equal to the hardware ID of the fixed sensing node FN1, the mobile sensing node MN2 is connected with a fixed sensing node FN2 through a link, the address is MA2, the local prefix of the address MA2 is the hardware ID of the local controller LC2, the address of the local controller LC2 is LA2, and the fixed prefix of the address MA2 is the hardware ID of the fixed sensing node FN2, if the condition 1 is met, the mobile sensing node MN1 executes the following processes to realize the communication with the mobile sensing node MN 2; condition 1: in the upstream table of the fixed sensing node FN1, there is at least one upstream table entry whose local address is LA2, and in the upstream table of the fixed sensing node FN2, there is at least one upstream table entry whose local address is LA 1;

step 401: starting;

step 402: the mobile sensing node MN1 sends a request message, the source address of the request message is MA1, the destination address is the address of the fixed sensing node FN1, the local prefix of the address of the fixed sensing node FN1 is 0, the fixed prefix is the hardware ID of the fixed sensing node FN1, the mobile prefix is 0, and the load of the request message is the address MA 2; after receiving the request message, the fixed sensing node FN1 selects upstream table entries whose local prefixes of all local addresses are equal to the local prefix of the address MA2, and for each selected upstream table entry, the fixed sensing node FN1 updates the destination address of the request message to the upstream address of the upstream table entry, and forwards the request message;

step 403: if the destination local controller receives the request message, executing step 405, otherwise executing step 404; the destination local controller is a local controller with a hardware ID equal to the local prefix of the destination address of the request message;

step 404: after the destination fixed sensing node receives the request message, the hardware ID of the destination fixed sensing node is equal to the fixed prefix of the destination address of the request message, the upstream table entries of which the local prefixes of all the local addresses are equal to the local prefix of the address MA2 are selected, for each selected upstream table entry, the destination fixed sensing node updates the destination address of the request message to the upstream address of the upstream table entry, forwards the request message, and executes step 403;

step 405: after receiving the request message from the wireless interface, the target local controller selects all path table entries meeting the condition 2; for each selected path entry, the destination local controller extracting a subset of addresses equal to all elements in the set of addresses of the path entry from address CA1 to the last element, the order of the elements of the subset of addresses being the same as the order of the elements of the set of addresses of the path entry, adding the extracted subset of addresses to the request message payload, updating the destination address of the request message to the last element of the subset of addresses, removing the last element from the subset of addresses in the request message payload, forwarding the request message;

condition 2: the address set domain value contains an address CA1, the local prefix and the fixed prefix of the address CA1 are equal to the local prefix and the fixed prefix of the address MA2, and the mobile prefix is 0;

step 406: judging whether the mobile sensing node MN2 or the target fixed sensing node receives the request message, if so, executing the step 408, otherwise, executing the step 407;

step 407: the destination fixed sensing node judges whether the subset in the request message load is empty, if so, the destination fixed sensing node updates the destination address of the request message to the address MA2 and forwards the request message; otherwise, the destination fixed sensing node updates the destination address of the request message to the last element of the address subset in the request message load, deletes the last element from the address subset, forwards the request message, and executes step 406;

step 408: the mobile sensing node MN2 sends a response message, wherein the source address of the response message is the address MA2, the destination address is the address of the fixed sensing node FN2, the local prefix and the mobile prefix of the address are 0, the fixed prefix is the hardware ID of the fixed sensing node FN2, and the load is the address MA1 and the response data; after receiving the response message, the fixed sensing node FN2 selects upstream table entries whose local prefixes of all local addresses are equal to the local prefix of the address MA1, and for each selected upstream table entry, the fixed sensing node FN2 updates the destination address of the response message to the upstream address of the upstream table entry, and forwards the response message;

step 409: if the destination local controller receives the response message, performing step 411, otherwise performing step 410; wherein the hardware ID of the destination local controller is equal to the local prefix of the destination address of the response message;

step 410: after receiving the response message, the destination fixed sensing node selects upstream table entries whose local prefixes of all local addresses are equal to the local prefix of the address MA1, and for each selected upstream table entry, the destination fixed sensing node updates the destination address of the response message to the upstream address of the upstream table entry, forwards the response message, and executes step 409; the hardware ID of the target fixed sensing node is equal to the fixed prefix of the target address of the response message;

step 411: after receiving the response message from the wireless interface, the destination local controller selects all path table entries meeting the condition 3; for each selected path entry, the destination local controller extracting a subset of addresses equal to all elements in the set of addresses of the path entry from address CA2 to the last element, the order of the elements of the subset of addresses being the same as the order of the elements of the set of addresses of the path entry, adding the extracted subset of addresses to the response message payload, updating the destination address of the response message to the last element of the subset of addresses, removing the last element from the subset of addresses in the response message payload, forwarding the response message from the wireless interface;

condition 3: the address set domain value contains an address CA2, the local prefix and the fixed prefix of the address CA2 are equal to the local prefix and the fixed prefix of the address MA1, and the mobile prefix is 0;

step 412: judging whether the mobile sensing node MN1 or the destination fixed sensing node receives the response message, if so, executing the step 414 by the mobile sensing node MN1, otherwise, executing the step 413;

step 413: after receiving the response message, the destination fixed sensing node judges whether the subset in the load of the response message is empty, if so, the destination fixed sensing node updates the destination address of the response message to the address MA1 and forwards the response message; otherwise, the destination fixed sensing node updates the destination address of the response message to the last element of the address subset in the response message payload, deletes the last element from the address subset, forwards the response message, and executes step 412;

step 414: after receiving the response message, the mobile sensing node MN1 saves the data in the response message load;

step 415: and (6) ending.

Under the condition that the condition 1 is met, the two mobile sensing nodes realize communication through the process, the communication is realized through the path table and the upstream table in the process, a routing path does not need to be established, and the optimal routing path from the fixed sensing node to the local controller is established through the path table, so that the data delay and the cost are greatly reduced.

In the method of the present invention, under the condition that the mobile sensing node MN1 is linked with the fixed sensing node FN1, the address is MA1, the local prefix of the address MA1 is the hardware ID of the local controller LC1, the address of the local controller LC1 is LA1, the fixed prefix is equal to the hardware ID of the fixed sensing node FN1, the mobile sensing node MN2 is linked with the fixed sensing node FN2, the address is MA2, the local prefix of the address MA2 is the hardware ID of the local controller LC2, the address of the local controller LC2 is LA2, and the fixed prefix of the address MA2 is the hardware ID of the fixed sensing node FN2, if condition 1 is not satisfied, the mobile sensing node MN1 implements the communication with the mobile sensing node MN2 by performing the following procedures:

step 501: starting;

step 502: the mobile sensing node MN1 sends a request message, the source address of the request message is MA1, the destination address is the address of the fixed sensing node FN1, the local prefix of the address of the fixed sensing node FN1 is 0, the fixed prefix is the hardware ID of the fixed sensing node FN1, the mobile prefix is 0, and the load of the request message is the address MA 2; after receiving the request message, the fixed sensing node FN1 selects all the upstream table entries with the smallest distance threshold value, and for each selected upstream table entry, the fixed sensing node FN1 updates the destination address of the request message to the upstream address of the upstream table entry, and forwards the request message;

step 503: if the destination local controller receives the request message, executing step 505, otherwise executing step 504; the destination local controller is a local controller with a hardware ID equal to the local prefix of the destination address of the request message;

step 504: after the destination fixed sensing node receives the request message, the hardware ID of the destination fixed sensing node is equal to the fixed prefix of the destination address of the request message, all the upstream table entries with the smallest distance threshold value are selected, for each selected upstream table entry, the destination fixed sensing node updates the destination address of the request message to the upstream address of the upstream table entry, forwards the request message, and executes step 503;

step 505: after receiving the request message from the wireless interface, the destination local controller forwards the request message from the wired interface, and after receiving the request message, the central controller selects a local table entry, the local prefix of the local address of the local table entry is equal to the local prefix of the address MA2, and forwards the request message from the interface identified by the interface ID field value of the local table entry; after receiving the request message from the wired interface, the local controller selects all path table entries meeting the condition 2; for each selected path entry, the local controller extracting a subset of addresses equal to all elements in the set of addresses of the path entry from address CA1 to the last element, the order of the elements of the subset of addresses being the same as the order of the elements of the set of addresses of the path entry, adding the extracted subset of addresses to the request message payload, updating the destination address of the request message to the last element of the subset of addresses, removing the last element from the subset of addresses in the request message payload, forwarding the request message;

step 506: judging whether the mobile sensing node MN2 or the target fixed sensing node receives the request message, if so, executing the step 508 if the mobile sensing node MN2 is not received, otherwise, executing the step 507;

step 507: the destination fixed sensing node judges whether the subset in the request message load is empty, if so, the destination fixed sensing node updates the destination address of the request message to the address MA2 and forwards the request message; otherwise, the destination fixed sensing node updates the destination address of the request message to the last element of the address subset in the request message load, deletes the last element from the address subset, forwards the request message, and executes step 506;

step 508: the mobile sensing node MN2 sends a response message, wherein the source address of the response message is the address MA2, the destination address is the address of the fixed sensing node FN2, the local prefix and the mobile prefix of the address are 0, the fixed prefix is the hardware ID of the fixed sensing node FN2, and the load is the address MA1 and the response data; after receiving the response message, the fixed sensing node FN2 selects all the upstream table entries with the smallest distance threshold value, and for each selected upstream table entry, the fixed sensing node FN2 updates the destination address of the response message to the upstream address of the upstream table entry, and forwards the response message;

step 509: if the destination local controller receives the response message, executing step 511, otherwise executing step 510;

step 510: after receiving the response message, the destination fixed sensing node selects all the upstream entries with the smallest distance threshold, and for each selected upstream entry, the destination fixed sensing node updates the destination address of the response message to the upstream address of the upstream entry, forwards the response message, and executes step 509; wherein the destination fixed sensing node is a fixed sensor with a hardware ID equal to the fixed prefix of the destination address of the response message,

step 511: after receiving the response message from the wireless interface, the destination local controller forwards the response message from the wired interface, and after receiving the response message, the central controller selects a local table entry, the local prefix of the local address of the local table entry is equal to the local prefix of the address MA1, and forwards the request message from the interface identified by the interface ID field value of the local table entry; after receiving the request message from the wired interface, the local controller selects all path table entries meeting the condition 3; for each selected path entry, the local controller extracting a subset of addresses equal to all elements in the set of addresses of the path entry from address CA2 to the last element, the order of the elements of the subset of addresses being the same as the order of the elements of the set of addresses of the path entry, adding the extracted subset of addresses to the response message payload, updating the destination address of the response message to the last element of the subset of addresses, removing the last element from the subset of addresses in the response message payload, forwarding the response message from the wireless interface;

step 512: judging whether the mobile sensing node MN1 or the destination fixed sensing node receives the response message, if so, executing the step 514, otherwise, executing the step 513;

step 513: after receiving the response message, the destination fixed sensing node judges whether the subset in the load of the response message is empty, if so, the destination fixed sensing node updates the destination address of the response message to the address MA1 and forwards the response message; otherwise, the destination fixed sensing node updates the destination address of the response message to the last element of the address subset in the response message payload, deletes the last element from the address subset, forwards the response message, and executes step 512;

step 514: after receiving the response message, the mobile sensing node MN1 saves the data in the response message load;

step 515: and (6) ending.

Under the condition that the condition 1 is not met, the two mobile sensing nodes realize communication through the process, the process realizes communication through the local table, the path table and the upstream table, a routing path does not need to be established, the effectiveness of a forwarding interface is ensured through the life cycle of the local table and the upstream table, and the optimal routing path from the fixed sensing nodes to the local controller is established through the path table, so that data delay and cost are greatly reduced.

Has the advantages that: the invention provides a method for realizing a next generation sensor network communication system, and the network can quickly acquire network data, shorten routing delay, reduce data packet loss rate and improve service quality by the method.

Drawings

The foregoing and/or other advantages of the invention will become further apparent from the following detailed description of the invention when taken in conjunction with the accompanying drawings.

Fig. 1 is a flow chart illustrating the establishment of an upstream table according to the present invention.

Fig. 2 is a schematic diagram of a process for establishing a local table according to the present invention.

Fig. 3 is a schematic flow chart of establishing a path table according to the present invention.

Fig. 4 is a schematic diagram of a local data communication process according to the present invention.

Fig. 5 is a schematic diagram of a data acquisition process according to the present invention.

The specific implementation mode is as follows:

the invention provides a method for realizing a next generation sensor network communication system, and the network can quickly acquire network data, shorten routing delay, reduce data packet loss rate and improve service quality by the method.

Fig. 1 is a flow chart illustrating the establishment of an upstream table according to the present invention. The next generation sensing network comprises a central controller, more than two local controllers and sensing nodes; the sensor nodes are divided into fixed sensor nodes and mobile sensor nodes; the central controller and the local controllers are routers, the central controller is used for managing the local controllers, and the local controllers are used for managing the sensing nodes;

step 101: starting;

step 102: the local controller LC1 constructs an address, the local prefix of the address is the hardware ID of the local controller LC1, the fixed prefix and the mobile prefix are both 0, the parameter d1 is set, the initial value of the parameter d1 is 0, a release message is sent from the wireless interface, the source address of the release message is the constructed address, the destination address is a broadcast address, namely, the address with each bit being 1, and the load is the parameter d1 and the constructed address;

step 109: the fixed mobile node receiving the release message creates an upstream table entry, the local address of the upstream table entry is equal to the address in the load of the release message, the distance domain value is equal to the parameter d1 in the load of the release message, the upstream address domain value is equal to the source address of the release message, and the life cycle is set to be the maximum value; the fixed mobile node constructs an address, the local prefix and the mobile prefix of the address are 0, the fixed prefix is equal to the hardware ID of the fixed mobile node, the source address of the received release message is updated into the constructed address, the release message is forwarded, and step 103 is executed;

step 112: finishing;

Fig. 2 is a schematic diagram of a process for establishing a local table according to the present invention. The central controller stores a local table, and a local table item comprises an interface ID domain, a local address domain and a life cycle domain;

step 201: starting;

step 204: finishing;

Fig. 3 is a schematic flow chart of establishing a path table according to the present invention. The fixed sensing node sends a beacon message periodically, the source address of the beacon message is the address of the fixed sensing node, the local prefix and the mobile prefix of the address are both 0, the fixed prefix is the hardware ID of the fixed sensing node, the destination address of the beacon message is a broadcast address, and the load is an upstream table of the fixed sensing node;

step 301: starting;

step 306: and (6) ending.

Fig. 4 is a schematic diagram of a local data communication process according to the present invention. Under the condition that the mobile sensing node MN1 is connected with the fixed sensing node FN1 through a link, the address is MA1, the local prefix of the address MA1 is the hardware ID of the local controller LC1, the address of the local controller LC1 is LA1, the fixed prefix is equal to the hardware ID of the fixed sensing node FN1, the mobile sensing node MN2 is connected with the fixed sensing node FN2 through a link, the address is MA2, the local prefix of the address MA2 is the hardware ID of the local controller LC2, the address of the local controller LC2 is LA2, and the fixed prefix of the address MA2 is the hardware ID of the fixed sensing node FN2, if the condition 1 is met, the mobile sensing node MN1 executes the following process to realize communication with the mobile sensing node MN 2; condition 1: in the upstream table of the fixed sensing node FN1, there is at least one upstream table entry whose local address is LA2, and in the upstream table of the fixed sensing node FN2, there is at least one upstream table entry whose local address is LA 1;

step 401: starting;

step 415: and (6) ending.

Fig. 5 is a schematic diagram of a data acquisition process according to the present invention. Under the condition that the mobile sensing node MN1 is link-connected to the fixed sensing node FN1, the address is MA1, the local prefix of the address MA1 is the hardware ID of the local controller LC1, the address of the local controller LC1 is LA1, the fixed prefix is equal to the hardware ID of the fixed sensing node FN1, the mobile sensing node MN2 is link-connected to the fixed sensing node FN2, the address is MA2, the local prefix of the address MA2 is the hardware ID of the local controller LC2, the address of the local controller LC2 is LA2, and the fixed prefix of the address MA2 is the hardware ID of the fixed sensing node FN2, if the condition 1 is not met, the mobile sensing node MN1 implements the following process to communicate with the mobile sensing node MN 2:

step 501: starting;

step 515: and (6) ending.

Example 1

Based on the simulation parameters in table 1, this embodiment simulates an implementation method of a next-generation sensor network communication system in the present invention, and the performance analysis is as follows: when the transmission quantity of the network data is small, the delay of the sensing node for acquiring the data is low, and when the transmission quantity of the network data is large, the delay of the mobile node for acquiring the data is high; the average delay for the network to acquire data is 273 ms.

TABLE 1 simulation parameters

The present invention provides a method for implementing a next generation sensor network communication system, and a method and a way for implementing the technical solution are many, and the above description is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, a plurality of improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be regarded as the protection scope of the present invention. The components not specified in this embodiment can be implemented by the prior art.

Claims

1. The method for realizing the next generation sensor network communication system is characterized in that the next generation sensor network comprises a central controller, more than two local controllers and sensor nodes; the sensor nodes are divided into fixed sensor nodes and mobile sensor nodes; the central controller and the local controllers are routers, the central controller is used for managing the local controllers, and the local controllers are used for managing the sensing nodes;

the sensing node and the local controller are respectively identified by unique addresses, and the addresses are composed of local prefixes, fixed prefixes and mobile prefixes; the fixed prefix and the mobile prefix of the local controller address are both 0, and the mobile prefix of the fixed sensing node address is 0;

step 101: starting;

step 112: finishing;

2. The method of claim 1, wherein the central controller stores a local table, and a local table entry comprises an interface ID field, a local address field, and a life cycle field;

step 201: starting;

step 204: finishing;

3. The method according to claim 2, wherein the fixed sensor node periodically transmits a beacon message, the source address of the beacon message is its own address, the local prefix and the mobile prefix of the address are both 0, the fixed prefix is its own hardware ID, the destination address of the beacon message is a broadcast address, and the load is an upstream table of the fixed sensor node;

step 301: starting;

step 306: and (6) ending.

4. The method as claimed in claim 2, wherein the mobile sensor node MN1 implements the following process to implement communication with the mobile sensor node MN2 if condition 1 is satisfied, under the condition that the mobile sensor node MN1 is linked with the fixed sensor node FN1, the address is MA1, the local prefix of the address MA1 is the hardware ID of the local controller LC1, the address of the local controller LC1 is LA1, the fixed prefix is equal to the hardware ID of the fixed sensor node FN1, the mobile sensor node MN2 is linked with the fixed sensor node FN2, the address is MA2, the local prefix of the address MA2 is the hardware ID of the local controller LC2, the address of the local controller LC2 is LA2, and the fixed prefix of the address MA2 is the hardware ID of the fixed sensor node FN 2; condition 1: in the upstream table of the fixed sensing node FN1, there is at least one upstream table entry whose local address is LA2, and in the upstream table of the fixed sensing node FN2, there is at least one upstream table entry whose local address is LA 1;

step 401: starting;

step 415: and (6) ending.

5. The method as claimed in claim 4, wherein the mobile sensor node MN1 implements the following process to communicate with the mobile sensor node MN2 if condition 1 is not satisfied under the condition that the mobile sensor node MN1 is linked with the fixed sensor node FN1, the address is MA1, the local prefix of the address MA1 is the hardware ID of the local controller LC1, the address of the local controller LC1 is LA1, the fixed prefix is equal to the hardware ID of the fixed sensor node FN1, the mobile sensor node MN2 is linked with the fixed sensor node FN2, the address is MA2, the local prefix of the address MA2 is the hardware ID of the local controller LC2, the address of the local controller LC2 is LA2, and the fixed prefix of the address MA2 is the hardware ID of the fixed sensor node FN 2:

step 501: starting;

step 515: and (6) ending.