Zifeng device access control method and Open Link Alliance OLA gateway

Abstract

A method for controlling access to Zigbee devices and an Open Intelligent Alliance (OLA) gateway are provided, capable of implementing access control for Zigbee devices compatible with the OLA protocol standard. The method comprises: developing an intelligent alliance OLA gateway to receive Zigbee device description information reported by Zifeng devices; establishing, by the OLA gateway, a mapping relationship between the Zifeng device description information of the Zifeng device and the OLA device description information of the Zifeng device based on a Zifeng device data model and an OLA device data model; and performing access control on the Zifeng device based on the mapping relationship.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and specifically to an access control method for Zifeng devices and an Open Link Alliance (OLA) gateway. Background Art

[0002] To leverage the advantages of the Internet of Things (IoT), unify the technologically advanced IoT connectivity standards and ecosystem, address end-to-end communication technology and device management challenges within the IoT industry, and promote global openness and adoption, the Open Link Association (OLA) was established. OLA is considering adding Zigbee devices to the OLA network. However, devices joining the OLA network must support the OLA protocol standard, while Zigbee devices support the Zigbee protocol standard. Therefore, implementing access control for Zigbee devices within the OLA network to ensure better compatibility with the existing OLA protocol standard is an urgent issue. Summary of the Invention

[0003] The embodiments of the present application provide an access control method for Zigbee devices and an Open Link Alliance (OLA) gateway, which can implement access control of Zigbee devices compatible with the OLA protocol standard.

[0004] In a first aspect, a method for controlling access to a Zifeng device is provided, comprising:

[0005] Developing an intelligent alliance OLA gateway to receive Zifeng device description information of the Zifeng device reported by the Zifeng device;

[0006] The OLA gateway establishes a mapping relationship between the Zifeng device description information of the Zifeng device and the OLA device description information of the Zifeng device according to the Zifeng device data model and the OLA device data model;

[0007] Access control is performed on the Zifeng device according to the mapping relationship.

[0008] In a second aspect, an OLA gateway is provided, configured to execute the method in the first aspect or any possible implementation of the first aspect. Specifically, the OLA gateway includes a unit configured to execute the method in the first aspect or any possible implementation of the first aspect.

[0009] In a third aspect, an OLA gateway is provided, comprising a processor and a memory, wherein the memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method of the first aspect or its implementations.

[0010] In a fourth aspect, a chip is provided for implementing the method in the above-mentioned first aspect or its various implementations.

[0011] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method in the above-mentioned first aspect or its various implementations.

[0012] In a fifth aspect, a computer-readable storage medium is provided for storing a computer program, which enables a computer to execute the method in the above-mentioned first aspect or its various implementations.

[0013] In a sixth aspect, a computer program product is provided, comprising computer program instructions, which enable a computer to execute the method in the above-mentioned first aspect or its various implementations.

[0014] In a seventh aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in the above-mentioned first aspect or its various implementations.

[0015] Based on the above technical solution, the OLA gateway maps the Zigbee device description information of the Zigbee device to the OLA device description information according to the rules of the Zigbee device data model definition specified in the Zigbee protocol and the rules of the OLA device data model definition specified in the OLA protocol, which is equivalent to simulating the Zigbee device as an OLA device. Furthermore, the OLA control end can use the general access control method for OLA devices to control access to the Zigbee device, which can better be compatible with the existing OLA protocol standard. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 It is a structural diagram of a Zigbee device data model according to an embodiment of the present application.

[0017] Figure 2 Schematic diagram of the structure of an OLA device data model according to an embodiment of the present application.

[0018] Figure 3 It is a schematic diagram of an application scenario provided by an embodiment of the present application.

[0019] Figure 4 This is a schematic diagram of an access control method for a Zifeng device provided in an embodiment of the present application.

[0020] Figure 5 This is a schematic diagram of a mapping method provided in an embodiment of the present application.

[0021] Figure 6 This is a schematic diagram of another mapping method provided in an embodiment of the present application.

[0022] Figure 7 This is a schematic flowchart of an access control method for a Zigbee device according to an embodiment of the present application.

[0023] Figure 8 This is a schematic flowchart of an access control method for a Zigbee device according to another embodiment of the present application.

[0024] Figure 9 This is a schematic block diagram of an OLA gateway provided in an embodiment of the present application.

[0025] Figure 10 This is a schematic block diagram of a communication device provided in another embodiment of the present application.

[0026] Figure 11 This is a schematic block diagram of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0028] First, a brief introduction to the terms involved in the embodiments of this application is given:

[0029] Zigbee (Purple Bee Protocol) technology:

[0030] ZigBee is a low-power local area network protocol based on the Institute of Electrical and Electronics Engineers (IEEE) 802.15.4 standard. According to international standards, ZigBee technology is a short-range, low-power wireless communication technology.

[0031] In the embodiments of the present application, a device that supports the Zigbee protocol is referred to as a Zigbee device.

[0032] The ZigBee protocol introduces the concepts of profiles, endpoints, clusters, and attributes to enable interoperability between multiple devices. Each ZigBee device is a node, which is a physical device. A node consists of multiple endpoints, an endpoint can consist of multiple clusters, and a cluster consists of multiple attributes. A profile is a set of regulations for a specific application (such as home automation (HA) applications and telecom applications (TA)). A specific application (such as a smart home) includes numerous detailed specifications (for example, light control: turning on, off, and dimming). These specifications are clusters, and attributes are the corresponding properties of a cluster (for example, light brightness). Different profiles, endpoints, clusters, and attributes are used by the controlling and controlled devices according to different application scenarios.

[0033] An endpoint is a logical device. An endpoint can contain a device identifier (deviceid) to indicate the device type corresponding to the endpoint, such as a light or switch. An endpoint can contain multiple clusters, each of which contains multiple attributes. Each attribute has a data value (value) and a corresponding data type (type). The data value can reflect a physical quantity or state, such as a switch value (On / Off), light status value (On / Off), temperature value, percentage, and so on.

[0034] The profile also provides a set of operation commands for controlling the attribute, such as turning the light on or off, the color of the light, etc.

[0035] Profiles enable interoperability between ZigBee devices. The ZigBee Alliance has defined many standard profiles, such as the switch profile and the light profile. Any node that follows a standard profile can interoperate with other nodes that implement the same profile.

[0036] In summary, a profile can be understood as a collection of various device descriptors for an application. This means a profile can be considered a descriptor data model or structure, also known as the ZigBee Cluster Library (ZCL). In other words, a descriptor is a descriptor provided to an application, and a collection of descriptors is a profile. For example, an application can be described based on the data packets it processes and the operations it performs.

[0037] A ZigBee device can describe itself based on this descriptor data structure. The specific data for these descriptors is defined in the device description information of the ZigBee device. For ease of distinction and explanation, the device description information of a ZigBee device is referred to as ZigBee device description information, and the descriptor data structure of a ZigBee device is referred to as the ZigBee device data model.

[0038] Figure 1 This example illustrates a data model structure for the description item of a Zigbee device. It should be understood that Figure 1 The description item data model in is only an example, and it can correspond to different description item data model structures according to different application scenarios. This application is not limited to this.

[0039] The Open Link Association (OLA) was established to leverage the industrial advantages of the Internet of Things (IoT), unify the technologically advanced IoT connection standard system and industrial ecosystem, solve the end-to-end communication technology and device management problems in the IoT industry, and open and promote it globally.

[0040] In the embodiments of this application, a device that supports the OLA protocol is referred to as an OLA device. The OLA protocol also defines a descriptive item data structure for an OLA device, or a descriptive item data model. For ease of distinction and explanation, this is referred to as the OLA device data model. The OLA device data model defines the following concepts:

[0041] 1. Device Type. Each OLA device corresponds to a Device Type. For example, the Device Type corresponding to the e smart light device is: olaV1.device.light.000012.

[0042] 2. Service Type: An OLA device can include multiple Service Types. For example, the service types corresponding to smart light devices include the light service type (olaV1.service.light.100128) and the device basic information service type (olaV1.service.deviceInfo.100101).

[0043] 3. Property Type. Each service type of an OLA device contains multiple Property Types. For example, the light service type contains the property types of brightness (olaV1.property.brightness.2xxxxx) and color temperature (olaV1.property.hue.2xxxxx).

[0044] 4. Action: used to control the attribute type of the OLA device and report the attribute event of the OLA device when there is an event corresponding to the attribute type.

[0045] The OLA device can describe itself according to the OLA data model structure. The specific data of these description items of the OLA device are defined in the device description information of the OLA device. For the convenience of distinction and description, the device description information of the OLA device is recorded as OLA device description information.

[0046] Figure 2 An example of a description item data model of an OLA device is given. It should be understood that Figure 2 The description item data model in is only an example. Different description item data models may correspond to different application scenarios, and this application is not limited to this.

[0047] Figure 3 A schematic diagram showing an application scenario provided by an embodiment of the present application is shown.

[0048] like Figure 3 As shown, the Zigbee device 12 is a device that supports Zigbee technology and can access the Zigbee network. In some embodiments, the Zigbee device 12 is a smart device (such as virtual reality (VR) glasses, smart wearable devices, etc.), a terminal device, or other device with network access capabilities, which is not limited in this embodiment of the present application.

[0049] In one example, when Zigbee devices are applied to smart home life scenarios, the Zigbee device 12 can be a smart home device such as a smart TV, a smart speaker, a smart air conditioner, a smart light, a smart door and window, a smart curtain, a smart socket, and a smart switch.

[0050] Optionally, the number of Zigbee devices 12 is one, or the number of Zigbee devices 12 is multiple. The embodiment of the present application does not limit this. In actual applications, the number of Zigbee devices 12 can be determined in combination with application requirements or the maximum number of devices that the distribution network platform gateway 141 can manage.

[0051] The Zigbee device 12 is configured to access the network by the distribution network platform gateway 141. The cloud server corresponding to the distribution network platform gateway 141 is the distribution network platform cloud 142. The distribution network platform gateway 141 and the distribution network platform cloud 142 are connected via a wired or wireless network.

[0052] The network configuration platform gateway 141 refers to a device capable of configuring a Zigbee network. Optionally, the network configuration platform gateway 141 may be a server, terminal device, router, terminal device, mobile phone, tablet computer, wearable device, or other device capable of configuring network access. This embodiment of the present application is not limited to this. In actual applications, the implementation form of the network configuration platform gateway 141 may be determined in conjunction with the application scenario of the Zigbee device.

[0053] In one example, when Zigbee devices are applied to smart home life scenarios, considering that the home environment has the characteristics of small area and frequent activities, the use of a distribution network platform gateway 141 that occupies a larger space will affect normal home life. The distribution network platform gateway 141 can be implemented as a router, terminal device, mobile phone, tablet computer, wearable device, etc.

[0054] Optionally, the number of distribution network platform gateways 141 may be one or more, which is not limited in the embodiment of the present application. Usually, for considerations such as saving resources, the number of distribution network platform gateways 141 is one.

[0055] Optionally, a device platform cloud 16 may be further included. The Zigbee device 12 is developed based on the device platform cloud 16 , and the license key Kc of the Zigbee device 12 is stored in the device platform cloud 16 .

[0056] There is a communication link between the distribution network platform cloud 142 and the device platform cloud 16. Optionally, the distribution network platform cloud 142 sends the information required for the access authentication process of the Zigbee device 12 to the device platform cloud 16; or forwards the information required for the access authentication process of the Zigbee device 12 to the distribution network platform gateway 141.

[0057] Among them, the above-mentioned distribution network platform cloud 142 and device platform cloud 16 are cloud computing resource pools in the field of cloud technology. Various types of virtual resources are deployed in the resource pool for external customers to choose to use. The cloud computing resource pool mainly includes: computing devices (virtualized machines, including operating systems), storage devices, and network devices. It can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), as well as big data and artificial intelligence platforms and other basic cloud computing services.

[0058] Optionally, the distribution network platform gateway 141 and the control device 18 are connected via a wired or wireless network. The control device 18 can be operated by the user to control access to devices connected to the distribution network platform gateway 141. For example, the user can use an application on the control device 18 to control the devices connected to the distribution network platform gateway 141. The control device 18 can be implemented as a terminal device, mobile phone, tablet computer, wearable device, etc.

[0059] In the embodiment of the present application, the network distribution platform 141 may be an OLA gateway, which may support the construction of an OLA network, thereby enabling access to OLA devices and device authentication.

[0060] OLA is considering adding Zigbee devices to OLA, but devices joining OLA need to support the OLA protocol standard, while Zigbee devices support the Zigbee protocol standard. Therefore, how to implement access control for Zigbee devices in the OLA network to better compatibility with the existing OLA protocol standard is an urgent problem to be solved.

[0061] Figure 4 is a schematic interactive diagram of the access control method of the Zifeng device according to an embodiment of the present application, such as Figure 4 As shown, the method 200 includes:

[0062] S210 , the Zigbee device reports the Zigbee device description information of the Zigbee device to the OLA gateway.

[0063] Correspondingly, the OLA gateway receives the Zigbee device description information of the Zigbee device.

[0064] In some embodiments, the Zifeng device may correspond to Figure 3 For the Zigbee device 12 in the embodiment, please refer to the relevant description of the above embodiment for its specific implementation.

[0065] In some embodiments of the present application, the OLA gateway can be used to build a Zigbee network, and the Zigbee device can access the OLA gateway through the Zigbee network.

[0066] In some embodiments of the present application, the Zigbee device may send the Zigbee device description information of the Zigbee device to the OLA gateway when the Zigbee device is connected to the OLA gateway and the device authentication of the Zigbee device is completed.

[0067] In some embodiments of the present application, the Zigbee description information of the Zigbee device may include specific data of the description items defined by the Zigbee device data model. As an example, the Zigbee device description information includes at least one of the following information:

[0068] Node information, endpoint information, cluster information and attribute information, manufacturer information, device name, and generation date information.

[0069] Optionally, in some embodiments, the node information includes a Media Access Control (MAC) address and / or a network short address, wherein the MAC address is an address assigned to the Zigbee device before joining the Zigbee network, and the network short address is an address assigned to the Zigbee device when the Zigbee device accesses the Zigbee network after the Zigbee network is established.

[0070] Optionally, in some embodiments, if the Zigbee device includes an endpoint, the node information of the Zigbee device may also include a device ID corresponding to the endpoint.

[0071] Optionally, in some embodiments, if the Zigbee device includes multiple endpoints, and the multiple endpoints correspond to the same Device ID, the node information of the Zigbee device may also include the Device IDs corresponding to the multiple endpoints.

[0072] Optionally, the endpoint information may include device ID information and cluster information, wherein the device ID information is used to indicate the device type of the endpoint.

[0073] Optionally, the cluster information may include a cluster ID and attribute information included in the cluster.

[0074] Optionally, the attribute information may include at least one of an attribute ID, an attribute value, a type of the attribute value, and a length of the attribute value.

[0075] S220: The OLA gateway establishes a mapping relationship between the Zigbee device description information of the Zifeng device and the OLA device description information of the Zifeng device according to the Zigbee device data model and the OLA device data model.

[0076] The specific implementation of the Zigbee device data model and the OLA device data model is described above and will not be repeated here for the sake of brevity. It should be understood that the OLA device data model and the Zigbee device data model described above are merely examples. As the standards evolve, the OLA device data model and the Zigbee device data model may also include other rules or have more descriptive item information. The specific mapping logic is similar, and this application is not limited thereto.

[0077] Therefore, in an embodiment of the present application, the Zigbee device description information of the Zigbee device can be understood as the device description information of the Zigbee device that follows the rules defined by the Zigbee device data model, and the OLA device description information of the Zifeng device can be understood as the device description information of the Zifeng device that follows the rules defined by the OLA device data model.

[0078] In other words, the Zigbee device description information for a Zigbee device describes the device's capabilities based on the rules defined by the Zigbee device data model, while the OLA device description information for a Zigbee device describes the device's capabilities based on the rules defined by the OLA device data model. The capabilities of the Zigbee device itself remain unchanged; only the description method changes.

[0079] By establishing the above mapping relationship, the Zigbee device description information that follows the rules defined by the Zigbee device data model is converted into the OLA device description information that follows the rules defined by the OLA device data model. This is equivalent to the OLA gateway simulating the Zigbee device as an OLA device. In this way, the OLA control end can use the standard OLA control interface to control access to the Zigbee device without modifying the OLA control interface, which is conducive to compatibility with the existing OLA protocol.

[0080] In some embodiments of the present application, the OLA device description information includes at least one of the following information:

[0081] Device type information, service type information, and property type information.

[0082] In some implementations, each physical device in a Zigbee device can be mapped as an independent device to an OLA device, or the Zigbee device can be mapped to an OLA device.

[0083] In some embodiments, the mapping method to be used may be determined according to the number of physical devices included in the Zigbee device.

[0084] Optionally, the number of physical devices included in the Zigbee device can be determined based on the number of RF modules included in the Zigbee device. If the Zigbee device includes only one RF module, it is considered that the Zigbee device corresponds to one physical device; or, if the Zigbee device includes multiple RF modules, it can be considered that the Zigbee device corresponds to multiple physical devices, and the multiple physical devices can be independently controlled by the corresponding RF modules.

[0085] Optionally, if the Zigbee device corresponds to one physical device, the Zigbee device can be mapped to an OLA device; or, if the Zigbee device corresponds to multiple physical devices, each physical device in the Zigbee device can be mapped to an OLA device, thereby enabling refined control of the multiple physical devices.

[0086] In some embodiments, mapping may be performed based on the hierarchical relationship between the description items defined in the OLA device data model and the hierarchical relationship between the description items defined in the Zigbee device data model.

[0087] It can be understood that the hierarchical relationship of each descriptive item in the Zigbee device data model can be node, endpoint, cluster and attribute from high to low, and the hierarchical relationship of each descriptive item in the OLA device data model can be device type, service type and attribute type from high to low.

[0088] The following describes the specific mapping method in combination with mapping method 1 and mapping method 2, but the present application is not limited thereto.

[0089] Mapping method 1:

[0090] Mapping the node information in the Zigbee device description information to the devicetype information in the OLA device description information;

[0091] Mapping at least one cluster information included in the node information in the Zigbee device description information to the service type information in the OLA device description information;

[0092] Mapping the attribute information included in the at least one cluster information in the Zigbee device description information to the property type information included in the service type information in the OLA device description information.

[0093] Based on mapping method 1, the OLA gateway searches for the mapping relationship based on the device type information to determine the corresponding node information, searches for the mapping relationship based on the service type information to determine that it corresponds to the cluster information under the node, and searches for the mapping relationship based on the property type information to determine the attribute information under the corresponding cluster.

[0094] Optionally, the mapping method 1 may be applicable to a scenario where the Zigbee device corresponds to one physical device.

[0095] In the mapping mode 1, if the first service type information in the OLA device description information corresponds to multiple cluster information, the multiple cluster information may belong to the same endpoint of the Zigbee device, or may belong to different endpoints of the Zigbee device.

[0096] For example, in some scenarios, a Zigbee device corresponds to a physical device, and the combination of the functions of the physical device is equivalent to an application, that is, an application can include multiple functions. The information of the multiple functions can be stored in a cluster under the same endpoint, or in clusters under different endpoints. When mapping, the clusters of multiple functions belonging to a physical device can be mapped to a service type in the OLA device description information, thereby enabling precise control of the physical device.

[0097] In some embodiments, mapping the node information in the Zigbee device description information to the device type information in the OLA device description information may include mapping the MAC address or network short address of the Zigbee device to the device type information in the OLA device description information. That is, establishing a mapping relationship between the MAC address or network short address of the Zigbee device and the device type information in the OLA device description information.

[0098] In some embodiments, mapping the at least one cluster information included in the node information in the Zigbee device description information to the service type information in the OLA device description information includes:

[0099] Mapping other cluster information except basic cluster information in the Zigbee device description information to the first service type information in the OLA device description information;

[0100] The basic cluster information in the Zigbee device description information is mapped to the second service type information in the OLA device description information.

[0101] In some embodiments, the basic cluster is used to store basic information of the device, such as manufacturer information (ManufacturerName), data code (DataCode), etc. Other clusters are used to store service information of the device, such as light service, etc.

[0102] In some embodiments, the OLA gateway may map the basic cluster in the Zigbee device description information to one service type and map other clusters in the Zigbee device description information to another service type when the Zigbee device corresponds to one physical device.

[0103] Furthermore, mapping the attribute information included in the at least one cluster information in the Zigbee device description information to the property type information included in the service type information in the OLA device description information includes:

[0104] Mapping attribute information included in other cluster information except basic cluster information to corresponding property type information in the first service type information;

[0105] Map the attribute information included in the basic cluster information to the corresponding property type information in the second service type information.

[0106] Figure 5 A schematic diagram illustrating a mapping relationship based on mapping mode 1 is shown.

[0107] like Figure 5As shown, the Zifeng device, as a node, includes three clusters: Cluster 1, Cluster 2, and Cluster 3. Cluster 3 can be a basic cluster, while Clusters 1 and 2 can be non-basic clusters. For example, if the Zigbee device is a Zigbee lamp, Cluster 1 can be a switch control cluster, and Cluster 2 can be a color control cluster. Based on mapping method 1, the Zifeng device can be mapped as an OLA device. For example, the node information of the Zifeng device is mapped to the device type information of the OLA device, the information of Clusters 1 and 2 is mapped to Service Type 1 of the OLA device, Cluster 3 is mapped to Service Type 2, and the attribute information in Clusters 1 and 2 is mapped to the corresponding attribute types in Service Type 1, and the attribute information in Cluster 3 is mapped to the corresponding attribute types in Service Type 2.

[0108] The following describes mapping method 1 by taking a Zigbee lamp as an example.

[0109] In this example, the Zigbee device supports Zigbee 3.0 and includes an endpoint. The Device ID corresponding to the endpoint is 0x010c, indicating that the device type of the Zigbee device is a lamp device type. The Zigbee device description information includes a basic cluster, a switch (On / Off) cluster, and a color control (color control) cluster. Each cluster corresponds to a corresponding attribute.

[0110] The basic cluster includes the manufacturer name (ManufactureName) attribute and the data code (datacode) attribute, which correspond to IDs: 0x0004 and 0x0006 respectively.

[0111] The On / Off cluster includes the OnOff attribute, and the color control cluster includes the CurrentX attribute, the CurrentY attribute, the CurrentHue attribute, and the CurrentSaturation attribute.

[0112] OLA device description information may include device information service type (olaV1.service.deviceInfo.100101) and light device service type (olaV1.device.light.000012), wherein the device information service type may include manufacturer attribute type and production date attribute type, and the light device service type may include switch attribute type, color temperature attribute type, color temperature attribute type and saturation attribute type.

[0113] Based on mapping method 1, as shown in Table 1, the node information of the Zigbee device (for example, Device ID) is mapped to the device type information (olaV1.device.light.000012) in the OLA device description information, and the On / OffCluster and color control cluster are mapped to the light service type (olaV1.service.light.100128) in the OLA device description information.

[0114] Furthermore, map the attributes in the On / Off Cluster and the color control cluster to the corresponding property types in olaV1.service.light.100128.

[0115] For example, the OnOff property is mapped to the switch property type (olaV1.property.on.2xxxxx) in olaV1.service.light.100128, the CurrentX property and the CurrentY property are mapped to the color temperature property type (olaV1.property.colorTemperature.2xxxxx), the CurrentHue property is mapped to the color temperature property type (olaV1.property.hue.2xxxxx), and the CurrentSaturation property is mapped to the saturation property type (olaV1.property.saturation.2xxxxx).

[0116] Table 1

[0117]

[0118]

[0119] As shown in Table 2, the basic cluster can be mapped to the device information service type (olaV1.service.deviceInfo.100101) in the OLA device description information, and the manufacturer name attribute and data code attribute in the basic cluster can be mapped to the manufacturer name attribute type (olaV1.property.manufacturer.2xxxxx) and production date attribute type (olaV1.property.manufactureDate.2xxxxx) under olaV1.service.deviceInfo.100101.

[0120] Table 2

[0121]

[0122] Based on the above mapping process, the Zigbee lamp can be mapped to an OLA lamp. Furthermore, the OLA control end can control the Zigbee lamp based on the control method of the OLA lamp.

[0123] Optionally, in some embodiments, in mapping mode 1, the command corresponding to the attribute information in the Zigbee device description information can also be mapped to the action corresponding to the property type information in the OLA device description information. That is, the command on the Zigbee property information can be executed as an operation on the property type of the OLA device.

[0124] Optionally, in some embodiments, in mapping mode 1, the status in the Zigbee device description information may be reported to an event (envent) in the OLA device description information. That is, the Zigbee status report (e.g., attribute status report) may be executed as an event of the OLA device.

[0125] Mapping method 2:

[0126] Mapping the endpoint information in the Zigbee device description information to the devicetype information in the OLA device description information;

[0127] Mapping at least one cluster information included in the endpoint information in the Zigbee device description information to the service type information in the OLA device description information;

[0128] Mapping the attribute information included in the at least one cluster information in the Zigbee device description information to the attribute type information included in the service type information in the OLA device description information.

[0129] Based on mapping method 1, the OLA gateway searches for the mapping relationship according to the device type, and can determine the node information and endpoint information of the corresponding Zigbee device. It further searches for the mapping relationship according to the service type information, and can determine the cluster information under the corresponding endpoint information. It searches for the mapping relationship according to the property type information, and determines the attribute information under the corresponding cluster information.

[0130] In some scenarios, a Zigbee device corresponds to multiple physical devices, and one physical device corresponds to one endpoint. The information of multiple functions of one endpoint can be stored in multiple clusters under one endpoint. When mapping, each physical device in the Zigbee device (that is, each endpoint) can be mapped as an independent device to an OLA device.

[0131] That is, mapping method 2 can be applied to situations where the Zigbee device corresponds to multiple physical devices. For example, if a Zigbee device corresponds to multiple Zigbee lights, each Zigbee light can be mapped to an OLA light for independent access control, which is conducive to achieving refined control of the Zigbee device.

[0132] In some embodiments, mapping the endpoint information in the Zigbee device description information to the device type information in the OLA device description information includes mapping the MAC address or network short address and endpoint of the Zigbee device to the device type information in the OLA device description information. That is, establishing a mapping relationship between the MAC address or network short address plus the endpoint of the Zigbee device and the device type information in the OLA device description information.

[0133] Figure 6 A schematic diagram illustrating a mapping relationship based on mapping mode 2 is shown.

[0134] In this example, one endpoint of the Zifeng device corresponds to a physical device. This endpoint includes Cluster 1 and Cluster 2. Based on Mapping Method 2, the endpoint of the Zifeng device can be treated as an OLA device. For example, endpoint information is mapped to OLA device type information, Cluster 1 and Cluster 2 are mapped to different service types, and the attribute information included in Cluster 1 and Cluster 2 is further mapped to the corresponding attribute type information in the corresponding service type. For the subsequent mapping methods, refer to the description of Mapping Method 1 and are not repeated here for the sake of brevity.

[0135] Optionally, in some embodiments, in mapping mode 2, the command corresponding to the attribute information in the Zigbee device description information can also be mapped to the action corresponding to the property type information in the OLA device description information. That is, the command for the Zigbee property information can be executed as an operation on the property type of the OLA device.

[0136] Optionally, in some embodiments, in mapping mode 2, the status in the Zigbee device description information may be reported to an event (envent) in the OLA device description information. That is, the Zigbee status report (e.g., attribute status report) may be executed as an event of the OLA device.

[0137] It should be understood that the above mapping method is only an example. In other embodiments, the OLA gateway can use other methods for mapping, such as establishing a mapping relationship between Zigbee device description information and OLA device description information according to service logic, for example, mapping in units of services, etc. This application is not limited to this.

[0138] It should also be understood that the embodiments of the present application can be applied to the mapping between the OLA device data model and the Zigbee device data model. Of course, the mapping logic of the embodiments of the present application can also be applied to the mapping of data models of two other different protocols, for example, the mapping between the data models of the first protocol and the second protocol. In this case, the mapping can be performed according to the rules defined by the data model of the first protocol and the rules defined by the data model of the second protocol. The specific mapping logic is similar, and the present application is not limited to this.

[0139] In some embodiments of this application, see Figure 4 , the method 200 further includes:

[0140] S221, the OLA gateway reports the OLA device description information of the Zigbee device to the OLA control terminal.

[0141] That is, the OLA gateway reports the Zigbee device as an OLA device to the OLA control end, so that the OLA control end can perform access control on the Zigbee device.

[0142] Optionally, the OLA control terminal may correspond to Figure 3 The control device 18 in the OLA gateway can be connected to the OLA control terminal via a wired or wireless network. The OLA control terminal allows users to operate to control devices connected to the OLA gateway. For example, users can use applications on the OLA control terminal to control devices connected to the OLA gateway.

[0143] Optionally, the OLA device description information of the Zigbee device reported by the OLA gateway may include at least one of the following:

[0144] The device type information of the Zigbee device, the service type information of the Zigbee device, the attribute type information of the Zigbee device, etc.

[0145] Optionally, in some embodiments, the OLA gateway may further report the device protocol type of the Zigbee device. For example, the device protocol type field supported by the Zigbee device may be set to Zigbee.

[0146] In some embodiments of this application, see Figure 4 , the method 200 further includes:

[0147] S222: The OLA gateway receives an access control command sent by the OLA control terminal, where the access control command includes OLA device description information of the device to be controlled.

[0148] Alternatively, the OLA control terminal may send the access control command to the OLA gateway via a standard OLA control interface. In other words, by mapping the Zigbee device description information of the Zigbee device to the OLA device description information, the OLA control terminal can perform access control on the Zigbee device as an OLA device without having to modify the existing OLA control interface, thereby achieving better compatibility with existing protocols.

[0149] In some embodiments, the access control command may include device type information, service type information, attribute type information, etc. of the device to be controlled, and may also include device protocol type information supported by the device to be controlled.

[0150] In some embodiments of this application, see Figure 4 , the method 200 further includes:

[0151] S230: Perform access control on the Zifeng device according to the mapping relationship.

[0152] For example, when the OLA gateway receives the access control command, it performs access control on the Zifeng device according to the mapping relationship.

[0153] Optionally, when receiving an access control command, the OLA gateway may determine whether to perform access control on the device to be controlled according to the mapping relationship based on the device protocol type information of the device to be controlled indicated in the access control command.

[0154] As an example, when the device protocol type of the device to be controlled is the Zifeng protocol, it is determined to perform access control on the device to be controlled according to the mapping relationship.

[0155] In some embodiments, the embodiments of the present application are applicable to the mapping of the device data model of the first protocol to the second protocol. When access control is required for a device that supports the first protocol, the OLA gateway can perform access control on the device to be controlled according to the mapping relationship corresponding to the first protocol when the device protocol type of the device to be controlled is the first protocol. The mapping relationship corresponding to the first protocol can be a mapping relationship obtained based on the device data model of the first protocol and the device data model of the second protocol.

[0156] In some embodiments, when determining to perform access control on the device to be controlled, the OLA gateway can determine the Zifeng device description information of the device to be controlled based on the OLA device description information of the device to be controlled in the access control command and the mapping relationship, and further perform access control on the device to be controlled based on the Zifeng device description information of the device to be controlled.

[0157] For mapping method 1, the OLA gateway can determine the node information of the device to be controlled, such as the MAC address or network short address, based on the device type information in the OLA device description information and the mapping relationship. Furthermore, based on the service type information in the OLA device description information and the mapping relationship, the cluster information of the endpoint under the node of the device to be controlled is determined. Then, based on the property type information in the OLA device description information, the attribute information of the device to be controlled is determined, thereby obtaining the Zigbee device description information, namely, the network short address (or MAC address) / endpoint / cluster / attribute. Access control is further performed on the Zigbee device based on the network short address (or MAC address) / endpoint / cluster / attribute.

[0158] For mapping method 2, the OLA gateway can determine the node information (e.g., network short address or MAC address) and endpoint information of the device to be controlled based on the device type information in the OLA device description information and the mapping relationship. Furthermore, the OLA gateway can determine the cluster of the device to be controlled based on the service type information in the OLA device description information and the mapping relationship. Then, the attribute information of the device to be controlled is determined based on the property type information in the OLA device description information, thereby obtaining the Zigbee device description information, namely, the network short address (or MAC address) / endpoint / cluster / attribute. Access control is then performed on the Zigbee device based on the network short address (or MAC address) / endpoint / cluster / attribute.

[0159] Combine Figure 7 and Figure 8 Taking the above two mapping methods as examples, the overall process of the access control method of the Zigbee device according to the embodiment of the present application is explained.

[0160] Figure 7 This is a flow chart of the access control method for Zigbee devices based on mapping mode 1, as shown in Figure 7 As shown, the following steps may be included:

[0161] S301: The Zigbee device reports the Zigbee device description information of the Zigbee device to the OLA gateway.

[0162] Optionally, the Zigbee device may report the Zigbee device description information of the Zigbee device to the OLA gateway when the Zigbee device is connected to the OLA gateway and the device authentication of the Zigbee device succeeds.

[0163] Optionally, the Zigbee device description information includes at least one of the following information:

[0164] Node information, endpoint information, cluster information and attribute information, manufacturer information, device name, and generation date information.

[0165] S302: The OLA gateway establishes a mapping relationship between the Zig device description information of the Zigbee device and the OLA device description information according to the rules defined by the Zigbee device data model and the rules defined by the OLA device data model.

[0166] For example, mapping the node information in the Zigbee device description information to the device type information in the OLA device description information;

[0167] Mapping the cluster information in the Zigbee device description information to the service type information in the OLA device description information;

[0168] Map the attribute information in the Zigbee device description information to the property type information in the OLA device description information.

[0169] S303: Report the OLA device description information of the Zigbee device to the OLA control terminal.

[0170] Optionally, the OLA device description information of the Zigbee device reported by the OLA gateway may include device type information, service type information, and attribute type information. Optionally, it may also include device protocol type information supported by the Zigbee device, for example, setting the device protocol type supported by the Zigbee device to Zigbee.

[0171] S304: The OLA control terminal may send an access control command for the Zigbee device to the OLA gateway.

[0172] For example, the access control command is sent to the OLA gateway through a standard OLA access control interface.

[0173] Optionally, the user may send an access control command by operating an application on the OLA control terminal.

[0174] Optionally, the access control command includes parameter information of the device to be controlled, such as device type information, service type information, attribute type information, etc. Optionally, it may also include device protocol type information supported by the device to be controlled.

[0175] S305: After receiving the access control command, the OLA gateway may parse the access control command to obtain parameter information of the device to be controlled.

[0176] Optionally, when the device protocol type supported by the device to be controlled is Zigbee, the OLA gateway may perform access control on the Zigbee in combination with the aforementioned mapping relationship.

[0177] For example, the Zigbee device description information is obtained according to the parameter information included in the access control command in combination with the mapping relationship, and access control is further performed on the Zigbee device based on the Zigbee device description information.

[0178] For example, the OLA gateway can search for the mapping relationship based on the device type information to determine the node information of the device to be controlled, such as the MAC address or network short address, and further search for the mapping relationship based on the service type information to determine the cluster information of the endpoint under the node of the device to be controlled. The attribute information of the device to be controlled can be determined by searching for the mapping relationship based on the property type information, thereby obtaining the Zigbee device description information of the Zigbee device, that is, the network short address (or MAC address) / endpoint / cluster / attribute, and further performing access control on the Zigbee device based on the network short address (or MAC address) / endpoint / cluster / attribute.

[0179] S306: The OLA gateway sends an access control command to the Zigbee device.

[0180] The access control command includes Zigbee device description information of the Zigbee device.

[0181] S307: Execute corresponding operations according to the access control command of the OLA gateway and return a result to the OLA gateway. For example, if the Zigbee device is a Zigbee light and the access control command is to turn on the light, the result may be that the light is turned on.

[0182] S308: The OLA gateway sends the control result to the OLA control terminal.

[0183] Figure 8 This is a flow chart of the access control method for Zigbee devices based on mapping mode 2. Figure 8 As shown, the following steps may be included:

[0184] S401: The Zigbee device reports the Zigbee device description information of the Zigbee device to the OLA gateway.

[0185] Optionally, the Zigbee device may report the Zigbee device description information of the Zigbee device to the OLA gateway when the Zigbee device is connected to the OLA gateway and the device authentication of the Zigbee device succeeds.

[0186] Optionally, the Zigbee device description information includes at least one of the following information:

[0187] Node information, endpoint information, cluster information and attribute information, manufacturer information, device name, and generation date information.

[0188] S402: The OLA gateway establishes a mapping relationship between the Zig device description information of the Zigbee device and the OLA device description information according to the rules defined by the Zigbee device data model and the rules defined by the OLA device data model.

[0189] For example, mapping the endpoint information in the Zigbee device description information to the device type information in the OLA device description information;

[0190] Mapping the cluster information in the Zigbee device description information to the service type information in the OLA device description information;

[0191] Map the attribute information in the Zigbee device description information to the property type information in the OLA device description information.

[0192] S403: Report the OLA device description information of the Zigbee device to the OLA control terminal.

[0193] Optionally, the OLA device description information of the Zigbee device reported by the OLA gateway may include device type information, service type information, and attribute type information. Optionally, it may also include device protocol type information supported by the Zigbee device, for example, setting the device protocol type supported by the Zigbee device to Zigbee.

[0194] S404: The OLA control terminal may send an access control command for the Zigbee device to the OLA gateway.

[0195] For example, the access control command is sent to the OLA gateway through a standard OLA access control interface.

[0196] Optionally, the user may send an access control command by operating an application on the OLA control terminal.

[0197] Optionally, the access control command includes parameter information of the device to be controlled, such as device type information, service type information, attribute type information, etc. Optionally, it may also include device protocol type information supported by the device to be controlled.

[0198] S405: After receiving the access control command, the OLA gateway may parse the access control command to obtain parameter information of the device to be controlled.

[0199] Optionally, when the device protocol type supported by the device to be controlled is Zigbee, the OLA gateway may perform access control on the Zigbee in combination with the aforementioned mapping relationship.

[0200] For example, the Zigbee device description information is obtained according to the parameter information included in the access control command in combination with the mapping relationship, and access control is further performed on the Zigbee device based on the Zigbee device description information.

[0201] For example, the OLA gateway can search for the mapping relationship based on the device type information to determine the node information and endpoint information of the device to be controlled, such as the MAC address or network short address and endpoint information, and further search for the mapping relationship based on the service type information to determine the cluster information of the endpoint under the node of the device to be controlled, and search for the mapping relationship based on the property type information to determine the attribute information of the device to be controlled, thereby obtaining the Zigbee device description information of the Zigbee device, that is, the network short address (or MAC address) / endpoint / cluster / attribute, and further perform access control on the Zigbee device based on the network short address (or MAC address) / endpoint / cluster / attribute.

[0202] S406: The OLA gateway sends an access control command to the Zigbee device.

[0203] The access control command includes Zigbee device description information of the Zigbee device.

[0204] S407: Execute corresponding operations according to the access control command of the OLA gateway and return a result to the OLA gateway. For example, if the Zigbee device is a Zigbee light and the access control command is to turn on the light, the result may be that the light is turned on.

[0205] S408: The OLA gateway sends the control result to the OLA control terminal.

[0206] To sum up, the OLA gateway maps the Zigbee device description information of the Zigbee device to the OLA device description information according to the rules defined by the Zigbee device data model specified in the Zigbee protocol and the rules defined by the OLA device data model specified in the OLA protocol, which is equivalent to simulating the Zigbee device as an OLA device. Furthermore, the OLA control end can use the general access control method for OLA devices to control access to the Zigbee device, which can better be compatible with the existing OLA protocol standard.

[0207] Figure 9 is a schematic block diagram of an OLA gateway 500 according to an embodiment of the present application. Figure 9 The OLA Gateway 500 includes:

[0208] The communication unit 510 is configured to receive Zifeng device description information of the Zifeng device reported by the Zifeng device;

[0209] The processing unit 520 is configured to establish a mapping relationship between the Zifeng device description information of the Zifeng device and the OLA device description information of the Zifeng device according to the Zifeng device data model and the OLA device data model; and

[0210] Access control is performed on the Zifeng device according to the mapping relationship.

[0211] In some embodiments of the present application, the Zifeng device description information includes at least one of the following information: node information, endpoint information, device type information, cluster information, and attribute information;

[0212] The OLA device description information includes at least one of the following information:

[0213] Device type information, service type information, attribute type information.

[0214] In some embodiments of the present application, the processing unit 520 is specifically configured to:

[0215] Mapping the node information in the Zifeng device description information to the device type information in the OLA device description information;

[0216] Mapping at least one cluster information included in the node information in the Zifeng device description information to the service type information in the OLA device description information;

[0217] The attribute information included in the at least one cluster information in the Zifeng device description information is mapped to the attribute type information included in the service type information in the OLA device description information to obtain the OLA device description information of the Zifeng device.

[0218] In some embodiments of the present application, if the first service type information in the OLA device description information corresponds to multiple clusters, the multiple cluster information belongs to the same endpoint of the Zifeng device, or belongs to different endpoints of the Zifeng device.

[0219] In some embodiments of the present application, the processing unit 520 is further configured to:

[0220] Mapping the other cluster information except the basic cluster information in the Zifeng device description information to the first service type information in the OLA device description information;

[0221] The basic cluster information in the Zifeng device description information is mapped to the second service type information in the OLA device description information.

[0222] In some embodiments of the present application, the processing unit 520 is further configured to:

[0223] Attribute information included in other cluster information except basic cluster information is mapped to corresponding attribute type information in the first service type.

[0224] In some embodiments of the present application, the processing unit 520 is further configured to:

[0225] The attribute information included in the basic cluster information is mapped to corresponding attribute type information in the second service type information.

[0226] In some embodiments of the present application, the Zifeng device includes multiple endpoint information, and the multiple endpoint information corresponds to the same physical device.

[0227] In some embodiments of the present application, the communication unit 510 is further configured to:

[0228] An access control command sent by the OLA control terminal is received, where the access control command includes OLA device description information of the device to be controlled, wherein the OLA device description information of the device to be controlled includes a device protocol type of the device to be controlled.

[0229] In some embodiments of the present application, the processing unit 520 is further configured to:

[0230] In a case where the device protocol type of the device to be controlled is the Zifeng protocol, determining the Zifeng device description information of the device to be controlled according to the OLA device description information of the device to be controlled and the mapping relationship;

[0231] Access control is performed on the device to be controlled according to the Zifeng device description information of the device to be controlled.

[0232] In some embodiments of the present application, the processing unit 520 is further configured to:

[0233] Determine the node information in the Zifeng device description information according to the device type information in the OLA device description information and the mapping relationship;

[0234] Determine the endpoint information and cluster information in the Zifeng device description information according to the service type information in the OLA device description information and the mapping relationship;

[0235] Determining the attribute information in the Zifeng device description information according to the attribute type information in the OLA device description information and the mapping relationship;

[0236] The Zifeng device description information of the device to be controlled is determined according to the node information, endpoint information, cluster information and attribute information.

[0237] In some embodiments of the present application, the processing unit 520 is further configured to:

[0238] Mapping the endpoint information in the Zifeng device description information to the device type information in the OLA device description information;

[0239] Mapping at least one cluster information included in the endpoint information in the Zifeng device description information to the service type information in the OLA device description information;

[0240] The attribute information included in the at least one cluster information in the Zifeng device description information is mapped to the attribute type information included in the service type information in the OLA device description information to obtain the OLA device description information corresponding to the Zifeng device.

[0241] In some embodiments of the present application, the Zifeng device includes a plurality of endpoint information, and each of the plurality of endpoint information corresponds to a physical device.

[0242] In some embodiments of the present application, the communication unit 510 is further configured to:

[0243] An access control command sent by the OLA control terminal is received, where the access control command includes OLA device description information of the device to be controlled, wherein the OLA device description information of the device to be controlled includes a device protocol type of the device to be controlled.

[0244] In some embodiments of the present application, the processing unit 520 is further configured to:

[0245] In a case where the device protocol type of the device to be controlled is the Zifeng protocol, determining the Zifeng device description information of the device to be controlled according to the OLA device description information of the device to be controlled and the mapping relationship;

[0246] Access control is performed on the device to be controlled according to the Zifeng device description information of the device to be controlled.

[0247] In some embodiments of the present application, the processing unit 520 is further configured to:

[0248] Determine the node information and endpoint information in the Zifeng device description information according to the device type information in the OLA device description information and the mapping relationship;

[0249] Determining cluster information in the Zifeng device description information according to the service type information in the OLA device description information and the mapping relationship;

[0250] Determining the attribute information in the Zifeng device description information according to the attribute type information in the OLA device description information and the mapping relationship;

[0251] The Zifeng device description information of the device to be controlled is determined according to the node information, endpoint information, cluster information and attribute information.

[0252] In some embodiments of the present application, the communication unit 510 is further configured to:

[0253] Send the OLA device description information of the Zifeng device to the OLA control terminal.

[0254] In some embodiments of the present application, the OLA device description information of the Zifeng device includes device protocol type information of the Zifeng device, and the device protocol type information of the Zifeng device is the Zifeng protocol.

[0255] In some embodiments of the present application, the processing unit 520 is further configured to:

[0256] Mapping the command corresponding to the attribute information in the Zifeng device description information to the operation corresponding to the attribute type information in the OLA device description information;

[0257] Report the status in the Zifeng device description information to the event in the OLA device description information.

[0258] In some embodiments of the present application, the communication unit 510 is specifically configured to:

[0259] The Zifeng device description information reported by the Zifeng device when the Zifeng device accesses the OLA gateway and the OLA gateway successfully authenticates the Zifeng device is received.

[0260] Alternatively, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0261] It should be understood that the OLA gateway 500 according to the embodiment of the present application may correspond to the OLA gateway in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the OLA gateway 500 are respectively to achieve Figures 4 to 8 The corresponding process of the OLA gateway in the illustrated method embodiment will not be described in detail here for the sake of brevity.

[0262] Figure 10 It is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application. Figure 10 The communication device 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0263] Alternatively, as Figure 10 As shown, the communication device 600 may further include a memory 620. The processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0264] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0265] Alternatively, as Figure 10 As shown, 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, to send information or data to other devices, or to receive information or data sent by other devices.

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

[0267] Optionally, the communication device 600 may specifically be an OLA gateway in an embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the OLA gateway in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0268] In some embodiments, the processor 610 in the communication device 600 may correspond to Figure 9 The processing unit 520 in the processor 610 can execute the operations or functions performed by the processing unit 520, which will not be repeated here for the sake of brevity.

[0269] In some embodiments, the transceiver 630 in the communication device 600 may correspond to Figure 9 The communication unit 510 in the embodiment of the present invention can perform the operations or functions performed by the communication unit 510, which will not be described here for the sake of brevity.

[0270] Figure 11 It is a schematic structural diagram of the chip of an embodiment of the present application. Figure 11 The chip 700 shown includes a processor 710, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0271] Alternatively, as Figure 11 As shown, the chip 700 may further include a memory 720. The processor 710 may call and execute a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0272] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0273] 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 obtain information or data sent by other devices or chips.

[0274] 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.

[0275] Optionally, the chip can be applied to the OLA gateway in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the OLA gateway in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0276] In some embodiments, the processor 710 in the chip 700 may correspond to Figure 9 The processing unit 520 in the processor 710 can execute the operations or functions performed by the processing unit 520, which will not be repeated here for the sake of brevity.

[0277] In some embodiments, the input interface 730 and the output interface 740 in the chip 700 may correspond to Figure 9 The communication unit 510, the input interface 730 and the output interface 740 can perform the operations or functions performed by the communication unit 510, and for the sake of brevity, they are not repeated here.

[0278] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0279] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented as a hardware decoding processor, or can be implemented by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0280] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as 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 RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0281] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present 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 RAM bus random access memory (DR RAM). In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0282] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0283] Optionally, the computer-readable storage medium can be applied to the OLA gateway in the embodiment of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the OLA gateway in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.

[0284] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0285] Optionally, the computer program product can be applied to the OLA gateway in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the OLA gateway in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.

[0286] The embodiment of the present application also provides a computer program.

[0287] Optionally, the computer program can be applied to the OLA gateway in the embodiment of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the OLA gateway in the various methods of the embodiment of the present application. For the sake of brevity, they are not repeated here.

[0288] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0289] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0290] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0291] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0292] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0293] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0294] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any modifications or substitutions that can be readily conceived by a person skilled in the art within the technical scope 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 based on the scope of protection of the claims.

Claims

1. A method for controlling access to a Zifeng device, characterized in that: include: Developing an intelligent alliance OLA gateway to receive Zifeng device description information of the Zifeng device reported by the Zifeng device; The OLA gateway establishes a mapping relationship between the Zifeng device description information of the Zifeng device and the OLA device description information of the Zifeng device according to the Zifeng device data model and the OLA device data model; Performing access control on the Zifeng device according to the mapping relationship; The Zifeng device description information includes node information, cluster information and attribute information, and the OLA device description information includes device type information, service type information and attribute type information; The OLA gateway establishes a mapping relationship between the Zifeng device description information of the Zifeng device and the OLA device description information of the Zifeng device according to the Zifeng device data model and the OLA device data model, including: Mapping the node information in the Zifeng device description information to the device type information in the OLA device description information; Mapping at least one cluster information included in the node information in the Zifeng device description information to the service type information in the OLA device description information; The attribute information included in the at least one cluster information in the Zifeng device description information is mapped to the attribute type information included in the service type information in the OLA device description information to obtain the OLA device description information of the Zifeng device.

2. The method according to claim 1, characterized in that The Zifeng device description information also includes at least one of the following information: endpoint information, device type information.

3. The method according to claim 2, characterized in that If the first service type information in the OLA device description information corresponds to multiple cluster information, the multiple cluster information belongs to the same endpoint of the Zifeng device, or belongs to different endpoints of the Zifeng device.

4. The method according to claim 2, characterized in that The mapping of at least one cluster information included in the node information in the Zifeng device description information to the service type information in the OLA device description information includes: Mapping the other cluster information except the basic cluster information in the Zifeng device description information to the first service type information in the OLA device description information; The basic cluster information in the Zifeng device description information is mapped to the second service type information in the OLA device description information.

5. The method according to claim 4, characterized in that The mapping of the attribute information included in the at least one cluster information in the Zifeng device description information to the attribute type information included in the service type in the OLA device description information includes: Attribute information included in other cluster information except basic cluster information is mapped to corresponding attribute type information in the first service type.

6. The method according to claim 4, characterized in that The mapping of the attribute information included in the at least one cluster information in the Zifeng device description information to the attribute type information included in the service type information in the OLA device description information includes: The attribute information included in the basic cluster information is mapped to corresponding attribute type information in the second service type information.

7. The method according to any one of claims 3 to 6, characterized in that The Zifeng device includes multiple endpoint information, and the multiple endpoint information corresponds to the same physical device.

8. The method according to any one of claims 2 to 6, characterized in that The method further comprises: The OLA gateway receives the access control command sent by the OLA control terminal, where the access control command includes the OLA device description information of the device to be controlled, wherein the OLA device description information of the device to be controlled includes the device protocol type of the device to be controlled.

9. The method according to claim 8, characterized in that The method further comprises: In a case where the device protocol type of the device to be controlled is the Zifeng protocol, determining the Zifeng device description information of the device to be controlled according to the OLA device description information of the device to be controlled and the mapping relationship; Access control is performed on the device to be controlled according to the Zifeng device description information of the device to be controlled.

10. The method according to claim 9, characterized in that The determining, according to the OLA device description information of the device to be controlled and the mapping relationship, the Zifeng device description information of the device to be controlled includes: Determine the node information in the Zifeng device description information according to the device type information in the OLA device description information and the mapping relationship; Determine the endpoint information and cluster information in the Zifeng device description information according to the service type information in the OLA device description information and the mapping relationship; Determining the attribute information in the Zifeng device description information according to the attribute type information in the OLA device description information and the mapping relationship; The Zifeng device description information of the device to be controlled is determined according to the node information, endpoint information, cluster information and attribute information.

11. The method according to claim 2, characterized in that The OLA gateway establishes a mapping relationship between the Zifeng device description information of the Zifeng device and the OLA device description information of the Zifeng device according to the Zifeng device data model and the OLA device data model, further comprising: Mapping the endpoint information in the Zifeng device description information to the device type information in the OLA device description information; Mapping at least one cluster information included in the endpoint information in the Zifeng device description information to the service type information in the OLA device description information; The attribute information included in the at least one cluster information in the Zifeng device description information is mapped to the attribute type information included in the service type information in the OLA device description information to obtain the OLA device description information corresponding to the Zifeng device.

12. The method according to claim 11, characterized in that The Zifeng device includes a plurality of endpoint information, and each of the plurality of endpoint information corresponds to a physical device.

13. The method according to claim 11, characterized in that The method further comprises: An access control command sent by the OLA control terminal is received, where the access control command includes OLA device description information of the device to be controlled, wherein the OLA device description information of the device to be controlled includes a device protocol type of the device to be controlled.

14. The method according to claim 13, characterized in that The method further comprises: In a case where the device protocol type of the device to be controlled is the Zifeng protocol, determining the Zifeng device description information of the device to be controlled according to the OLA device description information of the device to be controlled and the mapping relationship; Access control is performed on the device to be controlled according to the Zifeng device description information of the device to be controlled.

15. The method according to claim 14, characterized in that The determining, according to the OLA device description information of the device to be controlled and the mapping relationship, the Zifeng device description information of the device to be controlled includes: Determine the node information and endpoint information in the Zifeng device description information according to the device type information in the OLA device description information and the mapping relationship; Determining cluster information in the Zifeng device description information according to the service type information in the OLA device description information and the mapping relationship; Determining the attribute information in the Zifeng device description information according to the attribute type information in the OLA device description information and the mapping relationship; The Zifeng device description information of the device to be controlled is determined according to the node information, endpoint information, cluster information and attribute information.

16. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The OLA gateway sends the OLA device description information of the Zifeng device to the OLA control terminal.

17. The method according to claim 16, characterized in that The OLA device description information of the Zifeng device includes device protocol type information of the Zifeng device, and the device protocol type information of the Zifeng device is the Zifeng protocol.

18. The method according to any one of claims 1 to 6, characterized in that The OLA gateway establishes a mapping relationship between the Zifeng device description information of the Zifeng device and the OLA device description information of the Zifeng device according to the Zifeng device data model and the OLA device data model, further comprising: Mapping the command corresponding to the attribute information in the Zifeng device description information to the operation corresponding to the attribute type information in the OLA device description information; Report the status in the Zifeng device description information to the event in the OLA device description information.

19. The method according to any one of claims 1 to 6, characterized in that The Development Smart Alliance OLA gateway receives the Zifeng device description information of the Zifeng device reported by the Zifeng device, including: The OLA gateway receives the Zifeng device description information reported by the Zifeng device when the Zifeng device accesses the OLA gateway and the OLA gateway successfully authenticates the Zifeng device.

20. A development of an intelligent alliance OLA gateway, characterized in that, include: A communication unit, configured to receive Zifeng device description information of the Zifeng device reported by the Zifeng device; a processing unit, configured to establish a mapping relationship between the Zifeng device description information of the Zifeng device and the OLA device description information of the Zifeng device according to the Zifeng device data model and the OLA device data model; as well as Performing access control on the Zifeng device according to the mapping relationship; The Zifeng device description information includes node information, cluster information and attribute information, and the OLA device description information includes device type information, service type information and attribute type information; The processing unit is specifically configured to: Mapping the node information in the Zifeng device description information to the device type information in the OLA device description information; Mapping at least one cluster information included in the node information in the Zifeng device description information to the service type information in the OLA device description information; The attribute information included in the at least one cluster information in the Zifeng device description information is mapped to the attribute type information included in the service type information in the OLA device description information to obtain the OLA device description information of the Zifeng device.

21. The OLA gateway according to claim 20, wherein: The Zifeng device description information also includes at least one of the following information: endpoint information, device type information.

22. The OLA gateway according to claim 21, wherein: If the first service type information in the OLA device description information corresponds to multiple clusters, the multiple cluster information belongs to the same endpoint of the Zifeng device, or belongs to different endpoints of the Zifeng device.

23. The OLA gateway according to claim 21, wherein: The processing unit is further configured to: Mapping the other cluster information except the basic cluster information in the Zifeng device description information to the first service type information in the OLA device description information; The basic cluster information in the Zifeng device description information is mapped to the second service type information in the OLA device description information.

24. The OLA gateway according to claim 23, wherein: The processing unit is further configured to: Attribute information included in other cluster information except basic cluster information is mapped to corresponding attribute type information in the first service type.

25. The OLA gateway according to claim 23, wherein: The processing unit is further configured to: The attribute information included in the basic cluster information is mapped to corresponding attribute type information in the second service type information.

26. The OLA gateway according to any one of claims 22 to 25, characterized in that: The Zifeng device includes multiple endpoint information, and the multiple endpoint information corresponds to the same physical device.

27. The OLA gateway according to any one of claims 21 to 25, characterized in that: The communication unit is further configured to: An access control command sent by the OLA control terminal is received, where the access control command includes OLA device description information of the device to be controlled, wherein the OLA device description information of the device to be controlled includes a device protocol type of the device to be controlled.

28. The OLA gateway according to claim 27, wherein: The processing unit is further configured to: In a case where the device protocol type of the device to be controlled is the Zifeng protocol, determining the Zifeng device description information of the device to be controlled according to the OLA device description information of the device to be controlled and the mapping relationship; Access control is performed on the device to be controlled according to the Zifeng device description information of the device to be controlled.

29. The OLA gateway according to claim 28, wherein: The processing unit is further configured to: Determine the node information in the Zifeng device description information according to the device type information in the OLA device description information and the mapping relationship; Determine the endpoint information and cluster information in the Zifeng device description information according to the service type information in the OLA device description information and the mapping relationship; Determining the attribute information in the Zifeng device description information according to the attribute type information in the OLA device description information and the mapping relationship; The Zifeng device description information of the device to be controlled is determined according to the node information, endpoint information, cluster information and attribute information.

30. The OLA gateway according to claim 21, wherein: The processing unit is further configured to: Mapping the endpoint information in the Zifeng device description information to the device type information in the OLA device description information; Mapping at least one cluster information included in the endpoint information in the Zifeng device description information to the service type information in the OLA device description information; The attribute information included in the at least one cluster information in the Zifeng device description information is mapped to the attribute type information included in the service type information in the OLA device description information to obtain the OLA device description information corresponding to the Zifeng device.

31. The OLA gateway according to claim 30, wherein: The Zifeng device includes a plurality of endpoint information, and each of the plurality of endpoint information corresponds to a physical device.

32. The OLA gateway according to claim 30, wherein: The communication unit is further configured to: An access control command sent by the OLA control terminal is received, where the access control command includes OLA device description information of the device to be controlled, wherein the OLA device description information of the device to be controlled includes a device protocol type of the device to be controlled.

33. The OLA gateway according to claim 32, wherein: The processing unit is further configured to: In a case where the device protocol type of the device to be controlled is the Zifeng protocol, determining the Zifeng device description information of the device to be controlled according to the OLA device description information of the device to be controlled and the mapping relationship; Access control is performed on the device to be controlled according to the Zifeng device description information of the device to be controlled.

34. The OLA gateway according to claim 33, wherein: The processing unit is further configured to: Determine the node information and endpoint information in the Zifeng device description information according to the device type information in the OLA device description information and the mapping relationship; Determining cluster information in the Zifeng device description information according to the service type information in the OLA device description information and the mapping relationship; Determining the attribute information in the Zifeng device description information according to the attribute type information in the OLA device description information and the mapping relationship; The Zifeng device description information of the device to be controlled is determined according to the node information, endpoint information, cluster information and attribute information.

35. The OLA gateway according to any one of claims 20 to 25, characterized in that: The communication unit is further configured to: Send the OLA device description information of the Zifeng device to the OLA control terminal.

36. The OLA gateway according to claim 35, characterized in that The OLA device description information of the Zifeng device includes device protocol type information of the Zifeng device, and the device protocol type information of the Zifeng device is the Zifeng protocol.

37. The OLA gateway according to any one of claims 20 to 25, characterized in that: The processing unit is further configured to: Mapping the command corresponding to the attribute information in the Zifeng device description information to the operation corresponding to the attribute type information in the OLA device description information; Report the status in the Zifeng device description information to the event in the OLA device description information.

38. The OLA gateway according to any one of claims 20 to 25, characterized in that: The communication unit is specifically used for: The Zifeng device description information reported by the Zifeng device when the Zifeng device accesses the OLA gateway and the OLA gateway successfully authenticates the Zifeng device is received.

39. A development of an intelligent alliance OLA gateway, characterized in that, include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 19.

40. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 19.

41. A computer-readable storage medium, characterized in that Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 19.

42. A computer program product, characterized in that The method comprises computer program instructions for causing a computer to execute the method according to any one of claims 1 to 19.

Images