WO2009115020A1

WO2009115020A1 - Network route establishing and data transmitting method and network node

Info

Publication number: WO2009115020A1
Application number: PCT/CN2009/070770
Authority: WO
Inventors: 周元; 张炜; 冯丹凤
Original assignee: 华为技术有限公司
Priority date: 2008-03-21
Filing date: 2009-03-13
Publication date: 2009-09-24
Also published as: EP2254285A4; US8498292B2; EP2254285A1; CN101540714B; US20110013509A1; CN101540714A; EP2254285B1

Abstract

Mesh network technology, especially a route establishing and data transmitting method and network node are provided in the embodiments of the present invention. A network route establishing method includes a gateway notice transmitted by a node on the main route is received, and route request timer is established. A route request is sent after the route request timer is overtime. The request includes the information whether the route is a main route. A route response message sent by the gateway is received via the main route, and the route response message is created by the gateway after the gateway receives the route request. A network node is also provided for carrying out this method.

Description

Method for establishing network path and data transmission and network node The application is submitted to the China Intellectual Property Office on March 21, 2008, and the application number is 200810066199. 2 , and the invention name is "method of network path establishment and data transmission and network node" The priority of the Chinese patent application is incorporated herein by reference in its entirety.

Technical field

The present invention relates to mesh (Mesh) network technology, and more particularly to network path establishment and data transmission methods and network nodes.

Background technique

A mesh network is a wireless network that supports multi-hop transmission. Mesh technology can be applied to the interconnection between infrastructure, the interconnection between home devices, and the interconnection between user equipment and infrastructure. For infrastructure interconnection, Mesh networking provides better fault tolerance than cellular coverage. H (Ph Hybrid Wi re les s Mesh Protocol) is a routing protocol in the mesh network. The routing protocol combines both the proactive and reactive routing protocols, making the protocol applicable to both the network topology and the relatively static wireless mesh network, and the network topology dynamic change network can also adapt well.

The process of creating a path by the H medical P is as follows: The H medical P routing protocol passes the gateway node, which is also called the root node, and the broadcast gateway advertises the message, and the advertised message carries the address and serial number of the gateway, and the metr ic (metric value); The non-gateway node receives the gateway advertisement message, selects the latest sequence number corresponding to the gateway, and the metr ic optimal, and creates path information to the gateway. The non-gateway node unicasts a routing request to the gateway, carries the address and sequence number of the node to establish a downlink path, and forwards the gateway advertisement message; the non-gateway node receives the route request message, and creates a route request source node. The path information, and continues to unicast the routing request message to the gateway node carried in the routing request message; the gateway node receives the routing request message, creates the path information to the routing request source node, and replies to the routing response message; The node receives the route reply message, verifies the path information created when the gateway advertisement message is received, and continues the unicast forwarding route reply message; the destination node receives the route reply message and verifies the path information. In a Me sh network with multiple gateways, all non-gateway Me sh nodes can have paths to each gateway. If multiple gateways or these multi-paths do not capture equalization policies, the nodes in the network will be unevenly loaded. Some nodes (including gateway nodes) may be congested, while some nodes are underutilized.

Summary of the invention

An embodiment of the present invention provides a path establishment method, which improves a load balancing ratio of a node in a network, where the method includes:

Receiving a gateway advertisement forwarded by a node having a trunk path, establishing a route request timer; sending the route request after the route request timer expires, the request carrying the information of the trunk path; receiving the route response message sent by the gateway through the trunk path The routing response message is generated by the gateway after receiving the routing request.

The embodiment of the invention further provides a network node, where the network node includes:

a first receiving unit, configured to receive a gateway advertisement forwarded by a node having a trunk path, and a sending unit, configured to send a routing request after the first receiving unit receives the gateway advertisement and the routing request timer expires;

And a second receiving unit, configured to receive, by using a trunk path, a route reply message sent by the gateway, where the route reply message is generated by the gateway after receiving the route request.

The embodiment of the invention further provides a method for data transmission, the method comprising:

When the sent data is to receive data sent by other nodes to the external network, the verified trunk path is selected, and the data is sent through the trunk path; when the sent data is locally sent to the external network, an authenticated path is selected for forwarding.

The embodiment of the invention further provides a method for link fault processing, the method is:

Determine whether it is the path to the gateway;

If it is the path to the gateway, further determine whether it is a trunk path;

If it is a trunk path, trigger the trunk path selection and reselect the trunk path.

The above method and the network node are used. When the source node of the network sends a data packet to the external network, the source node uses a common traffic policy in the industry, so that multiple paths are used in a balanced manner at the source node. When the node forwards data sent by other nodes to the external network, it sends along the trunk path, and load balancing is considered because the trunk is selected. For the data sent by the gateway, the reverse path corresponding to the uplink path is used for forwarding. Compared with H doctor P, the load is more balanced in the network, which increases the network throughput.

DRAWINGS

Figure 1 is a typical schematic diagram of a multi-gateway mesh network;

2 is a flowchart of processing a gateway advertisement according to an embodiment of the present invention;

3 is a flowchart of processing a routing request message according to an embodiment of the present invention;

4 is a flowchart of processing a routing response message according to an embodiment of the present invention;

Figure 5 is a flow chart of step S 310 - embodiment of the embodiment of the present invention;

6 is a flowchart of a second embodiment of a gateway advertisement processing procedure according to an embodiment of the present invention;

7 is a flow chart of link break processing in an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a node device according to an embodiment of the present invention.

detailed description

The embodiment of the invention designs a balanced routing mechanism for the mesh network. Figure 1 shows a typical schematic diagram of a mesh network in a multi-gateway scenario. Among them, Gl, G2, and G3 are gateway nodes, and other nodes are non-gateway nodes. For a non-gateway node, select a path as the trunk path in the path from the node to the gateway, and record the trunk path information in the route list.

The timing of the selection of the trunk path can be: The non-gateway node starts the trunk selection timer when it receives the first gateway advertisement. After the timer expires, the trunk selection is triggered and the trunk path is selected. Another implementation is that after the non-gateway node is started, a trunk selection timer is started. After the timer expires, the trunk selection is triggered, and the trunk path is selected.

The trunk path is selected by randomly selecting a path according to the gateway address or the next hop address and the local node device address in the path as the trunk path. Another implementation is to randomly select a path as the trunk path according to the gateway address or the next hop address and the local device address in the path list with the smallest layer number: use the local address and the path with the smallest layer number. The one-hop address is XORed separately, and the largest one is marked as the main path.

The layer number can be generated according to the minimum hop count to the gateway. In addition, the layer number can be based on air time Generated; can also be generated according to other additive path Metrics (the path Metr ic is equal to the weighted sum of the individual links Metr ic). If the layer number is generated according to the air interface time, an embodiment of the current layer number calculation is provided: the layer number in the received message is added to the current link, and the current layer number is obtained by rounding up the above result ( The empirical value of the air interface time between two neighboring nodes given by 802. lis is 10 ms).

A method for establishing a network path according to an embodiment of the present invention includes:

5001. Receive a gateway advertisement forwarded by a node having a trunk path, and establish a route request timer.

5002. After the route request timer expires, a route request is sent, where the route request carries information about a trunk path.

5003: Receive a route reply message sent by the gateway by using a trunk path, where the route reply message is generated by the gateway after receiving the route request.

Before step S001, a path should be selected as the trunk path in the path connected to the current node, and the trunk path information is recorded in the route list. The step of selecting the trunk path in the path connected to the current node includes starting the trunk selection timer when the first gateway advertisement is received, triggering the trunk selection after the timer expires, and selecting the trunk path; or, the current node is started. After that, a trunk selection timer is started, and after the timer expires, the trunk selection is triggered, and the trunk path is selected.

Referring to FIG. 1, a process of creating a path according to an embodiment of the present invention is specifically described.

The gateway node periodically broadcasts the gateway advertisement message, and after the gateway node starts, starts a periodic gateway advertisement timer, and after the timer expires, the broadcast gateway advertises;

The non-gateway node receives and processes the gateway advertisement forwarded by the node having the trunk path, and triggers establishment of a route request timer;

After the route request timer expires, the current non-gateway node sends a route request message to the gateway node through the trunk path, where the route request carries information about whether the path is a trunk path;

After receiving the route request message from the non-gateway node, the gateway node generates a route response message, and the gateway node sends the route response message to the non-gateway node;

The path establishment is completed when the non-gateway node receives the route reply message corresponding to the local node through the trunk path.

The frame structure of the gateway advertisement is shown in the following table: Source

Source Layer

ID Length Flags TTL Sequence Metric

Address Number

Number

The ID is the sequence number of the gateway advertisement data frame, the length is the frame length, the Flags is the flag bit, the TTL is the life cycle, the Source Address is the source address, the Source Sequence Number is the serial number of the source node that sends the route request message, and the metric is the metric value. , Layer Number is the layer number.

The frame structure of the route request message is as follows:

The ID is the sequence number of the routing request message data frame, and the length is the frame length. One bit of the Flags indicates whether the routing request is a trunk request. In this embodiment, the bit 3 is used as an example, and the bit 3=1 is a trunk request. A bit indicates whether to request the path to any gateway (in this embodiment, bit 7 is taken as an example, bit 7 = l indicates the path to the arbitrary gateway), the PREQ ID is the sequence number of the routing request message, and the Source Address is the sending route. The source node MAC (Media Access Control) address of the request message. The Source Sequence Number is the sequence number of the source node that sends the route request message. The initial value of the metric is 0. It can be seen that there is an identifier in the routing request, indicating whether the routing request is a trunk request.

The frame structure of the route reply message is as follows:

Dest

Dest Source

ID Length Flags TTL Sequence Metric

Addr Addres s

Number The ID is the sequence number of the routing response message data frame, and the length is the frame length. The meaning of Flags is the same as the meaning of the Flags of the route request element, that is, bit3 indicates whether it is a trunk request, and bit7 indicates whether to request a path to any gateway. Dest Addr indicates the destination address of the route reply message, that is, the source address of the route request message. The Dest Sequence Number is the sequence number of the destination node. The initial value of the metric is 0. The Source Address is the source node MAC address of the route reply message.

The non-gateway node receives and processes the gateway advertisement through the trunk path, and the process of triggering the establishment of the route request timer is shown in FIG. 2, and the process flow of the gateway advertisement is shown. The specific process is:

5201, receiving a gateway advertisement;

S202: Determine whether the sequence number in the gateway advertisement is smaller than the sequence number corresponding to the source address of the locally stored gateway, and if yes, execute S203 to set the forced update; otherwise, discard;

5203. Update the TTL, metric value, and layer number in the gateway advertisement, and decrease the TTL by 1. The metric is added to the metric of the previous f-mega link, and the layer number is increased by 1;

5204. Determine whether the gateway advertisement layer number is greater than a local storage layer number. If yes, execute S205 to set a forced update; otherwise, discard;

S205. Query a route to the gateway according to the sending address in the gateway advertisement. The routing entry is a route to the gateway, and is marked as unverified. After the completion, S210 is executed, if the local section

S207, determining whether the gateways in the frame and the entries in the frame are the same, if the gateway information in the frame is different from the gateway information in the local routing table, executing S208a, if the gateway information in the frame is the same as the gateway information in the local routing table, executing S208b;

S208a, comparing the metric value in the frame with the metric value of the gateway that is locally sent by using the sending address, if the mean value in the frame is greater than the mean value of the local to the gateway, the gateway advertisement is discarded, if in the frame The metric value is smaller than the metric value locally to the gateway, and S ² 09 is performed;

S208b, updating the routing table of the local node, the routing flag is marked as the routing entry is a route to the gateway, updating the serial number, the metric value, and the access time in the entry, and executing the S209 after the update is completed;

S209, updating the gateway address, the gateway sequence number, and the metric value in the routing table, and marking the flag bit as The routing entry is routing information to the gateway;

5210, determining whether the routing entry of the routing information is information of a trunk path, if yes, executing S211, if otherwise executing S212;

5211. Continue to forward the gateway advertisement according to the routing information.

S212. If the routing request timer of the destination address is not started, start a routing request timer of the sending destination address.

Through the above processing, the current node receives the gateway advertisement from the trunk path, and after the route request timer expires, sends a route request, where the route request carries the information of whether the path is a trunk path, and then sends the information to the source gateway advertised by the gateway. Routing request, when the node receives the routing request, the processing flow is as shown in Figure 3:

S301. Compare the sequence number carried in the received routing request with the sequence number corresponding to the routing request source address in the local cache. If the sequence number carried by the received routing request is smaller than the serial number of the local cache, discard If the sequence number carried in the received routing request is larger than the local cache serial number, the process proceeds to S302, and the forced update is set.

S302. Update a serial number and a PreqID corresponding to the locally cached routing request source node.

S303, comparing the size of the PreqID carried in the received routing request with the source address of the routing request source in the local cache; if the received routing request carries a PreqID smaller than the local cached PreqID, discarding the received If the PreqID carried in the received routing request is larger than the local cache PreqID, execute S304 to set the forced update.

S304. Update a PreqID corresponding to the locally cached routing request source node.

5305, update the TTL, metric value in the local routing request frame, TTL minus 1, metric plus link metric;

5306. Search, in the routing information of the local node, a routing entry corresponding to the source address of the received routing request.

S307, if the routing entry exists, executing S308a, if the routing entry does not exist, executing S308b;

S308a, if the forced update has been set, update the routing entry, including the serial number, next hop, Metric, access time; otherwise, compare the metric of the metric and routing entry in the routing request. If the metric in the routing request is small, update the routing entry as above; otherwise, discard the routing request;

S308b, adding the routing entry, and marking the routing entry as verified;

5309, determining whether the current node is a gateway node, if yes, executing S310, if the current node is a non-gateway node, executing S311;

5310. Send a route request response message to the source address of the routing request.

5311, determining whether the current device has a trunk path route to the gateway node, if otherwise, the routing request information is discarded, if yes, executing S311

5312. Forward the routing request information along a trunk path.

After receiving the routing request, the gateway generates a routing response message, and sends the routing response message to the non-gateway node that sends the routing request along the trunk path. When the non-gateway node receives the routing response message sent by the gateway, the non-gateway node processes. The process is shown in Figure 4:

5401. Query a routing table according to the sending address carried in the received routing response message, where the routing information is stored in the routing table.

S402: If the corresponding routing entry is found, perform S403, and if there is no corresponding routing entry, discard the received routing response message.

5403. Compare the generation time of the sequence number in the received route response information with the sequence number route entry corresponding to the destination address in the locally cached route response, and discard if the sequence number in the route response is not less than the locally stored sequence number. Otherwise, execute S404;

5404. Update the TTL and metric values in the route response information, and decrease the TTL by 1. The metric increases the metric corresponding to the receiving link.

5405. Update the serial number and the metric value in the routing table, and mark the routing entry as verified;

S406: Determine whether the destination address in the received route reply message is the current node, if not, execute S407 to forward the route response message, and if yes, indicate that the path between the current node and the gateway node is established.

When the mesh source node in the network sends data packets to the external network, the source node uses the common traffic policy in the industry, so that multiple paths are used in a balanced manner at the source node. The node is forwarding the other nodes. When data is sent, it is sent along the trunk path, and load balancing is considered because the trunk is selected. Compared with H doctor P, the load is more balanced in the network, which increases the network throughput.

In the above embodiment, S310, in the specific implementation, further provides an embodiment. If 5 is shown, S311 is specifically:

53011. The source node in the routing request message sent by the unicast routing response message carries the identifier of the gateway, the serial number, and the metric value of the current node to the gateway.

53012. The unicast sends a route reply message to the gateway node corresponding to the trunk path, the source address carrying the route request message, the source sequence number, and the metric value of the source node in the current node to the route request message.

The present invention provides a gateway advertisement frame format of the second embodiment, as shown in the following table:

A Las Thop address is added to the above-mentioned gateway advertisement frame.

The processing flow of the gateway advertisement in this embodiment is as shown in FIG. 6:

5610, receiving a gateway notice;

5611, find if there is 1^8 (^ information; if there is, execute 8612, if not, execute 8613;

5612, determining whether the current node information is included in the Lasthop list, if yes, the gateway advertisement is discarded, if not, executing S613;

5613. Query the route to the gateway according to the source address in the gateway advertisement, and then execute S205.

In this embodiment, after the routing entry of the trunk path is selected, the lasthop list, metric, and TTL in the gateway advertisement are updated, and then the gateway advertisement is forwarded.

The embodiment of the invention further provides a link fault processing procedure. Referring to Figure 7, a flow chart of link break processing in accordance with an embodiment of the present invention.

S701. When detecting a link break, the current node queries the routing table according to the peer address.

S702a, determining whether it is a path to the gateway, if not a path to the gateway, executing S702b Deleting the routing entry of the faulty link from the routing table, if it is the path to the gateway, executing S703;

S703, determining whether the link is a trunk path, if not a trunk path, deleting a routing entry of the faulty link from the routing table, and if it is a trunk path, executing S704;

5704, triggering trunk path selection;

5705, determining whether to select the trunk path, if there is no trunk path, executing S708, if there is a trunk path, executing S706;

5706, triggering a routing request;

5707. The proxy trunk gateway sends a gateway advertisement.

5708, constructing PERR (route error message), which includes the gateway corresponding to the trunk path and the corresponding serial number, and then executing S709,

S 709, sending the PERR to all direct peers outside the current node.

The embodiment of the invention further provides a method for link fault processing, including:

Determine whether it is the path to the gateway;

If it is the path to the gateway, further determine whether it is a trunk path;

Select a path as the trunk path among the paths connected to the current node, and record the trunk path information in the route list.

PERR is constructed if no trunk path is selected, the PERR containing information corresponding to the trunk path; and the PERR is sent to all directly opposite parties outside the current node. If a trunk path is selected, a routing request is triggered and the proxy trunk gateway sends a gateway advertisement.

A person skilled in the art can understand that all or part of the steps of implementing the foregoing embodiments may be completed by a program instructing related hardware, and the program may be stored in a computer readable storage medium, and the program is executed. The method includes the following steps: receiving a gateway advertisement forwarded by a node having a trunk path, establishing a route request timer; sending a route request after the route request timer expires, where the request carries information of a trunk path; Routing reply message. The storage medium is, for example, R0M/RAM, a magnetic disk, an optical disk, or the like. Embodiments of the present invention also provide a method for data transmission. The data packet contains the receiving address, the sending address, the Mesh source address, the Mesh destination address, and the destination address.

When the data is sent to the external network when the data is sent from the non-gateway node to the gateway node, it is determined whether the data to be sent is locally generated data. If the current node receives the data of the other node and forwards the data to the gateway node, the verified trunk path is selected. Forward. When the current node sends local data to the gateway, if there are multiple authenticated paths to the gateway, a traffic forwarding policy is used for forwarding. The forwarding policy may be: Each verified path forwards the same number of data flows, and each data flow is identified by a source IP address and a destination IP address.

When data is transmitted inwardly from the gateway to the intranet node, the current node uses the reverse path to send data from the non-gateway node to the gateway node. If the reverse path does not exist, the traffic policy is selected to select a forwarding path to forward the data. The above policy requires the egress gateway to maintain path information through all gateways to the Mes h node.

Data sent from the external network, the data is sent to the egress gateway of the node. The gateway sends the data to the external gateway corresponding to the corresponding path according to the path information. After the external gateway receives the data, if there is a single path, the path is sent to the node; otherwise, the traffic policy is used to send to the node.

Embodiments of the present invention also provide a network node device that implements the foregoing method. As shown in FIG. 8, a network node device 80 is provided, and the device includes:

a first receiving unit 801, configured to receive a gateway advertisement forwarded by a node having a trunk path, and a sending unit 802, configured to send a routing request after the first receiving unit receives the gateway advertisement and the routing request timer expires;

The second receiving unit 803 is configured to receive, by using a trunk path, a route response message sent by the gateway, where the route response message is generated by the gateway after receiving the routing request;

a path selection unit 804, configured to select a path as a trunk path among the paths connected to the current node;

The determining unit 805 is configured to determine whether a routing information corresponds to the trunk path information, and the information adding unit 806 is configured to add information about the trunk path to the routing request. The query unit 807 is configured to use routing information in the routing table, including routing information to the gateway that sends the gateway advertisement, and routing information that sends the routing request.

The process of selecting a path by the path selection unit is: randomly selecting a path according to a gateway address or a next hop address and a local node device address in the path as a trunk path. Another implementation is to randomly select a path as the trunk path according to the gateway address or the next hop address and the local device address in the path list with the smallest layer number: use the local address and the path with the smallest path number The one-hop address is XORed separately, and the largest one is marked as the main path.

Using the above method and the network node, when the mes h source node in the network sends a data packet to the outer network, the source node uses an industry-wide traffic policy, so that multiple paths are used in a balanced manner at the source node. When the node forwards the data sent by other nodes to the external network, it sends along the trunk path, and the load balancing is considered because the trunk is selected. For the data sent by the gateway, the reverse path corresponding to the uplink path is used for forwarding. Compared with H doctor P, the load is more balanced in the network, which increases the network throughput.

Claims

Claim

A method for establishing a network path, the method comprising:

Receiving a gateway advertisement forwarded by a node having a trunk path, establishing a route request timer; sending a route request after the route request timer expires, the route request carrying information of the trunk path;

Receiving, by the trunk path, a route reply message sent by the gateway, where the route reply message is generated by the gateway after receiving the route request.

2. The method according to claim 1, wherein the method further comprises:

The method of claim 2, wherein the step of selecting a path as a trunk path in the path connected to the current node comprises:

When the first gateway advertisement is received, the trunk selection timer is started. After the timer expires, the trunk selection is triggered, and the trunk path is selected.

Or,

After the current node is started, a trunk selection timer is started. After the timer expires, the trunk selection is triggered to select the trunk path.

The method of claim 2, wherein the information that carries the path to the trunk path in the routing request is:

An identifier is added to the routing request, and the routing request is used to record the routing request as a trunk request.

The method according to claim 2, wherein selecting a path as a trunk path in the path connected to the current node is: randomly selecting according to a gateway address or a next hop address and a local node device address in the path. A path is used as the trunk path.

The method according to claim 2, wherein selecting a path as a trunk path in the path connected to the current node is: using a local address and a next hop address of each path with the smallest layer number respectively Or operation, the largest result is marked as the main path.

The method according to claim 2, wherein the receiving a node having a trunk path

13 replacement page (^)^ ) The forwarded gateway advertisement is:

Querying routing information of the gateway that sends the gateway advertisement;

Determining whether the routing information is information of a trunk path, and if yes, forwarding a gateway advertisement according to the routing information, and starting a routing request timer corresponding to the gateway address.

8. A network node, wherein the node comprises:

a first receiving unit, configured to receive a gateway advertisement forwarded by a node having a trunk path, and establish a route request timer;

a sending unit, configured to send a routing request after the first receiving unit receives the gateway advertisement and the routing request timer expires;

And a second receiving unit, configured to receive, by using a trunk path, a route response message sent by the gateway, where the route response message is generated by the gateway after receiving the route request.

The node according to claim 8, wherein the node further comprises:

a path selection unit, configured to select a path as a trunk path among the paths connected to the current node.

The node of claim 8, wherein the node further comprises:

And an information adding unit, configured to add information of the trunk path to the routing request.

11. The node of claim 9, wherein the node further comprises:

The determining unit is configured to determine whether a routing information corresponds to the trunk path information.

The query unit is used for routing information in the routing table, including routing information to the gateway that sends the gateway advertisement and routing information for sending the routing request.

12. A method of data transmission, wherein the method is:

When the sent data is to receive data sent by other nodes to the external network, the verified trunk path is selected, and the data is sent through the trunk path; when the sent data is sent locally to the external network, an authenticated path is selected for forwarding.

The method according to claim 12, wherein the method further comprises: transmitting, by the gateway, data sent to the network by using a reverse path corresponding to the path of the service flow to the external network;

If the reverse path does not currently exist, then a traffic policy is used to select a verified path.

14

Replacement page (3⁄4 :>^) Forward.

The method according to claim 12 or 13, wherein the selecting a verified path for forwarding uses a forwarding policy to select an authenticated path for forwarding, and the forwarding policy is:

Each path forwards the same number of data streams, each of which uses the source IP address and the destination IP address identifier.

A method for processing link faults, the method comprising:

Determine whether it is the path to the gateway;

If it is the path to the gateway, further determine whether it is a trunk path;

The method according to claim 15, wherein the method further comprises: selecting a path as a trunk path among the paths connected to the current node, and recording the trunk path information in the route list.

The method according to claim 16, wherein the method further comprises: constructing a PERR if the trunk path is not selected, where the PERR includes a correspondence corresponding to the trunk path to all directly opposite to the current node. Send the PERR.

The method according to claim 16, wherein the method further comprises: if a trunk path is selected, triggering a routing request, and the proxy trunk gateway sends a gateway advertisement.

15

Correction page (Article 91)