CN109005026B

CN109005026B - Network communication realizing method

Info

Publication number: CN109005026B
Application number: CN201810916535.1A
Authority: CN
Inventors: 王晓喃; 闫海英; 程宏斌
Original assignee: Changshu Institute of Technology
Current assignee: Suzhou Institute Of Technology
Priority date: 2018-08-13
Filing date: 2018-08-13
Publication date: 2021-04-20
Anticipated expiration: 2038-08-13
Also published as: CN109005026A

Abstract

The invention provides a network communication realization method, wherein the network comprises a common node and forwarding equipment, and the forwarding equipment comprises a router, a switch and an access node; the network is divided into more than two domains, and each domain comprises a route, more than two switches, more than two access nodes and more than two common nodes; the node can safely acquire the data service provided by the network through the implementation method provided by the invention, can ensure the safety, shorten the data acquisition delay and cost and improve the service quality, can be applied to the transmission of important information, such as the fields of road condition monitoring, vehicle management and the like, and has wide application prospect.

Description

Network communication realizing method

Technical Field

The present invention relates to a network communication implementation method, and in particular, to a network communication implementation method.

Background

Future networks enable multi-hop wireless communication from node to node. With the continuous development of network technology and the continuous emergence of various new applications, it is urgently required to realize fast network communication to meet the application demand of the user which is increased sharply.

Future networks, as a special type, are data-centric, whereas traditional networks are address-centric and therefore do not facilitate data acquisition. For example, in an IP network, data is provided by a destination node determined by a destination IP address, and if the destination node fails, the data cannot be provided. In the future, the network takes data as the center, and any node can provide the data, so that the delay and the cost of data acquisition are reduced.

However, how to implement data-centric networks requires further research and discussion.

Disclosure of Invention

The purpose of the invention is as follows: the technical problem to be solved by the present invention is to provide a method for implementing network communication, aiming at the defects of the prior art.

The technical scheme is as follows: the invention discloses a network communication realization method, wherein the network comprises a common node and forwarding equipment, and the forwarding equipment comprises a router, a switch and an access node; the network is divided into more than two domains, and each domain comprises a route, more than two switches, more than two access nodes and more than two common nodes; the access node is forwarding equipment and has a forwarding function, and the common node does not have the forwarding function;

the router is provided with more than two upstream wired interfaces and more than two downstream wired interfaces, each upstream interface is connected with the router, and each downstream interface is connected with the switch; one exchanger has an upstream wired interface and more than two downstream wired interfaces, one upstream interface is connected with the router or the exchanger, and one downstream interface is connected with the exchanger or the access node; an access node has an upstream wired interface and a downstream wireless interface, the upstream interface is connected with the switch, the downstream interface is connected with the common node; a common node has a wireless interface connected with a downstream interface link of the access node; each interface is uniquely identified by an interface ID, and the interface with the interface ID i is abbreviated as the interface i; an access node and all common nodes connected with the downstream interface link of the access node form a sub-network;

one router is uniquely identified by a domain name, such as cslg/N6; an access node is uniquely identified by a subnet name, e.g., CS/402, computer school 402 lab; a common node is uniquely identified by a common node name, and the common node name has uniqueness in a domain; the switch does not need any name identification; the network is configured with an inter-domain hash function, and each domain is configured with an intra-domain hash function; the inter-domain hash function and the intra-domain hash function are stored and issued by a third party authentication data center computer, and a common node, an access node or a router registers to the third party authentication data center computer to acquire the inter-domain hash function and the intra-domain hash function of the domain in which the common node, the access node or the router is located;

a common node, an access node or a router is configured with an inter-domain address and an intra-domain address; the inter-domain address is composed of a domain name, a subnet name and a common node name; the intra-domain address is composed of a domain name, a subnet name and a common node name;

the name of the subnet and the name of the common node of the inter-domain address of the router are null, and the name of the subnet and the name of the common node of the intra-domain address of the router are null; the common node name of the inter-domain address of the access node is null, and the common node name of the intra-domain address of the access node is null; the common node name of the inter-domain address of one common node is not null, and the common node name of the intra-domain address of one common node is not null;

each router and switch maintains a forwarding table, and a forwarding table entry comprises an inter-domain subnet name, an intra-domain subnet name, an interface ID and a life cycle domain;

the subnet name of the access node AP1 is SN1, the access node AP1 is located in a domain D1, the router of the domain D1 is R1, the domain name of the router R1 is DN1, the access node AP1 obtains an inter-domain hash function H1 and an intra-domain hash function H2, such as MD5(Message Digest Algorithm, chinese name is fifth edition), the access node AP1 calculates the inter-domain hash value HSN1 of the subnet name SN1 by using the inter-domain hash function H1, the access node AP1 calculates the intra-domain hash value HSN2 of the subnet name SN1 by using the intra-domain hash function H2, and the access node AP1 calculates the intra-domain hash value HDN2 of the domain name DN1 by using the intra-domain hash function H2, as shown in formulas (1) -3; the access node AP1 performs the following process to build a forwarding table:

HSN1 ═ H1(SN1) formula (1)

HSN2 ═ H2(SN1) formula (2)

HDN2 ═ H2(DN1) formula (3)

Step 101: starting;

step 102: the access node AP1 creates an intra-domain address, the domain name of the intra-domain address is the intra-domain hash value HDN2 of the domain name DN1, the subnet name is the intra-domain hash value HSN2 of the subnet name SN1, and the common node name is null; the access node AP1 sends a release message from the upstream wired interface, the source address of the release message is a constructed address, the destination address is null, and the load is the inter-domain hash value HSN1 of the subnet name SN 1;

step 103: judging whether the router R1 receives the publish message from the downstream interface f1 or the switch receives the publish message from the downstream interface f2, if the router R1 does, executing the step 106, otherwise, executing the step 104;

step 104: the switch looks up a forwarding table, if a forwarding table entry exists, the intra-domain subnet name of the forwarding table entry is equal to the subnet name of the issuing message source address, the switch updates the inter-domain subnet name of the forwarding table entry to the inter-domain hash value HSN1 in the issuing message load, updates the interface ID to f2, and sets the life cycle to a maximum value, for example, 1s, otherwise, the switch creates a forwarding table entry, the intra-domain subnet name of the forwarding table entry is equal to the subnet name of the issuing message source address, the inter-domain subnet name of the forwarding table entry is equal to the inter-domain hash value HSN1 in the issuing message load, the interface ID is equal to f2, and the life cycle is a maximum value;

step 105: the switch receiving the publish message from the downstream interface f2 forwards the publish message from the upstream interface, and executes step 103;

step 106: the router R1 checks a forwarding table, if a forwarding table entry exists, the intra-domain subnet name of the forwarding table entry is equal to the subnet name of the issuing message source address, the router R1 updates the inter-domain subnet name of the forwarding table entry to the inter-domain hash value HSN1 in the issuing message load, updates the interface ID to f1, and sets the life cycle to the maximum value, otherwise, the router R1 creates a forwarding table entry, the intra-domain subnet name of the forwarding table entry is equal to the subnet name of the issuing message source address, the inter-domain subnet name of the forwarding table entry is equal to the inter-domain hash value HSN1 in the issuing message load, the interface ID is equal to f1, and the life cycle is the maximum value;

step 107: and (6) ending.

The access node establishes a forwarding table through the process, so that an optimal routing path can be established through the forwarding table, the forwarding table realizes correct forwarding of the message through the interface ID, and therefore correctness of communication is ensured.

In the method of the invention, a router maintains a domain table, and a domain table item comprises a domain name, a distance, an interface ID and a life cycle domain; the router R1 is located in the domain D1, the domain name is DN1, after the router R1 obtains the inter-domain hash function H1, the inter-domain hash value HDN1 of the domain name DN1 is calculated by using the hash function H1, as shown in formula (4), and then the following processes are performed to establish a domain table:

HDN1 ═ H1(DN1) formula (4)

Step 201: starting;

step 202: the router R1 creates an inter-domain address, the domain name of the inter-domain address is a hash value HDN1, and the subnet name and the common node name are both null; the router R1 sends a domain release message, the source address of the domain release message is the constructed inter-domain address, the destination address is null, the load is the parameter t1, and the initial value of the parameter t1 is 0;

step 203: after receiving the domain publishing message from the upstream interface u1, the router increments the value of the parameter t1 in the domain publishing message load by 1, detects the own domain table, and judges whether a domain table entry exists, the domain name of the domain table entry is equal to the domain name of the domain publishing message source address, and the distance domain value is less than the parameter t1 in the domain publishing message load, if so, step 204 is executed, otherwise, step 205 is executed;

step 204: the router receiving the domain publishing message from the upstream interface u1 discards the domain publishing message, and performs step 209;

step 205: the router receiving the domain distribution message from the upstream interface u1 detects its own domain table, and determines whether there is a domain table entry, the domain name of the domain table entry is equal to the domain name of the source address of the domain distribution message and the distance domain value is equal to or greater than the parameter t1 in the load of the domain distribution message, if yes, step 206 is executed, otherwise step 207 is executed;

step 206: a router receiving a domain distribution message from an upstream interface u1 selects a domain table entry, the domain name of the domain table entry is equal to the domain name of the source address of the domain distribution message, and the distance domain value is equal to or greater than the parameter t1 in the load of the domain distribution message, the router updates the distance domain value of the domain table entry to the parameter t1 in the load of the domain distribution message, the interface ID is updated to u1, the life cycle is set to the maximum value, for example, 500ms, and step 208 is executed;

step 207: the router receiving the domain issuing message from the upstream interface u1 creates a domain table entry, the domain name of the domain table entry is equal to the domain name of the source address of the domain issuing message, the distance domain value is equal to the parameter t1 in the load of the domain issuing message, the interface ID is equal to u1, and the life cycle is set to the maximum value;

step 208: the router receiving the domain publish message from the upstream interface u1 forwards the domain publish message from each upstream interface except the interface u1, executing step 203;

step 209: and (6) ending.

The router establishes a domain table through the process so as to establish an optimal routing path between different domains through the domain table, the domain table realizes the shortest routing path through a distance domain value, and realizes the correct forwarding of messages through an interface ID (identity), thereby ensuring the correctness of communication, and meanwhile, the process ensures the instantaneity and the validity of a forwarding table through a life cycle, thereby ensuring the validity and the correctness of communication.

In the method of the invention, under the condition that the domain name of the router R1 is DN1 and the intra-domain hash function of the domain is H2, the router R1 periodically executes the following operations to release the domain name of the router R1:

step 301: starting;

step 302: the router R1 creates an intra-domain address, the domain name of the intra-domain address is the hash value of the domain name DN1 calculated by the hash function H2, and the subnet name and the common node name are null; the router R1 sends a domain name publishing message from each downstream interface, the source address of the domain name publishing message is a built intra-domain address, the destination address is null, and the load is domain name DN 1;

step 303: judging whether the access node or the switch receives the domain name publishing message from the upstream interface, if the access node is the access node, executing the step 305, otherwise, executing the step 304;

step 304: after receiving the domain name publishing message from the upstream interface, the switch stores the domain name DN1 in the load of the domain name publishing message, and then forwards the domain name publishing message from each downstream interface, and step 303 is executed;

step 305: after receiving the domain name publishing message from the upstream interface, the access node stores the domain name DN1 in the domain name publishing message load, then adds the subnet name of the access node into the domain name publishing message load, and forwards the domain name publishing message from the downstream interface;

step 306: after receiving the domain name publishing message, the common node stores the domain name DN1 in the domain name publishing message load and the subnet name of the subnet in which the common node is located;

step 307: and (6) ending.

The router publishes the own domain name through the process, so that the node can store the domain name published by the router and the subnet of the subnet where the node is located so as to acquire required data from the subnet. Because the above process is encrypted by the hash function, the security of domain name publishing is realized.

In the method of the invention, an access node, a switch and a router respectively store an aggregation table, and an aggregation table item comprises a source address, a destination address and an interface ID; under the conditions that the common node name of the common node N1 is NN1 and is located in a domain D1, the router in the domain D1 is R1, the domain name of the router R1 is DN1, the common node N1 is connected with an access node AP1 link, the subnet name of the access node AP1 is SN1, the common node name of the common node N2 is NN2 and is located in a domain D1 and is connected with the access node AP1 link, the inter-domain hash function is H1, and the intra-domain hash function of the domain D1 is H2, the common node N1 realizes communication with the common node N2 through the following processes:

step 401: starting;

step 402: the ordinary node N1 creates an own intra-domain address, wherein the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN1 calculated by the hash function H2, and the ordinary node name is a hash value of an ordinary node name NN1 calculated by the hash function H2; the common node N1 creates an intra-domain address for the common node N2, the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN1 calculated by the hash function H2, and the common node name is a hash value of a common node name NN2 calculated by the hash function H2; the common node N1 creates an inter-domain address for the common node N2, the domain name of the inter-domain address is a hash value of a domain name DN1 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN1 calculated by the hash function H1, and the common node name is a hash value of a common node name NN2 calculated by the hash function H1; the ordinary node N1 sends a request message, the source address of the request message is the own intra-domain address, the destination address is the intra-domain address of the ordinary node N2, and the load is the inter-domain address of the ordinary node N2;

step 403: the access node AP1 checks the aggregation table after receiving the request message from the downstream interface; judging whether an aggregation table entry exists, wherein the source address of the aggregation table entry is equal to the source address of the request message, and the destination address of the aggregation table entry is equal to the destination address of the request message, if so, executing a step 410, otherwise, executing a step 404;

step 404: the access node AP1 that receives the request message from the downstream interface creates an aggregate entry with a source address and a destination address equal to the source address and the destination address, respectively, of the request message and an interface ID equal to the interface ID of the interface that received the request message; the access node AP1 looks up the aggregation table, if there are at least two aggregation table entries whose destination addresses are equal to the destination address of the received request message or there is at least one aggregation table entry whose destination address is equal to the inter-domain address in the request message load, then step 410 is executed, otherwise step 405 is executed;

step 405: if the access node AP1 that receives the request message from the downstream interface detects that the subnet name of the destination address of the request message is equal to the intradomain hash value of its subnet name calculated using the intradomain hash function H2, then step 406 is performed, otherwise step 413 is performed;

step 406: the access node AP1 that received the request message from the downstream interface forwards the request message from the downstream interface;

step 407: after receiving the request message, the common node creates an intra-domain address and an inter-domain address of the common node; the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN1 calculated by a hash function H2, and the common node name is a hash value of the common node name of the node itself calculated by a hash function H2; the domain name of the inter-domain address is a hash value of a domain name DN1 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN1 calculated by a hash function H1, and the common node name is a hash value of a common node name of the inter-domain address calculated by a hash function H1; if the intra-domain address or inter-domain address of the normal node is equal to the destination address of the request message, performing step 409, otherwise performing step 408;

step 408; the ordinary node receiving the request message discards the request message, and performs step 410;

step 409: the common node receiving the request message sends a response message, the source address of the response message is the destination address of the request message, the destination address of the response message is equal to the source address of the request message, and the load is the inter-domain address in the load of the request message and the response data;

step 410: the access node AP1 checks the aggregation table after receiving the response message; the access node AP1 selects all aggregation entries with destination addresses equal to the source address of the response message or the inter-domain addresses in the load, and for each selected aggregation entry, the access node AP1 performs the following operations: the access node AP1 updates the destination address of the response message to the source address field value of the aggregation table entry, sends the response message from the interface identified by the interface ID field value of the aggregation table entry, and deletes the aggregation table entry;

step 411: after receiving the response message, the common node creates an intra-domain address and an inter-domain address of the common node; the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN1 calculated by a hash function H2, and the common node name is a hash value of the common node name of the node itself calculated by a hash function H2; the domain name of the inter-domain address is a hash value of a domain name DN1 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN1 calculated by a hash function H1, and the common node name is a hash value of a common node name of the inter-domain address calculated by a hash function H1; if the intra-domain address or inter-domain address of the normal node is equal to the destination address of the response message, performing step 412, otherwise performing step 413;

step 412: the common node receiving the response message saves the response data in the response message load;

step 413: and (6) ending.

The node realizes the communication with the local node through the process, and the process realizes the request aggregation through the aggregation table, so that a plurality of nodes can acquire response data through one-time data communication, thereby reducing the data communication delay and cost.

In the method, the name of a common node N1 is NN1, the common node is positioned in a domain D1, a router in the domain D1 is R1, the domain name of a router R1 is DN1, the common node N1 is connected with an access node AP1 link, and the subnet name of an access node AP1 is SN 1; the common node name of the common node N3 is NN3, and is located in the domain D1 and is connected to the access node AP3 via a link, the subnet name of the access node AP3 is SN3, the inter-domain hash function is H1, and the intra-domain hash function of the domain D1 is H2, the common node N1 implements communication with the common node N3 through the following processes:

step 501: starting;

step 502: the ordinary node N1 creates an own intra-domain address, wherein the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN1 calculated by the hash function H2, and the ordinary node name is a hash value of an ordinary node name NN1 calculated by the hash function H2; the common node N1 creates an intra-domain address for the common node N3, the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN1 calculated by the hash function H2, and the common node name is a hash value of a common node name NN3 calculated by the hash function H2; the common node N1 creates an inter-domain address for the common node N3, the domain name of the inter-domain address is a hash value of a domain name DN1 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN1 calculated by the hash function H1, and the common node name is a hash value of a common node name NN3 calculated by the hash function H1; the ordinary node N1 sends a request message, the source address of the request message is the own intra-domain address, the destination address is the intra-domain address of the ordinary node N3, and the load is the inter-domain address of the ordinary node N3;

step 503: the forwarding device checks the aggregation table after receiving the request message from the interface x 1; if there is an aggregation table entry, the source address of the aggregation table entry is equal to the source address of the request message, and the destination address is equal to the destination address of the request message, execute step 514, otherwise execute step 504;

step 504: the forwarding device receiving the request message from the interface x1 creates an aggregation table entry, the source address and the destination address of the aggregation table entry are respectively equal to the source address and the destination address of the request message, and the interface ID is equal to x 1; the forwarding device checks the aggregation table, if at least two aggregation table entries exist, the destination addresses of the two aggregation table entries are equal to the destination address of the received request message, or at least one aggregation table entry exists, the destination address of the aggregation table entry is equal to the inter-domain address in the load of the request message, step 514 is executed, otherwise step 505 is executed;

step 505: if the forwarding device receiving the request message is AP1, performing step 506, otherwise performing step 508;

step 506: if the access node AP1 that receives the request message detects that the subnet name of the destination address of the request message is not equal to the intradomain hash value of its subnet name calculated by the intradomain hash function H2, then step 507 is executed, otherwise step 518 is executed;

step 507: the access node AP1 that received the request message forwards the request message from the upstream interface and performs step 503;

step 508: if the forwarding device receiving the request message is AP3, performing step 510, otherwise performing step 509;

step 509: the forwarding device receiving the request message checks a forwarding table, selects a forwarding table entry, the intra-domain subnet name or the inter-domain subnet name of the forwarding table entry is equal to the subnet name of the destination address of the request message, then forwards the request message from the interface identified by the interface ID of the forwarding table entry, and executes step 503;

step 510: if the access node AP3 that received the request message detects that the subnet name of the destination address of the request message is equal to the intra-domain hash value of its subnet name calculated by using the intra-domain hash function H2, then step 511 is executed, otherwise step 518 is executed;

step 511: the access node AP3 that received the request message forwards the request message from the downstream interface;

step 512: after receiving the request message, the common node creates an intra-domain address and an inter-domain address of the common node; the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN1 calculated by a hash function H2, and the common node name is a hash value of the common node name of the node itself calculated by a hash function H2; the domain name of the inter-domain address is a hash value of a domain name DN1 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN1 calculated by a hash function H1, and the common node name is a hash value of a common node name of the inter-domain address calculated by a hash function H1; if the intra-domain address or inter-domain address of the normal node is equal to the destination address of the request message, go to step 513, otherwise go to step 514;

step 513: the ordinary node receiving the request message sends a response message, the source address of the response message is equal to the destination address of the request message, the destination address of the response message is equal to the source address of the request message, and the load is the inter-domain address in the load of the request message and the response data;

step 514: if the ordinary node receives the response message, go to step 516, otherwise go to step 515;

step 515: the forwarding equipment checks the aggregation table after receiving the response message; the forwarding device selects all aggregation table entries with destination addresses equal to the response message source address or the inter-domain addresses in the load, and for each selected aggregation table entry, the forwarding device executes the following operations: the forwarding device updates the destination address of the response message to the source address field value of the aggregation table entry, sends the response message from the interface identified by the interface ID field value of the aggregation table entry, deletes the aggregation table entry, and performs step 514;

step 516: after receiving the response message, the common node creates an intra-domain address and an inter-domain address of the common node; the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN1 calculated by a hash function H2, and the common node name is a hash value of the common node name of the node itself calculated by a hash function H2; the domain name of the inter-domain address is a hash value of a domain name DN1 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN1 calculated by a hash function H1, and the common node name is a hash value of a common node name of the inter-domain address calculated by a hash function H1; if the intra-domain address or inter-domain address of the normal node is equal to the destination address of the response message, performing step 517, otherwise, performing step 518;

517: the common node receiving the response message saves the response data in the response message load;

step 518: and (6) ending.

The nodes realize the communication with the nodes through the process, the process carries out the correct forwarding of the messages through the forwarding table, thereby ensuring the correctness of the data communication, and the request aggregation is realized through the aggregation table, so that a plurality of nodes can acquire response data through one-time data communication, thereby reducing the delay and the cost of the data communication.

In the method of the present invention, under the condition that the common node name of the common node N1 is NN1, the common node N1 is located in a domain D1, the router in the domain D1 is R1, the domain name of the router R1 is DN1, the common node N1 is connected to the access node AP1 link, the subnet name of the access node AP1 is SN1, the common node name of the common node N4 is NN4, the common node N4 is located in a domain D2, the router in the domain D2 is R2, the domain name of the router R2 is DN2, the common node N4 is connected to the access node AP4 link, the subnet name of the access node AP4 is SN4, the inter-domain hash function is H1, the intra-domain hash function of the domain D1 is H2, and the intra-domain hash function of the domain D2 is H3, the common node N1 realizes communication with the common node N4 through the following processes:

step 601: starting;

step 602: the common node N1 creates an inter-domain address of the node, wherein the domain name of the inter-domain address is a hash value of a domain name DN1 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN1 calculated by the hash function H1, and the common node name is a hash value of a common node name NN1 calculated by the hash function H1; the common node N1 creates an inter-domain address for the common node N4, the domain name of the inter-domain address is a hash value of a domain name DN2 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN4 calculated by the hash function H1, and the common node name is a hash value of a common node name NN4 calculated by the hash function H1; the ordinary node N1 sends a request message, the source address of the request message is the inter-domain address of the ordinary node N4, the destination address is the inter-domain address of the ordinary node N4, and the load is the ordinary node name NN4 of the ordinary node N4;

step 603: the forwarding device checks the aggregation table after receiving the request message from the interface x 2; if there is an aggregation table entry, the source address of the aggregation table entry is equal to the source address of the request message, and the destination address is equal to the destination address of the request message, then step 629 is performed, otherwise step 604 is performed;

step 604: the forwarding device receiving the request message from the interface x2 creates an aggregation table entry, the source address and the destination address of the aggregation table entry are respectively equal to the source address and the destination address of the request message, and the interface ID is equal to x 2; the forwarding device checks the aggregation table, if at least two aggregation table entries exist, and the destination addresses of the two aggregation table entries are equal to the destination address of the received request message, step 621 is executed, otherwise step 605 is executed;

step 605: if the forwarding device receiving the request message is AP1, performing step 606, otherwise performing step 608;

step 606: if the access node AP1 that receives the request message detects that the subnet name of the destination address of the request message is not equal to the hash value of its subnet name calculated by using the intra-domain hash function H2 or the inter-domain hash function H1, then step 607 is executed, otherwise step 629 is executed;

step 607: the access node AP1 that received the request message forwards the request message from the upstream interface and performs step 603;

step 608: if the router R1 receives the request message, go to step 610, otherwise go to step 609;

step 609: the forwarding device receiving the request message forwards the request message from the upstream interface, and performs step 603;

step 610: if router R2 receives the request message, go to step 612, otherwise go to step 611;

step 611: the router receiving the request message checks the domain table, selects a domain table entry, the domain name of the domain table entry is equal to the domain name of the destination address of the request message, forwards the request message from the interface identified by the interface ID of the domain table entry, and executes step 610;

step 612: after receiving the request message from the upstream interface, the router R2 selects a forwarding table, where the inter-domain subnet name of the forwarding table is equal to the subnet name of the destination address of the request message, and constructs an intra-domain address, where the domain name of the intra-domain address is the hash value of domain name DN1 calculated by using hash function H3, the subnet name is the intra-domain subnet name of the forwarding table entry, and the common node name is the hash value of common node name NN4 in the request message load calculated by using hash function H3; the router R2 deletes the ordinary node name NN4 from the request message load, adds the constructed address to the request message load, and forwards the request message from the interface identified by the interface ID of the forwarding table entry;

step 613: the forwarding device that receives the request message from interface x3 looks at the aggregation table; if there is an aggregation table entry, the source address of the aggregation table entry is equal to the source address of the request message, and the destination address is equal to the destination address of the request message, then step 621 is executed, otherwise step 614 is executed;

step 614: the forwarding device receiving the request message from the interface x3 creates an aggregation table entry, the source address and the destination address of the aggregation table entry are respectively equal to the source address and the destination address of the request message, and the interface ID is equal to x 3; the forwarding device checks the aggregation table, if at least two aggregation table entries exist, the destination addresses of the two aggregation table entries are equal to the destination address of the received request message, or at least one aggregation table entry exists, the destination address of the aggregation table entry is equal to the address in the load of the request message, step 621 is executed, otherwise step 615 is executed;

step 615: if the forwarding device receiving the request message is AP4, execute step 617, otherwise execute step 616;

step 616: the forwarding device receiving the request message checks a forwarding table, selects a forwarding table entry whose intra-domain subnet name or inter-domain subnet name is equal to the subnet name of the destination address of the request message, then forwards the request message from the interface identified by the interface ID of the forwarding table entry, and executes step 615;

step 617: if the access node AP4 that receives the request message detects that the subnet name of the destination address of the request message is equal to the intra-domain hash value of its own subnet name calculated by using the inter-domain hash function H1 or the intra-domain hash function H3, then step 618 is executed, otherwise step 629 is executed;

step 618: the access node AP4 that received the request message forwards the request message from the downstream interface;

step 619: after receiving the request message, the common node creates an intra-domain address and an inter-domain address of the common node; the domain name of the intra-domain address is a hash value of a domain name DN3 calculated by a hash function H3, the subnet name is a hash value of a subnet name SN4 calculated by a hash function H3, and the common node name is a hash value of the common node name of the node itself calculated by a hash function H3; the domain name of the inter-domain address is a hash value of a domain name DN2 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN4 calculated by a hash function H1, and the common node name is a hash value of a common node name of the inter-domain address calculated by a hash function H1; if the intra-domain address or inter-domain address of the normal node is equal to the destination address of the request message, performing step 620, otherwise performing step 621;

step 620: the ordinary node receiving the request message sends a response message, the source address of the response message is equal to the destination address of the request message, the destination address of the response message is equal to the source address of the request message, and the load is the address in the request message load and the response data;

step 621: the forwarding equipment checks the aggregation table after receiving the response message; the forwarding device selects all aggregation table entries with destination addresses equal to the response message source address or the intra-domain address in the load, and for each selected aggregation table entry, the forwarding device executes the following operations: the forwarding device updates the destination address of the response message to the source address field value of the aggregation table entry, sends the response message from the interface identified by the interface ID field value of the aggregation table entry, and deletes the aggregation table entry;

step 622: if the forwarding device receiving the response message is R2, executing step 623, otherwise executing step 621;

step 623: if router R1 receives the response message, go to step 625, otherwise go to step 624;

step 624: the router receiving the response message checks the domain table, selects a domain table entry whose domain name is equal to the domain name of the destination address of the response message, forwards the response message from the interface identified by the interface ID of the domain table entry, and executes step 623;

step 625: judging whether the ordinary node or the forwarding device receives the response message, if the ordinary node is the forwarding device, executing step 627, otherwise, executing step 626;

step 626: the forwarding equipment checks the aggregation table after receiving the response message; the forwarding device selects all aggregation table entries with destination addresses equal to the response message source address or the address in the load, and for each selected aggregation table entry, the forwarding device executes the following operations: the forwarding device updates the destination address of the response message to the source address field value of the aggregation table entry, sends the response message from the interface identified by the interface ID field value of the aggregation table entry, deletes the aggregation table entry, and performs step 625;

step 627: after receiving the response message, the common node creates an intra-domain address and an inter-domain address of the common node; the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN1 calculated by a hash function H2, and the common node name is a hash value of the common node name of the node itself calculated by a hash function H2; the domain name of the inter-domain address is a hash value of a domain name DN1 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN1 calculated by a hash function H1, and the common node name is a hash value of a common node name of the inter-domain address calculated by a hash function H1; if the intra-domain address or the inter-domain address of the general node is equal to the destination address of the response message, performing step 628, otherwise performing step 629;

step 628: the common node receiving the response message saves the response data in the response message load;

step 629: and (6) ending.

The node realizes communication with the remote node through the process, the process realizes the safety of data communication through encryption by a hash function, in addition, the process carries out correct forwarding of messages through a domain table and a forwarding table, thereby ensuring the correctness of the data communication, and the request aggregation is realized through an aggregation table, so that a plurality of nodes can acquire response data through one-time data communication, thereby reducing the delay and the cost of the data communication.

Has the advantages that: the invention provides a network communication implementation method, and the node can safely acquire the data service provided by the network through the implementation method provided by the invention, can ensure the safety, shorten the data acquisition delay and cost, and improve the service quality.

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 schematic diagram illustrating a process of establishing a forwarding table according to the present invention.

Fig. 2 is a schematic flow chart of the domain table according to the present invention.

Fig. 3 is a schematic diagram of a distribution process according to the present invention.

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

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

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

The specific implementation mode is as follows:

the invention provides a network communication implementation method, and the node can safely acquire the data service provided by the network through the implementation method provided by the invention, can ensure the safety, shorten the data acquisition delay and cost, and improve the service quality.

Fig. 1 is a schematic diagram illustrating a process of establishing a forwarding table according to the present invention. The network comprises a common node and forwarding equipment, wherein the forwarding equipment comprises a router, a switch and an access node; the network is divided into more than two domains, and each domain comprises a route, more than two switches, more than two access nodes and more than two common nodes;

one router is uniquely identified by a domain name, one access node is uniquely identified by a subnet name, one common node is uniquely identified by a common node name, and the common node name has uniqueness in one domain;

the network is configured with an inter-domain hash function, and each domain is configured with an intra-domain hash function; the inter-domain hash function and the intra-domain hash function are stored and issued by a third party authentication data center computer, and a common node, an access node or a router registers to the third party authentication data center computer to acquire the inter-domain hash function and the intra-domain hash function of the domain in which the common node, the access node or the router is located;

the subnet name of the access node AP1 is SN1, the access node AP1 is located in a domain D1, the router of the domain D1 is R1, the domain name of the router R1 is DN1, the access node AP1 obtains an inter-domain hash function H1 and an intra-domain hash function H2, the access node AP1 calculates an inter-domain hash value HSN1 of the subnet name SN1 by using the inter-domain hash function H1, the access node AP1 calculates an intra-domain hash value HSN2 of the subnet name SN1 by using the intra-domain hash function H2, and the access node AP1 calculates an intra-domain hash value HDN2 of the domain name DN1 by using the intra-domain hash function H2, as shown in formulas (1) -3; the access node AP1 performs the following process to build a forwarding table:

HSN1 ═ H1(SN1) formula (1)

HSN2 ═ H2(SN1) formula (2)

HDN2 ═ H2(DN1) formula (3)

Step 101: starting;

step 104: the switch checks a forwarding table, if a forwarding table entry exists, the intra-domain subnet name of the forwarding table entry is equal to the subnet name of the issuing message source address, the switch updates the inter-domain subnet name of the forwarding table entry to the inter-domain hash value HSN1 in the issuing message load, updates the interface ID to f2, and sets the life cycle to be the maximum value, otherwise, the switch creates a forwarding table entry, the intra-domain subnet name of the forwarding table entry is equal to the subnet name of the issuing message source address, the inter-domain subnet name of the forwarding table entry is equal to the inter-domain hash value HSN1 in the issuing message load, the interface ID is equal to f2, and the life cycle is the maximum value;

step 107: and (6) ending.

Fig. 2 is a schematic flow chart of the domain table according to the present invention. The router maintains a domain table, and a domain table item comprises a domain name, a distance, an interface ID and a life cycle domain; the router R1 is located in the domain D1, the domain name is DN1, after the router R1 obtains the inter-domain hash function H1, the inter-domain hash value HDN1 of the domain name DN1 is calculated by using the hash function H1, as shown in formula (4), and then the following processes are performed to establish a domain table:

HDN1 ═ H1(DN1) formula (4)

Step 201: starting;

step 206: the router which receives the domain publishing message from the upstream interface u1 selects a domain table entry, the domain name of the domain table entry is equal to the domain name of the domain publishing message source address, and the distance domain value is equal to or greater than the parameter t1 in the domain publishing message load, the router updates the distance domain value of the domain table entry to the parameter t1 in the domain publishing message load, the interface ID is updated to u1, the life cycle is set to the maximum value, and step 208 is executed;

step 209: and (6) ending.

Fig. 3 is a schematic diagram of a distribution process according to the present invention. Under the condition that the domain name of the router R1 is DN1 and the intra-domain hash function of the domain is H2, the router R1 periodically executes the following operations to issue the own domain name:

step 301: starting;

step 307: and (6) ending.

Fig. 4 is a schematic diagram of a local communication process according to the present invention. An access node, a switch and a router respectively store an aggregation table, wherein an aggregation table item comprises a source address, a destination address and an interface ID; under the conditions that the common node name of the common node N1 is NN1 and is located in a domain D1, the router in the domain D1 is R1, the domain name of the router R1 is DN1, the common node N1 is connected with an access node AP1 link, the subnet name of the access node AP1 is SN1, the common node name of the common node N2 is NN2 and is located in a domain D1 and is connected with the access node AP1 link, the inter-domain hash function is H1, and the intra-domain hash function of the domain D1 is H2, the common node N1 realizes communication with the common node N2 through the following processes:

step 401: starting;

step 413: and (6) ending.

Fig. 5 is a schematic diagram of a data acquisition process according to the present invention. The name of a common node of the common node N1 is NN1, the common node is located in a domain D1, a router in the domain D1 is R1, the domain name of the router R1 is DN1, the common node N1 is connected with a link of an access node AP1, and the name of a subnet of the access node AP1 is SN 1; the common node name of the common node N3 is NN3, and is located in the domain D1 and is connected to the access node AP3 via a link, the subnet name of the access node AP3 is SN3, the inter-domain hash function is H1, and the intra-domain hash function of the domain D1 is H2, the common node N1 implements communication with the common node N3 through the following processes:

step 501: starting;

step 518: and (6) ending.

Fig. 6 is a schematic diagram of a remote data acquisition process according to the present invention. Under the condition that the common node name of the common node N1 is NN1, the common node N1 is located in a domain D1, the router in the domain D1 is R1, the domain name of the router R1 is DN1, the common node N1 is connected with an access node AP1 link, the subnet name of the access node AP1 is SN1, the common node name of the common node N4 is NN4, the common node N6356 is located in a domain D2, the router in the domain D2 is R2, the domain name of the router R2 is DN2, the common node N4 is connected with an access node AP4 link, the subnet name of the access node AP4 is SN4, the inter-domain hash function is H1, the intra-domain hash function of the domain D1 is H2, and the intra-domain hash function of the domain D2 is H3, the common node N1 realizes communication with the common node N4 through the following processes:

step 601: starting;

step 629: and (6) ending.

Example 1

Based on the simulation parameters in table 1, this embodiment simulates a network communication implementation method in the present invention, and the performance analysis is as follows: when the distance between the source node and the destination node is long, the data communication cost is high, and when the distance between the source node and the destination node is small, the data communication cost is low, and the average data communication cost is 5.8.

TABLE 1 simulation parameters

The present invention provides a method for implementing network communication, 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 modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations 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. A network communication realizing method is characterized in that the network comprises a common node and a forwarding device, wherein the forwarding device comprises a router, a switch and an access node; the network is divided into more than two domains, and each domain comprises a route, more than two switches, more than two access nodes and more than two common nodes;

HSN1 ═ H1(SN1) formula (1)

HSN2 ═ H2(SN1) formula (2)

HDN2 ═ H2(DN1) formula (3)

Step 101: starting;

step 107: and (6) ending.

2. The method of claim 1, wherein the router maintains a domain table, and a domain table entry contains domain name, distance, interface ID and life cycle domain; the router R1 is located in the domain D1, the domain name is DN1, after the router R1 obtains the inter-domain hash function H1, the inter-domain hash value HDN1 of the domain name DN1 is calculated by using the hash function H1, as shown in formula (4), and then the following processes are performed to establish a domain table:

HDN1 ═ H1(DN1) formula (4)

Step 201: starting;

step 209: and (6) ending.

3. The method as claimed in claim 1, wherein under the condition that the domain name of the router R1 is DN1, and the intra-domain hash function of the domain is H2, the router R1 issues its own domain name by periodically performing the following operations:

step 301: starting;

step 307: and (6) ending.

4. The method of claim 1, wherein an access node, switch and router each maintain an aggregation table, an aggregation table entry comprising a source address, a destination address and an interface ID; under the conditions that the common node name of the common node N1 is NN1 and is located in a domain D1, the router in the domain D1 is R1, the domain name of the router R1 is DN1, the common node N1 is connected with an access node AP1 link, the subnet name of the access node AP1 is SN1, the common node name of the common node N2 is NN2 and is located in a domain D1 and is connected with the access node AP1 link, the inter-domain hash function is H1, and the intra-domain hash function of the domain D1 is H2, the common node N1 realizes communication with the common node N2 through the following processes:

step 401: starting;

step 409: the ordinary node receiving the request message sends a response message, the source address of the response message is the destination address of the request message, the destination address of the response message is equal to the source address of the request message, the load is the inter-domain address in the load of the request message and the response data, and the access node AP1 receives the response message;

step 410: the access node AP1 looks at the aggregation table; the access node AP1 selects all aggregation entries with destination addresses equal to the source address of the response message or the inter-domain addresses in the load, and for each selected aggregation entry, the access node AP1 performs the following operations: the access node AP1 updates the destination address of the response message to the source address field value of the aggregation table entry, sends the response message from the interface identified by the interface ID field value of the aggregation table entry, and deletes the aggregation table entry;

step 413: and (6) ending.

5. The method as claimed in claim 1, wherein the general node name of the general node N1 is NN1, and is located in the domain D1, the router in the domain D1 is R1, the domain name of the router R1 is DN1, the general node N1 is connected to the access node AP1 via a link, and the subnet name of the access node AP1 is SN 1; the common node name of the common node N3 is NN3, and is located in the domain D1 and is connected to the access node AP3 via a link, the subnet name of the access node AP3 is SN3, the inter-domain hash function is H1, and the intra-domain hash function of the domain D1 is H2, the common node N1 implements communication with the common node N3 through the following processes:

step 501: starting;

step 502: the ordinary node N1 creates an own intra-domain address, wherein the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN1 calculated by the hash function H2, and the ordinary node name is a hash value of an ordinary node name NN1 calculated by the hash function H2; the common node N1 creates an intra-domain address for the common node N3, the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN3 calculated by the hash function H2, and the common node name is a hash value of a common node name NN3 calculated by the hash function H2; the common node N1 creates an inter-domain address for the common node N3, the domain name of the inter-domain address is a hash value of a domain name DN1 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN3 calculated by the hash function H1, and the common node name is a hash value of a common node name NN3 calculated by the hash function H1; the ordinary node N1 sends a request message, the source address of the request message is the own intra-domain address, the destination address is the intra-domain address of the ordinary node N3, and the load is the inter-domain address of the ordinary node N3;

step 512: after receiving the request message, the common node creates an intra-domain address and an inter-domain address of the common node; the domain name of the intra-domain address is a hash value of a domain name DN1 calculated by a hash function H2, the subnet name is a hash value of a subnet name SN3 calculated by a hash function H2, and the common node name is a hash value of the common node name of the node itself calculated by a hash function H2; the domain name of the inter-domain address is a hash value of a domain name DN1 calculated by a hash function H1, the subnet name is a hash value of a subnet name SN3 calculated by a hash function H1, and the common node name is a hash value of a common node name of the inter-domain address calculated by a hash function H1; if the intra-domain address or inter-domain address of the normal node is equal to the destination address of the request message, go to step 513, otherwise go to step 514;

step 513: the ordinary node receiving the request message sends a response message, the source address of the response message is equal to the destination address of the request message, the destination address of the response message is equal to the source address of the request message, the load is the inter-domain address in the load of the request message and response data, and the ordinary node or the forwarding equipment receives the response message;

step 515: the forwarding device checks the aggregation table; the forwarding device selects all aggregation table entries with destination addresses equal to the response message source address or the inter-domain addresses in the load, and for each selected aggregation table entry, the forwarding device executes the following operations: the forwarding device updates the destination address of the response message to the source address field value of the aggregation table entry, sends the response message from the interface identified by the interface ID field value of the aggregation table entry, deletes the aggregation table entry, and performs step 514;

step 518: and (6) ending.

6. The method according to claim 1, wherein the general node N1 has a general node name NN1 and is located in a domain D1, the router in the domain D1 is R1, the domain name of the router R1 is DN1, the general node N1 is connected to the access node AP1 link, the subnet name of the access node AP1 is SN1, the general node name of the general node N4 is NN4 and is located in a domain D2, the router in the domain D2 is R2, the domain name of the router R2 is DN2, the general node N4 is connected to the access node AP4 link, the subnet name of the access node AP4 is SN4, the inter-domain hash function is H1, the intra-domain hash function of the domain D1 is H2, and the intra-domain hash function of the domain D2 is H3, the general node N1 and the general node N4 realize the communication through the following procedures:

step 601: starting;

step 610: if router R1 receives the request message, go to step 612, otherwise go to step 611;

step 612: after receiving the request message from the upstream interface, the router R1 selects a forwarding table, where the inter-domain subnet name of the forwarding table is equal to the subnet name of the destination address of the request message, and constructs an intra-domain address, where the domain name of the intra-domain address is the hash value of domain name DN1 calculated by using hash function H2, the subnet name is the intra-domain subnet name of the forwarding table entry, and the common node name is the hash value of common node name NN4 in the request message load calculated by using hash function H2; the router R1 deletes the ordinary node name NN4 from the request message load, adds the constructed address to the request message load, and forwards the request message from the interface identified by the interface ID of the forwarding table entry;

step 620: the ordinary node receiving the request message sends a response message, the source address of the response message is equal to the destination address of the request message, the destination address of the response message is equal to the source address of the request message, the load is the address in the load of the request message and the response data, and the forwarding device receives the response message;

step 621: the forwarding device checks the aggregation table; the forwarding device selects all aggregation table entries with destination addresses equal to the response message source address or the intra-domain address in the load, and for each selected aggregation table entry, the forwarding device executes the following operations: the forwarding device updates the destination address of the response message to the source address field value of the aggregation table entry, sends the response message from the interface identified by the interface ID field value of the aggregation table entry, and deletes the aggregation table entry;

step 623: if router R2 receives the response message, go to step 625, otherwise go to step 624;

step 629: and (6) ending.