WO2022087795A1

WO2022087795A1 - Resource mapping method and apparatus, device, and storage medium

Info

Publication number: WO2022087795A1
Application number: PCT/CN2020/123782
Authority: WO
Inventors: 包永明; 张军
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-10-26
Filing date: 2020-10-26
Publication date: 2022-05-05
Also published as: CN115968543A; CN115968543A8

Abstract

The present application relates to the technical field of the Internet of Things. Disclosed are a resource mapping method and apparatus, a device, and a storage medium. The method comprises: creating a first OCF device corresponding to a first physical device, wherein the first physical device is a device based on a target communication protocol, and the first OCF device is a virtual OCF device mapped from the first physical device; creating a first OCF resource on the basis of a mapping relationship between the first OCF device and the first physical device, wherein the first OCF resource has a mapping relationship with a first object in the first physical device; and generating and storing a resource address of the first OCF resource, wherein the resource address of the first OCF resource is used to determine the first object having the mapping relationship with the first OCF resource. In the present application, the relationship between an OCF resource address and an object in a target communication protocol is specified, thereby enhancing the interconnection capacity of an OCF protocol with other standard protocols.

Description

Resource mapping method, apparatus, device and storage medium

technical field

The embodiments of the present application relate to the technical field of the Internet of Things, and in particular, to a resource mapping method, apparatus, device, and storage medium.

Background technique

The Internet of things (IOT) and artificial intelligence (Artificial Intelligence, AI) are increasingly integrated. On the one hand, the Internet of Things is moving from "connection" to "intelligence"; on the other hand, artificial intelligence is moving from "cloud" to "edge", and the two are working together to promote the Internet of Things to the Internet of Intelligences.

The world's largest international standards alliance for the Internet of Intelligence is OCF (Open Connectivity Foundation). The OCF standard supports search and communication between smart devices without being restricted by manufacturers, operating systems, chips or physical transmission. It provides technical specifications for realizing seamless connection between various physical medium layer, transport layer and application layer devices. OCF has a wide range of flexible application scenarios: First, the OCF client (Client) (such as a mobile phone application) and OCF device (Server) (such as an air conditioner) can interact. and other information to obtain and set; secondly, multiple OCF clients can control OCF devices at the same time, for example, users can flexibly control the same device at home through smart phones, smart TVs, and smart speakers; again, through bridging (Bridging), OCF clients can interact with other standard devices, such as Bluetooth, Zigbee (Zigbee), etc. Finally, OCF devices can also be bridged and controlled by other standard clients.

However, the current interaction scheme between the OCF client and other standard devices needs further research.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a resource mapping method, apparatus, device, and storage medium. The technical solution is as follows:

According to an aspect of the embodiments of the present application, a resource mapping method is provided, applied to a gateway device, the method includes:

creating a first OCF device corresponding to a first physical device, where the first physical device is a device based on a target communication protocol, and the first OCF device is a virtual OCF device mapped by the first physical device;

creating a first OCF resource based on the mapping relationship between the first OCF device and the first physical device, where the first OCF resource has a mapping relationship with the first object in the first physical device;

A resource address of the first OCF resource is generated and stored, where the resource address of the first OCF resource is used to determine the first object that has a mapping relationship with the first OCF resource.

According to an aspect of the embodiments of the present application, a resource mapping apparatus is provided, and the apparatus includes:

A device creation module, configured to create a first OCF device corresponding to a first physical device, where the first physical device is a device based on a target communication protocol, and the first OCF device is a virtual OCF mapped by the first physical device equipment;

A resource creation module, configured to create a first OCF resource based on the mapping relationship between the first OCF device and the first physical device, the first OCF resource and the first object in the first physical device has a mapping relationship;

An address generation module, configured to generate and store a resource address of the first OCF resource, where the resource address of the first OCF resource is used to determine the first object that has a mapping relationship with the first OCF resource.

According to an aspect of the embodiments of the present application, a gateway device is provided, and the gateway device includes a processor, a memory, and a transceiver;

The processor is configured to create a first OCF device corresponding to a first physical device, where the first physical device is a device based on a target communication protocol, and the first OCF device is a virtual device mapped by the first physical device. OCF equipment;

The processor is further configured to create a first OCF resource based on the mapping relationship between the first OCF device and the first physical device, the first OCF resource and the first OCF resource in the first physical device. An object has a mapping relationship;

The processor is further configured to generate and store a resource address of the first OCF resource, where the resource address of the first OCF resource is used to determine the first object that has a mapping relationship with the first OCF resource.

According to an aspect of the embodiments of the present application, a computer-readable storage medium is provided, where a computer program is stored in the storage medium, and the computer program is configured to be executed by a processor to implement the above resource mapping method.

According to an aspect of the embodiments of the present application, a chip is provided, the chip includes a programmable logic circuit and/or program instructions, and when the chip runs on a gateway device, it is used to implement the above resource mapping method.

According to an aspect of the embodiments of the present application, a computer program product is provided, which, when the computer program product runs on a gateway device, enables the gateway device to execute the above resource mapping method.

The technical solutions provided in the embodiments of the present application can bring the following beneficial effects:

A mapping relationship between the first OCF resource and the first object in the first physical device is established by the gateway device, and the resource address of the first OCF resource is generated and stored, so as to determine the mapping relationship with the first OCF resource. The first object specifies the relationship between the OCF resource address and the object under the target communication protocol, thereby enhancing the interconnection capability between the OCF protocol and other standard protocols.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the drawings that are used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort.

1 is a schematic diagram of a device model structure of a Zigbee device provided by an embodiment of the present application;

2 is a schematic diagram of realizing the interaction between an OCF client and a Zigbee device through a bridge platform provided by an embodiment of the present application;

3 is a schematic diagram of a device model structure of a BLE mesh device provided by an embodiment of the present application;

4 is a schematic diagram of realizing interaction between an OCF client and a BLE mesh device through a bridge platform provided by an embodiment of the present application;

5 is a schematic diagram of an implementation environment provided by an embodiment of the present application;

6 is a structural block diagram of a gateway device provided by an embodiment of the present application;

7 is a flowchart of a resource mapping method provided by an embodiment of the present application;

8 is a flowchart of a resource mapping method provided by another embodiment of the present application;

9 is a flowchart of a resource mapping method provided by another embodiment of the present application;

10 is a flowchart of a resource mapping method provided by another embodiment of the present application;

11 is a block diagram of a resource mapping apparatus provided by an embodiment of the present application;

FIG. 12 is a structural block diagram of a gateway device provided by an embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

Zigbee is a low-speed and short-distance transmission wireless network protocol. Zigbee network has the characteristics of large capacity, low latency, low power consumption, high security and high stability. Home improvement, smart office and other complex smart scenarios provide stable and secure LAN communication.

FIG. 1 shows a schematic diagram of a device model structure of a Zigbee device. After the Zigbee device is connected to the network, it becomes a node (Node) in the Zigbee network. The node may have multiple endpoints (Endpoints), and there may be multiple service clusters (Server Cluster, referred to as "cluster") under each endpoint. There may be multiple attributes (Attribute) under a cluster, and each attribute has its own data type and data content (Type&Data).

OCF clients can interact with Zigbee devices. Please refer to FIG. 2, which shows the interaction between the OCF client and the Zigbee device through the bridge platform. The bridge platform 110 includes the following functional modules: a virtual OCF server 112 , a bridging function 114 and a virtual Zigbee client 116 . The communication between the OCF client 120 and the virtual OCF server 112 may be based on the OCF protocol, and the communication between the virtual Zigbee client 116 and the Zigbee device 130 may be based on the Zigbee protocol. For example, the above Zigbee protocol may be the Zigbee 3.0 protocol or may also be the Zigbee protocol of another existing version or a subsequent evolution version, which is not limited in this embodiment of the present application.

The bridge function module 114 is used to realize the conversion between the OCF protocol and the Zigbee protocol. For example, the role of the bridging function module 114 includes converting the information based on the OCF protocol sent by the OCF client 120 into the information based on the Zigbee protocol that can be recognized by the Zigbee device 130 . In addition, the role of the bridging function module 114 may further include converting the Zigbee protocol-based information sent by the Zigbee device 130 into OCF protocol-based information identifiable by the OCF client 120 .

Optionally, the bridging function module 114 may establish a mapping relationship between the information based on the OCF protocol and the information based on the Zigbee protocol, so as to realize the conversion between the information based on the OCF protocol and the information based on the Zigbee protocol. As shown in Table 1 below, it shows the translation model between the Zigbee protocol and the OCF protocol.

Table I

Zigbee协议Zigbee Protocol	映射计数map count	OCF协议OCF protocol	映射计数map count
节点(Node)Node	11	OCF设备(OCF Device)OCF Device (OCF Device)	11
服务集群(Server Cluster)Server Cluster	11	OCF资源(OCF Resource)OCF Resource	nn
属性(Attribute)Attribute	11	OCF资源属性(OCF Resource property)OCF Resource property	11

From the above Table 1, three sets of mapping relationships between the information based on the Zigbee protocol and the information based on the OCF protocol can be obtained, as well as the mapping counts of both parties in each set of mapping relationships. The three groups of mapping relationships based on Table 1 include: the mapping relationship between a node (Node) and an OCF device (OCF Device), and the mapping relationship is a 1-to-1 mapping relationship; a service cluster (Server Cluster) and an OCF resource (OCF Resource), and the mapping relationship is a 1-to-n mapping relationship; the mapping relationship between attributes (Attribute) and OCF resource attributes (OCF Resource property), and the mapping relationship is a 1-to-1 mapping relationship .

In the following, taking the Zigbee device as the color temperature lamp as an example, the translation model between the Zigbee protocol and the OCF protocol is introduced. As shown in Table 2 below:

Table II

Compared with the earlier classic Bluetooth, BLE (Bluetooth Low Energy, Bluetooth Low Energy) greatly reduces the power consumption of the device and has been widely used. BLE mesh (star network) is a network support designed for large-scale nodes to communicate with each other. Its goal is to establish a trusted and secure network, fully interoperable operations, mature ecosystems, and industrial-level applications. Supports networking with a large number of nodes. The way BLE mesh works is managed flood (managed flood message propagation), the flooding way makes the message propagation very reliable, easy to expand, and the performance can meet the commercial and industrial market.

Figure 3 shows a schematic diagram of the device model structure of a BLE mesh device. After the BLE mesh device is connected to the network, it becomes a node (Node) in the BLE mesh network. The node may have multiple elements (Element), and there may be multiple service models (Server Model, referred to as "model") under each element. , there may be multiple attributes (State, or "state") under each model, and each attribute has its own data type and data content (Type&Data).

OCF clients can interact with BLE mesh devices. Please refer to Figure 4, which shows the interaction between the OCF client and the BLE mesh device through the bridge platform. The bridge platform 110 includes the following functional modules: a virtual OCF server 112 , a bridging function module (Bridging Function) 114 and a virtual BLE mesh client 118 . Communication between the OCF client 120 and the virtual OCF server 112 may be based on the OCF protocol, and communication between the virtual BLE mesh client 118 and the BLE mesh device 140 may be based on the BLE mesh protocol.

The bridge function module 114 is used to realize the conversion between the OCF protocol and the BLE mesh protocol. For example, the role of the bridge function module 114 includes converting the information based on the OCF protocol sent by the OCF client 120 into information based on the BLE mesh protocol that can be recognized by the BLE mesh device 140. In addition, the role of the bridging function module 114 may also include converting the information based on the BLE mesh protocol sent by the BLE mesh device 140 into information based on the OCF protocol identifiable by the OCF client 120.

Optionally, the bridging function module 114 can establish a mapping relationship between the information based on the OCF protocol and the information based on the BLE mesh protocol, so as to realize the conversion between the information based on the OCF protocol and the information based on the BLE mesh protocol. As shown in Table 3 below, it shows the translation model between the BLE mesh protocol and the OCF protocol.

Table 3

BLE mesh协议BLE mesh protocol	映射计数map count	OCF协议OCF protocol	映射计数map count
节点(Node)Node	11	OCF设备(OCF Device)OCF Device (OCF Device)	11
服务模型(Server Model)Server Model	11	OCF资源(OCF Resource)OCF Resource	11
属性(State)Properties (State)	11	OCF资源属性(OCF Resource property)OCF Resource property	11

From the above Table 3, three sets of mapping relationships between the information based on the BLE mesh protocol and the information based on the OCF protocol can be obtained, as well as the mapping counts of both parties in each set of mapping relationships. The three groups of mapping relationships based on Table 3 include: the mapping relationship between the node (Node) and the OCF device (OCF Device), and the mapping relationship is a 1-to-1 mapping relationship; the service model (Server Model) and the OCF resource (OCF Resource), and the mapping relationship is a 1-to-1 mapping relationship; the mapping relationship between attributes (State) and OCF resource properties (OCF Resource property), and the mapping relationship is a 1-to-1 mapping relationship .

Next, take the BLE mesh device as the color temperature lamp as an example to introduce the translation model between the BLE mesh protocol and the OCF protocol. As shown in Table 4 below:

Table 4

The translation model between the Zigbee protocol and the OCF protocol, and the translation model between the BLE mesh protocol and the OCF protocol, only specify the mapping relationship between OCF resources and the Zigbee cluster (Cluster) and the BLE mesh model (Model). In the embodiment of the present application, the relationship between the OCF resource address and the Zigbee cluster (Cluster) and the BLE mesh model (Model) is specified, thereby enhancing the interconnection capability between the OCF protocol and other standard protocols.

Hereinafter, the technical solutions of the present application will be introduced and described through several embodiments.

Please refer to FIG. 5 , which shows a schematic diagram of an implementation environment provided by an embodiment of the present application. The implementation environment may include: a terminal 210 , a Zigbee device/BLE mesh device 220 , and a gateway device 230 . The implementation environment may be an intelligent networked system.

The terminal 210 may include various handheld devices with wireless communication functions (such as mobile phones, tablet computers, etc.), in-vehicle devices, wearable devices, computing devices, or other processing devices connected to wireless modems, and various forms of user equipment (User Equipment). Equipment, UE), mobile station (Mobile Station, MS), terminal device (terminal device) and so on. For convenience of description, in the embodiments of the present application, the devices mentioned above are collectively referred to as terminals.

Zigbee device/BLE mesh device 220 refers to a smart networking device with network access capability under Zigbee networking/BLE mesh networking, such as Zigbee device/BLE mesh device 220 can be a smart home device, terminal device, or other devices with network access. This is not limited in this embodiment of the present application. In an example, taking the implementation environment as a home intelligent networking system as an example, the Zigbee device/BLE mesh device 220 may be smart home devices such as smart TVs, smart speakers, smart air conditioners, smart lights, smart doors and windows, smart curtains, and smart sockets.

The gateway device 230 is also referred to as a network connector and a protocol converter, and is a computer system or device that provides data conversion services between multiple networks. Between two systems or devices that use different communication protocols, data formats or languages, or even have completely different architectures, the gateway device is equivalent to a translator. The gateway device can parse the received information, and repackage and send it to The destination system or destination device can meet the needs of the destination system or destination device, and the gateway device can also play the role of filtering and security.

Taking the access process of the OCF client 211 to the Zigbee device/BLE mesh device 220 as an example, the gateway device 230 is connected to the terminal 210 and the Zigbee device/BLE mesh device 220 respectively, and the OCF client 211 is installed and running in the terminal 210. The OCF client The terminal 211 can access the Zigbee device/BLE mesh device 220 through the gateway device 230. For example, the user sends an access request to the gateway device 230 by operating the OCF client 211 running on the terminal 210. The access request is information based on the OCF protocol. After receiving the access request, the gateway device 230 converts the access request. The access request is based on the information of the Zigbee protocol/BLE mesh protocol, and then the gateway device 230 sends the converted access request to the Zigbee device/BLE mesh device 220, thereby completing the OCF client 211 to the Zigbee device/BLE mesh device 220. access process.

It should be noted that, in the embodiment of this application, the "access" of the OCF client to the Zigbee device/BLE mesh device includes two methods: "acquisition" and "setting". The status of the BLE mesh device, etc. "Settings" refers to the OCF client to select, set, and update the status of the Zigbee device/BLE mesh device. In addition, in this embodiment of the present application, the "access" of the OCF client to the Zigbee device/BLE mesh device may also be referred to as the "operation" of the OCF client to the Zigbee device/BLE mesh device, but those skilled in the art can understand that meaning.

Please refer to FIG. 6 , which shows a structural block diagram of a gateway device provided by an embodiment of the present application. As shown in FIG. 6 , the gateway device 300 includes a virtual OCF server 310, a bridge function module 320, and a virtual Zigbee client/virtual BLE mesh client 330.

The virtual OCF server 310 is a functional module in the gateway device 300 for interacting with the OCF client 301 , and the virtual OCF server 310 and the OCF client 301 interact based on the OCF protocol.

The virtual Zigbee client/virtual BLE mesh client 330 is a functional module in the gateway device 300 for interacting with the Zigbee device/BLE mesh device 302, and the virtual Zigbee client/virtual BLE mesh client 330 communicates with the Zigbee device/BLE mesh device The interaction between 302 is based on the Zigbee protocol/BLE mesh protocol. The Zigbee device/BLE mesh device 302 can act as a Zigbee server/BLE mesh server and receive an access request from a virtual Zigbee client/virtual BLE mesh client 330.

The bridging functional module 320 is a functional module used to realize the conversion between two different protocol information in the gateway device 300, that is, the bridging functional module 320 is used to convert the information based on the OCF protocol into the information based on the Zigbee protocol/BLE mesh protocol, Or used to convert information based on Zigbee protocol/BLE mesh protocol to information based on OCF protocol.

In an example, when the OCF client 301 initiates an access request to the Zigbee device/BLE mesh device 302, the OCF client 301 first sends a first access request to the gateway device 300, where the first access request is information based on the OCF protocol , then the virtual OCF server 310 in the gateway device 300 receives the first access request, and the bridging function module 320 converts the first access request into a second access request, and the second access request is based on the Zigbee protocol/BLE mesh protocol Then, the virtual Zigbee client/virtual BLE mesh client 330 in the gateway device 300 sends a second access request to the Zigbee device/BLE mesh device 302 to complete the OCF client 301 to the Zigbee device/BLE mesh device 302. access.

In addition, the gateway device 300 can also be called a bridge platform, which is used to realize the interaction function between the OCF client 301 and the Zigbee device/BLE mesh device 302.

Please refer to FIG. 7 , which shows a flowchart of a resource mapping method provided by an embodiment of the present application, and the method can be applied to a gateway device. The method may include the following steps (710-730):

Step 710: Create a first OCF device corresponding to the first physical device, where the first physical device is a device based on the target communication protocol, and the first OCF device is a virtual OCF device mapped by the first physical device.

Optionally, the target communication protocol can be a certain wireless communication protocol, such as Zigbee protocol or BLE mesh protocol.

Step 720: Create a first OCF resource based on the mapping relationship between the first OCF device and the first physical device, and the first OCF resource and the first object in the first physical device have a mapping relationship.

In this embodiment of the present application, there is a mapping relationship between the OCF resource and the object in the physical device based on the target communication protocol. Optionally, the mapping relationship may be a one-to-one mapping relationship, that is, one OCF resource corresponds to one object, and different OCF resources correspond to different objects.

Of course, in some other examples, the mapping relationship may also be a one-to-many mapping relationship, that is, one OCF resource corresponds to multiple objects, and multiple different objects may correspond to the same OCF resource; or, the mapping relationship also It may be a many-to-one mapping relationship, that is, one object corresponds to multiple OCF resources, which is not limited in this embodiment of the present application.

Step 730: Generate and store a resource address of the first OCF resource, where the resource address of the first OCF resource is used to determine a first object that has a mapping relationship with the first OCF resource.

For example, if the operation request received by the gateway device includes the resource address of the first OCF resource, the gateway device may determine that the first object corresponding to the first OCF resource needs to perform a relevant operation. The resource address of the first OCF resource is used to uniquely identify the first OCF resource, and different OCF resources have different resource addresses. For example, the resource address can be a URL (Uniform Resource Locator).

Optionally, the gateway device may generate the resource address of the first OCF resource according to the identification information of the first object. Of course, in other examples, the gateway device may also generate the resource address of the first OCF resource in other manners, as long as the resource address can play a role of uniquely identifying the OCF, which is not limited in this embodiment of the present application.

In an example, when the target communication protocol is the Zigbee protocol, that is, when the first physical device is the first Zigbee device, the first OCF resource and the first service cluster in the first physical device have a mapping relationship. Correspondingly, the resource address of the first OCF resource includes: identification information of the endpoint to which the first service cluster belongs, and identification information of the first service cluster. For example, assuming that the first service cluster is Cluster 6 (that is, the cluster with id 6) under Endpoint 1 (that is, the endpoint whose id is 1) under the first Zigbee device, the resource address of the first OCF resource may include the address of Endpoint 1. Identification information and identification information of Cluster 6. Among them, the identification information of the endpoint is used to uniquely identify the endpoint. Different endpoints under the same Zigbee device have different identification information; the identification information of the service cluster is used to uniquely identify the service cluster. Different service clusters under the command line have different identification information. Exemplarily, the resource address of the first OCF resource may be represented as "/ep/1/cluster/6", where ep represents the endpoint, 1 represents the id value of the endpoint, cluster represents the service cluster, and 6 represents the id value of the service cluster.

Optionally, the resource address of the first OCF resource further includes: identification information of the Zigbee protocol. Exemplarily, the resource address of the first OCF resource can be represented as "/eco/zigbee3.0/ep/1/cluster/6", eco represents the communication protocol, and zigbee3.0 represents the identification information of the communication protocol (that is, the representative is zigbee3. .0 protocol), ep represents the endpoint, 1 represents the id value of the endpoint, cluster represents the service cluster, and 6 represents the id value of the service cluster.

In another example, when the target communication protocol is the BLE Mesh protocol, that is, when the first physical device is the first BLE mesh device, the first OCF resource and the first service model in the first physical device have Mapping relations. Correspondingly, the resource address of the first OCF resource includes: identification information of the element to which the first service model belongs, and identification information of the first service model. For example, assuming that the first service model is Model 3 (that is, the model with id 3) under Element 2 (that is, the element with id 2) under the first BLE mesh device, the resource address of the first OCF resource can include Element2's Identification information and the identification information of Model 3. Among them, the identification information of the element is used to uniquely identify the element. Different elements under the same BLE mesh device have different identification information; the identification information of the service model is used to uniquely identify the service model. Different service models under the element have different identification information. Exemplarily, the resource address of the first OCF resource may be represented as "/ele/2/model/3", where ele represents an element, 2 represents an id value of the element, model represents a service model, and 3 represents an id value of the service model.

Optionally, the resource address of the first OCF resource further includes: identification information of the BLE Mesh protocol. Exemplarily, the resource address of the first OCF resource may be represented as "/eco/blemesh/ele/2/model/3", where eco represents a communication protocol, and blemesh represents identification information of the communication protocol (that is, it represents the BLE mesh protocol), ele represents the element, 2 represents the id value of the element, model represents the service model, and 3 represents the id value of the service model.

In an exemplary embodiment, as shown in FIG. 8 , the above step 730 further includes the following steps (740-760):

Step 740: Receive a first access request sent by the OCF client, where the first access request is a request by the OCF client to access the first OCF resource, and the first access request includes the resource address of the first OCF resource.

Optionally, the first access request further includes operation type indication information, which is used to indicate the operation performed on the first OCF resource. Exemplarily, the operations that can be performed on the first OCF resource include, but are not limited to, at least one of the following: read, update, delete, subscribe, and so on.

Step 750: Map the resource address of the first OCF resource to the identification information of the first object.

After receiving the first access request, the gateway device parses the first access request and obtains the resource address of the first OCF resource, thus knowing that the OCF client wants to access the first OCF resource. Optionally, the operation type indication information carried in the request is also read, so as to know the operation that needs to be performed on the first OCF resource. Then, the gateway device maps the resource address of the first OCF resource to the identification information of the first object, and generates and sends a second access request to the first physical device.

Step 760: Send a second access request to the first physical device, where the second access request is a request by the gateway device to access the first object, and the second access request includes identification information of the first object.

Optionally, the first access request further includes operation type indication information, which is used to indicate the operation performed on the first object. Exemplarily, the operations that can be performed on the first object include, but are not limited to, at least one of the following: read, update, delete, subscribe, and so on.

To sum up, in the technical solutions provided by the embodiments of the present application, a mapping relationship between the first OCF resource and the first object in the first physical device is established through the gateway device, and the resource address of the first OCF resource is generated and stored, This is used to determine the first object that has a mapping relationship with the first OCF resource, and specifies the relationship between the OCF resource address and the object under the target communication protocol, thereby enhancing the ability of the OCF protocol to interconnect with other standard protocols. .

For example, the relationship between the OCF resource address and the Zigbee cluster (Cluster) and the BLE mesh model (Model) is specified, thereby enhancing the interconnectivity between the OCF protocol and the Zigbee protocol/BLE mesh protocol.

It should be noted that, in this embodiment of the present application, only relationship mapping is performed for functional resource URLs, and no such mapping processing is performed for OCF specific resource type URLs (specific resource URLs, such as "/oic/res", "/oic" /d", "/oic/p", etc.

Please refer to FIG. 9 , which shows a flowchart of a resource mapping method provided by another embodiment of the present application, and the method can be applied to the implementation environment shown in FIG. 5 . In this embodiment, the relationship between the OCF resource address and the Zigbee cluster (Cluster) is specified. The method may include the following steps (901-917):

Step 901, the virtual Zigbee client discovers the first Zigbee device.

Step 902, the virtual Zigbee client establishes a connection with the first Zigbee device.

Step 903, the virtual Zigbee client sends a mapping relationship establishment request to the bridging function module, where the mapping relationship establishment request is used to request the establishment of a mapping relationship between the first Zigbee device and the first OCF device, where the first OCF device is the first Zigbee device Device-mapped virtual OCF device.

Step 904, the bridging function module sets the mapping relationship between the OCF resource and the service cluster of the first Zigbee device.

The bridge function module sets the corresponding OCF resource URL according to the data model structure characteristics of the Zigbee protocol. For example, for a Zigbee 3.0 device, when a Cluster (id value 6) under the device Endpoint (id value 1) establishes a mapping relationship with an OCF resource, the OCF resource URL can be set to /ep/1/cluster/6 .

Step 905, the bridging function module sends a virtual OCF device creation request to the virtual OCF server, where the virtual OCF device creation request is used to request to create a virtual OCF device (ie, the first OCF device) mapped with the first Zigbee device.

Step 906, the virtual OCF server creates a first OCF device, and creates an OCF resource based on the OCF resource address.

Step 907: The OCF client sends a device resource acquisition request to the virtual OCF server, where the device resource acquisition request is used to request to acquire related information of the OCF resource created by the virtual OCF server.

For example, obtain information such as resource addresses and resource access policies of each OCF resource created by the virtual OCF server.

Step 908, the virtual OCF server sends the related information of the OCF resource to the OCF client.

Step 909, the OCF client sends a first access request to the virtual OCF server, where the first access request includes the resource address of the first OCF resource to be accessed.

For example, the first access request includes /ep/1/cluster/6.

Step 910, the virtual OCF server sends a resource address resolution request to the bridging function module, the resource address resolution request is used for requesting to resolve the resource address, and the resource address resolution request includes the resource address to be resolved (that is, the above-mentioned first OCF resource). resource address).

Step 911, the bridging function module determines the identification information of the service cluster corresponding to the resource address to be resolved, for example, the first OCF resource corresponds to the first service cluster.

The bridging function module determines which Cluster under which Endpoint of the Zigbee 3.0 device is to be accessed according to the resource address to be resolved. For example, if the first access request includes /ep/1/cluster/6, it is determined that the one to be accessed is Cluster 6 under Endpoint 1 under the Zigbee 3.0 device.

Step 912, the bridging function module sends a request for accessing the first service cluster to the virtual Zigbee client, where the request may include identification information of the first service cluster.

Step 913: The virtual Zigbee client sends a second access request to the first Zigbee device, where the second access request includes identification information of the first service cluster to be accessed.

Step 914, the first Zigbee device sends the first access result to the virtual Zigbee client.

Step 915, the virtual Zigbee client sends the first access result to the bridging function module.

Step 916, the bridging function module sends a second access result to the virtual OCF server, where the second access result is an access result conforming to the OCF protocol specification generated by converting the first access result based on the Zigbee protocol.

Step 917, the virtual OCF server sends the second access result to the OCF client.

Please refer to FIG. 10 , which shows a flowchart of a resource mapping method provided by another embodiment of the present application, and the method can be applied to the implementation environment shown in FIG. 5 . In this embodiment, the relationship between the OCF resource address and the BLE mesh model (Model) is specified. The method may include the following steps (1001-1017):

Step 1001, the virtual BLE mesh client discovers the first BLE mesh device.

Step 1002, the virtual BLE mesh client establishes a connection with the first BLE mesh device.

Step 1003, the virtual BLE mesh client sends a mapping relationship establishment request to the bridging function module, and the mapping relationship establishment request is used to request the establishment of a mapping relationship between the first BLE mesh device and the first OCF device, and the first OCF device is the first OCF device. A virtual OCF device mapped by a BLE mesh device.

Step 1004, the bridging function module sets the mapping relationship between the OCF resource and the service model of the first BLE mesh device.

The bridge function module sets the corresponding OCF resource URL according to the data model structure characteristics of the BLE mesh protocol. For example, for a BLE mesh device, when the Model (id value is 3) under the device Element (id value is 2) establishes a mapping relationship with the OCF resource, the OCF resource URL can be set to /ele/2/model/3 .

Step 1005, the bridging function module sends a virtual OCF device creation request to the virtual OCF server, where the virtual OCF device creation request is used to request the creation of a virtual OCF device (that is, the first OCF device) mapped with the first BLE mesh device.

Step 1006, the virtual OCF server creates a first OCF device, and creates an OCF resource based on the OCF resource address.

Step 1007, the OCF client sends a device resource acquisition request to the virtual OCF server, where the device resource acquisition request is used to request to acquire related information of the OCF resource created by the virtual OCF server.

Step 1008, the virtual OCF server sends the relevant information of the OCF resource to the OCF client.

Step 1009, the OCF client sends a first access request to the virtual OCF server, where the first access request includes the resource address of the first OCF resource to be accessed.

For example, the first access request includes /ele/2/model/3.

Step 1010, the virtual OCF server sends a resource address resolution request to the bridging function module, the resource address resolution request is used to request to resolve the resource address, and the resource address resolution request includes the resource address to be resolved (that is, the above-mentioned first OCF resource). resource address).

Step 1011, the bridging function module determines the identification information of the service model corresponding to the resource address to be resolved, for example, the first OCF resource corresponds to the first service model.

The bridge function module determines which Model under which Element of the BLE mesh device is to be accessed according to the resource address to be resolved. For example, if the first access request includes /ele/2/model/3, it is determined that the Model 3 under Element 2 under the BLE mesh device is to be accessed.

Step 1012, the bridging function module sends a request for accessing the first service model to the virtual BLE mesh client, where the request may include identification information of the first service model.

Step 1013, the virtual BLE mesh client sends a second access request to the first BLE mesh device, where the second access request includes identification information of the first service model to be accessed.

Step 1014, the first BLE mesh device sends the first access result to the virtual BLE mesh client.

Step 1015, the virtual BLE mesh client sends the first access result to the bridge function module.

Step 1016, the bridging function module sends a second access result to the virtual OCF server, where the second access result is an access result conforming to the OCF protocol specification generated after converting the first access result based on the BLE mesh protocol.

Step 1017, the virtual OCF server sends the second access result to the OCF client.

In the following, the encoding scheme of the OCF resource address is introduced through an exemplary embodiment.

In one example, the resource address of the first OCF resource includes: a first padding bit, a second padding bit, a third padding bit, and a fourth padding bit; wherein the first padding bit is used to pad the representation information of the object; the second padding bit The padding bit is used to pad the identification information of the first object; the third padding bit is used to pad the representation information of the service type to which the object belongs; and the fourth padding bit is used to pad the identification information of the service type to which the first object belongs.

For example, for the mapping from the OCF protocol to the Zigbee protocol, the first padding bit is used to pad the representation information of the service cluster; the second padding bit is used to pad the identification information of the service cluster; the third padding bit is used to pad the endpoint to which the service cluster belongs ; the fourth padding bit is used to fill in the identification information of the endpoint to which the service cluster belongs.

For another example, for the mapping from the OCF protocol to the BLE mesh protocol, the first padding bit is used to pad the representation information of the service model; the second padding bit is used to pad the identification information of the service model; the third padding bit is used to pad the service model Representation information of the element to which it belongs; the fourth padding bit is used to fill the identification information of the element to which the service model belongs.

Optionally, in the first padding bit, the second padding bit, the third padding bit, and the fourth padding bit, any two adjacent padding bits have a separator, and the separator is used to distinguish different padding bits. effect. For example, the OCF resource URL can be expressed as "/app/x2/res/x3", from left to right: app corresponds to the third padding bit, x2 corresponds to the fourth padding bit, res corresponds to the first padding bit, and x3 corresponds to The second padding bit, "/" indicates the delimiter. For Zigbee 3.0 devices, for example, app=ep(endpoint, endpoint), res=cluster(cluster), x2=id value of endpoint, x3=id value of cluster. For BLE Mesh devices, for example, app=ele(element, element), res=model(model), x2=id value of element, x3=id value of model.

Optionally, the resource address of the first OCF resource further includes: a fifth padding bit and a sixth padding bit, the fifth padding bit is used to pad the representation information of the communication protocol, and the sixth padding bit is used to pad the identification information of the communication protocol. Optionally, in the first padding bit, the second padding bit, the third padding bit, the fourth padding bit, the fifth padding bit and the sixth padding bit, any two adjacent padding bits have a separator between them. For example, the OCF resource URL can be expressed as "/eco/x1/app/x2/res/x3", from left to right: eco corresponds to the fifth padding bit, x1 corresponds to the sixth padding bit, and app corresponds to the third padding bit , x2 corresponds to the fourth padding bit, res corresponds to the first padding bit, and x3 corresponds to the second padding bit, and "/" represents a separator. For Zigbee 3.0 devices, for example, x1=zigbee3.0, app=ep(endpoint, endpoint), res=cluster (cluster), x2=id value of endpoint, x3=id value of cluster. For BLE Mesh devices, for example, x1=blemesh, app=ele(element, element), res=model(model), x2=id value of element, x3=id value of model.

In another example, the resource address of the first OCF resource includes: a first padding bit and a second padding bit; wherein the first padding bit is used to pad the identification information of the first object; the second padding bit is used to pad the first padding bit Identification information of the service type to which the object belongs.

For example, for the mapping from the OCF protocol to the Zigbee protocol, the first padding bit is used to pad the identification information of the service cluster; the second padding bit is used to pad the identification information of the endpoint to which the service cluster belongs.

For another example, for the mapping from the OCF protocol to the BLE mesh protocol, the first padding bit is used to fill in the identification information of the service model; the second padding bit is used to fill in the identification information of the element to which the service model belongs.

Optionally, there is a separator between the first padding bit and the second padding bit, and the separator is used to distinguish different padding bits. For example, the OCF resource URL may be expressed as "/x2/x3", from left to right: x2 corresponds to the second padding bit, x3 corresponds to the first padding bit, and "/" represents a separator. For Zigbee 3.0 devices, for example, x2=id value of endpoint, x3=id value of cluster. Exemplarily, the OCF resource URL is "/1/6", indicating that the id value of the endpoint is 1, and the id value of the cluster is 6. For BLE Mesh devices, for example, x2=id value of element, x3=id value of model. Exemplarily, the OCF resource URL is "/2/3", indicating that the id value of the element is 2, and the id value of the model is 3.

Optionally, there is no separator between the first padding bit and the second padding bit, and the length of the first padding bit and the length of the second padding bit are predefined. For example, the OCF resource URL may be expressed as "/x2x3", in order from left to right: x2 corresponds to the second padding bit, and x3 corresponds to the first padding bit. For Zigbee 3.0 devices, for example, x2=id value of endpoint, x3=id value of cluster. For BLE Mesh devices, for example, x2=id value of element, x3=id value of model. In addition, since there is no separator between the first padding bit and the second padding bit, in order to distinguish the padding data in the first padding bit and the second padding bit, the length of the first padding bit and the length of the second padding bit The length is predefined, for example, the length of the first padding bit is 32 bits, and the length of the second padding bit is also 32 bits. Of course, the length of the first padding bit and the length of the second padding bit may be pre-defined in combination with the actual situation, and the lengths of the two may be the same or different, which are not limited in this embodiment of the present application.

Optionally, the resource address of the first OCF resource further includes: a third padding bit, which is used to pad the identification information of the communication protocol. There may or may not be a separator between the third padding bit and the first and second padding bits. If there is no separator, the length of the third padding bit may also be predefined. Taking the separator between the third padding bit and the first and second padding bits as an example, the OCF resource URL can be expressed as "/x1/x2x3", from left to right: x1 corresponds to the third padding bit, and x2 corresponds to the first padding bit. Two padding bits, x3 corresponds to the first padding bit. Taking the third padding bit and the first and second padding bits without a separator as an example, the OCF resource URL can be expressed as "/x1x2x3", from left to right: x1 corresponds to the third padding bit, x2 corresponds to the second padding bit Padding bit, x3 corresponds to the first padding bit.

Compared with the method provided in the previous example, the method provided in this example helps to shorten the length of the OCF resource address, thereby saving the storage overhead and transmission overhead of the OCF resource address.

The following are apparatus embodiments of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

Please refer to FIG. 11 , which shows a block diagram of a resource mapping apparatus provided by an embodiment of the present application. The apparatus has the function of implementing the above-mentioned method example on the gateway device side, and the function may be implemented by hardware or by executing corresponding software in hardware. The device may be the gateway device described above, or may be set in the gateway device. As shown in FIG. 11 , the apparatus 1100 may include: a device creation module 1110 , a resource creation module 1120 and an address generation module 1130 .

A device creation module 1110, configured to create a first OCF device corresponding to a first physical device, where the first physical device is a device based on a target communication protocol, and the first OCF device is a virtual device mapped by the first physical device OCF equipment;

A resource creation module 1120, configured to create a first OCF resource based on the mapping relationship between the first OCF device and the first physical device, the first OCF resource and the first in the first physical device Objects have a mapping relationship;

The address generation module 1130 is configured to generate and store a resource address of the first OCF resource, where the resource address of the first OCF resource is used to determine the first object that has a mapping relationship with the first OCF resource.

In an exemplary embodiment, when the target communication protocol is the BLE Mesh protocol, the first OCF resource and the first service model in the first physical device have a mapping relationship.

Optionally, the resource address of the first OCF resource includes:

Identification information of the element to which the first service model belongs, and identification information of the first service model.

Optionally, the resource address of the first OCF resource further includes:

The identification information of the BLE Mesh protocol.

In an exemplary embodiment, when the target communication protocol is the Zigbee protocol, the first OCF resource and the first service cluster in the first physical device have a mapping relationship.

Optionally, the resource address of the first OCF resource includes:

Identification information of the endpoint to which the first service cluster belongs, and identification information of the first service cluster.

Optionally, the resource address of the first OCF resource further includes:

The identification information of the Zigbee protocol.

In an exemplary embodiment, the apparatus 1110 further includes: a request receiving module, an address mapping module and a request sending module (not shown in FIG. 11 ).

A request receiving module, configured to receive a first access request sent by an OCF client, where the first access request is a request by the OCF client to access the first OCF resource, and the first access request includes all Describe the resource address of the first OCF resource.

The address mapping module is configured to map the resource address of the first OCF resource to the identification information of the first object.

A request sending module is configured to send a second access request to the first physical device, where the second access request is a request by the gateway device to access the first object, and the second access request includes all Describe the identification information of the first object.

In an exemplary embodiment, the resource address of the first OCF resource includes: a first padding bit, a second padding bit, a third padding bit, and a fourth padding bit; wherein,

The first padding bit is used to pad the representation information of the object;

The second filling bit is used to fill the identification information of the first object;

The third padding bit is used to fill in the representation information of the service type to which the object belongs;

The fourth padding bit is used to pad the identification information of the service type to which the first object belongs.

Optionally, in the first padding bit, the second padding bit, the third padding bit and the fourth padding bit, any two adjacent padding bits have a separator between them.

In an exemplary embodiment, the resource address of the first OCF resource includes: a first padding bit and a second padding bit; wherein,

The first filling bit is used to fill the identification information of the first object;

The second padding bit is used to pad the identification information of the service type to which the first object belongs.

Optionally, there is a separator between the first padding bits and the second padding bits.

Optionally, there is no separator between the first padding bit and the second padding bit, and the length of the first padding bit and the length of the second padding bit are predefined.

It should be noted that, when the device provided in the above embodiment realizes its functions, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions can be allocated to different functional modules according to actual needs. That is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.

Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

Please refer to FIG. 12 , which shows a schematic structural diagram of a gateway device 120 provided by an embodiment of the present application. The gateway device 120 may be used to implement the attribute subscription method of the Zigbee device on the gateway device side. The gateway device 120 may include: a processor 121 , a receiver 122 , a transmitter 123 , a memory 124 and a bus 125 .

The processor 121 includes one or more processing cores, and the processor 121 executes various functional applications and information processing by running software programs and modules.

The receiver 122 and the transmitter 123 may be implemented as a communication component, which may be a communication chip.

The memory 124 is connected to the processor 121 through the bus 125 .

The memory 124 can be used to store a computer program, and the processor 121 is used to execute the computer program, so as to implement each step performed by the gateway device in the above method embodiments.

Additionally, memory 124 may be implemented by any type or combination of volatile or non-volatile storage devices including, but not limited to, magnetic or optical disks, electrically erasable programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Static Anytime Access Memory (SRAM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Programmable Read Only Memory (PROM) .

In an exemplary embodiment, the gateway device includes a processor, a memory, and a transceiver (the transceiver may include a receiver for receiving information and a transmitter for transmitting information);

Optionally, the resource address of the first OCF resource includes:

Optionally, the resource address of the first OCF resource further includes:

The identification information of the BLE Mesh protocol.

Optionally, the resource address of the first OCF resource includes:

Optionally, the resource address of the first OCF resource further includes:

The identification information of the Zigbee protocol.

In an exemplary embodiment, the transceiver is configured to receive a first access request sent by an OCF client, where the first access request is a request by the OCF client to access the first OCF resource, so The first access request includes the resource address of the first OCF resource;

The processor is further configured to map the resource address of the first OCF resource to the identification information of the first object;

The transceiver is further configured to send a second access request to the first physical device, where the second access request is a request by the gateway device to access the first object, and the second access request includes Including identification information of the first object.

An exemplary embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a gateway device, so as to realize the resources on the side of the gateway device. mapping method.

An exemplary embodiment of the present application further provides a chip, where the chip includes a programmable logic circuit and/or program instructions, and when the chip runs on a gateway device, is used to implement the above-mentioned resource mapping method on the gateway device side .

An exemplary embodiment of the present application further provides a computer program product, which, when the computer program product runs on the gateway device, enables the gateway device to execute the foregoing method for resource mapping on the gateway device side.

Those skilled in the art should realize that, in one or more of the above examples, the functions described in the embodiments of the present application may be implemented by hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

The above are only exemplary embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the protection of the present application. within the range.

Claims

A resource mapping method, characterized in that, applied to a gateway device, the method comprising:

creating a first OCF device corresponding to a first physical device, where the first physical device is a device based on a target communication protocol, and the first OCF device is a virtual OCF device mapped by the first physical device;

creating a first OCF resource based on the mapping relationship between the first OCF device and the first physical device, where the first OCF resource has a mapping relationship with the first object in the first physical device;

A resource address of the first OCF resource is generated and stored, where the resource address of the first OCF resource is used to determine the first object that has a mapping relationship with the first OCF resource.
The method according to claim 1, wherein, when the target communication protocol is a BLE Mesh protocol, the first OCF resource and the first service model in the first physical device have a mapping relationship.
The method according to claim 2, wherein the resource address of the first OCF resource comprises:

Identification information of the element to which the first service model belongs, and identification information of the first service model.
The method according to claim 3, wherein the resource address of the first OCF resource further comprises:

The identification information of the BLE Mesh protocol.
The method according to claim 1, wherein when the target communication protocol is the Zigbee protocol, the first OCF resource and the first service cluster in the first physical device have a mapping relationship.
The method according to claim 5, wherein the resource address of the first OCF resource comprises:

Identification information of the endpoint to which the first service cluster belongs, and identification information of the first service cluster.
The method according to claim 6, wherein the resource address of the first OCF resource further comprises:

The identification information of the Zigbee protocol.
The method according to any one of claims 1 to 7, wherein the method further comprises:

Receive a first access request sent by the OCF client, where the first access request is a request by the OCF client to access the first OCF resource, and the first access request includes the first access request of the first OCF resource. resource address;

mapping the resource address of the first OCF resource to the identification information of the first object;

Sending a second access request to the first physical device, where the second access request is a request by the gateway device to access the first object, and the second access request includes the identifier of the first object information.
The method according to any one of claims 1 to 8, wherein the resource address of the first OCF resource comprises: a first padding bit, a second padding bit, a third padding bit and a fourth padding bit; wherein ,

The first padding bit is used to pad the representation information of the object;

The second filling bit is used to fill the identification information of the first object;

The third padding bit is used to fill in the representation information of the service type to which the object belongs;

The fourth padding bit is used to pad the identification information of the service type to which the first object belongs.
The method according to claim 9, wherein among the first padding bits, the second padding bits, the third padding bits and the fourth padding bits, any two adjacent padding bits are There are separators between them.
The method according to any one of claims 1 to 8, wherein the resource address of the first OCF resource comprises: a first padding bit and a second padding bit; wherein,

The first filling bit is used to fill the identification information of the first object;

The second padding bit is used to pad the identification information of the service type to which the first object belongs.
The method of claim 11, wherein a separator is provided between the first padding bits and the second padding bits.
The method according to claim 11, wherein there is no separator between the first padding bit and the second padding bit, and the length of the first padding bit is the same as the length of the second padding bit. The length is predefined.
A resource mapping apparatus, characterized in that the apparatus comprises:

A device creation module, configured to create a first OCF device corresponding to a first physical device, where the first physical device is a device based on a target communication protocol, and the first OCF device is a virtual OCF mapped by the first physical device equipment;

A resource creation module, configured to create a first OCF resource based on the mapping relationship between the first OCF device and the first physical device, the first OCF resource and the first object in the first physical device has a mapping relationship;

An address generation module, configured to generate and store a resource address of the first OCF resource, where the resource address of the first OCF resource is used to determine the first object that has a mapping relationship with the first OCF resource.
The apparatus according to claim 14, wherein when the target communication protocol is a BLE Mesh protocol, the first OCF resource and the first service model in the first physical device have a mapping relationship.
The apparatus according to claim 15, wherein the resource address of the first OCF resource comprises:

Identification information of the element to which the first service model belongs, and identification information of the first service model.
The apparatus according to claim 16, wherein the resource address of the first OCF resource further comprises:

The identification information of the BLE Mesh protocol.
The apparatus according to claim 14, wherein when the target communication protocol is a Zigbee protocol, the first OCF resource and the first service cluster in the first physical device have a mapping relationship.
The apparatus according to claim 18, wherein the resource address of the first OCF resource comprises:

Identification information of the endpoint to which the first service cluster belongs, and identification information of the first service cluster.
The apparatus according to claim 19, wherein the resource address of the first OCF resource further comprises:

The identification information of the Zigbee protocol.
The device according to any one of claims 14 to 20, wherein the device further comprises:

A request receiving module, configured to receive a first access request sent by an OCF client, where the first access request is a request by the OCF client to access the first OCF resource, and the first access request includes all Describe the resource address of the first OCF resource;

An address mapping module, configured to map the resource address of the first OCF resource to the identification information of the first object;

A request sending module is configured to send a second access request to the first physical device, where the second access request is a request by the gateway device to access the first object, and the second access request includes all Describe the identification information of the first object.
The apparatus according to any one of claims 14 to 21, wherein the resource address of the first OCF resource comprises: a first padding bit, a second padding bit, a third padding bit, and a fourth padding bit; wherein ,

The first padding bit is used to pad the representation information of the object;

The second filling bit is used to fill the identification information of the first object;

The third padding bit is used to fill in the representation information of the service type to which the object belongs;

The fourth padding bit is used to pad the identification information of the service type to which the first object belongs.
The device according to claim 22, wherein among the first padding bit, the second padding bit, the third padding bit and the fourth padding bit, any two adjacent padding bits are between any two adjacent padding bits. There are separators between them.
The apparatus according to any one of claims 14 to 21, wherein the resource address of the first OCF resource comprises: a first padding bit and a second padding bit; wherein,

The first filling bit is used to fill the identification information of the first object;

The second padding bit is used to pad the identification information of the service type to which the first object belongs.
The apparatus of claim 24, wherein a separator is provided between the first padding bits and the second padding bits.
The device according to claim 24, wherein there is no separator between the first padding bit and the second padding bit, and the length of the first padding bit is the same as the length of the second padding bit. The length is predefined.
A gateway device, characterized in that the gateway device includes a processor, a memory and a transceiver;

The processor is configured to create a first OCF device corresponding to a first physical device, where the first physical device is a device based on a target communication protocol, and the first OCF device is a virtual device mapped by the first physical device. OCF equipment;

The processor is further configured to create a first OCF resource based on the mapping relationship between the first OCF device and the first physical device, the first OCF resource and the first OCF resource in the first physical device. An object has a mapping relationship;

The processor is further configured to generate and store a resource address of the first OCF resource, where the resource address of the first OCF resource is used to determine the first object that has a mapping relationship with the first OCF resource.
A computer-readable storage medium, wherein a computer program is stored in the storage medium, and the computer program is used to be executed by a processor to implement the resource mapping method according to any one of claims 1 to 13 .