Nothing Special   »   [go: up one dir, main page]

CN116491222A - Connection establishment method, device, equipment and storage medium - Google Patents

Connection establishment method, device, equipment and storage medium Download PDF

Info

Publication number
CN116491222A
CN116491222A CN202080107383.6A CN202080107383A CN116491222A CN 116491222 A CN116491222 A CN 116491222A CN 202080107383 A CN202080107383 A CN 202080107383A CN 116491222 A CN116491222 A CN 116491222A
Authority
CN
China
Prior art keywords
identifier
ble mesh
endpoint
chip
chip virtual
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.)
Pending
Application number
CN202080107383.6A
Other languages
Chinese (zh)
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.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp 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 Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN116491222A publication Critical patent/CN116491222A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Landscapes

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

Abstract

The application discloses a connection establishment method, a device, equipment and a storage medium, and relates to the technical field of Internet of things. The method comprises the following steps: based on the connection between the bridging device and the BLE Mesh device, a CHIP virtual device is created, and a mapping relation between the BLE Mesh device and the CHIP virtual device is established; and establishing the connection between the CHIP virtual device and the terminal device, so that the BLE Mesh device can be ensured to be accessed into the CHIP network, the terminal device and the BLE Mesh device can communicate by adopting a CHIP protocol, and the mode of controlling the BLE Mesh device is expanded.

Description

Connection establishment method, device, equipment and storage medium Technical Field
The present disclosure relates to the field of internet of things, and in particular, to a connection establishment method, device, apparatus, and storage medium.
Background
Along with the rapid development of the internet of things technology, various internet of things devices can access to a network, and further terminal devices can control the internet of things devices through the network.
The internet of things device comprises a Zigbee (Zigbee) device and a Z-Wave (wireless network protocol) device, the Zigbee device adopts a Zigbee protocol, the Z-Wave device adopts a Z-Wave protocol, and the terminal device adopts a CHIP (ConnectedHomeoverInternet ProtocolWorking Group, and the home workgroup is connected through an internet protocol under the Zigbee alliance) protocol. Therefore, the terminal device adopting the CHIP protocol needs to establish a connection with the Zigbee device or the Z-Wave device through the bridge device, so as to perform protocol conversion through the bridge device, and access the Zigbee device or the Z-Wave device into the CHIP protocol, so that communication between the terminal device and the Zigbee device or the Z-Wave device is performed on the basis of the CHIP protocol.
However, since the internet of things device further includes a bluetooth low energy mesh device, how to establish a connection between a terminal device adopting the CHIP protocol and the bluetooth device becomes a problem to be solved.
Disclosure of Invention
The embodiment of the application provides a connection establishment method, a device, equipment and a storage medium, wherein terminal equipment and BLE Mesh equipment communicate by adopting a CHIP protocol, and a mode of controlling the BLE Mesh equipment is expanded. The technical scheme is as follows:
according to an aspect of the present application, there is provided a connection establishment method applied to a bridging device, the method including:
based on the connection between the bridging device and the BLE Mesh device, a CHIP virtual device is created, and a mapping relation between the BLE Mesh device and the CHIP virtual device is established;
establishing connection between the CHIP virtual equipment and terminal equipment;
the CHIP virtual device and the terminal device adopt a CHIP protocol, and the BLE Mesh device and the terminal device are used for communication based on a mapping relationship between the BLE Mesh device and the CHIP virtual device and connection between the CHIP virtual device and the terminal device.
According to an aspect of the present application, there is provided a connection establishment apparatus applied to a bridging device, the apparatus comprising:
a relation establishing module, configured to establish a CHIP virtual device based on the connection between the bridge device and the BLE Mesh device, and establish a mapping relation between the BLE Mesh device and the CHIP virtual device;
a connection establishment module, configured to establish a connection between the CHIP virtual device and a terminal device;
the CHIP virtual device and the terminal device adopt a CHIP protocol, and the BLE Mesh device and the terminal device are used for communication based on a mapping relationship between the BLE Mesh device and the CHIP virtual device and connection between the CHIP virtual device and the terminal device.
According to an aspect of the present application, there is provided a bridging device, the terminal device including: a processor; a transceiver coupled to the processor; a memory for storing executable program code for the processor; wherein the processor is configured to load and execute the executable program code to implement the connection establishment method as described in the above aspect.
According to an aspect of the present application, there is provided a computer readable storage medium having stored therein executable program code loaded and executed by the processor to implement the connection establishment method as described in the above aspect.
According to one aspect of the present application, there is provided a chip comprising programmable logic circuits and/or program instructions for implementing the connection establishment method as described in the above aspects, when the chip is run on a bridging device.
According to an aspect of the present application, embodiments of the present application provide a computer program product for implementing the connection establishment method of the above aspect, when the computer program product is executed by a processor of a bridging device.
The technical scheme provided by the embodiment of the application at least comprises the following beneficial effects:
the embodiment of the application provides a scheme for establishing connection between BLE Mesh equipment and CHIP virtual equipment, after a bridging device establishes a mapping relation between the BLE Mesh equipment and the CHIP virtual equipment, the BLE Mesh equipment can be ensured to be accessed into a CHIP network, so that terminal equipment and the BLE Mesh equipment communicate by adopting a CHIP protocol, and a mode of controlling the BLE Mesh equipment is expanded.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 illustrates a schematic diagram of a CHIP virtual device provided in an exemplary embodiment of the present application;
fig. 2 is a schematic structural diagram of a BLE Mesh device according to an exemplary embodiment of the present application;
FIG. 3 illustrates a flow chart of a connection establishment method provided by an exemplary embodiment of the present application;
FIG. 4 illustrates a map provided by an exemplary embodiment of the present application;
FIG. 5 illustrates a map provided by an exemplary embodiment of the present application;
fig. 6 is a schematic diagram of a BLE Mesh device connected to a terminal device according to an exemplary embodiment of the present application;
FIG. 7 illustrates a flow chart of a connection establishment method provided by an exemplary embodiment of the present application;
FIG. 8 illustrates a flow chart of a connection establishment method provided by an exemplary embodiment of the present application;
FIG. 9 illustrates a flow chart of a connection establishment method provided by an exemplary embodiment of the present application;
fig. 10 shows a block diagram of a connection establishment apparatus provided in an exemplary embodiment of the present application;
FIG. 11 illustrates a block diagram of a connection establishment apparatus provided by an exemplary embodiment of the present application;
fig. 12 is a schematic structural diagram of a communication device according to an exemplary embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
It will be understood that the terms "first," "second," and the like, as used herein, may be used to describe various concepts, but are not limited by these terms unless otherwise specified. These terms are only used to distinguish one concept from another.
First, the terms involved in the embodiments of the present application will be briefly described:
CHIP virtual device: the CHIP virtual device is a device adopting the CHIP protocol, and comprises an endpoint, a cluster identifier and an attribute identifier, wherein the endpoint is used for representing the device identifier of the CHIP virtual device, the cluster identifier is used for representing the function of the CHIP virtual device, and the attribute identifier is used for representing the attribute of the CHIP virtual device.
Wherein, the endpoint is represented by endpoint, the cluster identifier is represented by cluster, and the attribute identifier is represented by attribute. Each endpoint includes a device ID (Identity document, identification number) therein, which is used in the CHIP protocol to indicate the device type.
For example, as shown in FIG. 1, the CHIP virtual device corresponds to two endpoints of endpoint1 and endpoint2, endpoint1 corresponds to two cluster identifications of cluster1 and cluster2, cluster1 corresponds to two attribute identifications of attribute1 and attribute2, endpoint2 corresponds to two cluster identifications of cluster3 and cluster4, cluster2 corresponds to two attribute identifications of attribute3 and attribute4, and in addition, attribute1 and attribute2, attribute3 and attribute4 have Data Type and Data, respectively, wherein the Data Type is represented by Type and the Data is represented by Data.
As can be seen from fig. 1, the CHIP virtual device corresponds to at least one endpoint, and each endpoint corresponds to at least one cluster identifier, has at least one function, each cluster identifier corresponds to at least one attribute identifier, and has at least one attribute under each function.
BLE Mesh device: the BLE Mesh device comprises an element identifier, a model identifier and a state, wherein the element identifier is used for representing an entity addressing identifier of the BLE Mesh device, the model identifier is used for representing a function of the BLE Mesh device, and the state is used for representing a state of the BLE Mesh device.
Wherein, the element mark is expressed by element, the model mark is expressed by model, and the state is expressed by state.
For example, as shown in fig. 2, the BLE Mesh device corresponds to two element identifiers of element1 and element2, element1 corresponds to two model identifiers of model1 and model2, model1 corresponds to two states of state1 and state2, element2 corresponds to two model identifiers of model3 and model4, model2 corresponds to two states of state3 and state4, and in addition, each state of state1 and state2, state3 and state4 has a Data Type and Data, wherein the Data Type is represented by Type, and the Data is represented by Data.
As can be seen from fig. 2, the BLE Mesh device corresponds to at least one element identifier, and each element identifier corresponds to at least one model identifier, has at least one function, and each model identifier corresponds to at least one state, and has at least one state under each function.
Bridging device: the bridge device serves as a bridge to connect the terminal device and the BLE Mesh device, so that the BLE Mesh device is accessed to a CHIP protocol adopted by the terminal device. In some embodiments, the bridging device comprises a gateway device, smart home device, or other type of device.
The method provided by the embodiment of the application is applied to the scene of adopting the CHIP protocol to communicate with the BLE Mesh equipment, and the terminal equipment adopting the CHIP protocol and the BLE Mesh equipment are connected through the bridging equipment by adopting the method provided by the embodiment of the application for at least one currently known BLE Mesh equipment, so that the terminal equipment and the BLE Mesh equipment communicate under the CHIP protocol.
Fig. 3 shows a flowchart of a connection establishment method according to an exemplary embodiment of the present application, where the method is applied to a bridging device, and the method includes at least some of the following:
301. and creating a CHIP virtual device based on the connection between the bridge device and the BLE Mesh device, and establishing a mapping relation between the BLE Mesh device and the CHIP virtual device.
In the embodiment of the application, in order to connect the terminal device with the BLE Mesh device through the bridge device, a mapping relationship between the BLE Mesh device and the CHIP virtual device is established first, and the subsequent bridge device processes a received request of the terminal device or the BLE Mesh device according to the mapping relationship, so as to realize communication between the terminal device and the BLE Mesh device.
The bridging device establishes a CHIP virtual device based on connection with the BLE Mesh device, establishes a mapping relation between the BLE Mesh device and the CHIP virtual device, and completes mapping of the BLE Mesh device and the CHIP virtual device.
In some embodiments, a mapping relationship between device information of a BLE Mesh device and device information of a CHIP virtual device is established.
The device information of the BLE Mesh device comprises an element identifier, a model identifier and a state, wherein the element identifier is used for representing an entity addressing identifier of the BLE Mesh device, the model identifier is used for representing a function of the BLE Mesh device, and the state is used for representing the state of the BLE Mesh device.
The device information of the CHIP virtual device includes an element identifier, a model identifier and a state, wherein the element identifier is used for representing an entity addressing identifier of the BLE Mesh device, the model identifier is used for representing a function of the BLE Mesh device, and the state is used for representing a state of the BLE Mesh device.
On the basis that the BLE Mesh device and the CHIP virtual device comprise the device information, establishing a mapping relation between the device information of the BLE Mesh device and the device information of the CHIP virtual device comprises the following situations:
(1) And establishing a mapping relation between the element identification of the BLE Mesh device and the endpoint of the CHIP virtual device.
In the embodiment of the present application, the device information of the BLE Mesh device includes an element identifier, and the device information of the CHIP virtual device includes an endpoint, then a mapping relationship between the element identifier and the endpoint is established, and when the endpoint is received, the element identifier corresponding to the endpoint can be determined.
For example, endpoints of the CHIP virtual device are 0x0012, 0x0013, and 0x0014, and elements of the ble Mesh device are identified as 0x0001,0x 0002, and 0x0003, then in the mapping relationship, 0x0012 corresponds to 0x0001,0x0013 corresponds to 0x0002, and 0x0014 corresponds to 0x0003.
For another example, if the element identifications of the BLE Mesh device are 0x0001,0x 0002, and 0x0003, the endpoints of the CHIP virtual device are set to 0x0001,0x 0002, and 0x0003, the endpoint 0x0001 of the CHIP virtual device directly represents the element identification 0x0001 of the BLE Mesh device, the endpoint 0x0002 of the CHIP virtual device directly represents the element identification 0x0002 of the BLE Mesh device, and the endpoint 0x0003 of the CHIP virtual device directly represents the element identification 0x0003 of the BLE Mesh device.
In this case, the element identifier of the BLE Mesh device is in an equivalent relationship with the endpoint of the CHIP virtual device, and the bridge device can directly determine the element identifier of the BLE Mesh device corresponding to the endpoint of the CHIP virtual device.
In some embodiments, the element identification of the BLE Mesh device includes a master element identification capable of representing node addressing of the BLE Mesh device and a slave element identification that is a sum of accumulated values based on the master element identification.
For example, the master element identification is 0x0001, then the first slave element identification is 0x0002 after the master element identification is added with 1, and the second slave element identification is 0x0003 after the master element identification is added with 2, so on, the slave element identifications can be determined on the basis of the master element identification.
In some embodiments, the mapping is stored in a mapping table; alternatively, the mapping relationship is stored in the bridging device.
The bridge device can create a mapping relation table, store a mapping relation between element identifiers of the BLE Mesh device and endpoints of the CHIP virtual device in the mapping relation table, and query the mapping relation table when the subsequent bridge device receives the endpoints of the CHIP virtual device so as to determine the element identifiers of the corresponding BLE Mesh device.
According to the embodiment of the application, the mapping relation is stored in the mapping relation table, the mapping relation can be determined by directly inquiring the mapping relation table, mapping is flexible, and inquiring efficiency is improved.
Or after the bridge device establishes connection with the BLE Mesh device, directly determining a mapping relation between the element identifier of the BLE Mesh device and the endpoint of the CHIP virtual device, directly storing the mapping relation in the bridge device, and if the bridge device acquires the endpoint of the CHIP virtual device, directly determining the element identifier of the BLE Mesh device corresponding to the endpoint of the CHIP virtual device.
According to the embodiment of the application, the mapping relation is directly stored in the bridging equipment, a mapping relation table is not required to be maintained, and resources are saved.
In some embodiments, an endpoint list of the CHIP virtual device is determined, the endpoint list including at least one endpoint of the CHIP virtual device, a mapping relationship between an element identification of the BLE Mesh device and the endpoint list of the CHIP virtual device is established.
In the process of establishing the mapping relation between the CHIP virtual device and the BLE Mesh device, an endpoint list is allocated for the BLE Mesh device, and the mapping relation between the element identification of the BLE Mesh device and the endpoint list of the CHIP virtual device is established.
In one possible implementation, a mapping relationship is established between an identifier of an endpoint list of the CHIP virtual device and an element identifier of the BLE Mesh device, and the element identifier of the BLE Mesh device is determined according to the endpoint list of the CHIP virtual device, so as to determine a corresponding relationship between an endpoint of the CHIP virtual device and the element identifier of the BLE Mesh device.
For example, the endpoint list includes three endpoints of 0x0012, 0x0013 and 0x0014, which are respectively in one-to-one correspondence with the element identifiers 0x0001, 0x0002 and 0x0003 of the BLE Mesh device.
(2) And establishing a mapping relation between the model identifier of the BLE Mesh device and the cluster identifier of the CHIP virtual device.
In the embodiment of the application, the device information of the BLE Mesh device further comprises a model identifier, the CHIP virtual device further comprises a cluster identifier, a mapping relation between the model identifier and the cluster identifier is established, and when the cluster identifier is received, the model identifier corresponding to the cluster identifier can be determined according to the mapping relation.
For example, the model identifier of the BLE Mesh device is 0x1000, the cluster identifier corresponding to the model identifier is 0x0008, and the mapping relationship established includes a correspondence relationship between 0x1000 and 0x 0008.
(3) And establishing a mapping relation between the state of the BLE Mesh device and the attribute identification of the CHIP virtual device.
In the embodiment of the application, the device information of the BLE Mesh device further comprises a state, the CHIP virtual device further comprises an attribute identifier, a mapping relation between the state and the attribute identifier is established, and when the state is received, the attribute identifier corresponding to the state can be determined according to the mapping relation.
It should be noted that, in the embodiment of the present application, the modes (1), (2), and (3) of establishing a mapping relationship may be combined with each other, so that the established mapping relationship includes a mapping relationship between a plurality of pieces of device information.
In some embodiments, the mapping relationship is established in a combined manner of (1), (2) and (3), and then the mapping relationship includes a mapping relationship between an element identifier of the BLE Mesh device and an endpoint of the CHIP virtual device, a mapping relationship between a model identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device, and a mapping relationship between a state of the BLE Mesh device and an attribute identifier of the CHIP virtual device.
For example, fig. 4 shows a mapping relationship diagram provided in an exemplary embodiment of the present application, referring to fig. 4, the device information of the chip virtual device has a one-to-one correspondence with the device information of the BLE Mesh device.
(4) And establishing a mapping relation between a main element identifier in the element identifiers of the BLE Mesh device and the endpoint of the CHIP virtual device.
The element identification of the BLE Mesh device comprises a master element identification and a slave element identification, the BLE Mesh device can be addressed based on the master element identification, and the slave element identification is the sum of accumulated values based on the master element identification.
The device information of the BLE Mesh device includes a main element identifier, the device information of the CHIP virtual device includes an endpoint, in this embodiment, a mapping relationship between the main element identifier of the BLE Mesh device and the endpoint of the CHIP virtual device is established, and when the endpoint of the CHIP virtual device is received, the mapping relationship can determine the main element identifier of the BLE Mesh device corresponding to the endpoint.
(5) And establishing a mapping relation between the element identification of the BLE Mesh device and the cluster identification of the CHIP virtual device.
In the embodiment of the application, the device information of the BLE Mesh device further comprises an element identifier, the CHIP virtual device further comprises a cluster identifier, and when the mapping relation between the element identifier and the cluster identifier is established, the element identifier corresponding to the cluster identifier is determined according to the mapping relation.
(6) And establishing a mapping relation between the model identifier of the BLE Mesh device and the attribute identifier of the CHIP virtual device.
In the embodiment of the application, the device information of the BLE Mesh device further comprises a model identifier, the device information of the CHIP virtual device further comprises an attribute identifier, and when the mapping relation between the model identifier and the attribute identifier is established, the model identifier corresponding to the attribute identifier is determined according to the mapping relation when the attribute identifier is received.
It should be noted that, in the embodiment of the present application, the ways (4), (5), and (6) of establishing the mapping relationship may be combined with each other, so that the established mapping relationship includes a mapping relationship between a plurality of pieces of device information.
In some embodiments, the mapping relationship is established in a combined manner (4), (5) and (6), and then the mapping relationship includes a mapping relationship between a main element identifier in the element identifier of the BLE Mesh device and an endpoint of the CHIP virtual device, a mapping relationship between the element identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device, and a mapping relationship between a model identifier of the BLE Mesh device and an attribute identifier of the CHIP virtual device.
For example, fig. 5 shows a mapping relationship diagram provided in an exemplary embodiment of the present application, referring to fig. 5, the device information of the chip virtual device has a one-to-one correspondence with the device information of the BLE Mesh device.
After establishing a mapping relation between the CHIP virtual device and the BLE Mesh device, the subsequent terminal acquires state data corresponding to the state of the BLE Mesh device according to the mapping relation.
302. And establishing connection between the CHIP virtual device and the terminal device.
In the embodiment of the present application, the mapping relationship between the BLE Mesh device and the CHIP virtual device is established through step 301, and then the connection between the CHIP virtual device and the terminal device is established, at this time, the bridge device serves as a bridge between the terminal device and the BLE Mesh device, so as to implement communication between the terminal device and the BLE Mesh device. Wherein the terminal device is a device with CHIP client functionality, the terminal device having an execution control service or a request service, or being capable of executing other services as well.
In some embodiments, the terminal device has an application program (CHIP APP) installed therein, the application program being a program that controls the BLE Mesh device using the CHIP protocol.
For example, fig. 6 shows a schematic diagram of a BLE Mesh device connected to a terminal device according to an exemplary embodiment of the present application. Referring to fig. 6, a Bridge device is represented by Bridge, which is capable of connecting with each BLE Mesh device over a secure communication link, and is also capable of interpreting the BLE Mesh devices as CHIP virtual devices displayed in a CHIP APP, providing an accessible interface for the CHIP APP. And the Bridge device comprises CHIP device1 and CHIP device2, and Bridge devices corresponding to the Bridge device, wherein the Bridge device and the Bridge device1 and the Bridge device2 respectively establish BLE Mesh network connection, and the Bridge and the CHIP device1 and the CHIP device2 are respectively connected by adopting CHIP network, and each CHIP APP in the CHIP APP1, the CHIP APP2 and the CHIP APP3 can call an interface provided by the Bridge to control the BLE Mesh device through the Bridge.
303. Based on the connection between the CHIP virtual device and the terminal device, a read request sent by the terminal device is received.
In the embodiment of the present application, after the terminal device and the BLE Mesh device can communicate through the bridge device, the terminal device sends a read request to the BLE Mesh device based on the connection, so as to read the state data of the BLE Mesh device.
Wherein the read request is for reading status data of the BLE Mesh device. The read request carries first device information of the CHIP virtual device, where the first device information includes an endpoint and a cluster identifier, or the first device information includes an endpoint, a cluster identifier, and an attribute identifier.
304. And determining second equipment information corresponding to the first equipment information based on the mapping relation.
In this embodiment of the present application, when the terminal device adopts the CHIP protocol, and when the terminal device sends a read request, the device information carried in the read request is the device information of the CHIP virtual device, and after the bridge device receives the read request, the bridge device can determine the device information of the BLE Mesh device according to the device information and the mapping relationship of the CHIP virtual device included in the read request.
Because the BLE Mesh device cannot identify the device information included in the read request sent by the terminal device, the bridge device can convert the device information of the CHIP virtual device into the device information of the BLE Mesh device according to the established mapping relationship, and if the BLE Mesh device receives the converted device information sent by the bridge device, the bridge device can determine the corresponding state data according to the device information.
In some embodiments, since the mapping relationship includes a mapping relationship between the endpoint list and the element identifier, when the bridging device determines, based on the mapping relationship, the element identifier corresponding to the endpoint list to which the endpoint belongs in the mapping relationship needs to be determined.
It should be noted that, in the embodiment of the present application, only the element identifier of the BLE Mesh device corresponding to the endpoint is determined by the bridge device based on the mapping relationship between the endpoint list and the BLE Mesh device. Before this process, the terminal device needs to obtain the endpoint of the CHIP virtual device included in the endpoint list from the bridge device, and then obtain the element identifier of the corresponding BLE Mesh device according to the obtained endpoint of the CHIP virtual device.
In some embodiments, the terminal device sends the list identifier of the endpoint list to the bridge device, and the bridge device determines a corresponding endpoint list according to the list identifier and returns the endpoint list to the terminal device.
305. And determining the state data of the BLE Mesh device to which the second device information belongs.
In the embodiment of the present application, after the bridge device determines the second device information corresponding to the first device information, a read request including the second device information is sent to the BLE Mesh device, and after the BLE Mesh device receives the read request including the second device information, state data corresponding to the second device information is sent to the bridge device, so that the bridge device can determine the state data of the BLE Mesh device to which the second device information belongs.
In the embodiment of the present application, since the manner of the mapping relationship established by the bridge device is different, the method for determining the state data is also different:
the first way is:
since the first device information included in the read request sent by the terminal device is different, it is necessary to acquire the state data of the BLE Mesh device in different manners:
(1) If the reading request comprises the endpoint and the cluster identifier, determining an element identifier corresponding to the endpoint and a model identifier corresponding to the cluster identifier based on the mapping relation, and determining state data of a state corresponding to the model identifier.
In the embodiment of the application, the bridging device determines the corresponding element identifier and the model identifier according to the endpoint and the cluster identifier included in the read request, so that the state data of at least one state corresponding to the model identifier can be determined.
For example, if the model identifier corresponds to one state, the state data of the one state is determined, and if the model identifier corresponds to three states, the state data of the three states is determined.
The mapping relationship between the CHIP virtual device and the BLE Mesh device established by the bridge device includes a mapping relationship between an element identifier of the BLE Mesh device and an endpoint of the CHIP virtual device, a mapping relationship between a model identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device, or the mapping relationship includes a mapping relationship between an element identifier of the BLE Mesh device and an endpoint of the CHIP virtual device, a mapping relationship between a model identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device, and a mapping relationship between a state of the BLE Mesh device and an attribute identifier of the CHIP virtual device, and after receiving a read request, the bridge device can determine an element identifier corresponding to the endpoint and a model identifier corresponding to the cluster identifier, and determine state data of a state corresponding to the model identifier.
(2) If the read request includes the endpoint, the cluster identifier and the attribute identifier, determining an element identifier corresponding to the endpoint, a model identifier corresponding to the cluster identifier and a state corresponding to the attribute identifier based on the mapping relation, and determining state data of the state.
In the embodiment of the application, the bridging device determines the corresponding element identifier, model identifier and state according to the endpoint, cluster identifier and attribute identifier included in the read request, so that the state data of the state can be determined.
The mapping relationship between the CHIP virtual device and the BLE Mesh device established by the bridge device includes a mapping relationship between an element identifier of the BLE Mesh device and an endpoint of the CHIP virtual device, a mapping relationship between a model identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device, and a mapping relationship between a state of the BLE Mesh device and an attribute identifier of the CHIP virtual device, and after the bridge device receives a read request, the bridge device can determine an element identifier corresponding to the endpoint and a model identifier corresponding to the cluster identifier based on the mapping relationship, and determine state data of a state corresponding to the model identifier.
The second way is:
since the first device information included in the read request sent by the terminal device is different, it is necessary to acquire the state data of the BLE Mesh device in different manners:
(1) If the read request comprises the endpoint, the cluster identifier and the attribute identifier, determining a main element identifier corresponding to the endpoint, an element identifier corresponding to the cluster identifier and a model identifier corresponding to the attribute identifier based on the mapping relation, and determining state data of a state corresponding to the model identifier.
In the embodiment of the application, the bridging device determines the corresponding main element identifier, the element identifier and the model identifier according to the endpoint, the cluster identifier and the attribute identifier included in the read request, so that the state data of at least one state corresponding to the model identifier can be determined.
For example, if the model identifier corresponds to one state, the state data of the one state is determined, and if the model identifier corresponds to three states, the state data of the three states is determined.
The mapping relationship between the CHIP virtual device and the BLE Mesh device established by the bridge device includes a mapping relationship between a main element identifier in an element identifier of the BLE Mesh device and an endpoint of the CHIP virtual device, a mapping relationship between an element identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device, and a mapping relationship between a model identifier of the BLE Mesh device and an attribute identifier of the CHIP virtual device.
(2) If the reading request comprises the endpoint and the cluster identifier, determining a main element identifier corresponding to the endpoint and an element identifier corresponding to the cluster identifier based on the mapping relation, determining each model identifier corresponding to the element identifier, and determining state data of a state corresponding to each model identifier.
In the embodiment of the application, the bridging device determines the corresponding main element identifier and the element identifier according to the endpoint and the cluster identifier included in the read request, so that at least one model identifier corresponding to the element identifier can be determined, and further state data of at least one state corresponding to each model identifier is determined.
For example, an element identifier corresponds to one model identifier, one model identifier corresponds to state data of one state, or an element identifier corresponds to a plurality of model identifiers, one model identifier corresponds to state data of a plurality of states.
The mapping relationship between the CHIP virtual device and the BLE Mesh device established by the bridge device includes a mapping relationship between a main element identifier in an element identifier of the BLE Mesh device and an endpoint of the CHIP virtual device, a mapping relationship between an element identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device, or a mapping relationship between a main element identifier in an element identifier of the BLE Mesh device and an endpoint of the CHIP virtual device, a mapping relationship between an element identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device, and a mapping relationship between a model identifier of the BLE Mesh device and an attribute identifier of the CHIP virtual device.
306. The state data is converted into corresponding attribute data.
307. And sending the attribute data to the terminal equipment.
In the embodiment of the application, the bridge device determines the state data of the BLE Mesh device in the above manner, and before sending the state data to the terminal device, the bridge device needs to convert the state data into attribute data that can be identified by the terminal device, and then sends the attribute data to the terminal device, so as to complete the process of reading the state data of the BLE Mesh device by the terminal device.
It should be noted that, in the embodiments of the present application, only the bridging device is taken as an example to describe the connection establishment method. In another embodiment, the bridge device includes a CHIP virtual service module, a CHIP bridge module, and a BLE Mesh virtual client.
The CHIP virtual service module is used for creating the CHIP virtual device, establishing the secure connection with the terminal device and interacting with the terminal device.
The embodiment of the application provides a scheme for establishing connection between BLE Mesh equipment and CHIP virtual equipment, after a bridging device establishes a mapping relation between the BLE Mesh equipment and the CHIP virtual equipment, the BLE Mesh equipment can be ensured to be accessed into a CHIP network, so that terminal equipment and the BLE Mesh equipment communicate by adopting a CHIP protocol, and a mode of controlling the BLE Mesh equipment is expanded.
The embodiment of fig. 3 describes a method for the bridge device to implement communication between the BLE Mesh device and the CHIP virtual device by establishing a mapping relationship between the BLE Mesh device and the CHIP virtual device. In some embodiments, the bridge device includes a CHIP virtual service module, a CHIP bridge module and a BLE Mesh virtual client, and the interaction between each module in the bridge device and between the terminal device and the BLE Mesh device is described below. Fig. 7 shows a flowchart of a connection establishment method according to an exemplary embodiment of the present application, and referring to fig. 7, the method includes:
701. and the BLE Mesh virtual client establishes secure connection with the BLE Mesh device.
702. And the BLE Mesh virtual client sends a mapping relation establishment request to the CHIP bridging module.
703. The CHIP bridging module establishes a mapping relation between element identifiers of the BLE Mesh device and endpoints of the CHIP virtual device, a mapping relation between model identifiers of the BLE Mesh device and cluster identifiers of the CHIP virtual device, and a mapping relation between states of the BLE Mesh device and attribute identifiers of the CHIP virtual device based on the mapping relation establishment request.
704. The CHIP bridging module sends a create request to the CHIP virtual service module.
705. The CHIP virtual service module creates a CHIP virtual device based on the creation request.
706. The CHIP virtual service module establishes a secure connection with the terminal device.
707. And the terminal equipment sends a read request to the CHIP virtual service module.
708. The CHIP virtual service module sends a relationship resolution request to the CHIP bridge module.
709. The CHIP bridging module determines a state of the BLE Mesh device based on device information included in the relationship resolution request, and sends a data read request to the BLE Mesh virtual client.
710. And the BLE Mesh virtual client sends a data reading request to the BLE Mesh device.
711. And the BLE Mesh virtual client receives state data corresponding to the state returned by the BLE Mesh device.
712. And the BLE Mesh virtual client sends state data to the CHIP bridging module.
713. The CHIP bridging module converts the status data into attribute data and sends the attribute data to the CHIP virtual service module.
714. The CHIP virtual service module sends attribute data to the terminal device.
Based on the embodiment of fig. 7, the bridge device is further capable of establishing a mapping relationship between the endpoint list and the BLE Mesh device, step 703 is replaced by 7031, and before step 707, referring to fig. 8, the method further includes steps 71-75:
7031. The CHIP bridging module establishes a mapping relation between the device identifier of the BLE Mesh device and the endpoint list based on the mapping relation establishment request, and establishes a mapping relation between the element identifier of the BLE Mesh device and the endpoint of the CHIP virtual device, a mapping relation between the model identifier of the BLE Mesh device and the cluster identifier of the CHIP virtual device, and a mapping relation between the state of the BLE Mesh device and the attribute identifier of the CHIP virtual device.
71. The terminal device sends a list reading request to the CHIP virtual service module.
72. The CHIP virtual service module sends the accepted list read request to the CHIP bridge module.
73. The CHIP bridging module determines a corresponding endpoint list according to the list identifier in the list read request.
74. The CHIP bridging module sends the endpoint list to the CHIP virtual service module.
75. The CHIP virtual service module sends the endpoint list to the terminal device.
The above embodiment of fig. 7 is described taking as an example one possible implementation manner of establishing the mapping relationship between the BLE Mesh device and the CHIP virtual device. Another possible implementation manner of establishing the mapping relationship between the BLE Mesh device and the CHIP virtual device will be described below. Fig. 9 shows a flowchart of a connection establishment method according to an exemplary embodiment of the present application, and referring to fig. 9, the method includes:
901. And the BLE Mesh virtual client establishes secure connection with the BLE Mesh device.
902. And the BLE Mesh virtual client sends a mapping relation establishment request to the CHIP bridging module.
903. The CHIP bridging module establishes a mapping relation between a main element identifier in element identifiers of the BLE Mesh device and endpoints of the CHIP virtual device, a mapping relation between the element identifiers of the BLE Mesh device and cluster identifiers of the CHIP virtual device, and a mapping relation between model identifiers of the BLE Mesh device and attribute identifiers of the CHIP virtual device based on the mapping relation establishment request.
904. The CHIP bridging module sends a create request to the CHIP virtual service module.
905. The CHIP virtual service module creates a CHIP virtual device based on the creation request.
906. The CHIP virtual service module establishes a secure connection with the terminal device.
907. And the terminal equipment sends a read request to the CHIP virtual service module.
908. The CHIP virtual service module sends a relationship resolution request to the CHIP bridge module.
909. The CHIP bridging module determines a state of the BLE Mesh device based on device information included in the relationship resolution request, and sends a data read request to the BLE Mesh virtual client.
910. And the BLE Mesh virtual client sends a data reading request to the BLE Mesh device.
911. And the BLE Mesh virtual client receives state data corresponding to the state returned by the BLE Mesh device.
912. And the BLE Mesh virtual client sends state data to the CHIP bridging module.
913. The CHIP bridging module converts the status data into attribute data and sends the attribute data to the CHIP virtual service module.
914. The CHIP virtual service module sends attribute data to the terminal device.
Fig. 10 shows a block diagram of a connection establishment apparatus according to an exemplary embodiment of the present application, the apparatus comprising:
a relationship establishing module 1001, configured to create a CHIP virtual device based on a connection between the bridge device and the BLE Mesh device, and establish a mapping relationship between the BLE Mesh device and the CHIP virtual device;
a connection establishment module 1002, configured to establish a connection between a CHIP virtual device and a terminal device;
the CHIP virtual device and the terminal device adopt CHIP protocol, and the BLE Mesh device and the terminal device are used for communication based on the mapping relation between the BLE Mesh device and the CHIP virtual device and the connection between the CHIP virtual device and the terminal device.
In some embodiments, the relationship establishment module 1001 is configured to establish a mapping relationship between device information of the BLE Mesh device and device information of the CHIP virtual device.
In some embodiments, the device information of the BLE Mesh device includes an element identifier, a model identifier, and a state, where the element identifier is used to represent an entity addressing identifier of the BLE Mesh device, the model identifier is used to represent a function of the BLE Mesh device, and the state is used to represent a state in which the BLE Mesh device is located;
the device information of the CHIP virtual device includes an endpoint for representing the device identification of the CHIP virtual device, a cluster identification for representing the function of the CHIP virtual device, and an attribute identification for representing the attribute of the CHIP virtual device.
In some embodiments, a relationship establishment module 1001 is configured to establish a mapping relationship between an element identifier of a BLE Mesh device and an endpoint of a CHIP virtual device.
In some embodiments, referring to fig. 11, the relationship establishment module 1001 includes:
a list determining unit 10011, configured to determine an endpoint list of the CHIP virtual device, where the endpoint list includes at least one endpoint of the CHIP virtual device;
an establishing unit 10012 is configured to establish a mapping relationship between a device identifier of the BLE Mesh device and an endpoint list of the CHIP virtual device.
In some embodiments, the mapping is stored in a mapping table; alternatively, the mapping relationship is stored in the bridging device.
In some embodiments, the relationship establishment module 1001 is configured to establish a mapping relationship between a model identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device.
In some embodiments, the relationship establishing module 1001 is configured to establish a mapping relationship between a state of the BLE Mesh device and an attribute identifier of the CHIP virtual device.
In some embodiments, the relationship establishment module 1001 is configured to establish a mapping relationship between a main element identifier in the element identifier of the BLE Mesh device and an endpoint of the CHIP virtual device.
In some embodiments, the relationship establishment module 1001 is configured to establish a mapping relationship between an element identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device.
In some embodiments, the relationship establishing module 1001 is configured to establish a mapping relationship between a model identifier of the BLE Mesh device and an attribute identifier of the CHIP virtual device.
In some embodiments, referring to fig. 11, a receiving module 1003 is configured to receive, based on a connection between the CHIP virtual device and the terminal device, a read request sent by the terminal device, where the read request carries first device information of the CHIP virtual device, and the first device information includes an endpoint and a cluster identifier, or the first device information includes an endpoint, a cluster identifier, and an attribute identifier;
An information determining module 1004, configured to determine second device information corresponding to the first device information based on the mapping relationship;
a data determining module 1005, configured to determine status data of a BLE Mesh device to which the second device information belongs;
a conversion module 1006, configured to convert the state data into corresponding attribute data;
a sending module 1007 is configured to send attribute data to the terminal device.
In some embodiments, the first device information includes an endpoint and a cluster identifier, and the information determining module 1004 is configured to determine, based on the mapping relationship, an element identifier corresponding to the endpoint and a model identifier corresponding to the cluster identifier;
the data determining module 1005 is configured to determine state data of a state corresponding to the model identifier.
In some embodiments, the device information includes an endpoint, a cluster identifier, and an attribute identifier, and the information determining module 1004 is configured to determine, based on the mapping relationship, an element identifier corresponding to the endpoint, a model identifier corresponding to the cluster identifier, and a state corresponding to the attribute identifier;
the data determining module 1005 is configured to determine status data of the status.
In some embodiments, the information determining module 1004 is configured to determine at least one endpoint included in the endpoint list to which the endpoint belongs in the mapping relationship;
A sending module 1007 is configured to send at least one endpoint to the terminal device.
In some embodiments, the first device information includes an endpoint, a cluster identifier, and an attribute identifier, and the information determining module 1004 is configured to determine, based on the mapping relationship, a main element identifier corresponding to the endpoint, an element identifier corresponding to the cluster identifier, and a model identifier corresponding to the attribute identifier;
the data determining module 1005 is configured to determine state data of a state corresponding to the model identifier.
In some embodiments, the first device information includes an endpoint and a cluster identifier, and the information determining module 1004 is configured to determine, based on the mapping relationship, a main element identifier corresponding to the endpoint and an element identifier corresponding to the cluster identifier;
an information determining module 1004, configured to determine each model identifier corresponding to the element identifier; state data is determined for each model identifying a corresponding state.
Fig. 12 shows a schematic structural diagram of a bridge device according to an exemplary embodiment of the present application, where the bridge device includes: a processor 1201, a receiver 1202, a transmitter 1203, a memory 1204, and a bus 1205.
The processor 1201 includes one or more processing cores, and the processor 1201 executes various functional applications and information processing by running software programs and modules.
The receiver 1202 and the transmitter 1203 may be implemented as one communication component, which may be a communication chip.
The memory 1204 is connected to the processor 1201 by a bus 1205.
The memory 1204 may be used for storing at least one program code for execution by the processor 1201 to implement the various steps of the method embodiments described above.
The memory 1204 may be implemented by any type or combination of volatile or nonvolatile memory devices including, but not limited to: magnetic or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static Random Access Memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, programmable read-only memory (PROM).
In an exemplary embodiment, there is also provided a computer readable storage medium having stored therein executable program code loaded and executed by the processor to implement the connection establishment method performed by the communication device provided by the above respective method embodiments.
In an exemplary embodiment, a chip is also provided, the chip comprising programmable logic circuits and/or program instructions for implementing a connection establishment method as described above, when the chip is run on a bridging device.
In an exemplary embodiment, a computer program product for implementing the above-described connection establishment method is also provided, which, when being executed by a processor of a bridging device.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The foregoing description of the preferred embodiments is merely exemplary in nature and is in no way intended to limit the invention, since it is intended that all modifications, equivalents, improvements, etc. that fall within the spirit and scope of the invention.

Claims (38)

  1. A method of connection establishment, applied to a bridging device, the method comprising:
    based on the connection between the bridging device and BLE Mesh device of the Bluetooth low-power grid network, establishing a CHIP virtual device which is connected with a family work group through an Internet protocol under the Zigbee alliance, and establishing a mapping relation between the BLE Mesh device and the CHIP virtual device;
    Establishing connection between the CHIP virtual equipment and terminal equipment;
    the CHIP virtual device and the terminal device adopt a CHIP protocol, and the BLE Mesh device and the terminal device are used for communication based on a mapping relationship between the BLE Mesh device and the CHIP virtual device and connection between the CHIP virtual device and the terminal device.
  2. The method of claim 1, wherein the establishing a mapping relationship between the BLE Mesh device and the CHIP virtual device comprises:
    and establishing a mapping relation between the equipment information of the BLE Mesh equipment and the equipment information of the CHIP virtual equipment.
  3. The method of claim 2, wherein the step of determining the position of the substrate comprises,
    the device information of the BLE Mesh device comprises an element identifier, a model identifier and a state, wherein the element identifier is used for representing an entity addressing identifier of the BLE Mesh device, the model identifier is used for representing a function of the BLE Mesh device, and the state is used for representing the state of the BLE Mesh device;
    the device information of the CHIP virtual device includes an endpoint, a cluster identifier, and an attribute identifier, where the endpoint is used to represent a device identifier of the CHIP virtual device, the cluster identifier is used to represent a function of the CHIP virtual device, and the attribute identifier is used to represent an attribute of the CHIP virtual device.
  4. A method according to claim 3, wherein said establishing a mapping relationship between device information of said BLE Mesh device and device information of said CHIP virtual device comprises:
    and establishing a mapping relation between the element identification of the BLE Mesh device and the endpoint of the CHIP virtual device.
  5. The method of claim 4, wherein the establishing a mapping relationship between the element identification of the BLE Mesh device and the endpoint of the CHIP virtual device further comprises:
    determining an endpoint list of the CHIP virtual device, wherein the endpoint list comprises at least one endpoint of the CHIP virtual device;
    and establishing a mapping relation between the device identification of the BLE Mesh device and the endpoint list of the CHIP virtual device.
  6. The method of claim 4, wherein the mapping relationship is stored in a mapping relationship table; or, the mapping relation is stored in the bridging device.
  7. A method according to claim 3, wherein said establishing a mapping relationship between device information of said BLE Mesh device and device information of said CHIP virtual device comprises:
    and establishing a mapping relation between the model identifier of the BLE Mesh device and the cluster identifier of the CHIP virtual device.
  8. A method according to claim 3, wherein said establishing a mapping relationship between device information of said BLE Mesh device and device information of said CHIP virtual device comprises:
    and establishing a mapping relation between the state of the BLE Mesh device and the attribute identification of the CHIP virtual device.
  9. A method according to claim 3, wherein said establishing a mapping relationship between device information of said BLE Mesh device and device information of said CHIP virtual device comprises:
    and establishing a mapping relation between a main element identifier in the element identifiers of the BLE Mesh device and the endpoint of the CHIP virtual device.
  10. A method according to claim 3, wherein said establishing a mapping relationship between device information of said BLE Mesh device and device information of said CHIP virtual device comprises:
    and establishing a mapping relation between the element identification of the BLE Mesh device and the cluster identification of the CHIP virtual device.
  11. A method according to claim 3, wherein said establishing a mapping relationship between device information of said BLE Mesh device and device information of said CHIP virtual device comprises:
    And establishing a mapping relation between the model identifier of the BLE Mesh device and the attribute identifier of the CHIP virtual device.
  12. The method according to claim 2, wherein the method further comprises:
    receiving a read request sent by the terminal equipment based on the connection between the CHIP virtual equipment and the terminal equipment, wherein the read request carries first equipment information of the CHIP virtual equipment, the first equipment information comprises an endpoint and a cluster identifier, or the first equipment information comprises the endpoint, the cluster identifier and an attribute identifier;
    determining second equipment information corresponding to the first equipment information based on the mapping relation;
    determining state data of BLE Mesh equipment to which the second equipment information belongs;
    converting the state data into corresponding attribute data;
    and sending the attribute data to the terminal equipment.
  13. The method of claim 12, wherein the first device information includes an endpoint and a cluster identity, and wherein the determining, based on the mapping relationship, the second device information corresponding to the first device information includes:
    determining an element identifier corresponding to the endpoint and a model identifier corresponding to the cluster identifier based on the mapping relation;
    The determining the state data of the BLE Mesh device to which the second device information belongs includes:
    and determining state data of the state corresponding to the model identification.
  14. The method of claim 12, wherein the first device information includes an endpoint, a cluster identifier, and an attribute identifier, and wherein the determining, based on the mapping relationship, the second device information corresponding to the first device information includes:
    determining an element identifier corresponding to the endpoint, a model identifier corresponding to the cluster identifier and a state corresponding to the attribute identifier based on the mapping relation;
    the determining the state data of the BLE Mesh device to which the second device information belongs includes:
    state data of the state is determined.
  15. The method according to claim 13 or 14, wherein prior to said receiving a read request sent by said terminal device, the method further comprises:
    and determining at least one endpoint included in an endpoint list to which the endpoint belongs in the mapping relation, and sending the at least one endpoint to the terminal equipment.
  16. The method of claim 12, wherein the first device information includes an endpoint, a cluster identifier, and an attribute identifier, and wherein the determining, based on the mapping relationship, the second device information corresponding to the first device information includes:
    Determining a main element identifier corresponding to the endpoint, an element identifier corresponding to the cluster identifier and a model identifier corresponding to the attribute identifier based on the mapping relation;
    the determining the state data of the BLE Mesh device to which the second device information belongs includes:
    and determining state data of the state corresponding to the model identification.
  17. The method of claim 12, wherein the first device information includes an endpoint and a cluster identity, and wherein the determining, based on the mapping relationship, the second device information corresponding to the first device information includes:
    determining a main element identifier corresponding to the endpoint and an element identifier corresponding to the cluster identifier based on the mapping relation;
    the determining the state data of the BLE Mesh device to which the second device information belongs includes:
    determining each model identifier corresponding to the element identifier;
    and determining state data of the corresponding states of each model identifier.
  18. A connection establishment apparatus for use with a bridging device, the apparatus comprising:
    a relation establishing module, configured to establish a CHIP virtual device based on the connection between the bridge device and the BLE Mesh device, and establish a mapping relation between the BLE Mesh device and the CHIP virtual device;
    A connection establishment module, configured to establish a connection between the CHIP virtual device and a terminal device;
    the CHIP virtual device and the terminal device adopt a CHIP protocol, and the BLE Mesh device and the terminal device are used for communication based on a mapping relationship between the BLE Mesh device and the CHIP virtual device and connection between the CHIP virtual device and the terminal device.
  19. The apparatus of claim 18, wherein the relationship establishment module is configured to establish a mapping relationship between device information of the BLE Mesh device and device information of the CHIP virtual device.
  20. The apparatus of claim 19, wherein the device comprises a plurality of sensors,
    the device information of the BLE Mesh device comprises an element identifier, a model identifier and a state, wherein the element identifier is used for representing an entity addressing identifier of the BLE Mesh device, the model identifier is used for representing a function of the BLE Mesh device, and the state is used for representing the state of the BLE Mesh device;
    the device information of the CHIP virtual device includes an endpoint, a cluster identifier, and an attribute identifier, where the endpoint is used to represent a device identifier of the CHIP virtual device, the cluster identifier is used to represent a function of the CHIP virtual device, and the attribute identifier is used to represent an attribute of the CHIP virtual device.
  21. The apparatus of claim 20, wherein the relationship establishment module is configured to establish a mapping relationship between an element identifier of the BLE Mesh device and an endpoint of the CHIP virtual device.
  22. The apparatus of claim 21, wherein the relationship establishment module comprises:
    a list determining unit, configured to determine an endpoint list of the CHIP virtual device, where the endpoint list includes at least one endpoint of the CHIP virtual device;
    and the establishing unit is used for establishing a mapping relation between the device identifier of the BLE Mesh device and the endpoint list of the CHIP virtual device.
  23. The apparatus of claim 21, wherein the mapping is stored in a mapping table; or, the mapping relation is stored in the bridging device.
  24. The apparatus of claim 20, wherein the relationship establishment module is configured to establish a mapping relationship between a model identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device.
  25. The apparatus of claim 20, wherein a relationship establishment module is configured to establish a mapping relationship between a state of the BLE Mesh device and an attribute identifier of the CHIP virtual device.
  26. The apparatus of claim 20, wherein the relationship establishment module is configured to establish a mapping relationship between a master element identifier in element identifiers of the BLE Mesh device and endpoints of the CHIP virtual device.
  27. The apparatus of claim 20, wherein the relationship establishment module is configured to establish a mapping relationship between an element identifier of the BLE Mesh device and a cluster identifier of the CHIP virtual device.
  28. The apparatus of claim 20, wherein the relationship establishment module is configured to establish a mapping relationship between a model identifier of the BLE Mesh device and an attribute identifier of the CHIP virtual device.
  29. The apparatus of claim 19, wherein the apparatus further comprises:
    a receiving module, configured to receive, based on a connection between the CHIP virtual device and the terminal device, a read request sent by the terminal device, where the read request carries first device information of the CHIP virtual device, where the first device information includes an endpoint and a cluster identifier, or where the first device information includes an endpoint, a cluster identifier, and an attribute identifier;
    the information determining module is used for determining second equipment information corresponding to the first equipment information based on the mapping relation;
    A data determining module, configured to determine state data of a BLE Mesh device to which the second device information belongs;
    the conversion module is used for converting the state data into corresponding attribute data;
    and the sending module is used for sending the attribute data to the terminal equipment.
  30. The apparatus of claim 29, wherein the first device information includes an endpoint and a cluster identity, and wherein the information determining module is configured to determine, based on the mapping relationship, an element identity corresponding to the endpoint and a model identity corresponding to the cluster identity;
    the data determining module is used for determining state data of a state corresponding to the model identifier.
  31. The apparatus of claim 29, wherein the first device information includes an endpoint, a cluster identifier, and an attribute identifier, and wherein the information determining module is configured to determine, based on the mapping relationship, an element identifier corresponding to the endpoint, a model identifier corresponding to the cluster identifier, and a state corresponding to the attribute identifier;
    the data determining module is used for determining state data of the state.
  32. The apparatus according to claim 30 or 31, wherein the information determining module is configured to determine at least one endpoint included in the endpoint list to which the endpoint belongs in the mapping relationship;
    The sending module is configured to send the at least one endpoint to the terminal device.
  33. The apparatus of claim 29, wherein the first device information includes an endpoint, a cluster identifier, and an attribute identifier, and wherein the information determining module is configured to determine, based on the mapping relationship, a main element identifier corresponding to the endpoint, an element identifier corresponding to the cluster identifier, and a model identifier corresponding to the attribute identifier;
    the data determining module is used for determining state data of a state corresponding to the model identifier.
  34. The apparatus of claim 29, wherein the first device information includes an endpoint and a cluster identifier, and wherein the information determining module is configured to determine, based on the mapping relationship, a main element identifier corresponding to the endpoint and an element identifier corresponding to the cluster identifier;
    the information determining module is used for determining each model identifier corresponding to the element identifier; and determining state data of the corresponding states of each model identifier.
  35. A bridging device, the bridging device comprising:
    a processor;
    a transceiver coupled to the processor;
    a memory for storing executable program code for the processor;
    Wherein the processor is configured to load and execute the executable program code to implement the connection establishment method of any of claims 1 to 17.
  36. A computer readable storage medium having stored therein executable program code loaded and executed by the processor to implement the connection establishment method of any of claims 1 to 17.
  37. A chip comprising programmable logic circuits and/or program instructions for implementing a connection establishment method as claimed in any of claims 1 to 17 when said chip is run on a bridging device.
  38. A computer program product for implementing a connection establishment method as claimed in any of the claims 1 to 17, when the computer program product is executed by a processor of a bridging device.
CN202080107383.6A 2020-12-04 2020-12-04 Connection establishment method, device, equipment and storage medium Pending CN116491222A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/134023 WO2022116191A1 (en) 2020-12-04 2020-12-04 Connection establishment method and apparatus, and device and storage medium

Publications (1)

Publication Number Publication Date
CN116491222A true CN116491222A (en) 2023-07-25

Family

ID=81853675

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202080107383.6A Pending CN116491222A (en) 2020-12-04 2020-12-04 Connection establishment method, device, equipment and storage medium

Country Status (2)

Country Link
CN (1) CN116491222A (en)
WO (1) WO2022116191A1 (en)

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9728021B2 (en) * 2014-09-16 2017-08-08 Honeywell International Inc. System and method for auto-configuration of devices in BIM using bluetooth low energy devices
CN104734893B (en) * 2015-04-02 2018-02-27 重庆邮电大学 A kind of TR069 protocol managerial approach towards WIA PA networks
CN107613501A (en) * 2017-09-28 2018-01-19 无锡商业职业技术学院 A kind of blueteeth network system for strengthening base station signal
CN110247940A (en) * 2018-03-08 2019-09-17 上海仪电（集团）有限公司中央研究院 Based on Zigbee and BLE protocol self-adapting intelligent gateway control system
CN108684071A (en) * 2018-04-25 2018-10-19 东峡大通（北京）管理咨询有限公司 The power consumption control method and system of the device node of MESH network
CN109922150A (en) * 2019-03-07 2019-06-21 深圳市简智联信息科技有限公司 Virtual device information processing method, device, gateway of internet of things and Internet of Things communication system

Also Published As

Publication number Publication date
WO2022116191A1 (en) 2022-06-09

Similar Documents

Publication Publication Date Title
CN107431651B (en) Life cycle management method and equipment for network service
EP2526734B1 (en) Hierarchical routing and interface selection for multi-processor multimode network devices
US7493377B2 (en) Method and apparatus to manage a configuration of clustered computers according to deployment date structures
CN101197812B (en) System and method for implementing page invocation
CN109324912B (en) Communication method of application management software oriented to software communication system structure
CN109104368B (en) Connection request method, device, server and computer readable storage medium
CN111767144B (en) Transaction route determination method, device, equipment and system for transaction data
CN111064626B (en) Configuration updating method, device, server and readable storage medium
CN110740057B (en) Service deployment method and block chain platform
CN114510452B (en) SOC (system on chip) integration method and device and electronic equipment
CN113296987B (en) Interface calling method and device for calling module, computer equipment and storage medium
CN103685535A (en) Interface design of cloud database system for large-scale distributed heterogeneous data treatment
CN111416723A (en) Equipment management method and related equipment
CN111338758A (en) Resource management method and device and electronic equipment
CN113225407A (en) Equipment identification information management method and device, electronic equipment and storage medium
CN111641669B (en) Dynamic load balancing in a network-centric process control system
CN104092661A (en) Serial port communication method and apparatus of virtual machines
CN110868374A (en) Security authentication method, server and client device
CN116491222A (en) Connection establishment method, device, equipment and storage medium
CN113556255B (en) Method and device for configuring smart home
CN113726578A (en) Fusion method of API gateway and network architecture system
CN112766486A (en) Searching method of neural network structure, terminal, server and readable storage medium
CN115943616A (en) Attribute subscription method, device and equipment of Zigbee equipment
WO2014176954A1 (en) Processing method, device and system for data of distributed storage system
CN112559199A (en) Device and method for controlling android Bluetooth in glibc environment and terminal equipment

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