OLSR routing protocol message compression method and system

Abstract

The present invention provides an OLSR routing protocol message compression method and system, including: using a network-wide unique node ID to replace the node IP address in the OLSR control signaling, compressing the length of the air interface message, reducing the air interface message overhead, improving the wireless self-organizing network transmission rate and network robustness, and avoiding network congestion caused by excessive messages. The present invention reduces air interface resource overhead and improves system capacity; realizes rapid response to network changes and improves network robustness; and at the same time reduces control signaling overhead and improves user experience.

Description

Technical Field

[0001] The present invention relates to the technical field of wireless ad hoc networks, and in particular to an OLSR routing protocol message compression method and system. Background Art

[0002] A wireless ad hoc network is a centerless, self-organizing wireless network where each node is independent and discovers each other. Compared with a wired ad hoc network, a wireless ad hoc network mainly has the following differences:

[0003] Air interface resources are tight. Unlike traditional wired ad hoc networks, wireless ad hoc networks are not connected by cables, and communication between nodes needs to rely on wireless channels. Due to the particularity of wireless channels, the communication bandwidth is limited, and considering factors such as wireless channel competition, signal attenuation, and interference, the air interface resources will be further tightened.

[0004] Nodes move frequently. Unlike traditional wired ad hoc networks, wireless ad hoc networks are not fixed in one location but can move freely. The movement of nodes will cause changes in the network topology. After the network topology changes, the routing protocol needs to perform a routing update process. Routing updates inevitably introduce air interface messages, further exacerbating the competition for air interface resources.

[0005] From the above analysis, we can imagine that the bottleneck for improving network robustness and transmission efficiency is on the air interface side. If the air interface can transmit control messages and data to the destination node in a timely manner, the network will operate in an orderly and efficient manner. The rapid response to changes in the wireless self-organizing network topology and system overhead are a contradiction. The rapid response of the network topology is conducive to improving system performance, but it will increase system overhead and thus reduce system capacity.

[0006] Considering the node mobility of wireless ad hoc networks, in order to update network routes in a timely manner, the OLSR routing protocol (Optimized Link State Routing, OLSR) can be used in wireless ad hoc networks. The OLSR routing protocol uses the multi-point relay node mechanism (Multi Point Relay, MPR) to optimize the flooding algorithm and reduce network overhead.

[0007] The OLSR routing protocol generates HELLO messages and TC messages. The encoding format of the message refers to the RFC 5444 protocol. The encoding format of each air interface packet is as follows.

[0008] <packet> :＝ <packet-header>

[0009] <message>*

[0010] "*" indicates that the message contains one or more. The message format is as follows:

[0011] <message> :＝ <message-header>

[0012] <tlv-block>

[0013] ( <addr-block> <tlv-block> )*

[0014] <message-header> :＝ <msg-type>

[0015] <msg-flags>

[0016] <msg-addr-length>

[0017] <msg-size>

[0018] <msg-orig-addr> ？

[0019] <msg-hop-limit> ？

[0020] <msg-hop-count> ？

[0021] <msg-seq-num> ？

[0022] <addr-block> :＝ <num-addr>

[0023] <addr-flags>

[0024] ( <head-length> ？)？

[0025] ( <tail-length> <tail> ？)？

[0026] <mid> *

[0027] <prefix-length>*

[0028] The "?" indicates that the field is optional and the corresponding flag needs to be set in the flags field.

[0029] in, <msg-addr-length>Indicates the byte length of the IP address in the message. According to the RFC 5444 protocol, the value of the IPv4 type address is 3, and the value of the IPv6 type address is 15, that is, <msg-addr-length>:=(actual length of IP address – 1).

[0030] in, <addr-block>The address carried by the message. The address in the message is: <mid> : <tail>For example, if a routing message needs to carry multiple IPV4 addresses: 192.167.0.1, 192.168.1.1, 192.169.2.1, 192.170.3.1, direct transmission requires 16 bytes. After compression by the RFC 5444 protocol method, :=192 (1 byte), <head-length>=1(1 byte), <tail>:=1(1 byte), <tail-length>=1(1 byte), <mid>=167.0,168.1,169.2,170.3 (8 bytes), occupying a total of 12 bytes. The OLSR protocol can effectively reduce the length of air interface messages by using the above method, but it is still not enough, especially when there are many nodes, the IP address configuration is more complicated, making the air interface message still larger.

[0031] Patent document CN111356202A (application number: 202010159814.5) discloses a low-overhead hybrid routing protocol method for narrowband ad hoc networks, including: adopting a link layer relay transmission method to reduce the IP header bandwidth consumption caused by network layer relay by simplifying the protocol stack; adopting an active and passive hybrid routing mode; adopting a low-overhead topology control method, periodically exchanging neighbor information between nodes, and using compression coding for information compression and single-hop broadcasting to establish and maintain the 2-hop topology table on which the passive routing mode depends; adopting a piggyback routing update method, in which the node piggybacks the path information of the destination node through the extended field of the Hello message, and diffuses it to the upstream node along the reverse path, which is used for the upstream node to update the routing table required in the active routing mode. Summary of the invention

[0032] In view of the defects in the prior art, the object of the present invention is to provide an OLSR routing protocol message compression method and system.

[0033] According to the present invention, an OLSR routing protocol message compression method is provided, comprising: replacing the node IP address in the OLSR control signaling with a network-wide unique identification node ID, compressing the length of the air interface message, reducing the air interface message overhead, improving the wireless self-organizing network transmission rate and the robustness of the network, and avoiding network congestion caused by excessively large messages.

[0034] Preferably, it includes:

[0035] Step S1: Get the current network size and set <message-header>of <msg-addr-length>value; when the total number of nodes in the network is less than 256, <msg-addr-length>Set to 0, when the total number of nodes in the network is greater than or equal to 256 but less than 65536, <msg-addr-length>Set to 1;

[0036] Step S2: According to the number of node identifiers carried in the HELLO message and the TC message, set <address-block> : <num-addr>value;

[0037] Step S3: According to <msg-addr-length>Set the value of <address-block>In <addr-flag>field; when <msg-addr-length>If the value is 0 or 1, <addr-flag>The mark is changed to 0;

[0038] Step S4: According to <msg-addr-length>The value of <address-block>of <mid>field; when <msg-addr-length>Set to 0, <mid>Each node identifier contained takes up 1 byte; if <msg-addr-length>Set to 1, <mid>Each node identifier contained takes up 2 bytes.

[0039] Preferably, the network-wide unique node identifier assigned to each node has a value smaller than the total number of nodes.

[0040] Preferably, the nodes have a unified mapping relationship, mapping the node ID and the node IP address one by one.

[0041] Preferably, only wireless ad hoc network internal addressing is supported.

[0042] An OLSR routing protocol message compression system provided by the present invention includes: using a network-wide unique node ID to replace the node IP address in the OLSR control signaling, compressing the length of the air interface message, reducing the air interface message overhead, improving the wireless self-organizing network transmission rate and the robustness of the network, and avoiding network congestion caused by excessively large messages.

[0043] Preferably, it includes:

[0044] Module M1: Get the current network size and set <message-header>of <msg-addr-length>value; when the total number of nodes in the network is less than 256, <msg-addr-length>Set to 0, when the total number of nodes in the network is greater than or equal to 256 but less than 65536, <msg-addr-length>Set to 1;

[0045] Module M2: Set the number of node identifiers carried in the HELLO message and the TC message <address-block> : <num-addr>value;

[0046] Module M3: Based on <msg-addr-length>Set the value of <address-block>In <addr-flag>field; when <msg-addr-length>If the value is 0 or 1, <addr-flag>The mark is changed to 0;

[0047] Module M4: Based on <msg-addr-length>The value of <address-block>of <mid>field; when <msg-addr-length>Set to 0, <mid>Each node identifier contained takes up 1 byte; if <msg-addr-length>Set to 1, <mid>Each node identifier contained takes up 2 bytes.

[0048] Preferably, the network-wide unique node identifier assigned to each node has a value smaller than the total number of nodes.

[0049] Preferably, the nodes have a unified mapping relationship, mapping the node ID and the node IP address one by one.

[0050] Preferably, only wireless ad hoc network internal addressing is supported.

[0051] Compared with the prior art, the present invention has the following beneficial effects:

[0052] 1. Reduced air interface resource overhead and improved system capacity. The rapid response to changes in wireless self-organizing network topology and system overhead are contradictory. Rapid response to network topology is conducive to improving system performance, but it will also increase system overhead, thereby reducing system capacity. The longer the air interface message, the more air interface resources it occupies. Compressing the length of the air interface message can effectively reduce the air interface resource overhead, while being able to quickly respond to changes in network topology and improve system capacity.

[0053] 2. Rapid response to network changes is achieved, and network robustness is improved; message compression reduces the length of air interface messages, and network transmission efficiency is improved. HELLO messages and TC messages that the OLSR routing protocol relies on can be transmitted to the destination node more timely, and the current wireless self-organizing network topology changes can be responded to in a timely manner, effectively improving the robustness of the network;

[0054] 3. Reduced control signaling overhead and improved user experience: OLSR's air interface messages belong to control signaling, and the network overhead occupied by control signaling is reduced, which can effectively improve data transmission efficiency and improve user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Other features, objects and advantages of the present invention will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0056] Figure 1 Schematic diagram of local topology of network nodes. DETAILED DESCRIPTION

[0057] The present invention is described in detail below in conjunction with specific embodiments. The following embodiments will help those skilled in the art to further understand the present invention, but are not intended to limit the present invention in any form. It should be noted that, for those of ordinary skill in the art, several changes and improvements can also be made without departing from the concept of the present invention. These all belong to the protection scope of the present invention.

[0058] Example 1

[0059] In a wireless self-organizing network, air interface resources are very valuable, and the movement of each node will cause frequent topology changes, and more HELLO messages and TC messages will be generated. If the air interface message is too long, it will reduce the transmission efficiency and cause network congestion. HELLO messages and TC messages contain multiple IP addresses. The OLSR protocol can reduce the length of air interface messages to a certain extent by compressing the IP addresses. The present invention is aimed at a wireless self-organizing network based on the OLSR routing protocol, and proposes an OLSR routing protocol message compression method. The node IP address in the OLSR control signaling is replaced with a network-wide unique node ID, which can compress the length of the air interface message, reduce the air interface message overhead, improve the transmission rate of the wireless self-organizing network and the robustness of the network, and avoid network congestion caused by excessive messages.

[0060] The wireless self-organizing network to which the present invention is applied follows the following principles:

[0061] 1) The number of nodes in a self-organizing network is limited. The total number of nodes in a small-scale network is less than 256, and the total number of nodes in a large-scale network is less than 65,536.

[0062] 2) Each node is assigned a unique node identifier in the entire network, namely, a node ID, and the value of the node ID is less than the total number of nodes (65536 or 256).

[0063] 3) The nodes have a unified mapping relationship, and the node ID and IP address can be mapped one by one.

[0064] 4) Only supports internal addressing within wireless ad hoc networks.

[0065] The present invention provides an OLSR routing protocol message compression method, which is actually a new <msg-header>and <address-block>Filling method, according to RFC5444, <msg-header>The format is as follows:

[0066] <msg-header> :＝ <msg-type>

[0067] <msg-flags>

[0068] <msg-addr-length>

[0069] <msg-size>

[0070] <msg-orig-addr> ？

[0071] <msg-hop-limit> ？

[0072] <msg-hop-count> ？

[0073] <msg-seq-num>?

[0074] in, <msg-type>Indicates the message type; <msg-flags>Indicates that the message carries field identifier; <msg-addr-length>Indicates the length of the address in the message; <msg-size>Indicates the message size; <msg-orig-addr>Indicates the source address of the message; <msg-hop-limit>Indicates the message hop limit; <msg-hop-count>Indicates the number of message hops; <msg-seq-num>Indicates the message sequence number.

[0075] According to RFC 5444, the air interface message <msg-addr-length>Parameter, the value of IPV4 type address is 3 (the actual length is 4), and the value of IPV6 type address is 15 (the actual length is 16). The present invention is extended as follows, namely <msg-addr-length>It can be 0 or 1 (i.e. the actual length is 1 or 2 bytes).

[0076] <address-block>The format is as follows:

[0077] <address-block> :＝ <num-addr>

[0078] <addr-flags>

[0079] ( <head-length> ？)？

[0080] ( <tail-length> <tail> ？)？

[0081] <mid> *

[0082] <prefix-length>*

[0083] in, <num-addr>Indicates the number of addresses; <addr-flags>Indicates the address block identifier; <head-length>Indicates the length of the address header and the address header; <tail-length> <tail>Indicates the address tail length and address tail; <mid>Indicates the middle of an address; <prefix-length>Indicates the proxy length.

[0084] Specifically, the steps of this method are as follows:

[0085] Step 1: Get the current network size and set <message-header>of <msg-addr-length>If the total number of nodes in the network is less than 256, <msg-addr-length>Set to 0, if the total number of nodes in the network is greater than or equal to 256 but less than 65536, <msg-addr-length>Set to 1.

[0086] Step 2: Set the number of node identifiers carried in the HELLO message and the TC message. <address-block> : <num-addr>value.

[0087] Step 3: According to <msg-addr-length>Set the value of <address-block>In <addr-flag>field. If <msg-addr-length>If the value is 0 or 1, <addr-flag>The mark is changed to "0", that is, <head-length> 、 <tail> 、 <tail-length> 、 <prefix-length>Fields are not included.

[0088] Step 4: According to <msg-addr-length>The value of <address-block>of <mid>field. If <msg-addr-length>Set to 0, <mid>Each node identifier contained in the <msg-addr-length>Set to 1, <mid>Each node identifier contained takes up 2 bytes.

[0089] The present invention provides an OLSR routing protocol message compression system, which is actually a new <msg-header>and <address-block>Filling method, according to RFC5444, <msg-header>The format is as follows:

[0090] <msg-header> :＝ <msg-type>

[0091] <msg-flags>

[0092] <msg-addr-length>

[0093] <msg-size>

[0094] <msg-orig-addr> ？

[0095] <msg-hop-limit> ？

[0096] <msg-hop-count> ？

[0097] <msg-seq-num>?

[0098] in, <msg-type>Indicates the message type; <msg-flags>Indicates that the message carries field identifier; <msg-addr-length>Indicates the length of the address in the message; <msg-size>Indicates the message size; <msg-orig-addr>Indicates the source address of the message; <msg-hop-limit>Indicates the message hop limit; <msg-hop-count>Indicates the number of message hops; <msg-seq-num>Indicates the message sequence number.

[0099] According to RFC 5444, the air interface message <msg-addr-length>Parameter, the value of IPV4 type address is 3 (the actual length is 4), and the value of IPV6 type address is 15 (the actual length is 16). The present invention is extended as follows, namely <msg-addr-length>It can be 0 or 1 (i.e. the actual length is 1 or 2 bytes).

[0100] <address-block>The format is as follows:

[0101] <address-block> :＝ <num-addr>

[0102] <addr-flags>

[0103] ( <head-length> ？)？

[0104] ( <tail-length> <tail> ？)？

[0105] <mid> *

[0106] <prefix-length>*

[0107] in, <num-addr>Indicates the number of addresses; <addr-flags>Indicates the address block identifier; <head-length>Indicates the length of the address header and the address header; <tail-length> <tail>Indicates the address tail length and address tail; <mid>Indicates the middle of an address; <prefix-length>Indicates the proxy length.

[0108] Specifically, they include:

[0109] Module 1: Get the current network size and set <message-header>of <msg-addr-length>If the total number of nodes in the network is less than 256, <msg-addr-length>Set to 0, if the total number of nodes in the network is greater than or equal to 256 but less than 65536, <msg-addr-length>Set to 1.

[0110] Module 2: Set the number of node identifiers carried in the HELLO message and the TC message <address-block> : <num-addr>value.

[0111] Module 3: Based on <msg-addr-length>Set the value of <address-block>In <addr-flag>field. If <msg-addr-length>If the value is 0 or 1, <addr-flag>The mark is changed to "0", that is, <head-length> 、 <tail> 、 <tail-length> 、 <prefix-length>Fields are not included.

[0112] Module 4: Based on <msg-addr-length>The value of <address-block>of <mid>field. If <msg-addr-length>Set to 0, <mid>Each node identifier contained in the <msg-addr-length>Set to 1, <mid>Each node identifier contained takes up 2 bytes.

[0113] Among them, the number of nodes in the self-organizing network is limited, the total number of nodes in the small-scale network is less than 256, and the total number of nodes in the large-scale network is less than 65,536;

[0114] Specifically, each node is assigned a node identifier that is unique in the entire network, namely, a node ID, and the value of the node ID is less than the total number of nodes (65536 or 256).

[0115] Furthermore, the nodes have a unified mapping relationship, and the node identification (node ​​ID) and the IP address can be mapped one by one.

[0116] Meanwhile, the present invention only supports internal addressing of wireless ad hoc networks.

[0117] According to a computer-readable storage medium storing a computer program provided by the present invention, the steps of the above-mentioned method are implemented when the computer program is executed by a processor.

[0118] An OLSR routing protocol message compression device provided according to the present invention includes: a controller;

[0119] The controller includes the computer-readable storage medium storing a computer program as described above, or the controller includes the OLSR routing protocol message compression system as described above.

[0120] Example 2

[0121] Embodiment 2 is a preferred embodiment of Embodiment 1

[0122] According to RFC 5444, the air interface message <msg-addr-length>Parameter, the IPv4 type address value is 3, and the IPv6 type address value is 15. For the self-organizing network of this project, the following expansion is performed, namely <msg-addr-length>It can be 0 or 1 (that is, the actual length is 1 or 2 bytes). When the total number of nodes is less than 256, the value is 0; when the total number of nodes is greater than or equal to 256 and less than 65536, the value is 1.

[0123] According to RFC 5444, the air interface message <addr-block>Code Stream <addr-flag>Can be used to indicate whether the current address contains, <head-length> 、 <tail> 、 <tail-length>In this method, if <msg-addr-length>If the value is 0 or 1, the addr-flag tag should be modified to <head-length> 、 <tail> 、 <tail-length>Not included.

[0124] <addr-block>The address carried by the message. The address in the message is: <mid> : <tail>The compression format is <msg-addr-length>= 0 or 1, the address does not carry <head-length> 、 <tail> 、 <tail-length>etc. fields, only contains multiple <mid>, used to represent the node identifier (NodeId).

[0125] Example 3

[0126] Embodiment 3 is a preferred embodiment of Embodiment 1

[0127] like Figure 1 The figure shows a part of a network with less than 256 nodes. Node 1 has symmetric links with nodes 2, 3, and 4, so the number of IP addresses carried in the HELLO message of node 1 is 4 (including the address of this node). The multiple IPV4 addresses that need to be included in the HELLO message are: 192.167.0.1 (node ​​ID = 1), 192.168.1.1 (node ​​ID = 2), 192.169.2.1 (node ​​ID = 3), 192.170.3.1 (node ​​ID = 4).

[0128] The compression method provided by the RFC5444 protocol results are as follows:

[0129] <num-addr> ＝4

[0130] <addr-flags>=0xC0

[0131] <head-length> ＝1

[0132] ＝192

[0133] <tail-length> ＝1

[0134] <tail> ＝1

[0135] <mid>=167,0,168,1,169,2,170,3

[0136] Not counted <num-addr>and <addr-flags>The address part of the field occupies 12 bytes, see Table 1 for details.

[0137] This method uses node ID instead of IP address to identify nodes in messages. According to the compression method provided by the new scheme, the results are as follows:

[0138] <num-addr> ＝4

[0139] <addr-flags> ＝0x00

[0140] <head-length>Do not carry

[0141] Do not carry

[0142] <tail-length>Do not carry

[0143] <tail>Do not carry

[0144] <mid>=1,2,3,4

[0145] Not counted <num-addr>and <addr-flags>The address part of the field occupies 4 bytes, as shown in Table 2. This is a significant improvement compared to the 12 bytes occupied by the OLSR protocol compression method.

[0146] Table 1 RFC5444 protocol compression results

[0147]

[0148] Note: <message-header> : <msg-addr-length>=3, indicating that the node identification adopts the IPv4 identification, for example, IP=192.167.0.1.

[0149] Table 2 Compression results of this method

[0150] Byte1 Byte2 Byte3 Byte4 --- --- <num-addr> ＝4 < / num-addr> <addr-flags> ＝0x00 < / addr-flags> <mid1> ＝1 < / mid1> <mid2> ＝2 < / mid2> <mid3> ＝3 < / mid3> <mid4> ＝4 < / mid4>

[0151] Note: <message-header> : <msg-addr-length>=0, indicating that the node identification adopts a 1-byte node ID, for example, node ID=4.

[0152] Those skilled in the art know that, in addition to implementing the system, device and its various modules provided by the present invention in a purely computer-readable program code, it is entirely possible to implement the same program in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded microcontrollers by logically programming the method steps. Therefore, the system, device and its various modules provided by the present invention can be considered as a hardware component, and the modules included therein for implementing various programs can also be considered as structures within the hardware component; the modules for implementing various functions can also be considered as both software programs for implementing the method and structures within the hardware component.

[0153] The above describes the specific embodiments of the present invention. It should be understood that the present invention is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essence of the present invention. In the absence of conflict, the embodiments of the present application and the features in the embodiments can be combined with each other arbitrarily. < / message-header> < / message-header> < / mid> < / tail> < / addr-flags> < / num-addr> < / mid> < / tail> < / tail-length> < / head-length> < / num-addr> < / mid> < / tail> < / head-length> < / tail> < / mid> < / tail> < / head-length> < / tail> < / head-length> < / mid> < / mid> < / mid> < / tail-length> < / tail> < / head-length> < / address-block> < / mid> < / tail> < / tail-length> < / mid> < / tail> < / tail-length> < / head-length> < / addr-flags> < / num-addr> < / address-block> < / msg-hop-count> < / msg-hop-limit> < / msg-orig-addr> < / msg-size> < / msg-addr-length> < / msg-flags> < / msg-type> < / msg-header> < / mid> < / mid> < / mid> < / tail-length> < / tail> < / head-length> < / address-block> < / mid> < / tail> < / tail-length> < / mid> < / tail> < / tail-length> < / head-length> < / addr-flags> < / num-addr> < / address-block> < / msg-hop-count> < / msg-hop-limit> < / msg-orig-addr> < / msg-size> < / msg-addr-length> < / msg-flags> < / msg-type> < / msg-header> < / mid> < / mid> < / mid> < / address-block> < / mid> < / mid> < / mid> < / address-block> < / mid> < / tail> < / tail> < / mid> < / mid> < / tail> < / tail-length> < / head-length> < / addr-flags> < / num-addr> < / addr-block> < / msg-seq-num> < / msg-hop-count> < / msg-hop-limit> < / msg-orig-addr> < / msg-size> < / msg-addr-length> < / msg-flags> < / msg-type> < / message-header> < / tlv-block> < / addr-block> < / tlv-block> < / message-header> < / message> < / message> < / packet-header> < / packet>

Claims

1. A method for compressing OLSR routing protocol messages, characterized in that: include: The node IP address in the OLSR control signaling is replaced by the network-wide unique node ID, which compresses the length of the air interface message, reduces the air interface message overhead, improves the wireless self-organizing network transmission rate and network robustness, and avoids network congestion caused by excessively large messages; Step S1: Get the current network size and set <message-header>of <msg-addr-length>value; when the total number of nodes in the network is less than 256, <msg-addr-length>Set to 0, when the total number of nodes in the network is greater than or equal to 256 but less than 65536, <msg-addr-length> Set to 1;< / msg-addr-length> Step S2: According to the number of node identifiers carried in the HELLO message and the TC message, set <address-block> : <num-addr> value;< / num-addr> < / address-block> Step S3: According to <msg-addr-length>Set the value of <address-block>In <addr-flag>field; when <msg-addr-length>If the value is 0 or 1, <addr-flag> The mark is changed to 0;< / addr-flag> Step S4: According to <msg-addr-length>The value of <address-block>of <mid>field; when <msg-addr-length>Set to 0, <mid>Each node identifier contained takes up 1 byte; if <msg-addr-length>Set to 1, <mid> Each node identifier contained takes up 2 bytes.< / mid> < / mid> < / mid> 2. The OLSR routing protocol message compression method according to claim 1, characterized in that: The network-wide unique node identifier assigned to each node is less than the total number of nodes.

3. The OLSR routing protocol message compression method according to claim 1, characterized in that: The nodes have a unified mapping relationship, mapping the node ID and the node IP address one by one.

4. The OLSR routing protocol message compression method according to claim 1, characterized in that: Only addressing within wireless ad hoc networks is supported.

5. An OLSR routing protocol message compression system, characterized in that: include: The node IP address in the OLSR control signaling is replaced by the network-wide unique node ID, which compresses the length of the air interface message, reduces the air interface message overhead, improves the wireless self-organizing network transmission rate and network robustness, and avoids network congestion caused by excessively large messages; Module M1: Get the current network size and set <message-header>of <msg-addr-length>value; when the total number of nodes in the network is less than 256, <msg-addr-length>Set to 0, when the total number of nodes in the network is greater than or equal to 256 but less than 65536, <msg-addr-length> Set to 1;< / msg-addr-length> Module M2: Set the number of node identifiers carried in the HELLO message and the TC message <address-block> : <num-addr> value;< / num-addr> < / address-block> Module M3: Based on <msg-addr-length>Set the value of <address-block>In <addr-flag>field; when <msg-addr-length>If the value is 0 or 1, <addr-flag> The mark is changed to 0;< / addr-flag> Module M4: Based on <msg-addr-length>The value of <address-block>of <mid>field; when <msg-addr-length>Set to 0, <mid>Each node identifier contained takes up 1 byte; if <msg-addr-length>Set to 1, <mid> Each node identifier contained takes up 2 bytes.< / mid> < / mid> < / mid> 6. The OLSR routing protocol message compression system according to claim 5, characterized in that: The network-wide unique node ID assigned to each node is less than the total number of nodes.

7. The OLSR routing protocol message compression system according to claim 5, characterized in that: The nodes have a unified mapping relationship, mapping the node ID and the node IP address one by one.

8. The OLSR routing protocol message compression system according to claim 5, characterized in that: Only addressing within wireless ad hoc networks is supported.

Images