Self-organizing network communication system and message communication method thereof, and readable storage medium
Through the message communication method of the ad hoc network communication system, forward and reverse link building request messages are built, and the network is automatically formed to solve the problem of multicast path discovery, which improves communication efficiency, is suitable for channels with limited bandwidth, and avoids advanced nodes planning.
Patent Information
- Application Number
- CN202310024088.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-01-09
- Publication Date
- 2024-12-13
- Estimated Expiration
- 2043-01-09
AI Technical Summary
In the discovery of multicast paths in existing communication systems, multicast routing is inconsistent with the data flow path, and the standard dynamic routing protocol cannot be run under limited bandwidth, resulting in low communication efficiency and requiring early node planning.
Using the message communication method of the ad hoc network communication system, the forward link building request messages and reverse link building request messages are constructed through the service source node, the intermediate node and the service target node, and the network is automatically formed and the path is constructed, which is suitable for any Wireless or wired channels, any one-way or two-way channel, improve communication efficiency and avoid early node planning.
It realizes improving communication efficiency under limited bandwidth, and automatic networking does not require advanced node planning, and is suitable for channels that cannot run standard dynamic routing protocols.
Smart Images

Figure CN116155799B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a self-organizing network communication system and a message communication method and a readable storage medium thereof. Background Art
[0002] In communication systems, multicast path discovery is mostly done according to the control layer protocol, that is, multicast path discovery is usually achieved through multicast routing, rather than the path that the actual multicast data flow passes through. In some cases, the multicast routing may not be consistent with the multicast data flow, so it is necessary to detect the multicast path based on the actual multicast data flow.
[0003] However, all of these require node planning and network planning in advance, and their applicability is low. Summary of the invention
[0004] In order to solve the above problems, the present application provides a self-organizing network communication system and its message communication method, and a readable storage medium, which are applicable to any wireless or wired channel, any unidirectional or bidirectional channel, especially channels that cannot run standard dynamic routing protocols (such as OSPF, RIP, BGP, etc.) due to low bandwidth, to improve communication efficiency and eliminate the need for advance node planning and network planning.
[0005] A technical solution adopted in the present application is to provide a message communication method for a self-organizing network communication system, the self-organizing network communication system includes multiple service nodes, each service node includes a receiving device and a sending device, the method includes: the service source node responds to receiving a service message, and uses the service source node and at least one intermediate node and the service target node to construct a forward link establishment request message and a reverse link establishment request message; wherein the forward link establishment request message at least includes a forward path target address, a forward path source address and a forward path passing ID list; the reverse link establishment request message includes a forward path target address, a forward path target address mask, a forward path passing ID list, a reverse path target address, a reverse path source address, and a reverse path passing ID list; the service source node sends the service message to the service target node according to the forward link establishment request message and the reverse link establishment request message.
[0006] The service source node, in response to receiving the service message, constructs a forward link establishment request message and a reverse link establishment request message using the service source node, at least one intermediate node and the service target node, including: the service source node, in response to receiving the service message, constructs a forward link establishment request message, and sends the forward link establishment request message to at least one intermediate node; the intermediate node, in response to not matching the forward path target address in the forward link establishment request message, adds the receiving device ID and the sending device ID of the intermediate node to the forward path passing ID list of the forward link establishment request message; the intermediate node, in response to matching the forward path target address in the forward link establishment request message, uses the intermediate node as the service target node, adds the receiving device ID of the intermediate node to the forward path passing ID list of the forward link establishment request message, constructs a reverse link establishment request message, and sends the reverse link establishment request message to at least one intermediate node. an intermediate node; in response to the reverse path target address in the reverse link establishment request message not matching, at least one intermediate node adds the receiving device ID and the sending device ID of at least one intermediate node to the reverse path path ID list of the reverse link establishment request message; in response to the reverse path target address in the reverse link establishment request message matching, at least one intermediate node is used as a service source node, the receiving device ID of the service source node is added to the reverse path path ID list of the reverse link establishment request message, and a reverse link establishment response message is constructed, the reverse link establishment response message at least includes a forward path target address, a forward path target address mask, a forward path path ID list, a number of remaining nodes on the forward path, a reverse path target address, a reverse path target address mask, and a reverse path path ID list, and the reverse link establishment response message is sent to the service target node through at least one intermediate node.
[0007] Among them, the service source node obtains the forward target address segment and the forward path node ID list from the reverse link establishment request message, and the service target node obtains the reverse target address segment and the reverse path ID list from the reverse link establishment response message.
[0008] The service source node sends the service message to the service target node according to the forward link establishment request message and the reverse link establishment request message, including: the service source node constructs a data message according to the forward target address segment, the forward path passing node ID list and the service message; wherein the data message at least includes the forward target address segment, the selected forward path passing node ID list, the forward path remaining ID number and the service message; the service source node sends the data message to the intermediate node corresponding to the first device ID in the forward path passing node ID list; when the intermediate node receives the data message, the forward path remaining ID number is reduced by 1. In response to the forward path remaining ID number being greater than 0, the intermediate node sends it to the intermediate node corresponding to the next device ID in the selected forward path passing ID list; in response to the forward path remaining ID number being equal to 0, the intermediate node strips the service message from the data message and sends the service message to the access side port of the intermediate node according to the forward target address segment.
[0009] The data message at least includes the forward target address segment, the selected forward path ID list, the number of remaining forward path IDs, the service message forward path request sequence number, and the forward path response sequence number.
[0010] Among them, in response to the number of remaining IDs of the forward path being equal to 0, the intermediate node determines whether the service message needs to be responded to. If so, the response content is encapsulated into a data response message, and the data response message at least includes a reverse target address segment, a selected reverse path passing ID list, a reverse path remaining ID number, a reverse path request sequence number, a forward path response sequence number, and a service message; if not, a maintenance response message is constructed, and the maintenance response message at least includes a reverse target address segment, a selected reverse path passing ID list, a reverse path remaining ID number, a reverse path request sequence number, and a forward path response sequence number.
[0011] Among them, when there are multiple paths to a certain target address segment, the route maintenance function will switch to the low-priority path after determining that the high-priority path is disconnected. When the high-priority path is restored, it will switch back to the high-priority path.
[0012] Among them, after each business node sends or forwards a data message by selecting a forward path, it then sends a greeting request message by selecting a forward path. The greeting request message at least includes a list of all online sending devices of the business node, a list of all online receiving devices, the local address, and the neighbor address; the neighbor node of the business node receives the greeting reply message by selecting a forward path and also sends a greeting reply message by selecting a reverse path. The greeting reply message at least includes a list of all sending devices of the neighbor node, a list of all online receiving devices, the local address, and the neighbor address; when the business node receives the greeting reply message sent by the neighbor node, it sends a neighbor detection request message to the neighbor node through all online sending devices of the node; the neighbor detection request message It at least includes the following fields: the sending device ID of the business node, the receiving device ID of the business node, the local address, and the neighbor address; after the neighbor node receives the neighbor detection message through the receiving device, the neighbor node sends a neighbor detection response message through the sending device associated with the receiving device; the neighbor detection response message at least includes the sending device ID of the business node, the receiving device ID of the business node, the sending device ID of the neighbor node, the receiving device ID of the neighbor node, the local address, and the neighbor address; when the business node receives the neighbor detection response message and finds that the priority of the sending device of the business node is higher than the priority of the sending device of the selected forward path, the sending device ID of the business node and the receiving device ID of the neighbor node are recorded in the path preference list.
[0013] Another technical solution adopted by the present application is to provide a self-organizing network communication system, which includes multiple service nodes, each service node includes a receiving device and a sending device; the service source node responds to receiving the service message, and uses the service source node and at least one intermediate node and the service target node to construct a forward link establishment request message and a reverse link establishment request message; wherein the forward link establishment request message at least includes a forward path target address, a forward path source address and a forward path passing ID list; the reverse link establishment request message includes a forward path target address, a forward path target address mask, a forward path passing ID list, a reverse path target address, a reverse path source address, and a reverse path passing ID list;
[0014] The service source node sends the service message to the service target node according to the forward link establishment request message and the reverse link establishment request message.
[0015] Another technical solution adopted by the present application is to provide a computer-readable storage medium, which is used to store a computer program. When the computer program is executed by a processor, it is used to implement any method of the above solution.
[0016] The beneficial effect of the present application is that, different from the prior art, the message communication method of the self-organizing network communication system of the present application comprises a plurality of service nodes, each service node comprises a receiving device and a sending device, and the method comprises: in response to receiving a service message, the service source node constructs a forward link establishment request message and a reverse link establishment request message using the service source node and at least one intermediate node and the service target node; wherein the forward link establishment request message comprises at least a forward path target address, a forward path source address and a forward path passing ID list; the reverse link establishment request message comprises a forward path target address, a forward path target address mask, a forward path passing ID list, a reverse path target address, a reverse path source address and a reverse path passing ID list; the service source node sends the service message to the service target node according to the forward link establishment request message and the reverse link establishment request message. Through the above method, arbitrary automatic networking of nodes is utilized, which is applicable to any wireless or wired channel, any unidirectional or bidirectional channel, especially the channel that cannot run standard dynamic routing protocols (such as OSPF, RIP, BGP, etc.) due to small bandwidth, to improve communication efficiency and eliminate the need for advance node planning and network planning. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0018] in:
[0019] Figure 1 It is a flow chart of an embodiment of a message communication method of a self-organizing network communication system provided by the present application;
[0020] Figure 2-Figure 27 It is a schematic diagram of the message structure received or sent by the service source node, intermediate node, and service target node provided by this application;
[0021] Fig.28 It is a structural schematic diagram of an embodiment of a computer-readable storage medium provided by the present application. DETAILED DESCRIPTION
[0022] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It will be understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for ease of description, only some but not all structures related to the present application are shown in the drawings. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.
[0023] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0024] The ad hoc network communication system includes multiple service nodes, each of which includes a receiving device and a sending device. The ports of each service node are divided into two types: access side ports and channel side ports. The channel side ports are connected to sending devices and receiving devices, including but not limited to radio stations, etc. They can be bidirectional devices or unidirectional devices.
[0025] If it is a unidirectional device, in order to complete transmission and reception, the service node must include a transmitting device and a receiving device.
[0026] The sending device and receiving device of each service node are configured with a unique identifier (ID) in the entire network. According to the performance parameters of the sending device (bandwidth, delay, packet loss rate, etc.), a priority is set for each sending device.
[0027] See also Figure 1 , Figure 1 It is a flow chart of the first embodiment of the message communication method of the self-organizing network communication system provided by the present application.
[0028] Step 11: In response to receiving the service message, the service source node uses the service source node and at least one intermediate node and the service target node to construct a forward link establishment request message and a reverse link establishment request message.
[0029] Among them, the forward link establishment request message includes at least the forward path target address, the forward path source address and the forward path passing ID list; the reverse link establishment request message includes the forward path target address, the forward path target address mask, the forward path passing ID list, the reverse path target address, the reverse path source address, and the reverse path passing ID list.
[0030] In some embodiments, in response to receiving a service message, the service source node constructs a forward link establishment request message and sends the forward link establishment request message to at least one intermediate node.
[0031] In response to the mismatch between the forward path target address in the forward link establishment request message, the intermediate node adds the receiving device ID and the sending device ID of the intermediate node to the forward path passing ID list of the forward link establishment request message.
[0032] In response to matching the forward path target address in the forward link establishment request message, the intermediate node is used as the service target node, and the receiving device ID of the intermediate node is added to the forward path passing ID list of the forward link establishment request message, and a reverse link establishment request message is constructed and sent to at least one intermediate node.
[0033] In response to the mismatch between the reverse path target address in the reverse link establishment request message, at least one intermediate node adds the receiving device ID and the sending device ID of the at least one intermediate node to the reverse path passing ID list of the reverse link establishment request message.
[0034] In response to matching the reverse path target address in the reverse link establishment request message, at least one intermediate node uses the at least one intermediate node as a service source node, adds the receiving device ID of the service source node to the reverse path passing ID list of the reverse link establishment request message, and constructs a reverse link establishment response message, the reverse link establishment response message at least includes the forward path target address, the forward path target address mask, the forward path passing ID list, the number of remaining nodes on the forward path, the reverse path target address, the reverse path target address mask, and the reverse path passing ID list, and sends the reverse link establishment response message to the service target node through at least one intermediate node.
[0035] Among them, the service source node obtains the forward target address segment and the forward path node ID list from the reverse link establishment request message, and the service target node obtains the reverse target address segment and the reverse path ID list from the reverse link establishment response message.
[0036] Step 12: The service source node sends the service message to the service target node according to the forward link establishment request message and the reverse link establishment request message.
[0037] Among them, the service source node constructs a data message according to the forward target address segment, the forward path passing node ID list and the service message; wherein the data message at least includes the forward target address segment, the selected forward path passing ID list, the remaining number of forward path IDs and the service message; the service source node sends the data message to the intermediate node corresponding to the first device ID in the forward path passing node ID list.
[0038] When the intermediate node receives the data message, the number of remaining IDs on the forward path is reduced by 1. In response to the number of remaining IDs on the forward path being greater than 0, the intermediate node sends the message to the intermediate node corresponding to the next device ID in the ID list passed by the selected forward path.
[0039] The intermediate node responds that the number of remaining IDs in the forward path is equal to 0, indicating that the intermediate node is a service target node, so the service message is stripped from the data message and sent to the access side port of the intermediate node according to the forward target address segment.
[0040] In other embodiments, the data message includes at least a forward target address segment, a selected forward path passing ID list, a number of remaining forward path IDs, a service message forward path request sequence number, and a forward path response sequence number.
[0041] Among them, the intermediate node responds that the number of remaining IDs in the forward path is equal to 0, indicating that the intermediate node is a service target node, so it is necessary to determine whether the service message needs to be responded to. If it needs to be responded to, the response content is encapsulated into a data response message. The data response message at least includes the reverse target address segment, the selected reverse path ID list, the number of remaining IDs in the reverse path, the reverse path request sequence number, the forward path response sequence number, and the service message.
[0042] If no response is required, the service target node constructs a maintenance response message, which at least includes the reverse target address segment, the selected reverse path ID list, the number of reverse path remaining IDs, the reverse path request sequence number, and the forward path response sequence number.
[0043] In other embodiments, when there are multiple paths to a target address segment, the route maintenance function determines that a high priority path is disconnected and switches to a low priority path. When the high priority path is restored, it switches back to the high priority path.
[0044] Among them, after each business node sends or forwards a data message by selecting a forward path, it then sends a greeting request message by selecting a forward path. The greeting request message at least includes a list of all online sending devices of the business node, a list of all online receiving devices, the local address, and the neighbor address; the neighbor node of the business node receives the greeting reply message by selecting a forward path and also sends a greeting reply message by selecting a reverse path. The greeting reply message at least includes a list of all sending devices of the neighbor node, a list of all online receiving devices, the local address, and the neighbor address; when the business node receives the greeting reply message sent by the neighbor node, it sends a neighbor detection request message to the neighbor node through all online sending devices of the node; the neighbor detection request message It at least includes the following fields: the sending device ID of the business node, the receiving device ID of the business node, the local address, and the neighbor address; after the neighbor node receives the neighbor detection message through the receiving device, the neighbor node sends a neighbor detection response message through the sending device associated with the receiving device; the neighbor detection response message at least includes the sending device ID of the business node, the receiving device ID of the business node, the sending device ID of the neighbor node, the receiving device ID of the neighbor node, the local address, and the neighbor address; when the business node receives the neighbor detection response message and finds that the priority of the sending device of the business node is higher than the priority of the sending device of the selected forward path, the sending device ID of the business node and the receiving device ID of the neighbor node are recorded in the path preference list.
[0045] In an application scenario, the ports of each service node are divided into two types: access side ports and channel side ports. The channel side ports are connected to the sending device and the receiving device, including but not limited to the radio station, etc. They can be bidirectional devices or unidirectional devices.
[0046] If it is a unidirectional device, in order to complete transmission and reception, the service node must include a transmitting device and a receiving device.
[0047] The sending device and receiving device of each service node are configured with a unique identifier (ID) in the entire network. According to the performance parameters of the sending device (bandwidth, latency, packet loss rate, etc.), the priority of each sending device is set. Specifically, it includes functions such as path establishment, data transmission, path maintenance, and path optimization.
[0048] Combination Figure 2 , the path establishment can be the following process:
[0049] 1) The service source node receives the service message (including the target address and source address) from the access side port, parses the service target address, and finds that there is no path to the target address segment, so it caches the service message. Construct a forward link establishment request message such as Figure 3As shown, the forward link establishment request message contains at least the following fields: forward path target address, forward path source address, and forward path ID list. The forward path ID list is filled with the sending device ID and sent to all sending devices of this node. The sending device can be a wired or wireless channel, a bidirectional or unidirectional channel, and broadcasts the link establishment request. If the service source node has multiple sending devices in the same frequency band, in order to avoid interference, different delays are set for sending according to the priority of the sending device.
[0050] 2) The intermediate node receives the forward link establishment request through the receiving device. Figure 4 As shown in FIG. 1 , if the forward target address is found not to belong to the access side address segment, the receiving device ID of the intermediate node and the sending device ID of the intermediate node are added to the forward path ID list of the forward link establishment request message, as shown in FIG. Figure 5 As shown, the forward link establishment request is then broadcasted to all sending devices of the intermediate node. If the intermediate node has multiple sending devices of the same frequency band, different delays are set for sending according to the priority of the sending device to avoid interference.
[0051] 3) The service target node receives the forward link establishment request message through the receiving device, such as Figure 6 As shown in the figure, if the forward target address segment is found to belong to its own access side address segment, the receiving device ID of the service target node is added to the forward path ID list of the forward link establishment request message. A reverse link establishment request message is constructed, and the reverse link establishment request message contains at least the following fields: forward path target address, forward path target address mask, forward path ID list, reverse path target address (i.e. forward path source address), reverse path source address, and reverse path ID list. Among them, the reverse path ID list is filled with only one sending device ID, which is sent to all sending devices of this service target node.
[0052] 4) The intermediate node receives the reverse link establishment request sent by the service target node or the previous intermediate node through the receiving device. Figure 7 As shown in FIG. 1 , if the reverse target address segment is not one of its own access side address segments, the receiving device ID of the intermediate node and the sending device ID of the intermediate node are added to the reverse path ID list of the reverse link establishment request message, such as Figure 8 As shown, it is then sent to all sending devices of the intermediate node to broadcast and forward the reverse link establishment request.
[0053] 5) The service source node receives a reverse link establishment request message sent by the intermediate node or the service target node, such as Fig.10As shown in FIG. 1 , if the reverse target address segment is found to be one of its own access side address segments, the receiving device ID of the service source node is added to the reverse path ID list of the reverse link establishment request message, such as Fig.11 As shown in the figure, the forward path target address segment and the forward path ID list are recorded. Construct a reverse link establishment response message, such as Fig.12 The message shown includes at least the following fields: forward path target address, forward path target address mask, forward path passing ID list, number of remaining nodes on the forward path, reverse path target address, reverse path target address mask, reverse path passing ID list, and the first device ID sent to the forward path passing ID list.
[0054] 6) The intermediate node receives the reverse link establishment response sent by the previous intermediate node or service source node through the receiving device, and the number of remaining nodes in the forward path is reduced by 1, such as Fig.13 If the number of remaining IDs is greater than 0, the ID of the next device in the ID list of the forward path is sent.
[0055] 7) The service target node receives the reverse link establishment response sent by the previous intermediate node or service source node through the receiving device, and the number of remaining IDs on the forward path is reduced by 1. If the number of remaining nodes is 0, the reverse path target address, reverse path target address mask, and reverse path ID list are recorded, such as Fig.14 shown.
[0056] Through the above steps, the service source node obtains the forward target address segment and the ID list of the nodes passed by the forward path, and the service target node obtains the reverse target address segment and the ID list passed by the reverse path.
[0057] If a forward target address segment has multiple forward paths passing through the ID list, the priority is set according to the bandwidth of the sending device and the receiving device, and the number of IDs. The wider the bandwidth, the higher the priority, and the fewer the number of IDs, the higher the priority. The available path with the highest priority is the selected path, and the rest are alternative paths.
[0058] That is, combined Fig.15 , data transmission can include the following processes:
[0059] 1) The service source node takes out the cached service message, or receives the service message from the access side port, and constructs the data message, such as Fig.16 The data message contains at least the following fields: forward target address segment, selected forward path ID list, number of remaining forward path IDs, business message, and the first device ID sent to the selected forward path ID list.
[0060] 2) The intermediate node receives the data message through the receiving device, such as Fig.17As shown, the number of remaining IDs on the forward path is reduced by 1. If the number of remaining IDs is found to be greater than 0, the ID of the next device in the ID list passed by the selected forward path is sent.
[0061] 3) The service target node receives the data message through the receiving device, such as Fig.18 As shown, the number of remaining IDs in the forward path is reduced by 1. If the number of remaining IDs is 0, the service message is stripped out and sent to the access side port according to the target address segment.
[0062] In some embodiments, Fig.19 As shown, path maintenance is used to determine whether a forward path is disconnected. Since the bandwidth of the transmitting device and the receiving device in the node may be very small, it is not possible to send additional keep-alive messages regularly, so data messages are directly used as keep-alive messages.
[0063] Specifically, the service source node is each forward path, and the service target node is each reverse path. A serial number (SN) range is set, and a SN is generated for each selected path at regular intervals. The SN increases regularly. After reaching the maximum value of the range, it increases regularly from the minimum value of the range.
[0064] The service source node constructs a data message, such as Fig. 20 As shown, when sending through the selected forward path, in addition to the fields of the above data message, two more fields are added: forward path request SN and forward path response SN. The forward path request SN is filled with the sequence number generated regularly by the service source node, and the forward path response SN is empty.
[0065] The service target node receives the data message, such as Fig.21 As shown, if the service needs to be responded, the response content is encapsulated into a data response message. The data response message contains at least the following fields: reverse target address segment, selected reverse path passing ID list, reverse path remaining ID number, reverse path request SN, forward path response SN, and service message. The reverse path request SN is filled with the SN generated periodically by the service target node, and the forward path response SN is filled with the forward path request SN sent by the service source node. If the service does not need to be responded, a maintenance response message is also constructed, which contains at least the following fields: reverse target address segment, selected reverse path passing ID list, reverse path remaining ID number, reverse path request SN, and forward path response SN.
[0066] The service source node receives a data response message or a maintenance response message, such as Fig. 22 As shown, the selected forward path is considered to be available. When the service source node sends a service message next time, in the above step, the forward path response SN is filled in with the reverse path request SN sent by the service target node.
[0067] The service source node sets a cyclic timer (the timing duration can be set). When the timer times out, if the number of packets sent by the source node increases, but no data response message or maintenance response message is received, and this situation occurs multiple times (the number of times can be set), the forward path state is set to disconnected. At this time, if there are other forward paths in the target address segment, the other forward paths are set to selected, otherwise the path establishment process is initiated. If the forward path state is disconnected and the number of path packets does not increase for a long time (the time can be set), this forward path is deleted.
[0068] Further, combined with Fig.23 , path optimization can include the following processes:
[0069] When there are multiple paths to a target address segment, the route maintenance function determines that the high-priority path is disconnected and switches to the low-priority path. When the high-priority path is restored, it switches back to the high-priority path. This function is called path optimization.
[0070] 1) Each service node (assuming service node A) sends (or forwards) a data message through the selected forward path, and then sends a hello request message through the selected forward path, such as Fig.24 As shown. The hello request message contains at least the following fields: a list of all online sending devices (including priority parameters) of this service node (excluding offline sending devices), a list of all online receiving devices (excluding offline receiving devices), the local address, and the neighbor address. During the first detection, because the neighbor address is unknown, the neighbor address field is filled with the broadcast address.
[0071] 2) The neighbor node (assuming node B) receives the message by selecting the forward path and sends a hello response message by selecting the reverse path. Fig.25 The hello response message also contains at least the following fields: a list of all sending devices (including priority parameters) of this node B, a list of all online receiving devices, the local address, and the neighbor address. The neighbor address is filled in with the local address of the received neighbor detection message.
[0072] 3) When node A receives the greeting response message from node B, it sends a neighbor detection request message to node B through all online sending devices of node A. Fig.26 As shown, the neighbor detection request message includes at least the following fields: the sending device ID of node A, the receiving device ID of node A, the local address, and the neighbor address.
[0073] 4) After receiving the neighbor detection message through the receiving device, node B sends a neighbor detection response message through the sending device associated with the receiving device. Fig. 27As shown, the neighbor detection response message contains at least the following fields: the sending device ID of node A, the receiving device ID of node A, the sending device ID of node B, the receiving device ID of node B, the local address, and the neighbor address. The neighbor address is filled in with the local address of the received neighbor detection request message.
[0074] 4) Node A receives the neighbor detection response message and finds that the priority of the sending device of node A is higher than the priority of the sending device of the selected forward path, so it records the sending device ID of node A and the receiving device ID of node B into the path optimization list. The next time node A sends (or forwards) a data message and finds that there is a value in the path optimization list of this node, it switches to the preferred path instead of using the selected forward path.
[0075] This ensures that the highest priority available path is used every time.
[0076] Another technical solution adopted by the above-mentioned present application is to provide a self-organizing network communication system, which includes multiple service nodes, each service node includes a receiving device and a sending device; the service source node responds to receiving the service message, and uses the service source node and at least one intermediate node and the service target node to construct a forward link establishment request message and a reverse link establishment request message; wherein the forward link establishment request message at least includes a forward path target address, a forward path source address and a forward path passing ID list; the reverse link establishment request message includes a forward path target address, a forward path target address mask, a forward path passing ID list, a reverse path target address, a reverse path source address, and a reverse path passing ID list;
[0077] The service source node sends the service message to the service target node according to the forward link establishment request message and the reverse link establishment request message.
[0078] See also Fig.28 , Fig.28 1 is a schematic diagram of a structure of an embodiment of a computer-readable storage medium provided in the present application. The computer-readable storage medium 110 is used to store a computer program 111. When the computer program 111 is executed by a processor, it is used to implement the following method:
[0079] In response to receiving the service message, the service source node uses the service source node and at least one intermediate node and the service target node to construct a forward link establishment request message and a reverse link establishment request message; wherein the forward link establishment request message at least includes a forward path target address, a forward path source address and a forward path passing ID list; the reverse link establishment request message includes a forward path target address, a forward path target address mask, a forward path passing ID list, a reverse path target address, a reverse path source address, and a reverse path passing ID list; the service source node sends the service message to the service target node according to the forward link establishment request message and the reverse link establishment request message.
[0080] It can be understood that when the computer program 111 is executed by a processor, it is used to implement the method of any of the above embodiments.
[0081] In this application, the use of any automatic networking of nodes is applicable to any wireless or wired channel, any unidirectional or bidirectional channel, especially channels that cannot run standard dynamic routing protocols (such as OSPF, RIP, BGP, etc.) due to low bandwidth, to improve communication efficiency and eliminate the need for advance node planning and network planning.
[0082] The above description is only an implementation method of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly used in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A message communication method for a self-organizing network communication system, characterized in that: The self-organizing network communication system includes a plurality of service nodes, each service node includes a receiving device and a sending device, and the method includes: In response to receiving the service message, the service source node constructs a forward link establishment request message and a reverse link establishment request message using the service source node, at least one intermediate node and the service target node; wherein the forward link establishment request message at least includes a forward path target address, a forward path source address and a forward path passing ID list; and the reverse link establishment request message includes a forward path target address, a forward path target address mask, a forward path passing ID list, a reverse path target address, a reverse path source address and a reverse path passing ID list; The service source node sends the service message to the service target node according to the forward link establishment request message and the reverse link establishment request message; the service source node, in response to receiving the service message, constructs a forward link establishment request message and a reverse link establishment request message using the service source node, at least one intermediate node and the service target node, including: The service source node constructs a forward link establishment request message in response to receiving the service message, and sends the forward link establishment request message to at least one intermediate node; In response to the intermediate node not matching the forward path target address in the forward link establishment request message, the intermediate node adds the receiving device ID and the sending device ID of the intermediate node to the forward path passing ID list of the forward link establishment request message; In response to matching the forward path target address in the forward link establishment request message, the intermediate node takes the intermediate node as the service target node, adds the receiving device ID of the intermediate node to the forward path passing ID list of the forward link establishment request message, constructs a reverse link establishment request message, and sends the reverse link establishment request message to the at least one intermediate node; In response to the at least one intermediate node not matching the reverse path target address in the reverse link establishment request message, the at least one intermediate node adds the receiving device ID and the sending device ID of the at least one intermediate node to the reverse path passing ID list of the reverse link establishment request message; In response to matching the reverse path target address in the reverse link establishment request message, the at least one intermediate node uses the at least one intermediate node as the service source node, adds the receiving device ID of the service source node to the reverse path passing ID list of the reverse link establishment request message, and constructs a reverse link establishment response message, wherein the reverse link establishment response message at least includes a forward path target address, a forward path target address mask, a forward path passing ID list, a number of remaining nodes on the forward path, a reverse path target address, a reverse path target address mask, and a reverse path passing ID list, and sends the reverse link establishment response message to the service target node through the at least one intermediate node.
2. The method according to claim 1, characterized in that The service source node obtains the forward target address segment and the forward path node ID list from the reverse link establishment request message, and the service target node obtains the reverse target address segment and the reverse path node ID list from the reverse link establishment response message.
3. The method according to claim 2, characterized in that The service source node sends the service message to the service target node according to the forward link establishment request message and the reverse link establishment request message, including: The service source node constructs a data message according to the forward target address segment, the forward path node ID list and the service message; wherein the data message at least includes the forward target address segment, the selected forward path ID list, the number of remaining forward path IDs and the service message; The service source node sends the data message to the intermediate node corresponding to the first device ID in the node ID list passed by the forward path; When the intermediate node receives the data message, the number of remaining IDs on the forward path is reduced by 1. In response to the number of remaining IDs on the forward path being greater than 0, the intermediate node sends the message to the intermediate node corresponding to the next device ID in the ID list passed by the selected forward path; In response to the number of remaining IDs on the forward path being equal to 0, the intermediate node strips the service message from the data message, and sends the service message to the access side port of the intermediate node according to the forward target address segment.
4. The method according to claim 3, characterized in that The data message at least includes a forward target address segment, a selected forward path ID list, a number of remaining forward path IDs, a service message forward path request sequence number, and a forward path response sequence number.
5. The method according to claim 4, characterized in that In response to the number of remaining IDs of the forward path being equal to 0, the intermediate node determines whether the service message needs to be responded to, and if so, encapsulates the response content into a data response message, wherein the data response message at least includes a reverse target address segment, a selected reverse path ID list, a reverse path remaining ID number, a reverse path request sequence number, a forward path response sequence number, and a service message; If not, construct a maintenance response message, which at least includes the reverse target address segment, the selected reverse path ID list, the number of reverse path remaining IDs, the reverse path request sequence number, and the forward path response sequence number.
6. The method according to claim 3, characterized in that When there are multiple paths to a target address segment, the route maintenance function determines that the high-priority path is disconnected and switches to the low-priority path. When the high-priority path is restored, it switches back to the high-priority path.
7. The method according to claim 6, characterized in that After each service node sends or forwards a data message through the selected forward path, it then sends a hello request message through the selected forward path, wherein the hello request message at least includes a list of all online sending devices of the service node, a list of all online receiving devices, a local address, and a neighbor address; The neighbor node of the service node receives the message by selecting the forward path and sends a hello response message by selecting the reverse path. The hello response message at least includes a list of all sending devices of the neighbor node, a list of all online receiving devices, a local address, and a neighbor address. When the service node receives the hello response message from the neighbor node, it sends a neighbor detection request message to the neighbor node through all online sending devices of the node; The neighbor detection request message contains at least the following fields: the sending device ID of the service node, the receiving device ID of the service node, the local address, and the neighbor address; After receiving the neighbor detection message through the receiving device, the neighbor node sends a neighbor detection response message through the sending device associated with the receiving device; The neighbor detection response message contains at least the sending device ID of the service node, the receiving device ID of the service node, the sending device ID of the neighbor node, the receiving device ID of the neighbor node, the local address, and the neighbor address; The service node receives the neighbor detection response message and finds that the priority of the sending device of the service node is higher than the priority of the sending device of the selected forward path, so it records the sending device ID of the service node and the receiving device ID of the neighbor node into the path priority list.
8. A self-organizing network communication system, characterized in that: The self-organizing network communication system includes a plurality of service nodes, each of which includes a receiving device and a sending device; In response to receiving the service message, the service source node constructs a forward link establishment request message and a reverse link establishment request message using the service source node, at least one intermediate node and the service target node; wherein the forward link establishment request message at least includes a forward path target address, a forward path source address and a forward path passing ID list; and the reverse link establishment request message includes a forward path target address, a forward path target address mask, a forward path passing ID list, a reverse path target address, a reverse path source address and a reverse path passing ID list; The service source node sends the service message to the service target node according to the forward link establishment request message and the reverse link establishment request message; In response to receiving the service message, the service source node uses the service source node, at least one intermediate node and the service target node to construct a forward link establishment request message and a reverse link establishment request message, including: The service source node constructs a forward link establishment request message in response to receiving the service message, and sends the forward link establishment request message to at least one intermediate node; In response to the intermediate node not matching the forward path target address in the forward link establishment request message, the intermediate node adds the receiving device ID and the sending device ID of the intermediate node to the forward path passing ID list of the forward link establishment request message; In response to matching the forward path target address in the forward link establishment request message, the intermediate node takes the intermediate node as the service target node, adds the receiving device ID of the intermediate node to the forward path passing ID list of the forward link establishment request message, constructs a reverse link establishment request message, and sends the reverse link establishment request message to the at least one intermediate node; In response to the at least one intermediate node not matching the reverse path target address in the reverse link establishment request message, the at least one intermediate node adds the receiving device ID and the sending device ID of the at least one intermediate node to the reverse path passing ID list of the reverse link establishment request message; In response to matching the reverse path target address in the reverse link establishment request message, the at least one intermediate node uses the at least one intermediate node as the service source node, adds the receiving device ID of the service source node to the reverse path passing ID list of the reverse link establishment request message, and constructs a reverse link establishment response message, wherein the reverse link establishment response message at least includes a forward path target address, a forward path target address mask, a forward path passing ID list, a number of remaining nodes on the forward path, a reverse path target address, a reverse path target address mask, and a reverse path passing ID list, and sends the reverse link establishment response message to the service target node through the at least one intermediate node.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and when the computer program is executed by a processor, the computer program is used to implement the method according to any one of claims 1 to 7.
