WO2022120545A1

WO2022120545A1 - Device bridging mapping method and bridging device

Info

Publication number: WO2022120545A1
Application number: PCT/CN2020/134366
Authority: WO
Inventors: 包永明; 茹昭
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-12-07
Filing date: 2020-12-07
Publication date: 2022-06-16
Also published as: CN116547997A

Abstract

The present application relates to a device bridging mapping method and a bridging device. The device bridging mapping method is applied to a Connected Home over IP Working Group (CHIP) bridging device, and said method comprises: establishing a mapping relationship between a CHIP device and a Bluetooth low energy (BLE) device. The CHIP bridging device comprises: a first processing unit, configured to establish a mapping relationship between the CHIP device and the BLE device. The embodiments of the present application enable a CHIP network to access a device of a BLE network type, and enable a CHIP control device to interoperate with the BLE device.

Description

Device bridging mapping method and bridging device

technical field

The present application relates to the field of communications, and more particularly, to a device bridging mapping method and bridging device.

Background technique

Zigbee and Z-Wave technologies are widely used in some smart home devices. CHIP (Connected Home over IP Working Group) is a standard for connecting home working groups over IP under the Zigbee Alliance. In the current CHIP bridge (Bridge) solution, it mainly includes the bridge between the CHIP device and the Zigbee device and the bridge between the CHIP device and the Z-Wave device.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a device bridging mapping method and a bridging device, which can enable a CHIP network to access a BLE network type device.

An embodiment of the present application provides a device bridging mapping method, which is applied to connecting a home CHIP bridging device through an Internet protocol. The method includes: establishing a mapping relationship between a CHIP device and a Bluetooth low energy BLE device.

An embodiment of the present application provides a CHIP bridging device, including: a mapping unit configured to establish a mapping relationship between the CHIP device and the Bluetooth low energy BLE device.

Embodiments of the present application provide a communication device including a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, so that the communication device executes the above-mentioned method for device bridging mapping.

An embodiment of the present application provides a chip for implementing the foregoing method for device bridge mapping.

Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device installed with the chip executes the above-mentioned method for device bridge mapping.

Embodiments of the present application provide a computer-readable storage medium for storing a computer program, and when the computer program is run by a device, the device enables the device to execute the above-mentioned method for device bridging mapping.

An embodiment of the present application provides a computer program product, including computer program instructions, where the computer program instructions cause a computer to execute the above-mentioned method for device bridging mapping.

An embodiment of the present application provides a computer program, which, when running on a computer, enables the computer to execute the above-mentioned method for device bridging mapping.

This embodiment of the present application enables the CHIP network to access devices of the BLE network type.

Description of drawings

FIG. 1 is a schematic structural diagram of a CHIP device model according to an embodiment of the present application.

FIG. 2 is a schematic diagram of a structure of a CHIP bridge (Bridge) device according to an embodiment of the present application.

FIG. 3 is a schematic structural diagram of a BLE device model according to an embodiment of the present application.

FIG. 4 is a schematic flowchart of a method for device bridging mapping according to an embodiment of the present application.

FIG. 5 is a schematic diagram of a CHIP-to-BLE bridging manner of a device bridging mapping method according to an embodiment of the present application.

FIG. 6 is a schematic diagram of a mapping relationship of a method for device bridging mapping according to an embodiment of the present application.

FIG. 7 is a schematic flowchart of a CHIP-to-BLE mapping technical solution of a method for device bridging mapping according to an embodiment of the present application.

FIG. 8 is a schematic diagram of a mapping relationship of a method for device bridging mapping according to another embodiment of the present application.

FIG. 9 is a schematic flowchart of a CHIP-to-BLE mapping technical solution of a method for device bridging mapping according to another embodiment of the present application.

FIG. 10 is a schematic block diagram of a CHIP bridging device according to an embodiment of the present application.

FIG. 11 is a schematic block diagram of a CHIP bridging device according to another embodiment of the present application.

FIG. 12 is a schematic block diagram of a CHIP bridging device according to another embodiment of the present application.

FIG. 13 is a schematic block diagram of a communication device according to an embodiment of the present application.

FIG. 14 is a schematic block diagram of a chip according to an embodiment of the present application.

FIG. 15 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed ways

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, which all belong to the embodiments of the present application. protected range.

As shown in Figure 1, it is an example of the structure of a CHIP device model. The CHIP device model is implemented based on Zigbee Cluster Library (ZCL). The model structure is consistent with ZCL, and some CHIP protocol needs to be added. The Cluster definition, etc. The CHIP device model can include the following features:

1. CHIP (Connected Home over IP Working Group, under the Zigbee Alliance) device can have multiple endpoints (Endpoint, ep), and the length of the ep value is 16-bit (bit).

2. Each endpoint represents a device, and each device can be represented by a device id (device id) to represent the device type. Each endpoint may contain a set of clusters, and each cluster contains multiple attributes. (attribute).

FIG. 2 is a schematic diagram of the structure of a CHIP bridge (Bridge) device. The structure of a CHIP Bridge device can include the following features:

1. The bridged device 1 (Bridged Device1) and the bridged device 2 (Bridged Device2) represent non-CHIP (non-CHIP) (such as Zigbee, Z-Wave) protocol devices, and establish Zigbee or Z with the bridged (Bridge) device. -Wave secure connection. The bridged device can undertake a secure communication link to each bridged device; act as an interpreter for the bridged device, interpret it as a CHIP device and present it to the CHIP APP; provide the CHIP APP with accessible 'API/ 'interface.

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

3. The CHIP protocol adopts ZCL as the device model, and the cluster (Cluster) of the CHIP protocol device and the Zigbee protocol device adopts one-to-one mapping.

4. For example, a network physical Zigbee device (eg, a plug-in strip) securely connected to a bridge device includes two endpoints, ep1 and ep2. After mapping through the Bridge device, it is mapped to ep10, ep11 of the CHIP device.

Among them, ep1 can be the Zigbee switch 1 (switch1), corresponding to the bridged device 1 (Bridged Device1) in Figure 2, and ep5 can be the Zigbee switch 2 (switch2), corresponding to the bridged device 2 (Bridged Device2) in Figure 2 ); ep10 can be CHIP switch 1 (switch1), corresponding to CHIP device 1 (CHIP Device1) in Figure 1, and ep11 can be CHIP switch 2 (switch2), corresponding to CHIP device 2 (CHIP Device2) in Figure 2.

5. The manufacturer's application (Application, APP) can access the Bridge through the network.

6. The CHIP APP can access the mapped CHIP Device in the Bridge through the network. For example, each CHIP APP can use the interface provided by CHIP to see and control all bridged devices (Bridged Device) through CHIP Bridge.

As shown in FIG. 3 , it is a schematic diagram of a model structure of a Bluetooth Low Energy (Bluetooth Low Energy, BLE) device. The BLE device model structure can include the following features:

1. A BLE physical device can be composed 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 (Characteristic). Each Characteristic can also be uniquely identified by a UUID. Each Characteristic is assigned to a Handler differently from the network. Each Characteristic includes a corresponding property value (Property Value), which can also be referred to as a characteristic value (Characteristic Value).

2. A BLE physical device may include a master service (Service) through which slave services can be searched, and each service may include multiple services.

The embodiments of the present application may provide a method for bridging and mapping between a CHIP device and a BLE device.

FIG. 4 is a schematic flowchart of a method 200 for device bridging mapping according to an embodiment of the present application. The method can optionally be applied to a system including the devices shown in FIG. 1 , FIG. 2 , and FIG. 3 , but is not limited thereto. Exemplarily, the method may be applied to a CHIP bridging device, and the method may include at least part of the following contents.

S210. Establish a mapping relationship between the CHIP device and the Bluetooth low energy BLE device.

The CHIP bridge device and the CHIP device in the embodiments of the present application are not limited to devices supporting the CHIP protocol, and may also include devices supporting other protocols such as Zigbee and Z-Wave.

Exemplarily, the CHIP bridging device can establish a secure connection with the 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. In this way, the CHIP network can be enabled to access devices of the BLE network type, which enriches the types of devices that the CHIP ecosystem can access, and can interoperate with different types of devices. For example, enabling 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 healthcare, sports and fitness, security, home entertainment, and more. For example, blood pressure monitors, heart rate monitors, wristbands, speakers, etc.

Optionally, in this embodiment of the present application, the method further includes:

The CHIP device is created based on the mapping relationship between the CHIP device and the BLE device.

Exemplarily, after the CHIP bridging device can establish the mapping relationship between the CHIP device and the BLE device, for example, after saving the mapping relationship between the CHIP device and the BLE device in the mapping relationship table, it can create a virtual CHIP device based on the mapping relationship. The CHIP bridge device can create a virtual CHIP device under a certain endpoint, and the identifier of the endpoint can be used as the endpoint identifier of the virtual CHIP device. In addition, the cluster identifier under the endpoint can be used as the cluster identifier of the virtual CHIP device, and the attribute identifier under the cluster included in the endpoint can be used as the attribute identifier of the virtual CHIP device. For example, the CHIP bridge device creates a virtual CHIP device device1 under a certain endpoint ep1, and the endpoint identifier of the device1 is ep1. If the clusters included in the endpoint ep1 are Cluster1 and Cluster2, the cluster Cluster1 includes attributes Attribute1 and Attribute2, and the cluster Cluster2 includes attributes Attribute3 and Attribute4, then the cluster identifiers of device1 are Culster1 and Cluster2, then the attribute identifiers under Cluster1 of device1 are Attribute1 and Attribute2 , the attributes under the cluster Cluster2 are identified as Attribute3 and Attribute4.

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

the virtual client

receiving a first request from the CHIP control device, where the first request includes information about the target CHIP device;

Find 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;

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

Exemplarily, after the virtual CHIP device establishes a secure connection with the CHIP control device, the CHIP control device may send the first request to the CHIP bridge device. The first request may be of various types, for example, a read request, a write request, a control request, and the like. The first request may include information of the target CHIP device. For example, the first request may include one or more of a group endpoint (group ep) identifier, an endpoint (ep) identifier, a cluster (Cluster) identifier, and an attribute (Attribute) identifier of the target CHIP device. Based on the information of the target CHIP device in the first request, the CHIP bridge device may search for the information of the corresponding target BLE device in the mapping relationship between the CHIP device and the BLE device. The information of the target BLE device may include one or more of the physical device address of the target BLE device, a service handler (Service Handler) identifier, a characteristic handler (Characteristic Handler) identifier, and a characteristic value (Characteristic Value). After finding the information of the target BLE device, the CHIP bridge device may 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 may be a data request for obtaining data from the target BLE device.

Receive service data from the target BLE device;

Obtain 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.

Illustratively, the CHIP bridge device may receive service data from the target BLE device. For example, the service data includes a plurality of characteristic values of a certain service of the target BLE device. The attribute value of the corresponding target CHIP device can be obtained based on these characteristic values. For example, a service (Service) is a blood pressure service, and the service includes characteristics such as pulse rate and cardiac contraction, and there are attributes such as pulse rate, cardiac contraction and unit measurement under the cluster (Cluster) corresponding to the service. When only a Cluster request is issued, two values of pulse rate and cardiac systole can be returned according to the relationship between the BLE feature and the CHIP attribute.

Optionally, in the first manner of the embodiment of the present application, the CHIP device includes an endpoint (ep), the endpoint includes a cluster (Cluster), the cluster includes an attribute (Attribute), and the mapping relationship between the CHIP device and the BLE device includes the following: at least one of:

The mapping relationship between the endpoint identifier (ep ID) of the CHIP device and the BLE physical device address;

The mapping relationship between the cluster ID (Cluster ID) in the endpoint of the CHIP device and the BLE service handler ID (Service Handler ID);

The mapping relationship between the attribute identifier (Attribute ID) in the cluster of the CHIP device and the characteristic handler identifier (Characteristic Handler ID) in the BLE service.

Exemplarily, the endpoint identification ep 1 of the CHIP device has a mapping relationship with the BLE physical device address XXXX; the cluster identification Cluster1 of ep1 has a mapping relationship with the service processor identification Service Handler1 of BLE; the attribute identification Attribute 1 of Cluster1 is in the service of BLE. The feature handler identifier of Characteristic Handler 1 has a mapping relationship.

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

Optionally, in the first manner of the embodiment of the present application, searching for 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, including:

Find 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.

Exemplarily, if the first request includes the endpoint identifier and the cluster identifier of the target CHIP device, for example, the endpoint identifier is ep 1 and the cluster identifier is Cluster 1, in the mapping relationship, the target BLE device can be found based on the endpoint identifier ep 1. The address XXXX, based on the Cluster1 to find the Service Handler1 of the target BLE device.

Optionally, in the first manner of the embodiment of the present application, searching for 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 comprising:

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.

Exemplarily, if the first request includes the endpoint identifier and the cluster identifier of the target CHIP device, but also includes an attribute identifier. For example, the endpoint identifier is ep 1, the cluster identifier is Cluster 1, and the attribute identifier is Attribute 1. In the mapping relationship, The CHIP bridge device can find the address XXXX of the target BLE device based on the endpoint identifier ep 1, find the Service Handler 1 of the target BLE device based on the cluster identifier Cluster1, and find the Characteristic Handler 1 of the target BLE device based on the attribute identifier Attribute 1.

Optionally, in the second manner of this embodiment of the present application, the CHIP device includes a group endpoint (group ep) and an endpoint, the endpoint includes a cluster, and the cluster includes attributes, and the mapping relationship between the CHIP device and the BLE device includes at least one of the following: one:

The mapping relationship between the group endpoint identifier of the CHIP device and the BLE physical device address;

The mapping relationship between the endpoint identifier of the CHIP device and the service processor identifier of the BLE;

The mapping relationship between the cluster ID in the endpoint of the CHIP device and the feature processor ID in the BLE service;

The mapping relationship between the attribute identifier in the cluster of the CHIP device and the characteristic value (Characteristic Value) of BLE.

Exemplarily, the group endpoint identification group ep 1 of the CHIP device has a mapping relationship with the BLE physical device address XXXX; the endpoint identification ep 2 of the CHIP device has a mapping relationship with the service processor identification Service Handler2; The feature handler identifier Characteristic Handler 2 has a mapping relationship; the attribute identifier Attribute2 of Cluster2 has a mapping relationship with the feature processor identifier Characteristic Value2 in the BLE service.

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 identifiers in the endpoints of the CHIP device and the BLE service processor identifiers. There is a one-to-one correspondence between the cluster identifier in the cluster of the CHIP device and the feature processor identifier in the BLE service. There is a one-to-one correspondence between the attribute identifiers in the cluster of CHIP devices and the characteristic values of BLE.

Optionally, in the second manner of the embodiment of the present 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, including:

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

Exemplarily, if the first request includes the group endpoint identifier group ep 1 of the target CHIP device, in the mapping relationship, the CHIP bridge device can find the address XXXX of the target BLE device based on the group endpoint identifier group ep 1.

Optionally, in the second manner of the embodiment of the present application, the method further includes:

Return the endpoint list to the CHIP control device, where the endpoint list includes the endpoint identifier corresponding to the service processor identifier of the BLE.

Exemplarily, the CHIP bridging device may return an endpoint list to the CHIP control device, and the endpoint list may include multiple endpoint identifiers such as ep1, ep2 and ep3. The list of endpoints can be displayed on the CHIP control device, and the user can select a certain cluster of an endpoint among them. For example, if the user selects Cluster2 of ep2, the CHIP control device may send the first request to the CHIP bridge device again. The first request may include the endpoint identifier ep2 and the cluster identifier Cluster2.

Optionally, in the second manner of the embodiment of the present 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 comprising:

Find 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;

The feature processor identifier corresponding to the cluster identifier in the first request is searched in the mapping relationship between the CHIP device and the BLE device.

Exemplarily, if the received first request can include the endpoint identifier ep2 and the cluster identifier Cluster2, the CHIP bridge device can find the Service Handler2 of the target BLE device based on ep2 in the mapping relationship, and find the target BLE device based on the cluster identifier Cluster2. Characteristic Handler 2 for the device.

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.

Exemplarily, if the received first request also includes the attribute identifier Attribute 2, the CHIP bridge device can find the characteristic value Characteristic Value 2 of the target BLE device based on the attribute identifier Attribute 2 in the mapping relationship.

In the case that the attribute identifier is included in the first request, a data request corresponding to the attribute identifier is initiated to the service or feature of the BLE device.

Exemplarily, based on Manner 1, the first request includes the cluster identifier cluster1, and also includes the attribute identifier Attribute1. The CHIP bridge 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 characteristic handler Characteristic Handler1.

Exemplarily, based on the second method, the first request includes the cluster identifier cluster2, and also includes the attribute identifier Attribute2. The CHIP bridge 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 Characteristic Value2.

In the case that the attribute identifier is not included in the first request, a set of data requests is obtained based on each attribute identifier corresponding to the cluster identifier in the first request.

Exemplarily, based on the first method, the first request includes the cluster identifier cluster1, but does not include the specific attribute identifier. The cluster1 includes a plurality of attribute identifiers Attribute1, Attribute3, and Attribute5. The CHIP bridge device can obtain multiple corresponding status data requests based on the mapping relationship between these attribute identifiers Attribute1, Attribute3, and Attribute5 and the characteristic processors Characteristic Handler1, Characteristic Handler3, and Characteristic Handler5. The CHIP bridge device can then initiate these multiple status data requests to the service or feature of the target BLE device.

Exemplarily, based on the second method, the first request includes the cluster identifier cluster2, but does not include the specific attribute identifier. The cluster2 includes a plurality of attribute identifiers Attribute2, Attribute4, and Attribute6. The CHIP bridge device can obtain multiple corresponding status data requests based on the mapping relationship between these attribute identifiers Attribute2, Attribute4, and Attribute6 and the characteristic values Characteristic Value2, Characteristic Value 4, and Characteristic Value6. The CHIP bridge device can then initiate these multiple status data requests to the service or feature of the target BLE device.

In an application scenario, in order to enable the CHIP network to access devices of different network types, the embodiments of the present application provide a bridge mapping solution from a CHIP device to a BLE device based on the CHIP bridge (Bridge) technology.

Exemplarily, the bridge mode from the CHIP device to the BLE device is shown in FIG. 5 . BLE devices such as BLE device 1 and BLE device 2 are connected to bridge devices through a BLE network. The bridge device can be used to undertake the secure communication link to each BLE device, and can also act as an interpreter for the BLE device, interpreting it as a CHIP device and presenting it to the CHIP APP. The manufacturer APP can connect to the CHIP network through the interface defined by the manufacturer. CHIP devices such as CHIP device 1 and CHIP device 2 access the CHIP network. CHIP APP can also be connected to CHIP network, for example CHIP APP1, CHIP APP2, CHIP APP3 can be connected to CHIP network. Each CHIP APP can use the interface provided by CHIP to see and control all BLE devices through the CHIP bridge device.

Scenario Example 1:

As shown in FIG. 6 , an exemplary mapping relationship between CHIP devices and BLE devices (also referred to as a corresponding relationship) may include:

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

The service (Service) in BLE maintains a one-to-one relationship with the cluster (Cluster) in the CHIP bridge device;

The characteristic (Characteristic) in the service (Service) in BLE maintains a one-to-one relationship with the attribute (Attribute) in the endpoint (ep) in the CHIP bridge device;

As shown in FIG. 7 , it is a flowchart of Example 1 of the CHIP to BLE mapping scheme. The process can include:

S11, BLE Master (BLE Master) and BLE Slave (BLE Slave) have established a secure connection; among them, the BLE master device can be a virtual client in the CHIP bridge device to establish a connection with the BLE physical device, and the BLE slave device Physical device for BLE.

S12. The BLE master device sends a request for establishing a mapping relationship to the CHIP bridging function module.

S13. The CHIP bridge function module establishes a mapping relationship table: use the ep identifier of the CHIP Bridge to establish a mapping relationship with the address of the BLE physical device, and establish a relationship between the cluster ID (Cluster ID) of the CHIP device and the service handler ID (Service Handler ID) of the BLE. Mapping relationship, establish the mapping relationship between the attribute ID (Attribute ID) of CHIP and the characteristic handler ID (Characteristic Handler ID) of BLE.

S14. The CHIP bridging function module initiates a request for creating a CHIP device according to the mapping relationship.

S15. Create a CHIP device corresponding to the BLE device; the CHIP device may be a virtual device in the CHIP bridge device.

S16, the CHIP control device (controller) establishes a secure communication connection with the CHIP device;

S17. The CHIP control device sends a read (READ) request to the CHIP device; the request may include one or more of ep identifier, Cluster ID, and Attribute ID. For example, if the read request includes the Cluster ID, the read request is a read cluster request. If the read request includes Cluster ID and Attribute ID, the read request is a read attribute request. The read request is only an example, and other types of requests such as write requests, control requests, and the like are also possible.

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

S19, the CHIP bridging function module searches for the information of the corresponding BLE device according to one or more of the received ep identifier, Cluster ID, and Attribute ID. The value of the ep identifier can be 16 bits. For example, if you receive the ep identifier and the Cluster ID, find the corresponding BLE address in the mapping relationship based on the ep identifier, and find the Characteristic Handler ID in the mapping relationship based on the Attribute ID. If you receive the ep ID, clusterID and attribute information, find the corresponding BLE address in the mapping relationship according to the ep ID, find the corresponding Service Handler ID in the mapping relationship according to the Cluster ID, and find the Characteristic Handler ID in the mapping relationship according to the Attribute ID.

S20. After parsing the mapping relationship, the CHIP bridge function module can initiate access to Service/characteristic through the BLE master device. For example, if the received read request includes attributeID, a request to read data corresponding to attributeID can be initiated to service/characteristic. For another example, if there is no attribute ID in the received read request, a set of data requests can be obtained according to the mapping relationship between all AttributeIDs corresponding to the Cluster ID in the read request and the Characteristic Handler.

S21. The BLE master device in the bridge device sends a request to read data to the Service of the BLE slave device.

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

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

S24. The CHIP bridging function module returns the attribute data to the CHIP device.

S25, the CHIP device returns the attribute data to the CHIP control device.

Scenario Example 2:

As shown in Figure 8, an exemplary mapping relationship between CHIP devices and BLE devices may include:

CHIP to BLE mapping relationship 2 description:

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

The service in BLE maintains a one-to-one relationship with the ep in the CHIP bridge device;

The characteristic (Characteristic) in the service (Service) in BLE and the cluster (Cluster) in the ep in the CHIP bridge device maintain a mapping relationship;

The characteristic value (Property Value) of the characteristic (Characteristic) in BLE, that is, the characteristic value, maintains a mapping relationship with the attribute (Attribute) in the cluster (Cluster) in the CHIP bridge device.

As shown in FIG. 9 , it is a flowchart of Example 2 of the CHIP to BLE mapping scheme. The process can include:

The main differences between the scheme example 2 and the scheme example 1 include: different mapping methods.

S31 , S32 , S34 , S35 , and S36 of Scheme Example 2 are the same as S11 , S12 , S14 , S15 , and S16 of Scheme Example 1. In addition, the main differences between this scheme example 2 and scheme example 1 also include:

In S33, the CHIP bridge function module establishes a mapping relationship table, which may specifically include: using a group endpoint identifier group ep ID in the CHIP Bridge device to establish a mapping relationship with the BLE physical device address, and establishing the ep identifier of the CHIP Bridge device and the BLE Service Handler ID mapping relationship, establish the mapping relationship between the Cluster ID under the ep of the CHIP Bridge device and the Characteristic Handler ID under the BLE Service, and establish the mapping relationship between the Attribute ID and the Property Value under the Cluster device of the CHIP Bridge device. For example, the group ep: 0x0010 of the CHIP Bridge device corresponds to the device address of the actual BLE physical device. There are two Services under the BLE physical device, which correspond to 0x0011 and 0x0012 of the CHIP Bridge device, respectively, and the Characteristic and CHIP Bridge under the two Services. The Cluster of the device corresponds, and the Property Value under the Characteristic corresponds to the Attribute under the Cluster of the CHIP Bridge device.

In S37, the CHIP control device may issue a read (READ) request to the group ep: 0x0010 of the CHIP bridge device.

In S38, the CHIP device sends a request for parsing the mapping relationship to the CHIP bridging function module; and can send the received group ep identifier to the CHIP bridging function module.

In S39, the CHIP bridging function module may find the relationship between the corresponding BLE physical devices in the mapping relationship table according to the requested group ep identifier.

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

In and S41, the CHIP device may return the ep list to the CHIP control device, and the content included in the ep list may be the ep identification information corresponding to the BLE Service. For example, the Service Handler ID corresponding to ep1, and the Service Handler ID corresponding to ep2.

In S42, the CHIP control device sends a READ request to ep/cluster of the CHIP device or to ep/cluster/attribute. The READ request may include one or more of the group ep ID, ep ID, Cluster ID, and Attribute ID.

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

In S44, the CHIP bridge function module searches for the information of the BLE device according to the requested information of the CHIP device. For example, find the Service Handler ID corresponding to BLE from the mapping relationship according to the ep identifier, find the corresponding Characteristic Handler ID according to the Cluster ID, and find the Value of the corresponding Property according to the Attribute ID.

In S45, the CHIP bridge function module initiates a read data request through the BLE master device. For example, if the received read request includes attribute ID, you can initiate a read data request corresponding to attributeID to service/characteristic/value. For another example, if there is no attribute ID in the received read request, a set of status data requests can be obtained according to all the mapping relationships between the Cluster ID in the read request and the CharacteristicValue.

In S46, a request for reading data is sent to the service/characteristic of the BLE slave device (BLE Slave).

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

In S48, the BLE master device returns the service data corresponding to the read request to the CHIP bridging function module, and the CHIP bridging function module converts the Service data (for example, the characteristic value of the Service) into the attribute data of the CHIP device; The relationship fills the value of the attribute of the Characteristic Handler corresponding to the cluster.

In S49, the CHIP bridge function module returns the attribute data to the CHIP device.

In S50, the CHIP device returns the attribute data to the CHIP control device.

Example 2 can be applied to the situation where there are multiple attribute values under one characteristic. If the characteristic has only a single attribute value, example 1 can be used.

The embodiment of the present application can enable the CHIP network to access devices of the BLE network type, which enriches the device types for CHIP ecological access, and the CHIP devices can interoperate with different types of devices, such as BLE devices.

FIG. 10 is a schematic block diagram of a CHIP bridging device 400 according to an embodiment of the present application. The CHIP bridging device 400 may include:

The first processing unit 410 is configured to establish a mapping relationship between the CHIP device and the Bluetooth low energy BLE device.

Optionally, in this embodiment of the present 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.

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

Optionally, in this embodiment of the present application, the first processing unit 410 is further configured to receive a first request from the CHIP control device, where the first request includes information about the target CHIP device; between the CHIP device and the BLE device Find the information of the target BLE device corresponding to the information of the target CHIP device in the mapping relationship;

As shown in FIG. 11 , the CHIP bridge 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.

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

The first processing unit 420 is further configured to acquire 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.

Optionally, in this embodiment of the present application, referring to the first mode of the above method embodiment, the CHIP device includes an endpoint, 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: :

The mapping relationship between the endpoint identifier of the CHIP device and the BLE physical device address;

The mapping relationship between the cluster ID in the endpoint of the CHIP device and the service processor ID of BLE;

The mapping relationship between the attribute identifier in the cluster of the CHIP device and the feature processor identifier in the BLE service.

Optionally, in this embodiment of the present 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; The service processor identifier corresponding to the cluster identifier in the first request is searched in the mapping relationship between the CHIP device and the BLE device.

Optionally, in this embodiment of the present 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.

Optionally, in this embodiment of the present application, referring to the second mode of the above method embodiment, the CHIP device includes a group endpoint and an endpoint, the endpoint includes a cluster, and the cluster includes an attribute, and the mapping relationship between the CHIP device and the BLE device includes the following: at least one of:

The mapping relationship between the attribute identifier in the cluster of the CHIP device and the characteristic value of BLE.

Optionally, in this embodiment of the present 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.

Optionally, in this embodiment of the present application, the first processing unit 410 is further configured to return an endpoint list to the CHIP control device, where the endpoint list includes an endpoint identifier corresponding to the service processor identifier of the BLE.

Optionally, in this embodiment of the present application, the first processing unit 410 is further configured to 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; in this The feature processor identifier corresponding to the cluster identifier in the first request is searched in the mapping relationship between the CHIP device and the BLE device.

Optionally, in this embodiment of the present 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.

Optionally, in the embodiment of the present application, the first processing unit 410 is further configured to initiate a data request corresponding to the attribute identifier to the service or feature of the BLE device in the case that the attribute identifier is included in the first request.

Optionally, in this embodiment of the present application, the first processing unit 410 is further configured to obtain a group of attribute identifiers based on the attribute identifiers corresponding to the cluster identifiers in the first request when the first request does not include an attribute identifier. data request.

The CHIP bridging device 400 in this embodiment of the present application can implement the corresponding functions of the CHIP bridging device in the foregoing method embodiments. For the corresponding processes, functions, implementations, and beneficial effects of each module (submodule, unit, or component, etc.) in the CHIP bridging device 400, reference may be made to the corresponding descriptions in the above method embodiments, which will not be repeated here. It should be noted that the functions described by each module (submodule, unit, or component, etc.) in the CHIP bridging device 400 of the application embodiment may be implemented by different modules (submodule, unit, or component, etc.), or by the same A module (submodule, unit or component, etc.) implementation.

FIG. 12 is a schematic block diagram of a CHIP bridging device 500 according to an embodiment of the present application. The CHIP bridging device 500 may be each module (sub-module, unit or component, etc.) of the CHIP bridging device in the above-mentioned embodiments. Optionally, in this embodiment of the present application, the CHIP bridging device 500 further includes: a virtual client 510 and a CHIP bridging function module 520 . The virtual client 510 may implement the functions of the above-mentioned second processing unit.

The virtual client 510 is used for establishing a secure connection with the BLE device; sending a mapping relationship establishment request to the CHIP bridging function module 520;

The CHIP bridging function module 520 is configured to receive the mapping relationship establishment request.

Optionally, in this embodiment of the present application, the CHIP bridging function module 520 is further configured to establish a mapping relationship between the CHIP device and the BLE device.

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

The CHIP bridge device 500 also includes the virtual CHIP device 530 . The CHIP bridging function module 520 and the virtual CHIP device 530 may implement the function of the first processing unit.

Exemplarily, after receiving the mapping relationship establishment request from the virtual client 510, the CHIP bridging function module 520 establishes the mapping relationship between the CHIP device and the BLE device, and can create a virtual CHIP device 530 based on the mapping relationship. Then, the virtual CHIP device 530 establishes a secure connection with the CHIP control device. The virtual CHIP device 530 receives the first request from the CHIP control device, parses the first request, and sends it to the CHIP bridging function module 520 . Based on the first request, the CHIP bridging function 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 function module 520 may request the virtual client for data, and the virtual client initiates a second request to the service or feature of the BLE device. The virtual client can forward the service data received from the BLE device to the CHIP bridging function module 520. After the CHIP bridging function module 520 obtains the attribute data of the CHIP device, it sends it to the CHIP control device through the virtual CHIP device.

The CHIP bridging device 500 in this embodiment of the present application can implement the corresponding functions of the CHIP bridging device in the foregoing method embodiments. For the corresponding processes, functions, implementations, and beneficial effects of each module (submodule, unit, or component, etc.) in the CHIP bridging device 500, reference may be made to the corresponding descriptions in the above method embodiments, which will not be repeated here. It should be noted that the functions described by each module (submodule, unit, or component, etc.) in the CHIP bridging device 500 of the application embodiment may be implemented by different modules (submodule, unit, or component, etc.), or by the same module. A module (submodule, unit or component, etc.) implementation.

FIG. 13 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 includes a processor 610, and the processor 610 can call and run a computer program from a memory, so that the communication device 600 implements the methods in the embodiments of the present application.

Optionally, the communication device 600 may also include a memory 620 . The processor 610 may call and run a computer program from the memory 620, so that the communication device 600 implements the methods in the embodiments of the present application.

The memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .

Optionally, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices .

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

Optionally, the communication device 600 may be the CHIP bridging device in this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the CHIP bridging device in each method in the embodiment of the present application, which is not repeated here for brevity. Repeat.

FIG. 14 is a schematic structural diagram of a chip 700 according to an embodiment of the present application. The chip 700 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in the embodiments of the present application.

Optionally, the chip 700 may further include a memory 720 . The processor 710 may call and run a computer program from the memory 720 to implement the method executed by the CHIP bridge device in the embodiment of the present application.

The memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .

Optionally, the chip 700 may further include an input interface 730 . The processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740 . The processor 710 may control the output interface 740 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

Optionally, the chip can be applied to the CHIP bridging device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the CHIP bridging device in each method of the embodiments of the present application, which is not repeated here for brevity.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.

The above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (field programmable gate array, FPGA), an application specific integrated circuit (ASIC) or Other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor or the like.

The memory mentioned above may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM).

It should be understood that the above memory is an example but not a limitative description, for example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

FIG. 15 is a schematic block diagram of a communication system 800 according to an embodiment of the present application. The communication system 800 includes a CHIP bridge device 810 . The CHIP bridge device 810 is used to establish a mapping relationship between the CHIP device and the BLE device.

Optionally, the system may further include a CHIP control device 820 and a BLE device 830 .

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 may be used to implement the corresponding functions implemented by the BLE physical device in the above method. For brevity, details are not repeated here.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored on or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted over a wire from a website site, computer, server or data center (eg coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a Solid State Disk (SSD)), and the like.

It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art who is familiar with the technical scope disclosed in the present application can easily think of changes or substitutions. Covered within the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method for device bridging mapping, which is applied to connecting home CHIP bridging devices through Internet Protocol, the method includes:

Establish the mapping relationship between CHIP devices and Bluetooth low energy BLE devices.
The method of claim 1, wherein the method further comprises:

The CHIP device is created based on the mapping relationship between the CHIP device and the BLE device.
The method according to claim 1 or 2, wherein the method further comprises:

A secure connection is established with the CHIP control device through the CHIP device.
The method of claim 3, wherein the method further comprises:

receiving a first request from the CHIP control device, where the first request includes information about the target CHIP device;

Find 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;

Based on the information of the target BLE device, a second request corresponding to the first request is sent to the target BLE device.
The method of claim 4, wherein the method further comprises:

receiving service data from the target BLE device;

Obtain 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.
The method according to claim 4 or 5, wherein searching 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 comprises:

Find 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.
The method according to claim 6, wherein searching 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 comprising:

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.
The method according to any one of claims 1 to 7, wherein the CHIP device includes a group endpoint and an endpoint, 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:

The mapping relationship between the group endpoint identifier of the CHIP device and the BLE physical device address;

The mapping relationship between the endpoint identifier of the CHIP device and the service processor identifier of the BLE;

The mapping relationship between the cluster ID in the endpoint of the CHIP device and the feature processor ID in the BLE service;

The mapping relationship between the attribute identifier in the cluster of the CHIP device and the characteristic value of BLE.
The method according to claim 4 or 5, wherein searching 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 comprises:

The address of the target BLE device corresponding to the group endpoint identifier in the first request is searched in the mapping relationship between the CHIP device and the BLE device.
The method of claim 9, wherein the method further comprises:

Return the endpoint list to the CHIP control device, where the endpoint list includes endpoint identifiers corresponding to the service processor identifiers of BLE.
The method according to claim 9 or 10, wherein searching 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 comprising:

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;

The feature processor identifier corresponding to the cluster identifier in the first request is searched in the mapping relationship between the CHIP device and the BLE device.
The method according to claim 11, wherein searching 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 comprising:

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.
The method according to any one of claims 1 to 5 and 9 to 12, wherein the CHIP device includes an endpoint, the endpoint includes a cluster, the cluster includes an attribute, and a mapping relationship between the CHIP device and the BLE device Include at least one of the following:

The mapping relationship between the endpoint identifier of the CHIP device and the BLE physical device address;

The mapping relationship between the cluster ID in the endpoint of the CHIP device and the service processor ID of BLE;

The mapping relationship between the attribute identifier in the cluster of the CHIP device and the feature processor identifier in the BLE service.
The method of claim 7 or 12, wherein the method further comprises:

In the case that 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.
The method of claim 6 or 11, wherein the method further comprises:

In the case that the attribute identifier is not included in the first request, a set of data requests is obtained based on each attribute identifier corresponding to the cluster identifier in the first request.
The method according to any one of claims 1 to 15, wherein the CHIP bridging device comprises a virtual client and a CHIP bridging function module, and the method further comprises:

establishing a secure connection between the virtual client and the BLE device;

The virtual client sends a mapping relationship establishment request to the CHIP bridging function module.
The method according to claim 16, wherein establishing the mapping relationship between the CHIP device and the BLE device comprises:

In the CHIP bridging function module, a mapping relationship between the CHIP device and the BLE device is established.
The method according to claim 16 or 17, wherein creating the CHIP device based on the mapping relationship between the CHIP device and the BLE device comprises:

The CHIP bridging function module creates the virtual CHIP device based on the mapping relationship between the CHIP device and the BLE device, and the CHIP bridging device further includes the CHIP device.
A CHIP bridging device including:

The first processing unit is configured to establish a mapping relationship between the CHIP device and the Bluetooth low energy BLE device.
The device according to claim 19, wherein the first processing unit is further configured to create the CHIP device based on a mapping relationship between the CHIP device and the Bluetooth Low Energy BLE device.
The device according to claim 19 or 20, wherein the first processing unit is further configured to establish a secure connection with a CHIP control device through the CHIP device.
The device according to claim 21, wherein the first processing unit is further configured to receive a first request from the CHIP control device, where the first request includes information of a target CHIP device; Find the information of the target BLE device corresponding to the information of the target CHIP device in the mapping relationship with 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 apparatus of claim 22, wherein,

The second processing unit is further configured to receive service data from the target BLE device;

The first processing unit is further configured to acquire 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.
The device according to claim 22 or 23, wherein the first processing unit is further configured to search for 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 address; 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.
The device according to claim 24, 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.
The device according to any one of claims 19 to 25, wherein the CHIP device includes an endpoint, 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 one:

The mapping relationship between the endpoint identifier of the CHIP device and the BLE physical device address;

The mapping relationship between the cluster ID in the endpoint of the CHIP device and the service processor ID of BLE;

The mapping relationship between the attribute identifier in the cluster of the CHIP device and the feature processor identifier in the BLE service.
The device according to claim 22 or 23, wherein the first processing unit is further configured to search for the target BLE corresponding to the group endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device The address of the device.
The device according to claim 27, wherein the first processing unit is further configured to return an endpoint list to the CHIP control device, the endpoint list including an endpoint identifier corresponding to a service processor identifier of BLE.
The device according to claim 27 or 28, wherein the first processing unit is further configured to search for a service processor corresponding to the endpoint identifier in the first request in the mapping relationship between the CHIP device and the BLE device Identification; searching for the feature processor identification corresponding to the cluster identification in the first request in the mapping relationship between the CHIP device and the BLE device.
The device according to claim 29, wherein the first processing unit is further configured to search for the characteristic value corresponding to the attribute identifier in the first request in the mapping relationship between the CHIP device and the BLE device.
The device of any one of claims 19 to 23, 27 to 30, wherein the CHIP device includes a group endpoint and an endpoint, the endpoint includes a cluster, the cluster includes an attribute, the CHIP device is associated with a BLE device The mapping relationship includes at least one of the following:

The mapping relationship between the group endpoint identifier of the CHIP device and the BLE physical device address;

The mapping relationship between the endpoint ID of the CHIP device and the service processor ID of the BLE;

The mapping relationship between the cluster ID in the endpoint of the CHIP device and the feature processor ID in the BLE service;

The mapping relationship between the attribute identifier in the cluster of the CHIP device and the characteristic value of BLE.
The device according to claim 25 or 30, wherein the first processing unit is further configured to initiate a service or feature of the BLE device corresponding to the attribute identification when the first request includes an attribute identification data request.
The device according to claim 24 or 29, wherein the first processing unit is further configured to, in the case where the first request does not include the attribute identifier, based on each attribute identifier corresponding to the cluster identifier in the first request Get a set of data requests.
The device according to any one of claims 19 to 33, wherein the CHIP bridging device further comprises:

A virtual client, used for establishing a secure connection with the BLE device; sending a mapping relationship establishment request to the CHIP bridging function module;

The CHIP bridging function module is used for receiving the mapping relationship establishment request.
The device according to claim 34, wherein the CHIP bridging function module is further configured to establish a mapping relationship between the CHIP device and the BLE device.
The device according to claim 34 or 35, wherein the CHIP bridging function module is further configured to create the virtual CHIP device based on the mapping relationship between the CHIP device and the BLE device;

The CHIP bridging device further includes the CHIP device.
A communication device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and execute the computer program according to any one of claims 1 to 18 Methods.
A chip, comprising: a processor for invoking and running a computer program from a memory, so that a device on which the chip is installed executes the method according to any one of claims 1 to 18.
A computer-readable storage medium storing a computer program that causes a computer to perform the method of any one of claims 1 to 18.
A computer program product comprising computer program instructions that cause a computer to perform the method of any one of claims 1 to 18.
A computer program that causes a computer to perform the method of any one of claims 1 to 18.