CN113454966A

CN113454966A - Method and device for generating shadow device and storage medium

Info

Publication number: CN113454966A
Application number: CN201980092672.0A
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: 2021-09-28
Anticipated expiration: 2039-07-24
Also published as: CN113454966B; WO2021012235A1

Abstract

The invention discloses a method for generating shadow equipment, which comprises the following steps: the cloud agent equipment receives a first request message; and the cloud proxy equipment generates first shadow equipment of the server equipment based on the first request message. The cloud server receives a second request message; and the cloud server generates a second shadow device for the first shadow device of the server device based on the second request message. The invention also discloses another generation method, equipment and storage medium of the shadow equipment.

Description

Method and device for generating shadow device and storage medium

Technical Field

The present invention relates to the field of information processing technologies, and in particular, to a method and an apparatus for generating a shadow device, and a storage medium.

Background

In the related art, a shadow device is generated for an Open Connectivity Foundation (OCF) server device, and remote communication is performed between the shadow device and an OCF client device, so as to improve communication processing efficiency. At this time, the OCF server device is required to have the capability of establishing and maintaining a long Transport Layer (TLS) connection with the cloud server. However, for OCF server-side devices (also referred to as cloud-limited devices) that do not have the capability to establish and maintain TLS long connections with a cloud server, shadow devices cannot be generated on the cloud server.

Disclosure of Invention

In order to solve the foregoing technical problem, embodiments of the present invention provide a method, a device, and a storage medium for generating a shadow device, which can generate a shadow device on a cloud server for a cloud-limited device.

In a first aspect, an embodiment of the present invention provides a method for generating a shadow device, including: the cloud agent equipment receives a first request message; and the cloud proxy equipment generates first shadow equipment of the server equipment based on the first request message.

In a second aspect, an embodiment of the present invention provides a method for generating a shadow device, including: the method comprises the steps that server-side equipment sends a first request message to cloud-side proxy equipment, wherein the first request message is used for requesting the cloud-side proxy equipment to generate first shadow equipment of the server-side equipment; the server side equipment receives a first request response message.

In a third aspect, an embodiment of the present invention provides a method for generating a shadow device, including: the cloud server receives a second request message; and the cloud server generates a second shadow device for the first shadow device of the server device based on the second request message.

In a fourth aspect, an embodiment of the present invention provides a method for generating a shadow device, including: the method comprises the steps that a configurator sends a first request message to cloud proxy equipment, wherein the first request message is used for requesting the cloud proxy equipment to generate first shadow equipment of server-side equipment; the configurator receives a first request response message.

In a fifth aspect, an embodiment of the present invention provides a cloud proxy device, where the cloud proxy device includes:

a first receiving unit configured to receive a first request message;

and the first processing unit is configured to generate a first shadow device of the server device based on the first request message.

In a sixth aspect, an embodiment of the present invention provides a server device, where the server device includes:

a sixth sending unit, configured to send a first request message to a cloud proxy device, where the first request message is used to request the cloud proxy device to generate a first shadow device of the server device;

a second receiving unit configured to receive the first request response message.

In a seventh aspect, an embodiment of the present invention provides a cloud server, where the cloud server includes:

a third receiving unit configured to receive the second request message;

and the fourth processing unit is configured to generate a second shadow device for the first shadow device of the server device based on the second request message.

In an eighth aspect, an embodiment of the present invention provides a configurator, which includes:

an eighth sending unit, configured to send a first request message to a cloud proxy device, where the first request message is used to request the cloud proxy device to generate a first shadow device of a server device;

a fourth receiving unit configured to receive the first request response message.

In a ninth aspect, an embodiment of the present invention provides a cloud proxy device, including a processor and a memory, where the memory is used for storing a computer program that can be run on the processor, and when the processor is used for running the computer program, the method for generating a shadow device executed by the cloud proxy device is executed.

In a tenth aspect, an embodiment of the present invention provides a server device, including a processor and a memory, where the memory is used for storing a computer program that can be run on the processor, and when the processor is used for running the computer program, the server device executes the steps of the shadow device generation method executed by the server device.

In an eleventh aspect, an embodiment of the present invention provides a cloud server, including a processor and a memory, where the memory is used for storing a computer program capable of being executed on the processor, and the processor is configured to, when the computer program is executed, execute the steps of the shadow device generation method executed by the cloud server.

In a twelfth aspect, an embodiment of the present invention provides a configurator, which includes a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the steps of the method for generating a shadow device executed by the configurator when running the computer program.

In a thirteenth aspect, an embodiment of the present invention provides a storage medium, where an executable program is stored, and when the executable program is executed by a processor, the method for generating a shadow device executed by a cloud proxy device is implemented.

In a fourteenth aspect, an embodiment of the present invention provides a storage medium, which stores an executable program, and when the executable program is executed by a processor, the storage medium implements a method for generating a shadow device executed by the server device.

In a fifteenth aspect, an embodiment of the present invention provides a storage medium, which stores an executable program, and when the executable program is executed by a processor, the storage medium implements the method for generating a shadow device executed by a cloud server.

In a sixteenth aspect, an embodiment of the present invention provides a storage medium, which stores an executable program, and when the executable program is executed by a processor, the storage medium implements the method for generating a shadow device executed by the configurator.

The method for generating the shadow device provided by the embodiment of the invention comprises the following steps: the cloud agent equipment receives a first request message; and the cloud proxy equipment generates first shadow equipment of the server equipment based on the first request message. The cloud server receives a second request message; and the cloud server generates a second shadow device for the first shadow device of the server device based on the second request message. Therefore, the server side equipment without the capability of directly accessing the cloud server can generate shadow equipment on the cloud proxy equipment and the cloud server. Moreover, the resource synchronization between the server device and the first shadow device and between the first shadow device and the second shadow device enables the client device to communicate with the first shadow device or the second shadow device, and further improves the communication efficiency of the server device.

Drawings

FIG. 1 is a schematic flow chart of communication between a client device and a server device according to the present invention;

FIG. 2 is a schematic flow chart illustrating the creation of a shadow device for a server device and the synchronization of the server device and the shadow device according to the present invention;

fig. 3 is a schematic view of an optional processing flow of a generation method of a shadow device applied to a cloud proxy device according to an embodiment of the present invention;

FIG. 4 is a schematic diagram illustrating an optional processing flow of a method for generating a shadow device applied to a server device according to an embodiment of the present invention;

FIG. 5 is a schematic view of an alternative processing flow of a generation method of a shadow device applied to a cloud server according to an embodiment of the present invention;

FIG. 6 is a schematic diagram illustrating an alternative processing flow of a generation method of a shadow device applied to a configurator according to an embodiment of the present invention;

FIG. 7 is a detailed processing flow diagram of a shadow device generation method according to an embodiment of the present invention;

FIG. 8 is a flowchart illustrating a detailed process of another shadow device generation method according to an embodiment of the present invention;

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

FIG. 10 is a schematic diagram of a component structure of a server device according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a cloud server according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of a configurator according to an embodiment of the present invention;

fig. 13 is a schematic diagram of a hardware component structure of an electronic device according to an embodiment of the present invention.

Detailed Description

So that the manner in which the features and technical contents of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the present invention will be rendered by reference to the appended drawings, which are included for purposes of illustration and not limitation.

Before describing the shadow device generating method provided by the embodiment of the present invention in detail, terms related to the embodiment of the present invention are briefly described.

1) The configurator is a tool for providing a cloud server access configuration function for the server-side equipment, and the function of the configurator can be realized by application software.

2) And the resource link represents the reference relation between the OCF resources.

3) And the endpoints are the source ends or the destination ends of the request messages and the response messages.

4) And the server side equipment is an OCF server.

5) The shadow device is a digital twin device generated by the server device, and other devices can directly communicate with the shadow device, so that the workload of message processing on the server device is reduced, and the communication efficiency of the system is improved.

6) And the resource directory supports the OCF equipment to issue resources and discover the logical functional entities of the resources.

The OCF device and the communication between the OCF devices will be briefly described.

The OCF is a new technical standard organization of an application layer of the Internet of things, and establishes a Restful service framework for interconnection and intercommunication among the Internet of things equipment; in the OCF Restful service framework, information such as Internet of things equipment, functional services of the OCF equipment, the state of the OCF equipment and the like is expressed through resources. The entity providing the resource is an OCF server device (hereinafter referred to as a server device), and the entity accessing the resource is an OCF client (hereinafter referred to as a client device).

For example, the control terminal that acquires the indoor environment status data is a client device, the sensor device that monitors the indoor environment status data is a server device, and the service interaction between the client device and the server device is realized by resource operation methods such as creation, reading, updating, deletion, or notification of resources.

The flow of communication between the client device and the server device is as shown in fig. 1: the client device sends an update resource request for a resource on the server device to the server device. The server side equipment executes corresponding resource operation according to the resource updating request and sends a resource updating response to the client side equipment; wherein the update resource response carries an expression of the resource.

In an alternative embodiment, the resource update request is in the form of:

accordingly, the update resource response is in the form of:

here, the Resource update request carries a Uniform Resource Identifier (URI) of the Resource and a Resource operation method; taking fig. 1 as an example, the server device has an environment temperature resource, and the URI of the resource is "/environment temperature"; the resource operation method requested by the client device from the server device is an update method POST.

The representation of the resource includes: URI of resource, resource type, resource interface, and functional attribute of resource, etc., information included in the expression of resource is described below:

the resource URI is expressed by 'href' in the resource expression, provides the address of the OCF server equipment resource, the value of 'href' is the specific resource URI, and the OCF client equipment accesses the resource of the OCF server equipment through the resource URI; in FIG. 1, the URI of the ambient temperature resource is "/environmental temperature".

The resource type, which is denoted by "rt" in the expression of the resource, indicates the type of the resource, and the resource type "rt" in fig. 1 is "oic.r. temperature" and indicates the temperature resource type.

The resource interface, denoted in the representation of the resource by "if", provides a view of the resource and a response to the resource support, is "oic.

The resource attribute describes attribute information of the resource in the expression of the resource, and in fig. 1, "targetTemperature" indicates a target temperature attribute of the temperature resource, "currentTemperature" indicates a current temperature attribute of the temperature resource, and "tempreturarge" indicates a temperature range attribute of the temperature resource.

The OCF defines a resource discovery resource "/oic/res" which all OCF devices must support, wherein the resource discovery resource is used for discovering the OCF devices and resources; the resource discovery resource provides a function of device resource discovery, and the URI of the resource discovery resource is fixed to "/oic/res".

In order to express the incidence relation among the resources, the OCF defines the resource link, namely the resource Links; the OCF server-side equipment can provide own resources in a resource link mode, and the OCF client-side equipment can conveniently discover the resources of the OCF server-side equipment. The content of the resource link is as follows:

the content of the resource link includes:

anchor, a context URI, represents the URI of the owner resource that contains the resource link.

href target URI, the URI of the target resource referenced in the resource link.

rt, resource type identification of the target resource.

if is the interface supported by the target resource.

eps-an endpoint that can access a target resource.

Because the OCF standard Protocol uses a restricted Application Protocol (CoAP) to carry OCF messages in the transport layer, each OCF server device needs to have an endpoint, and each OCF device must associate with at least one endpoint for sending and receiving messages; the client device may access a target resource of the server device 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 'ep', namely the target resource can be accessed through the address of the value 'ep' in the 'eps' parameter. For example, in the resource linking example above, the client device may access the target resource/myLightSwitch "through the message endpoint" maps:// [2001: db8: b:: c2e5]:22222 ".

For some specific scenarios, such as IoT devices that do not need to update state frequently, the client device may improve system communication efficiency by communicating with the shadow device of the server device. The OCF cloud server realizes shadow service, the shadow service of the OCF cloud service creates a shadow device for each OCF server device, and the shadow device can directly respond to the request of the client device without acquiring the resource expression of the server device; by the method, the client device can obtain the resource expression of the server device without communicating with the server device, so that the workload of message processing on the server device is reduced, and the communication efficiency of the system is improved.

In the related art, creating a shadow device for a server device, and a synchronization process of the server device and the shadow device is shown in fig. 2, and includes the following steps:

1. the configurator configures the server side equipment: the configurator executes a shadow configuration process for the server equipment, sends a resource updating request to a shadow configuration resource of the server equipment and provides shadow service information for the server equipment to generate the shadow equipment; wherein. The shadow service information includes: shadow service identification, URI of shadow generation resource and indication of generating shadow equipment; wherein the shadow service identifier represents identification information of the shadow service, the URI of the shadow generation resource provides a URI for accessing the shadow generation resource "oic.

2. Generating a shadow device for the server device: obtaining shadow service information by the server-side equipment in the step 1, wherein the shadow service information comprises a URI of a shadow generation resource, sending a request for creating the shadow equipment to a cloud server by the server-side equipment aiming at the URI of the shadow generation resource, and providing original resource information needing to be copied in the request; after receiving a request of the server-side equipment, the cloud server generates shadow equipment for the server-side equipment; wherein the shadow device includes replicated resource information corresponding to the original resource information.

3. The configurator configures the shadow device: the configurator performs a configuration process for the shadow device, which obtains access control information.

4. The cloud server receives the resource updating request: the cloud server receives an update request of a client device for the copied resources on the shadow device.

5. The shadow device and the server device synchronize resources: the server device and the shadow device establish a synchronization relationship through the shadow synchronization resource, and the server device and the shadow device perform information synchronization.

6. The shadow device sends a synchronization message to the client device.

In executing the flow shown in fig. 2, the server device is required to have the capability of establishing and maintaining a TLS long connection with the cloud server, that is, the server device has the capability of directly accessing the cloud server. However, for a server device without the capability of directly accessing the cloud server, a shadow device cannot be generated on the cloud server; therefore, the communication processing efficiency cannot be improved by the characteristics of the shadow device.

Based on the above problem, the present invention provides a method for generating a shadow device, and an optional processing flow of the method for generating a shadow device applied to a cloud proxy device provided in the embodiment of the present invention is shown in fig. 3, and includes the following steps:

in step S201, the cloud proxy device receives a first request message.

Step S202, the cloud proxy device generates a first shadow device of the server device based on the first request message.

In the first embodiment, before performing step S201, the method further includes:

in step S200a, the cloud proxy device receives the first resource discovery request message sent by the configurator.

The first resource discovery request message indicates the resource type of the cloud proxy equipment; for example, the resource type of the cloud proxy device is oic.

In step S200b, the cloud proxy device sends a first resource discovery request response message to the configurator.

Wherein the first resource discovery request response message includes: resource linking of the cloud proxy device; the resource link of the cloud proxy device comprises at least one of the following items: the resource type of the cloud agent device and the endpoint of the resource of the cloud agent device. Optionally, the resource link of the cloud proxy device may further include a URI of the cloud proxy device resource. For example, the resource type of the cloud proxy device is oic.r.cloudproxy, the URI of the cloud proxy device resource is/oic/cloudproxy, and the endpoint of the cloud proxy resource is maps:// [ fe80::2]: 3333.

In step S200c, the cloud proxy device receives a request message for obtaining shadow service information sent by the configurator.

In step S200d, the cloud proxy device sends a request response message for obtaining shadow service information to the configurator.

Wherein the request response message for obtaining shadow service information includes at least one of the following: an identification of the shadow service and an endpoint of the shadow service.

For step S201, the cloud proxy device receives a first request message sent by the configurator. Before the cloud proxy device receives the first request message sent by the configurator, the method further includes:

the cloud proxy equipment receives shadow service information of the cloud proxy equipment sent by the configurator.

In specific implementation, the configurator sends an update request message to the cloud proxy device for the shadow configuration resource of the server device. Wherein, the shadow configuration resource of the server device is: oil/shadow/conf; the shadow service information of the cloud proxy device comprises at least one of the following items: and the identifier of the shadow service on the cloud proxy equipment and the endpoint of the shadow service. Optionally, the shadow service information of the cloud proxy device may further include: an original resource link which needs to be copied to the cloud proxy equipment; the original resource link refers to a resource link of the server device.

Aiming at the step S202, the cloud proxy equipment generates first shadow equipment for the server equipment; in specific implementation, a shadow service in the cloud proxy device generates a first shadow device for the server device.

The URL of the copied resource of the first shadow device comprises a device identification of the server device.

Optionally, the description information of the first shadow device includes second indication information, where the second indication information is used to indicate that the first shadow device does not have a capability of directly accessing a cloud server. In specific implementation, the first shadow device does not have the capability of directly accessing the cloud server, and may be characterized by a device type in the description information of the first shadow device.

After performing step S202, the method further includes:

in step S203, the cloud proxy device sends a first request response message to the configurator.

Wherein the first request response message comprises: a resource link of the first shadow device; the resource link of the first shadow device may include at least one of: an identification of the first shadow device and an endpoint of the first shadow device.

Optionally, the first request response message further includes third indication information, where the third indication information is used to indicate that the first shadow device does not have a capability of directly accessing a cloud server. In specific implementation, the first shadow device does not have the capability of directly accessing the cloud server, and may be characterized by a device type in the description information of the first shadow device.

After step S203 is executed, and the cloud server generates a second shadow device for the first shadow device, the method further includes:

step S204, the cloud proxy device associates the first shadow device with the second shadow device.

In specific implementation, the cloud proxy equipment receives an update request message aiming at the shadow configuration resource, which is sent by a configurator; wherein, the shadow configuration resource is: and/oic/shadow/conf. The update request message for the shadow configuration resource includes at least one of: the identifier of the second shadow device, the endpoint of the second shadow device, and the shadow synchronization resource of the second shadow device; optionally, the update request message for the shadow configuration resource may further include a shadow service identifier of the cloud server. For example, the update request message for the shadow configuration resource includes: the identity of the second shadow device, the endpoint of the second shadow device, and the shadow synchronization resource of the second shadow device. Alternatively, the update request message for the shadow configuration resource may further include a shadow service identifier of the cloud server. For example, the update request message for the shadow configuration resource includes: the identifier of the second shadow device, the endpoint of the second shadow device, the shadow synchronization resource of the second shadow device, and the shadow service identifier of the cloud server.

After performing step S204, the method further includes:

in step S205, the configurator starts resource synchronization between the first shadow device and the second shadow device, and resource synchronization between the first shadow device and the server device.

In step S206, the cloud proxy device receives the resource synchronization request sent by the cloud server.

The target resource in the resource synchronization request is a shadow synchronization resource/oic/shadow/sync, the device identifier is a device identifier of a second shadow device, and the URI of the resource comprises the device identifier of the server device.

Step S207, the cloud proxy device sends a resource synchronization request to the server device.

Wherein, the target resource in the resource synchronization request is a shadow synchronization resource/oic/shadow/sync; the device identifier in the resource synchronization request is the device identifier of the first shadow device; and the URI of the resource in the resource synchronization request does not comprise the equipment identification of the server-side equipment.

Step S208, the cloud proxy device receives the synchronization result sent by the server device, and sends the synchronization result to the cloud server.

In the second embodiment, before performing step S201, the method further includes:

in step S200 a', the cloud proxy device receives the first resource discovery request message sent by the server device.

In step S200 b', the cloud proxy device sends a first resource discovery request response message to the server device.

In step S200 c', the cloud proxy device receives a request message for obtaining shadow service information sent by the server device.

In step S200 d', the cloud proxy device sends a request response message for obtaining shadow service information to the server device.

The description of step S202 in the second embodiment is the same as the description of step S202 in the first embodiment, and is not repeated here.

After performing step S202, the method further includes:

in step S203', the cloud proxy device sends a first request response message to the server device.

It should be noted that the description of the first request response message in step S203' is the same as the description of the first request response message in step S203, and is not repeated here.

After step S203', the method further comprises:

the cloud proxy device sends a second request message to the cloud server, wherein the second request message is used for requesting the cloud server to generate a second shadow device for the first shadow device. Wherein the second request message comprises at least one of: a shadow synchronization resource of the first shadow device, a replicated resource link of the first shadow device, and an endpoint of the first shadow device. Optionally, the second request message includes fourth indication information, where the fourth indication information is used to indicate that the server device does not have a capability of directly accessing the cloud server. In specific implementation, the server device does not have the capability of directly accessing the cloud server, and can be characterized by the device type in the description information of the server device.

Correspondingly, the method further comprises the following steps: the cloud proxy equipment receives a second request response message sent by the cloud server; the second request response message includes: a resource link of the second shadow device. Wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device. Optionally, the second request response message further includes fifth indication information, where the fifth indication information is used to indicate that the second shadow device does not have a capability of directly accessing a cloud server. In specific implementation, the second shadow device does not have the capability of directly accessing the cloud server, and may be characterized by the device type in the description information of the second shadow device.

After the cloud server generates the second shadow device for the first shadow device, the method further includes:

in step S204', the cloud proxy device associates the first shadow device with the second shadow device.

During specific implementation, a first shadow device on the cloud proxy device updates own shadow configuration resource/oic/shadow/conf, and configures an identifier of a second shadow device on the cloud server, an endpoint of the second shadow device and a shadow synchronization resource/oic/shadow/sync of the second shadow device for the first shadow device; optionally, the first shadow device on the cloud proxy device may also configure a shadow service identifier on the cloud server for itself.

In step S205', the cloud proxy device starts resource synchronization between the first shadow device and the server device, and resource synchronization between the cloud proxy device and the second shadow device.

After step S205' is performed, steps S206 to S208 in the above-described first embodiment are performed.

As shown in fig. 4, the optional processing flow of the method for generating a shadow device applied to a server device according to the embodiment of the present invention includes:

step S301, a server device sends a first request message to a cloud proxy device, where the first request message is used to request the cloud proxy device to generate a first shadow device of the server device.

It should be noted that, in the embodiment of the present invention, the description of the first request message is the same as the description of the first request message in step S201, and is not repeated here.

Step S302, the server device receives the first request response message.

In specific implementation, the server device receives a first request response message sent by the cloud proxy device. In the embodiment of the present invention, the description of the first request response message in step S203 is the same as that described above, and details are not repeated here.

After performing step S302, the method further includes:

step S303, the server device associates itself with the first shadow device.

In specific implementation, the server device configures at least one of the following for itself by updating its shadow configuration resource: the identifier of the first shadow device, the endpoint of the first shadow device, and the shadow synchronization resource of the first shadow device.

For example, the server device updates its shadow configuration resource/oic/shadow/conf, and configures at least one of an identifier of the shadow device on the cloud proxy device, an endpoint of the shadow device, and a shadow synchronization resource/oic/shadow/sync of the shadow device for itself.

After performing step S303, the method further includes:

step S304, the server device starts resource synchronization between the server device and the first shadow device.

In step S305, the server device receives a resource synchronization request sent by the cloud agent device.

It should be noted that, the description of the resource synchronization request in the embodiment of the present invention is the same as the description of the resource synchronization request in step S207, and is not repeated here.

In this embodiment of the present invention, before performing step S301, the method further includes:

in step S300 a', the server device sends a first resource discovery request message to the cloud proxy device.

It should be noted that, in the embodiment of the present invention, the description of the first resource discovery request message is the same as the description of the first resource discovery request message in step S200 a', and is not repeated here.

In step S300 b', the server device receives the first resource discovery request response message sent by the cloud proxy device.

It should be noted that, in the embodiment of the present invention, the description of the first resource discovery request response message is the same as the description of the first resource discovery request response message in step S200 b', and is not repeated here.

In step S300 c', the server device sends a request message for obtaining shadow service information to the cloud proxy device.

In step S300 d', the server device receives a request response message for obtaining shadow service information sent by the cloud proxy device.

It should be noted that, in the embodiment of the present invention, the description of the request response message for obtaining shadow service information is the same as the description of the request response message for obtaining shadow service information in step S300 d', and is not repeated here.

As shown in fig. 5, an optional processing flow of the generation method of the shadow device applied to the cloud server provided in the embodiment of the present invention includes:

in step S401, the cloud server receives the second request message.

Step S402, the cloud server generates a second shadow device for the first shadow device of the server device based on the second request message.

In the first embodiment, for step S401, the cloud server receives the second request message sent by the configurator.

In a second embodiment, for step S401, the cloud server receives a second request message sent by the cloud proxy device.

In an embodiment of the present invention, the second request message includes at least one of the following: a shadow synchronization resource of the first shadow device, a replicated resource link of the first shadow device, and an endpoint of the first shadow device. Optionally, the second request message includes fourth indication information, where the fourth indication information is used to indicate that the server device does not have a capability of directly accessing the cloud server. In specific implementation, the capability that the server device does not directly access the cloud server can be characterized by the device type in the description information of the cloud server.

For step S402, the URI of the replicated resource of the second shadow device remains unchanged, that is, the target URI of the second shadow device is not added with the device identifier of the cloud proxy device.

After performing step S402, the method further includes:

step S403, the cloud server sends a second request response message; the second request response message includes: a resource link of the second shadow device.

Wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device. Optionally, the second request response message further includes fifth indication information, where the fifth indication information is used to indicate that the second shadow device does not have a capability of directly accessing a cloud server. Optionally, the capability of the second shadow device not having direct access to the cloud server may be characterized by a device type of the second shadow device.

In step S404, the cloud server starts resource synchronization between the second shadow device and the first shadow device.

In step S405, the cloud server issues the copied resource link of the second shadow device to a resource discovery directory of the cloud server.

In specific implementation, step S405 may be executed after step S402, and there is no execution sequence between step S405 and step S403, and there is no execution sequence between step S405 and step S404.

As shown in fig. 6, an optional processing flow of the generation method of the shadow device applied to the configurator according to the embodiment of the present invention includes:

step S501, a configurator sends a first request message to a cloud proxy device, where the first request message is used to request the cloud proxy device to generate a first shadow device of a server device.

Step S502, the configurator receives a first request response message.

In specific implementation, the configurator receives a first request response message sent by the cloud agent device. In the embodiment of the present invention, the description of the first request response message in step S203 is the same as that described above, and details are not repeated here.

And the configurator receives the first request response message and associates the server side equipment with the first shadow equipment on the cloud proxy equipment. During specific implementation, the configurator sends an update request message to the shadow configuration resource/oic/shadow/conf of the server device; the update request message includes at least one of the following: the cloud proxy device comprises an identification of a first shadow device on the cloud proxy device, an endpoint of the first shadow device, and a shadow synchronization resource/oic/shadow/sync of the first shadow device.

After performing step S502, the method further includes:

step S503, the configurator sends a second request message to the cloud server, where the second request message is used to request the cloud server to generate a second shadow device for the first shadow device.

It should be noted that, in the embodiment of the present invention, the description of the second request message is the same as the description of the second request message in step S401, and is not repeated here.

Step S504, the configurator receives a second request response message sent by the cloud server.

It should be noted that, in the embodiment of the present invention, the description of the second request response message is the same as the description of the second request response message in step S402, and is not repeated here.

In step S505, the configurator associates the first shadow device and the second shadow device.

In specific implementation, the configurator sends an update request message aiming at the shadow configuration resource to the cloud proxy equipment; the update request message for the shadow configuration resource includes at least one of: the identifier of the second shadow device, the endpoint of the second shadow device, the shadow synchronization resource of the second shadow device, and the shadow service identifier of the cloud server.

Wherein, the shadow configuration resource is/oic/shadow/conf, and the shadow synchronization resource is/oic/shadow/sync.

Step S506, the configurator configures resource synchronization between the first shadow device and the second shadow device, and resource synchronization between the first shadow device and the server device.

Before performing step S501, the method further includes:

step S500a, the configurator sends a second resource discovery request message to the server device.

In step S500b, the configurator receives the second resource discovery request response message sent by the server device.

It should be noted that, in the embodiment of the present invention, descriptions for the second resource discovery request message and the second resource discovery request response message are the same as the descriptions for the second resource discovery request message and the second resource discovery request response message in the foregoing embodiment, and are not described herein again.

In step S500c, the configurator sends a first resource discovery request message to the cloud proxy device.

In step S500d, the configurator receives a first resource discovery request response message sent by the cloud agent device.

In step S500e, the configurator sends a request message for obtaining shadow service information to the cloud proxy device.

It should be noted that, in the embodiment of the present invention, the description of the request message for obtaining shadow service information is the same as the description of the request message for obtaining shadow service information in step S200 c', and is not repeated here.

In step S500f, the configurator receives a request response message for obtaining shadow service information sent by the cloud proxy device.

It should be noted that, in the embodiment of the present invention, the description of the request response message for obtaining shadow service information is the same as the description of the request response message for obtaining shadow service information in step S200 d', and is not repeated here.

As shown in fig. 7, the detailed processing flow of the method for generating a shadow device according to the embodiment of the present invention includes that a configurator controls generation of the shadow device, including the following steps:

step S601, the configurator discovers the server device.

In specific implementation, the configurator sends a resource discovery request to the server-side device; the server device resource type is specified in the request message. For example, the resource type of the server device is oic.

Step S602, the server device sends a response for discovering the server device to the configurator.

In specific implementation, discovering that the response of the server-side equipment carries the resource link of the server-side equipment; the resource link of the server side equipment comprises at least one of the following items: the server equipment resource type, the URI of the server equipment resource and the endpoint information of the server equipment resource.

For example, the resource type of the server device returned to the configurator by the server device is oic.r.cloudconstream, the URI of the server device resource is/oic/cloudconstream, and the endpoint of the server device resource is maps:// [ fe80::1]: 2222.

In step S603, the configurator discovers the cloud agent device.

In specific implementation, the configurator sends a resource discovery request to the cloud agent device; and the resource discovery request specifies the resource type of the cloud proxy equipment. For example, the resource type of the cloud proxy device is oic.

In step S604, the cloud proxy device sends a response to discover the cloud proxy device to the configurator.

During specific implementation, discovering that the cloud proxy equipment responses carry resource links of the cloud proxy equipment; the resource link of the cloud proxy device comprises at least one of the following items: the resource type of the cloud proxy equipment, the URI of the cloud proxy equipment resource, and the resource link of the endpoint cloud proxy equipment of the cloud proxy equipment resource.

For example, the resource type of the cloud proxy device returned by the cloud proxy device to the configurator is oic.r.cloudproxy, the URI of the cloud proxy device resource is/oic/cloudproxy, and the endpoint of the cloud proxy resource is maps:// [ fe80:: 2: 3333.

In step S605, the configurator requests the cloud proxy device to acquire shadow service information.

In step S606, the cloud proxy returns shadow service information to the configurator.

Wherein the shadow service information comprises at least one of the following: an identification of the shadow service and an endpoint of the shadow service.

Step S607, the configurator configures the server device.

In some embodiments, the configurator configures shadow service information of the cloud proxy device for the server device.

During specific implementation, the configurator sends an update request to the shadow configuration resource/oic/shadow/conf of the server device, and the update request provides an identifier of the shadow service on the cloud proxy device and an endpoint of the shadow service.

Optionally, the configurator may also configure, for the server device, an original resource link that needs to be copied to the cloud proxy device.

In step S608, the configurator requests the shadow service of the cloud proxy device to generate a shadow device for the server device.

In some embodiments, generating the request of the shadow device may include: and the indication of the cloud-limited device is used for indicating that an original device (namely, a server device) generating the shadow device is the cloud-limited device.

In specific implementation, the configurator sends a creation request to the shadow generation resource/oic/shadow/gen of the cloud proxy device, wherein the creation request carries an original resource link of the server device and an endpoint of the server device. The original resource link of the server-side equipment is used for generating corresponding copied resources for the original resources of the server-side equipment. Optionally, the creation request may also carry an indication of a server device, which is used to indicate that an original device (i.e., the server device) that generates the shadow device is a cloud-end restricted device.

In step S609, the shadow service of the cloud proxy device generates a first shadow device for the server device.

Here, the URI of the replicated resource of the first shadow device includes a device identification of the server device.

In some embodiments, the description information of the first shadow device may indicate that the first shadow device is a cloud-limited device.

Optionally, the cloud proxy device issues the copied resource link of the first shadow device to a resource discovery directory of the cloud proxy device.

In step S610, the cloud proxy device sends a response to generate the first shadow device to the configurator.

In some embodiments, the resource link of the first shadow device generated on the cloud proxy device is carried in the first shadow device response.

Wherein the resource link comprises at least one of: resource link of the/oic/res resource of the shadow device and resource link of the shadow synchronization resource (/ oic/shadow/sync resource); the/oic/res resource and/or the shadow synchronization resource link includes an identification of the shadow device on the cloud proxy device and an endpoint of the shadow device.

Optionally, the generating the first shadow device response may further indicate that the first shadow device is a cloud-limited device.

In step S611, the configurator associates the server device with the first shadow device on the cloud proxy device.

During specific implementation, the configurator sends an update request to the shadow configuration resource/oic/shadow/conf of the server device; the update request includes at least one of: the cloud proxy device comprises an identification of a first shadow device, an endpoint of the first shadow device and a shadow synchronization resource/oic/shadow/sync of the first shadow device.

Wherein the shadow synchronization resource/oic/shadow/sync of the first shadow device is obtained in step S610.

After the server-side device is associated with the corresponding first shadow device, the configurator generates a second shadow device on the cloud server for the first shadow device on the cloud proxy device.

Step S612, the configurator configures a first shadow device on the cloud proxy device, and configures a copy resource link that needs to be copied to the cloud server for the first shadow device.

During specific implementation, the configurator sends an update request to the shadow configuration resource/oic/shadow/conf of the cloud proxy device, and a copy resource link, which is required to be copied to the cloud server, of the first shadow device on the cloud proxy device is provided in the update request.

In step S613, the configurator requests the shadow service of the cloud server to generate a second shadow device on the cloud server for the first shadow device.

Optionally, the create shadow device request may indicate that the original device (first shadow device) requesting the creation of the shadow device is a cloud-limited device.

In specific implementation, the configurator sends a creation request to the shadow generation resource/oic/shadow/gen of the cloud server, wherein the creation request carries at least one of the following items: the cloud proxy device comprises a shadow synchronization resource/oic/shadow/sync of the first shadow device, a copy resource link on the first shadow device (namely, a copy resource generated by the cloud proxy device for an original resource of the server device), and an endpoint of the first shadow device.

In some optional embodiments, the create request further indicates that the original device that generated the shadow device (i.e., the first shadow device) is a cloud-limited device.

In step S614, the shadow service of the cloud server generates a second shadow device for the first shadow device.

In the embodiment of the present invention, the generated URI of the copied resource of the second shadow device remains unchanged, that is, the target URI of the shadow device does not include the device identifier of the cloud proxy device.

Optionally, the generated second shadow device may indicate that the second shadow device is a cloud-limited device.

Optionally, the cloud server issues the copied resource link of the second shadow device to a resource discovery directory of the cloud server.

In step S615, the cloud server sends a generate second shadow device response to the configurator.

In the embodiment of the invention, a resource link carrying a second shadow device in the response of the shadow device is generated, wherein the resource link comprises a resource link of an oic/res resource of the shadow device and a resource link of a shadow synchronous resource (/ oic/shadow/sync resource); the/oic/res resource and/or the shadow synchronization resource link includes an identification of a second shadow device on the cloud server, an endpoint of the second shadow device.

Optionally, the generating the shadow device response may further indicate that the second shadow device is a cloud-limited device.

In step S616, the configurator associates the first shadow device on the cloud proxy device to the second shadow device on the cloud server.

In specific implementation, the configurator sends an update request to the shadow configuration resource/oic/shadow/conf on the cloud proxy device, where the update request provides an identifier of a second shadow device on the cloud server, an endpoint of the second shadow device, and a shadow synchronization resource/oic/shadow/sync of the second shadow device (obtained in step S615); optionally, the update request may further include a shadow service identifier of the cloud server; at this point, the configurator has configured the shadow service identification of the cloud server by default.

It should be noted that, the configurator may associate the server device with the first shadow device first, and then request to generate the second shadow device; step S611 is executed first, and then steps S612 to S615 are executed. The configurator may also request to generate the second shadow device first, and then associate the server device with the first shadow device; step S612 to step S615 are executed first, and then step S611 is executed. The configurator may associate the server device with the first shadow device first, and then associate the first shadow device with the second shadow device; step S611 is executed first, and then step S616 is executed. The configurator may associate the first shadow device and the second shadow device first, and then associate the server device and the first shadow device; step S616 is executed first, and then step S611 is executed.

In step S617, the configurator starts resource synchronization for the server device, the first shadow device on the cloud proxy device, and the second shadow device on the cloud server.

In the embodiment of the invention, after the resource synchronization is started, the resource synchronization is performed between the server device and the first shadow device on the cloud proxy device, and the resource synchronization is performed between the first shadow device on the cloud proxy device and the second shadow device on the cloud server.

In step S618, the second shadow device on the cloud server sends a resource synchronization request to the first shadow device on the cloud proxy device.

In the embodiment of the present invention, a target resource in the resource synchronization request is a shadow synchronization resource (/ oic/shadow/sync resource), a device identifier is a device identifier of a second shadow device on the cloud server, and a URI of the resource has a device identifier of the cloud-limited device.

Step S619, the first shadow device on the cloud proxy device sends a resource synchronization request to the server device.

In the embodiment of the invention, the target resource of the resource synchronization request is a shadow synchronization resource (/ oic/shadow/sync resource), the device identifier is a device identifier of a first shadow device on the cloud proxy device, and the device identifier of the server device is removed from the URI of the resource.

In steps S620 to S621, the server device sends the resource synchronization result to the first shadow device on the cloud proxy device, and the first shadow device on the cloud proxy device sends the resource synchronization result to the second shadow device on the cloud server.

As shown in fig. 8, a detailed processing flow of another method for generating a shadow device according to an embodiment of the present invention is that a server device controls generation of a shadow device, and includes the following steps:

step S801, the server device discovers the cloud proxy device.

In specific implementation, the server device sends a resource discovery request to the cloud agent device, wherein the resource discovery request specifies the resource type of the cloud agent device. For example, the resource type of the cloud proxy device is oic.

Step S802, the cloud proxy device sends a response to the server device to discover the cloud proxy device.

For example, the resource type of the cloud proxy device returned by the cloud proxy device to the server device is oic.r.cloudproxy, the URI of the cloud proxy device resource is/oic/cloudproxy, and the endpoint of the cloud proxy resource is maps:// [ fe80::2]: 3333.

In step S803, the server device requests the cloud proxy device to obtain shadow service information.

In step S804, the cloud proxy device returns shadow service information to the server device.

In step S805, the server device requests the shadow service of the cloud proxy device to generate a shadow device for the server device.

In some embodiments, generating the request of the shadow device may include: and the indication of the cloud-end restricted device is used for indicating that the original device requesting to generate the shadow device is the cloud-end restricted device.

During specific implementation, the server device sends a creation request to the shadow generation resource/oic/shadow/gen of the cloud proxy device, wherein the creation request carries an original resource link of the server device and an endpoint of the server device. The original resource link of the server-side equipment is used for generating corresponding copied resources for the original resources of the server-side equipment.

Optionally, the creation request may further carry an indication of a server device, which is used to indicate that an original device generating the shadow device is a cloud-end restricted device.

In step S806, the shadow service of the cloud proxy device generates a first shadow device for the server device.

In step S807, the cloud proxy device sends a response for generating the first shadow device to the server device.

Step S808, the server device associates itself with the first shadow device on the cloud proxy device.

In specific implementation, the server device updates its shadow configuration resource/oic/shadow/conf, and configures the identifier of the first shadow device on the cloud proxy device, the endpoint of the first shadow device, and the shadow synchronization resource/oic/shadow/sync of the first shadow device for itself.

Wherein the shadow synchronization resource/oic/shadow/sync of the first shadow device is obtained in step S807.

Step S809, the cloud proxy device requests the shadow service of the cloud server to generate a second shadow device on the cloud server for the first shadow device.

In specific implementation, the cloud proxy device sends a creation request to the shadow generation resource/oic/shadow/gen of the cloud server, wherein the creation request carries at least one of the following items: the cloud proxy device comprises a shadow synchronization resource/oic/shadow/sync of the first shadow device, a copy resource link on the first shadow device (namely, a copy resource generated by the cloud proxy device for an original resource of the server device), and an endpoint of the first shadow device.

In step S810, the shadow service of the cloud server generates a second shadow device for the first shadow device.

In step S811, the cloud server sends a create shadow device response to the cloud proxy device.

In step S812, the first shadow device on the cloud proxy device is associated with the second shadow device on the cloud server.

During specific implementation, a first shadow device on the cloud proxy device updates a shadow configuration resource/oic/shadow/conf of the first shadow device, and configures an identifier of a second shadow device on the cloud server, an endpoint of the second shadow device and a shadow synchronization resource/oic/shadow/sync of the second shadow device for the first shadow device; optionally, the first shadow device on the cloud proxy device may also configure itself with a shadow service identifier on the cloud server.

It should be noted that, the association between the server device and the first shadow device may occur before the cloud server generates the second shadow device; that is, step S808 is executed first, and then steps S809 to S811 are executed. The association of the server device with the first shadow device may also occur after the cloud server generates the second shadow device; that is, steps S809 to S811 are executed first, and then step S808 is executed. Moreover, the server device is associated with the first shadow device, and there is no execution sequence between the first shadow device and the second shadow device, that is, step S809 may be executed first, and then step S812 may be executed; step S812 may be executed first, and then step S809 may be executed.

In steps S813 to S814, the server device, the first shadow device on the cloud proxy device, and the second shadow device on the cloud server start resource synchronization.

In specific implementation, resource synchronization may be started by any one of the server device, the first shadow device on the cloud management device, and the second shadow device on the cloud server.

In step S815, the second shadow device on the cloud server sends a resource synchronization request to the first shadow device on the cloud proxy device.

In step S816, the first shadow device on the cloud proxy device sends a resource synchronization request to the server device.

In steps S817 to S818, the server device sends the resource synchronization result to the first shadow device on the cloud proxy device, and the first shadow device on the cloud proxy device sends the resource synchronization result to the second shadow device on the cloud server.

In order to implement the above method for generating a shadow device, an embodiment of the present invention further provides a cloud proxy device, where a composition structure of the cloud proxy device 900 is as shown in fig. 9, and the method includes:

a first receiving unit 901 configured to receive a first request message;

a first processing unit 902 configured to generate a first shadow device of the server device based on the first request message.

In the embodiment of the present invention, the first request message is sent to the cloud agent device by a configurator, or the first request message is sent to the cloud agent device by the server device.

In this embodiment of the present invention, the first receiving unit 901 is further configured to receive shadow service information of the cloud proxy device sent by a configurator. Wherein the shadow service information of the cloud proxy device includes at least one of the following: an identification of the shadow service on the cloud proxy device, and an endpoint of the shadow service.

In this embodiment of the present invention, the shadow service information of the cloud proxy device includes: the original resource link to the cloud proxy device needs to be copied.

In an embodiment of the present invention, the first request message includes at least one of the following: the original resource link of the server-side equipment and the endpoint of the server-side equipment.

In this embodiment of the present invention, the first request message includes first indication information, where the first indication information is used to indicate that the server device does not have a capability of directly accessing the cloud server.

In this embodiment of the present invention, the uniform resource identifier of the copy resource of the first shadow device includes a device identifier of the server device.

In this embodiment of the present invention, the description information of the first shadow device includes second indication information, where the second indication information is used to indicate that the first shadow device does not have a capability of directly accessing a cloud server.

In this embodiment of the present invention, the first processing unit 902 is further configured to issue the copied resource link of the first shadow device to the resource discovery directory of the cloud proxy device.

In this embodiment of the present invention, the cloud proxy device 900 further includes:

a first sending unit 903 configured to send a first request response message; the first request response message includes: a resource link of the first shadow device. And the first request response message is sent to a configurator, or the first request response message is sent to the server side equipment.

Wherein the resource link of the first shadow device comprises at least one of: an identification of the first shadow device and an endpoint of the first shadow device.

In some embodiments, the first request response message further includes third indication information indicating that the first shadow device does not have the capability of directly accessing a cloud server.

In this embodiment of the present invention, the cloud proxy device 900 further includes: a second sending unit 904, configured to send a second request message to a cloud server, where the second request message is used to request the cloud server to generate a second shadow device for the first shadow device.

Wherein the second request message comprises at least one of: a shadow synchronization resource of the first shadow device, a replicated resource link of the first shadow device, and an endpoint of the first shadow device.

In some embodiments, the second request message includes fourth indication information, where the fourth indication information is used to indicate that the server device does not have the capability of directly accessing a cloud server.

In this embodiment of the present invention, the first receiving unit 901 is further configured to receive a second request response message sent by the cloud server; the second request response message includes: a resource link of the second shadow device.

Wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device.

In some embodiments, the second request response message further includes fifth indication information indicating that the second shadow device does not have the capability of directly accessing a cloud server.

In this embodiment of the present invention, the first processing unit 902 is further configured to associate the first shadow device with the second shadow device.

In some embodiments, the first processing unit 902 is configured to configure the cloud proxy device with at least one of: the identifier of the second shadow device, the endpoint of the second shadow device, the shadow synchronization resource of the second shadow device, and the shadow service identifier of the cloud server.

In other embodiments, the first processing unit 902 is configured to receive an update request message for a shadow configuration resource sent by a configurator;

the update request message for the shadow configuration resource includes at least one of: the identifier of the second shadow device, the endpoint of the second shadow device, the shadow synchronization resource of the second shadow device, and the shadow service identifier of the cloud server.

In this embodiment of the present invention, the first processing unit 902 is further configured to start resource synchronization between the first shadow device and the second shadow device, and resource synchronization between the first shadow device and the server device.

a third sending unit 905, configured to send a resource synchronization request to the server device.

Wherein, the device identifier in the resource synchronization request is the device identifier of the first shadow device; and/or the uniform resource identifier of the resource in the resource synchronization request does not include the equipment identification of the server-side equipment.

In this embodiment of the present invention, the first receiving unit 901 is further configured to receive a first resource discovery request message;

correspondingly, the cloud proxy device 900 further includes a fourth sending unit 906, configured to send a first resource discovery request response message, where the first resource discovery request response message includes: and resource linkage of the cloud proxy equipment.

Wherein the first resource discovery request message indicates a resource type of the cloud proxy device; the resource link of the cloud proxy device comprises at least one of the following items: the resource type of the cloud agent device and the endpoint of the resource of the cloud agent device.

In the embodiment of the present invention, the first resource discovery request message is sent by a configurator, or sent by the server device; correspondingly, the first resource discovery request response message is sent to the configurator or is sent to the server side equipment.

In this embodiment of the present invention, the first receiving unit 901 is further configured to receive a request message for obtaining shadow service information;

correspondingly, the cloud proxy device 900 further includes a fifth sending unit 907 configured to send a request response message for obtaining the shadow service information.

Wherein the request response message for obtaining the shadow service information comprises at least one of the following items: an identification of the shadow service and an endpoint of the shadow service.

The request message for obtaining the shadow service information is sent by a configurator or is sent by a server device; correspondingly, the request response message for obtaining the shadow service information is sent to a configurator or is sent to the server side equipment.

In order to implement the method for generating a shadow device, an embodiment of the present invention further provides a server device, where a structure of the server device 1000 is as shown in fig. 10, and includes:

a sixth sending unit 1001, configured to send a first request message to a cloud proxy device, where the first request message is used to request the cloud proxy device to generate a first shadow device of the server device;

the second receiving unit 1002 is configured to receive the first request response message.

In some embodiments, the first request message further includes first indication information, where the first indication information is used to indicate that the server device does not have the capability of directly accessing a cloud server.

Wherein the uniform resource identifier of the replicated resource of the first shadow device comprises a device identifier of the server device. The description information of the first shadow device comprises second indication information, and the second indication information is used for indicating that the first shadow device does not have the capability of directly accessing the cloud server.

The server device 1000 further includes: a second processing unit 1003 configured to associate the server device with the first shadow device.

In this embodiment of the present invention, the second processing unit 1003 is configured to, by updating the shadow configuration resource of the server device, configure at least one of the following for the server device: the identifier of the first shadow device, the endpoint of the first shadow device, and the shadow synchronization resource of the first shadow device.

In this embodiment of the present invention, the server device 1000 further includes:

a third processing unit 1004 configured to start resource synchronization between the server device and the first shadow device.

In this embodiment of the present invention, the second receiving unit 1002 is further configured to receive a resource synchronization request sent by the cloud agent device.

In this embodiment of the present invention, the sixth sending unit 1001 is further configured to send a first resource discovery request message to the cloud proxy device;

the server device receives a first resource discovery response message sent by the cloud proxy device, where the first resource discovery request response message includes: and resource linkage of the cloud proxy equipment.

In this embodiment of the present invention, the sixth sending unit 1001 is further configured to send a request message for obtaining shadow service information to the cloud proxy device;

the second receiving unit 1002 is further configured to receive a request response message for obtaining shadow service information, where the request response message is sent by the cloud proxy device. Wherein the request response message for obtaining shadow service information includes at least one of the following: an identification of the shadow service and an endpoint of the shadow service.

In order to implement the method for generating a shadow device, an embodiment of the present invention further provides a cloud server, where a composition structure of the cloud server 1100, as shown in fig. 11, includes:

a third receiving unit 1101 configured to receive a second request message;

a fourth processing unit 1102 configured to generate a second shadow device for the first shadow device of the server device based on the second request message.

In some embodiments, the second request message further includes fourth indication information, where the fourth indication information is used to indicate that the server device does not have the capability of directly accessing a cloud server.

In this embodiment of the present invention, the cloud server 1100 further includes:

a seventh transmitting unit 1103 configured to transmit the second request response message; the second request response message includes: a resource link of the second shadow device. Wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device.

In this embodiment of the present invention, the fourth processing unit 1102 is further configured to start resource synchronization between the second shadow device and the first shadow device.

In the embodiment of the present invention, the second request message is sent by a configurator, or the second request message is sent by a cloud agent device. Correspondingly, the second request response message is sent to the configurator or sent to the cloud agent device.

In this embodiment of the present invention, the fourth processing unit 1102 is further configured to issue a copied resource link of the second shadow device to a resource discovery directory of the cloud server.

In order to implement the method for generating a shadow device, an embodiment of the present invention further provides a configurator, where as shown in fig. 12, the configurator 1200 includes:

an eighth sending unit 1201, configured to send a first request message to a cloud proxy device, where the first request message is used to request the cloud proxy device to generate a first shadow device of a server device;

a fourth receiving unit 1202 configured to receive the first request response message.

In this embodiment of the present invention, the eighth sending unit 1201 is further configured to send a second request message to a cloud server, where the second request message is used to request the cloud server to generate a second shadow device for the first shadow device.

In this embodiment of the present invention, the fourth receiving unit 1202 is further configured to receive a second request response message sent by the cloud server; the second request response message includes: a resource link of the second shadow device. Wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device.

In this embodiment of the present invention, the second request response message includes fifth indication information, where the fifth indication information is used to indicate that the second shadow device does not have a capability of directly accessing the cloud server.

In this embodiment of the present invention, the configurator 1200 further includes: a fifth processing unit 1203 configured to associate the first shadow device with the second shadow device.

In this embodiment of the present invention, the fifth processing unit 1203 is configured to send an update request message for a shadow configuration resource to the server device;

In this embodiment of the present invention, the configurator 1200 further includes: a sixth processing unit 1204, configured to configure resource synchronization between the first shadow device and the second shadow device, and resource synchronization between the first shadow device and the server device.

In this embodiment of the present invention, the eighth sending unit 1201 is further configured to send a second resource discovery request message to the server device;

the fourth receiving unit 1202 is further configured to receive a second resource discovery request response message sent by the server device, where the second resource discovery response message includes: and resource linkage of the server-side equipment.

Wherein the second resource discovery request message indicates a resource type of a server device; the resource link of the server side equipment comprises at least one of the following items: the resource type of the server device and the endpoint of the resource of the server device.

In this embodiment of the present invention, the eighth sending unit 1201 is further configured to send a first resource discovery request message to the cloud proxy device;

the fourth receiving unit 1202 is further configured to receive a first resource discovery request response message sent by the cloud proxy device, where the first resource discovery request response message includes: and resource linkage of the cloud proxy equipment.

Wherein the first resource discovery request message indicates a resource type of the cloud proxy device, and the resource link of the cloud proxy device includes at least one of: the resource type of the cloud agent device and the endpoint of the resource of the cloud agent device.

In this embodiment of the present invention, the eighth sending unit 1201 is further configured to send a request message for obtaining shadow service information to the cloud proxy device;

the fourth receiving unit 1202 is further configured to receive a request response message for obtaining shadow service information, which is sent by the cloud proxy device.

Wherein the request response message for obtaining shadow service information includes at least one of the following:

an identification of the shadow service and an endpoint of the shadow service.

The embodiment of the invention also provides cloud proxy equipment, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the generation method of the shadow equipment executed by the cloud proxy equipment when the computer program is run.

The embodiment of the present invention further provides a server device, which includes a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the steps of the method for generating the shadow device executed by the server device when running the computer program.

The embodiment of the invention also provides a cloud server, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the method for generating the shadow device executed by the cloud server when the computer program is run.

The embodiment of the present invention further provides a configurator, which includes a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the steps of the method for generating the shadow device executed by the configurator when running the computer program.

It should be noted that, in the embodiment of the present invention, the cloud agent device, the server device, the cloud server, and the configurator may all be OCF devices.

Fig. 13 is a schematic diagram of a hardware composition structure of electronic devices (a cloud agent device, a server device, a cloud server, and a configurator) according to an embodiment of the present invention, where the electronic device 700 includes: at least one processor 701, a memory 702, and at least one network interface 704. The various components in the electronic device 700 are coupled together by a bus system 705. It is understood that the bus system 705 is used to enable communications among the components. The bus system 705 includes a power bus, a control bus, and a status signal bus in addition to a data bus. But for clarity of illustration the various busses are labeled in figure 13 as the bus system 705.

It will be appreciated that the memory 702 can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. The non-volatile Memory may be ROM, Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic random access Memory (FRAM), Flash Memory (Flash Memory), magnetic surface Memory, optical Disc, or Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory (DRmb Access), and Random Access Memory (DRAM). The memory 702 described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

The memory 702 in embodiments of the present invention is used to store various types of data in support of the operation of the electronic device 700. Examples of such data include: any computer program for operating on electronic device 700, such as application 7022. Programs that implement methods in accordance with embodiments of the present invention can be included within application program 7022.

The method disclosed in the above embodiments of the present invention may be applied to the processor 701, or implemented by the processor 701. The processor 701 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 701. The Processor 701 may be a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 701 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed by the embodiment of the invention can be directly implemented by a hardware decoding processor, or can be implemented by combining hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the memory 702, and the processor 701 may read the information in the memory 702 and perform the steps of the aforementioned methods in conjunction with its hardware.

In an exemplary embodiment, the electronic Device 700 may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), FPGAs, general purpose processors, controllers, MCUs, MPUs, or other electronic components for performing the foregoing methods.

The embodiment of the application also provides a storage medium for storing the computer program.

Optionally, the storage medium may be applied to the cloud agent device in the embodiment of the present application, and the computer program enables the computer to execute corresponding processes in the methods executed by the cloud agent device in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the storage medium may be applied to the server device in the embodiment of the present application, and the computer program enables the computer to execute corresponding processes in the methods executed by the server device in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the storage medium may be applied to a cloud server in the embodiment of the present application, and the computer program enables a computer to execute corresponding processes in each method executed by the cloud server in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the storage medium may be applied to a configurator in the embodiment of the present application, and the computer program enables a computer to execute corresponding processes in each method executed by the configurator in the embodiment of the present application, which is not described herein again for brevity.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.

Claims

A method for generating a shadow device, the method comprising:

the cloud agent equipment receives a first request message;

and the cloud proxy equipment generates first shadow equipment of the server equipment based on the first request message.
The method of claim 1, wherein the first request message is sent by a configurator to the cloud proxy device.
The method according to claim 1 or 2, wherein the method further comprises:

the cloud proxy equipment receives shadow service information of the cloud proxy equipment sent by a configurator.
The method of claim 3, wherein the shadow service information of the cloud proxy device comprises at least one of:

and the identifier of the shadow service on the cloud proxy equipment and the endpoint of the shadow service.
The method of claim 3 or 4, wherein the shadow service information of the cloud proxy device comprises:

the original resource link to the cloud proxy device needs to be copied.
The method of claim 1, wherein the first request message is sent by the server device to the cloud proxy device.
The method of any of claims 1 to 6, wherein the first request message comprises at least one of:

the original resource link of the server-side equipment and the endpoint of the server-side equipment.
The method according to any one of claims 1 to 7, wherein the first request message includes first indication information, and the first indication information is used for indicating that the server-side device does not have the capability of directly accessing a cloud server.
The method of any of claims 1 to 8, wherein the uniform resource identifier of the replicated resource of the first shadow device comprises a device identification of the server device.
The method of any one of claims 1 to 9, wherein the description information of the first shadow device includes second indication information indicating that the first shadow device does not have a capability of directly accessing a cloud server.
The method of any one of claims 1 to 10, wherein the method further comprises:

and the cloud proxy equipment issues the copied resource link of the first shadow equipment to a resource discovery directory of the cloud proxy equipment.
The method of any one of claims 1 to 11, wherein the method further comprises:

the cloud proxy equipment sends a first request response message;

the first request response message includes: a resource link of the first shadow device.
The method of claim 12, wherein the resource link of the first shadow device comprises at least one of: an identification of the first shadow device and an endpoint of the first shadow device.
The method of claim 12 or 13, wherein the first request response message further includes third indication information indicating that the first shadow device does not have a capability of directly accessing a cloud server.
The method of any of claims 12 to 14, wherein the first request response message is sent to a configurator.
The method according to any one of claims 12 to 14, wherein the first request response message is sent to the server device.
The method of any of claims 1, 6-14, and 16, wherein the method further comprises:

the cloud proxy device sends a second request message to a cloud server, wherein the second request message is used for requesting the cloud server to generate a second shadow device for the first shadow device.
The method of claim 17, wherein the second request message comprises at least one of:

a shadow synchronization resource of the first shadow device, a replicated resource link of the first shadow device, and an endpoint of the first shadow device.
The method according to claim 17 or 18, wherein the second request message includes fourth indication information indicating that the server device does not have a capability of directly accessing a cloud server.
The method of any of claims 17 to 19, wherein the method further comprises:

the cloud proxy equipment receives a second request response message sent by the cloud server;

the second request response message includes: a resource link of the second shadow device.
The method of claim 20, wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device.
The method of claim 20 or 21, wherein the second request response message further includes fifth indication information indicating that the second shadow device does not have the capability to directly access a cloud server.
The method of any of claims 20 to 22, wherein the method further comprises:

the cloud proxy device associates the first shadow device and the second shadow device.
The method of claim 23, wherein the cloud proxy device associating the first shadow device and the second shadow device comprises:

the cloud proxy device configures at least one of the following items for itself: the identifier of the second shadow device, the endpoint of the second shadow device, the shadow synchronization resource of the second shadow device, and the shadow service identifier of the cloud server.
The method of claim 23, wherein the cloud proxy device associating the first shadow device and the second shadow device comprises:

the cloud proxy equipment receives an update request message aiming at the shadow configuration resource sent by a configurator;

the update request message for the shadow configuration resource includes at least one of: the identifier of the second shadow device, the endpoint of the second shadow device, the shadow synchronization resource of the second shadow device, and the shadow service identifier of the cloud server.
The method of any one of claims 1 to 25, wherein the method further comprises:

the cloud proxy device starts resource synchronization between the first shadow device and the second shadow device and resource synchronization between the first shadow device and the server device.
The method of claim 26, wherein the method further comprises:

and the cloud proxy equipment sends a resource synchronization request to the server equipment.
The method of claim 27, wherein the device identification in the resource synchronization request is a device identification of the first shadow device;

and/or the uniform resource identifier of the resource in the resource synchronization request does not include the equipment identification of the server-side equipment.
The method of any one of claims 1 to 28, wherein the method further comprises:

the cloud proxy equipment receives a first resource discovery request message;

the cloud proxy device sends a first resource discovery request response message, where the first resource discovery request response message includes: and resource linkage of the cloud proxy equipment.
The method of claim 29, wherein the first resource discovery request message indicates a resource type of the cloud proxy device.
The method of claim 29 or 30, wherein the resource link of the cloud proxy device comprises at least one of:

the resource type of the cloud agent device and the endpoint of the resource of the cloud agent device.
The method of any of claims 29 to 31, wherein the first resource discovery request message is sent by a configurator or sent by the server device.
The method according to any one of claims 29 to 32, wherein the first resource discovery request response message is sent to a configurator or to the server device.
The method of any one of claims 1 to 33, wherein the method further comprises:

the cloud proxy equipment receives a request message for acquiring shadow service information;

and the cloud proxy equipment sends a request response message for acquiring the shadow service information.
The method of claim 34, wherein the request response message to obtain shadow service information comprises at least one of:

an identification of the shadow service and an endpoint of the shadow service.
The method of claim 34 or 35, wherein the request message to obtain shadow service information is sent by a configurator or sent by a server device.
The method according to claims 34 to 36, wherein the request response message for obtaining shadow service information is sent to a configurator or to a server device.
A method for generating a shadow device, the method comprising:

the method comprises the steps that server-side equipment sends a first request message to cloud-side proxy equipment, wherein the first request message is used for requesting the cloud-side proxy equipment to generate first shadow equipment of the server-side equipment;

the server side equipment receives a first request response message.
The method of claim 38, wherein the first request message comprises at least one of:

the original resource link of the server-side equipment and the endpoint of the server-side equipment.
The method of claim 38 or 39, wherein the first request message includes first indication information indicating that the server device does not have the capability of directly accessing a cloud server.
The method of any of claims 38 to 40, wherein the uniform resource identifier of the replicated resource of the first shadow device comprises a device identification of the server device.
The method of any of claims 38 to 41, wherein the description information of the first shadow device includes second indication information indicating that the first shadow device does not have a capability to directly access a cloud server.
The method of any one of claims 38 to 42, wherein the method further comprises:

and the server side equipment associates the server side equipment with the first shadow equipment.
The method of claim 43, wherein the server device associating itself with the first shadow device comprises:

the server-side equipment configures resources for the server-side equipment by updating the shadow of the server-side equipment, and configures at least one of the following items for the server-side equipment: the identifier of the first shadow device, the endpoint of the first shadow device, and the shadow synchronization resource of the first shadow device.
The method of any one of claims 38 to 44, wherein the method further comprises:

and the server side equipment starts the resource synchronization between the server side equipment and the first shadow equipment.
The method of claim 45, wherein the method further comprises:

and the server side equipment receives a resource synchronization request sent by the cloud side agent equipment.
The method of claim 46, wherein the device identification in the resource synchronization request is a device identification of the first shadow device;

and/or the uniform resource identifier of the resource in the resource synchronization request does not include the equipment identification of the server-side equipment.
The method of any one of claims 38 to 47, wherein the method further comprises:

the server side equipment sends a first resource discovery request message to the cloud side proxy equipment;

the server device receives a first resource discovery response message sent by the cloud proxy device, where the first resource discovery request response message includes: and resource linkage of the cloud proxy equipment.
The method of claim 48, wherein the first resource discovery request message indicates a resource type of the cloud proxy device.
The method of claim 48 or 49, wherein the resource link of the cloud proxy device comprises at least one of:

the resource type of the cloud agent device and the endpoint of the resource of the cloud agent device.
The method of any one of claims 38 to 50, wherein the method further comprises:

the server side equipment sends a request message for acquiring shadow service information to the cloud proxy equipment;

and the server side equipment receives a request response message for acquiring shadow service information, which is sent by the cloud proxy equipment.
The method of claim 51, wherein the get shadow service information request response message comprises at least one of:

an identification of the shadow service and an endpoint of the shadow service.
A method for generating a shadow device, the method comprising:

the cloud server receives a second request message;

and the cloud server generates a second shadow device for the first shadow device of the server device based on the second request message.
The method of claim 53, wherein the second request message comprises at least one of:

a shadow synchronization resource of the first shadow device, a replicated resource link of the first shadow device, and an endpoint of the first shadow device.
The method of claim 53 or 54, wherein the second request message includes fourth indication information indicating that the server device does not have the capability of directly accessing a cloud server.
The method of claims 53 to 55, wherein the method further comprises:

the cloud server sends a second request response message;

the second request response message includes: a resource link of the second shadow device.
The method of claim 56, wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device.
The method of claim 56 or 57, wherein the second request response message further includes fifth indication information indicating that the second shadow device does not have the capability to directly access a cloud server.
The method of any one of claims 53 to 58, wherein the method further comprises:

the cloud server starts resource synchronization between the second shadow device and the first shadow device.
The method of any one of claims 53 to 59, wherein the second request message is sent by a configurator or the second request message is sent by a cloud proxy device.
The method of any one of claims 56 to 60, wherein the second request response message is sent to a configurator or to a cloud proxy device.
The method of any one of claims 53 to 61, wherein the method further comprises:

the cloud server issues the copied resource link of the second shadow device to a resource discovery directory of the cloud server.
A method for generating a shadow device, the method comprising:

the method comprises the steps that a configurator sends a first request message to cloud proxy equipment, wherein the first request message is used for requesting the cloud proxy equipment to generate first shadow equipment of server-side equipment;

the configurator receives a first request response message.
The method of claim 63, wherein the first request message comprises at least one of:

the original resource link of the server-side equipment and the endpoint of the server-side equipment.
The method of claim 63 or 64, wherein the first request message includes first indication information indicating that the server device does not have the capability of directly accessing a cloud server.
The method of any of claims 63-65, wherein the uniform resource identifier of the replicated resource of the first shadow device includes a device identification of the server device.
The method of any of claims 63 to 66, wherein the description information of the first shadow device includes second indication information indicating that the first shadow device does not have a capability to directly access a cloud server.
The method of any one of claims 63 to 67, wherein the method further comprises:

the configurator sends a second request message to a cloud server, wherein the second request message is used for requesting the cloud server to generate a second shadow device for the first shadow device.
The method of claim 68, wherein the second request message comprises at least one of:

a shadow synchronization resource of the first shadow device, a replicated resource link of the first shadow device, and an endpoint of the first shadow device.
The method of claim 68 or 69, wherein the second request message includes fourth indication information indicating that the server device does not have the capability of directly accessing a cloud server.
The method of any one of claims 68 to 70, wherein the method further comprises:

the configurator receives a second request response message sent by the cloud server;

the second request response message includes: a resource link of the second shadow device.
The method of claim 71, wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device.
The method of claim 71 or 72, wherein the second request response message includes fifth indication information indicating that the second shadow device does not have the capability to directly access a cloud server.
The method of any one of claims 71 to 73, wherein the method further comprises:

the configurator associates the first shadow device and the second shadow device.
The method of claim 74, wherein the configurator associates the first shadow device and the second shadow device, comprising:

the configurator sends an update request message aiming at the shadow configuration resource to the server-side equipment;

the update request message for the shadow configuration resource includes at least one of: the identifier of the second shadow device, the endpoint of the second shadow device, the shadow synchronization resource of the second shadow device, and the shadow service identifier of the cloud server.
The method of any one of claims 63 to 75, wherein the method further comprises:

the configurator configures resource synchronization between the first shadow device and the second shadow device, and resource synchronization between the first shadow device and the server device.
The method of any one of claims 63 to 76, wherein the method further comprises:

the configurator sends a second resource discovery request message to the server-side equipment;

the configurator receives a second resource discovery request response message sent by the server-side device, wherein the second resource discovery response message includes: and resource linkage of the server-side equipment.
The method of claim 77, wherein the second resource discovery request message indicates a resource type of a server device.
The method of claim 77 or 78, wherein the resource link of the server device comprises at least one of:

the resource type of the server device and the endpoint of the resource of the server device.
The method of any one of claims 63 to 79, wherein the method further comprises:

the configurator sends a first resource discovery request message to the cloud proxy equipment;

the configurator receives a first resource discovery request response message sent by the cloud proxy device, wherein the first resource discovery request response message comprises: and resource linkage of the cloud proxy equipment.
The method of claim 80, wherein the first resource discovery request message indicates a resource type of the cloud proxy device.
The method of claim 80 or 81, wherein the resource link of the cloud proxy device comprises at least one of:

the resource type of the cloud agent device and the endpoint of the resource of the cloud agent device.
The method of any one of claims 63 to 82, wherein the method further comprises:

the configurator sends a request message for acquiring shadow service information to the cloud proxy equipment;

and the configurator receives a request response message for acquiring shadow service information, which is sent by the cloud proxy equipment.
The method of claim 83, wherein the request response message to obtain shadow service information comprises at least one of:

an identification of the shadow service and an endpoint of the shadow service.
A cloud proxy device, the cloud proxy device comprising:

a first receiving unit configured to receive a first request message;

and the first processing unit is configured to generate a first shadow device of the server device based on the first request message.
The cloud proxy device of claim 85, wherein the first request message is sent by a configurator to the cloud proxy device.
The cloud proxy device of claim 85 or 86, wherein the first receiving unit is further configured to receive shadow service information of the cloud proxy device sent by a configurator.
The cloud proxy device of claim 87, wherein the shadow service information of the cloud proxy device includes at least one of:

an identification of the shadow service on the cloud proxy device, and an endpoint of the shadow service.
The cloud proxy device of claim 87 or 88, wherein the shadow service information of the cloud proxy device comprises:

the original resource link to the cloud proxy device needs to be copied.
The cloud proxy device of claim 85, wherein the first request message is sent by the server device to the cloud proxy device.
The cloud proxy device of any of claims 85-90, wherein the first request message comprises at least one of:

the original resource link of the server-side equipment and the endpoint of the server-side equipment.
The cloud proxy device of any of claims 85-91, wherein the first request message includes first indication information indicating that the server device does not have the capability to directly access a cloud server.
The cloud proxy device of any of claims 85-92, wherein a uniform resource identifier of the replicated resource of the first shadow device comprises a device identification of the server device.
The cloud proxy device of any of claims 85-93, wherein the description information of the first shadow device includes second indication information indicating that the first shadow device does not have the capability to directly access a cloud server.
The cloud proxy device of any of claims 85-94, wherein the first processing unit is further configured to publish the replicated resource link of the first shadow device to a resource discovery directory of the cloud proxy device.
The cloud proxy device of any of claims 85-95, wherein the cloud proxy device further comprises:

a first transmitting unit configured to transmit a first request response message; the first request response message includes: a resource link of the first shadow device.
The cloud proxy device of claim 96, wherein the resource link of the first shadow device includes at least one of: an identification of the first shadow device and an endpoint of the first shadow device.
The cloud proxy device of claim 96 or 97, wherein the first request response message further includes third indication information indicating that the first shadow device does not have the capability to directly access a cloud server.
The cloud proxy device of any of claims 96-98, wherein the first request response message is sent to a configurator.
The cloud proxy device of any of claims 96-98, wherein the first request response message is sent to the server device.
The cloud proxy device of any one of claims 85, 90-98, and 100, wherein the cloud proxy device further comprises:

a second sending unit, configured to send a second request message to a cloud server, where the second request message is used to request the cloud server to generate a second shadow device for the first shadow device.
The cloud proxy device of claim 101, wherein the second request message comprises at least one of:

a shadow synchronization resource of the first shadow device, a replicated resource link of the first shadow device, and an endpoint of the first shadow device.
A cloud proxy device as claimed in claim 101 or 102, wherein the second request message includes fourth indication information indicating that the server device does not have the capability of directly accessing a cloud server.
The cloud proxy device of claim 103, wherein the first receiving unit is further configured to receive a second request response message sent by the cloud server; the second request response message includes: a resource link of the second shadow device.
The cloud proxy device of claim 104, wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device.
The cloud proxy device of claim 104 or 105, wherein the second request response message further includes fifth indication information indicating that the second shadow device does not have the capability to directly access a cloud server.
The cloud proxy device of any of claims 104-106, wherein the first processing unit is further configured to associate the first shadow device with the second shadow device.
The cloud proxy device of claim 107, wherein the first processing unit is configured to configure the cloud proxy device with at least one of: the identifier of the second shadow device, the endpoint of the second shadow device, the shadow synchronization resource of the second shadow device, and the shadow service identifier of the cloud server.
The cloud proxy device of claim 107, wherein the first processing unit is configured to receive an update request message for a shadow configuration resource sent by a configurator;

the update request message for the shadow configuration resource includes at least one of: the identifier of the second shadow device, the endpoint of the second shadow device, the shadow synchronization resource of the second shadow device, and the shadow service identifier of the cloud server.
The cloud proxy device of claims 85-109, wherein the first processing unit is further configured to initiate resource synchronization between the first shadow device and the second shadow device, and between the first shadow device and the server device.
The cloud proxy device of claim 110, wherein the cloud proxy device further comprises:

a third sending unit, configured to send a resource synchronization request to the server device.
The cloud proxy device of claim 111, wherein the device identifier in the resource synchronization request is the device identifier of the first shadow device;

and/or the uniform resource identifier of the resource in the resource synchronization request does not include the equipment identification of the server-side equipment.
The cloud proxy device of any of claims 85-112, wherein the first receiving unit is further configured to receive a first resource discovery request message;

correspondingly, the cloud proxy device further includes a fourth sending unit, configured to send a first resource discovery request response message, where the first resource discovery request response message includes: and resource linkage of the cloud proxy equipment.
The cloud proxy device of claim 113, wherein the first resource discovery request message indicates a resource type of the cloud proxy device.
The cloud proxy device of claim 113 or 114, wherein the resource link of the cloud proxy device comprises at least one of:

the resource type of the cloud agent device and the endpoint of the resource of the cloud agent device.
A cloud proxy device as claimed in any one of claims 113 to 115, wherein the first resource discovery request message is sent by a configurator or by the server device.
A cloud proxy device as claimed in any one of claims 113 to 116, wherein said first resource discovery request response message is sent to a configurator or to said server device.
The cloud proxy device of any of claims 85-117, wherein the first receiving unit is further configured to receive a request message to obtain shadow service information;

correspondingly, the cloud proxy device further includes a fifth sending unit configured to send a request response message for obtaining the shadow service information.
The cloud proxy device of claim 118, wherein the get shadow service information request response message includes at least one of:

an identification of the shadow service and an endpoint of the shadow service.
The cloud proxy device of claim 118 or claim 119, wherein the request message to obtain shadow service information is sent by a configurator or by a server device.
The cloud proxy device of any of claims 118-120, wherein the request response message to obtain shadow service information is sent to a configurator or to a server device.
A server device, the server device comprising:

a sixth sending unit, configured to send a first request message to a cloud proxy device, where the first request message is used to request the cloud proxy device to generate a first shadow device of the server device;

a second receiving unit configured to receive the first request response message.
The server device of claim 122, wherein the first request message comprises at least one of:

the original resource link of the server-side equipment and the endpoint of the server-side equipment.
The server-side device of claim 122 or 123, wherein the first request message includes first indication information indicating that the server-side device does not have a capability of directly accessing a cloud server.
The server device of any of claims 122 to 124, wherein a uniform resource identifier of the replicated resource of the first shadow device comprises a device identification of the server device.
The server device of any one of claims 122 to 125, wherein the description information of the first shadow device includes second indication information indicating that the first shadow device does not have a capability of directly accessing a cloud server.
The server device of any one of claims 122 to 126, wherein the server device further comprises:

the second processing unit is configured to associate the server device with the first shadow device.
The server device of claim 127, wherein the second processing unit is configured to configure at least one of the following for the server device by updating shadow configuration resources of the server device: the identifier of the first shadow device, the endpoint of the first shadow device, and the shadow synchronization resource of the first shadow device.
The server device of any one of claims 122 to 128, wherein the server device further comprises:

a third processing unit configured to start resource synchronization between the server device and the first shadow device.
The server device of claim 129, wherein the second receiving unit is further configured to receive a resource synchronization request sent by the cloud proxy device.
The server device of claim 130, wherein the device identifier in the resource synchronization request is a device identifier of the first shadow device;

and/or the uniform resource identifier of the resource in the resource synchronization request does not include the equipment identification of the server-side equipment.
The server device according to any one of claims 122 to 131, wherein the sixth sending unit is further configured to send a first resource discovery request message to the cloud proxy device;

the server device receives a first resource discovery response message sent by the cloud proxy device, where the first resource discovery request response message includes: and resource linkage of the cloud proxy equipment.
The server device of claim 132, wherein the first resource discovery request message indicates a resource type of the cloud proxy device.
The server device of claim 132 or 133, wherein the resource link of the cloud proxy device comprises at least one of:

the resource type of the cloud agent device and the endpoint of the resource of the cloud agent device.
The server device according to any one of claims 122 to 134, wherein the sixth sending unit is further configured to send a request message for obtaining shadow service information to the cloud proxy device;

the second receiving unit is further configured to receive a request response message for obtaining shadow service information, which is sent by the cloud proxy device.
The server device of claim 135, wherein the request response message to obtain shadow service information comprises at least one of:

an identification of the shadow service and an endpoint of the shadow service.
A cloud server, the cloud server comprising:

a third receiving unit configured to receive the second request message;

and the fourth processing unit is configured to generate a second shadow device for the first shadow device of the server device based on the second request message.
The cloud server of claim 137, wherein the second request message comprises at least one of:

a shadow synchronization resource of the first shadow device, a replicated resource link of the first shadow device, and an endpoint of the first shadow device.
The cloud server of claim 137 or 138, wherein the second request message includes fourth indication information indicating that the server device does not have a capability of directly accessing a cloud server.
The cloud server of any of claims 137-139, wherein the cloud server further comprises:

a seventh transmitting unit configured to transmit a second request response message; the second request response message includes: a resource link of the second shadow device.
The cloud server of claim 140, wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device.
The cloud server of claim 140 or 141, wherein the second request response message further includes fifth indication information indicating that the second shadow device does not have the capability to directly access the cloud server.
The cloud server of any of claims 137-142, wherein the fourth processing unit is further configured to initiate resource synchronization between the second shadow device and the first shadow device.
The cloud server of any of claims 137-143, wherein the second request message is sent by a configurator or the second request message is sent by a cloud proxy device.
The cloud server of any of claims 140-144, wherein the second request response message is sent to a configurator or to a cloud proxy device.
The cloud server of any of claims 137-145, wherein the fourth processing unit is further configured to publish the replicated resource link of the second shadow device to a resource discovery directory of the cloud server.
A configurator, the configurator comprising:

an eighth sending unit, configured to send a first request message to a cloud proxy device, where the first request message is used to request the cloud proxy device to generate a first shadow device of a server device;

a fourth receiving unit configured to receive the first request response message.
The configurator of claim 147, wherein the first request message comprises at least one of:

the original resource link of the server-side equipment and the endpoint of the server-side equipment.
The configurator of claim 147 or 148, wherein the first request message includes first indication information indicating that the server device does not have a capability of directly accessing a cloud server.
The configurator of any of claims 147 to 149, wherein a uniform resource identifier of the replicated resource of the first shadow device includes a device identification of the server device.
The configurator of any one of claims 147 to 150, wherein the description information of the first shadow device includes second indication information indicating that the first shadow device does not have a capability to directly access a cloud server.
The configurator of any one of claims 147 to 151, wherein the eighth sending unit is further configured to send a second request message to a cloud server, the second request message requesting the cloud server to generate a second shadow device for the first shadow device.
The configurator of claim 152, wherein the second request message includes at least one of:

a shadow synchronization resource of the first shadow device, a replicated resource link of the first shadow device, and an endpoint of the first shadow device.
The configurator of claim 152 or 153, wherein the second request message includes fourth indication information indicating that the server device does not have a capability of directly accessing a cloud server.
The configurator of any one of claims 152 to 154, wherein the fourth receiving unit is further configured to receive a second request response message sent by the cloud server; the second request response message includes: a resource link of the second shadow device.
The configurator of claim 155, wherein the resource link of the second shadow device comprises at least one of: an identification of the second shadow device and an endpoint of the second shadow device.
The configurator of claim 155 or 156, wherein the second request response message includes fifth indication information indicating that the second shadow device does not have the capability to directly access a cloud server.
The configurator of any one of claims 155 to 157, wherein the configurator further comprises:

a fifth processing unit configured to associate the first shadow device and the second shadow device.
The configurator of claim 158, wherein the fifth processing unit is configured to send an update request message for shadow configuration resources to the server device;

the update request message for the shadow configuration resource includes at least one of: the identifier of the second shadow device, the endpoint of the second shadow device, the shadow synchronization resource of the second shadow device, and the shadow service identifier of the cloud server.
The configurator of any of claims 147 to 159, wherein the configurator further comprises:

a sixth processing unit, configured to configure resource synchronization between the first shadow device and the second shadow device, and resource synchronization between the first shadow device and the server device.
The configurator of any of claims 147 to 160,

the eighth sending unit is further configured to send a second resource discovery request message to the server device;

the fourth receiving unit is further configured to receive a second resource discovery request response message sent by the server device, where the second resource discovery response message includes: and resource linkage of the server-side equipment.
The configurator of claim 161, wherein the second resource discovery request message indicates a resource type of a server device.
The configurator of claim 161 or 162, wherein the resource link of the server device comprises at least one of:

the resource type of the server device and the endpoint of the resource of the server device.
The configurator of any one of claims 147 to 163,

the eighth sending unit is further configured to send a first resource discovery request message to the cloud proxy device;

the fourth receiving unit is further configured to receive a first resource discovery request response message sent by the cloud proxy device, where the first resource discovery request response message includes: and resource linkage of the cloud proxy equipment.
The configurator of claim 164, wherein the first resource discovery request message indicates a resource type of the cloud proxy device.
The configurator of claim 164 or 165, wherein the resource links of the cloud proxy device comprise at least one of:

the resource type of the cloud agent device and the endpoint of the resource of the cloud agent device.
The configurator of any one of claims 147 to 166,

the eighth sending unit is further configured to send a request message for obtaining shadow service information to the cloud proxy device;

the fourth receiving unit is further configured to receive a request response message for obtaining shadow service information, which is sent by the cloud proxy device.
The configurator of claim 167, wherein the request response message to obtain shadow service information includes at least one of:

an identification of the shadow service and an endpoint of the shadow service.
A cloud proxy device comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor is configured to execute the steps of the method for generating a shadow device according to any one of claims 1 to 37 when the computer program is run.
A server device comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor is configured to execute the steps of the method for generating a shadow device according to any one of claims 38 to 52 when the computer program is run.
A cloud server comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor is configured to execute the steps of the method for generating a shadow device according to any one of claims 53 to 62 when the computer program is run.
A configurator comprising a processor and a memory for storing a computer program operable on the processor, wherein the processor is operable when executing the computer program to perform the steps of the method of generating a shadow device of any of claims 63 to 84.
A storage medium storing an executable program which, when executed by a processor, implements the shadow device creation method of any one of claims 1 to 37.
A storage medium storing an executable program which, when executed by a processor, implements the shadow device creation method of any one of claims 38 to 52.
A storage medium storing an executable program which, when executed by a processor, implements the shadow device creation method of any one of claims 53 to 62.
A storage medium storing an executable program which, when executed by a processor, implements the shadow device creation method of any of claims 63 to 84.