Service connection method, apparatus and system

Abstract

The application provides a service connection method, device and system, wherein the service connection method applied to a first node comprises the following steps: receiving first configuration information sent by a first device and sending the first configuration information to mesh nodes in a self-organizing network except the first node, so that a second node sends the first configuration information to a second device, receiving second configuration information sent by the second node and sending the second configuration information to the first device, so that the first device and the second device perform service communication. According to the service connection method applied to the first node, the first device can automatically send the first configuration information to the first node, the first node sends the first configuration information to the mesh nodes in the self-organizing network except the first node, then the second node sends the first configuration information to the second device, and the second configuration information can be sent to the first device, so that the first device and the second device can perform service communication. The application has higher efficiency in automatically setting configuration information and improves the ease of use in an emergency communication scene.

Description

Technical Field

[0001] This application relates to the field of ad hoc network technology, and in particular to service connection methods, apparatus and systems. Background Technology

[0002] A self-organizing network consists of mesh nodes and external devices, enabling scheduling and command in specific scenarios, such as emergency situations. Currently, after the self-organizing network is set up, the configuration information of the external devices needs to be manually set by the user before the external devices can communicate with each other for services, such as audio and video communication.

[0003] However, manual configuration is inefficient and the configuration information can change, making it difficult to use for emergency communications. Summary of the Invention

[0004] In view of this, this application provides a service connection method, apparatus, and system to solve the problem that the configuration information of external devices in existing self-organizing networks needs to be manually set. The technical solution is as follows:

[0005] A service continuity method, characterized in that it is applied to a first node, wherein the first node is any mesh node in an ad hoc network;

[0006] Service continuity methods include:

[0007] Receive the first configuration information sent by the first device;

[0008] The first configuration information is sent to the mesh nodes in the ad hoc network other than the first node, so that the second node can send the first configuration information to the second device. The second node is a node in the mesh nodes in the ad hoc network other than the first node that is connected to the second device.

[0009] The device receives second configuration information sent by the second node and sends the second configuration information to the first device so that the first device and the second device can communicate for services. The second configuration information is the configuration information sent by the second device to the second node.

[0010] Optionally, the first configuration information and / or the second configuration information may include one or more of the following: IP address, device type, and identity information.

[0011] Optional, also includes:

[0012] Based on the heartbeat information sent by the first device, determine whether the first device is offline;

[0013] If the first device goes offline, the first notification message will be sent to all mesh nodes in the ad hoc network except for the first node, so that the second node can notify the second device to delete the first configuration information. The first notification message is used to notify the first device to go offline.

[0014] Optional, also includes:

[0015] Receive a second notification message sent by the second node, wherein the second notification message is information sent by the second node to the first node to notify the second device to go offline;

[0016] Notify the first device to delete the second configuration information.

[0017] A service continuity method is applied to a first device, which is any device in an ad hoc network;

[0018] Service continuity methods include:

[0019] The first node sends its own first configuration information to the first node, so that after the first node sends the first configuration information to the mesh nodes in the self-organizing network other than the first node, the second node sends the first configuration information to the second device. The second node is a node in the mesh nodes in the self-organizing network other than the first node that is connected to the second device.

[0020] The device receives second configuration information sent by the first node to enable business communication with the second device. The second configuration information is the configuration information sent by the second device to the first node through the second node.

[0021] Optional, also includes:

[0022] Send heartbeat information to the first node so that the first node can determine whether the first device is offline based on the heartbeat information.

[0023] Optional, also includes:

[0024] Receive a second notification message sent by the first node, wherein the second notification message is a message sent by the second node to the first node to notify the second device to go offline;

[0025] Delete the second configuration information stored within itself.

[0026] A service continuity system includes a first device, a second device, and at least two mesh nodes, wherein the at least two mesh nodes include the first node and the second node, the first node is any mesh node in the ad hoc network, and the second node is any mesh node in the ad hoc network other than the first node.

[0027] The first device is used to send its own first configuration information to the first node;

[0028] The first node is used to receive the first configuration information and send the first configuration information to the mesh nodes in the self-organizing network other than the first node;

[0029] The second node is used to receive the first configuration information and send the first configuration information to the second device;

[0030] The second device is used to receive the first configuration information and send its own second configuration information to the second node;

[0031] The second node is also used to receive the second configuration information and send the second configuration information to the mesh nodes in the self-organizing network other than the second node;

[0032] The first node is also used to receive the second configuration information and send the second configuration information to the first device so that the first device and the second device can communicate for services.

[0033] A service connection device is applied to a first node, which is any mesh node in an ad hoc network.

[0034] The service connection device includes: a first receiving module, a first transmitting module, and a second receiving module;

[0035] The first receiving module is used to receive the first configuration information sent by the first device;

[0036] The first sending module is used to send the first configuration information to the mesh nodes in the ad hoc network other than the first node, so that the second node can send the first configuration information to the second device. The second node is a node in the mesh nodes in the ad hoc network other than the first node that is connected to the second device.

[0037] The second receiving module is used to receive the second configuration information sent by the second node and send the second configuration information to the first device so that the first device and the second device can communicate for services. The second configuration information is the configuration information sent by the second device to the second node.

[0038] A service connection device is applied to a first device, which is any device in an ad hoc network, and the first device is connected to a first node.

[0039] The service connection device includes: a second transmitting module and a third receiving module;

[0040] The second sending module is used to send its own first configuration information to the first node, so that after the first node sends the first configuration information to the mesh nodes in the ad hoc network other than the first node, the second node sends the first configuration information to the second device. The second node is a node in the mesh nodes in the ad hoc network other than the first node that is connected to the second device.

[0041] The third receiving module is used to receive the second configuration information sent by the first node in order to conduct business communication with the second device. The second configuration information is the configuration information sent by the second device to the first node through the second node.

[0042] As can be seen from the above technical solutions, the service connection method for the first node provided in this application receives first configuration information sent by the first device and sends the first configuration information to the mesh nodes in the ad hoc network other than the first node, so that the second node can send the first configuration information to the second device. It also receives second configuration information sent by the second node and sends the second configuration information to the first device, so that the first device and the second device can communicate. In this service connection method for the first node, the first device can automatically send its own first configuration information to the first node, and the first node then notifies the mesh nodes in the ad hoc network of the first configuration information. Thus, the second node can automatically send the first configuration information to the second device. Similarly, the second device's second configuration information can be sent to the first device, enabling the first device and the second device to communicate. Compared to the prior art where the configuration information of external devices in an ad hoc network needs to be manually set, this application's automatic configuration setting is more efficient, and it also improves usability in emergency communication scenarios. Attached Figure Description

[0043] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0044] Figure 1 A flowchart illustrating the service continuity method provided in this application embodiment;

[0045] Figure 2 This is a schematic diagram illustrating the process of terminal 1 and terminal 2 connecting to a PC, as provided in the embodiments of this application.

[0046] Figure 3 A schematic diagram of the structure of a service connection device applied to a first node provided in an embodiment of this application;

[0047] Figure 4 A schematic diagram of the structure of a service connection device applied to a first device provided in an embodiment of this application;

[0048] Figure 5 A hardware structure block diagram of a service connection device applied to a first node provided in an embodiment of this application;

[0049] Figure 6 This is a hardware structure block diagram of a service connection device applied to a first device, provided as an embodiment of this application. Detailed Implementation

[0050] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0051] Given that existing ad hoc networks require manual configuration of external devices, leading to inefficiency and poor usability in emergency communication scenarios, the inventors of this application conducted in-depth research and ultimately proposed a service connection method, apparatus, and system. This service connection method, apparatus, and system are applicable to wireless private network trunking communication. The following embodiments will provide a detailed description of the service connection method provided in this application.

[0052] Please see Figure 1 The diagram illustrates a flowchart of a service continuity method provided in an embodiment of this application. This service continuity method may include:

[0053] S101, The first device is connected to the first node.

[0054] Here, the first device can be any device in the ad hoc network. Optionally, the first device can be a dispatch console, terminal, or other device. The terminal can be a smartphone or a device containing a camera, such as a law enforcement recorder.

[0055] It should be noted that in this embodiment, the dispatch console and the terminal are usually connected to different mesh nodes. Different terminals can be connected to the same mesh node or to different mesh nodes.

[0056] In this step, after powering on, the first device can connect to any mesh node in the ad hoc network to access the ad hoc network. That is, in this step, the first device can access the ad hoc network through any mesh node. For ease of subsequent description, this application refers to the mesh node connected to the first device as the first node. Optionally, the first device can connect to the first node via wired or wireless means (e.g., WIFI).

[0057] S102, The first device sends its own first configuration information to the first node.

[0058] Optionally, the first device can send and receive configuration information based on pre-generated software. In this step, after running the software, the first device can register its own first configuration information with the first node.

[0059] Optionally, the first configuration information may include one or more of the following: the IP address of the first device, the type of the first device, and the identity information of the first device. Of course, in this embodiment, the first configuration information may also be other types, and this application does not limit it.

[0060] Optionally, this step can be performed together with step S101. After the first device is powered on, it connects to any mesh node in the ad hoc network. During the connection process, the information sent carries the first configuration information, or the connection initiated by the first device contains the first configuration information.

[0061] S103. The first node sends the first configuration information to all mesh nodes in the self-organizing network except for the first node.

[0062] In the solution provided in this embodiment, each mesh node can share information with other mesh nodes after receiving the information. Based on this, in this step, after receiving the first configuration information sent by the first device, the first node can notify all mesh nodes in the ad hoc network of the first configuration information. After receiving the first configuration information, each mesh node can store the first configuration information so that it can be sent to the external device after connecting to it.

[0063] Optionally, in this step, after receiving the first configuration information, the first node can immediately send the first configuration information to each of the above mesh nodes. Of course, it can also periodically send the first configuration information to each of the above mesh nodes, that is, the first node can periodically synchronize the first configuration information to each mesh node.

[0064] S104, The second device is connected to the second node.

[0065] The connection process in this step is the same as in S101 above. For details, please refer to the description in S101 above. It will not be repeated here.

[0066] In this embodiment, the second device is different from the first device. Optionally, the second device may also be a dispatch console, terminal, or other similar device.

[0067] Optionally, the second device in this step can be any of the devices in the ad hoc network other than the first device, or any one of the devices in the ad hoc network other than the first device. If the second device is any of the devices in the ad hoc network other than the first device, then the mesh nodes connected to each of these devices are all considered as second nodes. If the second device is any one of the devices in the ad hoc network other than the first device, then the mesh nodes connected to this second device are considered as second nodes.

[0068] S105, the second node sends the first configuration information to the second device.

[0069] In S103, the first node sends the first configuration information to the mesh nodes in the ad hoc network other than the first node. Then the second node will receive the first configuration information and can then send the first configuration information to the second device.

[0070] After receiving the first configuration information, the second device can save the first configuration information so that it can communicate with the first device for business purposes based on the first configuration information in the future.

[0071] Step S106: The second device sends its second configuration information to the second node.

[0072] The process of sending the second configuration information in this step is the same as in S102 above. For details, please refer to the description in S102 above. It will not be repeated here.

[0073] Optionally, the second configuration information may include one or more of the following: the IP address of the second device, the type of the second device, and the identity information of the second device. Of course, in this embodiment, the second configuration information may also be other types, and this application does not limit its scope.

[0074] S107. The second node sends the second configuration information to all mesh nodes in the self-organizing network except for the second node.

[0075] The process of sending the second configuration information in this step is the same as in S103 above. For details, please refer to the description in S103 above. It will not be repeated here.

[0076] S108, The first node sends the second configuration information to the first device.

[0077] In the previous step, the second node sends the second configuration information to the mesh nodes in the ad hoc network other than the second node. The first node will then receive the second configuration information and can then send the second configuration information to the first device.

[0078] After receiving the second configuration information, the first device can save the second configuration information. With the first device saving the second configuration information and the second device saving the first configuration information, the first device and the second device can perform business communication.

[0079] Optionally, the business communication here can be audio and video business communication.

[0080] It should be noted that the embodiments of this application do not limit the execution order of S101 to S108. For example, S104 and S101 can be executed simultaneously or before S101. In addition, S101 and S102 can be completed in one configuration, and S104 and S106 can also be completed in one configuration.

[0081] The service continuity method provided in this application embodiment allows a first device to automatically send its first configuration information to a first node. The first node then notifies the mesh nodes in the ad hoc network of the first configuration information, thereby enabling a second node to automatically send its first configuration information to a second device. Similarly, the second device's second configuration information can be sent to the first device, allowing the first and second devices to communicate. Compared to the prior art where the configuration information of external devices in an ad hoc network needs to be manually set, this application's automatic configuration information setting is more efficient, and it also improves usability in emergency communication scenarios.

[0082] It is understandable that during the business communication between the first device and the second device, the first device and / or the second device may go offline. After the device goes offline, the first device and the second device cannot communicate. At this time, the device that is not offline can delete the configuration information of the offline device stored in the storage.

[0083] Based on this, in an optional embodiment, building upon the previous embodiment, for the case where the first device is offline but the second device is not offline, this application embodiment may include the following steps:

[0084] S109. The first device sends heartbeat information to the first node.

[0085] Optionally, after the first device connects to the first node, the first device may periodically send heartbeat information to the first node so that the first node can determine whether the first device is offline based on the heartbeat information.

[0086] S110. The first node determines whether the first device is offline based on the heartbeat information sent by the first device.

[0087] Optionally, the first node may periodically detect whether it receives heartbeat information sent by the first device, and determine whether the first device is offline based on whether it receives heartbeat information sent by the first device. If no heartbeat information is received from the first device, the first device is determined to be offline; if heartbeat information is received from the first device, the first device is determined to be online.

[0088] Optionally, in one embodiment, in addition to the heartbeat information of the first device, the first node may also determine that the first device is offline if it receives an offline message sent by the first device.

[0089] S111. If the first node detects that the first device is offline, it sends the first notification information to all mesh nodes in the ad hoc network except for the first node.

[0090] Here, the first notification message is used to notify the first device to be taken offline.

[0091] S112, The second node notifies the second device to delete the first configuration information.

[0092] In this step, after the second node determines that the first device is offline based on the first notification information, it can notify the second device to delete the first configuration information.

[0093] Optionally, the process of the second node notifying the second device to delete the first configuration information in this step can include the following two implementation methods:

[0094] The first implementation method is as follows: The second node can forward the first notification information to the second device so that the second device can delete the first configuration information.

[0095] The second implementation method is as follows: The second node sends a deletion instruction to the second device to delete the first configuration information, so that the second device can delete the first configuration information based on the received deletion instruction.

[0096] It should be noted that the above two implementation methods are only examples. In addition, other implementation methods can be used for this step, which are not limited here.

[0097] Step S113: The second device deletes the first configuration information stored in its own memory.

[0098] According to S109 to S113 above, when the first device is offline but the second device is not offline, the first configuration information stored in the second device can be deleted.

[0099] It is understandable that there may be a situation where the second device goes offline while the first device does not. In this case, the second configuration information can be deleted as follows: The second node determines whether the second device is offline based on the heartbeat information sent by the second device. If the second device is offline, the second node sends a second notification message to the first node to notify the second device of its offline status. Then, the first node notifies the first device to delete the second configuration information, so that the first device can delete the second configuration information stored within itself. This process is similar to S109 to S113 above, and details can be found in the descriptions of S109 to S113 above, which will not be repeated here.

[0100] This application also provides a service continuity system, which includes a first device, a second device, and at least two mesh nodes. The at least two mesh nodes include a first node and a second node. The first node is any mesh node in the ad hoc network, and the second node is any mesh node in the ad hoc network other than the first node.

[0101] In this system, the first device can send its own first configuration information to the first node. After receiving the first configuration information, the first node can send the first configuration information to all mesh nodes in the ad hoc network except for the first node. The mesh nodes in this ad hoc network, excluding the first node, include the second node. Based on this, after receiving the first configuration information, the second node can send the first configuration information to the second device. Thus, after receiving the first configuration information, the second device can save the first configuration information for subsequent business communication with the first device.

[0102] Similar to the process described above, the second device can also send its second configuration information to the second node. Upon receiving the second configuration information, the second node can then forward it to all mesh nodes in the ad hoc network except for the second node. This ad hoc network includes the first node among the mesh nodes excluding the second node. Therefore, upon receiving the second configuration information, the first node can send it to the first device, allowing the first device to save the second configuration information.

[0103] With the first device storing the second configuration information and the second device storing the first configuration information, the first device and the second device can communicate for services.

[0104] In an optional embodiment, the first device may also send heartbeat information to the first node during the connection with the first node, so that the first node can determine whether the first device is offline based on the heartbeat information sent by the first device. If the first device is offline, the first notification information for notifying the first device of its offline status will be sent to the mesh nodes in the ad hoc network other than the first node, so that after receiving the first notification information, the second node can notify the second device to delete the first configuration information. After that, the second device can delete the first configuration information stored in itself.

[0105] In another optional embodiment, the second device may also send heartbeat information to the second node during the connection with the second node, so that the second node can determine whether the second device is offline based on the heartbeat information sent by the second device. If the second device is offline, a second notification information for notifying the second device of its offline status will be sent to the mesh nodes in the ad hoc network other than the second node, so that after the first node receives the second notification information, it can notify the first device to delete the second configuration information. After that, the first device can delete the second configuration information stored in itself.

[0106] In summary, the service continuity system provided in this application embodiment and the above-described service continuity method can be referred to each other. For details, please refer to the description in the above-described service continuity method, which will not be repeated here.

[0107] To enable those skilled in the art to better understand the service connection method and system provided in the embodiments of this application, the following takes a service connection system including terminal 1 (e.g., a smartphone or law enforcement recorder), terminal 2 (e.g., a smartphone or law enforcement recorder), PC (i.e., dispatch console), mesh node 1, mesh node 2 and mesh node 3 as an example, and gives a specific embodiment to describe in detail the specific process of service connection between terminal 1 and terminal 2 and PC.

[0108] See Figure 2 This is a schematic diagram of the optional process for terminal 1 and terminal 2 to connect to a PC in an embodiment of this application.

[0109] S201, Terminal 1 is connected to mesh node 1, and PC is connected to mesh node 3.

[0110] In this step, after terminal 1 is powered on, it can connect to mesh node 1; similarly, after PC is powered on, it can connect to mesh node 3.

[0111] Optionally, the connection method in this step can include wired and wireless (e.g., WIFI) connections.

[0112] It should be noted that terminal 1 can also connect to mesh node 2 and mesh node 3 in the ad hoc network. For example, when terminal 1 goes offline and then comes back online, it can connect to mesh node 2 or mesh node 3. Similarly, PC can also connect to mesh node 1 and mesh node 2.

[0113] S202, Terminal 1 sends its own configuration information 1 to mesh node 1, and PC sends its own configuration information 2 to mesh node 3.

[0114] In this step, terminal 1 can run software and register its own configuration information 1 with mesh node 1; similarly, PC can run software and register its own configuration information 2 with mesh node 3.

[0115] Optionally, this step can be performed together with step S201, that is, the first configuration information is sent during the connection process between terminal 1 and mesh1 node after the terminal 1 is powered on, or the first configuration information is included in the initiated connection. Similarly, the PC can also send a connection containing the first configuration information, or send the first configuration information during the connection process.

[0116] S203, mesh node 1 sends configuration information 1 to mesh node 2 and mesh node 3, and mesh node 3 sends configuration information 2 to mesh node 1 and mesh node 2.

[0117] S204 and mesh node 3 send configuration information 1 to the PC, while mesh node 1 sends configuration information 2 to the terminal.

[0118] Through the above steps S201 to S204, terminal 1 can communicate with the PC for business purposes.

[0119] S205 and mesh node 1 perform heartbeat detection on terminal 1, and mesh node 3 performs heartbeat detection on the PC.

[0120] In this step, terminal 1 can send heartbeat information to mesh node 1 so that mesh node 1 can determine whether terminal 1 is offline based on the heartbeat information of terminal 1; similarly, PC can send heartbeat information to mesh node 3 so that mesh node 3 can determine whether PC is offline based on the heartbeat information of PC.

[0121] S206. When terminal 1 is powered off, mesh node 1 detects that terminal 1 is offline and sends notification information 1 indicating that terminal 1 is offline to mesh node 2 and mesh node 3.

[0122] In this step, if terminal 1 is powered off, mesh node 1 can detect that terminal 1 is offline. At this time, notification information 1 indicating that terminal 1 is offline will be sent to mesh node 2 and mesh node 3.

[0123] S207, mesh node 3 notifies the PC to delete configuration information 1.

[0124] S208, the PC deletes its own stored configuration information 1.

[0125] By following steps S205 to S208, terminal 1 can cease business communication with the PC after it goes offline.

[0126] S209, Terminal 2 connects to mesh node 1 and sends its own configuration information 3 to mesh node 1.

[0127] In this step, after terminal 2 is powered on, it can still connect to mesh node 1 and register its own configuration information 3 with mesh node 1.

[0128] S210 and mesh node 1 send configuration information 2 to terminal 2, and send configuration information 3 to mesh node 2 and mesh node 3.

[0129] S211, mesh node 3 sends configuration information 3 to the PC.

[0130] The above steps S209 to S211 enable terminal 2 to communicate with the PC.

[0131] In summary, as can be seen from this embodiment, after the terminal and PC are powered on, they can connect to the mesh node and automatically send their own configuration information to the connected mesh node. Then, the mesh node can send the configuration information of the external device to other mesh nodes in the ad hoc network, and then the other mesh nodes will send the received configuration information to their own external devices. Compared with the prior art where the configuration information of the external device in the ad hoc network needs to be manually set, this application automatically sets the configuration information, which makes it more efficient and improves the ease of use in emergency communication scenarios.

[0132] This application also provides a service connection device, which can be applied to a first node, which is any mesh node in an ad hoc network. The service connection device applied to the first node provided in this application is described below. The service connection device applied to the first node described below can be referred to in correspondence with the service connection method described above.

[0133] Please see Figure 3 This illustration shows a structural diagram of a service connection device applied to a first node according to an embodiment of this application, such as... Figure 3As shown, the service connection device applied to the first node may include: a first receiving module 301, a first sending module 302, and a second receiving module 303.

[0134] The first receiving module 301 is used to receive the first configuration information sent by the first device.

[0135] The first sending module 302 is used to send the first configuration information to the mesh nodes in the ad hoc network other than the first node, so that the second node can send the first configuration information to the second device. The second node is a node in the mesh nodes in the ad hoc network other than the first node that is connected to the second device.

[0136] The second receiving module 303 is used to receive the second configuration information sent by the second node and send the second configuration information to the first device so that the first device and the second device can communicate for services. The second configuration information is the configuration information sent by the second device to the second node.

[0137] The service connection device for a first node provided in this application receives first configuration information sent by a first device and sends the first configuration information to mesh nodes in the ad hoc network other than the first node, so that a second node can send the first configuration information to a second device. It also receives second configuration information sent by the second node and sends the second configuration information to the first device, enabling the first and second devices to communicate. In this service connection device for a first node, the first device can automatically send its own first configuration information to the first node, and the first node then notifies the mesh nodes in the ad hoc network of the first configuration information. Thus, the second node can automatically send the first configuration information to the second device. Similarly, the second device's second configuration information can be sent to the first device, enabling the first and second devices to communicate. Compared to existing technologies where the configuration information of external devices in an ad hoc network needs to be manually set, this application's automatic configuration setting is more efficient, and it also improves usability in emergency communication scenarios.

[0138] In one possible implementation, the service connection device applied to the first node provided in this application includes one or more of the following information: IP address, device type, and identity information.

[0139] In one possible implementation, the service connection device for the first node provided in this application embodiment may further include: a heartbeat detection module and a third sending module.

[0140] The heartbeat detection module is used to determine whether the first device is offline based on the heartbeat information sent by the first device.

[0141] The third sending module is used to send a first notification message to all mesh nodes in the ad hoc network except the first node if the first device goes offline, so that the second node can notify the second device to delete the first configuration information. The first notification message is used to notify the first device to go offline.

[0142] In one possible implementation, the service connection device for the first node provided in this application embodiment may further include: a fourth receiving module and a notification module.

[0143] The fourth receiving module is used to receive the second notification information sent by the second node, wherein the second notification information is information sent by the second node to the first node to notify the second device to go offline.

[0144] The notification module is used to notify the first device to delete the second configuration information.

[0145] This application also provides a service connection device, which can be applied to a first device, which is any device in an ad hoc network. The service connection device applied to the first device provided in this application is described below. The service connection device applied to the first device described below can be referred to in correspondence with the service connection method described above.

[0146] Please see Figure 4 This illustration shows a schematic diagram of the structure of a service connection device applied to a first device according to an embodiment of this application, such as... Figure 4 As shown, the service connection device applied to the first device may include: a second transmitting module 401 and a third receiving module 402.

[0147] The second sending module 401 is used to send its own first configuration information to the first node, so that after the first node sends the first configuration information to the mesh nodes in the ad hoc network other than the first node, the second node sends the first configuration information to the second device, wherein the second node is a node in the mesh nodes in the ad hoc network other than the first node that is connected to the second device.

[0148] The third receiving module 402 is used to receive the second configuration information sent by the first node so as to conduct business communication with the second device. The second configuration information is the configuration information sent by the second device to the first node through the second node.

[0149] The service connection device for a first device provided in this application sends its own first configuration information to a first node. After the first node sends the first configuration information to all mesh nodes in the ad hoc network (excluding the first node), the second node sends the first configuration information to the second device and receives the second configuration information sent by the first node, enabling service communication with the second device. In this service connection device for a first device, the first device can automatically send its own first configuration information to the first node, which then notifies all mesh nodes in the ad hoc network of the first configuration information. Thus, the second node can automatically send the first configuration information to the second device. Similarly, the second device's second configuration information can be sent to the first device, enabling service communication between the first and second devices. Compared to existing technologies where external device configuration information in ad hoc networks requires manual setup, this application's automatic configuration information setup is more efficient and improves usability in emergency communication scenarios.

[0150] In one possible implementation, the service connection device for the first device provided in this application may further include: a heartbeat information sending module.

[0151] The heartbeat information sending module is used to send heartbeat information to the first node so that the first node can determine whether the first device is offline based on the heartbeat information.

[0152] In one possible implementation, the service connection device for the first device provided in this application embodiment may further include: a fifth receiving module and a deletion module.

[0153] The fifth receiving module is used to receive the second notification information sent by the first node, wherein the second notification information is information sent by the second node to the first node to notify the second device to go offline.

[0154] The delete module is used to delete the second configuration information stored within itself.

[0155] This application embodiment also provides a service connection device, which can be applied to a first node, which is any mesh node in a self-organizing network. Optionally, Figure 5 The hardware structure block diagram of the service connection device applied to the first node is shown. (Refer to...) Figure 5 The hardware structure of the service connection device applied to the first node may include: at least one processor 501, at least one communication interface 502, at least one memory 503 and at least one communication bus 504.

[0156] In this embodiment of the application, the number of processor 501, communication interface 502, memory 503 and communication bus 504 is at least one, and processor 501, communication interface 502 and memory 503 communicate with each other through communication bus 504.

[0157] The processor 501 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.

[0158] The memory 503 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device;

[0159] The memory 503 stores a program, and the processor 501 can call the program stored in the memory 503. The program is used for:

[0160] Receive the first configuration information sent by the first device;

[0161] The first configuration information is sent to the mesh nodes in the self-organizing network other than the first node, so that the second node can send the first configuration information to the second device. The second node is the node in the mesh nodes in the self-organizing network other than the first node that is connected to the second device.

[0162] The device receives second configuration information sent by the second node and sends the second configuration information to the first device so that the first device and the second device can communicate for services. The second configuration information is the configuration information sent by the second device to the second node.

[0163] Optionally, the refined and extended functions of the program can be found in the description above.

[0164] This application embodiment also provides a service connection device, which can be applied to a first device, which is any device in a self-organizing network. Optionally, Figure 6 A hardware structure block diagram of the service connection equipment applied to the first device is shown, with reference to Figure 6 The hardware structure of the service connection device applied to the first device may include: at least one processor 601, at least one communication interface 602, at least one memory 603 and at least one communication bus 604.

[0165] In this embodiment of the application, the number of processor 601, communication interface 602, memory 603 and communication bus 604 is at least one, and processor 601, communication interface 602 and memory 603 communicate with each other through communication bus 604.

[0166] The processor 601 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.

[0167] The memory 603 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk storage device;

[0168] The memory 603 stores a program, and the processor 601 can call the program stored in the memory 603. The program is used for:

[0169] The first node sends its own first configuration information to the first node, so that after the first node sends the first configuration information to the mesh nodes in the self-organizing network other than the first node, the second node sends the first configuration information to the second device. The second node is a node in the mesh nodes in the self-organizing network other than the first node that is connected to the second device.

[0170] The device receives second configuration information sent by the first node to enable business communication with the second device. The second configuration information is the configuration information sent by the second device to the first node through the second node.

[0171] Optionally, the refined and extended functions of the program can be found in the description above.

[0172] This application embodiment also provides a readable storage medium storing a computer program thereon. When the computer program is executed by a processor, it implements the various processing flows of the first node in the service connection method as described above, or implements the various processing flows of the first device in the service connection method as described above.

[0173] Optionally, the refined and extended functions of the program can be found in the description above.

[0174] Finally, it should be noted that in this document, relational terms such as "second" and "etc." are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0175] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0176] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A service continuity method, characterized in that, It is applied to the first node, which is any mesh node in the ad hoc network; The service continuity method includes: Receive first configuration information sent by a first device, wherein the first device is an external device connected to the first node in the self-organizing network; The first configuration information is sent to the mesh nodes in the self-organizing network other than the first node, so that the second node can send the first configuration information to the second device. The second node is a node in the mesh nodes in the self-organizing network other than the first node that is connected to the second device. The device receives second configuration information sent by the second node and sends the second configuration information to the first device so that the first device and the second device can communicate for services. The second configuration information is the configuration information sent by the second device to the second node.

2. The service continuity method according to claim 1, characterized in that, The first configuration information and / or the second configuration information include one or more of the following: IP address, device type, and identity information.

3. The service continuity method according to claim 1, characterized in that, Also includes: Based on the heartbeat information sent by the first device, determine whether the first device is offline; If the first device goes offline, a first notification message is sent to all mesh nodes in the ad hoc network except the first node, so that the second node can notify the second device to delete the first configuration information. The first notification message is used to notify the first device to go offline.

4. The service continuity method according to claim 3, characterized in that, Also includes: Receive a second notification message sent by the second node, wherein the second notification message is information sent by the second node to the first node to notify the second device to go offline; The first device is notified to delete the second configuration information.

5. A service continuity method, characterized in that, It is applied to a first device, which is any external device connected to the first node in the self-organizing network; The service continuity method includes: The first node sends its own first configuration information to the first node, so that after the first node sends the first configuration information to the mesh nodes in the self-organizing network other than the first node, the second node sends the first configuration information to the second device, wherein the second node is a node in the mesh nodes in the self-organizing network other than the first node that is connected to the second device. The device receives second configuration information sent by the first node to enable business communication with the second device, wherein the second configuration information is configuration information sent by the second device through the second node.

6. The service continuity method according to claim 5, characterized in that, Also includes: Send heartbeat information to the first node so that the first node can determine whether the first device is offline based on the heartbeat information.

7. The service continuity method according to claim 6, characterized in that, Also includes: Receive a second notification message sent by the first node, wherein the second notification message is information sent by the second node to the first node to notify the second device to go offline; Delete the second configuration information stored within itself.

8. A service continuity system, characterized in that, It includes a first device, a second device, and at least two mesh nodes, wherein the at least two mesh nodes include a first node and a second node, the first node is any mesh node in the ad hoc network, the second node is a node in the ad hoc network other than the first node that is connected to the second device, and the first device is an external device in the ad hoc network that is connected to the first node. The first device is used to send its own first configuration information to the first node; The first node is configured to receive the first configuration information and send the first configuration information to the mesh nodes in the self-organizing network other than the first node. The second node is used to receive the first configuration information and send the first configuration information to the second device; The second device is configured to receive the first configuration information and send its own second configuration information to the second node; The second node is also configured to receive the second configuration information and send the second configuration information to the mesh nodes in the self-organizing network other than the second node; The first node is further configured to receive the second configuration information and send the second configuration information to the first device so that the first device and the second device can perform business communication.

9. A service connection device, characterized in that, It is applied to the first node, which is any mesh node in the ad hoc network; The service connection device includes: a first receiving module, a first sending module, and a second receiving module; The first receiving module is used to receive first configuration information sent by the first device, wherein the first device is an external device connected to the first node in the self-organizing network; The first sending module is used to send the first configuration information to the mesh nodes in the self-organizing network other than the first node, so that the second node can send the first configuration information to the second device, wherein the second node is a node in the mesh nodes in the self-organizing network other than the first node that is connected to the second device. The second receiving module is used to receive the second configuration information sent by the second node and send the second configuration information to the first device so that the first device and the second device can perform service communication, wherein the second configuration information is the configuration information sent by the second device to the second node.

10. A service connection device, characterized in that, It is applied to a first device, which is any external device connected to the first node in the self-organizing network; The service connection device includes: a second sending module and a third receiving module; The second sending module is used to send its own first configuration information to the first node, so that after the first node sends the first configuration information to the mesh nodes in the self-organizing network other than the first node, the second node sends the first configuration information to the second device, wherein the second node is a node in the mesh nodes in the self-organizing network other than the first node that is connected to the second device. The third receiving module is used to receive second configuration information sent by the first node in order to conduct business communication with the second device, wherein the second configuration information is configuration information sent by the second device to the first node through the second node.

Images