CN111247819B - Device management method and BLE device - Google Patents

Device management method and BLE device Download PDF

Info

Publication number
CN111247819B
CN111247819B CN201980005134.3A CN201980005134A CN111247819B CN 111247819 B CN111247819 B CN 111247819B CN 201980005134 A CN201980005134 A CN 201980005134A CN 111247819 B CN111247819 B CN 111247819B
Authority
CN
China
Prior art keywords
client
server
information
signal strength
candidate
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201980005134.3A
Other languages
Chinese (zh)
Other versions
CN111247819A (en
Inventor
蒲川
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Goodix Technology Co Ltd
Original Assignee
Shenzhen Goodix Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Goodix Technology Co Ltd filed Critical Shenzhen Goodix Technology Co Ltd
Publication of CN111247819A publication Critical patent/CN111247819A/en
Application granted granted Critical
Publication of CN111247819B publication Critical patent/CN111247819B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application provides a device management method, which can still ensure the normal function of a server side controlled by a client side when the client side cannot continue to work. The method is applied to a MESH network, the MESH network comprises a plurality of clients, a first client in the MESH network is used for controlling a plurality of servers, and the method comprises the following steps: a second client in the MESH network receives first binding information sent by the first client, wherein the first binding information is binding information between a first server side and the first client in the plurality of server sides, and the signal strength between the first server side and the second client is larger than a preset value; when the second client determines that the first client cannot continuously control the first server, the binding information is used for replacing the first client to control the first server.

Description

Device management method and BLE device
Technical Field
Embodiments of the present application relate to the field of information technology, and more particularly, to a method for device management and a BLE device.
Background
Bluetooth low energy (Bluetooth Low Energy, BLE) MESH networks include a large number of nodes, which may be clients. The client may correspond to one or more server sides, and is configured to implement control over a corresponding server side and collect information of the server side. However, when a certain client cannot continue to operate due to equipment failure, power consumption and the like, information of a server controlled by the client cannot be collected, and the server also loses control, so that normal functions of the server are affected.
Disclosure of Invention
The embodiment of the application provides a method and equipment for equipment management, which can still ensure the normal function of a server side controlled by a client side when the client side cannot continue to work.
In a first aspect, a method for device management is provided, where the method is applied to a MESH network, the MESH network includes a plurality of clients, and a first client in the MESH network is used to control a plurality of servers, and the method includes: a second client in the MESH network receives first binding information sent by the first client, wherein the first binding information is binding information between a first server side and the first client in the plurality of server sides, and the signal strength between the first server side and the second client is larger than a preset value; when the second client determines that the first client cannot continuously control the first server, the binding information is used for replacing the first client to control the first server.
In one possible implementation, the first binding information includes at least one of the following information: the address of the first client, the service information of the first server, and the key information between the first client and the first server.
In one possible implementation manner, before the second client replaces the first client to control the first server, the method further includes: the second client detects a heartbeat packet of the first client; and if the second client does not detect the heartbeat packet of the first client within the preset time, determining to execute substitution of the first client.
In one possible implementation manner, before the second client replaces the first client to control the first server, the method further includes: the second client receives a replacement instruction sent by the first client, wherein the replacement instruction is used for indicating the second client to execute replacement of the first client.
In a possible implementation manner, the replacement instruction includes an address of the second client and an address of the first server.
In one possible implementation manner, before the second client replaces the first client to control the first server, the method further includes: the second client receives a candidate client list sent by the first client, wherein the candidate client list comprises corresponding relations between a plurality of server ends and a plurality of clients; and the second client determines the first server according to the candidate client list, wherein at least one client corresponding to the first server comprises the second client.
In one possible implementation, before the second client receives the candidate client list sent by the first client, the method further includes: the second client sends the signal strength between the second client and the first server to the first client, wherein the signal strength between the second client and the first server is used for the first client to generate the candidate client list.
In one possible implementation, before the second client sends the signal strength between the second client and the first server to the first client, the method further includes: the second client receives a shared information instruction sent by the first client, wherein the shared information instruction comprises an address of the first server; wherein the second client sends the signal strength between the second client and the first server to the first client, including: and the second client sends the signal strength between the second client and the first server to the first client according to the shared information instruction.
In a possible implementation manner, the signal strength between the second client and the first server is further used for the first client to determine the priority order of the second client in at least one client corresponding to the first server.
In one possible implementation manner, the second client is a client with the maximum signal strength between the at least one client corresponding to the first server and the first server.
In one possible implementation, the method further includes: the second client receives a recovery instruction sent by the first client; and the second client stops replacing the first client according to the recovery instruction.
In one possible implementation, the method further includes: the second client sends transmission information to the first client, wherein the transmission information comprises information transmitted between the second client and the first server during replacing the first client.
In a second aspect, there is provided a method of device management, the method being applied to a MESH network, the MESH network including a plurality of clients, a first client in the MESH network being configured to control a plurality of servers, the method comprising: the first client determines a second client, wherein the signal strength between the second client and a first server side in the plurality of server sides is larger than a preset value; the method comprises the steps that a first client sends first binding information to a second client, wherein the first binding information is binding information between a first server and the first client, and the first binding information is used for replacing the first client to control multiple first servers when the first client cannot continuously control the first server.
In one possible implementation, the first binding information includes at least one of the following information: the address of the first client, the service information of the first server, and the key information between the first client and the first server.
In one possible implementation, the method further includes: and when the first client cannot continuously control the first server, the first client sends a replacement instruction to the second client, wherein the replacement instruction is used for indicating the second client to execute replacement of the first client.
In a possible implementation manner, the replacement instruction includes an address of the second client and an address of the first server.
In one possible implementation, the method further includes: the first client generates a candidate client list, wherein the candidate client list comprises corresponding relations between a plurality of server sides and a plurality of clients, and at least one client corresponding to the first server side comprises the second client; wherein the first client determines a second client, comprising: and the first client determines the second client according to the candidate client list.
In one possible implementation, the first client generates a candidate client list, including: the first client receives the signal strength between the second client and the first server, which are sent by the second client; and under the condition that the signal strength between the second client and the first server is larger than the preset value, the first client adds the corresponding relation between the second client and the first server to the candidate client list.
In one possible implementation, before the first client receives the signal strength between the second client and the first server, the method further includes: the first client sends a sharing information instruction to the second client, wherein the sharing information instruction comprises an address of the first server, and the sharing information instruction is used for indicating the second client to report the signal intensity between the second client and the first server.
In one possible implementation manner, the first client adds the correspondence between the second client and the first server to the candidate client list, including: the first client determines the priority order of the second client in at least one client corresponding to the first server according to the signal strength between the second client and the first server; and the first client adds the corresponding relation between the second client and the first server to the candidate client list according to the priority order.
In one possible implementation manner, the second client is a client with the maximum signal strength between the at least one client corresponding to the first server and the first server.
In one possible implementation, the method further includes: the first client sends the candidate client list to the second client.
In one possible implementation, the method further includes: the first client sends a recovery instruction to the second client, wherein the recovery instruction is used for indicating the second client to stop replacing the first client.
In one possible implementation, the method further includes: the first client receives transmission information sent by the second client, wherein the transmission information comprises information transmitted between the second client and the first server during replacing the first client.
In a third aspect, a BLE device is provided comprising functional modules for performing the method of the first aspect or any possible implementation of the first aspect.
In a fourth aspect, there is provided a BLE device comprising functional modules for performing the method of the second aspect or any possible implementation of the second aspect.
In a fifth aspect, there is provided a BLE chip comprising a processor and a memory, the memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to perform the method of the first aspect or any possible implementation of the first aspect.
In a sixth aspect, there is provided a BLE chip comprising a processor and a memory, the memory being for storing a computer program, the processor being for invoking and running the computer program stored in the memory to perform the method of the second aspect or any possible implementation of the second aspect.
In a seventh aspect, a computer readable storage medium is provided for storing a computer program. Wherein the computer program, when executed by a processor, causes the processor to perform the method of the first aspect or any possible implementation of the first aspect.
In an eighth aspect, a computer readable storage medium is provided for storing a computer program. Wherein the computer program, when executed by a processor, causes the processor to perform the method of the second aspect or any possible implementation of the second aspect.
In a ninth aspect, a computer program product is provided comprising computer program instructions for causing a computer to perform the method of the first aspect or any of the possible implementations of the first aspect.
In a tenth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of the second aspect or any of the possible implementations of the second aspect.
Based on the technical scheme, when a first node in the MESH network needs to send a large number of data packets to a second node, each node in the network enters a first transmission mode by sending a switching instruction, namely only the data packets from the first node to the second node are forwarded, so that the transmission efficiency of the data packets between the two nodes can be improved.
Based on the technical scheme, when the signal strength between the second client and the first server side meets the condition, the first client selects the second client and sends the binding information between the second client and the first server side to the second client, so that when the first client cannot continuously control the first server side, the second client uses the binding information to replace the first client to control the first server side. Thus, when the first client cannot continue to work due to equipment failure, electric quantity exhaustion and the like, the normal function of the first server is still ensured.
Drawings
FIG. 1 is a schematic diagram of a MESH network.
Fig. 2 is a schematic diagram of a client side and a server side.
Fig. 3 is a flow chart interaction diagram of a method of device management according to an embodiment of the present application.
Fig. 4 is a flowchart of a method of generating a client list according to an embodiment of the present application.
Fig. 5 is a schematic diagram of a client being replaced.
Fig. 6 and 7 are schematic block diagrams of BLE devices of embodiments of the present application.
Fig. 8 is a schematic structural diagram of a BLE chip of an embodiment of the present application.
Detailed Description
The technical solutions in the present application will be described below with reference to the accompanying drawings.
In order to more clearly understand the scheme of the embodiment of the present application, the following first describes the MESH network in brief.
FIG. 1 is a schematic diagram of one possible MESH network according to embodiments of the present application. The MESH network includes a plurality of devices, each of which may be referred to as a node. Each node may transmit data. The data packet may be relayed between the nodes so that the data packet is transmitted to a location that is further away. In practice, these nodes may be distributed in manufacturing plants, offices, shopping malls, commercial parks, homes, and other environments. Any number of nodes may be included in the MESH network, with nodes a through G being taken as examples only in fig. 1.
The MESH network in the embodiment of the present application is composed of a plurality of clients (clients). Each client may correspond to one or more server sides (servers). For example, as shown in fig. 2, client a corresponds to server 1, client D corresponds to server 2, client F corresponds to server 3 and server 4, and client B corresponds to server 5. Each client controls the corresponding server and collects the information of the corresponding server.
In general, the information of the server side has high requirement on real-time performance, and the information must be managed and collected in real time, so that information interruption is not allowed. However, if a certain client in the MESH network fails to continue to operate due to equipment failure or power failure, the normal function of its corresponding server may be affected.
For example, if the client F cannot continue to operate, the server 3 and the server 4 lose control, and the information cannot be collected in time.
Therefore, the embodiment of the application provides a method for managing equipment, which can still ensure the normal function of a corresponding server side when the client side cannot continue to work.
It should be understood that in the embodiment of the present application, the MESH network is formed by clients, and each client needs to support BLE MESH protocol and conventional BLE protocol. And each server node is not located in the MESH network. Each client may communicate with its corresponding server node based on a conventional BLE protocol.
Fig. 3 is a flow chart interaction diagram of a method of device management according to an embodiment of the present application. The method is applied to the MESH network, and the MESH network comprises a plurality of clients. The method 300 is performed by a first client and a second client in the MESH network. The first client side is used for controlling the plurality of server sides. As shown in fig. 3, the method 300 includes some or all of the following steps.
In 310, the first client determines a second client.
The signal strength between the second client and the first server side of the plurality of server sides is larger than a preset value.
In 320, the first client sends first binding information to the second client.
The first binding information is binding information between the first server side and the first client side.
In 330, the second client receives the first binding information sent by the first client.
In 340, when the second client determines that the first client cannot continue to control the first server, the first binding information is used to replace the first client to control the first server.
In this embodiment, the first client selects the second client satisfying the condition that the signal strength between the first client and the first server is greater than the preset value. The first client sends first binding information between the first client and the first server to the selected second client, so that when the first client cannot continuously control the first server, the second client uses the first binding information to replace the first client to control the first server. Therefore, when the first client cannot continue to work due to equipment failure, electric quantity exhaustion and the like, the normal function of the first server can be ensured.
The first binding information may include, for example, at least one of the following information: the address of the first client, the service information of the first server, and the key information between the first client and the first server.
The service information includes, for example, information of a battery service (battery service), a binary sensor service (binary sensor service), a generic attribute specification (Generic Attribute Profile, GATT) service, or a generic access specification (Generic Access Profile, GAP) service.
The first binding information is used for communication with the first server. The second client needs to use the first binding information in the process of controlling the first server instead of the first client. For example, the second client establishes a connection with the first server using the address of the first client, communicates with the first server using the key information, and controls the first server accordingly using the service information of the first server. The first server side can actively initiate connection, and at the moment, after the second client side detects a connection instruction of the first server side, connection is established between the second client side and the first server side by using the address of the first client side; the second client can also actively operate the first server, and at this time, the second client establishes a connection with the first server by using the address of the first client, and sends a control instruction to the first server by using the key information.
The first client may control one or more server sides. For multiple server ends, when the first client end cannot continue to work, different client ends in the MESH network can be selected to replace the first client end. Such as client F shown in fig. 2, which controls server side 3 and server side 4. When the client F cannot continue to work, the client G can be selected to replace the client F to control the server 3; and selects the client B instead of the client F to control the server 4.
Alternatively, the first client may generate a candidate client list. The candidate client list includes correspondence between a plurality of servers and a plurality of clients. And at least one client corresponding to the first server comprises a second client.
That is, the candidate client list includes a plurality of servers controlled by the first client, and includes a client corresponding to each server. Only a client corresponding to a certain server can control the server instead of the first client.
For example, as shown in table one, the client F shown in fig. 2 controls the server side 3 and the server side 4 in normal operation. The client F builds its own list of candidate clients so that when it cannot continue to operate, it is replaced by other clients that control the server 3 and the server 4. As shown in table one, the server 3 corresponds to the client G and the client D, and the server 4 corresponds to the client B. Therefore, when the client F cannot continue to operate, it is possible that the client G and the client D replace the client F to control the server 3, and the client B replaces the client F to control the server 4.
List one
Figure BDA0002450883200000081
Table one is merely an example, and one server side in the candidate client list may correspond to one or more clients, and one client side may also correspond to one or more server sides. For example, as shown in table two, the client F shown in fig. 2 controls the server side 3 and the server side 4 in normal operation. The client F builds its own list of candidate clients so that when it cannot continue to operate, it is replaced by other clients that control the server 3 and the server 4. As shown in table two, the server 3 corresponds to the client G, the client D, and the client E, and the server 4 corresponds to the client B and the client E. Therefore, when the client F cannot continue to operate, one of the client G, the client D, and the client E controls the server 3 instead of the client F, and one of the client B and the client E controls the server 4 instead of the client F.
Watch II
Figure BDA0002450883200000091
The first client needs to consider the signal strength between each server and the different clients in the candidate client list when building the candidate client list. If the signal strength between a certain client and a server is smaller than a preset value, which indicates that the communication quality is poor, the client is not suitable to be used as a candidate client for controlling the server; if the signal strength between a certain client and a server is greater than a preset value, which indicates that the communication quality is better, the client can be used for controlling the server.
For example, the first client may establish a candidate client list in the manner shown in fig. 4. As shown in fig. 4, the method may include steps 410 through 430. In fig. 4, the second client is taken as an example, and other candidate clients perform similar operations, which are not described herein.
In 410, the second client sends the signal strength between the second client and the first server to the first client.
In 420, the first client receives the signal strength between the second client and the first server transmitted by the second client.
At 430, the first client generates the candidate client list based on the signal strength between the second client and the first server.
Under the condition that the signal strength between the second client and the first server is greater than the preset value, the first client adds the corresponding relation between the second client and the first server to the candidate client list.
If the signal strength between the second client and the first server is less than the preset value, the first client will not add the second client to the client list.
In 410, the second client may detect a signal strength between the second client and the first server based on the indication of the first client and send the signal strength to the first client; alternatively, the second client may actively detect the signal strength with the nearby servers and send the signal strength between the second client and the servers to the first client when joining the MESH network.
For example, the first client may send a sharing information instruction to the second client, where the sharing information instruction includes an address of the first server, and the sharing information instruction is used to instruct the second client to detect a signal strength between the second client and the first server. After the second client receives the shared information instruction, the signal strength between the second client and the first server is detected according to the shared information instruction. After receiving the shared information instruction, the second client may reply to the first client with a response message, where the response message may include the address of the first server and the signal strength.
For another example, the second client may actively detect the signal strength with the nearby server when joining the MESH network, and if it is detected that the signal strength between the second client and the first server is greater than the preset value, the signal strength between the second client and the first server may be sent to the nearby client.
Further, the signal strength between the second client and the first server may be further used for the first client to determine a priority order of the second client in at least one client corresponding to the first server.
Optionally, in 430, when the first client generates the candidate client list, the first client may determine, according to the signal strength between the second client and the first server, a priority order of the second client in at least one client corresponding to the first server; and adding the corresponding relation between the second client and the first server to the candidate client list according to the priority order.
Taking table one as an example for illustration, the client F receives the signal strengths between the server 4 and each of the other clients in the MESH network, and only the signal strength between the client B and the server 4 is greater than the preset value, so the client F takes the client B as the client corresponding to the server 4 and writes the client B into the candidate client list.
Similarly, the client F receives the signal strengths between the clients and the server 3 sent by other clients in the MESH network, and only the signal strengths between the client G and the client D and the server 3 are greater than a preset value, so that the client F takes the client G and the client D as clients corresponding to the server 3 and writes the client G and the client D into the candidate client list. The signal strength between the client G and the server 3 is greater than the signal strength between the client D and the server 3. Therefore, the priority of the client G is higher than that of the client D, and the first client may add the priority information of each candidate client to the candidate client list.
Optionally, in 310, the first client determines the second client, and may select a client corresponding to the first server according to the candidate client list. For example, the second client may be the client with the highest priority among the at least one client corresponding to the first server, that is, the second client is the client with the highest signal strength between the at least one client corresponding to the first server and the first server. Thus, the first client selects the second client to control the first server instead of itself.
When the first client stops working, the second client replaces the first client to control the first server. The first server side can still realize the normal functions under the control of the second client side. For example, as shown in fig. 5, when the client F stops operating, the client G may control the server 3 instead of the client F, and the client B may control the server 4 instead of the client F.
It should be appreciated that the first client may also select the second client in other ways. For example, the first client randomly selects the second client among at least one client corresponding to the first server based on the candidate client list. For another example, the first client selects the second client having a lower workload or being idle, taking into consideration the workload of at least one client corresponding to the first server. For example, when the second client does not replace other clients, the first client may select the second client to replace the first client, although the second client has a lower priority, if there are fewer servers that need to be responsible for management.
There are two situations. In one case, when the first client cannot continue to control the first server, the first client may send a replacement instruction to the selected second client. Wherein the replacement instruction is for instructing the second client to perform a replacement for the first client. For example, the first client sends the replacement instruction to the second client when the power is less than 5%.
In another case, the first client may not send the replacement instruction to the second client in the event of an emergency, such as a device failure or a power outage. Therefore, it is desirable that the second client can determine the state of the first client by itself. For example, the second client may detect a heartbeat packet sent by the first client; and if the second client does not detect the heartbeat packet of the first client within the preset time, determining to execute the substitution of the first client.
Whether or not a replacement instruction is sent, the second client needs to know which server side it controls to replace the first client when judging that the first client needs to be replaced.
In one implementation, the replacement instruction includes an address of the second client and an address of the first server.
That is, the first client carries therein the addresses of those server sides that need to be controlled by the second client when sending the replacement instruction to the second client. The second client receives the replacement instruction sent by the first client, and the second client replaces the first client to control the first server because the replacement instruction comprises the address of the first server.
After the second client receives the substitution instruction, the corresponding relation between the second client and the first server contained in the substitution instruction is resolved. If the address of the second client is included, determining to control the first server instead of the first client; if the address of the second client is not included, the current state is maintained unchanged.
In another implementation, the replacement instruction is used only to instruct the second client to perform a replacement for the first client. The second client, instead of the first client, controls which server side may be determined by the second client itself from the candidate client list.
Optionally, as shown in fig. 4, the method may further include 440 and 450.
At 440, the first client sends the candidate client list to the second client.
At 450, the second client receives the list of candidate clients sent by the first client.
Thus, the second client can determine the first server according to the candidate client list. And the at least one client corresponding to the first server side in the candidate client list comprises a second client.
That is, if the address of the server side is carried in the replacement instruction, the second client performs the replacement of the first client according to the replacement instruction. If the address of the server terminal is not carried in the replacement instruction, the second client terminal selects the server terminal controlled by the second client terminal from the candidate client terminal list.
If a certain high priority client has already controlled the first server in place of the first client, a notification instruction may be sent in the MESH network to notify the other clients. And the second client determines the first server according to the candidate client list, detects the notification instruction, and if the replacement instruction is not detected, indicates that other clients with higher priority do not execute replacement, and the second client replaces the first client to control the first server.
The candidate client list may be updated, for example, periodically, when a new node joins the MESH network, or when the signal strength between the server and client changes. The specific updating process is similar to the process of adding the second client to the candidate client list, and for brevity, will not be described again here.
When the first client resumes operation, optionally, a resume instruction may be sent to the second client, the resume instruction being for instructing the second client to stop the replacement of the first client.
Correspondingly, the second client receives a recovery instruction sent by the first client; and stopping the substitution of the first client according to the recovery instruction.
Further optionally, the second client also sends the transmission information to the first client. Wherein the transmission information comprises information transmitted between the second client and the first server during the replacement of the first client.
The first client receives and stores the transmission information, and then continues to control the first server.
It should be understood that when the second client replaces the first client to control the first server, the original work of the second client will not be stopped, and the second client will still manage the server that is controlled by the second client. For example, as shown in fig. 5, after the client B controls the server side 4 instead of the client F, the original server side 5 still needs to be controlled.
In the embodiment of the present application, the sequence number of each process does not mean the sequence of execution sequence, and the execution sequence of each process should be determined by the function and the internal logic of each process, and should not constitute any limitation on the implementation process of the embodiment of the present application.
On the premise of no conflict, various embodiments described in the present application and/or technical features in various embodiments may be combined with each other arbitrarily, and a technical solution obtained after combination should also fall into the protection scope of the present application.
Having described the method of device management in detail according to embodiments of the present application, the apparatus according to embodiments of the present application will be described below with reference to fig. 6 to 8, and technical features described in the method embodiments are applicable to the following apparatus embodiments.
Figure 6 is a schematic block diagram of a BLE device 600 according to an embodiment of the present application. As shown in fig. 6, BLE device 600 is a second client in a MESH network of BLE, where the MESH network includes a plurality of clients, and the first client is configured to control a plurality of servers, and the second client includes:
a transceiver unit 610, configured to receive first binding information sent by the first client, where the first binding information is binding information between a first server side and the first client in the plurality of server sides, and a signal strength between the first server side and the second client is greater than a preset value;
And a processing unit 620, configured to use the binding information to replace the first client to control the first server when it is determined that the first client cannot continue to control the first server.
Therefore, after the second client obtains the binding information between the first client and the first server, the second client can use the binding information to replace the first client to control the first server when the first client cannot continuously control the first server. Therefore, when the first client cannot continue to work due to equipment failure, electric quantity exhaustion and the like, the normal function of the first server is ensured.
Optionally, the first binding information includes at least one of the following information: the address of the first client, the service information of the first server, and the key information between the first client and the first server.
Optionally, the processing unit 620 is further configured to: detecting a heartbeat packet of the first client; and if the heartbeat packet of the first client is not detected within the preset time, determining to execute substitution of the first client.
Optionally, the transceiver unit 610 is further configured to: and receiving a replacement instruction sent by the first client, wherein the replacement instruction is used for instructing the second client to execute replacement of the first client.
Optionally, the replacement instruction includes an address of the second client and an address of the first server.
Optionally, the transceiver unit 610 is further configured to: receiving a candidate client list sent by the first client, wherein the candidate client list comprises corresponding relations between a plurality of servers and a plurality of clients; the processing unit 620 is further configured to: and determining the first server according to the candidate client list, wherein at least one client corresponding to the first server comprises the second client.
Optionally, the transceiver unit 610 is further configured to: and sending the signal strength between the second client and the first server to the first client, wherein the signal strength between the second client and the first server is used for the first client to generate the candidate client list.
Optionally, the transceiver unit 610 is specifically configured to: receiving a shared information instruction sent by the first client, wherein the shared information instruction comprises an address of the first server; and sending the signal strength between the second client and the first server to the first client according to the information sharing instruction.
Optionally, the signal strength between the second client and the first server is further used for the first client to determine a priority order of the second client in at least one client corresponding to the first server.
Optionally, the second client is a client with the maximum signal strength between the second client and the first server in at least one client corresponding to the first server.
Optionally, the transceiver unit 610 is further configured to: receiving a recovery instruction sent by the first client; the processing unit 620 is further configured to: and stopping replacing the first client according to the recovery instruction.
Optionally, the transceiver unit 610 is further configured to: and sending transmission information to the first client, wherein the transmission information comprises information transmitted between the second client and the first server during replacing the first client.
It should be understood that BLE device 600 may perform the corresponding operations performed by the second client in the above-described method embodiments, and are not described herein for brevity.
Figure 7 is a schematic block diagram of a BLE device 700 according to an embodiment of the present application. As shown in fig. 7, the BLE device is a first client in a MESH network of BLE, where the MESH network includes a plurality of clients, and the first client in the MESH network is configured to control a plurality of servers, and the BLE device includes:
A processing unit 710, configured to determine a second client in the MESH, where a signal strength between the second client and a first server in the plurality of servers is greater than a preset value;
the transceiver unit 720 is configured to send first binding information to a second client, where the first binding information is binding information between the first server and the first client, and the first binding information is used for controlling the multiple first servers instead of the first client when the first client cannot continuously control the first server.
Therefore, when the signal strength between the second client and the first server meets the condition, the first client selects the second client and sends the binding information between the second client and the first server to the second client, so that when the first client cannot continuously control the first server, the second client uses the binding information to replace the first client to control the first server. Thus, when the first client cannot continue to work due to equipment failure, electric quantity exhaustion and the like, the normal function of the first server controlled by the first client is ensured.
Optionally, the first binding information includes at least one of the following information: the address of the first client, the service information of the first server, and the key information between the first client and the first server.
Optionally, the transceiver unit 720 is further configured to: and when the first client cannot continuously control the first server, sending a replacement instruction to the second client, wherein the replacement instruction is used for indicating the second client to execute replacement of the first client.
Optionally, the replacement instruction includes an address of the second client and an address of the first server.
Optionally, the processing unit 710 is specifically configured to: generating a candidate client list, wherein the candidate client list comprises corresponding relations between a plurality of servers and a plurality of clients, and at least one client corresponding to the first server comprises the second client; and determining the second client according to the candidate client list.
Optionally, the processing unit 710 is specifically configured to: controlling the transceiver unit 720 to receive the signal strength between the second client and the first server, which are sent by the second client; and under the condition that the signal strength between the second client and the first server is larger than the preset value, the first client adds the corresponding relation between the second client and the first server to the candidate client list.
Optionally, the transceiver unit 720 is specifically configured to: and sending a sharing information instruction to the second client, wherein the sharing information instruction comprises an address of the first server, and the sharing information instruction is used for indicating the second client to report the signal strength between the second client and the first server.
Optionally, the processing unit 710 is specifically configured to: determining the priority order of the second client in at least one client corresponding to the first server according to the signal strength between the second client and the first server; and adding the corresponding relation between the second client and the first server to the candidate client list according to the priority order.
Optionally, the second client is a client with the maximum signal strength between the second client and the first server in at least one client corresponding to the first server.
Optionally, the transceiver unit 720 is further configured to: and sending the candidate client list to the second client.
Optionally, the transceiver unit 720 is further configured to: and sending a recovery instruction to the second client, wherein the recovery instruction is used for instructing the second client to stop replacing the first client.
Optionally, the transceiver unit 720 is further configured to: and receiving transmission information sent by the second client, wherein the transmission information comprises information transmitted between the second client and the first server during the replacement of the first client.
It should be understood that BLE device 700 may perform the corresponding operations performed by the first client in the above-described method embodiments, and are not described herein for brevity.
Fig. 8 is a schematic block diagram of a BLE chip 800 according to an embodiment of the present application. The BLE chip 800 shown in fig. 8 includes a processor 810, a memory 820, and a transceiver 830.
Wherein the processor 810 may call and run a computer program from the memory 820 to implement the methods in embodiments of the present application. The processor 810 may control communication between the transceiver 830 and other BLE devices or BLE chips, in particular, may send data to other BLE devices or BLE chips, or receive information or data sent by other BLE devices or BLE chips.
Transceiver 830 may include an input interface 831 and an output interface 832. The processor 810 may control communication between the input interface 831 and the output interface 832 and other BLE devices or BLE chips to obtain information or data sent by the other BLE devices or BLE chips, or to output information or data to the other BLE devices or BLE chips.
Optionally, the BLE chip 800 may be specifically a first client in the embodiment of the present application, and the BLE chip 800 may implement a corresponding flow implemented by the first client in each method in the embodiment of the present application, which is not described herein for brevity.
Optionally, the BLE chip 800 may specifically be the second client in the embodiment of the present application, and the BLE chip 800 may implement a corresponding flow implemented by the second client in each method in the embodiment of the present application, which is not described herein for brevity.
The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
The memory described above may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM).
Embodiments of the present application also provide a computer-readable storage medium for storing a computer program. The computer readable storage medium may be applied to a BLE device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the first client or the second client in each method in the embodiments of the present application, which is not described in detail for brevity.
Embodiments of the present application also provide a computer program product comprising computer program instructions. The computer program product may be applied to a BLE device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding flow implemented by the first client or the second client in each method in the embodiments of the present application, which is not described herein for brevity.
The terms "system" and "network" in embodiments of the invention are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
In the embodiment of the present invention, "B corresponding to (corresponding to) a" means that B is associated with a, from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The specific examples in the embodiments of the present application are intended to help those skilled in the art to better understand the embodiments of the present application, and not to limit the scope of the embodiments of the present application, and those skilled in the art may make various modifications and variations on the basis of the above embodiments, and these modifications or variations fall within the scope of protection of the present application.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (52)

1. A method for device management, wherein the method is applied to a MESH network of bluetooth low energy, the MESH network includes a plurality of clients, and a first client in the MESH network is used for controlling a plurality of servers, the method includes:
a second client in the MESH network receives first binding information sent by the first client, wherein the first binding information is binding information between a first server side and the first client in the plurality of server sides, and the signal strength between the second client and the first server side is larger than a preset value;
when the second client determines that the first client cannot continuously control the first server, the binding information is used for replacing the first client to control the first server.
2. The method of claim 1, wherein the first binding information comprises at least one of:
the address of the first client, the service information of the first server, and the key information between the first client and the first server.
3. The method according to claim 1 or 2, wherein before the second client takes control of the first server side instead of the first client, the method further comprises:
The second client detects a heartbeat packet of the first client;
and if the second client does not detect the heartbeat packet of the first client within the preset time, determining to execute substitution of the first client.
4. The method according to claim 1 or 2, wherein before the second client takes control of the first server side instead of the first client, the method further comprises:
the second client receives a replacement instruction sent by the first client, wherein the replacement instruction is used for indicating the second client to execute replacement of the first client.
5. The method of claim 4, wherein the replacement instruction includes an address of the second client and an address of the first server.
6. The method according to claim 1 or 2, wherein before the second client takes control of the first server side instead of the first client, the method further comprises:
the second client receives a candidate client list sent by the first client, wherein the candidate client list comprises corresponding relations between a plurality of server ends and a plurality of clients;
And the second client determines the first server according to the candidate client list, wherein at least one client corresponding to the first server comprises the second client.
7. The method of claim 6, wherein prior to the second client receiving the list of candidate clients sent by the first client, the method further comprises:
the second client sends the signal strength between the second client and the first server to the first client, wherein the signal strength between the second client and the first server is used for the first client to generate the candidate client list.
8. The method of claim 7, wherein before the second client sends the signal strength between the second client and the first server to the first client, the method further comprises:
the second client receives a shared information instruction sent by the first client, wherein the shared information instruction comprises an address of the first server;
wherein the second client sends the signal strength between the second client and the first server to the first client, including:
And the second client sends the signal strength between the second client and the first server to the first client according to the shared information instruction.
9. The method of claim 8, wherein the signal strength between the second client and the first server is further used by the first client to determine a priority order of the second client in at least one client corresponding to the first server.
10. The method of claim 9, wherein the second client is a client with a maximum signal strength between the at least one client corresponding to the first server and the first server.
11. The method according to claim 1 or 2, characterized in that the method further comprises:
the second client receives a recovery instruction sent by the first client;
and the second client stops replacing the first client according to the recovery instruction.
12. The method of claim 11, wherein the method further comprises:
the second client sends transmission information to the first client, wherein the transmission information comprises information transmitted between the second client and the first server during replacing the first client.
13. A method for device management, wherein the method is applied to a MESH network of bluetooth low energy, the MESH network includes a plurality of clients, and a first client in the MESH network is used for controlling a plurality of servers, the method includes:
the first client determines a second client in the MESH network, wherein the signal strength between the second client and a first server in the plurality of servers is larger than a preset value;
the method comprises the steps that a first client sends first binding information to a second client, wherein the first binding information is binding information between a first server and the first client, and the first binding information is used for replacing the first client to control the first server when the first client cannot continuously control the first server.
14. The method of claim 13, wherein the first binding information comprises at least one of:
the address of the first client, the service information of the first server, and the key information between the first client and the first server.
15. The method according to claim 13 or 14, characterized in that the method further comprises:
and when the first client cannot continuously control the first server, the first client sends a replacement instruction to the second client, wherein the replacement instruction is used for indicating the second client to execute replacement of the first client.
16. The method of claim 15, wherein the replacement instruction includes an address of the second client and an address of the first server.
17. The method according to claim 13 or 14, characterized in that the method further comprises:
the first client generates a candidate client list, wherein the candidate client list comprises corresponding relations between a plurality of server sides and a plurality of clients, and at least one client corresponding to the first server side comprises the second client;
wherein the first client determines a second client, comprising:
and the first client determines the second client according to the candidate client list.
18. The method of claim 17, wherein the first client generating a candidate client list comprises:
The first client receives the signal strength between the second client and the first server, which are sent by the second client;
and under the condition that the signal strength between the second client and the first server is larger than the preset value, the first client adds the corresponding relation between the second client and the first server to the candidate client list.
19. The method of claim 18, wherein before the first client receives the signal strength between the second client and the first server transmitted by the second client, the method further comprises:
the first client sends a sharing information instruction to the second client, wherein the sharing information instruction comprises an address of the first server, and the sharing information instruction is used for indicating the second client to report the signal intensity between the second client and the first server.
20. The method of claim 17, wherein the first client adding the correspondence between the second client and the first server to the candidate client list comprises:
The first client determines the priority order of the second client in at least one client corresponding to the first server according to the signal strength between the second client and the first server;
and the first client adds the corresponding relation between the second client and the first server to the candidate client list according to the priority order.
21. The method of claim 20, wherein the second client is a client with a maximum signal strength between the at least one client corresponding to the first server and the first server.
22. The method of claim 17, wherein the method further comprises:
the first client sends the candidate client list to the second client.
23. The method according to claim 13 or 14, characterized in that the method further comprises:
the first client sends a recovery instruction to the second client, wherein the recovery instruction is used for indicating the second client to stop replacing the first client.
24. The method of claim 23, wherein the method further comprises:
The first client receives transmission information sent by the second client, wherein the transmission information comprises information transmitted between the second client and the first server during replacing the first client.
25. A bluetooth low energy BLE device, wherein the BLE device is a second client in a MESH network of BLE, the MESH network including a plurality of clients, a first client in the MESH network being configured to control a plurality of server sides, the BLE device comprising:
the receiving and transmitting unit is used for receiving first binding information sent by the first client, wherein the first binding information is binding information between a first server side and the first client in the plurality of server sides, and the signal strength between the first server side and the second client is larger than a preset value;
and the processing unit is used for replacing the first client to control the first server by using the binding information when the first client cannot continuously control the first server.
26. The BLE device of claim 25, wherein the first binding information comprises at least one of:
The address of the first client, the service information of the first server, and the key information between the first client and the first server.
27. The BLE device according to claim 25 or 26, wherein the processing unit is further configured to:
detecting a heartbeat packet of the first client;
and if the heartbeat packet of the first client is not detected within the preset time, determining to execute substitution of the first client.
28. The BLE device according to claim 25 or 26, wherein the transceiving unit is further configured to:
and receiving a replacement instruction sent by the first client, wherein the replacement instruction is used for instructing the second client to execute replacement of the first client.
29. The BLE device of claim 28, wherein the replacement instruction includes an address of the second client and an address of the first server.
30. The BLE device according to claim 25 or 26, wherein,
the transceiver unit is further configured to: receiving a candidate client list sent by the first client, wherein the candidate client list comprises corresponding relations between a plurality of servers and a plurality of clients;
The processing unit is further configured to: and determining the first server according to the candidate client list, wherein at least one client corresponding to the first server comprises the second client.
31. The BLE device of claim 30, wherein the transceiving unit is further to:
and sending the signal strength between the second client and the first server to the first client, wherein the signal strength between the second client and the first server is used for the first client to generate the candidate client list.
32. The BLE device according to claim 31, wherein the transceiving unit is specifically configured to:
receiving a shared information instruction sent by the first client, wherein the shared information instruction comprises an address of the first server;
and sending the signal strength between the second client and the first server to the first client according to the information sharing instruction.
33. The BLE device of claim 32, wherein the signal strength between the second client and the first server is further configured to determine, by the first client, a priority order of the second client in at least one client corresponding to the first server.
34. The BLE device of claim 33, wherein the second client is a client with a maximum signal strength between the at least one client corresponding to the first server and the first server.
35. The BLE device according to claim 25 or 26, wherein,
the transceiver unit is further configured to: receiving a recovery instruction sent by the first client;
the processing unit is further configured to: and stopping replacing the first client according to the recovery instruction.
36. The BLE device of claim 35, wherein the transceiving unit is further to:
and sending transmission information to the first client, wherein the transmission information comprises information transmitted between the second client and the first server during replacing the first client.
37. A bluetooth low energy BLE device, wherein the BLE device is a first client in a MESH network of BLE, the MESH network including a plurality of clients, the first client being configured to control a plurality of server sides, the BLE device comprising:
the processing unit is used for determining a second client in the MESH, wherein the signal strength between the second client and a first server in the plurality of server ends is larger than a preset value;
The receiving and transmitting unit is used for sending first binding information to the second client, wherein the first binding information is binding information between the first server and the first client, and the first binding information is used for replacing the first client to control the first server when the first client cannot continuously control the first server.
38. The BLE device of claim 37, wherein the first binding information comprises at least one of:
the address of the first client, the service information of the first server, and the key information between the first client and the first server.
39. The BLE device according to claim 37 or 38, wherein the transceiving unit is further configured to:
and when the first client cannot continuously control the first server, sending a replacement instruction to the second client, wherein the replacement instruction is used for indicating the second client to execute replacement of the first client.
40. The BLE device of claim 39, wherein the replacement instruction includes an address of the second client and an address of the first server.
41. BLE device according to claim 37 or 38, wherein the processing unit is specifically configured to:
generating a candidate client list, wherein the candidate client list comprises corresponding relations between a plurality of servers and a plurality of clients, and at least one client corresponding to the first server comprises the second client;
and determining the second client according to the candidate client list.
42. BLE device according to claim 41, wherein the processing unit is specifically configured to:
controlling the receiving and transmitting unit to receive the signal intensity between the second client and the first server, which are sent by the second client;
and under the condition that the signal strength between the second client and the first server is larger than the preset value, the first client adds the corresponding relation between the second client and the first server to the candidate client list.
43. The BLE device according to claim 42, wherein the transceiving unit is specifically configured to:
and sending a sharing information instruction to the second client, wherein the sharing information instruction comprises an address of the first server, and the sharing information instruction is used for indicating the second client to report the signal strength between the second client and the first server.
44. BLE device according to claim 41, wherein the processing unit is specifically configured to:
determining the priority order of the second client in at least one client corresponding to the first server according to the signal strength between the second client and the first server;
and adding the corresponding relation between the second client and the first server to the candidate client list according to the priority order.
45. The BLE device of claim 44, wherein the second client is a client with a maximum signal strength between the at least one client corresponding to the first server and the first server.
46. The BLE device of claim 41, wherein the transceiving unit is further to:
and sending the candidate client list to the second client.
47. The BLE device according to claim 37 or 38, wherein the transceiving unit is further configured to:
and sending a recovery instruction to the second client, wherein the recovery instruction is used for instructing the second client to stop replacing the first client.
48. The BLE device of claim 47, wherein the transceiving unit is further to:
And receiving transmission information sent by the second client, wherein the transmission information comprises information transmitted between the second client and the first server during the replacement of the first client.
49. A bluetooth low energy BLE chip comprising a processor and a memory, the memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to perform the method of any of claims 1 to 12.
50. A bluetooth low energy BLE chip comprising a processor and a memory, the memory for storing a computer program, the processor for invoking and running the computer program stored in the memory to perform the method of any of claims 13 to 24.
51. A computer readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, causes the processor to perform the method of any one of claims 1 to 12.
52. A computer readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, causes the processor to perform the method of any one of claims 13 to 24.
CN201980005134.3A 2019-11-11 2019-11-11 Device management method and BLE device Active CN111247819B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/117122 WO2021092724A1 (en) 2019-11-11 2019-11-11 Device management method and ble device

Publications (2)

Publication Number Publication Date
CN111247819A CN111247819A (en) 2020-06-05
CN111247819B true CN111247819B (en) 2023-05-02

Family

ID=70873800

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201980005134.3A Active CN111247819B (en) 2019-11-11 2019-11-11 Device management method and BLE device

Country Status (2)

Country Link
CN (1) CN111247819B (en)
WO (1) WO2021092724A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110177362A (en) * 2019-05-24 2019-08-27 广东美的制冷设备有限公司 Apparatus bound method, apparatus and electronic equipment

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104348524B (en) * 2013-07-26 2017-07-07 施耐德电气（澳大利亚）有限公司 A kind of binding method, central apparatus and ancillary equipment
CN104158946B (en) * 2014-07-21 2016-08-17 小米科技有限责任公司 A kind of method and device controlling terminal
US10111071B2 (en) * 2014-09-19 2018-10-23 Avago Technologies General Ip (Singapore) Pte. Ltd. Bluetooth low energy automation mesh network
US9924021B2 (en) * 2016-03-11 2018-03-20 Distech Controls Inc. Environment controllers capable of controlling a plurality of smart light fixtures
US9894512B2 (en) * 2016-04-27 2018-02-13 Texas Instruments Incorporated Mode-speed switching for exploiting high-speed in BLE-Mesh systems
KR102331886B1 (en) * 2017-12-21 2021-11-29 삼성전자주식회사 Electronic device contrrolling node in a network and control method thereof
CN108183827A (en) * 2017-12-29 2018-06-19 江苏惠通集团有限责任公司 Configuration method and startup configuration equipment based on low-power consumption bluetooth mesh network

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110177362A (en) * 2019-05-24 2019-08-27 广东美的制冷设备有限公司 Apparatus bound method, apparatus and electronic equipment

Also Published As

Publication number Publication date
WO2021092724A1 (en) 2021-05-20
CN111247819A (en) 2020-06-05

Similar Documents

Publication Publication Date Title
RU2639688C2 (en) Control method of mediators table in the wireless network, using the device-mediators
KR102392120B1 (en) Processing method, device and system for nf component abnormality
US10051561B2 (en) Methods and nodes for M2M communication
CN109040295B (en) Method and device for determining abnormal disconnection, terminal and storage medium
CN112448877A (en) SBFD session establishment method, device and system
CN110771097B (en) Connectivity monitoring for data tunneling between network device and application server
CN105530115A (en) Method and device for realizing operation management and maintenance function
CN106411574B (en) Management control method and device
CN110809262A (en) Internet of things equipment operation and maintenance management method based on COAP protocol
CN112671813A (en) Server determination method, device, equipment and storage medium
JP2006222659A (en) Radio communication device, system and method
WO2015139633A1 (en) Data transmission method and apparatus
CN111247819B (en) Device management method and BLE device
CN113595894B (en) Communication method, device, equipment and medium between service nodes and client nodes
US20210328887A1 (en) Method for performing task processing on common service entity, common service entity, apparatus and medium for task processing
WO2017000478A1 (en) Method and device for transmitting service data with microwave link
JP6176247B2 (en) Communication maintenance system, terminal device, communication maintenance method, and connection maintenance program
CN106304241B (en) Data transmission method, repeater and gateway
CN111869246B (en) Message transmission method, BLE equipment and BLE chip
CN107113311B (en) Method and apparatus for communication in a unified machine-to-machine system
CN111698784A (en) Data transmission method, device, equipment and storage medium
CN107465751B (en) Communication method, device, client and computer storage medium
JP2006270150A (en) Address management node of wireless communication network and node of wireless communication network
JP7118307B1 (en) Communication system, communication control device, communication control method and program
EP2028893A1 (en) Proxy network element and method of performance management in a network

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant