CN108347381B - A New Generation Data Network Communication Method - Google Patents

Abstract

The present invention provides a new generation data network communication method. The network includes a backbone network and more than two end networks, one backbone network includes more than two data routers, one end network includes a border router, more than two The access router and the mobile node are formed; in the present invention, the node can obtain data quickly, thereby greatly reducing the data communication delay and improving the data communication quality. The invention can be applied to many fields such as traffic road condition inspection and control, agricultural engineering, etc., and has wide application prospects.

Description

A New Generation Data Network Communication Method

technical field

The invention relates to a communication method, in particular to a new generation data network communication method.

Background technique

The communication between nodes in the next generation network is realized through the forwarding and routing of intermediate nodes. Therefore, one of the key technologies to be solved in the realization of the next generation network is to reduce the data transmission delay so that users can quickly obtain network services. With the development of next-generation network technology, the next-generation network will become a mode for providing services in the future network.

At present, the implementation mode of the next generation network is realized by broadcasting, so the delay and cost are relatively large, which reduces the network service performance. Therefore, how to reduce the delay of providing services in the next generation network has become a hot research issue in recent years.

Contents of the invention

Purpose of the invention: The technical problem to be solved by the present invention is to provide a new generation data network communication method for the deficiencies of the prior art.

Technical solution: The present invention discloses a new generation data network communication method. The network includes a backbone network and more than two end networks, one backbone network includes more than two data routers, and one end network includes a border router, More than two access routers and mobile nodes; a data router has T1 interfaces, T1 is a positive integer greater than 1, each interface is uniquely identified by an interface ID j1, and j1 ranges from 1 to T1; border routers and access The routers each include an upstream interface and T2 downstream interfaces, where T2 is a positive integer greater than 1. The upstream interface is uniquely identified by the interface ID T2+1, and each downstream interface is uniquely identified by the interface ID j2, where j2 ranges from 1 to T2; The mobile node has an interface;

The upstream interface of a border router is connected to an interface link of a data router, and each downstream interface of a border router is connected to an upstream interface link of an access router; an upstream interface of an access router is connected to an access router or a border router Each downstream interface of an access router is connected with an upstream interface of an access router or an interface link of a mobile node;

A type of data is uniquely identified by a name, and a name is uniquely identified by a name prefix and a name ID; an end network or a border router in an end network is uniquely identified by a name prefix, which is preset, such as china/js/cslg ;

A message includes name field, source interface ID set, backbone interface ID set, destination interface ID set, message type and payload;

The message types are shown in the table below:

message name message type value make an announcement 1 data release message 2 request message 3 response message 4

Each border router saves a backbone table and a stub table. A backbone table entry is composed of a name prefix field, an interface ID set field and a life cycle field; an end table is composed of a name field, an interface ID set field and a life cycle field;

The border router ER1 is uniquely identified by the name prefix NP1. After the border router ER1 is started, it periodically performs the following operations to create a backbone table:

Step 101: start;

Step 102: The border router ER1 sends a release message from the upstream interface. In the release message, the name prefix of the name domain is NP1, the name ID is 0, the field value of the source interface ID set is empty, the backbone interface ID set is empty, and the destination interface The ID set is empty, the message type is 1, and the payload is empty;

Step 103: If the data router receives the publish message, execute step 104, otherwise execute step 108;

Step 104: After the data router receives the release message from the interface p1, it adds the interface p1 to the source interface ID set of the release message, and the interface p1 is the last element of the source interface ID set; the data router checks the backbone table, if it exists A backbone table entry, the name prefix field value of the backbone table entry is equal to the name prefix in the name of the published message received and the interface ID set field value is equal to the source interface ID set of the published message, then perform step 105, otherwise perform step 106 ;

Step 105: The data router that receives the published message selects a backbone entry whose name prefix field value is equal to the name prefix in the name of the received published message, and whose interface ID set field value is equal to the source interface of the published message ID set, set the lifetime of the backbone entry to a maximum value, for example 500ms, and execute step 107;

Step 106: The data router that receives the release message creates a backbone entry, the name prefix field value of the backbone entry is equal to the name prefix in the name of the received release message, and the interface ID set field value is equal to the source interface ID of the release message A collection with lifetime set to the maximum value;

Step 107: The data router that receives the release message forwards the release message from every interface except p1, and executes step 103;

Step 108: After the border router receives the publish message from its own interface p2, it adds the interface p2 to the source interface ID set of the publish message, and the interface p2 is the last element of the source interface ID set; the border router checks the backbone table, If there is a backbone table entry, the name prefix field value of the backbone table entry is equal to the name prefix in the name of the published message name received, and the interface ID set field value is equal to the source interface ID set of the published message, then perform step 109, otherwise Execute step 110;

Step 109: The border router that receives the advertisement selects a backbone entry whose name prefix field value is equal to the name prefix in the name of the advertisement message received, and whose interface ID set field value is equal to the source interface of the advertisement message ID set, set the lifetime of the backbone entry to the maximum value, for example, 500ms, and execute step 111;

Step 110: The border router that receives the advertisement creates a backbone entry, the name prefix field value of the backbone entry is equal to the name prefix in the name of the advertisement message received, and the interface ID set field value is equal to the source interface ID of the advertisement message A collection with lifetime set to the maximum value;

Step 111: end.

The above process can quickly establish a backbone table to obtain data correctly.

In the method of the present invention, under the condition that the data C1 is uniquely identified by the name NA1, and the name NA1 is composed of the name prefix NP1 and the name ID NID1, if the node N1 can provide the data C1, it will periodically perform the following operations to create an end table:

Step 201: start;

Step 202: Node N1 sends a data release message. In the data release message, the name field is NA1, the value of the source interface ID set field is empty, the backbone interface ID set is empty, the destination interface ID set is empty, and the message type is 2. load is empty;

Step 203: If the access router receives the data publishing message, execute step 204, otherwise execute step 208;

Step 204: After the access router receives the data publishing message from its own interface p3, it adds the interface p3 to the source interface ID set of the data publishing message, and the interface p3 is the last element of the source interface ID set; the access router Check the end table, if there is an end entry, the name field value of the end entry is equal to the name in the name of the received data publishing message, and the interface ID set field value is equal to the source interface ID set of the data publishing message, then execute Step 205, otherwise execute step 206;

Step 205: The access router that has received the data release message selects an end entry whose name field value is equal to the name of the received data release message, and whose interface ID set field value is equal to the source interface of the data release message ID set, set the life cycle of the terminal entry to the maximum value, and execute step 207;

Step 206: The access router that receives the data release message creates an end entry, the name field value of the end entry is equal to the name of the received data release message, and the interface ID set field value is equal to the source interface ID of the data release message A collection with lifetime set to the maximum value;

Step 207: The access router that has received the data publishing message forwards the data publishing message from every interface except interface p3, and executes step 203;

Step 208: After the border router receives the data publishing message from its downstream interface p4, it adds the interface p4 to the source interface ID set of the data publishing message, and the interface p4 is the last element of the source interface ID set; the border router views End table, if there is an end table entry, the name field value of the end table entry is equal to the name in the name of the received data publishing message, and the interface ID set field value is equal to the source interface ID set of the data publishing message, then perform the steps 209, otherwise execute step 210;

Step 209: The border router that receives the data release message selects an end entry whose name field value is equal to the name of the received data release message, and whose interface ID set field value is equal to the source interface ID of the data release message Set, set the life cycle of the terminal entry to the maximum value, for example, 500ms, and execute step 211;

Step 210: The border router that receives the data release message creates an end entry, the name field value of the end entry is equal to the name of the received data release message, and the interface ID set field value is equal to the source interface ID set of the data release message , the lifetime is set to the maximum value;

Step 211: end.

The above process can quickly establish the terminal table to obtain the data correctly.

In the method of the present invention, under the condition that the data C1 is uniquely identified by the name NA1, the name NA1 is composed of the name prefix NP1 and the name ID NID1, the node N1 is located in the end network, and the border router of the end network is ER1, if the border router There is an end entry E1 in ER1, and the name field of the end entry E1 is NA1, then node N1 obtains data C1 through the following process:

Step 301: start;

Step 302: Node N1 sends a request message. In the request message, the name field is NA1, the source interface ID set field is empty, the backbone interface ID set field is empty, the destination interface ID set field is empty, the message type is 3, and the payload Is empty;

Step 303: If the access router receives the request message, execute step 304, otherwise execute step 305;

Step 304: The access router receives the request message from its downstream interface x1, adds interface x1 to the source interface ID set of the request message, and forwards the request message from the upstream interface with interface x1 as the last element of the source interface ID set , execute step 303;

Step 305: The border router receives the request message from its downstream interface x2, and adds the interface x2 to the source interface ID set of the request message, and the interface x2 is the last element of the source interface ID set; the border router selects an end entry , the name field of the end entry is equal to the name field of the request message, and the destination interface ID set of the request message is updated to the interface ID set of the end entry; the border router saves the last An interface ID L1, delete the interface L1 from the set of destination interface IDs of the request message, and forward the request message from the interface L1;

Step 306: If the access router receives the request message, execute step 307, otherwise execute step 308;

Step 307: After receiving the request message, the access router saves the last interface ID L2 in the request message destination interface ID set, deletes interface L2 from the request message destination interface ID set, and forwards the request message from interface L2, Execute step 306;

Step 308: After receiving the request message, the node sends a response message. In the response message, the name field value is equal to the name of the received request message, the source interface ID set is empty, the backbone interface ID set is empty, and the destination interface ID set is empty. It is equal to the source interface ID set of the received request message, the message type is 4, and the payload is the data identified by the name of the received request message;

Step 309: If the access router receives the response message, execute step 310, otherwise execute step 311;

Step 310: After receiving the response message from the downstream interface, the access router forwards the response message from the upstream interface, and executes step 309;

Step 311: After receiving the response message, the border router saves the last interface ID L3 in the destination interface ID set of the response message, deletes the interface L3 from the destination interface ID set of the response message, and forwards the response message from the interface L3;

Step 312: If the access router receives the response message, execute step 313, otherwise execute step 314;

Step 313: After receiving the response message, the access router saves the last interface ID L4 in the response message destination interface ID set, deletes interface L4 from the response message destination interface ID set, and forwards the response message from interface L4, Execute step 312;

Step 314: After receiving the response message, the node N1 saves the data in the response message;

Step 315: end.

Nodes can quickly obtain data through the above process.

In the method of the present invention, under the condition that the data C2 is uniquely identified by the name NA2, the name NA2 is composed of the name prefix NP2 and the name ID NID2, the node N1 is located in the end network, and the border router of the end network is ER1, if the border router There is no end table entry whose name field is NA2 in the end table of ER1, then node N1 obtains data C2 through the following process:

Step 401: start;

Step 402: Node N1 sends a request message. In the request message, the name field is NA1, the source interface ID set field is empty, the backbone interface ID set field is empty, the destination interface ID set field is empty, the message type is 3, and the payload Is empty;

Step 403: If the access router receives the request message, execute step 404, otherwise execute step 405;

Step 404: The access router receives the request message from its downstream interface y1, adds the interface y1 to the source interface ID set of the request message, and forwards the request message from the upstream interface with interface y1 as the last element of the source interface ID set , execute step 403;

Step 405: The border router receives the request message from its downstream interface y2, and adds interface y2 to the source interface ID set of the request message, with interface x2 as the last element of the source interface ID set; the border router selects a backbone entry , the name prefix field of the backbone entry is equal to the name prefix in the request message name, and the destination interface ID set of the request message is updated to the interface ID set of the backbone entry; the border router saves the request message destination interface ID set The last interface ID F1 in the request message, delete the interface F1 from the set of destination interface IDs of the request message, and forward the request message from the interface F1;

Step 406: If the border router receives the request message, then execute step 408, otherwise execute step 407;

Step 407: After receiving the request message from its own interface y3, the data router adds interface y3 to the backbone interface ID set of the request message, with interface y3 as the last element of the source interface ID set; the data router saves the request message purpose The last interface ID F2 in the interface ID set, delete the interface F2 from the request message destination interface ID set, forward the request message from the interface F2, and execute step 406;

Step 408: The border router receives the request message from its own interface y4, and adds the interface y4 to the backbone interface ID set of the request message, and the interface y4 is used as the last element of the backbone interface ID set; the border router selects an end entry, The name field of the end entry is equal to the name of the request message, and the destination interface ID set of the request message is updated to the interface ID set of the end entry; the border router saves the last interface in the request message destination interface ID set ID F3, delete the interface F3 from the ID set of the destination interface of the request message, and forward the request message from the interface F3;

Step 409: If the access router receives the request message, execute step 410, otherwise execute step 411;

Step 410: After receiving the request message, the access router saves the last interface ID F4 in the request message destination interface ID set, deletes interface F4 from the request message destination interface ID set, and forwards the request message from interface F4, Execute step 409;

Step 411: After the node receives the request message, it sends a response message. In the response message, the name domain value is equal to the name of the received request message, the source interface ID set is empty, and the backbone interface ID set is equal to the received request message. The backbone interface ID set, the destination interface ID set is equal to the source interface ID set of the received request message, the message type is 4, and the payload is the data identified by the name of the received request message;

Step 412: If the access router receives the response message, execute step 413, otherwise execute step 414;

Step 413: After receiving the response message from the downstream interface, the access router forwards the response message from the upstream interface, and executes step 412;

Step 414: After receiving the response message, the border router saves the last interface ID F5 in the backbone interface ID set of the response message, deletes interface F5 from the backbone interface ID set of the response message, and forwards the response message from interface F5;

Step 415: If the border router receives the response message, then execute step 417, otherwise execute step 416;

Step 416: After receiving the response message, the data router saves the last interface ID F6 in the backbone interface ID set of the response message, deletes the interface F6 from the backbone interface ID set of the response message, forwards the response message from the interface F6, and executes the steps 415;

Step 417: After receiving the response message, the border router saves the last interface ID F7 in the destination interface ID set of the response message, deletes the interface F7 from the destination interface ID set of the response message, and forwards the response message from the interface F7;

Step 418: If the access router receives the response message, execute step 419, otherwise execute step 420;

Step 419: After receiving the response message, the access router saves the last interface ID F8 in the response message destination interface ID set, deletes interface F8 from the response message destination interface ID set, and forwards the response message from interface F8, Execute step 418;

Step 419: After receiving the response message, the node N1 saves the data in the response message;

Step 420: end.

Nodes can quickly obtain data through the above process.

Beneficial effects: the present invention provides a new generation data network communication method. In the present invention, nodes can obtain data quickly, thereby greatly reducing data communication delay and improving data communication quality. The invention can be applied to many fields such as traffic road condition inspection and control, agricultural engineering, etc., and has wide application prospects.

Description of drawings

The advantages of the above and/or other aspects of the present invention will become clearer as the present invention will be further described below in conjunction with the accompanying drawings and specific embodiments.

Fig. 1 is a schematic flow chart of constructing a backbone table according to the present invention.

Fig. 2 is a schematic flow chart of constructing an end table according to the present invention.

FIG. 3 is a schematic diagram of the data communication process described in the present invention.

FIG. 4 is a schematic diagram of the data acquisition process described in the present invention.

Detailed ways:

The invention provides a new-generation data network communication method. In the invention, nodes can obtain data quickly, thereby greatly reducing data communication delay and improving data communication quality. The invention can be applied to many fields such as traffic road condition inspection and control, agricultural engineering, etc., and has wide application prospects.

Fig. 1 is a schematic flow chart of constructing a backbone table according to the present invention. The network includes a backbone network and more than two end networks, a backbone network includes more than two data routers, an end network includes a border router, more than two access routers and mobile nodes; a data router has T1 interfaces, T1 is a positive integer greater than 1, each interface is uniquely identified by an interface ID j1, j1 ranges from 1 to T1; the border router and the access router each include an upstream interface and T2 downstream interfaces, and T2 is greater than 1 is a positive integer, the upstream interface is uniquely identified by the interface ID T2+1, and each downstream interface is uniquely identified by the interface ID j2, where j2 takes a value from 1 to T2; a mobile node has one interface;

The upstream interface of a border router is connected to an interface link of a data router, and each downstream interface of a border router is connected to an upstream interface link of an access router; an upstream interface of an access router is connected to an access router or a border router Each downstream interface of an access router is connected with an upstream interface of an access router or an interface link of a mobile node;

A type of data is uniquely identified by a name, and a name is uniquely identified by a name prefix and a name ID; an end network or a border router in an end network is uniquely identified by a name prefix, which is preset;

A message includes name field, source interface ID set, backbone interface ID set, destination interface ID set, message type and payload;

The message types are shown in the table below:

message name message type value make an announcement 1 data release message 2 request message 3 response message 4

Each border router saves a backbone table and a stub table. A backbone table entry is composed of a name prefix field, an interface ID set field and a life cycle field; an end table is composed of a name field, an interface ID set field and a life cycle field;

The border router ER1 is uniquely identified by the name prefix NP1. After the border router ER1 is started, it periodically performs the following operations to create a backbone table:

Step 101: start;

Step 102: The border router ER1 sends a release message from the upstream interface. In the release message, the name prefix of the name domain is NP1, the name ID is 0, the field value of the source interface ID set is empty, the backbone interface ID set is empty, and the destination interface The ID set is empty, the message type is 1, and the payload is empty;

Step 103: If the data router receives the publish message, execute step 104, otherwise execute step 108;

Step 104: After the data router receives the release message from the interface p1, it adds the interface p1 to the source interface ID set of the release message, and the interface p1 is the last element of the source interface ID set; the data router checks the backbone table, if it exists A backbone table entry, the name prefix field value of the backbone table entry is equal to the name prefix in the name of the published message received and the interface ID set field value is equal to the source interface ID set of the published message, then perform step 105, otherwise perform step 106 ;

Step 105: The data router that receives the published message selects a backbone entry whose name prefix field value is equal to the name prefix in the name of the received published message, and whose interface ID set field value is equal to the source interface of the published message ID set, set the life cycle of the backbone entry to the maximum value, and execute step 107;

Step 106: The data router that receives the release message creates a backbone entry, the name prefix field value of the backbone entry is equal to the name prefix in the name of the received release message, and the interface ID set field value is equal to the source interface ID of the release message A collection with lifetime set to the maximum value;

Step 107: The data router that receives the release message forwards the release message from every interface except p1, and executes step 103;

Step 108: After the border router receives the publish message from its own interface p2, it adds the interface p2 to the source interface ID set of the publish message, and the interface p2 is the last element of the source interface ID set; the border router checks the backbone table, If there is a backbone table entry, the name prefix field value of the backbone table entry is equal to the name prefix in the name of the published message name received, and the interface ID set field value is equal to the source interface ID set of the published message, then perform step 109, otherwise Execute step 110;

Step 109: The border router that receives the advertised message selects a backbone entry whose name prefix field value is equal to the name prefix in the received advertised message name, and whose interface ID set field value is equal to the source interface of the advertised message ID set, set the life cycle of the backbone table item to the maximum value, and execute step 111;

Step 110: The border router that receives the advertisement creates a backbone entry, the name prefix field value of the backbone entry is equal to the name prefix in the name of the advertisement message received, and the interface ID set field value is equal to the source interface ID of the advertisement message A collection with lifetime set to the maximum value;

Step 111: end.

Fig. 2 is a schematic flow chart of constructing an end table according to the present invention. Under the condition that data C1 is uniquely identified by name NA1, and name NA1 is composed of name prefix NP1 and name ID NID1, if node N1 can provide data C1, it will periodically perform the following operations to create an end table:

Step 201: start;

Step 202: Node N1 sends a data release message. In the data release message, the name field is NA1, the value of the source interface ID set field is empty, the backbone interface ID set is empty, the destination interface ID set is empty, and the message type is 2. load is empty;

Step 203: If the access router receives the data publishing message, execute step 204, otherwise execute step 208;

Step 204: After the access router receives the data publishing message from its own interface p3, it adds the interface p3 to the source interface ID set of the data publishing message, and the interface p3 is the last element of the source interface ID set; the access router Check the end table, if there is an end entry, the name field value of the end entry is equal to the name in the name of the received data publishing message, and the interface ID set field value is equal to the source interface ID set of the data publishing message, then execute Step 205, otherwise execute step 206;

Step 205: The access router that has received the data release message selects an end entry whose name field value is equal to the name of the received data release message, and whose interface ID set field value is equal to the source interface of the data release message ID set, set the life cycle of the terminal entry to the maximum value, and execute step 207;

Step 206: The access router that receives the data release message creates an end entry, the name field value of the end entry is equal to the name of the received data release message, and the interface ID set field value is equal to the source interface ID of the data release message A collection with lifetime set to the maximum value;

Step 207: The access router that has received the data publishing message forwards the data publishing message from every interface except interface p3, and executes step 203;

Step 208: After the border router receives the data publishing message from its downstream interface p4, it adds the interface p4 to the source interface ID set of the data publishing message, and the interface p4 is the last element of the source interface ID set; the border router views End table, if there is an end table entry, the name field value of the end table entry is equal to the name in the name of the received data publishing message, and the interface ID set field value is equal to the source interface ID set of the data publishing message, then perform the steps 209, otherwise execute step 210;

Step 209: The border router that receives the data release message selects an end entry whose name field value is equal to the name of the received data release message, and whose interface ID set field value is equal to the source interface ID of the data release message set, set the life cycle of the terminal entry to the maximum value, and execute step 211;

Step 210: The border router that receives the data release message creates an end entry, the name field value of the end entry is equal to the name of the received data release message, and the interface ID set field value is equal to the source interface ID set of the data release message , the lifetime is set to the maximum value;

Step 211: end.

FIG. 3 is a schematic diagram of the data communication process described in the present invention. Under the condition that the data C1 is uniquely identified by the name NA1, the name NA1 is composed of the name prefix NP1 and the name ID NID1, the node N1 is located in the end network, and the border router of the end network is ER1, if the border router ER1 has an end entry E1 , the name field of the end entry E1 is NA1, then the node N1 obtains the data C1 through the following process:

Step 301: start;

Step 302: Node N1 sends a request message. In the request message, the name field is NA1, the source interface ID set field is empty, the backbone interface ID set field is empty, the destination interface ID set field is empty, the message type is 3, and the payload Is empty;

Step 303: If the access router receives the request message, execute step 304, otherwise execute step 305;

Step 304: The access router receives the request message from its downstream interface x1, adds interface x1 to the source interface ID set of the request message, and forwards the request message from the upstream interface with interface x1 as the last element of the source interface ID set , execute step 303;

Step 305: The border router receives the request message from its downstream interface x2, and adds the interface x2 to the source interface ID set of the request message, and the interface x2 is the last element of the source interface ID set; the border router selects an end entry , the name field of the end entry is equal to the name field of the request message, and the destination interface ID set of the request message is updated to the interface ID set of the end entry; the border router saves the last An interface ID L1, delete the interface L1 from the set of destination interface IDs of the request message, and forward the request message from the interface L1;

Step 306: If the access router receives the request message, execute step 307, otherwise execute step 308;

Step 307: After receiving the request message, the access router saves the last interface ID L2 in the request message destination interface ID set, deletes interface L2 from the request message destination interface ID set, and forwards the request message from interface L2, Execute step 306;

Step 308: After receiving the request message, the node sends a response message. In the response message, the name field value is equal to the name of the received request message, the source interface ID set is empty, the backbone interface ID set is empty, and the destination interface ID set is empty. It is equal to the source interface ID set of the received request message, the message type is 4, and the payload is the data identified by the name of the received request message;

Step 309: If the access router receives the response message, execute step 310, otherwise execute step 311;

Step 310: After receiving the response message from the downstream interface, the access router forwards the response message from the upstream interface, and executes step 309;

Step 311: After receiving the response message, the border router saves the last interface ID L3 in the destination interface ID set of the response message, deletes the interface L3 from the destination interface ID set of the response message, and forwards the response message from the interface L3;

Step 312: If the access router receives the response message, execute step 313, otherwise execute step 314;

Step 313: After receiving the response message, the access router saves the last interface ID L4 in the response message destination interface ID set, deletes interface L4 from the response message destination interface ID set, and forwards the response message from interface L4, Execute step 312;

Step 314: After receiving the response message, the node N1 saves the data in the response message;

Step 315: end.

FIG. 4 is a schematic diagram of the data acquisition process described in the present invention. Under the condition that the data C2 is uniquely identified by the name NA2, the name NA2 is composed of the name prefix NP2 and the name ID NID2, the node N1 is located in the end network, and the border router of the end network is ER1, if the end table of the border router ER1 does not exist The name field is the end entry of NA2, then node N1 obtains data C2 through the following process:

Step 401: start;

Step 402: Node N1 sends a request message. In the request message, the name field is NA1, the source interface ID set field is empty, the backbone interface ID set field is empty, the destination interface ID set field is empty, the message type is 3, and the payload Is empty;

Step 403: If the access router receives the request message, execute step 404, otherwise execute step 405;

Step 404: The access router receives the request message from its downstream interface y1, adds the interface y1 to the source interface ID set of the request message, and forwards the request message from the upstream interface with interface y1 as the last element of the source interface ID set , execute step 403;

Step 405: The border router receives the request message from its downstream interface y2, and adds interface y2 to the source interface ID set of the request message, with interface x2 as the last element of the source interface ID set; the border router selects a backbone entry , the name prefix field of the backbone entry is equal to the name prefix in the request message name, and the destination interface ID set of the request message is updated to the interface ID set of the backbone entry; the border router saves the request message destination interface ID set The last interface ID F1 in the request message, delete the interface F1 from the set of destination interface IDs of the request message, and forward the request message from the interface F1;

Step 406: If the border router receives the request message, then execute step 408, otherwise execute step 407;

Step 407: After receiving the request message from its own interface y3, the data router adds interface y3 to the backbone interface ID set of the request message, with interface y3 as the last element of the source interface ID set; the data router saves the request message purpose The last interface ID F2 in the interface ID set, delete the interface F2 from the request message destination interface ID set, forward the request message from the interface F2, and execute step 406;

Step 408: The border router receives the request message from its own interface y4, and adds the interface y4 to the backbone interface ID set of the request message, and the interface y4 is used as the last element of the backbone interface ID set; the border router selects an end entry, The name field of the end entry is equal to the name of the request message, and the destination interface ID set of the request message is updated to the interface ID set of the end entry; the border router saves the last interface in the request message destination interface ID set ID F3, delete the interface F3 from the ID set of the destination interface of the request message, and forward the request message from the interface F3;

Step 409: If the access router receives the request message, execute step 410, otherwise execute step 411;

Step 410: After receiving the request message, the access router saves the last interface ID F4 in the request message destination interface ID set, deletes interface F4 from the request message destination interface ID set, and forwards the request message from interface F4, Execute step 409;

Step 411: After the node receives the request message, it sends a response message. In the response message, the name domain value is equal to the name of the received request message, the source interface ID set is empty, and the backbone interface ID set is equal to the received request message. The backbone interface ID set, the destination interface ID set is equal to the source interface ID set of the received request message, the message type is 4, and the payload is the data identified by the name of the received request message;

Step 412: If the access router receives the response message, execute step 413, otherwise execute step 414;

Step 413: After receiving the response message from the downstream interface, the access router forwards the response message from the upstream interface, and executes step 412;

Step 414: After receiving the response message, the border router saves the last interface ID F5 in the backbone interface ID set of the response message, deletes interface F5 from the backbone interface ID set of the response message, and forwards the response message from interface F5;

Step 415: If the border router receives the response message, then execute step 417, otherwise execute step 416;

Step 416: After receiving the response message, the data router saves the last interface ID F6 in the backbone interface ID set of the response message, deletes the interface F6 from the backbone interface ID set of the response message, forwards the response message from the interface F6, and executes the steps 415;

Step 417: After receiving the response message, the border router saves the last interface ID F7 in the destination interface ID set of the response message, deletes the interface F7 from the destination interface ID set of the response message, and forwards the response message from the interface F7;

Step 418: If the access router receives the response message, execute step 419, otherwise execute step 420;

Step 419: After receiving the response message, the access router saves the last interface ID F8 in the response message destination interface ID set, deletes interface F8 from the response message destination interface ID set, and forwards the response message from interface F8, Execute step 418;

Step 419: After receiving the response message, the node N1 saves the data in the response message;

Step 420: end.

Example 1

Based on the simulation parameters in Table 1, this embodiment simulates a new generation of data network communication method in the present invention, and the performance analysis is as follows: when the number of nodes increases, the amount of data increases, the network performance decreases, and the data communication delays With the increase, the average delay of data communication is 1.45s.

Table 1 Simulation parameters

The present invention provides an idea of a new generation data network communication method. There are many methods and ways to realize this technical solution. The above description is only a preferred implementation mode of the present invention. That is to say, without departing from the principle of the present invention, some improvements and modifications can also be made, and these improvements and modifications should also be regarded as the protection scope of the present invention. All components that are not specified in this embodiment can be realized by existing technologies.

Claims (4)

1. A new-generation data network communication method, characterized in that, the network includes a backbone network and more than two end networks, a backbone network includes more than two data routers, and an end network includes a border router, two More than one access router and two or more mobile nodes; a data router has T1 interfaces, T1 is a positive integer greater than 1, each interface is uniquely identified by an interface ID j1, and j1 takes a value from 1 to T1; the border router and The access routers each include an upstream interface and T2 downstream interfaces, where T2 is a positive integer greater than 1, the upstream interface is uniquely identified by the interface ID T2+1, and each downstream interface is uniquely identified by the interface ID j2, where j2 ranges from 1 to T2 ;A mobile node has an interface; The upstream interface of a border router is connected to an interface link of a data router, and each downstream interface of a border router is connected to an upstream interface link of an access router; an upstream interface of an access router is connected to an access router or a border router Each downstream interface of an access router is connected with an upstream interface of an access router or an interface link of a mobile node; A type of data is uniquely identified by a name, and a name is uniquely identified by a name prefix and a name ID; an end network or a border router in an end network is uniquely identified by a name prefix, which is preset; A message includes name field, source interface ID set, backbone interface ID set, destination interface ID set, message type and payload; The message names of the message types are release message, data release message, request message and response message, and the corresponding message type values are 1, 2, 3 and 4 respectively; Each border router saves a backbone table and a stub table. A backbone table entry is composed of a name prefix field, an interface ID set field and a life cycle field; an end table is composed of a name field, an interface ID set field and a life cycle field; The border router ER1 is uniquely identified by the name prefix NP1. After the border router ER1 is started, it periodically performs the following operations to create a backbone table: Step 101: start; Step 102: The border router ER1 sends a release message from the upstream interface. In the release message, the name prefix of the name domain is NP1, the name ID is 0, the field value of the source interface ID set is empty, the backbone interface ID set is empty, and the destination interface The ID set is empty, the message type is 1, and the payload is empty; Step 103: If the data router receives the publish message, execute step 104, otherwise execute step 108; Step 104: After the data router receives the release message from the interface p1, it adds the interface p1 to the source interface ID set of the release message, and the interface p1 is the last element of the source interface ID set; the data router checks the backbone table, if it exists A backbone table entry, the name prefix field value of the backbone table entry is equal to the name prefix in the name of the published message received and the interface ID set field value is equal to the source interface ID set of the published message, then perform step 105, otherwise perform step 106 ; Step 105: The data router that receives the published message selects a backbone entry whose name prefix field value is equal to the name prefix in the name of the received published message, and whose interface ID set field value is equal to the source interface of the published message ID set, set the life cycle of the backbone entry to the maximum value, and execute step 107; Step 106: The data router that receives the release message creates a backbone entry, the name prefix field value of the backbone entry is equal to the name prefix in the name of the received release message, and the interface ID set field value is equal to the source interface ID of the release message A collection with lifetime set to the maximum value; Step 107: The data router that receives the release message forwards the release message from every interface except p1, and executes step 103; Step 108: The border router that receives the publish message from its own interface p2 adds the interface p2 to the source interface ID set of the publish message, and the interface p2 is the last element of the source interface ID set; the border router checks the backbone table, if There is a backbone table entry, the name prefix field value of the backbone table entry is equal to the name prefix in the name of the published message name received, and the interface ID set field value is equal to the source interface ID set of the published message, then execute step 109, otherwise execute Step 110; Step 109: The border router that receives the advertisement selects a backbone entry whose name prefix field value is equal to the name prefix in the name of the advertisement message received, and whose interface ID set field value is equal to the source interface of the advertisement message ID set, set the life cycle of the backbone table item to the maximum value, and execute step 111; Step 110: The border router that receives the advertisement creates a backbone entry, the name prefix field value of the backbone entry is equal to the name prefix in the name of the advertisement message received, and the interface ID set field value is equal to the source interface ID of the advertisement message A collection with lifetime set to the maximum value; Step 111: end. 2. A new generation data network communication method according to claim 1, characterized in that, under the condition that the data C1 is uniquely identified by a name NA1, and the name NA1 is composed of a name prefix NP1 and a name ID NID1, if the mobile node N1 Able to provide data C1, it periodically performs the following operations to create an end table: Step 201: start; Step 202: The mobile node N1 sends a data release message. In the data release message, the name field is NA1, the source interface ID set field value is empty, the backbone interface ID set is empty, the destination interface ID set is empty, and the message type is 2 , the load is empty; Step 203: If the access router receives the data publishing message, execute step 204, otherwise execute step 208; Step 204: After the access router receives the data publishing message from its own interface p3, it adds the interface p3 to the source interface ID set of the data publishing message, and the interface p3 is the last element of the source interface ID set; the access router Check the end table, if there is an end entry, the name field value of the end entry is equal to the name in the name of the received data publishing message, and the interface ID set field value is equal to the source interface ID set of the data publishing message, then execute Step 205, otherwise execute step 206; Step 205: The access router that has received the data release message selects an end entry whose name field value is equal to the name of the received data release message, and whose interface ID set field value is equal to the source interface of the data release message ID set, set the life cycle of the terminal entry to the maximum value, and execute step 207; Step 206: The access router that receives the data release message creates an end entry, the name field value of the end entry is equal to the name of the received data release message, and the interface ID set field value is equal to the source interface ID of the data release message A collection with lifetime set to the maximum value; Step 207: The access router that has received the data publishing message forwards the data publishing message from every interface except interface p3, and executes step 203; Step 208: After the border router receives the data publishing message from its downstream interface p4, it adds the interface p4 to the source interface ID set of the data publishing message, and the interface p4 is the last element of the source interface ID set; the border router views End table, if there is an end table entry, the name field value of the end table entry is equal to the name in the name of the received data publishing message, and the interface ID set field value is equal to the source interface ID set of the data publishing message, then perform the steps 209, otherwise execute step 210; Step 209: The border router that receives the data release message selects an end entry whose name field value is equal to the name of the received data release message, and whose interface ID set field value is equal to the source interface ID of the data release message set, set the life cycle of the terminal entry to the maximum value, and execute step 211; Step 210: The border router that receives the data release message creates an end entry, the name field value of the end entry is equal to the name of the received data release message, and the interface ID set field value is equal to the source interface ID set of the data release message , the lifetime is set to the maximum value; Step 211: end. 3. A new generation data network communication method according to claim 2, wherein the data C1 is uniquely identified by a name NA1, the name NA1 is composed of a name prefix NP1 and a name ID NID1, and the mobile node N1 is located in the end network , under the condition that the border router of the end network is ER1, if there is an end entry E1 in the border router ER1, and the name field of the end entry E1 is NA1, then the mobile node N1 obtains the data C1 through the following process: Step 301: start; Step 302: The mobile node N1 sends a request message. In the request message, the name field value is NA1, the source interface ID set field is empty, the backbone interface ID set field is empty, the destination interface ID set field is empty, and the message type is 3. load is empty; Step 303: If the access router receives the request message, execute step 304, otherwise execute step 305; Step 304: The access router receives the request message from its downstream interface x1, adds interface x1 to the source interface ID set of the request message, and forwards the request message from the upstream interface with interface x1 as the last element of the source interface ID set , execute step 303; Step 305: receiving the request message from its own downstream interface x2, the border router adds interface x2 to the source interface ID set of the request message, with interface x2 as the last element of the source interface ID set; the border router selects an end entry, The name field of the end entry is equal to the name field of the request message, and the destination interface ID set of the request message is updated to the interface ID set of the end entry; the border router saves the last one in the request message destination interface ID set Interface ID L1, delete interface L1 from the set of destination interface IDs of the request message, and forward the request message from interface L1; Step 306: If the access router receives the request message, execute step 307, otherwise execute step 308; Step 307: After receiving the request message, the access router saves the last interface ID L2 in the request message destination interface ID set, deletes interface L2 from the request message destination interface ID set, and forwards the request message from interface L2, Execute step 306; Step 308: The mobile node receiving the request message sends a response message, in which the name field value is equal to the name of the received request message, the source interface ID set is empty, the backbone interface ID set is empty, and the destination interface ID set is empty. It is equal to the source interface ID set of the received request message, the message type is 4, and the payload is the data identified by the name of the received request message; Step 309: If the access router receives the response message, execute step 310, otherwise execute step 311; Step 310: After receiving the response message from the downstream interface, the access router forwards the response message from the upstream interface, and executes step 309; Step 311: The border router that has received the response message saves the last interface ID L3 in the destination interface ID set of the response message, deletes the interface L3 from the destination interface ID set of the response message, and forwards the response message from the interface L3; Step 312: If the access router receives the response message, execute step 313, otherwise execute step 314; Step 313: After receiving the response message, the access router saves the last interface ID L4 in the response message destination interface ID set, deletes interface L4 from the response message destination interface ID set, and forwards the response message from interface L4, Execute step 312; Step 314: After receiving the response message, the mobile node N1 saves the data in the response message; Step 315: end. 4. A new-generation data network communication method according to claim 3, wherein the data C2 is uniquely identified by a name NA2, the name NA2 is composed of a name prefix NP2 and a name ID NID2, and the mobile node N1 is located in the terminal network , under the condition that the border router of the stub network is ER1, if there is no stub entry whose name field is NA2 in the stub table of the border router ER1, the mobile node N1 obtains the data C2 through the following process: Step 401: start; Step 402: The mobile node N1 sends a request message. In the request message, the name field value is NA1, the source interface ID set field is empty, the backbone interface ID set field is empty, the destination interface ID set field is empty, and the message type is 3. load is empty; Step 403: If the access router receives the request message, execute step 404, otherwise execute step 405; Step 404: The access router receives the request message from its downstream interface y1, adds the interface y1 to the source interface ID set of the request message, and forwards the request message from the upstream interface with interface y1 as the last element of the source interface ID set , execute step 403; Step 405: The border router that receives the request message from its downstream interface y2 adds interface y2 to the source interface ID set of the request message, with interface x2 as the last element of the source interface ID set; the border router selects a backbone entry , the name prefix field of the backbone entry is equal to the name prefix in the request message name, and the destination interface ID set of the request message is updated to the interface ID set of the backbone entry; the border router saves the request message destination interface ID set The last interface ID F1 in the request message, delete the interface F1 from the set of destination interface IDs of the request message, and forward the request message from the interface F1; Step 406: If the border router connected to the link forwarding the request message receives the request message, then perform step 408, otherwise perform step 407; Step 407: After receiving the request message from its own interface y3, the data router adds interface y3 to the backbone interface ID set of the request message, with interface y3 as the last element of the source interface ID set; the data router saves the request message purpose The last interface ID F2 in the interface ID set, delete the interface F2 from the request message destination interface ID set, forward the request message from the interface F2, and execute step 406; Step 408: The border router in step 406 receives the request message from its own interface y4, and adds interface y4 to the backbone interface ID set of the request message, with interface y4 as the last element of the backbone interface ID set; the border router selects a End entry, the name field of the end entry is equal to the name of the request message, and the destination interface ID set of the request message is updated to the interface ID set of the end entry; the border router saves the request message in the destination interface ID set The last interface ID F3 of the request message, delete the interface F3 from the set of destination interface IDs of the request message, and forward the request message from the interface F3; Step 409: If the access router receives the request message, execute step 410, otherwise execute step 411; Step 410: After receiving the request message, the access router saves the last interface ID F4 in the request message destination interface ID set, deletes interface F4 from the request message destination interface ID set, and forwards the request message from interface F4, Execute step 409; Step 411: The mobile node that receives the request message sends a response message, in which the name field value is equal to the name of the received request message, the source interface ID set is empty, and the backbone interface ID set is equal to the received request message. The backbone interface ID set, the destination interface ID set is equal to the source interface ID set of the received request message, the message type is 4, and the payload is the data identified by the name of the received request message; Step 412: If the access router receives the response message, execute step 413, otherwise execute step 414; Step 413: After receiving the response message from the downstream interface, the access router forwards the response message from the upstream interface, and executes step 412; Step 414: The border router that has received the response message saves the last interface ID F5 in the backbone interface ID set of the response message, deletes the interface F5 from the backbone interface ID set of the response message, and forwards the response message from the interface F5; Step 415: If the border router connected to the interface link forwarding the response message receives the response message, then perform step 417, otherwise perform step 416; Step 416: After receiving the response message, the data router saves the last interface ID F6 in the backbone interface ID set of the response message, deletes the interface F6 from the backbone interface ID set of the response message, forwards the response message from the interface F6, and executes the steps 415; Step 417: After receiving the response message, the border router in step 415 saves the last interface ID F7 in the destination interface ID set of the response message, deletes interface F7 from the destination interface ID set of the response message, and forwards the response from interface F7 information; Step 418: If the access router receives the response message, execute step 419, otherwise execute step 420; Step 419: After receiving the response message, the access router saves the last interface ID F8 in the response message destination interface ID set, deletes interface F8 from the response message destination interface ID set, and forwards the response message from interface F8, Execute step 418; Step 419: After receiving the response message, the mobile node N1 saves the data in the response message; Step 420: end.