CN118235384A

CN118235384A - Subscription configuration method, subscription configuration device, computer equipment and storage medium

Info

Publication number: CN118235384A
Application number: CN202180104163.2A
Authority: CN
Inventors: 茹昭
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-12-24
Filing date: 2021-12-24
Publication date: 2024-06-21
Also published as: WO2023115585A1

Abstract

A subscription configuration method, a subscription configuration device, computer equipment and a storage medium belong to the technical field of Internet of things. The method comprises the following steps: acquiring node information (401) of a virtual node, wherein the virtual node is created in cloud platform equipment; transmitting a first configuration instruction (402) including node information of the virtual node to a target source device; the first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node. The scheme expands the application scene of equipment subscription.

Description

Subscription configuration method, subscription configuration device, computer equipment and storage medium

Technical Field

The present application relates to the field of internet of things, and in particular, to a subscription configuration method, a subscription configuration device, a computer device, and a storage medium.

Background

With the continuous development of internet of things (Internet of Things, ioT) technology, more and more internet of things devices bring great convenience to the production and life of users in various fields such as smart home, industrial production and the like.

In the related art, a client device in the internet of things can directly subscribe to a resource on a target source device (such as a server device), and the subscription mode is monotonous.

Disclosure of Invention

The embodiment of the application provides a subscription configuration method, a subscription configuration device, computer equipment and a storage medium. According to the scheme, the application scene subscribed by the equipment in the Internet of things can be expanded. The technical scheme is as follows:

In one aspect, an embodiment of the present application provides a subscription configuration method, where the method is performed by a configuration device, and the method includes:

acquiring node information of a virtual node, wherein the virtual node is created in cloud platform equipment;

Transmitting a first configuration instruction comprising node information of the virtual node to target source equipment; the first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.

In one aspect, an embodiment of the present application provides a subscription configuration method, where the method is performed by a cloud platform device, and the method includes:

creating a virtual node in the cloud platform device;

Transmitting node information of the virtual node to configuration equipment so that the configuration equipment transmits a first configuration instruction comprising the node information of the virtual node to target source equipment;

The first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.

In one aspect, an embodiment of the present application provides a subscription configuration method, where the method is performed by a target source device, and the method includes:

Receiving a first configuration instruction comprising node information of a virtual node, which is sent by configuration equipment; the virtual node is established in cloud platform equipment;

And configuring the virtual node as a node with subscription authority to the target source equipment according to the first configuration instruction.

In another aspect, an embodiment of the present application provides a subscription configuration apparatus, where the apparatus includes:

The device comprises an identifier acquisition module, a cloud platform device and a virtual node management module, wherein the identifier acquisition module is used for acquiring node information of a virtual node, and the virtual node is created in the cloud platform device;

The configuration module is used for sending a first configuration instruction comprising node information of the virtual node to target source equipment; the first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.

The node creation module is used for creating a virtual node in the cloud platform equipment;

the device comprises an identification sending module, a configuration device and a target source device, wherein the identification sending module is used for sending node information of the virtual node to the configuration device so that the configuration device sends a first configuration instruction comprising the node information of the virtual node to the target source device;

the configuration instruction receiving module is used for receiving a first configuration instruction which is sent by the configuration equipment and comprises node information of the virtual node; the virtual node is established in cloud platform equipment;

And the node configuration module is used for configuring the virtual node into a node with subscription authority for the target source equipment according to the first configuration instruction.

In yet another aspect, an embodiment of the present application provides a computer device, where the computer device includes a processor, a memory, and a transceiver, where the memory stores a computer program, and the computer program is configured to be executed by the processor to implement the subscription configuration method described above.

In yet another aspect, an embodiment of the present application further provides a computer readable storage medium having a computer program stored therein, the computer program being loaded and executed by a processor to implement the subscription configuration method described above.

In yet another aspect, the present application further provides a chip, where the chip is configured to run in a computer device, so that the computer device performs the subscription configuration method described above.

In yet another aspect, the present application provides a computer program product comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the subscription configuration method described above.

In yet another aspect, the present application provides a computer program for execution by a processor of a computer device to implement the subscription configuration method described above.

The technical scheme provided by the embodiment of the application can bring the following beneficial effects:

Creating a virtual node in the cloud platform equipment, wherein the configuration equipment can acquire the identification information of the virtual node, configure the target source equipment based on the node information of the virtual node, and configure the node information of the virtual node to the target source equipment so that the virtual node subscribes the target source equipment; because the virtual node is located at the cloud, the virtual node can subscribe the target resource device from the cloud correspondingly, and further, the client device can subscribe the target source device in a proxy subscription mode through the cloud, so that the application scene of device subscription is expanded.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of a network architecture of an internet of things according to an embodiment of the present application;

FIG. 2 is a system framework diagram of resource subscriptions provided by one embodiment of the application;

FIG. 3 is a schematic diagram of a proxy subscription initiation flow provided by one embodiment of the present application;

FIG. 4 is a flow chart of a subscription configuration method provided by one embodiment of the present application;

FIG. 5 is a flow chart of a subscription configuration method provided by one embodiment of the present application;

FIG. 6 is a flow chart of a subscription configuration method provided by one embodiment of the present application;

FIG. 7 is a system framework diagram of a subscription arrangement provided by one embodiment of the present application;

FIG. 8 is a flow chart of a subscription configuration method provided by one embodiment of the present application;

FIG. 9 is a schematic diagram of a configuration and subscription flow of a remote agent involved in the embodiment of FIG. 8;

FIG. 10 is a schematic diagram of the configuration and subscription flow of another remote agent involved in the embodiment of FIG. 8;

FIG. 11 is a schematic diagram of the configuration and subscription flow of yet another remote agent involved in the embodiment of FIG. 8;

FIG. 12 is a schematic diagram of a remote proxy subscription flow involved in the embodiment of FIG. 8;

FIG. 13 is a block diagram of a subscription configuration apparatus provided by one embodiment of the present application;

FIG. 14 is a block diagram of a subscription configuration apparatus provided by one embodiment of the present application;

FIG. 15 is a block diagram of a subscription configuration apparatus provided by one embodiment of the present application;

Fig. 16 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided by the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided by the embodiments of the present application is applicable to similar technical problems.

Referring to fig. 1, a schematic diagram of a network architecture of the internet of things according to an embodiment of the present application is shown. The network architecture of the internet of things can comprise: source device 110 (shown in fig. 1 as source device 110a and source device 110 b), client device 120 (shown in fig. 1 as client device 120a and client device 120 b), proxy device 130, and configuration device 140; optionally, the network architecture may further include a cloud platform device 150;

The source device 110 may be a device for providing a server function corresponding to an internet of things protocol in the internet of things. The source device may provide subscribed resources externally.

For example, source device 110 may be a smart home device, such as a smart light fixture, a smart television, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart electric cooker, a sweeping robot, a smart sound box, a smart switch, and the like.

Or the source device 110 may be an industrial production device, such as a lathe, an industrial robot, a solar panel, a wind turbine, or the like.

Or the source device 110 may be a commercial service device, such as a vending machine or the like.

Or the source device 110 may be an intelligent monitoring device such as a monitoring camera, infrared sensor, acoustic sensor, temperature sensor, or the like.

In one possible implementation, the client device 120 may be a user-side terminal device. For example, the client device 120 may be a smart controller, smart remote control, smart phone, tablet, smart watch, smart television, gateway, or the like; or the client device 120 may be a personal computer such as a desktop computer, a portable computer, a personal workstation, or the like.

Or the client device 120 may be another device that provides a server function corresponding to the internet of things protocol.

In another possible implementation, the client device 120 is a client entity (may be a virtual entity) running based on a terminal device, for example, the client device 120 may be an Application (APP) running in the terminal device for performing operations such as accessing, controlling, and managing the internet of things device.

In one possible implementation, the proxy device 130 connects the source device 110 and the client device 120 at the same time, and provides a service for the client device 120 to proxy subscription resources to the source device 110.

The configuration device 140 may be a terminal device on the user side. For example, the configuration device 140 may be a smart phone, tablet, smart watch, smart television, or the like.

In another possible implementation, the configuration device 140 may also be a client entity (may be a virtual entity) running on the basis of the terminal device, for example, the configuration device 140 may be an APP running in a smart phone for managing configuration of the source device 110, the client device 120 and the proxy device 130.

Cloud platform device 150 is a server deployed on the network side. For example, the server may be a single server, or the server may be a server cluster composed of a plurality of servers. The cloud platform device 150 may be a computer device that provides hardware support for the cloud platform.

In an embodiment of the present application, the source device 110, the client device 120, the proxy device 130, and the configuration device 140 may be electronic devices that satisfy the same or different internet of things protocols, for example, may be electronic devices that satisfy a Matter protocol (or called connecting through IP (Internet Protocol, internet protocol) to a home workgroup (Connected Home over IP Working Group, CHIP) item) under a connection standard alliance (or Zigbee alliance).

Taking the source device 110, the client device 120, the proxy device 130, the configuration device 140, and other internet of things devices as examples, the data model of the Matter device has the following characteristics:

1) The Matter device includes one or more end points represented using an end point Number (also abbreviated as Endpoint-no).

For example, a Matter device is a spotlight, and the spotlight has three bulbs, so that each bulb corresponds to one endpoint, that is, an actual physical device may include multiple endpoints (or may include only one endpoint, of course); for another example, a water device is a socket having 4 jacks, each of which may correspond to an Endpoint.

2) One or more Device types (DEVICE TYPE) for each Endpoint are represented using a Device identification (DEVICE IDENTITY, device ID).

For example, one water device is an air conditioning device, which includes a thermostat and a fan, where the thermostat and the fan correspond to one device type under the same Endpoint, the fan corresponds to another device type, and the thermostat and the fan can be controlled by the same Endpoint.

3) Each Endpoint includes multiple clusters (Cluster), which are divided into two types, namely a Server (Server) and a Client (Client), and the corresponding Cluster IDs are the same.

4) Each Cluster comprises a plurality of attributes (Attribute), events (Event), instructions (Command), which are respectively represented by Attribute ID, event ID and Command ID, and the Attribute and the Event have corresponding data types.

The source device 110, the client device 120, the proxy device 130, the configuration device 140, and other devices of the internet of things may also be Zigbee devices, where the data model of the Zigbee devices is similar to the data model of the Matter device in structure, except that there is no Event in the data model of the Zigbee devices.

1) Proxy subscription:

In the embodiments of the application, the client device in the internet of things can subscribe resources to the target source device through the proxy device; for example, in the network architecture shown in fig. 1 described above, client device 120b may subscribe to resources with source device 110b through proxy device 130.

In the subscription scenario of an internet of things system, a source device refers to a node that is the original source of authenticity for a set of data. That is, the source device acts as a publisher of the data.

A client device refers to a node that wishes to subscribe to a source device.

In proxy subscriptions, a proxy device of a source device may present the same "mirror" of data resources in the source device to downstream client devices without the client devices having to change their interactions, whether they interact with the proxy device or with the source device itself. Referring to FIG. 2, a system framework diagram of resource subscriptions provided by one embodiment of the application is shown. As shown in fig. 2, the source device 21 includes therein a subscribed resource C1, a resource C2, and a resource C3; the client device 22 may subscribe to the resources directly to the source device 21 or may indirectly subscribe to the resources in the source device 21 by acting as a proxy through the proxy device 23.

Multiplexing of proxy subscriptions allows a source device to delegate subscriptions to resources to its proxy device, which itself only needs to support a single subscription from that proxy device. This reduces the energy and memory resource requirements of the source device. Thus, a single subscription from a proxy device may be a union of interest sets of multiple clients. If the combined set of attribute/event paths becomes quite large, the proxy device may merge multiple localization paths with wildcards into a single wider path with wildcards.

A client device subscribing to a proxy device may specify in the path the node ID of the source device to which it wishes to subscribe. The node ID of this source device is different from the logical target node ID of the subscription message (i.e., the node ID of the proxy device). Subscription messages herein refer to messages that a client device subscribes to a proxy device.

When a client device makes a currently active subscription to a proxy device for a resource, the proxy device may attempt to subscribe to the resource with the source device.

Referring to fig. 3, a schematic diagram of a proxy subscription initiation flow according to an embodiment of the present application is shown. As shown in fig. 3, the process by which the client device initiates a proxy subscription is as follows:

S31, the Client device (Client) sends a subscription request (SubscribeRequest) for initiating resource subscription to the target source device (a source device) to the Proxy device (Proxy) so as to request subscription to the C1 resource on the target source device.

Wherein the C1 resource may be any resource on the target source device, including functional resources, such as switches, etc.

In some scenarios, a client device may also be referred to as a subscribing device, and the target Source device may also be referred to simply as a Source (Source), or as a target resource device, target resource node, or the like.

S32, the proxy device sends a report data (ReportData) message to the target source device to inform the client device that it has temporarily no resources of the target source device.

In this process, the proxy device may check whether the client device has subscription rights, such as browsing (View) rights, to the C1 resource on the target source device. Wherein when the proxy device has the authority of proxy browsing (ProxyView) on an access control list (Access Control Lists, ACL) Cluster (Cluster) resource of the target source device, the ACL Cluster can be subscribed to or read. Based on the above, the proxy device may acquire the subscription authority of the client device to the C1 resource on the target source device, so as to determine whether the client device may subscribe to the C1 resource. Optionally, when the subscription device subscribes to the C1 resource on the target source device directly, or subscribes to the C1 resource through proxy device proxy, it is required to have a right (View right) to subscribe to the C1 resource on the target source device, for example, it is required to have an access control entry (Access Control Entry, ACE) corresponding to the client device on the ACL Cluster of the target source device.

Wherein, after receiving the ReportData message, the client device may send a status response to the proxy device (StatusResponse), and after receiving the status response, the proxy device sends a subscription response to the client device (SubscribeResponse).

S33, the proxy device initiates subscription to the C1 resource on the target source device.

In this process, the proxy device may send a subscription request to the target source device requesting subscription to the C1 resource on the target source device. The target source device sends a ReportData message to the proxy device that includes subscription data for the C1 resource, such as the state of the C1 resource, etc.

Optionally, after receiving the ReportData message sent by the target source device, the proxy device sends StatusResponse a message to the target source device, and after receiving the StatusResponse message, the target source device sends SubscribeResponse a message to the proxy device.

S34, after the proxy equipment successfully subscribes to the target source equipment, the subscription flow of the client equipment is processed.

In this process, the proxy device may send a ReportData message to the client device, including subscription data for subscribed C1 resources; after receiving the ReportData message, the client device can send StatusResponse a message to the proxy device.

Since the subscription mechanism provides a "sync" message to infer the operation of both subscribers, it allows the client device to monitor the operation of the source device to which it subscribes. In addition, the transmission of the "synchronization" message is preserved in the downstream subscription by the "no upstream subscription" status code. The proxy subscription may effectively convey the same information as the synchronization message of the client device direct feed device.

One proxy device may subscribe to another proxy device instead of directly subscribing to the source device. This may create a proxy chain that allows a single source device to be proxied by multiple proxy devices, thereby better utilizing the capacity of the available proxies.

2) Active agent cluster (ValidProxyCluster)

The active proxy cluster, also referred to as an active proxy cluster, provides a way for the source device to inform the source device of the active proxy devices on behalf of which it is subscribed.

In the embodiment of the present application, the Cluster of devices in the internet of things may also be referred to as a Cluster, a function set/Cluster, a resource set, and so on.

For example, when the client device needs to subscribe to the resource in the source device by proxy, the active proxy cluster may be acquired from the source device, so as to determine which devices may act as proxy devices for the source device, select one or more proxy devices from the active proxy devices, and initiate a proxy subscription procedure through the selected proxy devices.

The attributes of the active agent clusters may be as shown in table 1 below.

TABLE 1

As shown in Table 1, the attributes of the active agent cluster include an active agent list (ValidProxyList) made up of active agent entries (ValidProxyStruct). The structure of the valid agent entry may be as shown in table 2 below.

TABLE 2

Id	Name	Type	Constraint	Access	Conformance
0	FabricIndex	fabric-idx	all	RW	M
1	NodeID	node-idx	all	RW	M

As shown in table 2, an active agent entry includes an index of security domain (Fabric) and a node ID of a corresponding active agent device.

The definition of the command corresponding to the valid agent cluster may be as shown in table 3 below.

TABLE 3 Table 3

As shown in table 3, the commands corresponding to the active agent clusters include a get active agent request (Get Valid Proxies Request) sent by the client to the server, and a get active agent response (Get Valid Proxies Response) sent by the server to the client.

When the source device receives a request for acquiring the effective agent, the node ID of the effective agent device in the effective agent cluster can be returned to the opposite terminal through an effective agent response.

In the scheme, the local area network equipment is supported to serve as proxy equipment, and proxy subscription of resources in the source equipment is realized. For example, a user subscribes the on-off state of the lamp by taking a mobile phone as a client device and taking a gateway in a home local area network as an agent; or after the user mobile phone is connected to the home local area network, the on-off state of the lamp can be directly subscribed. In the subscription process, the mobile phone is required to be connected to the home local area network to establish connection, and when the user leaves the coverage area of the home local area network, direct subscription or proxy subscription cannot be performed, so that the subscription scene of the equipment is limited.

In view of the foregoing, the following embodiments of the present application provide a subscription configuration scheme, where a virtual node in a cloud platform device may be configured as a node having a subscription to a source device, that is, the source device may be subscribed by the virtual node in the cloud platform device, and further, a client device may subscribe, by proxy subscription, to a resource in the source device through the virtual node in the cloud.

Referring now to FIG. 4, a flowchart of a subscription configuration method provided by one embodiment of the present application is shown, which may be performed by a configuration device, such as configuration device 140 in the network architecture shown in FIG. 1; the method may comprise the following steps:

Step 401, obtaining node information of a virtual node, where the virtual node is created in a cloud platform device.

The Node information of the virtual Node may be a Node ID (Node ID) of the virtual Node.

Step 402, a first configuration instruction including node information of a virtual node is sent to target source equipment; the first configuration instruction is used for configuring node information of the virtual node to target source equipment; the node information of the virtual node is used for the virtual node to subscribe the target source device.

The cloud platform device may be deployed on the network side, that is, the cloud platform device, the configuration device, and the target source device do not belong to the same local area network.

The subscribing to the target source device may refer to subscribing to a resource in the target source device.

In summary, according to the scheme shown in the implementation of the present application, a virtual node is created in the cloud platform device, the configuration device may obtain the identification information of the virtual node, configure the target source device based on the node information of the virtual node, and configure the node information of the virtual node to the target source device, so that the virtual node subscribes to the target source device; because the virtual node is located at the cloud, the virtual node can subscribe the target resource device from the cloud correspondingly, and further, the client device can subscribe the target source device in a proxy subscription mode through the cloud, so that the application scene of device subscription is expanded.

Referring to fig. 5, a flowchart of a subscription configuration method provided by an embodiment of the present application is shown, where the method may be performed by a cloud platform device, for example, the cloud platform device may be the cloud platform device 150 in the network architecture shown in fig. 1; the method may comprise the following steps:

step 501, creating a virtual node in a cloud platform device.

Step 502, node information of a virtual node is sent to configuration equipment, so that the configuration equipment sends a first configuration instruction comprising the node information of the virtual node to target source equipment; the first configuration instruction is used for configuring node information of the virtual node to target source equipment; the node information of the virtual node is used for the virtual node to subscribe the target source device.

In summary, according to the scheme shown in the implementation of the present application, a virtual node is created in a cloud platform device, and node information of the virtual node is sent to a configuration device, where the configuration device may configure a target source device based on the node information of the virtual node, and the node information of the virtual node is configured to the target source device, so that the virtual node subscribes to the target source device; because the virtual node is located at the cloud, the virtual node can subscribe the target resource device from the cloud correspondingly, and further, the client device can subscribe the target source device in a proxy subscription mode through the cloud, so that the application scene of device subscription is expanded.

Referring now to FIG. 6, a flowchart of a subscription configuration method provided by one embodiment of the present application is shown, which may be performed by a target source device, such as source device 110 in the network architecture shown in FIG. 1; the method may comprise the following steps:

Step 601, receiving a first configuration instruction including node information of a virtual node, which is sent by a configuration device; the virtual nodes are created in the cloud platform device.

Step 602, configuring node information of a virtual node in a target source device according to a first configuration instruction; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.

In summary, according to the scheme shown in the implementation of the present application, a virtual node is created in the cloud platform device, and node information of the virtual node is sent to the configuration device, where the configuration device may configure the target source device based on the node information of the virtual node, and configure the node information of the virtual node to the target source device, so that the virtual node subscribes to the target source device; because the virtual node is located at the cloud, the virtual node can subscribe the target resource device from the cloud correspondingly, and further, the client device can subscribe the target source device in a proxy subscription mode through the cloud, so that the application scene of device subscription is expanded.

According to the scheme shown in the above-mentioned figures 4 to 6, the virtual nodes of the cloud capable of subscribing the target source equipment can be configured for the target source equipment, so that the target source equipment can be subscribed by the cloud.

Referring to fig. 7, a system framework diagram of a subscription configuration provided by one embodiment of the present application is shown. In one possible application scenario, as shown in fig. 7, the configuration device 71 and the target source device 72 are located in the same lan, and communication is performed between the two through an internet of things protocol. The cloud platform device 73 is located at the cloud. The cloud platform device 73 and the configuration device 71 and the target source device 72 may communicate through the internet.

In the system framework shown in fig. 7, the process of subscribing to a configuration may be as follows:

S1, the cloud platform device 73 creates a virtual node 73a, the virtual node 73a corresponding to node information of the virtual node.

S2, the cloud platform device 73 transmits the node information of the virtual node 73a to the configuration device 71.

S3, the configuration device 71 sends a first configuration instruction comprising node information of the virtual node to the target source device 72; accordingly, the target source device 72 may receive the first configuration instruction.

S4, the target source equipment 72 configures node information of the virtual node at the target source equipment 72 according to the first configuration instruction.

After configuring the virtual node 73a to configure the node information of the virtual node, the configuration device 71 or other client device 74 may subscribe to the resource C1 and/or the resource C2 in the target source device 72 in a proxy subscription manner through the virtual node 73 a; alternatively, virtual node 73a may itself act as a client device subscribing to resource C1 and/or resource C2 from target source device 72.

Referring to fig. 8, a flowchart of a subscription configuration method provided by an embodiment of the present application is shown, where the method may be interactively performed by a configuration device, a cloud platform device, a target source device, and a client device, for example, the configuration device, the cloud platform device, and the target source device may be the configuration device 140, the cloud platform device 150, the source device 110, and the client device 120 in the network architecture shown in fig. 1, respectively; the method can include a virtual node creation phase, a device configuration phase, a connection and cloud configuration phase, and a proxy subscription phase; the method may comprise the following steps:

1. Virtual node creation phase

In step 801, a cloud platform device creates a virtual node at a cloud end.

In the embodiment of the application, the cloud platform device can actively create the virtual node at the cloud end, or the cloud platform device can also create the virtual node at the cloud end when receiving the request/instruction for configuring the device.

Wherein the virtual nodes correspond to node information of the virtual nodes.

In one possible implementation manner, the node information of the virtual node includes at least one of node identification information (for example, may be denoted as vNode ID) of the virtual node, and security domain identification information (for example, may be denoted as FabricID) of the virtual node.

In one possible implementation manner, the node information of the virtual node may be automatically generated by the virtual node when the virtual node is created, and correspondingly, before the cloud platform device sends the node information of the virtual node to the configuration device, the node information of the virtual node generated by the virtual node may be acquired.

In another possible implementation manner, the node information of the virtual node may be generated by the cloud platform device before the virtual node is created. That is, the cloud platform device may generate node identification information of the virtual node when creating the virtual node, and then create the virtual node according to the node identification information of the virtual node and security domain identification information (Fabric ID) of the virtual node.

In another possible implementation manner, when the node information of the virtual node includes node identification information of the virtual node and security domain identification information of the virtual node, the node identification information of the virtual node and the security domain identification information of the virtual node may be generated by the configuration device and the cloud platform device, respectively. For example, the node identification information may be generated by a configuration device, and the security domain identification information of the virtual node may be generated by a cloud platform device; or the node identification information may be generated by the cloud platform device, and the security domain identification information of the virtual node may be generated by the configuration device.

The security domain identification information of the virtual node may be generated by the configuration device and sent to the cloud platform device.

For example, when the virtual node is generated when the cloud platform device receives a request/instruction of the configuration device, the configuration device may send the locally generated security domain identification information to the cloud platform device, so as to instruct the cloud platform device to generate the virtual node corresponding to the security domain identification information.

Or the security domain identification information of the virtual node may also be generated by the cloud platform device, in which case the cloud platform device subsequently sends the security domain identification information to the configuration device.

For example, when the cloud platform device creates a virtual node for the configuration device, the cloud platform device may generate security domain identification information, and create the virtual node according to the security domain identification information (Fabric ID), and at this time, the cloud platform device further sends the generated security domain identification information to the configuration device.

Optionally, when the virtual node is created, the cloud platform device may initiate creation of the virtual node according to the security domain identification information, and obtain the identification of the virtual node from the virtual node.

Step 802, the cloud platform device sends node information of the virtual node to the configuration device, and the configuration device receives the node information of the virtual node.

In the embodiment of the application, the cloud platform device can also send the node information of the virtual node to the configuration device so that the configuration device can acquire the node information of the virtual node.

2. Device configuration phase

In step 803, the configuration device sends a first configuration instruction including node information of the virtual node to the target source device, and correspondingly, the target source device receives the first configuration instruction.

After the configuration device obtains the node information of the virtual node, a first configuration instruction can be generated according to the node information of the virtual node, and the first configuration instruction is sent to the target source device.

In one possible implementation manner, the configuration device may further send an address of the cloud platform device to the target source device, and correspondingly, the target source device receives the address of the cloud platform device sent by the configuration device.

For example, the configuration device may send a cloud connection instruction to the target source device to configure the target source device to connect to the cloud platform device.

For another example, the configuration device may also send the address of the cloud platform device to the target source device, where the address is carried in the first configuration instruction. That is, the first configuration instruction at this time has both the functions of the authority configuration and the address configuration.

Step 804, the target source device configures node information of the virtual node in the target source device according to the first configuration instruction; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.

In the embodiment of the application, the target source equipment can configure the node information of the virtual node in the target cluster in the target source equipment.

In one possible implementation, the target source device may further configure the virtual node as a node having subscription rights to the target source device according to the first configuration instruction.

In the embodiment of the present application, after receiving the first configuration instruction, the target source device may configure the virtual node as a node having a subscription authority to the target source device.

The configuring the virtual node as a node having subscription authority to the target source device may include adding an access control entry (Access Control Entry, ACE) corresponding to the virtual node in an access control list (Access Control List, ACL) of the target source device.

In one possible implementation, the configuration device may further send a second configuration instruction to the target source device; the second configuration instruction is used to write node information (such as an active agent entry) of the virtual node in an active agent cluster of the target source device. Correspondingly, the target source device can write node information of the virtual node in the effective proxy cluster of the target source device according to the second configuration instruction.

In another possible implementation manner, the first configuration instruction is further used to write node information of the virtual node in an active agent cluster of the target source device. That is, the first configuration instruction and the second configuration instruction may be the same instruction.

In the embodiment of the application, the virtual node can also be used as an effective proxy node of the target source device, so that the client device initiates proxy subscription to the target source device through the virtual node of the cloud. At this time, the target source device may write the node information of the virtual node into the valid proxy entry corresponding to the virtual node, and the subsequent client device may learn from the target source device that the target source device may be proxy subscribed by the virtual node.

In one possible implementation manner, the node information of the virtual node includes at least one of security domain identification information of the virtual node and node identification information of the virtual node. Optionally, the node information of the virtual node further includes cloud agent attribute information;

the cloud agent attribute information is used for indicating that the virtual node is an agent node of the cloud.

For example, after receiving the first configuration instruction or the second configuration instruction, the target source device may add a parameter to the ValidProxyStruct structure in the ValidProxyList attribute of the local active agent cluster, to indicate whether the corresponding agent node is a cloud agent, where the structure of ValidProxyStruct may be as shown in table 4 below.

TABLE 4 Table 4

Id	Name	Type	Constraint	Access	Conformance
0	FabricIndex	fabric-idx	all	RW	M
1	NodeID	node-idx	all	RW	M
2	IsCloudProxy	bool	all	RW	M

As shown in table 4, the IsCloudProxy parameters are used to indicate whether the corresponding Node ID is the identifier of the proxy Node of the cloud.

Optionally, when the IsCloudProxy parameter indicates that the corresponding Node ID is an identifier of a proxy Node of the cloud, the IsCloudProxy parameter is cloud proxy attribute information.

Accordingly, when the IsCloudProxy parameter indicates that the corresponding Node ID is not the identifier of the proxy Node of the cloud, the IsCloudProxy parameter may be referred to as non-cloud proxy attribute information.

For example, the "pool" type of IsCloudProxy parameter in table 4 indicates that the parameter is a boolean variable, and the variable values include both (true) and false (false). When the value of the IsCloudProxy parameter is "true", it indicates that the corresponding node is a proxy node of the cloud, whereas when the value of the IsCloudProxy parameter is "false", it indicates that the corresponding node is not a proxy node of the cloud.

In another possible implementation, the target source device may not write the node information of the virtual node in the active agent cluster.

3. Connection and cloud configuration stage

In step 805, the target source device establishes session connection with the cloud platform device according to the address of the cloud platform device.

In the embodiment of the application, after the target source device obtains the address of the cloud platform device, a session connection request can be sent to the cloud platform device according to the address of the cloud platform device so as to establish session connection with the cloud platform device.

The session connection may be a secure connection established based on a node operation certificate (Node Operation Certificate, NOC), among others.

Step 806, the target source device binds the session connection with the source identification information; the source identification information is used to indicate the target source device, for example, the source identification information may include identification information of the target source device.

In the embodiment of the present application, after the session connection is established between the cloud platform device and the target source device, the cloud platform device may bind source identification information (for example, may be denoted as sNode ID) corresponding to the target source device to the session connection, so as to be used when subscribing to the target source device.

In one possible implementation, the cloud platform device may obtain the source identification information from a device certificate of the source node before binding the session connection with the source identification information.

In the embodiment of the application, in the process of establishing session connection between the target source device and the cloud platform device, the device certificate of the target source device can be sent to the cloud platform device, so that the cloud platform device can verify the validity of the cloud platform device through the device certificate. The device certificate may indirectly indicate or directly include source identification information, and the cloud platform device may obtain the source identification information from the device certificate.

Or the source identification information can also be sent to the cloud platform device by the target source device through the session connection.

Step 807, the cloud platform device sends a notification message to the client device; the notification message is used to indicate that the target source device is a source device to which the virtual node can proxy.

In the embodiment of the application, the cloud platform equipment can send a notification message to the client equipment through the virtual node; or the cloud platform device can also directly send the notification message to the client device through a path other than the virtual node.

In one possible implementation, the cloud platform device may first configure the source identification information to the virtual node, and then send a notification message to the client device through the virtual node.

When the cloud platform device configures the Source identification information to the virtual node, the virtual node may add the Source identification information to a Source List (Source List), which indicates that a target Source node corresponding to the Source identification information may be subscribed by the virtual node.

The client device may be a device that establishes a session connection with the cloud platform device. For example, the client device may be the configuration device, or may be a user terminal or an internet of things device other than the configuration device.

In one possible implementation manner, when the source identification information is configured to the virtual node, the cloud platform device may query the identification information of the cloud agent supported by the target source device, obtain node information of the virtual node, query the virtual node according to the node information of the virtual node, and then configure the source identification information to the queried virtual node.

In the embodiment of the application, a plurality of virtual nodes can be simultaneously created in the cloud platform equipment. The cloud platform device needs to determine the virtual node corresponding to the target source device before configuring the source identification information to the virtual node.

In an exemplary scheme, when determining a virtual node corresponding to a target source node, after establishing session connection with the target source device, the cloud platform device can query the target source device for a node belonging to a cloud agent in supported effective agent nodes through the session connection, and then locally queries the matched virtual node according to identification information of the cloud agent supported by the target source device.

In a possible implementation manner, the querying the identification information of the cloud agent supported by the target source device to obtain node information of the virtual node includes:

reading an effective agent list from the target source equipment, wherein the effective agent list comprises identification information of each effective agent of the target source equipment;

Acquiring node information which is a virtual node from identification information of each effective agent of target source equipment, wherein the identification information corresponds to cloud agent attribute information; the cloud agent attribute information is used for indicating that the virtual node is an agent node of the cloud.

In an exemplary scheme of the embodiment of the present application, after a session connection is established between the cloud platform device and the target source device, a request (Get Valid Proxies Request) for acquiring an effective agent may be sent to the target source device, so as to request to acquire an effective agent list in an effective agent list cluster of the target source device. And the target source equipment returns an effective agent obtaining response (Get Valid Proxies Response) to the cloud platform equipment according to the effective agent request, wherein the response can comprise the effective agent list. The cloud platform device queries the identification information corresponding to the cloud agent attribute information (namely IsCloudProxy parameters indicating that the corresponding Node ID is the identification of the cloud agent Node) from the effective agent list, and then queries the virtual nodes, of which the identification information is the identification information corresponding to the cloud agent attribute information, in all virtual nodes created by the cloud platform device, as the virtual nodes corresponding to the target source device.

In one possible implementation, configuring the source identification information to the virtual node includes:

acquiring security domain identification information of target source equipment;

inquiring the virtual node according to the security domain identification information;

And configuring the source identification information to the queried virtual node.

In the embodiment of the application, the target source equipment can accept subscription of other nodes in the same security domain (Fabric), and correspondingly, after the cloud platform equipment establishes session connection with the target source equipment, the corresponding virtual nodes can be queried through the security domain identification information of the target source equipment, and the source identification information of the target source equipment is configured to the queried virtual nodes. The security domain identification information of the target source device may also be obtained from a device certificate of the target source device.

In another possible implementation, when the cloud platform device directly sends the notification message to the client device through a path other than the virtual node, the cloud platform device may also temporarily not configure the source identification information to the virtual node.

4. Proxy subscription phase

In step 808, the cloud platform device receives a subscription request sent by the client device, where the subscription request includes source identification information.

In the embodiment of the present application, after receiving the notification message, if a resource in the target source device needs to be subscribed remotely, the client device may initiate a request for proxy subscription to a virtual node in the cloud platform device, so as to request the resource in the target source device to be subscribed by using the virtual node as a proxy.

In one possible implementation manner, the notification message may include node information of a virtual node of the virtual node, and accordingly, the client device may send, to the virtual node, a request for the proxy subscription according to the node information of the virtual node.

In another possible implementation, after the client device receives the notification message, the valid proxy list may be requested from the target source device through source identification information in the notification message. And the target source equipment returns the effective agent list to the client equipment according to the effective agent request. The client device queries the identification information corresponding to the cloud agent attribute information from the effective agent list to obtain node information of the virtual node capable of carrying out agent subscription on the target source device, and when the target source device needs to be subscribed remotely subsequently, the client device can send a request of the agent subscription to the virtual node according to the node information of the virtual node.

In a possible implementation manner, if the cloud platform device does not configure the source identification information to the virtual node in step 807, in step 808, after the virtual node receives the subscription request, the source identification information included in the subscription request may be written into the source list, so as to complete configuration of the source identification information.

In step 809, the cloud platform device queries for session connections bound to the source identification information.

In the embodiment of the application, after receiving the subscription request, the virtual node can notify the cloud platform device of source identification information included in the subscription request, and the cloud platform device queries the bound session connection according to the source identification information.

In step 810, the cloud platform device initiates a proxy subscription to the target source device through session connection.

After the cloud platform device queries the bound session connection according to the source identification information, the cloud platform device can initiate proxy subscription to the target source device according to the queried session connection.

Referring to fig. 9, a schematic diagram of a configuration and subscription flow of a remote agent according to an embodiment of the present application is shown. As shown in fig. 9, taking an example that a user purchases an intelligent home device (i.e., a target source device, hereinafter may be simply referred to as a device), and downloads an intelligent home APP as a configuration device and a client device (simply referred to as Commissioner), a process for implementing remote proxy configuration and subscription may include the following steps:

1. Virtual node creation phase

S91, after the user installs Commissioner APP in the mobile phone, opening the APP, connecting to the cloud platform, and registering the account number of the user.

S92, commissioner APP generates FabricID for the user.

S93, commissioner APP configures FabricID of the user to the cloud platform.

And S94, the cloud platform creates a virtual node and configures the virtual node to join the Fabric of the user.

S95, the virtual node generates an own ID (vNodeID) and enables a Proxy (Proxy) function.

And S96, the virtual node transmits vNodeID back to Commissioner APP through the cloud platform equipment.

2. Device configuration phase

S97, commissioner APP configures vNodeID corresponding rights on the device, for example, configures vNodeID corresponding rights of the virtual node to perform proxy subscription on the resource on the device, and so on.

S98, commissioner APP configures the device to the user Fabric and configures vNodeID into the device' S proxy list ValidProxyList, isCloudProxy is set to True (i.e., isCloudProxy parameter indicates vNodeID is the ID of the proxy node of the cloud).

And S99, commissioner APP, sending the cloud platform address to the equipment. Optionally, commissioner APP may also send network connection information to the device, such as Wi-Fi identification information, wi-Fi access password, etc.

3. Connection and cloud configuration stage

S910, the device establishes a session connection with the cloud platform address using the NOC. For example, the session connection may be a session (CERTIFICATE AUTHENTICATED SESSION ESTABLISHMENT, CASE) secure connection established based on certificate authentication.

For example, if the device has not been connected to the network, the device may access the network through the network connection information, and then establish a CASE secure connection with the cloud platform through the cloud platform address.

S911, the cloud platform acquires the device ID (snoid) from the certificate of the device, and saves sNodeID the association with the current session (i.e., binding sNodeID with the current session).

S912, the cloud platform sends sNodeID to Commissioner APP to notify that there is new device access. Optionally, the notification may also be sent to other Client (Client) APPs in the same Fabric, for example, a smart home APP of the user's home.

4. Proxy subscription phase

S913, commissioner APP or other CLIENT APP in the same Fabric sends Get Valid Proxies Request a command over the lan to retrieve a valid agent in the device agent list ValidProxyList and filter vNodeID according to IsCloudProxy.

S914, commissioner APP or other CLIENT APP in the same Fabric requests the subscribing device from the virtual node, carrying sNodeID.

S915, after receiving the subscription request, the virtual node sends a subscription initiating request to the cloud platform, wherein the subscription initiating request carries sNodeID. Optionally, the virtual node adds sNodeID to its own source device list SourceList.

S916, the virtual node initiates a subscription device request to the cloud platform, carrying sNodeID parameters.

And S917, the cloud platform finds out a corresponding session according to sNodeID and forwards the request to the equipment.

S918, after successful subscription, the device reports the subscribed device state to the virtual node.

After receiving the device state, the virtual node reports the device state to Commissioner APP or other CLIENT APP in the same Fabric.

Referring to fig. 10, a schematic diagram of another remote agent configuration and subscription flow is shown according to an embodiment of the present application. As shown in fig. 10, taking an example that a user purchases an intelligent home device (abbreviated as a device) and downloads an intelligent home APP as a configuration device and a client device (abbreviated as Commissioner), the process of implementing remote agent configuration and subscription may include the following steps:

1. Virtual node creation phase

S1001, after the user installs Commissioner APP, opening the APP, connecting to the cloud platform, and registering the user.

S1002, commissioner APP generates FabricID for the user.

S1003, commissioner APP configures FabricID of the user to the cloud platform.

And S1004, the cloud platform creates a virtual node and configures the virtual node to join the Fabric of the user.

S1005, the virtual node generates an own ID (vNodeID) and enables a Proxy function.

S1006, the virtual node returns vNodeID to Commissioner APP through the cloud platform.

2. Device configuration phase

S1007, commissioner APP configures vNodeID corresponding rights on the device, for example, configures vNodeID corresponding rights of the virtual node to perform proxy subscription on the resource on the device, and so on.

S1008, commissioner APP configures the device to the user Fabric and configures vNodeID into the proxy list ValidProxyList of the device, isCloudProxy set to True (i.e. IsCloudProxy parameter indicates vNodeID is the ID of the proxy node of the cloud).

S1009, commissioner APP sends the cloud platform address to the device. Optionally, commissioner APP may also send network connection information to the device, such as Wi-Fi identification information, wi-Fi access password, etc.

3. Connection and cloud configuration stage

S1010, the device establishes session connection with the cloud platform address by using the NOC. For example, the session connection may be a session (CERTIFICATE AUTHENTICATED SESSION ESTABLISHMENT, CASE) secure connection established based on certificate authentication.

And S1011, the cloud platform acquires the device ID (sNodeID) from the certificate of the device, and stores sNodeID the association with the current session.

S1012, the cloud platform sends Get Valid Proxies Request a command to the device to obtain the valid agents in the device agent list ValidProxyList, and screens vNodeID according to IsCloudProxy.

And S1013, the cloud platform finds a virtual node according to vNodeID and writes sNodeID into a source equipment list SourceList of the virtual node.

S1014, the virtual node sends sNodeID to Commissioner APP through the cloud platform, informing that there is new device access. Optionally, the notification may also be sent to other CLIENT APP in the same Fabric, e.g., the smart home APP of the user's home.

4. Proxy subscription phase

S1015, commissioner APP or other CLIENT APP in the same Fabric requests a subscription Device from the virtual node, carrying sNodeID.

S1016, after receiving the subscription request, the virtual node sends a subscription initiating request to the cloud platform, wherein the subscription initiating request carries sNodeID.

S1017, the virtual node initiates a subscription device request to the cloud platform, carrying sNodeID parameters.

S1018, the cloud platform finds out a corresponding session according to sNodeID and forwards the request to the device.

S1019, after successful subscription, the device reports the subscribed device state to the virtual node.

S1020, after receiving the device state, the virtual node reports the device state to Commissioner APP or other CLIENT APP in the same Fabric.

Referring to fig. 11, a schematic diagram of a configuration and subscription flow of a remote agent according to an embodiment of the present application is shown. As shown in fig. 11, taking an example that a user purchases an intelligent home device (abbreviated as a device) and downloads an intelligent home APP as a configuration device and a client device (abbreviated as Commissioner), the process of implementing remote agent configuration and subscription may include the following steps:

1. Virtual node creation phase

S1101, after the user installs Commissioner APP, opening the APP, connecting to the cloud platform, and registering the account number of the user.

And S1102, after the user is successfully registered, the cloud platform generates FabricID of the user.

And S1103, the cloud platform issues FabricID of the user to Commissioner APP.

S1104, the cloud platform generates an ID (vNodeID) of the virtual node.

S1105, the cloud platform creates a virtual node, configures the ID of the virtual node and configures the virtual node to join the Fabric of the user.

S1106, the virtual node enables Proxy function.

S1107, the cloud platform returns vNodeID to Commissioner APP.

2. Device configuration phase

S1108, commissioner APP configures vNodeID corresponding rights on the device, for example, configures vNodeID corresponding rights of the virtual node to perform proxy subscription on the resource on the device, and so on.

S1109, commissioner APP sends the cloud platform address to the device. Optionally, commissioner APP may also send network connection information to the device, such as Wi-Fi identification information, wi-Fi access password, etc.

3. Connection and cloud configuration stage

S1110, after the equipment is accessed to the network, CASE safe connection is established by using the NOC and the cloud platform address.

S1111, the cloud platform acquires device IDs (sNodeIDs) and FabricID from the certificates of the devices.

S1112, the cloud platform saves sNodeID the association with the current session.

And S1113, the cloud platform finds the virtual node with the same Fabric as the equipment according to the acquired FabricID.

S1114, the cloud platform writes sNodeID to the source device list SourceList of the virtual node.

And S1115, the virtual node sends sNodeID to Commissioner APP through the cloud platform to inform that a new device is accessed. Optionally, the notification may also be sent to other CLIENT APP in the same Fabric, e.g., the smart home APP of the user's home.

4. Proxy subscription phase

S1116, commissioner APP or other CLIENT APP in the same Fabric requests the subscription Device from the virtual node, carrying sNodeID.

S1117, after receiving the subscription request, the virtual node sends a subscription initiating request to the cloud platform, wherein the request carries sNodeID.

S1118, the virtual node initiates a subscription device request to the cloud platform, carrying sNodeID parameters.

And S1119, the cloud platform finds out a corresponding session according to sNodeID and forwards the request to the equipment.

And S1120, after the subscription is successful, the device reports the subscribed device state to the virtual node.

S1121, after receiving the device state, the virtual node reports the device state to Commissioner APP or other CLIENT APP in the same Fabric.

In the schemes shown in fig. 9 to 11, the notification message is a new device notification sent by the cloud platform after the cloud platform establishes a connection with the device and configures the device to the virtual node. Alternatively, the client device may notify the client device of the device to which the virtual node can subscribe by proxy in other ways than the new device notification.

Referring to fig. 12, a schematic diagram of a remote proxy subscription process according to an embodiment of the present application is shown. Taking a new access to a client device (CLIENT APP) as an example, as shown in fig. 12, after S911, S1013, or S1114, the process of remote proxy subscription may include the following steps:

s1201, CLIENT APP sends an access notification to the cloud platform. The access notification may notify the cloud platform that there is new client access.

S1202, the virtual node sends sNodeID to CLIENT APP through the cloud platform, and notifies CLIENT APP that the device corresponding to sNodeID can be subscribed by the virtual node proxy.

S1203, CLIENT APP requests the subscription Device from the virtual node, carrying sNodeID.

And S1204, after receiving the subscription request, the virtual node sends a subscription initiating request to the cloud platform, wherein the request carries sNodeID.

S1205, the virtual node initiates a subscription device request to the cloud platform, carrying sNodeID parameters.

And S1206, the cloud platform finds out a corresponding session according to sNodeID and forwards the request to the equipment.

And S1207, after the subscription is successful, the device reports the subscribed device state to the virtual node.

S1208, the virtual node reports the device state to CLIENT APP after receiving the device state.

According to the scheme disclosed by the embodiment of the application, the problem that the client device cannot subscribe and acquire the state of the source device remotely can be solved, and the source device is subscribed remotely by adding a virtual node with a proxy function in the cloud platform, so that a user can acquire the state of the source device to be subscribed in real time through the cloud platform.

Referring to fig. 13, a block diagram of a subscription configuration apparatus according to an embodiment of the present application is shown. The apparatus has the functions to be performed by the configuration device in implementing the method shown in fig. 4 or fig. 8 described above. As shown in fig. 13, the subscription configuration 1300 may include:

the identifier obtaining module 1301 is configured to obtain node information of a virtual node, where the virtual node is created in the cloud platform device;

A configuration module 1302, configured to send a first configuration instruction including node information of the virtual node to a target source device; the first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.

In one possible implementation, the first configuration instruction is configured to configure the virtual node as a node having subscription rights to the target source device.

In one possible implementation, the configuration module is further configured to:

Sending a second configuration instruction to the target source equipment; the second configuration instruction is used for writing node information of the virtual node in an effective agent cluster of the target source device.

In one possible implementation, the node information of the virtual node includes at least one of node identification information of the virtual node, and security domain identification information of the virtual node.

In one possible implementation manner, the node information of the virtual node further includes: cloud agent attribute information of the virtual node;

In one possible implementation, the apparatus further includes:

and the address sending module is used for sending the address of the cloud platform equipment to the target source equipment.

In a possible implementation manner, the identifier obtaining module is configured to receive node information of the virtual node sent by the cloud platform device.

In one possible implementation, the security domain identification information of the virtual node is generated by the configuration device;

or alternatively

The security domain identification information of the virtual node is generated and transmitted by the cloud platform device.

In summary, according to the scheme shown in the implementation of the present application, a virtual node is created in the cloud platform device, the configuration device may obtain node information of the virtual node, configure the target source device based on the node information of the virtual node, and configure the node information of the virtual node to the target source device, so that the virtual node subscribes to the target source device; because the virtual node is located at the cloud, the virtual node can subscribe the target resource device from the cloud correspondingly, and further, the client device can subscribe the target source device in a proxy subscription mode through the cloud, so that the application scene of device subscription is expanded.

Referring to fig. 14, a block diagram of a subscription configuration apparatus according to an embodiment of the present application is shown. The device has the function of realizing the method shown in the figure 5 or the figure 8 and executed by the cloud platform equipment. As shown in fig. 14, the subscription configuration 1400 may include:

A node creation module 1401, configured to create a virtual node in the cloud platform device;

An identifier sending module 1402, configured to send node information of the virtual node to a configuration device, so that the configuration device sends a first configuration instruction including node information of the virtual node to a target source device;

In one possible implementation manner, the first configuration instruction is configured to configure the virtual node as a node having subscription authority to the target source device.

In a possible implementation manner, the first configuration instruction is further used to write node information of the virtual node in an active agent cluster of the target source device.

In one possible implementation, the apparatus further includes:

The first identifier obtaining module is used for obtaining the node information of the virtual node generated by the virtual node before the identifier sending module sends the node information of the virtual node to the configuration equipment when the node information of the virtual node comprises the node identifier information of the virtual node.

In one possible implementation, the node creation module is configured to, in response to a request from a node,

Generating node identification information of the virtual node;

And creating the virtual node according to the node identification information of the virtual node and the security domain identification information of the virtual node.

In one possible implementation, the security domain identification information of the virtual node is generated and transmitted by the configuration device;

or alternatively

The security domain identification information of the virtual node is generated by the cloud platform device.

In one possible implementation, the apparatus further includes:

The connection establishment module is used for establishing session connection with the target source equipment;

The binding module is used for binding the session connection with the source identification information; the source identification information is used to indicate the target source device.

In one possible implementation, the apparatus further includes:

And the second identifier acquisition module is used for acquiring the source identifier information from the device certificate of the target source device before the binding module binds the session connection with the source identifier information.

In one possible implementation, the apparatus further includes:

And the notification module is used for sending a notification message to the client device, wherein the notification message is used for indicating that the target source device is the source device to which the virtual node can subscribe in a proxy mode.

In one possible implementation, the apparatus further includes:

and the information configuration module is used for configuring the source identification information to the virtual node before the notification module sends the notification message to the client device.

In a possible implementation manner, the notification module is configured to send, through the virtual node, the notification message to the client device.

In one possible implementation, the information configuration module is configured to, in use,

Inquiring identification information of a cloud agent supported by the target source equipment to obtain node information of the virtual node;

Inquiring the virtual node according to the node information of the virtual node;

Acquiring node information which is the virtual node from the identification information of each effective agent of the target source equipment, wherein the identification information corresponds to cloud agent attribute information; the cloud agent attribute information is used for indicating that the virtual node is an agent node of the cloud.

Acquiring security domain identification information of the target source equipment;

In one possible implementation, the apparatus further includes:

a subscription request receiving module, configured to receive a subscription request sent by a client device, where the subscription request includes the source identification information;

the connection inquiry module is used for inquiring the session connection bound with the source identification information;

And the subscription module is used for initiating proxy subscription to the target source equipment through the session connection.

Referring to fig. 15, a block diagram of a subscription configuration apparatus according to an embodiment of the present application is shown. The apparatus has the functions to implement the methods described above and illustrated in fig. 6 or 8, as performed by the target source device. As shown in fig. 15, the subscription configuration apparatus 1500 may include:

a configuration instruction receiving module 1501, configured to receive a first configuration instruction including node information of a virtual node, which is sent by a configuration device; the virtual node is established in cloud platform equipment;

A node configuration module 1502, configured to configure node information of the virtual node in the target source device according to the first configuration instruction; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.

In one possible implementation, the apparatus further includes:

and the permission configuration module is used for configuring the virtual node as a node with subscription permission for the target source equipment according to the first configuration instruction.

In a possible implementation manner, the configuration instruction receiving module is further configured to receive a second configuration instruction sent by the configuration device;

The apparatus further comprises:

And the writing module is used for writing the node information of the virtual node in the effective proxy cluster of the target source equipment according to the second configuration instruction.

In a possible implementation manner, the first configuration instruction is further configured to write node information of the virtual node in an active agent cluster of the target source device.

In one possible implementation, the node information of the virtual node further includes: cloud agent attribute information of the virtual node;

In one possible implementation, the apparatus includes:

the address receiving module is used for receiving the address of the cloud platform device, which is sent by the configuration device;

And the connection establishment module is used for establishing session connection with the cloud platform equipment according to the address of the cloud platform equipment.

It should be noted that, when the apparatus provided in the foregoing embodiment performs the functions thereof, only the division of the respective functional modules is used as an example, in practical application, the foregoing functional allocation may be performed by different functional modules according to actual needs, that is, the content structure of the device is divided into different functional modules, so as to perform all or part of the functions described above.

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

Referring to fig. 16, a schematic diagram of a computer device 1600 according to an embodiment of the application is shown. The computer device 1600 may include: a processor 1601, a receiver 1602, a transmitter 1603, a memory 1604, and a bus 1605.

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

The receiver 1602 and the transmitter 1603 may be implemented as one communication component, which may be a communication chip. The communication chip may also be referred to as a transceiver.

The memory 1604 is connected to the processor 1601 by way of a bus 1605.

The memory 1604 may be used for storing a computer program for execution by the processor 1601 to perform the steps of the method embodiments described above.

Further, the memory 1604 may be implemented by any type of volatile or nonvolatile memory device or combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable read-only memory, static random access memory, read-only memory, magnetic memory, flash memory, programmable read-only memory.

In an exemplary scenario, when the computer device 1600 is implemented as a configuration device, the transceiver 1602 is configured to obtain node information of a virtual node, where the virtual node is created in a cloud platform device; transmitting a first configuration instruction comprising node information of the virtual node to target source equipment; the first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.

The process performed by the processor 1601 and/or the transceiver 1602 in the computer device 1600 may refer to the steps performed by the configuration device in the method shown in any of fig. 4 or fig. 8.

In another exemplary aspect, when the computer device 1600 is implemented as a cloud platform device, the processor 1601 is configured to create a virtual node in the cloud platform device; a processor 1601, configured to send node information of the virtual node to a configuration device, so that the configuration device sends a first configuration instruction including the node information of the virtual node to a target source device; the first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.

The processes performed by the processor 1601 and/or the transceiver 1602 in the computer device 1600 may refer to the steps performed by the cloud platform device in the method shown in any of fig. 5 or fig. 8.

In another exemplary scenario, when the computer device 1600 is implemented as a target source device, the transceiver 1602 is configured to receive a first configuration instruction sent by a configuration device, including node information of a virtual node; the virtual node is established in cloud platform equipment; and a processor 1601, configured to configure the virtual node as a node having subscription rights to the target source device according to the first configuration instruction.

The process performed by the processor 1601 and/or transceiver 1602 in the computer device 1600 may refer to the steps performed by the target source device in the method shown in any of fig. 6 or 8.

The embodiment of the application also provides a computer readable storage medium, in which a computer program is stored, the computer program is loaded and executed by a processor to implement all or part of the steps executed by the configuration device, the cloud platform device or the target source device in the method shown in fig. 4, fig. 5, fig. 6 or fig. 8.

The present application also provides a chip for running in a computer device, so that the computer device performs all or part of the steps performed by the configuration device, the cloud platform device, or the target source device in the method shown in fig. 4, fig. 5, fig. 6, or fig. 8.

The present application also provides a computer program product, or computer program, comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device performs all or part of the steps performed by the configuration device, the cloud platform device, or the target source device in the method shown in fig. 4, fig. 5, fig. 6, or fig. 8.

The present application also provides a computer program to be executed by a processor of a computer device to implement all or part of the steps performed by a configuration device, a cloud platform device, or a target source device in the method shown in fig. 4, 5, 6, or 8.

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

The foregoing description of the exemplary embodiments of the application is not intended to limit the application to the particular embodiments disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the application.

Claims

A subscription configuration method, the method performed by a configuration device, the method comprising:

acquiring node information of a virtual node, wherein the virtual node is created in cloud platform equipment;

Transmitting a first configuration instruction comprising node information of the virtual node to target source equipment; the first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.
The method of claim 1, wherein the first configuration instruction is configured to configure the virtual node as a node having subscription rights to the target source device.
The method according to claim 1 or 2, characterized in that the method further comprises:

Sending a second configuration instruction to the target source equipment; the second configuration instruction is used for writing node information of the virtual node in an effective agent cluster of the target source device.
The method according to claim 1 or 2, wherein the first configuration instruction is further used to write node information of the virtual node in a valid proxy cluster of the target source device.
The method according to any one of claims 1 to 4, wherein the node information of the virtual node includes at least one of node identification information of the virtual node, and security domain identification information of the virtual node.
The method of claim 5, wherein the node information of the virtual node further comprises: cloud agent attribute information of the virtual node;

the cloud agent attribute information is used for indicating that the virtual node is an agent node of the cloud.
The method according to any one of claims 1 to 6, further comprising:

and sending the address of the cloud platform device to the target source device.
The method according to any one of claims 1 to 7, wherein the obtaining node information of the virtual node includes:

And receiving node information of the virtual nodes, which is sent by the cloud platform equipment.
The method according to any one of claims 1 to 8, wherein,

The security domain identification information of the virtual node is generated by the configuration device;

or alternatively

The security domain identification information of the virtual node is generated and transmitted by the cloud platform device.
A subscription configuration method, wherein the method is performed by a cloud platform device, the method comprising:

creating a virtual node in the cloud platform device;

Transmitting node information of the virtual node to configuration equipment so that the configuration equipment transmits a first configuration instruction comprising the node information of the virtual node to target source equipment;

The first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.
The method of claim 10, wherein the first configuration instruction is configured to configure the virtual node as a node having subscription rights to the target source device.
The method according to claim 10 or 11, wherein the first configuration instruction is further used to write node information of the virtual node in a valid proxy cluster of the target source device.
The method according to any one of claims 10 to 12, wherein the node information of the virtual node includes at least one of node identification information of the virtual node, and security domain identification information of the virtual node.
The method according to claim 13, wherein when the node information of the virtual node includes node identification information of the virtual node, before the sending the node information of the virtual node to the configuration device, further comprising:

and acquiring node identification information of the virtual node generated by the virtual node.
The method of claim 13, wherein the creating a virtual node in the cloud platform device comprises:

generating node identification information of the virtual node;

And creating the virtual node according to the node identification information of the virtual node and the security domain identification information of the virtual node.
The method of claim 15, wherein the step of determining the position of the probe is performed,

The security domain identification information of the virtual node is generated and transmitted by the configuration equipment;

or alternatively

The security domain identification information of the virtual node is generated by the cloud platform device.
The method according to any one of claims 10 to 16, further comprising:

Establishing session connection with the target source equipment;

binding the session connection with source identification information; the source identification information is used to indicate the target source device.
The method of claim 17, wherein prior to binding the session connection with source identification information, further comprising:

And acquiring the source identification information from the device certificate of the target source device.
The method of claim 18, wherein the method further comprises:

and sending a notification message to the client device, wherein the notification message is used for indicating that the target source device is a source device to which the virtual node can subscribe in a proxy mode.
The method of claim 19, wherein prior to sending the notification message to the client device, further comprising:

And configuring the source identification information to the virtual node.
The method of claim 20, wherein the sending a notification message to the client device comprises:

and sending the notification message to the client device through the virtual node.
The method of claim 20, wherein said configuring the source identification information to the virtual node comprises:

Inquiring identification information of a cloud agent supported by the target source equipment to obtain node information of the virtual node;

Inquiring the virtual node according to the node information of the virtual node;

and configuring the source identification information to the queried virtual node.
The method of claim 22, wherein the querying the identification information of the cloud agent supported by the target source device to obtain the node information of the virtual node includes:

Reading an effective agent list from the target source equipment, wherein the effective agent list comprises identification information of each effective agent of the target source equipment;

Acquiring node information which is the virtual node from the identification information of each effective agent of the target source equipment, wherein the identification information corresponds to cloud agent attribute information; the cloud agent attribute information is used for indicating that the virtual node is an agent node of the cloud.
The method of claim 20, wherein said configuring the source identification information to the virtual node comprises:

Acquiring security domain identification information of the target source equipment;

inquiring the virtual node according to the security domain identification information;

and configuring the source identification information to the queried virtual node.
The method according to any one of claims 17 to 24, further comprising:

Receiving a subscription request sent by a client device, wherein the subscription request comprises the source identification information;

querying the session connection bound with the source identification information;

and initiating a proxy subscription to the target source equipment through the session connection.
A subscription configuration method, the method performed by a target source device, the method comprising:

Receiving a first configuration instruction comprising node information of a virtual node, which is sent by configuration equipment; the virtual node is established in cloud platform equipment;

According to the first configuration instruction, node information of the virtual node is configured in the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.
The method of claim 22, wherein the method further comprises:

And configuring the virtual node as a node with subscription authority to the target source equipment according to the first configuration instruction.
The method according to claim 26 or 27, characterized in that the method further comprises:

Receiving a second configuration instruction sent by the configuration equipment;

and writing node information of the virtual node in an effective proxy cluster of the target source equipment according to the second configuration instruction.
The method according to claim 26 or 27, wherein the first configuration instruction is further configured to write node information of the virtual node in a valid proxy cluster of the target source device.
The method according to any one of claims 26 to 29, wherein the node information of the virtual node includes at least one of node identification information of the virtual node, and security domain identification information of the virtual node.
The method of claim 30, wherein the node information of the virtual node further comprises: cloud agent attribute information of the virtual node;

the cloud agent attribute information is used for indicating that the virtual node is an agent node of the cloud.
A method according to any one of claims 26 to 31, wherein the method comprises:

Receiving an address of the cloud platform device, which is sent by the configuration device;

And establishing session connection with the cloud platform equipment according to the address of the cloud platform equipment.
A subscription configuration apparatus, the apparatus comprising:

The device comprises an identifier acquisition module, a cloud platform device and a virtual node management module, wherein the identifier acquisition module is used for acquiring node information of a virtual node, and the virtual node is created in the cloud platform device;

The configuration module is used for sending a first configuration instruction comprising node information of the virtual node to target source equipment; the first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.
The apparatus of claim 33, wherein the first configuration instructions are configured to configure the virtual node as a node having subscription rights to the target source device.
The apparatus of claim 33 or 34, wherein the configuration module is further configured to send a second configuration instruction to the target source device; the second configuration instruction is used for writing node information of the virtual node in an effective agent cluster of the target source device.
The method of claim 33 or 34, wherein the first configuration instruction is further configured to write node information of the virtual node in a valid proxy cluster of the target source device.
The method according to any one of claims 33 to 36, wherein the node information of the virtual node includes at least one of node identification information of the virtual node, and security domain identification information of the virtual node.
The apparatus of claim 37, wherein the node information of the virtual node further comprises: cloud agent attribute information of the virtual node;

the cloud agent attribute information is used for indicating that the virtual node is an agent node of the cloud.
The apparatus according to any one of claims 33 to 38, further comprising:

and the address sending module is used for sending the address of the cloud platform equipment to the target source equipment.
The apparatus according to any one of claims 33 to 39, wherein the identifier obtaining module is configured to receive node information of the virtual node sent by the cloud platform device.
The apparatus of any one of claims 33 to 40, wherein,

The security domain identification information of the virtual node is generated by the configuration device;

or alternatively

The security domain identification information of the virtual node is generated and transmitted by the cloud platform device.
A subscription configuration apparatus, the apparatus comprising:

The node creation module is used for creating a virtual node in the cloud platform equipment;

the device comprises an identification sending module, a configuration device and a target source device, wherein the identification sending module is used for sending node information of the virtual node to the configuration device so that the configuration device sends a first configuration instruction comprising the node information of the virtual node to the target source device;

The first configuration instruction is used for configuring node information of the virtual node to the target source equipment; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.
The apparatus of claim 42, wherein the first configuration instructions are configured to configure the virtual node as a node having subscription rights to the target source device.
The apparatus of claim 42 or 43, wherein the first configuration instructions are further configured to write node information of the virtual node in a valid proxy cluster of the target source device.
The apparatus of any one of claims 42 to 44, wherein the node information of the virtual node includes at least one of node identification information of the virtual node, and security domain identification information of the virtual node.
The apparatus of claim 45, further comprising:

The first identifier obtaining module is used for obtaining the node information of the virtual node generated by the virtual node before the identifier sending module sends the node information of the virtual node to the configuration equipment when the node information of the virtual node comprises the node identifier information of the virtual node.
The apparatus of claim 45, wherein the node creation module is configured to,

Generating node identification information of the virtual node;

And creating the virtual node according to the node identification information of the virtual node and the security domain identification information of the virtual node.
The apparatus of claim 47, wherein the device comprises,

The security domain identification information of the virtual node is generated and transmitted by the configuration equipment;

or alternatively

The security domain identification information of the virtual node is generated by the cloud platform device.
The apparatus of any one of claims 42 to 48, further comprising:

The connection establishment module is used for establishing session connection with the target source equipment;

The binding module is used for binding the session connection with the source identification information; the source identification information is used to indicate the target source device.
The apparatus of claim 49, further comprising:

And the second identifier acquisition module is used for acquiring the source identifier information from the device certificate of the target source device before the binding module binds the session connection with the source identifier information.
The apparatus of claim 50, further comprising:

And the notification module is used for sending a notification message to the client device, wherein the notification message is used for indicating that the target source device is the source device to which the virtual node can subscribe in a proxy mode.
The apparatus of claim 51, wherein the apparatus further comprises:

and the information configuration module is used for configuring the source identification information to the virtual node before the notification module sends the notification message to the client device.
The apparatus of claim 52, wherein the notification module is configured to send the notification message to the client device via the virtual node.
The apparatus of claim 52, wherein the information configuration module is configured to,

Inquiring identification information of a cloud agent supported by the target source equipment to obtain node information of the virtual node;

Inquiring the virtual node according to the node information of the virtual node;

and configuring the source identification information to the queried virtual node.
The apparatus of claim 54, wherein the information configuration module is configured to,

Reading an effective agent list from the target source equipment, wherein the effective agent list comprises identification information of each effective agent of the target source equipment;

Acquiring node information which is the virtual node from the identification information of each effective agent of the target source equipment, wherein the identification information corresponds to cloud agent attribute information; the cloud agent attribute information is used for indicating that the virtual node is an agent node of the cloud.
The apparatus of claim 52, wherein the information configuration module is configured to,

Acquiring security domain identification information of the target source equipment;

inquiring the virtual node according to the security domain identification information;

and configuring the source identification information to the queried virtual node.
The apparatus of any one of claims 49 to 56, further comprising:

a subscription request receiving module, configured to receive a subscription request sent by a client device, where the subscription request includes the source identification information;

the connection inquiry module is used for inquiring the session connection bound with the source identification information;

And the subscription module is used for initiating proxy subscription to the target source equipment through the session connection.
A subscription configuration apparatus, the apparatus comprising:

the configuration instruction receiving module is used for receiving a first configuration instruction which is sent by the configuration equipment and comprises node information of the virtual node; the virtual node is established in cloud platform equipment;

The node configuration module is used for configuring node information of the virtual node in the target source equipment according to the first configuration instruction; the node information of the virtual node is used for subscribing the target source equipment by the virtual node.
The apparatus of claim 58, wherein the apparatus further comprises:

and the permission configuration module is used for configuring the virtual node as a node with subscription permission for the target source equipment according to the first configuration instruction.
The apparatus of claim 58 or 59, wherein the configuration instruction receiving module is further configured to receive a second configuration instruction sent by the configuration device;

The apparatus further comprises:

And the writing module is used for writing the node information of the virtual node in the effective proxy cluster of the target source equipment according to the second configuration instruction.
The apparatus of claim 58 or 59, wherein the first configuration instruction is further configured to write node information of the virtual node in a valid proxy cluster of the target source device.
The apparatus of any one of claims 58 to 61, wherein the node information of the virtual node includes at least one of node identification information of the virtual node, and security domain identification information of the virtual node.
The apparatus of claim 62, wherein the node information of the virtual node further comprises: cloud agent attribute information of the virtual node;

the cloud agent attribute information is used for indicating that the virtual node is an agent node of the cloud.
The apparatus of any one of claims 58 to 63, wherein the apparatus comprises:

the address receiving module is used for receiving the address of the cloud platform device, which is sent by the configuration device;

And the connection establishment module is used for establishing session connection with the cloud platform equipment according to the address of the cloud platform equipment.
A computer device comprising a processor, a memory, and a transceiver;

the memory has stored therein a computer program, which is executed by the processor to cause the computer device to implement the subscription configuration method as set forth in any one of the preceding claims 1 to 32.
A computer readable storage medium having stored therein a computer program for execution by a processor to implement a subscription configuration method as claimed in any one of claims 1 to 32.
A chip for running in a computer device to cause the computer device to perform a subscription configuration method as claimed in any one of claims 1 to 32.
A computer program product, the computer program product comprising computer instructions stored in a computer readable storage medium; a processor of a computer device reads the computer instructions from the computer readable storage medium and executes the computer instructions, causing the computer device to perform the subscription configuration method as claimed in any one of claims 1 to 32.
A computer program, characterized in that it is executed by a processor of a computer device to implement a subscription configuration method as claimed in any one of claims 1 to 32.