Method and bridging device for bridging a mapping

Abstract

The application relates to a device bridge mapping method and a bridge device. The device bridge mapping method is applied to a home CHIP bridge device connected through an Internet protocol, and the method comprises the following steps: a mapping relationship between a CHIP device and a Bluetooth low energy (BLE) device is established. The CHIP bridge device comprises a first processing unit configured to establish the mapping relationship between the CHIP device and the BLE device. The embodiment of the application enables a CHIP network to access a device of a BLE network type, and enables a CHIP control device to interoperate with a BLE device.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method for device bridging mapping and a bridging device. Background Technology

[0002] Zigbee and Z-Wave technologies are widely used in some smart home devices. CHIP (Connected Home over IP Working Group) is a standard of the Zigbee Alliance's IP-based connected home working group. Current CHIP bridging solutions mainly include bridging between CHIP devices and Zigbee devices, as well as bridging between CHIP devices and Z-Wave devices. Summary of the Invention

[0003] This application provides a method and bridging device for device bridging mapping, which enables a CHIP network to access BLE network type devices.

[0004] This application provides a device bridging mapping method, applied to home CHIP bridging devices connected via Internet Protocol, the method including: establishing a mapping relationship between CHIP devices and Bluetooth Low Energy (BLE) devices.

[0005] This application provides a CHIP bridging device, including a mapping unit for establishing a mapping relationship between the CHIP device and a Bluetooth Low Energy (BLE) device.

[0006] This application provides a communication device including a processor and a memory. The memory stores a computer program, and the processor calls and runs the computer program stored in the memory to cause the communication device to perform the device bridging mapping method described above.

[0007] This application provides a chip for implementing the above-described device bridging mapping method.

[0008] Specifically, the chip includes a processor for calling and running a computer program from memory, causing a device equipped with the chip to perform the device bridging mapping method described above.

[0009] This application provides a computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the device bridging mapping method described above.

[0010] This application provides a computer program product including computer program instructions that cause a computer to execute the device bridging mapping method described above.

[0011] This application provides a computer program that, when run on a computer, causes the computer to perform the device bridging mapping method described above.

[0012] This application embodiment enables CHIP networks to access BLE network type devices. Attached Figure Description

[0013] Figure 1 This is a schematic diagram of a CHIP device model structure according to an embodiment of this application.

[0014] Figure 2 This is a schematic diagram of a CHIP bridging device structure according to an embodiment of this application.

[0015] Figure 3 This is a schematic diagram of a BLE device model structure according to an embodiment of this application.

[0016] Figure 4 This is a schematic flowchart of a device bridging mapping method according to an embodiment of this application.

[0017] Figure 5 This is a schematic diagram of a CHIP-to-BLE bridging method according to an embodiment of the device bridging mapping method of this application.

[0018] Figure 6 This is a schematic diagram of the mapping relationship of a device bridging mapping method according to an embodiment of this application.

[0019] Figure 7 This is a schematic flowchart illustrating a CHIP-to-BLE mapping technique according to an embodiment of the device bridging mapping method of this application.

[0020] Figure 8 This is a schematic diagram of the mapping relationship of a device bridging mapping method according to another embodiment of this application.

[0021] Figure 9 This is a schematic flowchart illustrating a CHIP-to-BLE mapping technique for a device bridging mapping method according to another embodiment of this application.

[0022] Figure 10 This is a schematic block diagram of a CHIP bridging device according to an embodiment of this application.

[0023] Figure 11 This is a schematic block diagram of a CHIP bridging device according to another embodiment of this application.

[0024] Figure 12 This is a schematic block diagram of a CHIP bridging device according to another embodiment of this application.

[0025] Figure 13 This is a schematic block diagram of a communication device according to an embodiment of this application.

[0026] Figure 14 This is a schematic block diagram of a chip according to an embodiment of this application.

[0027] Figure 15 This is a schematic block diagram of a communication system according to an embodiment of this application. Detailed Implementation

[0028] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0029] like Figure 1 The image shows an example of a CHIP device model structure. This CHIP device model is implemented based on the Zigbee Cluster Library (ZCL), and its structure is consistent with ZCL, with the addition of some Cluster definitions required by the CHIP protocol itself. This CHIP device model may include the following characteristics:

[0030] 1. A CHIP (Connected Home over IP Working Group) device can have multiple endpoints (ep), and the length of an ep value is 16 bits.

[0031] 2. Each endpoint represents a device. Each device can be identified by a device ID. Each endpoint may contain a cluster, and each cluster contains multiple attributes.

[0032] like Figure 2 The diagram shown illustrates the structure of a CHIP bridge device. The structure of a CHIP bridge device may include the following features:

[0033] 1. Bridged Device 1 and Bridged Device 2 represent non-CHIP (e.g., Zigbee, Z-Wave) protocol devices that establish secure Zigbee or Z-Wave connections with the Bridge device. The Bridge device can provide a secure communication link to each Bridged Device; act as an interpreter for the Bridged Devices, interpreting them as CHIP devices and presenting them to the CHIP App; and provide an accessible 'API / ' interface to the CHIP App.

[0034] 2. The length of the ep value of a CHIP protocol device can be 16-bit; a CHIP bridge device is a special CHIP device. After a Zigbee device is mapped through a CHIP bridge device, a one-to-one mapping relationship is established between the ep (8-bit, value range 1 to 254) of each Zigbee device and the ep (16-bit, value range 1 to 65534) in the CHIP bridge device.

[0035] 3. The CHIP protocol uses ZCL as the device model, and CHIP protocol devices and Zigbee protocol device clusters are mapped one-to-one.

[0036] 4. For example: A network physical Zigbee device (e.g., a power strip) securely accesses a bridge device and includes two endpoints, ep1 and ep2. After mapping through the bridge device, these endpoints are mapped to ep10, ep11 of the CHIP device.

[0037] Where ep1 can be Zigbee switch 1, corresponding to Figure 2 In the bridged device 1, ep5 can be the Zigbee switch 2. Figure 2 The bridged device 2; ep10 can be the switch 1 of the chip, corresponding to Figure 1 In CHIP Device 1, ep11 can be CHIP switch 2, corresponding to... Figure 2 CHIP Device 2.

[0038] 5. Vendor applications (APPs) can access the Bridge via the network.

[0039] 6. CHIP apps can access the mapped CHIP devices in the Bridge via the network. For example, each CHIP app can use the interface provided by CHIP to see and control all bridged devices through the CHIP Bridge.

[0040] like Figure 3 The diagram shown illustrates a Bluetooth Low Energy (BLE) device model structure. The BLE device model structure may include the following characteristics:

[0041] 1. A BLE physical device can consist of multiple services. Each service can be uniquely identified by a Universally Unique Identifier (UUID). Each service of a BLE physical device connected to a BLE network is assigned a different handler. Each service can include multiple characteristics. Each characteristic can also have a unique UUID identifier. Each characteristic is assigned a different handler from the network. Each characteristic includes a corresponding property value, also known as a characteristic value.

[0042] 2. A BLE physical device can include a master service, through which slave services can be found, and each service can include multiple services.

[0043] This application provides a method for bridging and mapping CHIP devices and BLE devices.

[0044] Figure 4 This is a schematic flowchart of a device bridging mapping method 200 according to an embodiment of this application. The method can optionally be applied to [various applications including...]. Figure 1 , Figure 2 , Figure 3 The system of the device shown is applicable, but not limited to. Exemplarily, the method can be applied to a CHIP bridging device, and the method may include at least a portion of the following.

[0045] S210. Establish the mapping relationship between CHIP devices and Bluetooth Low Energy (BLE) devices.

[0046] The CHIP bridging device and CHIP device in the embodiments of this application are not limited to devices that support the CHIP protocol, but may also include devices that support other protocols such as Zigbee and Z-Wave.

[0047] For example, a CHIP bridging device can establish a secure connection with a BLE device that needs to be controlled; then, the CHIP bridging device can establish a mapping relationship between the CHIP device and the BLE device. This allows the CHIP network to access BLE network type devices, enriching the types of devices that can be accessed in the CHIP ecosystem and enabling interoperability with different types of devices. For example, it enables CHIP control devices to interoperate with BLE devices. BLE devices can include various physical devices based on the BLE protocol. BLE devices can include physical devices in fields such as healthcare, sports and fitness, security, and home entertainment. Examples include blood pressure monitors, heart rate monitors, wristbands, and speakers.

[0048] Optionally, in embodiments of this application, the method further includes:

[0049] The CHIP device is created based on the mapping relationship between CHIP devices and BLE devices.

[0050] For example, after establishing a mapping relationship between a CHIP device and a BLE device, such as by storing the mapping relationship in a mapping table, a virtual CHIP device can be created based on this mapping relationship. The CHIP bridging device can create a virtual CHIP device under a certain endpoint, and the identifier of that endpoint can serve as the endpoint identifier of the virtual CHIP device. Furthermore, the cluster identifier under that endpoint can serve as the cluster identifier of the virtual CHIP device, and the attribute identifiers under the clusters included by that endpoint can serve as the attribute identifiers of the virtual CHIP device. For example, the CHIP bridging device creates a virtual CHIP device device1 under a certain endpoint ep1, and the endpoint identifier of device1 is ep1. If the endpoint ep1 includes clusters Cluster1 and Cluster2, and cluster1 includes attributes Attribute1 and Attribute2, and cluster2 includes attributes Attribute3 and Attribute4, then the cluster identifiers of device1 are Cluster1 and Cluster2, and the attribute identifiers under cluster1 of device1 are Attribute1 and Attribute2, and the attribute identifiers under cluster2 are Attribute3 and Attribute4.

[0051] Optionally, in this embodiment of the application, the CHIP bridging device includes a virtual client and a CHIP bridging function module, and the method further includes:

[0052] The virtual client

[0053] Optionally, in embodiments of this application, the method further includes:

[0054] Receive a first request from the CHIP control device, the first request including information about the target CHIP device;

[0055] Search for the information of the target BLE device that corresponds to the information of the target CHIP device in the mapping relationship between the CHIP device and the BLE device.

[0056] Based on the information of the target BLE device, a second request corresponding to the first request is sent to the target BLE device.

[0057] For example, after a virtual CHIP device establishes a secure connection with a CHIP control device, the CHIP control device can send a first request to the CHIP bridging device. The first request can be of various types, such as a read request, a write request, or a control request. This first request may include information about the target CHIP device. For example, it may include one or more of the target CHIP device's group endpoint identifier, endpoint identifier, cluster identifier, and attribute identifier. Based on the target CHIP device information in the first request, the CHIP bridging device can search for the corresponding target BLE device information in the CHIP device-BLE device mapping relationship. The target BLE device information may include one or more of the target BLE device's physical device address, service handler identifier, characteristic handler identifier, and characteristic value. After finding the target BLE device information, the CHIP bridging device can send a second request to the target BLE device based on the first request. For example, if the first request is a read request, the second request could be a data request used to obtain data from the target BLE device.

[0058] Optionally, in embodiments of this application, the method further includes:

[0059] Receive service data from the target BLE device;

[0060] Obtain the attribute data of the target CHIP device based on the service data of the target BLE device;

[0061] Return the attribute data of the target CHIP device to the CHIP control device.

[0062] For example, a CHIP bridging device can receive service data from the target BLE device. This service data might include multiple feature values ​​of a specific service from the target BLE device. The corresponding attribute values ​​of the target CHIP device can be obtained based on these feature values. For instance, a service might be a blood pressure service, which includes features such as pulse rate and cardiac contraction. A cluster corresponding to this service might contain attributes such as pulse rate, cardiac contraction, and unit measurement. When only a Cluster request is sent, based on the relationship between BLE features and CHIP attributes, two values—pulse rate and cardiac contraction—can be returned.

[0063] Optionally, in one embodiment of this application, the CHIP device includes an endpoint (ep), the endpoint includes a cluster, the cluster includes an attribute, and the mapping relationship between the CHIP device and the BLE device includes at least one of the following:

[0064] Mapping relationship between endpoint identifiers (ep IDs) of CHIP devices and BLE physical device addresses;

[0065] The mapping relationship between cluster IDs and service handler IDs in the endpoints of CHIP devices;

[0066] The mapping relationship between the attribute ID in the CHIP device cluster and the characteristic handler ID in the BLE service.

[0067] For example, the endpoint identifier ep1 of the CHIP device is mapped to the BLE physical device address XXXX; the cluster identifier Cluster1 of ep1 is mapped to the BLE service handler identifier Service Handler1; and the attribute identifier Attribute1 of Cluster1 is mapped to the characteristic handler identifier Characteristic Handler1 in the BLE service.

[0068] Optionally, there is a one-to-one correspondence between the endpoint identifier of the CHIP device and the BLE physical device address. There is a one-to-one correspondence between the cluster identifier in the CHIP device endpoint and the BLE service processor identifier. There is a one-to-one correspondence between the attribute identifier in the CHIP device cluster and the feature processor identifier in the BLE service.

[0069] Optionally, in one embodiment of this application, searching for the information of the target BLE device corresponding to the information of the target CHIP device in the mapping relationship between the CHIP device and the BLE device includes:

[0070] Search for the address of the target BLE device corresponding to the endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device;

[0071] Search for the service processor identifier corresponding to the cluster identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

[0072] For example, if the first request includes the endpoint identifier and cluster identifier of the target CHIP device, for example, the endpoint identifier is ep 1 and the cluster identifier is Cluster1, in the mapping relationship, the address XXXX of the target BLE device can be found based on the endpoint identifier ep 1, and the Service Handler1 of the target BLE device can be found based on the Cluster1.

[0073] Optionally, in the first embodiment of this application, searching for the information of the target BLE device corresponding to the information of the target CHIP device in the mapping relationship between the CHIP device and the BLE device further includes:

[0074] Search for the feature processor identifier that corresponds to the attribute identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

[0075] For example, if the first request includes an attribute identifier in addition to the endpoint identifier and cluster identifier of the target CHIP device, such as the endpoint identifier being ep 1, the cluster identifier being Cluster1, and the attribute identifier being Attribute1, in the mapping relationship, the CHIP bridging device can find the address XXXX of the target BLE device based on the endpoint identifier ep 1, find the Service Handler1 of the target BLE device based on the cluster identifier Cluster1, and find the Characteristic Handler1 of the target BLE device based on the attribute identifier Attribute1.

[0076] Optionally, in the second embodiment of this application, the CHIP device includes a group endpoint and an endpoint, the endpoint including a cluster, the cluster including attributes, and the mapping relationship between the CHIP device and the BLE device includes at least one of the following:

[0077] Mapping relationship between group endpoint identifiers of CHIP devices and BLE physical device addresses;

[0078] Mapping relationship between endpoint identifiers of CHIP devices and service processor identifiers of BLE;

[0079] The mapping relationship between cluster identifiers in the endpoints of CHIP devices and feature processor identifiers in BLE services;

[0080] Mapping relationship between attribute identifiers in a CHIP device cluster and BLE characteristic values.

[0081] For example, the group endpoint identifier group ep1 of the CHIP device is mapped to the BLE physical device address XXXX; the endpoint identifier ep2 of the CHIP device is mapped to the service handler identifier Service Handler2; the cluster identifier Cluster2 of ep2 is mapped to the BLE characteristic handler identifier Characteristic Handler2; and the attribute identifier Attribute2 of Cluster2 is mapped to the characteristic handler identifier CharacteristicValue2 in the BLE service.

[0082] Optionally, there is a one-to-one correspondence between the group endpoint identifier of the CHIP device and the BLE physical device address. There is a one-to-one correspondence between the endpoint identifier of the CHIP device and the service processor identifier of the BLE. There is a one-to-one correspondence between the cluster identifier of the CHIP device and the feature processor identifier of the BLE service. There is a one-to-one correspondence between the attribute identifier of the CHIP device and the feature value of the BLE.

[0083] Optionally, in the second embodiment of this application, searching for the information of the target BLE device corresponding to the information of the target CHIP device in the mapping relationship between the CHIP device and the BLE device includes:

[0084] The address of the target BLE device corresponding to the group endpoint identifier in the first request is found in the mapping relationship between the CHIP device and the BLE device.

[0085] For example, if the first request includes the group endpoint identifier group ep 1 of the target CHIP device, the CHIP bridging device can find the address XXXX of the target BLE device based on the group endpoint identifier group ep 1 in the mapping relationship.

[0086] Optionally, in the second embodiment of this application, the method further includes:

[0087] Return an endpoint list to the CHIP control device, which includes endpoint identifiers corresponding to the service processor identifiers of BLE.

[0088] For example, the CHIP bridging device can return a list of endpoints to the CHIP control device. This list may include multiple endpoint identifiers, such as ep1, ep2, and ep3. The CHIP control device can then display this list, allowing the user to select a specific cluster of an endpoint. For instance, if the user selects Cluster2 of ep2, the CHIP control device can send a first request to the CHIP bridging device again. This first request may include the endpoint identifier ep2 and the cluster identifier Cluster2.

[0089] Optionally, in the second embodiment of this application, searching for the information of the target BLE device corresponding to the information of the target CHIP device in the mapping relationship between the CHIP device and the BLE device further includes:

[0090] Search for the service processor identifier corresponding to the endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device;

[0091] Search for the feature processor identifier corresponding to the cluster identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

[0092] For example, if the first request received may include endpoint identifier ep2 and cluster identifier Cluster2, the CHIP bridging device can find the target BLE device's Service Handler2 based on ep2 in the mapping relationship, and find the target BLE device's Characteristic Handler2 based on the cluster identifier Cluster2.

[0093] Optionally, in the second embodiment of this application, searching for the information of the target BLE device corresponding to the information of the target CHIP device in the mapping relationship between the CHIP device and the BLE device further includes:

[0094] Search for the feature value corresponding to the attribute identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

[0095] For example, if the first request received also includes attribute identifier Attribute 2, the CHIP bridging device can find the characteristic value 2 of the target BLE device in the mapping relationship based on attribute identifier Attribute 2.

[0096] Optionally, in embodiments of this application, the method further includes:

[0097] If the first request includes an attribute identifier, a data request corresponding to that attribute identifier is initiated to the service or feature of the BLE device.

[0098] For example, based on method one, the first request includes a cluster identifier (cluster1) and an attribute identifier (Attribute1). The CHIP bridging device can initiate a data request to the service or feature of the target BLE device based on the mapping relationship between the attribute identifier (Attribute1) and the feature handler (CharacteristicHandler1).

[0099] For example, based on method two, the first request includes a cluster identifier (cluster2) and an attribute identifier (Attribute2). The CHIP bridging device can initiate a data request to the service or feature of the target BLE device based on the mapping relationship between the attribute identifier (Attribute2) and the feature processor (CharacteristicValue2).

[0100] Optionally, in embodiments of this application, the method further includes:

[0101] If the first request does not include attribute identifiers, a set of data requests is obtained based on the attribute identifiers corresponding to the cluster identifiers in the first request.

[0102] For example, based on Method 1, the first request includes a cluster identifier (cluster1), but does not include specific attribute identifiers. This cluster1 includes multiple attribute identifiers: Attribute1, Attribute3, and Attribute5. The CHIP bridging device can obtain multiple corresponding state data requests based on the mapping relationship between these attribute identifiers (Attribute1, Attribute3, Attribute5) and feature handlers (Characteristic Handler1, Characteristic Handler3, Characteristic Handler5). Then, the CHIP bridging device can initiate these multiple state data requests to the services or features of the target BLE device.

[0103] For example, based on method two, the first request includes a cluster identifier (cluster2), but does not include specific attribute identifiers. This cluster2 includes multiple attribute identifiers: Attribute2, Attribute4, and Attribute6. The CHIP bridging device can obtain multiple corresponding state data requests based on the mapping relationship between these attribute identifiers (Attribute2, Attribute4, Attribute6) and characteristic values ​​(CharacteristicValue2, Characteristic Value4, Characteristic Value6). Then, the CHIP bridging device can initiate these multiple state data requests to the services or characteristics of the target BLE device.

[0104] In one application scenario, in order to enable CHIP networks to access devices of different network types, embodiments of this application provide a bridging mapping scheme from CHIP devices to BLE devices based on CHIP bridging technology.

[0105] For example, the bridging method from a CHIP device to a BLE device is as follows: Figure 5 As shown. BLE devices, such as BLE device 1 and BLE device 2, are connected to a bridge device via a BLE network. The bridge device can provide a secure communication link to each BLE device and also act as an interpreter for the BLE devices, presenting them as CHIP devices to the CHIP app. Vendor apps can connect to the CHIP network through vendor-defined interfaces. CHIP devices, such as CHIP device 1 and CHIP device 2, access the CHIP network. CHIP apps can also access the CHIP network; for example, CHIP app 1, CHIP app 2, and CHIP app 3 can all access the CHIP network. Each CHIP app can use the interfaces provided by CHIP to see and control all BLE devices through the CHIP bridge device.

[0106] Solution Example 1:

[0107] like Figure 6 As shown, an exemplary mapping relationship (also known as a correspondence) between a CHIP device and a BLE device may include:

[0108] The BLE physical device address maintains a one-to-one relationship with the endpoint (ep) of the CHIP bridge device;

[0109] In BLE, a service maintains a one-to-one relationship with a cluster in the CHIP bridging device;

[0110] In BLE, the characteristics of a service are linked to the attributes of an endpoint in the CHIP bridging device in a one-to-one relationship.

[0111] like Figure 7 The diagram shown is a flowchart of Example 1 of a CHIP-to-BLE mapping scheme. This process may include:

[0112] S11, a secure connection has been established between the BLE Master and the BLE Slave; the BLE Master can be a virtual client in the CHIP bridging device used to establish a connection with the BLE physical device, and the BLE Slave is the BLE physical device.

[0113] S12, the BLE master device sends a request to the CHIP bridging module to establish a mapping relationship.

[0114] S13. CHIP bridging module establishes a mapping relationship table: It establishes a mapping relationship between the CHIP Bridge's ep identifier and the BLE physical device address, establishes a mapping relationship between the CHIP device's cluster ID and the BLE's service handler ID, and establishes a mapping relationship between the CHIP's attribute ID and the BLE's characteristic handler ID.

[0115] S14. The CHIP bridging function module initiates a request to create a CHIP device based on the mapping relationship.

[0116] S15. Create a CHIP device corresponding to the BLE device; this CHIP device can be a virtual device in a CHIP bridging device.

[0117] S16. The CHIP controller establishes a secure communication connection with the CHIP device;

[0118] S17. The CHIP control device sends a read request to the CHIP device. This request may include one or more of the following: ep identifier, Cluster ID, and Attribute ID. For example, if the read request includes a Cluster ID, it is a read cluster request. If the read request includes both a Cluster ID and an Attribute ID, it is a read attribute request. A read request is just one example; other types of requests, such as write requests and control requests, are also possible.

[0119] S18. The CHIP device sends a request to the CHIP bridging function module to resolve the mapping relationship; and it can send one or more of the received ep identifier, Cluster ID, and Attribute ID to the CHIP bridging function module.

[0120] S19. The CHIP bridging module retrieves information about the corresponding BLE device based on one or more of the received ep identifier, Cluster ID, and Attribute ID. The ep identifier can be 16 bits. For example, if the ep identifier and Cluster ID are received, the module finds the corresponding BLE address in the mapping relationship based on the ep identifier, and the Characteristic Handler ID in the mapping relationship based on the Attribute ID. If the ep identifier, Cluster ID, and attribute information are received, the module finds the corresponding BLE address in the mapping relationship based on the ep identifier, the corresponding ServiceHandler ID in the mapping relationship based on the Cluster ID, and the Characteristic Handler ID in the mapping relationship based on the Attribute ID.

[0121] S20. After resolving the mapping relationship, the CHIP bridging module can initiate access to the Service / characteristic through the BLE master device. For example, if the received read request includes an attributeID, a request to read the data corresponding to the attributeID can be initiated to the service / characteristic. Alternatively, if the received read request does not contain an attributeID, a set of data requests can be obtained based on the mapping relationship between all AttributeIDs corresponding to the Cluster ID in the read request and the CharacteristicHandler.

[0122] S21. In the bridging device, the BLE master device sends a request to the BLE slave device's Service to read data.

[0123] S22. The BLE slave device returns the Service data corresponding to the read request to the BLE master device.

[0124] S23. The BLE master device returns the Service data corresponding to the read request to the CHIP bridging module, and the CHIP bridging module converts the Service data into attribute data of the CHIP device; for example, the CHIP bridging module fills in the attribute value of the cluster corresponding to the Service Handler according to the mapping relationship.

[0125] S24. The CHIP bridging module returns this attribute data to the CHIP device.

[0126] S25. The CHIP device returns this attribute data to the CHIP control device.

[0127] Solution Example 2:

[0128] like Figure 8 As shown, an exemplary mapping relationship between a CHIP device and a BLE device may include:

[0129] CHIP to BLE mapping relationship 2 explanation:

[0130] The BLE physical device address maintains a one-to-one relationship with the group ep of the CHIP bridge device;

[0131] In BLE, a service maintains a one-to-one relationship with an eP in the CHIP bridge device;

[0132] The characteristics of a service in BLE are mapped to the clusters in the ep of the CHIP bridging device;

[0133] In BLE, the property value of a characteristic is mapped to the attribute in the cluster of the CHIP bridging device.

[0134] like Figure 9 The diagram shown is a flowchart of Example 2 of the CHIP-to-BLE mapping scheme. This process may include:

[0135] The main differences between Scheme Example 2 and Scheme Example 1 include the different mapping methods.

[0136] S31, S32, S34, S35, and S36 of Scheme Example 2 are the same as S11, S12, S14, S15, and S16 of Scheme Example 1. Furthermore, the main differences between Scheme Example 2 and Scheme Example 1 also include:

[0137] In S33, the CHIP bridging module establishes a mapping table, which may include: establishing a mapping relationship between a group endpoint ID (group ep ID) in the CHIP Bridge device and the BLE physical device address; establishing a mapping relationship between the CHIP Bridge device's ep identifier and the BLE Service Handler ID; establishing a mapping relationship between the Cluster ID under the CHIP Bridge device's ep and the Characteristic Handler ID under the BLE Service; and establishing a mapping relationship between the Attribute ID and Property Value under the CHIP Bridge device's Cluster. For example, the group ep of the CHIP Bridge device, 0x0010, corresponds to the actual BLE physical device address. This BLE physical device has two Services, corresponding to 0x0011 and 0x0012 on the CHIP Bridge device, respectively. The Characteristics under these two Services correspond to the CHIP Bridge device's Cluster, and the Property Values ​​under these Characteristics correspond to the Attributes under the CHIP Bridge device's Cluster.

[0138] In S37, the CHIP control device can issue a read request to group ep:0x0010 of the CHIP bridge device.

[0139] In S38, the CHIP device sends a request to the CHIP bridging function module to resolve the mapping relationship; and it can send the received group ep identifier to the CHIP bridging function module.

[0140] In S39, the CHIP bridging module can look up the corresponding relationship between BLE physical devices in the mapping table based on the requested group ep identifier.

[0141] In S40, the CHIP bridging function module of the CHIP bridging device returns a list of group ep to the virtual CHIP device.

[0142] In S41, the CHIP device can return an EP list to the CHIP control device. The EP list can include EP identifier information corresponding to the BLE Service. For example, the Service Handler ID corresponding to EP1, and the Service Handler ID corresponding to EP2.

[0143] In S42, the CHIP control device sends a READ request to the CHIP device's ep / cluster or to the ep / cluster / attribute. The READ request may include one or more of the following: group ep identifier, ep identifier, Cluster ID, and Attribute ID.

[0144] In S43, the CHIP device sends a request to the CHIP bridging function module to resolve the mapping relationship; and it can send one or more of the received group ep identifier, ep identifier, Cluster ID, and Attribute ID to the CHIP bridging function module.

[0145] In S44, the CHIP bridging module looks up the BLE device information based on the requested CHIP device information. For example, it finds the corresponding BLE Service Handler ID from the mapping relationship based on the ep identifier, finds the corresponding Characteristic Handler ID based on the Cluster ID, and finds the corresponding Property Value based on the Attribute ID.

[0146] In S45, the CHIP bridging module initiates read data requests through the BLE master device. For example, if the received read request includes an attribute ID, a read request for the data corresponding to the attribute ID can be initiated to service / characteristic / value. Conversely, if the received read request does not contain an attribute ID, a set of status data requests can be obtained based on all mappings between ClusterID and CharacteristicValue in the read request.

[0147] In S46, a request to read data is sent to the service / characteristic of the BLE Slave.

[0148] In S47, the BLE slave device returns the Service data corresponding to the read request to the BLE master device.

[0149] In S48, the BLE master device returns the Service data corresponding to the read request to the CHIP bridging module, and the CHIP bridging module converts the Service data (e.g., the Service's characteristic value) into the attribute data of the CHIP device; for example, the CHIP bridging module fills in the attribute value of the corresponding cluster of the Characteristic Handler according to the mapping relationship.

[0150] In S49, the CHIP bridging module returns this attribute data to the CHIP device.

[0151] In S50, the CHIP device returns this attribute data to the CHIP control device.

[0152] Example 2 can be used when a characteristic has multiple attributes (value). If a characteristic has only a single attribute (value), Example 1 can be used.

[0153] This application embodiment enables CHIP networks to access BLE network type devices, enriching the types of devices accessible in the CHIP ecosystem. CHIP devices can interoperate with different types of devices, such as BLE devices.

[0154] Figure 10 This is a schematic block diagram of a CHIP bridging device 400 according to an embodiment of this application. The CHIP bridging device 400 may include:

[0155] The first processing unit 410 is used to establish a mapping relationship between the CHIP device and the Bluetooth Low Energy (BLE) device.

[0156] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to create the CHIP device based on the mapping relationship between the CHIP device and the BLE device.

[0157] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to establish a secure connection with the CHIP control device through the CHIP device.

[0158] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to receive a first request from the CHIP control device, the first request including information about the target CHIP device; and search for information about the target BLE device corresponding to the information of the target CHIP device in the mapping relationship between the CHIP device and the BLE device.

[0159] like Figure 11 As shown, the CHIP bridging device 400 further includes a second processing unit 420, configured to send a second request corresponding to the first request to the target BLE device based on the information of the target BLE device.

[0160] Optionally, in this embodiment of the application, the second processing unit 420 is further configured to receive service data from the target BLE device;

[0161] The first processing unit 420 is further configured to obtain the attribute data of the target CHIP device based on the service data of the target BLE device; and return the attribute data of the target CHIP device to the CHIP control device.

[0162] Optionally, in this embodiment of the application, referring to the first method embodiment described above, the CHIP device includes an endpoint, the endpoint includes a cluster, the cluster includes attributes, and the mapping relationship between the CHIP device and the BLE device includes at least one of the following:

[0163] Mapping relationship between endpoint identifiers of CHIP devices and BLE physical device addresses;

[0164] Mapping relationship between cluster identifiers in the endpoints of a CHIP device and service processor identifiers for BLE;

[0165] Mapping relationship between attribute identifiers in the CHIP device's cluster and feature processor identifiers in BLE services.

[0166] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to search for the address of the target BLE device corresponding to the endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device; and to search for the service processor identifier corresponding to the cluster identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

[0167] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to search for a feature processor identifier corresponding to the attribute identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

[0168] Optionally, in this embodiment of the application, referring to the second method embodiment described above, the CHIP device includes a group endpoint and an endpoint, the endpoint includes a cluster, the cluster includes attributes, and the mapping relationship between the CHIP device and the BLE device includes at least one of the following:

[0169] Mapping relationship between group endpoint identifiers of CHIP devices and BLE physical device addresses;

[0170] Mapping relationship between endpoint identifiers of CHIP devices and service processor identifiers of BLE;

[0171] The mapping relationship between cluster identifiers in the endpoints of CHIP devices and feature processor identifiers in BLE services;

[0172] Mapping relationship between attribute identifiers and BLE characteristic values ​​in the cluster of CHIP devices.

[0173] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to search for the address of the target BLE device corresponding to the group endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

[0174] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to return an endpoint list to the CHIP control device, the endpoint list including endpoint identifiers corresponding to the service processor identifiers of BLE.

[0175] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to search for a service processor identifier corresponding to the endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device; and to search for a feature processor identifier corresponding to the cluster identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

[0176] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to search for a feature value corresponding to the attribute identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

[0177] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to, when the first request includes an attribute identifier, initiate a data request corresponding to the attribute identifier to the service or feature of the BLE device.

[0178] Optionally, in this embodiment of the application, the first processing unit 410 is further configured to obtain a set of data requests based on each attribute identifier corresponding to the cluster identifier in the first request if the first request does not include an attribute identifier.

[0179] The CHIP bridging device 400 of this application embodiment can realize the corresponding functions of the CHIP bridging device in the foregoing method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the CHIP bridging device 400 can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the CHIP bridging device 400 of this application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0180] Figure 12This is a schematic block diagram of a CHIP bridging device 500 according to an embodiment of this application. The CHIP bridging device 500 can be any of the modules (sub-modules, units, or components, etc.) of the CHIP bridging device described in the above embodiment. Optionally, in this embodiment, the CHIP bridging device 500 further includes a virtual client 510 and a CHIP bridging function module 520. The virtual client 510 can implement the functions of the second processing unit described above.

[0181] Virtual client 510 is used to establish a secure connection with BLE devices; it sends a mapping relationship establishment request to the CHIP bridging module 520.

[0182] The CHIP bridging module 520 is used to receive the request to establish the mapping relationship.

[0183] Optionally, in this embodiment of the application, the CHIP bridging function module 520 is also used to establish a mapping relationship between the CHIP device and the BLE device.

[0184] Optionally, in this embodiment of the application, the CHIP bridging function module 520 is further used to create a virtual CHIP device 530 based on the mapping relationship between the CHIP device and the BLE device;

[0185] The CHIP bridging device 500 also includes the virtual CHIP device 530. The CHIP bridging module 520 and the virtual CHIP device 530 can implement the functions of the first processing unit.

[0186] For example, after receiving a mapping relationship establishment request from the virtual client 510, the CHIP bridging module 520 establishes a mapping relationship between the CHIP device and the BLE device, and based on this mapping relationship, a virtual CHIP device 530 can be created. Then, the virtual CHIP device 530 establishes a secure connection with the CHIP control device. The virtual CHIP device 530 receives a first request from the CHIP control device, parses the first request, and sends it to the CHIP bridging module 520. Based on the first request, the CHIP bridging module 520 searches for the information of the target BLE device corresponding to the information of the target CHIP device in the mapping relationship between the CHIP device and the BLE device. After finding the information of the target BLE device, the CHIP bridging module 520 can send a data request to the virtual client, which then initiates a second request to the BLE device's services or features. The virtual client can forward service data received from the BLE device to the CHIP bridging module 520, which then obtains the attribute data of the CHIP device and sends it to the CHIP control device through the virtual CHIP device.

[0187] The CHIP bridging device 500 of this application embodiment can realize the corresponding functions of the CHIP bridging device in the foregoing method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the CHIP bridging device 500 can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the CHIP bridging device 500 of this application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0188] Figure 13 This is a schematic structural diagram of a communication device 600 according to an embodiment of this application. The communication device 600 includes a processor 610, which can call and run computer programs from memory to enable the communication device 600 to implement the methods in the embodiments of this application.

[0189] Optionally, the communication device 600 may further include a memory 620. The processor 610 can retrieve and run computer programs from the memory 620 to enable the communication device 600 to implement the methods described in the embodiments of this application.

[0190] The memory 620 can be a separate device independent of the processor 610, or it can be integrated into the processor 610.

[0191] Optionally, the communication device 600 may also include a transceiver 630, which the processor 610 can control to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.

[0192] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

[0193] Optionally, the communication device 600 may be a CHIP bridging device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the CHIP bridging device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0194] Figure 14 This is a schematic structural diagram of a chip 700 according to an embodiment of this application. The chip 700 includes a processor 710, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0195] Optionally, the chip 700 may further include a memory 720. The processor 710 can retrieve and run computer programs from the memory 720 to implement the method executed by the CHIP bridging device in this embodiment.

[0196] The memory 720 can be a separate device independent of the processor 710, or it can be integrated into the processor 710.

[0197] Optionally, the chip 700 may also include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0198] Optionally, the chip 700 may also include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0199] Optionally, the chip can be applied to the CHIP bridging device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the CHIP bridging device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0200] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0201] The processors mentioned above can be general-purpose processors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processors mentioned above can be microprocessors or any conventional processor.

[0202] The aforementioned memory can be volatile memory or non-volatile memory, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM).

[0203] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0204] Figure 15 This is a schematic block diagram of a communication system 800 according to an embodiment of this application. The communication system 800 includes a CHIP bridging device 810. The CHIP bridging device 810 is used to establish a mapping relationship between CHIP devices and BLE devices.

[0205] Optionally, the system may also include a CHIP control device 820 and a BLE device 830.

[0206] Specifically, the CHIP bridging device 810 can be used to implement the corresponding functions implemented by the CHIP bridging device in the above method, the CHIP control device 820 can be used to implement the corresponding functions implemented by the CHIP control device in the above method, and the BLE device 830 can be used to implement the corresponding functions implemented by the BLE physical device in the above method. For the sake of brevity, further details are omitted here.

[0207] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0208] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0209] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0210] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for device bridging mapping, applied to a home CHIP bridging device connected via Internet Protocol, the method comprising: Establish a mapping relationship between CHIP devices and Bluetooth Low Energy (BLE) devices; The method further includes: The CHIP device is created based on the mapping relationship between CHIP devices and BLE devices; The method further includes: A secure connection is established between the CHIP device and the CHIP control device. Receive a first request from the CHIP control device, wherein the first request includes information about the target CHIP device; Search for the information of the target BLE device that corresponds to the information of the target CHIP device in the mapping relationship between CHIP devices and BLE devices; Based on the information of the target BLE device, a second request corresponding to the first request is sent to the target BLE device; Receive service data from the target BLE device; Obtain the attribute data of the target CHIP device based on the service data of the target BLE device; Return the attribute data of the target CHIP device to the CHIP control device.

2. The method according to claim 1, wherein, Searching for the target BLE device information corresponding to the target CHIP device information in the CHIP device-BLE device mapping relationship includes: Search for the address of the target BLE device corresponding to the endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device; Search for the service processor identifier corresponding to the cluster identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

3. The method according to claim 2, wherein, The process of searching for the target BLE device information corresponding to the target CHIP device information in the CHIP device-BLE device mapping relationship also includes: Search for the feature processor identifier corresponding to the attribute identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

4. The method according to any one of claims 1 to 3, wherein, The CHIP device includes group endpoints and endpoints, the endpoints include clusters, the clusters include attributes, and the mapping relationship between the CHIP device and the BLE device includes at least one of the following: Mapping relationship between group endpoint identifiers of CHIP devices and BLE physical device addresses; Mapping relationship between endpoint identifiers of CHIP devices and service processor identifiers of BLE; The mapping relationship between cluster identifiers in the endpoints of CHIP devices and feature processor identifiers in BLE services; Mapping relationship between attribute identifiers and BLE characteristic values ​​in the cluster of CHIP devices.

5. The method according to claim 1, wherein, Searching for the target BLE device information corresponding to the target CHIP device information in the CHIP device-BLE device mapping relationship includes: Search for the address of the target BLE device that corresponds to the group endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

6. The method according to claim 5, wherein, The method further includes: Return an endpoint list to the CHIP control device, the endpoint list including endpoint identifiers corresponding to the service processor identifiers of BLE.

7. The method according to claim 5, wherein, The process of searching for the target BLE device information corresponding to the target CHIP device information in the CHIP device-BLE device mapping relationship also includes: Search for the service processor identifier corresponding to the endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device; Search for the feature processor identifier corresponding to the cluster identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

8. The method according to claim 7, wherein, Searching for the information of the target BLE device corresponding to the information of the target CHIP device in the mapping relationship between CHIP devices and BLE devices further includes: Search for the feature value corresponding to the attribute identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

9. The method according to any one of claims 1 to 2, 5 to 8, wherein, The CHIP device includes an endpoint, the endpoint includes a cluster, the cluster includes attributes, and the mapping relationship between the CHIP device and the BLE device includes at least one of the following: Mapping relationship between endpoint identifiers of CHIP devices and BLE physical device addresses; Mapping relationship between cluster identifiers in the endpoints of a CHIP device and service processor identifiers for BLE; Mapping relationship between attribute identifiers in the CHIP device's cluster and feature processor identifiers in BLE services.

10. The method according to claim 3 or 8, wherein, The method further includes: If the first request includes an attribute identifier, a data request corresponding to the attribute identifier is initiated to the service or feature of the BLE device.

11. The method according to claim 2 or 7, wherein, The method further includes: If the first request does not include attribute identifiers, a set of data requests is obtained based on the attribute identifiers corresponding to the cluster identifiers in the first request.

12. The method according to any one of claims 1 to 3 or 5 to 8, wherein, The CHIP bridging device includes a virtual client and a CHIP bridging function module, and the method further includes: The virtual client establishes a secure connection with the BLE device; The virtual client sends a mapping relationship establishment request to the CHIP bridging function module.

13. The method according to claim 12, wherein, Establish the mapping relationship between CHIP devices and BLE devices, including: In the CHIP bridging function module, a mapping relationship between CHIP devices and BLE devices is established.

14. The method according to claim 12, wherein, The CHIP device is created based on the mapping relationship between CHIP devices and BLE devices, including: The CHIP bridging module creates a virtual CHIP device based on the mapping relationship between the CHIP device and the BLE device, and the CHIP bridging device also includes the CHIP device.

15. A chip bridging device, comprising: The first processing unit is used to establish the mapping relationship between CHIP devices and Bluetooth Low Energy (BLE) devices; The first processing unit is further configured to create the CHIP device based on the mapping relationship between the CHIP device and the Bluetooth Low Energy (BLE) device; The first processing unit is also used to establish a secure connection between the CHIP device and the CHIP control device. The first processing unit is further configured to receive a first request from the CHIP control device, the first request including information about the target CHIP device; and search for information about the target BLE device corresponding to the information of the target CHIP device in the mapping relationship between the CHIP device and the BLE device. The device further includes: a second processing unit, configured to send a second request corresponding to the first request to the target BLE device based on the information of the target BLE device; The second processing unit is further configured to receive service data from the target BLE device; the first processing unit is further configured to obtain attribute data of the target CHIP device based on the service data of the target BLE device; and return the attribute data of the target CHIP device to the CHIP control device.

16. The device according to claim 15, wherein, The first processing unit is further configured to search for the address of the target BLE device corresponding to the endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device; and to search for the service processor identifier corresponding to the cluster identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

17. The device according to claim 16, wherein, The first processing unit is further configured to search for a feature processor identifier corresponding to the attribute identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

18. The device according to any one of claims 15 to 17, wherein, The CHIP device includes an endpoint, the endpoint includes a cluster, the cluster includes attributes, and the mapping relationship between the CHIP device and the BLE device includes at least one of the following: Mapping relationship between endpoint identifiers of CHIP devices and BLE physical device addresses; Mapping relationship between cluster identifiers in the endpoints of a CHIP device and service processor identifiers for BLE; Mapping relationship between attribute identifiers in the CHIP device's cluster and feature processor identifiers in BLE services.

19. The device according to claim 15, wherein, The first processing unit is further configured to search for the address of the target BLE device corresponding to the group endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

20. The device according to claim 19, wherein, The first processing unit is also configured to return an endpoint list to the CHIP control device, the endpoint list including endpoint identifiers corresponding to the service processor identifiers of BLE.

21. The device according to claim 19, wherein, The first processing unit is further configured to search for a service processor identifier corresponding to the endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device; and to search for a feature processor identifier corresponding to the cluster identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

22. The device according to claim 21, wherein, The first processing unit is further configured to search for a feature value corresponding to the attribute identifier in the first request in the mapping relationship between the CHIP device and the BLE device.

23. The device according to any one of claims 15 to 16, 19 to 22, wherein, The CHIP device includes group endpoints and endpoints, the endpoints include clusters, the clusters include attributes, and the mapping relationship between the CHIP device and the BLE device includes at least one of the following: Mapping relationship between group endpoint identifiers of CHIP devices and BLE physical device addresses; Mapping relationship between endpoint identifiers of CHIP devices and service processor identifiers of BLE; The mapping relationship between cluster identifiers in the endpoints of CHIP devices and feature processor identifiers in BLE services; Mapping relationship between attribute identifiers and BLE characteristic values ​​in the cluster of CHIP devices.

24. The device according to claim 17 or 22, wherein, The first processing unit is further configured to, when the first request includes an attribute identifier, initiate a data request corresponding to the attribute identifier to a service or feature of the BLE device.

25. The device according to claim 16 or 21, wherein, The first processing unit is further configured to obtain a set of data requests based on the attribute identifiers corresponding to the cluster identifiers in the first request, if the first request does not include attribute identifiers.

26. The device according to any one of claims 15 to 17 and 19 to 22, wherein, The CHIP bridging device also includes: The virtual client is used to establish a secure connection with BLE devices; it sends a mapping relationship establishment request to the CHIP bridging module. The CHIP bridging module is used to receive the mapping relationship establishment request.

27. The device according to claim 26, wherein, The CHIP bridging module is also used to establish a mapping relationship between CHIP devices and BLE devices.

28. The device according to claim 26, wherein, The CHIP bridging module is also used to create a virtual CHIP device based on the mapping relationship between the CHIP device and the BLE device; The CHIP bridging device also includes the CHIP device.

29. A communication device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 14.

30. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 14.

31. A computer-readable storage medium for storing a computer program that causes a computer to perform the method as described in any one of claims 1 to 14.

32. A computer program product comprising computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 14.

Images