CN113439427B

CN113439427B - Resource release method and device

Info

Publication number: CN113439427B
Application number: CN201980092309.9A
Authority: CN
Inventors: 张军
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-07-24
Filing date: 2019-07-24
Publication date: 2023-10-27
Anticipated expiration: 2039-07-24
Also published as: WO2021012236A1; CN113439427A

Abstract

The embodiment of the application discloses a resource release method and equipment, wherein the method comprises the following steps: the cloud limited device establishes connection with a cloud proxy device; the cloud limited device transmits information to the cloud proxy device based on the connection, wherein the information is used for the cloud proxy device to issue resources to the cloud device.

Description

Resource release method and device

Technical Field

The application relates to the technical field of communication of the Internet of things, in particular to a resource release method and equipment.

Background

The open connection foundation (OCF, open Connectivity Foundation) is an emerging internet of things application layer technical standard organization, and the OCF formulates a Restful service framework for implementing interconnection between internet of things devices. OCF equipment and OCF cloud equipment can be included in the OCF deployment architecture; the OCF cloud device receives the OCF device release resource. In this case, the OCF device that issues the resource to the OCF cloud device needs to have the capability of connecting to the cloud, and the OCF device and the OCF cloud device implement resource issue and remote communication by establishing and maintaining a long connection of a secure transport layer protocol (TLS, transport Layer Security).

However, for OCF devices that do not have an OCF cloud device, resource release cannot be performed because the OCF cloud device cannot be connected. There is currently no effective solution to this problem.

Disclosure of Invention

The embodiment of the application provides a resource release method and equipment.

In a first aspect, a resource publishing method provided by an embodiment of the present application includes: the cloud limited device establishes connection with a cloud proxy device; the cloud limited device transmits information to the cloud proxy device based on the connection, wherein the information is used for the cloud proxy device to issue resources to the cloud device.

In a second aspect, a resource publishing method provided by an embodiment of the present application includes: the cloud proxy device establishes connection with the cloud limited device; the cloud proxy device transmits information to the cloud limited device based on the connection and issues resources of the cloud limited device to the cloud device based on the information.

In a third aspect, a resource publishing method provided by an embodiment of the present application includes: the cloud end equipment obtains resources issued by the cloud end proxy equipment; the resource is a resource of the cloud limited device, which is obtained by the cloud proxy device based on connection with the cloud limited device; and the cloud device publishes the resource.

In a fourth aspect, a cloud limited device provided by an embodiment of the present application includes: a first connection establishment unit and a first transmission unit; wherein, the liquid crystal display device comprises a liquid crystal display device,

The first connection establishing unit is configured to establish connection with the cloud proxy equipment;

the first transmission unit is configured to transmit information based on the connection and the cloud proxy device, wherein the information is used for the cloud proxy device to issue resources to the cloud device.

In a fifth aspect, a cloud proxy device provided by an embodiment of the present application includes: the second connection establishment unit, the second transmission unit and the third transmission unit; wherein, the liquid crystal display device comprises a liquid crystal display device,

the second connection establishing unit is configured to establish connection with the cloud limited equipment;

the second transmission unit is configured to transmit information with the cloud limited device based on the connection;

the third transmission unit is configured to issue the resources of the cloud limited device to the cloud device based on the information transmitted by the second transmission unit.

In a sixth aspect, the cloud device provided by the embodiment of the present application includes a fourth transmission unit and a publishing unit; wherein, the liquid crystal display device comprises a liquid crystal display device,

the fourth transmission unit is configured to obtain resources issued by the cloud agent equipment; the resource is a resource of the cloud limited device, which is obtained by the cloud proxy device based on connection with the cloud limited device;

The publishing unit is configured to publish the resource.

In a seventh aspect, an apparatus provided by an embodiment of the present application includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory to execute the resource release method of the first aspect, the second aspect or the third aspect.

The chip provided by the embodiment of the application is used for realizing the resource release method of the terminal.

Specifically, the chip includes: and a processor for calling and running a computer program from a memory so that a device mounted with the chip performs the resource issuing method of the first aspect, the second aspect or the third aspect described above.

The embodiment of the application provides a computer readable storage medium for storing a computer program, where the computer program makes a computer execute the resource publishing method of the first aspect, the second aspect or the third aspect.

An embodiment of the present application provides a computer program product, including computer program instructions, where the computer program instructions cause a computer to execute the resource release method of the first aspect, the second aspect or the third aspect.

The computer program provided by the embodiment of the application, when running on a computer, causes the computer to execute the resource release method of the first aspect, the second aspect or the third aspect.

Through the technical scheme, the cloud terminal proxy equipment and the cloud terminal limited equipment are connected, so that the cloud terminal limited equipment which cannot interact with the cloud terminal equipment can release resources through the cloud terminal proxy equipment, and the problem that the cloud terminal limited equipment cannot release resources to the cloud terminal equipment is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

FIGS. 1a and 1b are schematic diagrams of an OCF system architecture provided in accordance with embodiments of the present application;

FIG. 2 is a schematic flow chart of a resource publishing method according to an embodiment of the present application;

FIG. 3 is a flowchart illustrating a specific example of a resource publishing method according to an embodiment of the present application;

fig. 4 is a second flowchart of a specific example of a resource publishing method according to an embodiment of the present application;

fig. 5 is a flowchart illustrating a specific example of a resource publishing method according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a cloud limited device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a cloud proxy device according to an embodiment of the present application;

Fig. 8 is a schematic diagram of a structural composition of a cloud device according to an embodiment of the present application;

fig. 9 is a schematic diagram II of the structural composition of a cloud device according to an embodiment of the present application;

fig. 10 is a schematic diagram III of the structural composition of a cloud device according to an embodiment of the present application;

fig. 11 is a schematic diagram of a structural composition of a cloud device according to an embodiment of the present application;

FIG. 12 is a schematic block diagram of an apparatus according to an embodiment of the present application;

fig. 13 is a schematic structural view of a chip of an embodiment of the present application.

Detailed Description

The following description of the technical solutions according to the embodiments of the present application will be given with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The technical scheme of the embodiment of the application can be applied to an OCF system, and the OCF establishes a Restful service frame for realizing interconnection and interworking between the Internet of things equipment, and in the OCF Restful service frame, information such as the functional service and state data of the Internet of things equipment and the Internet of things equipment can be expressed through resources; the state data may be environmental state data obtained by the internet of things device. FIGS. 1a and 1b are schematic diagrams of an OCF system architecture provided in accordance with embodiments of the present application; as shown in fig. 1a, an entity that provides a resource may be referred to as an OCF server (hereinafter referred to as a server), and an entity that accesses a resource may be referred to as an OCF client (hereinafter referred to as a client). For example, the control terminal that obtains the indoor environment state data may be a client, the sensor device that monitors the indoor environment state data may be a server, and the business interaction between the client and the server is implemented by creating, reading, updating, deleting or notifying the resource operation methods.

The interaction between the client and the server may refer to fig. 1a, where the client 11 sends a request to the server 12, where the request is used to operate a resource on the server 12; the server 12 executes the resource operation corresponding to the request, and returns a response to the client 11, where the response carries the representation of the resource.

As an embodiment, the client sends an update (POST) resource request to the server, and operates on a resource on the server, where the object of the update resource request operation may be, for example, a resource uniform resource identifier (URI, uniform Resource Identifier). For example, if there is an ambient temperature resource on the server, the resource URI may be "/environmentTemperature". And the server side returns an updated resource response to the client side, wherein the updated resource response carries the expression of the resource.

Wherein the representation of the resource may include at least one of: resource URI, resource type, resource interface and functional attribute of resource, etc., specifically defined as follows:

resource URI: the resource expression is denoted by 'href', which represents the address of the server resource, and the value of 'href' is a specific resource URI; the client accesses the resource of the server through the resource URI;

Resource type: in the resource expression, the "rt" is used to represent the type of the resource, for example, the resource type "rt" is "oic.r.temperature", and the temperature resource type is represented;

resource interface: denoted by "if" in the resource expression, representing a view of the resource and a response to the support of the resource, e.g. the resource interface "if is" oic.if. A ", representing the controller interface;

resource attributes: the attribute information describing the resource in the resource expression, for example, the attribute information of the resource is "targetTemperature", which represents the target temperature attribute of the temperature resource, and for example, the attribute information of the resource is "currentTemperature", which represents the current temperature attribute of the temperature resource, and for example, the attribute information of the resource is "temp temperature range", which represents the temperature range attribute of the temperature resource.

The OCF defines resource discovery resources "/oic/res" that all OCF devices must support for OCF devices and discovery of resources, the resource discovery resources providing the function of device resource discovery, the URI of the resource discovery resources being fixed to "/oic/res".

In order to represent the association relationship between the resources, the OCF defines resource Links (namely, resource Links), and the server can provide the own resources in the form of resource Links, so that the client can find the resources of the server conveniently.

Wherein, the content of the resource link is as follows:

the content of the resource link includes:

■ Anchor: a URI of an owner resource containing a resource link is represented as a context URI;

■ href: target URI, i.e., URI of the target resource referenced in the resource link;

■ And rt: a resource type identifier representing a target resource;

■ if: an interface representing the support of the target resource;

■ eps: representing endpoints that have access to the target resource;

since the OCF standard protocol uses CoAP protocol to carry OCF messages at the transport layer, each server needs to have an endpoint, and each OCF device must associate at least one endpoint for sending and receiving OCF messages, and the client can access the target resource of the server through the endpoint. The end point of the target resource is represented by an 'eps' array in the parameter of the resource link, and the specific end point is represented by an 'ep', namely, the target resource can be accessed through the address of the 'ep' value in the 'eps' parameter. In the example of resource linking described above, a client may refer to an endpoint "shape" by the "ep" value in the "eps" parameter: // [2001: db8: b: : c2e5]:22222 "accesses" the target resource "/myLightSwitch" indicated by the href parameter.

When the OCF device and the control end are not in the same local network, as shown in fig. 1b, communication between the OCF device and the control end may be performed through the OCF cloud device. The OCF device may specifically be a server in fig. 1a, where the server is, for example, a sensor capable of collecting environmental data, and the control terminal may specifically be a client in fig. 1a, where the client is, for example, an electronic device such as a mobile phone, a computer, etc.; the electronic device may have installed therein a specific Application (APP) through which access to the resource is made.

Wherein, the OCF cloud device may include:

cloud interface: the method comprises the steps of taking charge of access management of OCF equipment and message routing of OCF equipment remote communication;

the authorization server: the method comprises the steps of being in charge of registering OCF equipment and verifying an access token of the OCF equipment;

resource catalogue: and the OCF client can acquire the resource information of the target device by searching the resource catalog.

In order to support resource release and resource discovery, the OCF cloud device needs to implement resource directory resources. The URI of the resource directory resource is "/oic/rd" and the resource type is "oic.wk.rd". The issuing device (namely the OCF device for issuing the resource link) issues the resource to the "/oic/rd" of the OCF cloud device, the issued content is the resource link of the OCF device, and after the resource directory service of the OCF cloud device receives the resource issuing request, the resource link of the OCF device is issued under the "/oic/res" resource of the OCF cloud device. The client can search the OCF cloud device to find out the resources of other OCF devices, the resource catalog represents the issuing device to provide the resource information of the OCF device, and after the client finds out the resource information of the OCF device, the client requests to interact with the corresponding OCF device through the OCF cloud device.

In the embodiment of the application, interaction can be performed between the OCF cloud device and the OCF device and between the OCF device and the configurator through various communication systems. Such as global system for mobile communications (Global System of Mobile communication, GSM) systems, code division multiple access (Code Division Multiple Access, CDMA) systems, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) systems, general packet radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX) communication systems, wireless local area network (Wireless Local Area Networks, WLAN), internet of things (Internet of Things System, ioT) or 5G systems, etc. The 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

In the embodiments of the present application, in the case where the OCF device cannot be connected to the OCF cloud device, the OCF device is referred to as a cloud limited device.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

The technical scheme of the embodiment of the application is mainly applied to the Internet of things system, and of course, the technical scheme of the embodiment of the application is not limited to the Internet of things system and can be applied to other types of communication systems.

The embodiment of the application provides a resource release method. FIG. 2 is a schematic flow chart of a resource publishing method according to an embodiment of the present application; as shown in fig. 2, the method includes:

step 201: the cloud limited device establishes connection with a cloud proxy device;

step 202: the cloud limited device transmits information to the cloud proxy device based on the connection, wherein the information is used for the cloud proxy device to issue resources to the cloud device;

step 203: the cloud limited device issues resources of the cloud limited device to a cloud device based on the information;

Step 204: the cloud end equipment obtains resources issued by the cloud end proxy equipment and publishes the resources; the resource is a resource of the cloud limited device obtained by the cloud proxy device based on connection with the cloud limited device.

In step 201 of this embodiment, the establishing a connection between the cloud limited device and the cloud proxy device includes: the cloud limited device obtains information of the cloud proxy device, and connection with the cloud proxy device is established based on the information. Correspondingly, the cloud proxy device establishes connection with the cloud limited device, and the cloud proxy device comprises: the cloud proxy device sends information of the cloud proxy device to the cloud limited device, and the information of the cloud proxy device is used for establishing connection between the cloud limited device and the cloud proxy device.

The obtaining information of the cloud proxy device in this embodiment may include the following ways:

as an embodiment, the obtaining, by the cloud limited device, information of a cloud proxy device includes: the cloud limited device receives configuration information sent by a configurator, wherein the configuration information comprises information of cloud proxy devices.

It can be appreciated that the cloud limited device may interact with the configurator although it may not be able to establish a connection with the cloud device. The cloud limited device can interact with the configurator in a local area network or short-distance communication mode, for example, so as to obtain configuration information sent by the configurator. Wherein the local area network is, for example, wireless fidelity (Wi-Fi); such as bluetooth communication, near field communication (Near Field Communication, NFC), etc.

As another embodiment, the obtaining, by the cloud limited device, information of a cloud proxy device includes: the cloud limited device sends a discovery request message in a broadcast or multicast mode; the discovery request message comprises a cloud proxy resource type; the cloud limited device receives a discovery response message; the discovery response message includes information of the cloud proxy device. Correspondingly, the cloud proxy device sends information of the cloud proxy device to the cloud limited device, including: the cloud proxy device receives a discovery request message sent by the cloud limited device in a broadcast or multicast mode; the discovery request message comprises a cloud proxy resource type; the cloud proxy device sends a discovery response message to the cloud limited device; the discovery response message includes information of the cloud proxy device.

It can be appreciated that the cloud limited device, although unable to establish a connection with the cloud device, may interact with the cloud proxy device. The cloud limited device can interact with the cloud proxy device in a local area network or short-distance communication mode, and the cloud limited device can send a discovery request message in a unicast, broadcast or multicast mode; the cloud proxy equipment in the same local area network or the cloud proxy equipment with the communication distance within the preset distance range can receive the discovery request message, and send a discovery response message to the cloud limited equipment after determining the cloud proxy resource type in the discovery request message. Wherein the local area network is, for example, wi-Fi; such as bluetooth communication, etc.

The information of the cloud agent equipment comprises at least one of the following: cloud agent resource identification of the cloud agent equipment and endpoint information of the cloud agent resources.

In an optional embodiment of the present application, the transmitting, by the cloud limited device, information with the cloud proxy device based on the connection includes: and the cloud limited device instructs the cloud proxy device to issue resources to the cloud device based on the connection. Correspondingly, the cloud proxy device transmits information based on the connection and the cloud limited device, and issues resources to the cloud device based on the information, and the cloud proxy device comprises: the cloud proxy device obtains an indication of the cloud limited device based on the connection, and issues resources to the cloud device based on the indication.

In this embodiment, the cloud limited device instructs, based on the connection, the cloud proxy device to issue resources to a cloud device, including: the cloud limited device sends a first resource release request message to the cloud proxy device, wherein the first resource release request message is used for indicating the cloud proxy device to release resources to the cloud device. Correspondingly, the cloud proxy device obtains an indication of the cloud limited device based on the connection, and issues resources to the cloud device based on the indication, including: the cloud proxy device receives a first resource release request message sent by the cloud limited device based on the connection, wherein the first resource release request message is used for indicating the cloud proxy device to release resources to the cloud device; the cloud proxy device sends a second resource release request message to the cloud device; the resource requested by the second resource release request message is a resource catalog resource; the second resource release request message includes at least one of: the identification of the cloud limited device and the second resource link of the cloud limited device; the end point of the resource in the second resource link of the cloud limited device is the end point of the cloud proxy device; the cloud proxy device obtains a first resource release response message sent by the cloud device and sends a second resource release response message to the cloud limited device. Correspondingly, the cloud limited device receives a second resource release response message sent by the cloud proxy device.

For a cloud device, the cloud device receives a resource published by a cloud proxy device, including: the cloud terminal device receives a second resource release request message sent by the cloud terminal proxy device; the resource requested by the second resource release request message is a resource catalog resource; and sending a first resource release response message to the cloud proxy equipment.

In this embodiment, the resources requested by the first resource release request message include the following ways:

as an implementation manner, the resource requested by the first resource release request message is a cloud proxy resource; the first resource release request message includes at least one of: the agent issues a resource indication, an identification of the cloud limited device and a first resource link of the cloud limited device; and the endpoints of the resources in the first resource link of the cloud limited device are endpoints of the cloud limited device. The proxy release resource indication is used for indicating the cloud proxy equipment to release proxy resources for the cloud limited equipment; the identification of the cloud limited device indicates a target cloud limited device needing to be issued resources by a cloud proxy device agent; the first resource link of the cloud limited device represents a resource which needs to be released to the cloud device.

As another implementation manner, the resource requested by the first resource release request message is a resource directory resource; the first resource release request message includes at least one of: the identification of the cloud limited device and the first resource link of the cloud limited device; and the endpoints of the resources in the first resource link of the cloud limited device are endpoints of the cloud limited device.

Wherein, optionally, the first resource release request message may further include at least one of the following: issuing effective time of resources and indication of cloud limited equipment; the second resource release request message may further include at least one of the following: the effective time of the release resource and the indication of the cloud limited device. The indication of the cloud limited device indicates that the device for publishing the resource is the cloud limited device.

Optionally, the target identifier in the second resource link of the cloud limited device includes an identifier of a target resource and an identifier of the cloud limited device.

In this embodiment, the cloud device publishes the resource, including: the cloud device adds the second resource link to a resource catalog; the published endpoints of the resources are endpoints of the cloud device.

As an optional implementation manner, the adding, by the cloud device, the second resource link to a resource directory includes: and under the condition that the second resource release request message comprises the indication of the cloud limited equipment, or under the condition that the target identifier in the second resource link of the cloud limited equipment comprises the identifier of the target resource and the identifier of the cloud limited equipment, the identifier of the released target resource is identical to the identifier of the target resource in the second resource link.

In an optional embodiment of the present application, before the cloud limited device sends the first resource release request message to the cloud proxy device, the method further includes: the cloud limited device sends a first cloud registration request message to the cloud proxy device; the cloud limited device receives a second cloud registration response message sent by the cloud proxy device; the second cloud registration response message includes at least one of: the user identification, the access token of the cloud limited device, the effective duration of the access token and the update token of the cloud limited device. Correspondingly, before the cloud proxy device receives the first resource release request message sent by the cloud limited device based on the connection, the method further includes: the cloud proxy device receives a first cloud registration request message sent by the cloud limited device and sends a second cloud registration request message to the cloud device; the cloud proxy device receives a first cloud registration response message sent by the cloud device; the first cloud registration response message includes at least one of: the user identification, the access token of the cloud limited device, the effective duration of the access token and the update token of the cloud limited device; the cloud proxy device sends a second cloud registration response message to the cloud limited device; the second cloud registration response message includes at least one of: the user identification, the access token of the cloud limited device, the effective duration of the access token and the update token of the cloud limited device. Correspondingly, the cloud limited device receives a second cloud registration response message sent by the cloud proxy device.

For the cloud device, before the cloud device obtains the resource published by the cloud proxy device, the method further includes: the cloud terminal device receives a second cloud terminal registration request message sent by the cloud terminal proxy device; the cloud end device distributes an access token for the cloud end limited device and associates the cloud end limited device with a user identifier; the cloud end device sends a first cloud end registration response message to the cloud end proxy device; the first cloud registration response message includes at least one of: the user identification, the access token of the cloud limited device, the effective duration of the access token and the update token of the cloud limited device.

In this embodiment, the resources requested by the first cloud registration request message and the second cloud registration request message include the following modes:

as an implementation manner, the resource requested by the first cloud registration request message is a cloud proxy resource; the first cloud registration request message includes at least one of: the cloud end registration indication, the identification of the cloud end limited device and the security credential information of the cloud end limited device are proxied; the resources requested by the second cloud registration request message are account resources; the second cloud registration request message includes at least one of: the cloud limited device comprises an identifier of the cloud limited device, security credential information of the cloud limited device and a user identifier. The proxy cloud registration instruction is used for indicating the cloud proxy equipment to perform proxy cloud registration for the cloud limited equipment; the identifier of the cloud limited device indicates a target cloud limited device which needs to be registered by a cloud proxy device; the security credential information of the cloud limited device is used for the cloud device to conduct security authentication on the registered cloud limited device.

As another implementation manner, the resource requested by the first cloud registration request message is an account resource; the first cloud registration request message includes at least one of: and the identification of the cloud limited equipment and the access token. The access token is obtained by the configurator from the cloud terminal device before the cloud terminal limited device establishes connection with the cloud terminal proxy device. The resources requested by the second cloud registration request message are account resources; the second cloud registration request message includes at least one of: and the identification of the cloud limited equipment and the access token. In this embodiment, the method further includes: and the cloud limited device obtains an access token sent by the configurator. The resources requested by the second cloud registration request message are account resources; the second cloud registration request message includes at least one of: and the identification of the cloud limited equipment and the access token.

In an optional embodiment of the present application, before the cloud limited device sends the first resource release request message to the cloud proxy device, the method further includes: the cloud limited device sends a first cloud login request message to the cloud proxy device; the cloud limited device receives a second cloud login response message sent by the cloud proxy device; the second cloud login response message includes a valid time for accessing the token. Correspondingly, before the cloud proxy device receives the first resource release request message sent by the cloud limited device based on the connection, the method further includes: the cloud proxy equipment receives a first cloud login request message sent by the cloud limited equipment and sends a second cloud login request message to the cloud equipment; the cloud proxy equipment receives a first cloud login response message sent by the cloud equipment; the first cloud login response message comprises the effective time of the access token; the cloud proxy device sends a second cloud login response message to the cloud limited device; the second cloud login response message includes a valid time for accessing the token. Correspondingly, the cloud limited device receives a second cloud login response message sent by the cloud proxy device.

For the cloud device, before the cloud device obtains the resource published by the cloud proxy device, the method further includes: the cloud terminal device receives a second cloud terminal login request message sent by the cloud terminal proxy device; the cloud terminal device sends a first cloud terminal login response message to the cloud terminal proxy device; the first cloud login response message includes a valid time for accessing the token.

In this embodiment, the resources requested by the first cloud login request message and the second cloud login request message include the following modes:

as an implementation manner, the resource requested by the first cloud login request message is a cloud proxy resource; the first cloud login request message includes at least one of the following: the cloud login indication is used for proxy, the identifier of the cloud limited device and the access token of the cloud limited device. The resource requested by the second cloud login request message is a session resource; the second cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification. The proxy cloud login indication is used for indicating the cloud proxy equipment to perform proxy cloud login for the cloud limited equipment. And the cloud login instruction is a cloud login of the cloud limited equipment.

As another implementation manner, the resource requested by the first cloud login request message is a session resource; the first cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification. The resource requested by the second cloud login request message is a session resource; the second cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification. The cloud login indication is a cloud login of the cloud limited equipment.

In an alternative embodiment of the application, the method further comprises: the cloud limited device sends a first update token request message to the cloud proxy device; the cloud limited device receives a second update token response message sent by the cloud proxy device; the second update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens. Correspondingly, the method further comprises the steps of: the cloud proxy device receives a first update token request message sent by the cloud limited device and sends a second update token request message to the cloud device; the cloud agent equipment receives a first update token response message sent by the cloud equipment; the first update token response message includes at least one of: a new access token, an update token, a validity time of the new access token; the cloud proxy device sends a second update token response message to the cloud limited device; the second update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens. Correspondingly, the cloud limited device receives a second update token response message sent by the cloud proxy device.

For a cloud device, the cloud device receives a second update token request message sent by the cloud proxy device; the cloud end equipment updates a new access token and sends a first update token response message to the cloud end proxy equipment; the first update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens.

In this embodiment, the resources requested by the first update token request message and the second update token request message include the following ways:

as an implementation manner, the resource requested by the first update token request message is a cloud proxy resource; the first update token request message includes at least one of: the agent updates the token indication, the identification of the cloud limited equipment, the update token and the user identification. The resource requested by the second update token request message is an update token resource; the second update token request message includes at least one of: and the cloud limited equipment comprises an identifier, an update token and a user identifier.

As another embodiment, the resource requested by the first update token request message is an update token resource; the first update token request message includes at least one of: and the cloud limited equipment comprises an identifier, an update token and a user identifier. The resource requested by the second update token request message is an update token resource; the second update token request message includes at least one of: and the cloud limited equipment comprises an identifier, an update token and a user identifier.

In an optional embodiment of the present application, before the cloud limited device sends the first resource release request message to the cloud proxy device, the method further includes: the cloud limited device sends a first device binding request message to the cloud proxy device; the resource requested by the first equipment binding request message is cloud agent resource; and the cloud limited device receives a second device binding response message sent by the cloud proxy device. Correspondingly, before the cloud proxy device receives the first resource release request message sent by the cloud limited device based on the connection, the method further includes: the cloud proxy device receives a first device binding request message sent by the cloud limited device; the resource requested by the first equipment binding request message is cloud agent resource; the cloud proxy device sends a second device binding request message to the cloud device; the resource requested by the second equipment binding request message is a binding resource; the cloud proxy device receives a first device binding response message sent by the cloud device; the first device binding response message includes a user identification; the cloud proxy device sends a second device binding response message to the cloud limited device; the second device binding response message includes a user identification. Correspondingly, the cloud limited device receives a second device binding response message sent by the cloud proxy device.

For a cloud device, the cloud device receives a second device binding request message sent by the cloud proxy device; the resource requested by the second equipment binding request message is a binding resource; the second device binding request message includes at least one of: the identification of the cloud limited equipment, the security credentials and the security identification of the cloud limited equipment; the cloud end device associates the cloud end limited device and the user identifier and sends a first device binding response message to the cloud end proxy device; the first device binding response message includes a user identification.

In an alternative embodiment, the method further comprises: and the cloud terminal device associates the access tokens of the cloud terminal limited device and the cloud terminal proxy device.

Wherein the first device binding request message includes at least one of: the proxy device binds the indication, the identification of the cloud limited device and the security credential of the cloud limited device; the second device binding response message includes a user identification.

The resource distribution method according to the embodiment of the present application is described in detail below with reference to specific examples. In the following examples of the application, the endpoints of the cloud-limited device may be represented as: "caps: /(fe 80): :2]:2222"; the identification of the cloud-limited device may be expressed as: "88b7c7f0-4b51-4e0a-9faa-cfb439fd7f49"; the endpoints of the cloud proxy device may be represented as: "caps: /(fe 80): :3]:3333"; the endpoints of the cloud device may be represented as: "caps+tcp: // [2001: db8: a: :123]:3333".

Example one

FIG. 3 is a flowchart illustrating a specific example of a resource publishing method according to an embodiment of the present application; as shown in fig. 3, the method includes:

step 301: the cloud agent equipment establishes connection with the cloud equipment, and the cloud equipment establishes association between the cloud agent equipment and the user identification.

Here, the cloud proxy device associates the cloud proxy device with the user identifier in the process of accessing the cloud device or after the cloud device is accessed. The user identifier may be an identifier allocated to the user by the system after the user completes user registration through the client (or configurator). The user identification may be bound to a user account. For example, the user can register through the client APP, and after the registration is completed, the user identification allocated by the system can be obtained.

Step 302: and the cloud limited device obtains information of the cloud proxy device.

The cloud limited device obtains information of the cloud proxy device in two ways:

mode 1: the configurator directly configures cloud proxy equipment information for the cloud limited equipment, and specifically comprises the following steps:

step 3021a: the configurator sends configuration information to the cloud limited equipment, wherein the configuration information comprises cloud proxy equipment information.

As an implementation manner, the configurator may configure cloud proxy device information for the cloud limited device by updating configuration resources, for example, the cloud proxy device configuration resources on the cloud limited device are denoted as "oic.r. proxyconf". The configuration information may include a cloud proxy resource URI and endpoint information of the cloud proxy device, for example, the cloud proxy resource URI is "/oic/cloudproxy", and the endpoint of the cloud proxy resource is "caps: /(fe 80): :2]:3333".

Step 3022a: the cloud limited device sends a response message to the configurator, wherein the response message is used for confirming that the cloud proxy device information is configured successfully.

Mode 2: the cloud limited device actively discovers cloud proxy devices, and specifically comprises the following steps:

step 3021b: the cloud limited device sends a cloud proxy device discovery request, wherein the cloud proxy device discovery request comprises a cloud proxy resource type.

The cloud-limited device may send a cloud proxy device discovery request in a broadcast or multicast manner. The proxy resource type of the cloud proxy resource may be "oic.r.cloudproxy".

Step 3022b: the cloud proxy device receives the cloud proxy device discovery request and sends a cloud proxy device discovery response to the cloud limited device.

The cloud proxy device discovery response may include at least one of the following: the cloud proxy device comprises a proxy resource type of the cloud proxy device, a cloud proxy resource URI and endpoint information of the cloud proxy resource. For example, the returned cloud proxy device has a proxy resource type of "oic.r. cloudproxy", a cloud proxy resource URI of "/oic/cloudproxy", and a cloud proxy resource endpoint of "caps: /(fe 80): :2]:3333".

Step 303: and establishing a secure connection between the cloud limited device and the cloud proxy device.

The cloud limited device establishes a secure connection with the cloud proxy device based on the obtained information of the cloud proxy device.

Step 304: the cloud limited device sends a first cloud registration request message to the cloud proxy device, wherein a resource URI requested by the first cloud registration request message is a cloud proxy resource URI. For example, the cloud proxy resource URI is "/oic/cloudproxy".

The first cloud registration request message may include at least one of the following: the proxy cloud registration instruction, the identification of the cloud limited device and the security credentials of the cloud limited device. The proxy cloud registration instruction is used for indicating the cloud proxy equipment to perform proxy cloud registration for the cloud limited equipment; the identifier of the cloud limited device indicates a target cloud limited device which needs to be registered by the cloud proxy device, and the security credential of the cloud limited device is used for the cloud device to perform security authentication on the registered cloud limited device.

Step 305: the cloud proxy device sends a second cloud registration request message to the cloud device, wherein a resource URI requested by the second cloud registration request message is an account resource URI.

Wherein the account resource URI is "/oic/sec/account". The second cloud registration request message may include at least one of the following: the cloud limited device identification, the cloud limited device security credentials and the user identification.

Step 306: the cloud terminal equipment receives a cloud terminal registration request corresponding to the second cloud terminal registration request message, allocates an access token for the cloud terminal limited equipment, and associates the identification of the cloud terminal limited equipment with the user identification.

Through the step, the cloud limited equipment and the cloud proxy equipment are both associated with the user identification.

It should be noted that, in step 301, in the process of accessing the cloud proxy device to the cloud device, the cloud device allocates an access token to the cloud proxy device, and the allocated access token information may include information such as an access token, an update token, and an expiration time of the access token. Here, the access token information allocated by the cloud device to the cloud limited device may be the same as the access token information allocated to the cloud proxy device, or may be different from the access token information allocated to the cloud proxy device.

Step 307: the cloud end device sends a first cloud end registration response message to the cloud end proxy device; the first cloud registration response message may include at least one of the following: user identification, access token of the cloud limited device, expiration time of the access token, update token of the cloud limited device.

Step 308: the cloud proxy device sends a second cloud registration response message to the cloud limited device; the second cloud registration response message includes at least one of the following: user identification, access token of the cloud limited device, expiration time of the access token, update token of the cloud limited device.

Step 309: the cloud limited device sends a first cloud login request message to the cloud proxy device, wherein a resource URI requested by the first cloud login request message is a cloud proxy resource URI. For example, the cloud proxy resource URI is "/oic/cloudproxy".

Here, the first cloud login request message may include at least one of the following: the method comprises the steps of agent cloud login indication, identification of cloud limited equipment and access token of the cloud limited equipment. The proxy cloud login instruction is used for indicating the cloud proxy equipment to perform proxy cloud login for the cloud limited equipment; the identification of the cloud limited device indicates a target cloud limited device which needs to be logged in by a cloud proxy device; the access token of the cloud limited device is used for carrying out security authentication on the logged-in cloud limited device by the cloud device.

Step 310: the cloud proxy equipment sends a second cloud login request message to the cloud equipment, wherein a resource URI requested by the second cloud login request message is a session resource URI; for example, the session resource URI is "/oic/sec/session".

Here, the second cloud login request message includes at least one of the following: the method comprises the steps of identification of cloud limited equipment, access tokens of the cloud limited equipment, user identification and cloud login indication. And the cloud login instruction is that the cloud limited equipment carries out cloud login.

Step 311: the cloud end equipment receives the second cloud end login request message, responds to equipment login, and sends a first cloud end login response message to the cloud end proxy equipment; the first cloud login response message includes a remaining expiration time of an access token of the cloud limited device.

Step 312: the cloud proxy device sends a second cloud login response message to the cloud limited device, wherein the second cloud login response message comprises the remaining expiration time of the cloud limited device access token.

It should be noted that, steps 309-312 are optional steps, i.e., the device login procedure is an optional step. The purpose of the device login is to confirm that the device maintains a session with the cloud device for subsequent communication, and when the cloud proxy device is logged in, the session between the cloud proxy device and the cloud device is described as being in a maintenance state, and the message routing of the cloud restricted device can reuse the session between the cloud proxy device and the cloud device, so that the cloud restricted device can also log in without cloud.

Step 313: the cloud limited device sends a first resource release request message to the cloud proxy device, wherein a resource URI (uniform resource identifier) requested by the first resource release request message is a cloud proxy resource URI; for example, the cloud proxy resource URI is "/oic/cloudproxy".

Here, the first resource release request message includes at least one of the following: the agent issues a resource instruction, an identifier of the cloud limited device and a resource link of the cloud limited device; the endpoints of the resources in the resource link are endpoints of the cloud limited device. The proxy release resource indication is used for indicating the cloud proxy equipment to release proxy resources for the cloud limited equipment; the identification of the cloud limited device indicates a target cloud limited device needing to be issued resources by a cloud proxy device agent; the resource links of the cloud limited device represent resources which need to be released to the cloud device.

In an optional embodiment of the present application, the first resource release request message may further include an effective time of releasing a resource, that is, a maximum lifetime of a resource link released to a resource directory of the cloud device, and if the cloud device does not receive the resource release request updated by the cloud limited device before the lifetime expires, the resource directory of the cloud device may not store the released resource link.

In an optional embodiment of the present application, the first resource release request message may further include an indication of a cloud limited device, where the indication of the cloud limited device is used to indicate that the device for releasing the resource is the cloud limited device.

For example, the content of the cloud limited device request for proxy resource release is as follows, wherein the bold fonts represent resource links of the cloud limited device; the endpoint information in the resource link is endpoint information of the cloud limited device itself:

where "di" is the device identification of the cloud-limited device, "ttl" is the time to live (i.e., the effective time of) the published resource link, "dt" is the cloud-limited device indication, "proxyfactor" is the proxy published resource indication, and "links" is the resource link of the cloud-limited device.

Step 314, the cloud proxy device sends a second resource release request message to the cloud device, where a resource URI requested by the second resource release request message is a resource directory resource URI; for example, the resource catalog resource URI is "/oic/rd".

Here, the second resource release request message includes at least one of the following: identification of the cloud-limited device and resource linking of the cloud-limited device; the endpoints of the resources in the resource links are endpoints of cloud agent equipment; the target URI in the resource link comprises an identification of the cloud limited device.

In an optional embodiment of the present application, the second resource release request message may further include an indication of a cloud limited device, where the indication of the cloud limited device is used to indicate that the device that provides the resource link is the cloud limited device.

In this embodiment, the cloud proxy device maintains an association between endpoint information in the cloud limited device resource release and endpoint information in the resource link released by the cloud proxy device proxy. That is, for the cloud limited device resources released to the cloud proxy device, the endpoints of the cloud limited device resources released to the cloud proxy device by the cloud proxy device are endpoints of the cloud proxy device itself, but not endpoints of the cloud limited device.

Since the cloud-limited devices of the same type release resources, the "href" parameter in the resource links they provide may be the same. For example, the "href" parameter of all lamps may be "/myLightSwitch", so as to ensure that all resource release requests received by the cloud proxy device have a unique resource URI for each released resource, and the cloud proxy device adds the device identifier of the cloud limited device in front of the "href" parameter value when releasing.

For example, the content of the request of the cloud proxy device for resource release is as follows, the endpoint "eps" in the resource link is endpoint information of the cloud proxy device, and the "href" parameter of the target URI in the resource link includes the cloud limited device identifier:

where "di" is the device identification of the cloud-limited device, "ttl" is the published resource link lifetime (i.e., the valid time of the resource link), "dt" is the cloud-limited device indication, "links" is the resource link of the cloud-limited device, the "href" parameter of the target URI in the resource link includes the identification "88 b7c7f0-4 e 51-4e0a-9faa-cfb439fd7f 49" (i.e., the "di" parameter value) of the cloud-limited device, and "eps" is the endpoint information "caps" of the cloud proxy device: /(fe 80): :3]: 3333'.

Step 315: the cloud device receives a resource release request corresponding to the second resource release request message, and adds a resource link of the cloud limited device to a resource directory; for example, a resource link for the cloud-limited device is added under the "/oic/res" resource.

Here, the cloud device maintains an association between endpoint information in the device resource release and endpoint information in the resource links released by the cloud resource catalog. That is, for the resource published to the cloud device, the endpoint of the resource published by the cloud device is the endpoint of the cloud device itself, but not the endpoint of the cloud proxy device. In addition, the value of the href parameter of the target URI in the resource link of the cloud limited device published by the resource catalog of the cloud device is the same as the value of the href parameter in the resource release request corresponding to the cloud limited device.

The cloud device can determine that the cloud device identifier is not added to the "href" parameter value according to the "href" parameter value added to the identifier "di" parameter value of the cloud limited device in the resource release request, that is, the target URI "href" parameter value in the resource link of the cloud limited device published by the OCF cloud resource catalog is the same as the parameter value of the "href" parameter value in the device resource release request.

In an optional embodiment of the present application, when the second resource release request message includes an indication of the cloud limited device, the cloud device may determine, according to the indication of the cloud limited device, that the resource link in the second resource release request message belongs to the cloud limited device, so as to determine that an identifier of the cloud device is not required to be added to an "href" parameter value in the published resource link, that is, the "href" parameter value of the target URI in the resource link of the cloud limited device published by the resource directory of the cloud device is the same as the "href" parameter value in the resource release request corresponding to the cloud limited device.

For example, the resource links of the cloud-limited device added under the resource directory of the cloud device (resource directory URI is "/oic/res") are as follows, the endpoint "eps" in the resource links is endpoint information of the cloud proxy device, and the "href" parameter value of the target URI in the resource links is the same as the "href" parameter value in the resource links in the resource release of the cloud proxy device:

Step 316: the cloud end device sends a first resource release response message to the cloud end proxy device, wherein the first resource release response message is used for confirming that resource release is successful.

Step 317: the cloud proxy device sends a second resource release response message to the cloud limited device, and the second resource release response message confirms that the resource release of the cloud limited device is successful.

Step 318: when or before the access token of the cloud limited device expires, the cloud limited device sends a first update token request message to a cloud proxy device; for example, the cloud limited device sends a first update token request message to a cloud proxy resource "/oic/cloudproxy" of the cloud proxy device.

Here, the first update token request message includes at least one of the following: the method comprises the steps of agent update token indication, cloud limited equipment identification, update token and user identification. The proxy update token indication is used for indicating the cloud proxy equipment to update the proxy access token for the cloud limited equipment; the identifier of the cloud limited device indicates a target cloud limited device needing to be updated with the token by the cloud proxy device; the update token is a credential of the cloud limited device for updating the access token; the user identification is a target user associated with the cloud-limited device.

Step 319: the cloud proxy device sends a second update token request message to the cloud device; the second update token request message requests update token resources; the token resource URI is "/oic/sec/tokenRefresh". Wherein the second update token request message includes at least one of: identification of cloud limited equipment, update token and user identification.

Step 320: the cloud terminal device updates an access token for the cloud terminal limited device; the cloud end device sends a first update token response message to the cloud end proxy device, wherein the first update token response message comprises at least one of the following: a new access token, an update token of the cloud limited device, and a valid time of the new access token.

Step 321: the cloud proxy device sends a second update token response message to the cloud limited device, wherein the second update token response message comprises at least one of the following: the cloud limited device is provided with a new access token, an update token and an expiration time of the new access token.

Example two

Fig. 4 is a second flowchart of a specific example of a resource publishing method according to an embodiment of the present application; as shown in fig. 4, the method includes:

Step 401: the cloud agent equipment establishes connection with the cloud equipment, and the cloud equipment establishes association between the cloud agent equipment and the user identification.

Step 402: and the cloud limited device obtains information of the cloud proxy device.

step 4021a: the configurator sends configuration information to the cloud limited equipment, wherein the configuration information comprises cloud proxy equipment information.

Step 4022a: the cloud limited device sends a response message to the configurator to confirm that the cloud proxy device information is configured successfully.

step 4021b: the cloud limited device sends a cloud proxy device discovery request, wherein the cloud proxy device discovery request comprises a cloud proxy resource type.

Step 4022b: the cloud proxy device receives the cloud proxy device discovery request and sends a cloud proxy device discovery response to the cloud limited device.

The cloud proxy device discovery response may include at least one of the following: cloud agent resource type, cloud agent resource URI and endpoint information of the cloud agent resource of the cloud agent device. For example, the returned cloud proxy device has a proxy resource type of "oic.r. cloudproxy", a cloud proxy resource URI of "/oic/cloudproxy", and a cloud proxy resource endpoint of "caps: /(fe 80): :2]:3333".

Step 403: and establishing a secure connection between the cloud limited device and the cloud proxy device.

Step 404: the cloud limited device sends a first device binding request message to a cloud proxy device, wherein a resource URI (uniform resource identifier) requested by the first device binding request message is a cloud proxy resource URI; for example, the cloud proxy resource URI is "/oic/cloudproxy".

Here, the first device binding request message includes at least one of: the proxy device binding instruction, the identification of the cloud limited device and the security credential of the cloud limited device. The proxy device binding instruction is used for indicating the cloud proxy device to perform proxy binding of the device and the user for the cloud limited device; the cloud limited device identifier represents a target cloud limited device to be bound by a cloud proxy device agent; the security credentials of the cloud-side limited device are used for carrying out security authentication on the cloud-side limited device requesting binding by the cloud-side device.

Step 405: the cloud proxy device sends a second device binding request message to the cloud device, wherein a resource URI requested by the second device binding request message is a binding resource URI; for example, the binding resource URI is "/oic/bind". Wherein the second device binding request message includes at least one of: the cloud limited device identification, the cloud limited device security credentials and the user identification.

Step 406: and the cloud end device receives a device binding request corresponding to the second device binding request message, and associates the cloud end limited device with the user identifier.

Through the step, the cloud limited device and the cloud proxy device are both associated with the user identifier.

In an optional embodiment of the present application, the cloud device may further associate an identification of the cloud limited device with an access token of the cloud proxy device.

Step 407: the cloud end device sends a first device binding response message to the cloud end proxy device, wherein the first device binding response message comprises a user identifier.

Step 408: the cloud proxy device sends a second device binding response message to the cloud limited device, wherein the second device binding response message comprises the user identification.

Step 409: the cloud limited device sends a first resource release request message to the cloud proxy device, wherein a resource URI (uniform resource identifier) requested by the first resource release request message is a cloud proxy resource URI; for example, the cloud proxy resource URI is "/oic/cloudproxy".

Step 410: the cloud agent equipment sends a second resource release request message to the cloud equipment, wherein a resource URI (uniform resource identifier) requested by the second resource release request message is a resource directory resource URI; for example, the resource catalog resource URI is "/oic/rd".

Step 411: the cloud device receives the second resource release request message, and adds the resource link of the cloud limited device to the resource directory; for example, a resource link of the cloud limited device is added under the/oic/res resource.

Here, the cloud device maintains an association between endpoint information in the device resource release and endpoint information in the resource links released by the cloud resource catalog. That is, for the resource published to the cloud device, the endpoint of the resource published by the cloud device is the endpoint of the cloud device itself, but not the endpoint of the cloud proxy device. In addition, the parameter value of the 'href' of the target URI in the resource link of the cloud limited device published by the resource catalog of the cloud device is the same as the parameter value of the 'href' parameter value in the resource publishing request corresponding to the cloud limited device.

In an optional embodiment of the present application, when the second resource release request message includes an indication of the cloud limited device, the cloud device may determine, according to the indication of the cloud limited device, that the resource link in the second resource release request message belongs to the cloud limited device, so as to determine that an "href" parameter value in the published resource link is not required to be added with an identifier of the cloud device, that is, a "href" parameter value of a target URI in the resource link of the cloud limited device published by a resource directory of the cloud device is the same as a parameter value of an "href" parameter value in a resource release request corresponding to the cloud limited device.

Step 412: the cloud end device sends a first resource release response message to the cloud end proxy device, wherein the first resource release response message is used for confirming that resource release is successful.

Step 413: the cloud proxy device sends a second resource release response message to the cloud limited device, and the second resource release response message confirms that the resource release of the cloud limited device is successful.

In this embodiment, the detailed descriptions of steps 409 to 413 may refer to the detailed descriptions of steps 313 to 317 in the foregoing examples, and are not repeated here.

In this example, optionally, after step 413, steps 318 to 321 in the foregoing embodiment may be further included, which will not be described herein.

Example three

Fig. 5 is a flowchart illustrating a specific example of a resource publishing method according to an embodiment of the present application; as shown in fig. 5, the method includes:

step 500: the cloud agent equipment establishes connection with the cloud equipment, and the cloud equipment establishes association between the cloud agent equipment and the user identification.

Step 501: the configurator obtains an access token of the cloud limited device from the cloud device.

As an implementation manner, the configurator may send a token acquisition request message to the cloud device, where the token acquisition request message includes an identifier of the cloud limited device; the configurator obtains a token acquisition response message sent by the cloud device; and the token acquisition response message comprises an access token of the cloud limited equipment.

Step 502: and the configurator sends the access token to the cloud limited device. The configurator may send the access token to the cloud limited device by updating a cloud configuration resource of the cloud limited device (a resource type of the cloud configuration resource is "oic.r. configurable conf").

Optionally, as an implementation manner, the configurator may further configure the cloud access URI and the cloud identifier for the cloud configuration resource of the cloud limited device, that is, the attribute of the cloud configuration resource may include: the access token, the cloud access URI and the cloud identifier. As another implementation, the configurator does not need to configure the cloud access URI and the cloud identifier for the cloud configuration resource of the cloud limited device, because the cloud proxy device already has the cloud access information.

Step 503: and the cloud limited device obtains information of the cloud proxy device. As an implementation manner, the cloud proxy device discovery request includes a cloud proxy resource type.

Step 504: the cloud proxy device receives the cloud proxy device discovery request and sends a cloud proxy device discovery response to the cloud limited device.

The cloud proxy device discovery response may include at least one of the following: the agent resource type of the cloud agent equipment and the endpoint information of the cloud agent resource. For example, the returned cloud proxy device has a proxy resource type of "oic.d. cloudproxy", and the cloud proxy device has a endpoint of "caps: /(fe 80): :2]:3333".

Step 505: and establishing a secure connection between the cloud limited device and the cloud proxy device.

Step 506: the cloud limited device sends a first cloud registration request message to the cloud proxy device, wherein a resource URI requested by the first cloud registration request message is an account resource URI. For example, the account resource URI is "/oic/sec/account".

Here, the first cloud registration request message includes at least one of the following: identification of the cloud-limited device and access token of the cloud-limited device. The cloud-limited device identifier indicates a target cloud-limited device to be registered to the cloud device; the access token of the cloud limited device is used for carrying out security authentication on the registered cloud limited device by the cloud device.

Step 507: the cloud proxy equipment sends a second cloud registration request message to the cloud equipment, wherein a resource URI (Uniform resource identifier) requested by the second cloud registration request message is an account resource; for example, the account resource URI is "/oic/sec/account". The second cloud registration request message includes at least one of the following: identification of the cloud-limited device, and access token of the cloud-limited device.

Step 508: the cloud terminal device receives the registration request of the second cloud terminal registration request message, distributes an access token, an update token and the expiration time of the access token for the cloud terminal limited device, and associates the identifier of the cloud terminal limited device with the user identifier. The cloud end device sends a first cloud end registration response message to the cloud end proxy device.

The first cloud registration response message includes at least one of the following: user identification, access token of the cloud limited device, effective time of the access token and update token of the cloud limited device.

Step 509: the cloud proxy device sends a second cloud registration response message to the cloud limited device, wherein the second cloud registration response message comprises at least one of the following components: user identification, access token of the cloud limited device, expiration time of the access token, update token of the cloud limited device.

Step 510: the cloud limited device sends a first cloud login request message to the cloud proxy device, and a resource URI requested by the first cloud login request message is a session resource URI. For example, the session resource URI is "/oic/sec/session".

The first cloud login request message may include at least one of the following: the method comprises the steps of identification of cloud limited equipment, access tokens of the cloud limited equipment, user identification and cloud login indication. The identification of the cloud limited device indicates a target cloud limited device which needs to log in to the cloud device; the access token of the cloud limited device is used for carrying out security authentication on the logged-in cloud limited device by the cloud device; the user identifier is a user identifier associated with the cloud-limited device; the cloud login indication is used for indicating to perform cloud login.

Step 511: the cloud proxy device sends a second cloud login request message to the cloud device, wherein a resource URI requested by the second cloud login request message is a session resource URI. For example, the session resource URI is "/oic/sec/session".

The second cloud login request message may include at least one of the following: the method comprises the steps of identification of cloud limited equipment, access tokens of the cloud limited equipment, user identification and cloud login indication.

Step 512: the cloud end equipment receives a login request corresponding to the second cloud end login request message, responds to equipment login, and sends a first cloud end login response message to the cloud end proxy equipment; the first cloud login response message includes a valid time of an access token of the cloud limited device.

Step 513: the cloud proxy device sends a second cloud login response message to the cloud limited device, wherein the second cloud login response message comprises the remaining expiration time of the access token of the cloud limited device.

It should be noted that, steps 510-513 are optional steps, i.e., the device login procedure is an optional step. The purpose of the device login is to confirm that the device maintains a session with the cloud device for subsequent communication, and when the cloud proxy device is logged in, the session between the cloud proxy device and the cloud device is described as being in a maintenance state, and the message routing of the cloud restricted device can reuse the session between the cloud proxy device and the cloud device, so that the cloud restricted device can also log in without cloud.

Step 514: the cloud limited device sends a first resource release request message to the cloud proxy device, wherein a resource URI requested by the first resource release request message is a resource directory resource, for example, the resource directory resource URI is "/oic/rd".

Here, the first resource release request message includes at least one of the following: identification of the cloud-limited device, and resource linking of the cloud-limited device. The endpoints of the resources in the resource links are endpoints of cloud limited equipment. The identification of the cloud limited device indicates a target cloud limited device needing to release resources; the resource links of the cloud limited device represent resources which need to be released to the cloud device.

Where "di" is the device identifier of the cloud-limited device, "ttl" is the lifetime of the published resource link (i.e., the effective time of the resource link), "dt" is the indication of the cloud-limited device, "links" is the resource link of the cloud-limited device, and "eps" in the resource link is endpoint information "caps" of the cloud-limited device itself: /(fe 80): : b1d6]:22222 ".

Step 515: the cloud agent equipment sends a second resource release request message to the cloud equipment, wherein a resource URI (uniform resource identifier) requested by the second resource release request message is a resource directory resource URI; for example, the resource catalog resource URI is "/oic/rd".

Here, the second resource release request message includes at least one of the following: identification of the cloud-limited device, and resource linking of the cloud-limited device. The endpoints of the resources in the resource links are endpoints of cloud agent equipment; the target URI in the resource link includes an identification of the cloud-limited device.

Step 516: the cloud device receives a resource release request corresponding to the second resource release request message, and adds a resource link of the cloud limited device to a resource directory; for example, a resource link for the cloud-limited device is added under the "/oic/res" resource.

In an optional embodiment of the present application, when the second resource release request message includes an indication of the cloud limited device, the cloud device may determine, according to the indication of the cloud limited device, that the resource link in the second resource release request message belongs to the cloud limited device, so as to determine that an "href" parameter value in the published resource link is not required to be added with an identifier of the cloud device, that is, the "href" parameter value of the target URI in the resource link of the cloud limited device published by the resource catalog of the cloud device is the same as the "href" parameter value in the resource release request corresponding to the cloud limited device.

Step 517: the cloud end device sends a first resource release response message to the cloud end proxy device, wherein the first resource release response message is used for confirming that resource release is successful.

Step 518: the cloud proxy device sends a second resource release response message to the cloud limited device, and the second resource release response message confirms that the resource release of the cloud limited device is successful.

Step 519: when or before the access token of the cloud limited device expires, the cloud limited device sends a first update token request message to a cloud proxy device; the first update token request message requests an update token resource, the token resource URI being "/oic/sec/tokenRefresh".

Here, the first update token request message includes at least one of the following: identification of cloud limited equipment, update token and user identification. The identification of the cloud limited device indicates a target cloud limited device needing to update the token; the update token is a credential of the cloud limited device for updating the access token; and the user identification represents a target user associated with the cloud limited device.

Step 520: the cloud proxy device sends a second update token request message to the cloud device; the second update token request message requests an update token resource, the token resource URI being "/oic/sec/tokenRefresh". Wherein the second update token request message includes at least one of: cloud limited device identification, update token, user identification.

Step 521: the cloud terminal device updates an access token for the cloud terminal limited device; after the access token is updated successfully, the cloud terminal device sends a first update token response message to the cloud terminal proxy device. Wherein the first update token response message includes at least one of: the cloud limited device is provided with a new access token, an update token and the effective time of the new access token.

Step 522: the cloud proxy device sends a second update token response message to the cloud limited device, wherein the second update token response message comprises at least one of the following: the cloud limited device is provided with a new access token, an update token and the effective time of the new access token.

The cloud terminal proxy equipment and the cloud terminal limited equipment are connected, so that the cloud terminal limited equipment which cannot interact with the cloud terminal equipment can release resources through the cloud terminal proxy equipment, and the problem that the cloud terminal limited equipment cannot release resources to the cloud terminal equipment is solved.

The embodiment of the application also provides cloud limited equipment. Fig. 6 is a schematic structural diagram of a cloud limited device according to an embodiment of the present application; as shown in fig. 6, the apparatus includes: a first connection establishment unit 31 and a first transmission unit 32; wherein, the liquid crystal display device comprises a liquid crystal display device,

The first connection establishing unit 31 is configured to establish a connection with a cloud proxy device;

the first transmission unit 32 is configured to transmit information based on the connection and the cloud proxy device, where the information is used for the cloud proxy device to issue resources to the cloud device.

In an optional embodiment of the present application, the first connection establishing unit 31 is configured to obtain information of the cloud proxy device, and establish a connection with the cloud proxy device based on the information.

as an implementation manner, the first connection establishing unit 31 is configured to receive configuration information sent by the configurator, where the configuration information includes information of the cloud proxy device.

As another embodiment, the first connection establishment unit 31 is configured to send the discovery request message by broadcasting or multicasting; the discovery request message comprises a cloud proxy resource type; receiving a discovery response message; the discovery response message includes information of the cloud proxy device.

In an optional embodiment of the present application, the first transmission unit 32 is configured to instruct the cloud proxy device to issue a resource to a cloud device based on the connection.

In this embodiment, the first transmission unit 32 is configured to send a first resource release request message to the cloud proxy device, where the first resource release request message is used to instruct the cloud proxy device to release resources to the cloud device.

as an implementation manner, the resource requested by the first resource release request message is a cloud proxy resource; the first resource release request message includes at least one of: the agent issues a resource indication, an identification of the cloud limited device and a first resource link of the cloud limited device; and the endpoints of the resources in the first resource link of the cloud limited device are endpoints of the cloud limited device.

Optionally, the first resource release request message further includes at least one of: the effective time of the release resource and the indication of the cloud limited device.

In an optional embodiment of the present application, the first transmission unit 32 is further configured to receive a second resource release response message sent by the cloud proxy device. And the second resource release response message is used for confirming that the resource release is successful.

In an optional embodiment of the present application, the first transmission unit 32 is further configured to send a first cloud registration request message to the cloud proxy device before sending a first resource release request message to the cloud proxy device; receiving a second cloud registration response message sent by the cloud proxy device; the second cloud registration response message includes at least one of: the user identification, the access token of the cloud limited device, the effective duration of the access token and the update token of the cloud limited device.

In this embodiment, the resources requested by the first cloud registration request message include the following ways:

as an implementation manner, the resource requested by the first cloud registration request message is a cloud proxy resource; the first cloud registration request message includes at least one of: the cloud terminal registration method comprises the steps of agent cloud terminal registration indication, identification of the cloud terminal limited equipment and security credential information of the cloud terminal limited equipment.

As another implementation manner, the resource requested by the first cloud registration request message is an account resource; the first cloud registration request message includes at least one of: and the identification of the cloud limited equipment and the access token.

In an alternative embodiment of the application, the first transmission unit 32 is further configured to obtain the access token sent by the configurator.

In an optional embodiment of the present application, the first transmission unit 32 is further configured to send a first cloud login request message to the cloud proxy device before sending a first resource release request message to the cloud proxy device; receiving a second cloud login response message sent by the cloud proxy device; the second cloud login response message includes a valid time for accessing the token.

In this embodiment, the resources requested by the first cloud login request message include the following ways:

as an implementation manner, the resource requested by the first cloud login request message is a cloud proxy resource; the first cloud login request message includes at least one of the following: the cloud login indication is used for proxy, the identifier of the cloud limited device and the access token of the cloud limited device.

As another implementation manner, the resource requested by the first cloud login request message is a session resource; the first cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification.

In an optional embodiment of the present application, the first transmission unit 32 is further configured to send a first update token request message to the cloud proxy device; receiving a second update token response message sent by the cloud proxy device; the second update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens.

In this embodiment, the resources requested by the first update token request message include the following ways:

as an implementation manner, the resource requested by the first update token request message is a cloud proxy resource; the first update token request message includes at least one of: the agent updates the token indication, the identification of the cloud limited equipment, the update token and the user identification.

As another embodiment, the resource requested by the first update token request message is an update token resource; the first update token request message includes at least one of: and the cloud limited equipment comprises an identifier, an update token and a user identifier.

In an optional embodiment of the present application, the first transmission unit 32 is further configured to send a first device binding request message to the cloud proxy device before sending the first resource release request message to the cloud proxy device; the resource requested by the first equipment binding request message is cloud agent resource; and receiving a second device binding response message sent by the cloud proxy device.

Wherein the first device binding request message includes at least one of: the proxy device binds the indication, the identification of the cloud limited device and the security credential of the cloud limited device;

the second device binding response message includes a user identification.

In the embodiment of the present application, the first connection establishment unit 31 in the cloud limited device may be implemented by a central processing unit (CPU, central Processing Unit), a digital signal processor (DSP, digital Signal Processor), a micro control unit (MCU, microcontroller Unit) or a programmable gate array (FPGA, field-Programmable Gate Array) in the device in practical application; the first transmission unit 32 in the device may be implemented in practical application by a communication module (including a basic communication suite, an operating system, a communication module, a standardized interface, a standardized protocol, etc.) and a transceiver antenna.

It should be noted that: in the device provided in the above embodiment, only the division of each program module is used for illustration when resource release is performed, and in practical application, the processing allocation may be performed by different program modules according to needs, that is, the internal structure of the device is divided into different program modules, so as to complete all or part of the processing described above. In addition, the device provided in the foregoing embodiments and the resource release method embodiment belong to the same concept, and specific implementation processes of the device and the resource release method embodiment are detailed in the method embodiment, which is not described herein again.

The embodiment of the application also provides cloud proxy equipment. Fig. 7 is a schematic structural diagram of a cloud proxy device according to an embodiment of the present application; as shown in fig. 7, the cloud proxy device includes: a second connection establishment unit 41, a second transmission unit 42, and a third transmission unit 43; wherein, the liquid crystal display device comprises a liquid crystal display device,

the second connection establishing unit 41 is configured to establish a connection with the cloud limited device;

the second transmission unit 42 is configured to transmit information with the cloud limited device based on the connection;

the third transmission unit 43 is configured to issue the resource of the cloud limited device to a cloud device based on the information transmitted by the second transmission unit 42.

The second connection establishment unit 41 is configured to send information of the cloud proxy device to the cloud limited device, where the information of the cloud proxy device is used for establishing connection between the cloud limited device and the cloud proxy device.

In an optional embodiment of the present application, the second connection establishment unit 41 is configured to receive a discovery request message sent by the cloud limited device through broadcasting or multicasting; the discovery request message comprises a cloud proxy resource type; sending a discovery response message to the cloud limited device; the discovery response message includes information of the cloud proxy device.

In an alternative embodiment of the present application, the second transmission unit 42 is configured to obtain an indication of the cloud limited device based on the connection;

the third transmission unit 43 is configured to issue a resource to a cloud device based on the indication obtained by the second transmission unit 42.

In this embodiment, the second transmission unit 42 is configured to receive, based on the connection, a first resource release request message sent by the cloud limited device, where the first resource release request message is used to instruct the cloud proxy device to release a resource to a cloud device;

The third transmission unit 43 is configured to send a second resource release request message to the cloud device; the resource requested by the second resource release request message is a resource catalog resource; the second resource release request message includes at least one of: the identification of the cloud limited device and the second resource link of the cloud limited device; the end point of the resource in the second resource link of the cloud limited device is the end point of the cloud proxy device; the cloud device is further configured to obtain a first resource release response message sent by the cloud device;

the second transmission unit 42 is further configured to send a second resource release response message to the cloud limited device.

Optionally, the first resource release request message further includes at least one of: issuing effective time of resources and indication of cloud limited equipment; the second resource release request message further includes at least one of the following: the effective time of the release resource and the indication of the cloud limited device.

In an optional embodiment of the present application, the target identifier in the second resource link of the cloud limited device includes an identifier of a target resource and an identifier of the cloud limited device.

In an optional embodiment of the present application, the second transmission unit 42 is further configured to receive, before receiving, based on the connection, the first resource release request message sent by the cloud limited device, a first cloud registration request message sent by the cloud limited device;

The third transmission unit 43 is further configured to send a second cloud registration request message to the cloud device; receiving a first cloud registration response message sent by the cloud device; the first cloud registration response message includes at least one of: the user identification, the access token of the cloud limited device, the effective duration of the access token and the update token of the cloud limited device;

the second transmission unit 42 is further configured to send a second cloud registration response message to the cloud limited device; the second cloud registration response message includes at least one of: the user identification, the access token of the cloud limited device, the effective duration of the access token and the update token of the cloud limited device.

as an implementation manner, the resource requested by the first cloud registration request message is a cloud proxy resource; the first cloud registration request message includes at least one of: the cloud end registration indication, the identification of the cloud end limited device and the security credential information of the cloud end limited device are proxied;

The resources requested by the second cloud registration request message are account resources; the second cloud registration request message includes at least one of: the cloud limited device comprises an identifier of the cloud limited device, security credential information of the cloud limited device and a user identifier.

As another implementation manner, the resource requested by the first cloud registration request message is an account resource; the first cloud registration request message includes at least one of: the identification of the cloud limited device and the access token;

the resources requested by the second cloud registration request message are account resources; the second cloud registration request message includes at least one of: and the identification of the cloud limited equipment and the access token.

The access token is obtained by a configurator from the cloud device for the cloud limited device before the cloud limited device establishes connection with the cloud proxy device.

In an optional embodiment of the present application, the second transmission unit 42 is further configured to receive, before receiving, based on the connection, the first resource release request message sent by the cloud limited device, a first cloud login request message sent by the cloud limited device;

The third transmission unit 43 is further configured to send a second cloud login request message to the cloud device; receiving a first cloud login response message sent by the cloud device; the first cloud login response message comprises the effective time of the access token;

the second transmission unit 42 is further configured to send a second cloud login response message to the cloud limited device; the second cloud login response message includes a valid time for accessing the token.

as an implementation manner, the resource requested by the first cloud login request message is a cloud proxy resource; the first cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device and the access token of the cloud limited device are proxied;

the resource requested by the second cloud login request message is a session resource; the second cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification.

As another implementation manner, the resource requested by the first cloud login request message is a session resource; the first cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification;

In an optional embodiment of the present application, the second transmission unit 42 is further configured to receive a first update token request message sent by the cloud limited device;

the third transmission unit 43 is further configured to send a second update token request message to the cloud device; receiving a first update token response message sent by the cloud device; the first update token response message includes at least one of: a new access token, an update token, a validity time of the new access token;

the second transmission unit 42 is further configured to send a second update token response message to the cloud limited device; the second update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens.

as an implementation manner, the resource requested by the first update token request message is a cloud proxy resource; the first update token request message includes at least one of: agent update token indication, identification of the cloud limited device, update token, user identification:

the resource requested by the second update token request message is an update token resource; the second update token request message includes at least one of: and the cloud limited equipment comprises an identifier, an update token and a user identifier.

As another embodiment, the resource requested by the first update token request message is an update token resource; the first update token request message includes at least one of: the identification of the cloud limited equipment, the update token and the user identification;

In an optional embodiment of the present application, the second transmission unit 42 is further configured to receive, before receiving, based on the connection, the first resource release request message sent by the cloud limited device, a first device binding request message sent by the cloud limited device; the resource requested by the first equipment binding request message is cloud agent resource;

The third transmission unit 43 is further configured to send a second device binding request message to the cloud device; the resource requested by the second equipment binding request message is a binding resource; receiving a first device binding response message sent by the cloud device; the first device binding response message includes a user identification;

the second transmission unit 42 is further configured to send a second device binding response message to the cloud limited device; the second device binding response message includes a user identification.

the second device binding request message includes at least one of: the cloud limited device comprises an identifier of the cloud limited device, a security credential of the cloud limited device and a security identifier.

In the embodiment of the present application, the second connection establishment unit 41 in the cloud limited device may be implemented by CPU, DSP, MCU or FPGA in the device in practical application; the second transmission unit 42 and the third transmission unit 43 in the device may be implemented in practical application by a communication module (including a basic communication suite, an operating system, a communication module, a standardized interface, a protocol, etc.) and a transceiver antenna.

The embodiment of the application also provides cloud equipment. Fig. 8 is a schematic diagram of a structural composition of a cloud device according to an embodiment of the present application; as shown in fig. 8, the cloud device includes a fourth transmission unit 51 and a publishing unit 52; wherein, the liquid crystal display device comprises a liquid crystal display device,

the fourth transmission unit 51 is configured to obtain a resource issued by the cloud proxy device; the resource is a resource of the cloud limited device, which is obtained by the cloud proxy device based on connection with the cloud limited device;

the publication unit 52 is configured to publish the resource.

In an optional embodiment of the present application, the fourth transmission unit 51 is configured to receive a second resource release request message sent by the cloud proxy device; the resource requested by the second resource release request message is a resource catalog resource; the second resource release request message includes at least one of: the identification of the cloud limited device and the second resource link of the cloud limited device; and the end point of the resource in the second resource link of the cloud limited device is the end point of the cloud proxy device.

Optionally, the second resource release request message further includes at least one of the following: the effective time of the release resource and the indication of the cloud limited device.

In an alternative embodiment of the application, the publication unit 52 is configured to add the second resource link to a resource catalog; the published endpoints of the resources are endpoints of the cloud device.

In an optional embodiment of the present application, the publishing unit 52 is further configured to, in a case where the indication of the cloud limited device is included in the second resource publishing request message, or in a case where the target identifier in the second resource link of the cloud limited device includes the identifier of the target resource and the identifier of the cloud limited device, publish the identifier of the target resource to be the same as the identifier of the target resource in the second resource link.

In an optional embodiment of the present application, the fourth transmission unit 51 is further configured to send a first resource release response message to the cloud proxy device.

In an alternative embodiment of the application, as shown in fig. 9, the device further comprises a registration unit 53;

the fourth transmission unit 51 is further configured to receive a second cloud registration request message sent by the cloud proxy device before obtaining the resource issued by the cloud proxy device;

the registration unit 53 is configured to allocate an access token to the cloud limited device and associate the cloud limited device with a user identifier;

the fourth transmission unit 51 is further configured to send a first cloud registration response message to the cloud proxy device; the first cloud registration response message includes at least one of: the user identification, the access token of the cloud limited device, the effective duration of the access token and the update token of the cloud limited device.

In this embodiment, the resource requested by the second cloud registration request message is an account resource; the second cloud registration request message includes at least one of: the cloud limited equipment identification, the security credential information of the cloud limited equipment and the user identification;

or the resource requested by the second cloud registration request message is an account resource; the second cloud registration request message includes at least one of: and the identification of the cloud limited equipment and the access token. The access token is obtained by a configurator from the cloud device for the cloud limited device before the cloud limited device establishes connection with the cloud proxy device.

In an optional embodiment of the present application, the fourth transmission unit 51 is further configured to receive a second cloud login request message sent by the cloud proxy device before obtaining the resource issued by the cloud proxy device; sending a first cloud login response message to the cloud proxy device; the first cloud login response message includes a valid time for accessing the token.

In this embodiment, the resource requested by the second cloud login request message is a session resource; the second cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification.

In an alternative embodiment of the application, as shown in fig. 10, the apparatus further comprises an updating unit 54;

the fourth transmission unit 51 is further configured to receive a second update token request message sent by the cloud proxy device;

the updating unit 54 is configured to update a new access token;

the fourth transmission unit 51 is further configured to send a first update token response message to the cloud proxy device; the first update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens.

In this embodiment, the resource requested by the second update token request message is an update token resource; the second update token request message includes at least one of: and the cloud limited equipment comprises an identifier, an update token and a user identifier.

In an alternative embodiment of the application, as shown in fig. 11, the device further comprises a binding unit 55;

the fourth transmission unit 51 is further configured to receive a second device binding request message sent by the cloud proxy device before obtaining the resource issued by the cloud proxy device; the resource requested by the second equipment binding request message is a binding resource; the second device binding request message includes at least one of: the identification of the cloud limited equipment, the security credentials and the security identification of the cloud limited equipment;

the binding unit 55 is configured to associate the cloud limited device with a user identifier;

the fourth transmission unit 51 is further configured to send a first device binding response message to the cloud proxy device; the first device binding response message includes a user identification.

Optionally, the binding unit 55 is further configured to associate access tokens of the cloud limited device and the cloud proxy device.

In the embodiment of the present application, the registering unit 53, the updating unit 54, the publishing unit 52 and the binding unit 55 in the cloud device may be implemented by CPU, DSP, MCU or FPGA in the device in practical application; the fourth transmission unit 51 in the device may be implemented in practical application by a communication module (including a basic communication suite, an operating system, a communication module, a standardized interface, a standardized protocol, etc.) and a transceiver antenna.

Fig. 12 is a schematic structural diagram of an apparatus provided in an embodiment of the present application. The device may be a cloud limited device, a cloud proxy device, or a cloud device, as shown in fig. 12, where the device 600 includes a processor 610, and the processor 610 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 12, the device may also include a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the method in an embodiment of the application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, as shown in fig. 12, the device may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.

Optionally, the device may be specifically a cloud limited device in the embodiment of the present application, and the device may implement a corresponding flow implemented by the cloud limited device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the device may be specifically a cloud proxy device in the embodiment of the present application, and the device may implement a corresponding flow implemented by the cloud proxy device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the device may be specifically a cloud device in the embodiment of the present application, and the device may implement a corresponding flow implemented by the cloud device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 13 is a schematic structural view of a chip of an embodiment of the present application. The chip 700 shown in fig. 13 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, as shown in fig. 13, chip 700 may also include memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the method in an embodiment of the application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

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

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

Optionally, the chip may be applied to the cloud limited device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the cloud limited device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to the cloud proxy device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the cloud proxy device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to the cloud device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the cloud device in each method in the embodiment of the present application, which is not described herein for brevity.

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

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the application may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is illustrative but not restrictive, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing a computer program. Optionally, the computer readable storage medium may be applied to the cloud limited device in the embodiment of the present application, and the computer program makes a computer execute corresponding processes implemented by the cloud limited device in each method in the embodiment of the present application, which are not described herein for brevity.

Optionally, the computer readable storage medium may be applied to the cloud proxy device in the embodiment of the present application, and the computer program makes a computer execute corresponding processes implemented by the cloud proxy device in each method in the embodiment of the present application, which are not described herein for brevity.

Optionally, the computer readable storage medium may be applied to the cloud device in the embodiment of the present application, and the computer program makes the computer execute corresponding processes implemented by the cloud device in each method in the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program product comprising computer program instructions. Optionally, the computer program product may be applied to the cloud limited device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding flow implemented by the cloud limited device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program product may be applied to the cloud proxy device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the cloud proxy device in each method of the embodiment of the present application, which is not described herein for brevity.

Optionally, the computer program product may be applied to the cloud device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding flow implemented by the cloud device in each method in the embodiment of the present application, which is not described herein for brevity.

The embodiment of the application also provides a computer program. Optionally, the computer program may be applied to the cloud limited device in the embodiment of the present application, where the computer program makes the computer execute a corresponding procedure implemented by the cloud limited device in the method according to the embodiment of the present application, and for brevity, will not be described herein.

The embodiment of the application also provides a computer program. Optionally, the computer program may be applied to the cloud proxy device in the embodiment of the present application, where the computer program makes the computer execute the corresponding procedure implemented by the cloud proxy device in the method according to the embodiment of the present application, and for brevity, details are not repeated herein.

The embodiment of the application also provides a computer program. Optionally, the computer program may be applied to the cloud device in the embodiment of the present application, where the computer program makes the computer execute the corresponding procedure implemented by the cloud device in the method according to the embodiment of the present application, and for brevity, will not be described herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A resource publishing method, the method comprising:

the cloud limited device establishes connection with a cloud proxy device;

the cloud terminal limited equipment transmits information to the cloud terminal proxy equipment based on the connection, the information is used for the cloud terminal proxy equipment to issue resources of the cloud terminal limited equipment to the cloud terminal equipment, and endpoints of the resources of the cloud terminal limited equipment added in a resource catalog of the cloud terminal equipment are endpoints of the cloud terminal proxy equipment; wherein the cloud-limited device cannot establish a connection with the cloud device;

the cloud limited device transmits information with the cloud proxy device based on the connection, and the cloud limited device comprises:

the cloud limited device instructs the cloud proxy device to issue resources of the cloud limited device to a cloud device based on the connection.

2. The method of claim 1, wherein the cloud-limited device establishes a connection with a cloud proxy device, comprising:

the cloud limited device obtains information of the cloud proxy device, and connection with the cloud proxy device is established based on the information.

3. The method of claim 2, wherein the cloud limited device obtains information of a cloud proxy device, comprising:

the cloud limited device receives configuration information sent by a configurator, wherein the configuration information comprises information of cloud proxy devices.

4. The method of claim 2, wherein the cloud limited device obtains information of a cloud proxy device, comprising:

the cloud limited device sends a discovery request message in a broadcast or multicast mode; the discovery request message comprises a cloud proxy resource type;

the cloud limited device receives a discovery response message; the discovery response message includes information of the cloud proxy device.

5. The method of any of claims 2 to 4, wherein the information of the cloud proxy device comprises at least one of: cloud agent resource identification of the cloud agent equipment and endpoint information of the cloud agent resources.

6. The method of claim 1, wherein the cloud limited device instructs the cloud proxy device to publish resources to a cloud device based on the connection, comprising:

the cloud limited device sends a first resource release request message to the cloud proxy device, wherein the first resource release request message is used for indicating the cloud proxy device to release resources to the cloud device.

7. The method of claim 6, wherein the resource requested by the first resource release request message is a cloud proxy resource;

the first resource release request message includes at least one of: the agent issues a resource indication, an identification of the cloud limited device and a first resource link of the cloud limited device;

and the endpoints of the resources in the first resource link of the cloud limited device are endpoints of the cloud limited device.

8. The method of claim 7, wherein the first resource release request message further comprises at least one of: the effective time of the release resource and the indication of the cloud limited device.

9. The method according to any one of claims 6 to 8, wherein the method further comprises:

and the cloud limited device receives a second resource release response message sent by the cloud proxy device.

10. The method of any of claims 6 to 8, wherein before the cloud limited device sends a first resource publication request message to the cloud proxy device, the method further comprises:

the cloud limited device sends a first cloud registration request message to the cloud proxy device;

the cloud limited device receives a second cloud registration response message sent by the cloud proxy device; the second cloud registration response message includes at least one of: the cloud limited device comprises a user identifier, an access token of the cloud limited device, an effective duration of the access token and an update token of the cloud limited device.

11. The method of claim 10, wherein the resource requested by the first cloud registration request message is a cloud proxy resource;

the first cloud registration request message includes at least one of: the cloud terminal registration method comprises the steps of agent cloud terminal registration indication, identification of the cloud terminal limited equipment and security credential information of the cloud terminal limited equipment.

12. The method of any of claims 6 to 8, wherein before the cloud limited device sends a first resource publication request message to the cloud proxy device, the method further comprises:

The cloud limited device sends a first cloud login request message to the cloud proxy device;

the cloud limited device receives a second cloud login response message sent by the cloud proxy device; the second cloud login response message includes a valid time for accessing the token.

13. The method of claim 12, wherein the resource requested by the first cloud login request message is a cloud proxy resource;

the first cloud login request message includes at least one of the following: the cloud terminal access token comprises an agent cloud terminal login indication, an identification of the cloud terminal limited equipment and an access token of the cloud terminal limited equipment.

14. The method of any one of claims 1 to 4, wherein the method further comprises:

the cloud limited device sends a first update token request message to the cloud proxy device;

the cloud limited device receives a second update token response message sent by the cloud proxy device; the second update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens.

15. The method of claim 14, wherein the resource requested by the first update token request message is a cloud proxy resource;

The first update token request message includes at least one of: the agent updates the token indication, the identification of the cloud limited equipment, the update token and the user identification.

16. The method of any of claims 1-4, wherein, before the cloud limited device sends a first resource publication request message to the cloud proxy device, the method further comprises:

the cloud limited device sends a first device binding request message to the cloud proxy device; the resource requested by the first equipment binding request message is cloud agent resource;

and the cloud limited device receives a second device binding response message sent by the cloud proxy device.

17. The method of claim 16, wherein the first device binding request message comprises at least one of: the proxy device binds the indication, the identification of the cloud limited device and the security credential of the cloud limited device;

the second device binding response message includes a user identification.

18. The method of claim 6, wherein the resource requested by the first resource release request message is a resource catalog resource;

the first resource release request message includes at least one of: the identification of the cloud limited device and the first resource link of the cloud limited device;

19. The method of claim 18, wherein the first resource release request message further comprises at least one of: the effective time of the release resource and the indication of the cloud limited device.

20. The method of claim 10, wherein the method further comprises:

and the cloud limited device obtains an access token sent by the configurator.

21. The method of claim 20, wherein the resource requested by the first cloud registration request message is an account resource;

the first cloud registration request message includes at least one of: and the identification of the cloud limited equipment and the access token.

22. The method of claim 12, wherein the resource requested by the first cloud login request message is a session resource;

the first cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification.

23. The method of claim 14, wherein the resource requested by the first update token request message is an update token resource;

The first update token request message includes at least one of: and the cloud limited equipment comprises an identifier, an update token and a user identifier.

24. A resource publishing method, the method comprising:

the cloud proxy device establishes connection with the cloud limited device;

the cloud proxy device transmits information to the cloud limited device based on the connection, and issues resources of the cloud limited device to the cloud device based on the information, wherein endpoints of the resources of the cloud limited device added in a resource catalog of the cloud device are endpoints of the cloud proxy device; wherein the cloud-limited device cannot establish a connection with the cloud device;

the cloud proxy device transmits information based on the connection and the cloud limited device, and issues resources to the cloud device based on the information, and the cloud proxy device comprises:

the cloud proxy device obtains an indication of the cloud limited device based on the connection, and issues resources of the cloud limited device to the cloud device based on the indication.

25. The method of claim 24, wherein the cloud proxy device establishes a connection with a cloud-limited device, comprising:

the cloud proxy device sends information of the cloud proxy device to the cloud limited device, and the information of the cloud proxy device is used for the cloud limited device to establish connection with the cloud proxy device.

26. The method of claim 25, wherein the cloud proxy device sending information of the cloud proxy device to the cloud limited device comprises:

the cloud proxy device receives a discovery request message sent by the cloud limited device in a broadcast or multicast mode; the discovery request message comprises a cloud proxy resource type;

the cloud proxy device sends a discovery response message to the cloud limited device; the discovery response message includes information of the cloud proxy device.

27. The method of claim 25 or 26, wherein the information of the cloud proxy device comprises at least one of: cloud agent resource identification of the cloud agent equipment and endpoint information of the cloud agent resources.

28. The method of claim 24, wherein the cloud proxy device obtains an indication of the cloud limited device based on the connection, and publishing resources to a cloud device based on the indication, comprising:

the cloud proxy device receives a first resource release request message sent by the cloud limited device based on the connection, wherein the first resource release request message is used for indicating the cloud proxy device to release resources to the cloud device;

The cloud proxy device sends a second resource release request message to the cloud device; the resource requested by the second resource release request message is a resource catalog resource; the second resource release request message includes at least one of: the identification of the cloud limited device and the second resource link of the cloud limited device; the end point of the resource in the second resource link of the cloud limited device is the end point of the cloud proxy device;

the cloud proxy device obtains a first resource release response message sent by the cloud device and sends a second resource release response message to the cloud limited device.

29. The method of claim 28, wherein the resource requested by the first resource release request message is a cloud proxy resource; the first resource release request message includes at least one of: the agent issues a resource indication, an identification of the cloud limited device and a first resource link of the cloud limited device; and the endpoints of the resources in the first resource link of the cloud limited device are endpoints of the cloud limited device.

30. The method of claim 29, wherein the first resource release request message further comprises at least one of: issuing effective time of resources and indication of cloud limited equipment;

The second resource release request message further includes at least one of the following: the effective time of the release resource and the indication of the cloud limited device.

31. The method of any of claims 28-30, wherein the target identification in the second resource link of the cloud-limited device comprises an identification of a target resource and an identification of the cloud-limited device.

32. The method of any of claims 28 to 30, wherein before the cloud proxy device receives the first resource release request message sent by the cloud limited device based on the connection, the method further comprises:

the cloud proxy device receives a first cloud registration request message sent by the cloud limited device and sends a second cloud registration request message to the cloud device;

the cloud proxy device receives a first cloud registration response message sent by the cloud device; the first cloud registration response message includes at least one of: the method comprises the steps of user identification, an access token of the cloud limited device, effective duration of the access token and an update token of the cloud limited device;

the cloud proxy device sends a second cloud registration response message to the cloud limited device; the second cloud registration response message includes at least one of: the cloud limited device comprises a user identifier, an access token of the cloud limited device, an effective duration of the access token and an update token of the cloud limited device.

33. The method of claim 32, wherein the resource requested by the first cloud registration request message is a cloud proxy resource; the first cloud registration request message includes at least one of: the cloud end registration indication, the identification of the cloud end limited device and the security credential information of the cloud end limited device are proxied;

34. The method of any of claims 28 to 30, wherein before the cloud proxy device receives the first resource release request message sent by the cloud limited device based on the connection, the method further comprises:

the cloud proxy device receives a first cloud login request message sent by the cloud limited device and sends a second cloud login request message to the cloud device;

the cloud proxy equipment receives a first cloud login response message sent by the cloud equipment; the first cloud login response message comprises the effective time of the access token;

The cloud proxy device sends a second cloud login response message to the cloud limited device; the second cloud login response message includes a valid time for accessing the token.

35. The method of claim 34, wherein the resource requested by the first cloud login request message is a cloud proxy resource; the first cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device and the access token of the cloud limited device are proxied;

36. The method of any one of claims 24 to 26, wherein the method further comprises:

the cloud proxy device receives a first update token request message sent by the cloud limited device and sends a second update token request message to the cloud device;

the cloud agent equipment receives a first update token response message sent by the cloud equipment; the first update token response message includes at least one of: a new access token, an update token, a validity time of the new access token;

The cloud proxy device sends a second update token response message to the cloud limited device; the second update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens.

37. The method of claim 36, wherein the resource requested by the first update token request message is a cloud proxy resource;

the first update token request message includes at least one of: the agent updates the token indication, the identification of the cloud limited equipment, the update token and the user identification;

38. The method of any of claims 24 to 26, wherein before the cloud proxy device receives the first resource release request message sent by the cloud limited device based on the connection, the method further comprises:

the cloud proxy device receives a first device binding request message sent by the cloud limited device; the resource requested by the first equipment binding request message is cloud agent resource;

The cloud proxy device sends a second device binding request message to the cloud device; the resource requested by the second equipment binding request message is a binding resource;

the cloud proxy device receives a first device binding response message sent by the cloud device; the first device binding response message includes a user identification;

the cloud proxy device sends a second device binding response message to the cloud limited device; the second device binding response message includes a user identification.

39. The method of claim 38, wherein the first device binding request message comprises at least one of: the proxy device binds the indication, the identification of the cloud limited device and the security credential of the cloud limited device;

40. The method of claim 28, wherein the resource requested by the first resource release request message is a resource catalog resource; the first resource release request message includes at least one of: the identification of the cloud limited device and the first resource link of the cloud limited device; and the endpoints of the resources in the first resource link of the cloud limited device are endpoints of the cloud limited device.

41. The method of claim 40, wherein the first resource release request message further includes at least one of: the effective time of the release resource and the indication of the cloud limited device.

42. The method of claim 32, wherein the resource requested by the first cloud registration request message is an account resource; the first cloud registration request message includes at least one of: the identification of the cloud limited device and the access token;

43. The method of claim 34, wherein the resource requested by the first cloud login request message is a session resource; the first cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification;

44. The method of claim 36, wherein the resource requested by the first update token request message is an update token resource;

the first update token request message includes at least one of: the identification of the cloud limited equipment, the update token and the user identification;

45. A resource publishing method, the method comprising:

the cloud end equipment obtains resources issued by the cloud end proxy equipment; the resource is a resource of the cloud limited device, which is obtained by the cloud proxy device based on connection with the cloud limited device; wherein the cloud-limited device cannot establish a connection with the cloud device;

the cloud terminal device publishes resources of the cloud terminal limited device, and endpoints of the resources of the cloud terminal limited device are endpoints of the cloud terminal proxy device;

the resource is issued to the cloud end device by the cloud end restricted device based on a connection with the cloud end proxy device.

46. The method of claim 45, wherein the cloud device obtaining the resource published by the cloud proxy device comprises:

the cloud terminal device receives a second resource release request message sent by the cloud terminal proxy device; the resource requested by the second resource release request message is a resource catalog resource; the second resource release request message includes at least one of: the identification of the cloud limited device and the second resource link of the cloud limited device; and the end point of the resource in the second resource link of the cloud limited device is the end point of the cloud proxy device.

47. The method of claim 46, wherein the second resource release request message further includes at least one of: the effective time of the release resource and the indication of the cloud limited device.

48. The method of claim 46 or 47, wherein the target identification in the second resource link of the cloud-limited device comprises an identification of a target resource and an identification of the cloud-limited device.

49. The method of claim 48, wherein the cloud device publishes the resource, comprising:

the cloud device adds the second resource link to a resource catalog; the published endpoints of the resources are endpoints of the cloud device.

50. The method of claim 49, wherein the cloud device adding the second resource link to a resource catalog comprises:

and under the condition that the second resource release request message comprises the indication of the cloud limited equipment, or under the condition that the target identifier in the second resource link of the cloud limited equipment comprises the identifier of the target resource and the identifier of the cloud limited equipment, the identifier of the released target resource is identical to the identifier of the target resource in the second resource link.

51. The method of any one of claims 45 to 47, wherein the method further comprises:

and the cloud end equipment sends a first resource release response message to the cloud end proxy equipment.

52. The method of any one of claims 45 to 47, wherein before the cloud device obtains the resource published by the cloud proxy device, the method further comprises:

the cloud terminal device receives a second cloud terminal registration request message sent by the cloud terminal proxy device;

the cloud end device distributes an access token for the cloud end limited device and associates the cloud end limited device with a user identifier;

the cloud end device sends a first cloud end registration response message to the cloud end proxy device; the first cloud registration response message includes at least one of: the user identification, the access token of the cloud limited device, the effective duration of the access token and the update token of the cloud limited device.

53. The method according to claim 52, wherein the resource requested by the second cloud registration request message is an account resource; the second cloud registration request message includes at least one of: the cloud limited equipment identification, the security credential information of the cloud limited equipment and the user identification;

or the resource requested by the second cloud registration request message is an account resource; the second cloud registration request message includes at least one of: and the identification of the cloud limited equipment and the access token.

54. The method of any one of claims 45 to 47, wherein before the cloud device obtains the resource published by the cloud proxy device, the method further comprises:

the cloud terminal device receives a second cloud terminal login request message sent by the cloud terminal proxy device;

the cloud end device sends a first cloud end login response message to the cloud end proxy device; the first cloud login response message includes a valid time for accessing the token.

55. The method of claim 54, wherein the resource requested by the second cloud login request message is a session resource; the second cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification.

56. The method of any one of claims 45 to 47, wherein the method further comprises:

the cloud end device receives a second update token request message sent by the cloud end proxy device;

the cloud terminal equipment updates the access token and sends a first update token response message to the cloud terminal proxy equipment; the first update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens.

57. The method of claim 56, wherein the resource requested by the second update token request message is an update token resource;

the second update token request message includes at least one of: and the cloud limited equipment comprises an identifier, an update token and a user identifier.

58. The method of any one of claims 45 to 47, wherein before the cloud device obtains the resource published by the cloud proxy device, the method further comprises:

the cloud end device receives a second device binding request message sent by the cloud end proxy device; the resource requested by the second equipment binding request message is a binding resource; the second device binding request message includes at least one of: the identification of the cloud limited equipment, the security credentials and the security identification of the cloud limited equipment;

The cloud end device associates the cloud end limited device and the user identifier and sends a first device binding response message to the cloud end proxy device; the first device binding response message includes a user identification.

59. The method of claim 58, wherein the method further comprises: and the cloud terminal device associates the access tokens of the cloud terminal limited device and the cloud terminal proxy device.

60. A cloud limited device, the device comprising: a first connection establishment unit and a first transmission unit; wherein, the liquid crystal display device comprises a liquid crystal display device,

the first transmission unit is configured to transmit information based on the connection and the cloud proxy device, wherein the information is used for the cloud proxy device to issue resources of the cloud limited device to the cloud device, and endpoints of the resources of the cloud limited device added in a resource catalog of the cloud device are endpoints of the cloud proxy device; wherein the cloud-limited device cannot establish a connection with the cloud device;

the first transmission unit is further configured to instruct the cloud proxy device to issue resources of the cloud limited device to a cloud device based on the connection.

61. The device of claim 60, wherein the first connection establishment unit is configured to obtain information of a cloud proxy device, and establish a connection with the cloud proxy device based on the information.

62. The device of claim 61, wherein the first connection establishment unit is configured to receive configuration information sent by a configurator, and the configuration information includes information of a cloud proxy device.

63. The apparatus of claim 61, wherein the first connection establishment unit is configured to send a discovery request message by broadcasting or multicasting; the discovery request message comprises a cloud proxy resource type; receiving a discovery response message; the discovery response message includes information of the cloud proxy device.

64. The device of any one of claims 61 to 63, wherein the information of the cloud proxy device comprises at least one of: cloud agent resource identification of the cloud agent equipment and endpoint information of the cloud agent resources.

65. The device of claim 60, wherein the first transmission unit is configured to send a first resource release request message to the cloud proxy device, where the first resource release request message is used to instruct the cloud proxy device to release resources to a cloud device.

66. The apparatus of claim 65, wherein the resource requested by the first resource publication request message is a cloud proxy resource;

67. The device of claim 66, wherein the first resource publication request message further includes at least one of: the effective time of the release resource and the indication of the cloud limited device.

68. The device of any one of claims 65 to 67, wherein the first transmission unit is further configured to receive a second resource release response message sent by the cloud proxy device.

69. The device of any one of claims 65 to 67, wherein the first transmission unit is further configured to send a first cloud registration request message to the cloud proxy device before sending a first resource release request message to the cloud proxy device; receiving a second cloud registration response message sent by the cloud proxy device; the second cloud registration response message includes at least one of: the cloud limited device comprises a user identifier, an access token of the cloud limited device, an effective duration of the access token and an update token of the cloud limited device.

70. The device of claim 69, wherein the resource requested by the first cloud registration request message is a cloud proxy resource;

71. The device of any one of claims 65 to 67, wherein the first transmission unit is further configured to send a first cloud login request message to the cloud proxy device before sending a first resource release request message to the cloud proxy device; receiving a second cloud login response message sent by the cloud proxy device; the second cloud login response message includes a valid time for accessing the token.

72. The device of claim 71, wherein the resource requested by the first cloud login request message is a cloud proxy resource;

73. The device of any one of claims 60 to 63, wherein the first transmission unit is further configured to send a first update token request message to the cloud proxy device; receiving a second update token response message sent by the cloud proxy device; the second update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens.

74. The apparatus of claim 73, wherein the resource requested by the first update token request message is a cloud proxy resource; the first update token request message includes at least one of: the agent updates the token indication, the identification of the cloud limited equipment, the update token and the user identification.

75. The device of any one of claims 60 to 63, wherein the first transmission unit is further configured to send a first device binding request message to the cloud proxy device before sending a first resource release request message to the cloud proxy device; the resource requested by the first equipment binding request message is cloud agent resource; and receiving a second device binding response message sent by the cloud proxy device.

76. The device of claim 75, wherein the first device binding request message comprises at least one of: the proxy device binds the indication, the identification of the cloud limited device and the security credential of the cloud limited device;

the second device binding response message includes a user identification.

77. The apparatus of claim 65, wherein the resource requested by the first resource publication request message is a resource catalog resource;

78. The device of claim 77, wherein the first resource publication request message further includes at least one of: the effective time of the release resource and the indication of the cloud limited device.

79. The apparatus of claim 69, wherein the first transmission unit is further configured to obtain an access token sent by a configurator.

80. The device of claim 79, wherein the resource requested by the first cloud registration request message is an account resource;

81. The device of claim 71, wherein the resource requested by the first cloud login request message is a session resource;

82. The apparatus of claim 73, wherein the resource requested by the first update token request message is an update token resource; the first update token request message includes at least one of: and the cloud limited equipment comprises an identifier, an update token and a user identifier.

83. A cloud proxy device, the cloud proxy device comprising: the second connection establishment unit, the second transmission unit and the third transmission unit; wherein, the liquid crystal display device comprises a liquid crystal display device,

the third transmission unit is configured to issue the resources of the cloud limited device to a cloud device based on the information transmitted by the second transmission unit, and an endpoint of the resources of the cloud limited device added in a resource catalog of the cloud device is an endpoint of the cloud proxy device; wherein the cloud-limited device cannot establish a connection with the cloud device;

the second transmission unit is further configured to obtain an indication of the cloud limited device based on the connection;

the third transmission unit is further configured to issue the resource of the cloud limited device to a cloud device based on the indication obtained by the second transmission unit.

84. The device of claim 83, wherein the second connection establishment unit is configured to send information of the cloud proxy device to the cloud limited device, the information of the cloud proxy device being used by the cloud limited device to establish a connection with the cloud proxy device.

85. The device of claim 84, wherein the second connection establishment unit is configured to receive a discovery request message sent by the cloud limited device by broadcasting or multicasting; the discovery request message comprises a cloud proxy resource type; sending a discovery response message to the cloud limited device; the discovery response message includes information of the cloud proxy device.

86. The device of claim 84 or 85, wherein the information of the cloud proxy device comprises at least one of: cloud agent resource identification of the cloud agent equipment and endpoint information of the cloud agent resources.

87. The device of claim 83, wherein the second transmission unit is configured to receive, based on the connection, a first resource release request message sent by the cloud limited device, where the first resource release request message is used to instruct the cloud proxy device to release resources to a cloud device;

The third transmission unit is configured to send a second resource release request message to the cloud device; the resource requested by the second resource release request message is a resource catalog resource; the second resource release request message includes at least one of: the identification of the cloud limited device and the second resource link of the cloud limited device; the end point of the resource in the second resource link of the cloud limited device is the end point of the cloud proxy device; the cloud device is further configured to obtain a first resource release response message sent by the cloud device;

the second transmission unit is further configured to send a second resource release response message to the cloud limited device.

88. The device of claim 87, wherein the resource requested by the first resource publication request message is a cloud proxy resource; the first resource release request message includes at least one of: the agent issues a resource indication, an identification of the cloud limited device and a first resource link of the cloud limited device; and the endpoints of the resources in the first resource link of the cloud limited device are endpoints of the cloud limited device.

89. The device of claim 88, wherein the first resource publication request message further comprises at least one of: issuing effective time of resources and indication of cloud limited equipment;

90. The device of any of claims 87-89, wherein the target identification in the second resource link of the cloud-limited device comprises an identification of a target resource and an identification of the cloud-limited device.

91. The device of any one of claims 87 to 89, wherein the second transmission unit is further configured to receive a first cloud registration request message sent by the cloud limited device before receiving, based on the connection, a first resource release request message sent by the cloud limited device;

the third transmission unit is further configured to send a second cloud registration request message to the cloud device; receiving a first cloud registration response message sent by the cloud device; the first cloud registration response message includes at least one of: the method comprises the steps of user identification, an access token of the cloud limited device, effective duration of the access token and an update token of the cloud limited device;

the second transmission unit is further configured to send a second cloud registration response message to the cloud limited device; the second cloud registration response message includes at least one of: the cloud limited device comprises a user identifier, an access token of the cloud limited device, an effective duration of the access token and an update token of the cloud limited device.

92. The device of claim 91, wherein the resource requested by the first cloud registration request message is a cloud proxy resource; the first cloud registration request message includes at least one of: the cloud end registration indication, the identification of the cloud end limited device and the security credential information of the cloud end limited device are proxied;

93. The device of any one of claims 87 to 89, wherein the second transmission unit is further configured to receive a first cloud login request message sent by the cloud limited device before receiving, based on the connection, the first resource release request message sent by the cloud limited device;

the third transmission unit is further configured to send a second cloud login request message to the cloud device; receiving a first cloud login response message sent by the cloud device; the first cloud login response message comprises the effective time of the access token;

The second transmission unit is further configured to send a second cloud login response message to the cloud limited device; the second cloud login response message includes a valid time for accessing the token.

94. The device of claim 93, wherein the resource requested by the first cloud login request message is a cloud proxy resource; the first cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device and the access token of the cloud limited device are proxied;

95. The device of any one of claims 83 to 85, wherein the second transmission unit is further configured to receive a first update token request message sent by the cloud limited device;

the third transmission unit is further configured to send a second update token request message to the cloud device; receiving a first update token response message sent by the cloud device; the first update token response message includes at least one of: a new access token, an update token, a validity time of the new access token;

The second transmission unit is further configured to send a second update token response message to the cloud limited device; the second update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens.

96. The device of claim 95, wherein the resource requested by the first update token request message is a cloud proxy resource; the first update token request message includes at least one of: the agent updates the token indication, the identification of the cloud limited equipment, the update token and the user identification;

97. The device of any one of claims 83 to 85, wherein the second transmission unit is further configured to receive a first device binding request message sent by the cloud limited device before receiving, based on the connection, the first resource release request message sent by the cloud limited device; the resource requested by the first equipment binding request message is cloud agent resource;

The third transmission unit is further configured to send a second device binding request message to the cloud device; the resource requested by the second equipment binding request message is a binding resource; receiving a first device binding response message sent by the cloud device; the first device binding response message includes a user identification;

the second transmission unit is further configured to send a second device binding response message to the cloud limited device; the second device binding response message includes a user identification.

98. The device of claim 97, wherein the first device binding request message comprises at least one of: the proxy device binds the indication, the identification of the cloud limited device and the security credential of the cloud limited device;

99. The device of claim 87, wherein the resource requested by the first resource publication request message is a resource catalog resource; the first resource release request message includes at least one of: the identification of the cloud limited device and the first resource link of the cloud limited device; and the endpoints of the resources in the first resource link of the cloud limited device are endpoints of the cloud limited device.

100. The device of claim 99, wherein the first resource publication request message further comprises at least one of: the effective time of the release resource and the indication of the cloud limited device.

101. The device of claim 91, wherein the resource requested by the first cloud registration request message is an account resource; the first cloud registration request message includes at least one of: the identification of the cloud limited device and the access token;

102. The device of claim 93, wherein the resource requested by the first cloud login request message is a session resource; the first cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification;

103. The apparatus of claim 95, wherein the resource requested by the first update token request message is an update token resource; the first update token request message includes at least one of: the identification of the cloud limited equipment, the update token and the user identification;

104. The cloud device comprises a fourth transmission unit and a publishing unit; wherein, the liquid crystal display device comprises a liquid crystal display device,

the fourth transmission unit is configured to obtain resources issued by the cloud agent equipment; the resource is a resource of the cloud limited device, which is obtained by the cloud proxy device based on connection with the cloud limited device; wherein the cloud-limited device cannot establish a connection with the cloud device;

the publishing unit is configured to publish resources of the cloud-side limited device, wherein endpoints of the resources of the cloud-side limited device are endpoints of the cloud-side proxy device; the resource is issued to the cloud end device by the cloud end restricted device based on a connection with the cloud end proxy device.

105. The device of claim 104, wherein the fourth transmission unit is configured to receive a second resource release request message sent by the cloud proxy device; the resource requested by the second resource release request message is a resource catalog resource; the second resource release request message includes at least one of: the identification of the cloud limited device and the second resource link of the cloud limited device; and the end point of the resource in the second resource link of the cloud limited device is the end point of the cloud proxy device.

106. The device of claim 105, wherein the second resource publication request message further includes at least one of: the effective time of the release resource and the indication of the cloud limited device.

107. The device of claim 105 or 106, wherein the target identification in the second resource link of the cloud-limited device includes an identification of a target resource and an identification of the cloud-limited device.

108. The device of any one of claims 104 to 106, wherein the publication unit is configured to add the second resource link to a resource catalog; the published endpoints of the resources are endpoints of the cloud device.

109. The device of claim 108, wherein the publication unit is further configured to, in a case where the indication of the cloud limited device is included in the second resource publication request message, or in a case where the target identifier in the second resource link of the cloud limited device includes an identifier of a target resource and an identifier of the cloud limited device, publish the same identifier as the target resource in the second resource link.

110. The device of any one of claims 104 to 106, wherein the fourth transmission unit is further configured to send a first resource release response message to the cloud proxy device.

111. The device of any one of claims 104 to 106, wherein the device further comprises a registration unit;

the fourth transmission unit is further configured to receive a second cloud registration request message sent by the cloud proxy device before obtaining the resource issued by the cloud proxy device;

the registration unit is configured to allocate an access token for the cloud limited device and associate the cloud limited device with a user identifier;

the fourth transmission unit is further configured to send a first cloud registration response message to the cloud proxy device; the first cloud registration response message includes at least one of: the user identification, the access token of the cloud limited device, the effective duration of the access token and the update token of the cloud limited device.

112. The device of claim 111, wherein the resource requested by the second cloud registration request message is an account resource; the second cloud registration request message includes at least one of: the cloud limited equipment identification, the security credential information of the cloud limited equipment and the user identification;

113. The device of any one of claims 104 to 106, wherein the fourth transmission unit is further configured to receive a second cloud login request message sent by the cloud proxy device before obtaining the resource published by the cloud proxy device; sending a first cloud login response message to the cloud proxy device; the first cloud login response message includes a valid time for accessing the token.

114. The device of claim 113, wherein the resource requested by the second cloud login request message is a session resource; the second cloud login request message includes at least one of the following: the cloud login indication, the identification of the cloud limited device, the access token of the cloud limited device and the user identification.

115. The device of any one of claims 104 to 106, wherein the device further comprises an update unit;

the fourth transmission unit is further configured to receive a second update token request message sent by the cloud proxy device;

the updating unit is configured to update a new access token;

the fourth transmission unit is further configured to send a first update token response message to the cloud proxy device; the first update token response message includes at least one of: new access tokens, update tokens, validity times of said new access tokens.

116. The device of claim 115, wherein the resource requested by the second update token request message is an update token resource; the second update token request message includes at least one of: and the cloud limited equipment comprises an identifier, an update token and a user identifier.

117. The device of any one of claims 104 to 106, wherein the device further comprises a binding unit;

the fourth transmission unit is further configured to receive a second device binding request message sent by the cloud proxy device before obtaining the resource issued by the cloud proxy device; the resource requested by the second equipment binding request message is a binding resource; the second device binding request message includes at least one of: the identification of the cloud limited equipment, the security credentials and the security identification of the cloud limited equipment;

The binding unit is configured to associate the cloud limited equipment with a user identifier;

the fourth transmission unit is further configured to send a first device binding response message to the cloud proxy device; the first device binding response message includes a user identification.

118. The device of claim 117, wherein the binding unit is further configured to associate access tokens of the cloud limited device and the cloud proxy device.

119. An apparatus, comprising: a processor and a memory for storing a computer program, the processor for invoking and running the computer program stored in the memory, performing the method of any of claims 1 to 23; alternatively, performing the method of any one of claims 24 to 44; alternatively, a method as claimed in any one of claims 45 to 59 is performed.

120. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 23; alternatively, a device on which the chip is mounted is caused to perform the method of any one of claims 24 to 44; causing a device on which the chip is mounted to perform the method of any one of claims 45 to 59.

121. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 23; alternatively, the computer program causes a computer to perform the method of any one of claims 24 to 44; alternatively, the computer program causes a computer to perform the method of any one of claims 45 to 59.