Method for automatic switching between mesh push-to-talk and 5g data network push-to-talk

Abstract

The present application relates to a method for automatic switching between mesh push-to-talk and 5G data network push-to-talk. The method comprises: Bluetooth devices creating mesh networks and performing mesh networking; using one node as a master node, and creating an online group on an application by means of the master node; all the Bluetooth devices communicating with the application by means of a bidirectional dynamic heartbeat data mode, and performing information synchronization by means of a virtual network formed by cloud-mapped nodes; communicating voice data between online nodes by means of a mesh mode; and when a Bluetooth device node is offline or reconnected, the node device automatically switching to a data network mode by means of the application, and using the data network mode to perform networked communication by means of a cloud. In the method for automatic switching between mesh push-to-talk and 5G data network push-to-talk, the online status of devices is monitored in real time, and automatic switching to a cloud network is performed for voice data transmission when a device / node is offline, thereby ensuring normal voice data transmission and reception of a disconnected node, and thus also ensuring the real-time performance, coherence and integrity of voice data transmission.

Description

Automatic switching method between Mesh intercom and 5G data network intercom Technical Field

[0001] The present application relates to the technical field related to wireless communications, and in particular to a method for automatically switching between Mesh intercom and 5G data network intercom. Background Art

[0002] Among related technologies, Bluetooth intercom technology is widely used in various fields, such as security intercom, off-road vehicle calls, and small-scale communication fields such as outdoor engineering command. Intercom equipment uses a mesh mechanism to form a voice network to achieve real-time intercom functions. Voice data can be transmitted within the coverage range of the Bluetooth signal.

[0003] The advantages of Bluetooth device communication lie in its short-range wireless connection, low power consumption, ease of pairing and setup, small size, and low cost. However, its limited transmission distance, relatively low data transmission rate, potential interference-induced connection stability, and inter-device compatibility issues hinder normal communication between devices. Due to the presence of obstacles such as buildings or large and small hillsides at the site of use, as well as interference from signals in their respective bands, the strength and reception sensitivity of Bluetooth signals are affected by different usage scenarios, often resulting in intermittent transmissions, which impact the real-time and continuity of voice data transmission. In existing mesh voice networks, when a node is disconnected, the voice data of other nodes is lost, and voice can only be maintained within its own sub-mesh network. The lost node cannot receive or send its own uplink and downlink voice data, affecting the voice data transmission between all other nodes and the lost node, thereby affecting the user experience of Bluetooth intercom devices and preventing the implementation of coherent communication functions.

[0004] The advantages of data network communication lie in its wide coverage, high data transmission rate, support for multiple devices and services, and ability to achieve long-distance communication. Bluetooth is superior to data network efficiency in short-distance communication, thus creating a complementary scenario logic mode between Bluetooth Mesh network and data network, reducing data packet loss. Technical issues

[0005] In order to overcome the problems existing in the relevant technologies, the present application provides an automatic switching method for Mesh intercom and 5G data network intercom, which integrates Bluetooth data communication and data network to effectively break down environmental and distance barriers, reduce data packet loss, and maintain the real-time and coherent integrity of voice data transmission. Technical Solutions

[0006] This application provides a method for automatically switching between Mesh intercom and 5G data network intercom, including:

[0007] S1: The Bluetooth device creates a Mesh network and performs Mesh networking. The Mesh network marks the device_id of all Bluetooth devices and the node information; generates a group identifier mesh_group_id. The mesh_group_id of Bluetooth devices in the same Mesh network is the same.

[0008] In step S2, one of the nodes serves as the master node, and an online group is created on the app through the master node. All Bluetooth devices join the online group through the app, report their node information to the cloud, and map the nodes on the cloud to form a virtual network. All Bluetooth devices in the cloud group have the same network_group_id.

[0009] In S3, all Bluetooth devices communicate with the APP through a two-way dynamic heartbeat data mode, synchronizing the status of the Bluetooth devices with the virtual network formed by the cloud mapping nodes in real time, and synchronously marking the signal strength and online status of the Bluetooth devices;

[0010] S4: In network communication, Mesh mode takes precedence over data network mode; voice data between online nodes is communicated via Mesh mode first;

[0011] S5: The node of the Bluetooth device is offline, and the node device automatically switches to the data network mode through the APP, and uses the data network mode to communicate through the cloud;

[0012] S6: When a device node is detected to be offline, the offline node information is reported and the voice data of the current node is uploaded. The cloud receives the voice data of the node, processes the node and voice data, and determines whether there is cloud data voice. If there is cloud data voice, the node voice data is mixed with the cloud data voice and then the voice data is played. If there is no data voice, the received node voice data is played directly.

[0013] S7, when it is detected that the device node is offline and there are multiple Mesh networks, the current node voice data is uploaded, the cloud receives the node voice data, processes the node and voice data, and determines whether there is cloud data voice. If there is cloud data voice, the node voice data is mixed with the cloud data voice and then the voice data is played; if there is no data voice, the received node voice data is played directly.

[0014] In the above-mentioned automatic switching method between Mesh intercom and 5G data network intercom, in S2, all Bluetooth devices in the virtual network are in the same network_group_id, and the same Mesh node is assigned the same mesh_group_id in the cloud. The network_group_id is equivalent to the parent of the mesh_group_id in the cloud. Devices with the same network_group_id communicate through the cloud in data network mode.

[0015] In the above-mentioned automatic switching method between Mesh intercom and 5G data network intercom, in S3, after the cloud receives the data information, when it finds that a device Mesh is offline, it will send the offline device to all devices in the same network_group_id. At this time, when all devices send voice information, they need to send the Mesh voice data packet at the same time and send it to the cloud through the APP, and then the cloud will send it to the offline device.

[0016] In the above-mentioned automatic switching method between Mesh intercom and 5G data network intercom, when there are offline nodes, if multiple nodes send voice at the same time, the cloud will mix the voice data and send the mixed voice data to the offline devices in the same network_group_id.

[0017] In the above-mentioned automatic switching method between Mesh intercom and 5G data network intercom, when there is an offline node, all Mesh online devices receive the Mesh device voice data and the cloud voice data at the same time, and the Mesh device voice data and the cloud voice data are mixed and played through the APP.

[0018] In the above-mentioned automatic switching method between Mesh intercom and 5G data network intercom, when the device Mesh node is offline and the cloud heartbeat data of the node is offline, the node is judged to be in the off-team state. For the off-team node, the cloud heartbeat data mode is used to inform the other online nodes; the off-team node is judged as non-existent, and voice data does not need to be sent to the off-team node.

[0019] In the automatic switching method between Mesh intercom and 5G data network intercom described above, the offline Mesh reconnects and the cloud heartbeat data automatically reconnects, determining that the node is online. When the node reconnects to the Mesh or the cloud heartbeat data reconnects, the cloud determines and sends a notification to the node whether the node device needs to upload voice data.

[0020] In the above-mentioned automatic switching method between Mesh intercom and 5G data network intercom, in S4, S41, within the same mesh_group_id network, if the voice data does not contain the voice of the offline device, the device only plays the Mesh voice data; S42, within the same mesh_group_id network, Mesh online nodes transmit data through the Mesh network. If there is an offline device, the node sending voice data also sends the voice data through the APP; S43, within the same network_group_id, data between different mesh_group_ids is sent and received in the form of a cloud network.

[0021] In the above-mentioned automatic switching method between Mesh intercom and 5G data network intercom, the data nodes are marked with authority levels through the APP. The master node has a higher authority level than ordinary nodes and has the highest authority to operate on the network, allowing the master node to control data communications of all Mesh nodes.

[0022] In the above-mentioned automatic switching method between Mesh intercom and 5G data network intercom, the master node sets whether to allow the addition of external device users; and specifies the device to set the listening mode, that is, only allowing the reception of voice data but not sending. Beneficial effects

[0023] The technical solution provided by the present application may include the following beneficial effects: This automatic switching method between Mesh intercom and 5G data network intercom, by real-time monitoring of the online status of the device, automatically switches to the cloud network to transmit voice data when the device / node is offline, so as to ensure normal voice data transmission and reception of the disconnected node, and ensure the real-time and coherent integrity of voice data transmission. The online nodes continue to use the Mesh network to transmit voice data, and use the cloud network transmission as a backup channel when the node is disconnected. The channel is enabled in time to ensure the stability and integrity of voice data transmission. By uploading the device information and voice data to the cloud through the APP, the cloud forwards the voice data of each node according to the loss of connection of the Mesh network node, thereby ensuring the normal transmission of voice data when the node is lost, and achieving the effect of all nodes being online and transmitting voice data uninterruptedly in real time.

[0024] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The above and other objects, features and advantages of the present application will become more apparent through a more detailed description of exemplary embodiments of the present application in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of the present application.

[0026] FIG1 is a flow chart of a method for automatically switching between Mesh intercom and 5G data network intercom according to an embodiment of the present application;

[0027] FIG2 is a flow chart of voice processing of a single node in a Mesh intercom according to an automatic switching method between Mesh intercom and 5G data network intercom, as shown in an embodiment of the present application;

[0028] FIG3 is an application example of a method for automatically switching between Mesh intercom and 5G data network intercom in an embodiment of the present application, in which all the members of the same Mesh network are online and the communication is completely within the Mesh;

[0029] FIG4 is an example of a communication method between devices in a Mesh network when some devices are offline, according to an embodiment of the present application, for automatically switching between Mesh intercom and 5G data network intercom.

[0030] FIG5 is an example of a communication method between devices in the same Mesh network when some devices leave the network, according to an embodiment of the present application, in a method for automatically switching between Mesh intercom and 5G data network intercom;

[0031] FIG6 is an example of a method for automatically switching between Mesh intercom and 5G data network intercom in different embodiments of the present application when all devices communicate in a fully online Mesh network;

[0032] FIG7 is an example of a method for automatically switching between Mesh intercom and 5G data network intercom in different Mesh networks when some devices are offline, as shown in an embodiment of the present application;

[0033] FIG8 is an example of a method for automatically switching between Mesh intercom and 5G data network intercom in different Mesh networks when some devices leave the network;

[0034] Figure 9 is an application example of a method for automatic switching between Mesh intercom and 5G data network intercom in an embodiment of the present application, in which the same Mesh network is fully online and the communication is completely within the Mesh. Best Mode for Carrying Out the Invention

[0035] The preferred embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the preferred embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. Instead, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.

[0036] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. As used in this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0037] It should be understood that although the terms "first", "second", "third", etc. may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0038] The technical solutions of the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0039] Referring to Figures 1 to 8, the present application provides a method for automatically switching between Mesh intercom and 5G data network intercom, including:

[0040] S1: The Bluetooth device creates a Mesh network and performs Mesh networking. The Mesh networking marks the device_id of all Bluetooth devices and the node information; generates a group identifier mesh_group_id. The mesh_group_id of Bluetooth devices in the same Mesh network is the same.

[0041] In S2, one of the nodes serves as the master node, and an online group is created on the APP through the master node; all Bluetooth devices join the online group through the APP, report their node information to the cloud, and map the nodes on the cloud to form a virtual network; all Bluetooth devices in the cloud group have the same network_group_id.

[0042] In S2, further comprising: S21, all Bluetooth devices in the virtual network are in the same network_group_id; S22, the same Mesh node is assigned the same mesh_group_id in the cloud, where the network_group_id is equivalent to the parent of the mesh_group_id in the cloud, and devices with the same network_group_id communicate through the cloud in data network mode.

[0043] In S3, all Bluetooth devices communicate with the app via a two-way dynamic heartbeat data mode, synchronizing their status with the virtual network formed by the cloud-based mapping nodes in real time, thereby simultaneously marking the signal strength and online status of the Bluetooth devices. This means that all devices communicate with the app via Bluetooth, continuously reporting the current device Mesh online status and surrounding Mesh device node information to the cloud using a heartbeat data mode. Upon receiving the data, the cloud processes it and sends the status information of the remaining devices in the same Mesh network using the same heartbeat data mode, achieving online and offline device status synchronization.

[0044] In S3, it further includes:

[0045] S31, after the Bluetooth device passes the APP, it continuously sends the device's current Mesh networking status information, device information, communication status, acquired surrounding node status and other device status information to the cloud through the heartbeat data mode, and the cloud processes the basic information of the device status.

[0046] S32, after the cloud receives the data information, when it finds that a device Mesh is offline, it will send the node of the offline device to all devices in the same network_group_id. At this time, when all online devices send voice information, they need to send the Mesh voice data packet at the same time and send it to the cloud through the APP, and then the cloud will send it to the offline device.

[0047] S33: When there are offline nodes, if multiple nodes send voice at the same time, the cloud will mix the voice data and send the mixed voice data to the offline devices in the same network_group_id.

[0048] In S34, when there are offline nodes, all Mesh online devices receive the Mesh device voice data and the cloud voice data at the same time, and mix the Mesh device voice data and the cloud voice data through the APP and then play them.

[0049] S35, when the device Mesh node is offline and the cloud heartbeat data of the node is offline, the node is judged to be in the off-team state. For the off-team node, the cloud heartbeat data mode is used to inform the other online nodes; the off-team node is judged as non-existent, and voice data does not need to be sent to the off-team node.

[0050] S36, offline Mesh reconnection, cloud heartbeat data automatically reconnects, and determines that the node is online.

[0051] S4: In network communication, Mesh mode takes precedence over data network mode; voice data between online nodes is communicated via Mesh mode first;

[0052] In S4, S41, within the same mesh_group_id network, if the voice data does not include offline device voice, the device will only play the mesh voice data. S42, within the same mesh_group_id network, mesh nodes transmit data via the mesh network. If there are offline devices, the node sending voice data also sends voice data via the app. S43, within the same network_group_id, data between different mesh_group_ids is sent and received via the cloud network. This means that all mesh nodes in different subnetworks sending voice data must perform step S42.

[0053] In S5, the node of the Bluetooth device is offline. The node device automatically switches to the data network mode through the APP and uses the data network mode for network communication through the cloud. That is, when the device detects that the Mesh is offline, the node device automatically switches to the data network through the APP and uses the cloud for network communication.

[0054] S6: When the device node is detected to be offline, the Bluetooth device reports the offline node information and uploads the current node voice data; the cloud receives the node voice data, processes the node and voice data, and determines whether there is cloud data voice. If there is cloud data voice, the node voice data is mixed with the cloud data voice and then the voice data is played; if there is no data voice, the received node voice data is played directly;

[0055] S7, when the device node is detected to be offline, if there are multiple Mesh networks, the current node voice data is uploaded, the cloud receives the node voice data, processes the node and voice data, and determines whether there is cloud data voice. If there is cloud data voice, the node voice data is mixed with the cloud data voice and then the voice data is played; if there is no data voice, the received node voice data is played directly.

[0056] Data nodes are assigned authority levels through the app. Master nodes have higher authority than ordinary nodes and have the highest permissions for network operations, allowing them to control data communications across all Mesh nodes. Specific operations include allowing the master node to add external device users and setting a device to listening mode, meaning it can only receive voice data but not send it.

[0057] Figure 2 is a schematic diagram of the voice processing flow of a single node in Mesh intercom.

[0058] Create / join a Mesh network. When a device creates or joins a Mesh network, it forms a mesh_group_id, making it a device with a Mesh network that can implement Bluetooth intercom. At the same time, the device is identified with a device_id and a node is identified, so that the device has a unique node name and device name.

[0059] Connect to the APP. The Bluetooth device that has been equipped with the Mesh network is connected to the dedicated Bluetooth APP, so that the Bluetooth device can realize data transmission and communication with the APP. The Bluetooth device can transmit the data it collects to the APP and wait for the APP to process it after receiving the data.

[0060] The heartbeat data server sends data, and data is transmitted between the Bluetooth device and the APP, and between the APP and the cloud through a two-way heartbeat data mode. The Bluetooth device communicates with the APP, exchanges data, and synchronizes information in real time. At the same time, the APP communicates with the cloud, exchanges data, and synchronizes information in real time, so that the data between the device, the APP, and the cloud are synchronized.

[0061] Create / join a network group and a mesh mirror group on the cloud. Create or join a network group on the cloud to generate a network_group_id. Create or join a virtual network mapped on the cloud.

[0062] Determine whether all nodes are online. After the Bluetooth device network is established, it starts monitoring all nodes and their status. If it is, that is, all nodes are normal and online, it will determine whether there are multiple Mesh networks. If there is only one Mesh network, you can directly conduct Mesh network intercom and generate voice data for this node.

[0063] If a node is detected to be offline, the device will report the node information of the offline node and upload the voice data of the offline node. After the cloud receives the node information and the node voice data, it will process the node information and the node voice data, and determine whether there is cloud data voice. If there is cloud data voice, the node voice data will be mixed with the cloud data voice and the mixed voice data will be played to form the voice data of this node; if there is no cloud data voice, the Mesh voice data will be played directly to form the voice data of this node.

[0064] When all nodes are online, but there are multiple Mesh networks, the device needs to upload the current node voice data to the cloud. After the cloud receives the node information and the node voice data, it processes the node information and the node voice data, and determines whether there is cloud data voice. If there is cloud data voice, the node voice data is mixed with the cloud data voice and the mixed voice data is played; if there is no cloud data voice, the Mesh voice data is played directly to form the voice data of this node.

[0065] Figure 3 shows an example of fully online, fully mesh-internal communication within the same mesh network. After a Bluetooth device creates or joins a mesh network, it identifies the device. Multiple Bluetooth devices form a mesh network. As shown in the figure, devices device_1, device_2, device_3, device_4, and device_5 form mesh group mesh_group_id_1. Within mesh group mesh_group_id_1, devices device_1, device_2, device_3, device_4, and device_5 communicate using mesh mode. Devices device_1, device_2, device_3, device_4, and device_5 are each connected to an app, and communication between the devices and the app occurs via bidirectional heartbeat data. Apps communicate with the cloud via a data network using bidirectional heartbeat data. Multiple apps are connected to the same cloud. In addition, nodes are mapped on the cloud to form a virtual network, that is, devices device_1, device_2, device_3, device_4, device_5, and Mesh network mesh_group_id_1 are mapped to the cloud to form a virtual network.

[0066] Figure 4 shows an example of communication between devices in a mesh network when some devices are offline. After a Bluetooth device creates or joins a mesh network, it identifies the device and forms a mesh network. As shown in the figure, devices device_1, device_2, device_3, device_4, and device_5 form mesh group mesh_group_id_1. However, device_5 in mesh group mesh_group_id_1 is offline. Within mesh group mesh_group_id_1, all online devices (device_1, device_2, device_3, and device_4) communicate using mesh mode. The offline device device_5 communicates with mesh_group_id_1 and its online devices (device_1, device_2, device_3, and device_4) using data network mode. Online devices device_1, device_2, device_3, and device_4 also communicate with the app using the two-way heartbeat data mode. The app and the cloud communicate via the data network using this mode. Multiple apps can be added to the same cloud. Offline device device_5 also communicates with the app using the two-way heartbeat data mode. The virtual network mirrors the same situation: devices device_1, device_2, device_3, and device_4 are online, while device_5 is offline. Device status and information are synchronized.

[0067] Figure 5 shows an example of communication between devices in a mesh network when some devices leave the network. After a Bluetooth device creates or joins a mesh network, it identifies the device and forms a mesh network. As shown in the figure, devices device_1, device_2, device_3, device_4, and device_5 form mesh network mesh_group_id_1. However, device_5 in mesh network mesh_group_id_1 is offline. Within mesh network mesh_group_id_1, all online devices device_1, device_2, device_3, and device_4 communicate with each other using mesh mode. Online devices device_1, device_2, device_3, and device_4 also communicate with apps using bidirectional heartbeat data mode. Apps communicate with the cloud using bidirectional heartbeat data mode over a data network. Multiple apps are connected to the same cloud. The offline device device_5 also communicates with the app using bidirectional heartbeat data, but the app and the cloud are unable to communicate. In this case, device_5 is considered to have left the team. The virtual network maps the same situation: devices device_1, device_2, device_3, and device_4 are online, and device_5 has left the team. The device status and information are synchronized. Other online devices and the cloud no longer send information to the device that has left the team.

[0068] Figure 6 shows an example of how all devices communicate in different mesh networks, all online. After a Bluetooth device creates or joins a mesh network, it identifies the device and forms a mesh network. As shown in the figure, devices device_1, device_2, and device_3 form mesh network mesh_group_id_1, while devices device_4 and device_5 form mesh network mesh_group_id_2. Devices device_1, device_2, and device_3 within mesh_group_id_1 communicate using mesh mode. Devices device_4 and device_5 within mesh_group_id_2 communicate using mesh mode. Mesh_group_id_1 and mesh_group_id_2 are within the same network_group_id_1 and communicate using the data network. Devices device_1, device_2, device_3, device_4, and device_5 also communicate with apps using bidirectional heartbeat data. Apps communicate with the cloud using this data network. Multiple apps can be added to the same cloud, but they need to send voice data packets to the cloud simultaneously. Virtual networking maps this to a consistent situation: devices device_1, device_2, and device_3 form mesh group mesh_group_id_1, while devices device_4 and device_5 form mesh group mesh_group_id_2. Device status and information are synchronized.

[0069] Figure 7 shows how all devices communicate in different mesh networks when some devices are offline. After a Bluetooth device creates or joins a mesh network, it identifies the device and forms a mesh network. As shown in the figure, devices device_1, device_2, and device_3 form mesh network mesh_group_id_1, while devices device_4 and device_5 form mesh network mesh_group_id_2. All devices within mesh_group_id_1, device_2, and device_3, are online and communicate using mesh mode. Within mesh network mesh_group_id_2, device_4 is online and device_5 is offline, making communication impossible. Mesh_group_id_1 and mesh_group_id_2 are within the same network_group_id_1 and communicate using the data network. Devices device_1, device_2, device_3, device_4, and device_5 also communicate with apps using bidirectional heartbeat data. Apps communicate with the cloud using bidirectional heartbeat data over a data network. Multiple apps are added to the same cloud, but the apps need to send voice packets to the cloud simultaneously. Virtual networking maps this to a consistent situation: devices device_1, device_2, and device_3 form mesh group 1 (mesh_group_id_1). Devices device_4 and device_5 form mesh group 2 (mesh_group_id_2). Device device_5 in mesh group 2 is offline. Mesh group 1 and mesh group 2 are in the same network group 1, and device status and information are synchronized.

[0070] Figure 8 shows how all devices communicate in different mesh networks when some devices have left the network. After a Bluetooth device creates or joins a mesh network, it identifies the device and forms a mesh network. As shown in the figure, devices device_1, device_2, and device_3 form mesh group mesh_group_id_1, while devices device_4 and device_5 form mesh group mesh_group_id_2. All devices within mesh_group_id_1 are online and communicate using mesh mode. Devices device_4 and device_5 within mesh_group_id_2 are offline, and the entire mesh group mesh_group_id_2 is offline. Devices device_4 and device_5 can communicate with the app using two-way heartbeat data, but the heartbeat data between the app and the cloud is offline. In this case, devices device_4 and device_5 are considered to have left the network.

[0071] Figure 9 shows the same mesh network, fully online and communicating within the mesh. After a Bluetooth device creates or joins a mesh network, it identifies the device. Multiple Bluetooth devices form a mesh network. As shown in the figure, devices device_1, device_2, device_3, device_4, and device_5 form mesh group mesh_group_id_1. Device device_1 is the master node, device_4 is a listening node, and device_5 is a discarded node. Devices device_1, device_2, and device_3 are online and communicating in mesh mode. Device device_4 is a listening node and does not interact with data. Device device_5 is a discarded node and does not interact with data. Devices device_1, device_2, device_3, device_4, and device_5 also communicate with the app using a two-way heartbeat data mode. The app and the cloud communicate via a data network using this two-way heartbeat data mode. Multiple apps are added to the same cloud, but the app for device_5 is excluded and cannot communicate with the cloud. This mode controls communication with non-essential nodes and reduces unnecessary clutter in communications. For example, a voice communication sent by a communication node could prevent other receiving nodes from interpreting important information. Modes for Carrying Out the Invention

[0072] This automatic switching method between Mesh intercom and 5G data network intercom monitors the online status of the device in real time. When the device / node is offline, it automatically switches to the cloud network to transmit voice data, so as to ensure the normal voice data transmission and reception of the disconnected node, and to ensure the real-time and coherent integrity of the voice data transmission. The online nodes continue to use the Mesh network to transmit voice data, and use the cloud network transmission as a backup channel when the node is disconnected. The channel is enabled in time to ensure the stability and integrity of the voice data transmission. By uploading the device information and voice data to the cloud through the APP, the cloud forwards the voice data of each node according to the loss of connection of the Mesh network node, ensuring the normal transmission of voice data when the node is lost, and achieving the effect of all nodes being online and transmitting voice data uninterruptedly in real time.

[0073] The embodiments of the present application have been described above. The above description is illustrative and not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or improvements to the technology in the market, or to enable other persons skilled in the art to understand the embodiments disclosed herein.

Claims

1. A method for automatically switching between Mesh intercom and 5G data network intercom, characterized in that: include: S1: The Bluetooth device creates a Mesh network and performs Mesh networking. The Mesh network marks the device_id of all Bluetooth devices and the node information. Generate the group identifier mesh_group_id. The mesh_group_id of Bluetooth devices in the same Mesh network is the same. In step S2, one of the nodes serves as the master node, and an online group is created on the app through the master node. All Bluetooth devices join the online group through the app, report their node information to the cloud, and map the nodes on the cloud to form a virtual network. All Bluetooth devices in the cloud group have the same network_group_id; In S3, all Bluetooth devices communicate with the APP through a two-way dynamic heartbeat data mode, synchronizing the status of the Bluetooth devices with the virtual network formed by the cloud mapping nodes in real time, and synchronously marking the signal strength and online status of the Bluetooth devices; S4: In network communication, Mesh mode takes precedence over data network mode; voice data between online nodes is communicated via Mesh mode first; S5: The node of the Bluetooth device is offline, and the node device automatically switches to the data network mode through the APP, and uses the data network mode to communicate through the cloud; S6: When a device node is detected to be offline, the offline node information is reported and the voice data of the current node is uploaded. The cloud receives the voice data of the node, processes the node and voice data, and determines whether there is cloud data voice. If there is cloud data voice, the node voice data is mixed with the cloud data voice and then the voice data is played. If there is no data voice, the received node voice data is played directly. S7, when it is detected that the device node is offline and there are multiple Mesh networks, the current node voice data is uploaded, the cloud receives the node voice data, processes the node and voice data, and determines whether there is cloud data voice. If there is cloud data voice, the node voice data is mixed with the cloud data voice and then the voice data is played; if there is no data voice, the received node voice data is played directly.

2. The method for automatically switching between Mesh intercom and 5G data network intercom according to claim 1, characterized in that: In S2, all Bluetooth devices in the virtual network are in the same network_group_id, and the same Mesh node is assigned the same mesh_group_id in the cloud. The network_group_id is equivalent to the parent of the mesh_group_id in the cloud. Devices with the same network_group_id communicate through the cloud in data network mode.

3. The method for automatically switching between Mesh intercom and 5G data network intercom according to claim 1, characterized in that: In S3, after the cloud receives the data information, if it finds that a device Mesh is offline, it will send the offline device to all devices in the same network_group_id. At this time, when all devices send voice information, they need to send the Mesh voice data packet at the same time and send it to the cloud through the APP, and then the cloud will send it to the offline device.

4. The method for automatically switching between Mesh intercom and 5G data network intercom according to claim 3, characterized in that: In the case of offline nodes, if multiple nodes send voice at the same time, the cloud will mix the voice data and send the mixed voice data to the offline devices in the same network_group_id.

5. The method for automatically switching between Mesh intercom and 5G data network intercom according to claim 4, characterized in that: When there are offline nodes, all online Mesh devices receive voice data from the Mesh device and cloud voice data at the same time, and mix the voice data from the Mesh device and cloud voice data through the APP before playing them.

6. The method for automatically switching between Mesh intercom and 5G data network intercom according to claim 5, characterized in that: When a device Mesh node is offline and its remote heartbeat data is offline, the node is judged to be in a de-teamed state. For the de-teamed node, the cloud heartbeat data mode is used to inform the other online nodes. The de-teamed node is judged as non-existent and voice data does not need to be sent to the de-teamed node.

7. The method for automatically switching between Mesh intercom and 5G data network intercom according to claim 6, characterized in that: Offline Mesh reconnection, cloud heartbeat data automatically reconnects, and determines that the node is online.

8. The method for automatically switching between Mesh intercom and 5G data network intercom according to claim 1, characterized in that: In S4, S41, within the same mesh_group_id network, if the voice data does not contain the voice of the offline device, the device only plays the Mesh voice data; S42, within the same mesh_group_id network, Mesh online nodes transmit data through the Mesh network. If there is an offline device, the node sending voice data also sends the voice data through the APP; S43, within the same network_group_id, data between different mesh_group_ids is sent and received in the form of a cloud network.

9. The method for automatically switching between Mesh intercom and 5G data network intercom according to claim 1, characterized in that: The data nodes are marked with authority levels through the APP. The authority level of the master node is higher than that of ordinary nodes, and it has the highest authority to operate the network, allowing the master node to control the data communication of all Mesh nodes.

10. The method for automatically switching between Mesh intercom and 5G data network intercom according to claim 9, characterized in that: The master node sets whether to allow the addition of external device users; and sets the listening mode of the designated device, that is, only allowing the reception of voice data but not sending.

Images