WO2023205988A1 - Method and apparatus for transmitting control information - Google Patents

Abstract

Provided are a method for transmitting control method, a relay device, a client device, a service device, and a configurator. The method comprises: a first relay device receives control information sent by a client device, the control information being used for controlling a first service device; and the first relay device sends the control information to the first service device. The client device can send the control information to a service device by means of a relay device (also known as the "first relay device"), such that even when the client device is disconnected from a communication network where the service device is located, the client device can send the control information to the service device by means of the relay device, so as to control the service device, thereby improving the user experience.

Description

Method and device for transmitting control information Technical field

The present application relates to the field of communication technology, and more specifically, to methods and devices for transmitting control information.

Background technique

The client device can send control information to the service device through the network to control the service device. However, when the client device leaves the communication network (eg, home network) where the service device is located, the client device can no longer control the service device, resulting in a lower user experience.

Contents of the invention

This application provides a method for transmitting control information, a first relay device, a client device, a first service device and a configuration device to improve user experience.

In a first aspect, a method for transmitting control information is provided, including: a first relay device receiving control information sent by a client device, the control information being used to control the first service device; The first relay device sends the control information to the first service device.

A second aspect provides a method for transmitting control information, including: a client device sending control information to a first service device through a first relay device, the control information being used to control the first service device .

In a third aspect, a method for transmitting control information is provided, including: a first service device receiving control information sent by a client device through a first relay device, and the control information is used to transmit control information to the first service device. control.

In a fourth aspect, a method for transmitting control information is provided, including: a configuration device sends second configuration information to a target device, where the second configuration information is used to configure a first relay device to provide control information for a first service device. Relay service, wherein the target device is the first relay device and the first service device, and the control information is used by the client device to control the first service device.

In a fifth aspect, a relay device (also known as "first relay device") is provided, including: a receiving unit configured to receive control information sent by a client device, where the control information is used to provide the first service The device performs control; a sending unit is configured to send the control information to the first service device.

A sixth aspect provides a client device, including: a sending unit configured to send control information to a first service device through a first relay device, where the control information is used to control the first service device.

In a seventh aspect, a service device (also called "first service device") is provided, including: a receiving unit configured to receive control information sent by a client device through a first relay device, where the control information is used to The first service device is controlled.

In an eighth aspect, a configuration device is provided, including: a sending unit configured to send second configuration information to a target device, where the second configuration information is used to configure a first relay device to provide control information relay for a first service device. Service, wherein the target device is the first relay device and the first service device, and the control information is used by the client device to control the first service device.

In a ninth aspect, a relay device (also called "first relay device") is provided, including a processor, a memory, and a communication interface. The memory is used to store one or more computer programs, and the processor is used to call The computer program in the memory causes the terminal device to perform some or all of the steps in the method of the first aspect.

In a tenth aspect, a client device is provided, including a processor, a memory, and a communication interface. The memory is used to store one or more computer programs. The processor is used to call the computer program in the memory so that the terminal The device performs some or all of the steps of the method of the second aspect.

In an eleventh aspect, a service device (also called "first service device") is provided, including a processor, a memory and a communication interface. The memory is used to store one or more computer programs, and the processor is used to call the The computer program in the memory causes the terminal device to perform some or all of the steps in the method of the third aspect.

A twelfth aspect, a configuration device is provided, including a processor, a memory and a communication interface, the memory is used to store one or more computer programs, the processor is used to call the computer program in the memory so that the terminal The device performs some or all of the steps in the method of the fourth aspect.

In a thirteenth aspect, embodiments of the present application provide a communication system, which includes the above-mentioned relay device, client device, service device, and configuration device. In another possible design, the system may also include other devices that interact with the above-mentioned device in the solutions provided by the embodiments of the present application.

In a fourteenth aspect, embodiments of the present application provide a computer-readable storage medium that stores a computer program, and the computer program causes the terminal to perform some or all of the steps in the methods of the above aspects.

In a fifteenth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause the terminal to execute the above Some or all of the steps in various aspects of the method. In some implementations, the computer program product can be a software installation package.

In a sixteenth aspect, embodiments of the present application provide a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects. .

The client device can send control information to the first service device through the first relay device. In this way, even when the client device leaves the communication network where the service device is located, the client device can send control information to the first service device through the first relay device. The device sends control information to control the first service device to improve user experience.

Description of the drawings

Figure 1 is a model structure of a Matter device applicable to the embodiment of this application.

Figure 2 is a schematic diagram of a communication system applicable to the embodiment of the present application.

Figure 3 is a schematic diagram of a communication system to which the proxy mechanism is applicable.

Figure 4 is a flow chart of a method for transmitting control information according to an embodiment of the present application.

Figure 5 is a schematic diagram of a communication system applicable to the embodiment of the present application.

Figure 6 is a flow chart of a method for transmitting control information according to an embodiment of the present application.

Figure 7 is a flow chart of a method for transmitting control information according to another embodiment of the present application.

Figure 8 is a flow chart of a method for transmitting control information according to another embodiment of the present application.

Figure 9 is a schematic diagram of a relay device according to an embodiment of the present application.

Figure 10 is a schematic diagram of a client device according to an embodiment of the present application.

Figure 11 is a schematic diagram of a service device according to an embodiment of the present application.

Figure 12 is a schematic diagram of a configuration device according to an embodiment of the present application.

Figure 13 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed ways

The technical solutions in this application will be described below with reference to the accompanying drawings. For ease of understanding, terminology involved in the embodiments of the present application is introduced below with reference to Figures 1 to 1 . It should be noted that the following uses the Matter protocol scenario as an example to introduce the terminology involved in the embodiments of the present application and the solutions of the embodiments of the present application. Of course, the solutions in the embodiments of this application can also be applied to other Internet of Things protocols.

The Internet of things (IoT) is the "Internet where everything is connected". It is a network that is extended and expanded based on the Internet. It can connect any item through various information sensing devices (such as radio frequency identification, global positioning system, etc.) Connected to the Internet to form a huge network for information exchange and communication to achieve interconnection among all things. In some embodiments, IoT devices may be smart home devices. For example, IoT devices may include smart air conditioners, smart refrigerators, washing machines, rice cookers, sweeping robots, and other devices. In some embodiments, the IoT device may be an intelligent monitoring device. For example, the IoT device may include a surveillance camera, a temperature sensor, a sound sensor, etc.

At present, different manufacturers may use different communication protocols (also called ecological chain protocols) to achieve interconnection and interoperability between IoT devices that support this communication protocol. This may cause IoT devices produced by different manufacturers to be unable to communicate with each other. The true Internet of Everything cannot be achieved.

Based on this, the Connectivity Standards Alliance (CSA) launched an Internet of Things application layer technology standard—Matter Standard Protocol, which can provide an interoperable application layer for smart home devices based on Internet Protocol (Internet Protocol, IP) solution. In some embodiments, the matter standard may also be called a connected home over IP (CHIP) standard. In some embodiments, the Matter standard can support three underlying communication protocols: Ethernet, Wi-Fi, and Thread, and can allow IoT devices with different protocols to communicate with each other.

Matter device model

Figure 1 is a model structure of a Matter device applicable to the embodiment of this application. The data model structure 100 of the Matter device includes a node 110, an endpoint 120, and a cluster 130.

Node 110 encapsulates an addressable and unique resource on the network and has a set of functions and capabilities that users can clearly view as a functional whole. Typically, node 110 may be the highest or outermost first-order element in the data model. In other words, node 110 is the only addressable element in the outermost layer of the data model.

It should be noted that one physical entity (for example, Matter device) can support multiple nodes 110 . In addition, a node can have multiple node IDs, and the scope of each node ID is a specific network (fabric). For example, when a node ID is used as the target address for an interaction, the network within the scope of the specified node ID is the access network for the interaction. A node may include one or more endpoints 120. Endpoint 120 is an instance, which can be a service or a virtual device, as indicated by the device type. Each endpoint 120 conforms to one or more device type definitions that define the clusters supported on the endpoint. Whereas a cluster is an object class instantiated on an endpoint.

It should be noted that in this architectural model, the above device types can be the highest semantic elements. A device type defines a consistent set of endpoints 120. A device type defines a set of requirements for a node 110 or endpoint 120.

Clusters 130 are functional building block elements of the data model, and therefore clusters may also be referred to as "functional sets." The cluster specification defines clients and servers that interact with each other. Cluster 130 can be viewed as an interface, service or object class, which is the lowest independent functional element in the data model. Each cluster 130 is defined by a cluster specification that defines the elements of the cluster 130, including properties, events, commands, and behaviors related to interactions with these elements. Properties, events, commands, and behaviors in cluster 130 are mandatory or optional depending on the definition of cluster 130 .

Generally, the above clusters can be divided into two categories: utility cluster (utility cluster) or application cluster (application cluster). Utility clusters are not part of the endpoint's primary application operations. It can be used for configuration, discovery, addressing, diagnostics, monitoring device health, software updates, and more. It may have a temporary relationship with its cluster counterpart. In this embodiment of the present application, the utility cluster may include one or more of a relay configuration cluster, an effective relay cluster, and a relay discovery cluster.

Application clusters (also known as "business clusters") support the primary operations of endpoints. Application clustering supports one or more persistent application interactions between clustered clients and clustered servers. For example, in a switch cluster (On/Off cluster) in a smart light, the client of the cluster can send control commands to the server of the cluster (i.e., switch cluster) to control the switch of the smart light.

A cluster command (also known as a "command") is a set of data fields, each data type, that is passed between client and server cluster instances to invoke the behavior of the command recipient. Currently, the agreement stipulates that each command can be listed in a table, which can contain the data quality columns of the command: identification (ID), name (name), direction (direction), response (response), access (access) ), constraint consistency. Accordingly, a command can indicate zero or more fields defined in a table. Each command field is defined as a row in the table.

Properties are cluster data. Currently, it is agreed in the agreement that each attribute can be listed in a table, and the data quality columns can include ID, name, (data) type, constraints, other qualities, access, default (value) and consistency. In some implementations, properties may also define their associated semantics and behavior. Properties can reflect the device's queryable/settable status, configuration, and capabilities. In some cases, if no privileges are explicitly defined for a property, default access privileges take effect.

For ease of understanding, the following describes the meanings of several common data qualities contained in commands and properties. It should be noted that the commands and attributes in the embodiments of this application may also include other quantitative qualities, or include part of the above-mentioned data qualities. The embodiments of the present application do not limit this.

Identification represents the unique field ID of the field, or in other words, it is the unique identification of the command.

Name represents the unique name of the field, or in other words, the name of the command.

Type, indicating the data type of the field (or command).

Direction, usually present in the command list, is used to define the transmission direction of the command. For example, it can be defined as from client to server. For another example, it can be determined from the server to the client.

Access permissions are used to define how an element can be accessed (such as read or write) and what permissions are required to access the data.

In some implementations, access rights may include V, where V indicates that read access or call access requires view privileges. Access permissions can also include O, which means "read access", "write access" or "call access" require operation permissions. Access permissions can also include R, which stands for read access. Access permissions can also include W, which represents write access.

Response, usually present in the command list, is used to define the response message of the command.

Quality, used to define additional data quality not covered in other columns.

Default, used to define the default value. It should be noted that the default value is not the value used when the service device returns to the factory refresh settings. The default value can indicate that the consistency specified for the data field can be optional or change over time. Default values can be defined to complete the dependency when the actual data field value is not present.

Consistency defines the optionality and dependencies of any data model element or set of elements.

Typically, this column is valid for properties, commands, events, enumerations, and fields of commands, events, or structures. In some implementations, "M" indicates that the corresponding command is part of the basic mandatory feature set.

For commands, client-to-server command consistency means that the server should recognize and support client-to-server commands and generate responses as defined. Server-to-client command consistency means that the server should send commands in a manner defined by cluster behavior, i.e., in response to client-to-server commands. The consistency of the command depends on the supported server features. Clients should not be required to support optional commands or commands that rely on optional features.

Constraints, including all and desc. Among them, all is defined in the numeric data type to allow all values. desc indicates that the constraint is defined in the description section.

Range, including "N/A" means not applicable.

Communication system based on Matter protocol

The communication system applicable to the embodiment of the present application is introduced below with reference to FIG. 2 . The communication system shown in Figure 2 includes a Matter client 210, a Matter service device 220, and a configuration device 230. It should be noted that the data model of the Matter client 210 and the Matter service device 220 can be as shown in Figure 1 .

The configuration device 230 is used to configure the Matter service device 220. In some implementations, the configuration device 230 may be an application (application, APP) or applet. In other implementations, the configuration device 230 can be installed on a terminal device, where the terminal device can be a mobile phone, a computer, a tablet, a smart bracelet, a smart watch, etc. This is not limited in the embodiments of the present application.

The Matter client 210 is a client on the user side, and the Matter client 210 can communicate with the Matter service device 220 . In some implementations, the Matter client 210 can send control information to the Matter service device 220 to control the Matter service device 220 . For example, when the Matter service device 220 is a smart air conditioner, the Matter client 210 can control the temperature adjustment of the Matter service device 220 by sending control information to the Matter service device 220 .

In some embodiments, the above-mentioned Matter client 210 may be an application (application, APP) or applet, etc. In other implementations, the Matter client 210 can be installed on a terminal device, where the terminal device can be a mobile phone, a computer, a tablet, a smart bracelet, a smart watch, etc. This is not limited in the embodiments of the present application.

It should be noted that the above configuration device 230 may be the same APP or applet as the Matter client 210. Of course, the configuration device 230 may be a different APP or applet from the Matter client 210. The embodiments of the present application do not limit this.

The matter service device 220 may refer to an Internet of Things device that supports the matter standard protocol. The Matter service device 220 can directly communicate with the Matter client 210, so that the Matter client 210 controls the Matter service device 220.

For example, when the Matter service device 220 is a smart air conditioner that supports the Matter standard protocol, the Matter client 210 can control the switch of the smart air conditioner and set the air conditioner temperature, wind speed, etc. When the Matter service device 220 is a sweeping robot that supports the matter standard protocol, the Matter client 210 can control the sweeping robot to start or stop working, control the working mode of the sweeping robot, etc.

Currently, the control interfaces supported by the Matter service device 220 mainly include control and subscribe and report.

Among them, control can be understood as a group of clusters that can modify or retrieve one or more attribute values of the Matter service device. For example, the Matter client is a smart speaker and the Matter service device is a smart air conditioner. Alice can say "cool down" to the smart speaker, and then the smart speaker sends a control command to lower the temperature to the smart air conditioner.

Utilize the subscription interaction model to define the properties that can be subscribed and the requirements for subscription, such as trigger thresholds, reporting intervals and durations, etc. For example, the Matter client is a smart speaker, the Matter service device is a smart air conditioner, and Alice can subscribe to the indoor temperature measured by the air conditioner sensor through the smart speaker. At this point, she can monitor the indoor temperature by receiving periodic reports.

Proxy mechanism provided for subscription operations

In some cases (for example, the Matter service device has insufficient resources), the Matter service device cannot directly handle the subscription request, and a proxy mechanism can be used to help the Matter service device process the subscription request. In other words, the proxy service can realize the proxy capability of subscribing to resources in the Matter service device.

Referring to Figure 3, proxy services usually involve Matter clients, source Matter service devices, and proxy devices. Among them, the source Matter service device refers to the node that is the original source of a set of data authenticity. The source Matter service device can act as a publisher of data. Matter client refers to the node that wants to subscribe to a source Matter service device. The feed proxy device can "mirror" the data of the source Matter service device to the Matter client, and for the Matter client, no matter whether it interacts with the proxy device or the source Matter service device, the Matter client does not need to change its interaction.

Generally, from the perspective of the Matter client, the proxy process can include the following processes: discovering that the Matter service device requires a proxy; finding a proxy on the network that can handle its subscription request; setting up the proxy to subscribe to the Matter service device.

During the proxy setup process, a Matter service device can indicate its capabilities as a certified Matter proxy by declaring support for the subscribing proxy device type. When configuring such a Matter service device, the configuration device should recognize this capability and can write the node IDs of all Matter service devices that require a proxy to the proxy configuration cluster on the proxy device. Alternatively, it can be configured to wildcard proxy all Matter service devices, eliminating the need to specify a specific set of node IDs.

In addition, the configuration device can write the node ID of the newly added agent to a valid agent cluster on the Matter service device that requires the agent. The cluster can store a static list of candidate agents for a given device. Typically, this configuration needs to be written for the Matter service device that supports the cluster.

In some cases, subscriptions may be declined. Since there is no a priori heuristic that can be used to infer whether the Matter service device requires a proxy. So when the Matter service appliance cannot handle more incremental subscriptions, that's when a proxy is needed. When the Matter client tries to subscribe to the Matter service device, it will find that the subscription cannot be processed and return a StatusResponse, which will contain an IM status code indicating that the resources of the Matter service device have been exhausted. At this time, the Matter service device cannot process the subscription request.

After receiving the IM status code, the Matter client can call get valid proxies request on the Matter service device. In response, the Matter client can receive a get valid proxies response (get valid proxies response) sent by the Matter service device, where the get valid proxies response contains the node ID of the valid proxy.

During the proxy discovery process, after the Matter client receives the valid proxy list, the Matter client can try to discover a valid proxy that can proxy its subscription request. In some implementations, the Matter client can send the agent discovery request as a multicast message to the group to which all agents belong. It should be noted that before transmitting this message, the Matter client should immediately subscribe to the IPv6 address mapped to this group to receive the response sent by the agent (i.e., the agent discovery response).

During the proxy response process, the proxy should only send a proxy discovery response if it is able to handle the subscription request. It should be noted that the agent can send an agent discovery response regardless of whether it is currently subscribed to the Matter service device. Additionally, the broker discovery response may contain metadata indicating the broker's ability to handle subscriptions.

It should be noted that the proxy discovery response should be sent as completely independent and unrelated information from the original request (the proxy discovery request). The Matter client can associate the two messages based on the source node identifier (SourceNodeId) of the Matter service device in the two messages.

During the proxy selection process, Matter clients should wait for a proxy scan cycle to aggregate all responses, and filter the set of responses received.

During the proxy subscription process, a Matter client can subscribe to the proxy of its choice. Accordingly, the agent can do one of two things: Option 1: If no other agent is already subscribed to the Matter service device, the agent will subscribe directly to the Matter service device: Option 2: If there is already another agent subscribed to the Matter service device, The selected agent will be subscribed to the agent.

It should be noted that the agent does not attempt to subscribe to the Matter service device directly because the agent does not know whether the Matter service device has any available slots to support the subscription. If it does so, it may cause the subscription to fail.

In some implementations, an agent can choose between these two options by "sniffing" "Agent Discovery Response" command messages issued by other agents. This allows the candidate agent to determine if there is another agent subscribed to the Matter service device.

Regardless of the number of subscription requests from a Matter client to a given Matter service device, the proxy can only subscribe to that Matter service device once. This is necessary to ensure timely execution of the ACL in the event that a Matter client no longer has access to the Matter service device, and subsequent state changes will not be available to that Matter client.

In some cases, the Matter service appliance may evict some Matter client subscriptions. For example, the Matter service appliance may not be able to handle another subscription, and the Matter service appliance cancels the non-agent subscription to make room for the agent subscription.

The commands and attributes in the cluster involved in the above proxy mechanism are introduced below in conjunction with Table 1 to Table 8. It should be noted that the meanings of some data quality columns of commands and attributes (for example, access, consistency, default, constraints, etc.) have been explained in detail above. For the sake of brevity, they will not be repeated below. Tables 1 through 3 show the commands and properties included in the agent discovery cluster.

Table 1

Referring to Table 1, the commands included in the agent discovery cluster include agent discovery requests and agent discovery responses. The transmission direction of the proxy discovery request is from the client to the service device, and the response to the proxy discovery request is the proxy discovery response. The transmission direction of the proxy discovery response is from the server to the client, and the response of the proxy discovery response is None.

Table 2

ID Field type constraint quality default consistency 0 SourceNodeId node-id all ​ ​ M 1 NumAttributePaths uint16 desc ​ ​ M 2 NumEventPaths uint16 desc ​ ​ M

Refer to Table 2, which shows the parameters that can be carried in the discovery proxy request. Among them, the field "SourceNodeId" is the node ID of the source Matter service device. The field "NumAttributePaths" indicates the number of attribute paths to be subscribed by the Matter client. The field "NumEventPaths" indicates the number of event paths to be subscribed by the Matter client.

table 3

ID Field type constraint quality default consistency 0 SourceNodeId node-id all ​ ​ M 1 NumHopsToSource uint16 desc ​ ​ M 2 AvailableCapacity uint16 desc ​ ​ M

Refer to Table 3, which shows the parameters that can be carried in the discovery agent response. Among them, the field "SourceNodeId" is the node ID of the source Matter service device. The field "NumHopsToSource" indicates the number of hops that the agent subscribes to the source Matter service device. When the agent directly subscribes to the source Matter service device, the value is 1. The field "AvailableCapacitys" indicates how much space the broker has left to support subscriptions to cluster properties.

Tables 4-5 show the properties included in the agent configuration cluster. Proxy configuration clustering provides a way for a proxy-capable device to be informed of the set of nodes (Matter service devices) it will proxy to.

Table 4

ID name type constraint quality access default consistency 0 Configuration list list[ConfigurationStruct] all N RW null M

Referring to Table 4, the properties included in the proxy configuration cluster are configuration lists. The configuration list can store in the form of a list the node identification of the Matter service device that the proxy can provide proxy services for subscription requests.

table 5

ID name type constraint quality access default consistency 0 FabricIndex fabric-idx all ​ RW 0 M 1 ProxyAllNodes bool desc ​ RW false M 2 SourceList list[nodeid] desc ​ RW empty M

Referring to Table 5, the data type of the list may specifically include the following attributes. The attribute "FabricIndex" represents the identifier of the interwoven network where the proxy and Matter service devices are located. The attribute "SourceList" is the list of source Matter service devices being proxied. Attributes

"ProxyAllNodes" being true means that the proxy can proxy all nodes, in which case the SourceList attribute should be ignored. If the attribute "ProxyAllNodes" is false, it means that the proxy cannot proxy all nodes, but can only proxy the source Matter service devices in the SourceList.

Tables 6 through 8 show the properties and commands contained by a valid agent cluster. Valid proxy clustering provides a way for Matter serving devices to inform the Matter serving device of valid proxies.

Table 6

ID name type scope quality access default consistency 0 Valid proxy list list[ValidProxyStruct] N/A N RW empty M

Referring to Table 6, the attribute name contained in the valid proxy cluster is valid proxy list (ValidProxyList), and its data type is list.

Table 7

ID name type constraint quality access default consistency 0 FabricIndex fabric-idx all ​ RW ​ M 1 NodeID node-idx all ​ RW ​ M

See Table 7, attribute "FabricIndex" Matter The identifier of the interwoven network where the service device and agent are located. The attribute "NodeID" represents the node ID of the effective agent that the agent subscribes to the Matter service device.

Table 8

Referring to Table 8, the commands included in the effective proxy cluster include obtaining effective proxy requests and obtaining effective proxy responses. Among them, the transmission direction of obtaining a valid proxy request is from the client to the service device, and the response to obtaining a valid proxy request is obtaining a valid proxy response. The transmission direction to obtain a valid proxy response is from the server to the client, and the transmission direction to obtain a valid proxy response is None.

In the current Internet of Things protocol (for example, Matter protocol), the client can send control to the service device through the communication network to control the service device (also known as the "first service device"). However, when the client device leaves the communication network (eg, home network) where the service device is located, the client device can no longer control the service device, resulting in a lower user experience.

In order to avoid the above problems, embodiments of the present application provide a solution for transmitting control information. The client device can send control information to the first service device through the first relay device, or in other words, the first relay device can provide control The information relay service enables the control information sent by the client device to be sent to the first service device through the relay link provided by the control information relay service. In this way, even when the client device leaves the communication network where the first service device is located, the client device can send control information to the first service device through the first relay device to control the first service device to improve user experience. .

The flow of the method for transmitting control information according to the embodiment of the present application is introduced below with reference to FIG. 4 . The method shown in Figure 4 includes step S410 and step S420.

In step S410, the client device sends control information to the first relay device.

In step S420, the first relay device sends the control information to the first service device.

As introduced above, the first relay device can send the control information sent by the client device to the first service device. Therefore, the first relay device usually has the ability to connect to the network. In other words, the first relay device can be any device with network connection capabilities. For example, routers, smart speakers, etc.

In order to facilitate understanding of the method of the embodiment of the present application, the following will first introduce the stage of establishing the control information relay service in which the first relay device provides control information for the first service device, that is, the establishment stage of the control information relay service.

In order to further improve the user experience, when the first relay device receives the control information, it can promptly feed back the response result given by the first service device in response to the control information to the client device. The control information control can be set in the first relay device. The first service device in the business cluster. That is, assuming that the control information is used to control the first service cluster in the first service device, the first relay device may include a target cluster, and the target cluster is the same as the first service cluster.

The above target cluster is the same as the first business cluster. It can be understood that the control functions supported by the target cluster are the same as the control functions supported by the first business cluster. In some implementations, the service list and command list included in the target cluster are the same as the service list and command list included in the first service cluster.

There are many ways to configure the above target cluster to be the same as the first service cluster. For example, the first relay device can read the node, endpoint and business cluster information of the first service device, and then send a subscription request to the first service device. , to request to subscribe to the business list and command list of the above-mentioned first business cluster. Correspondingly, after the first service device allows it, the first service device may send the service list and the command list of the first service cluster to the first relay device.

In order to improve resource utilization of the first relay device, the first relay device may provide control information relay services for multiple service devices. Therefore, a cluster of multiple service devices may be set in the first relay device. In some implementations, the first relay device may be provided with multiple virtual nodes, each virtual node corresponds to a node of the service device, and the virtual node is provided with a cluster having the same function as the service cluster in the service device node. That is to say, the target cluster in the first relay device can be set in a virtual node, and the virtual node corresponds to the node where the first cluster is located, or in other words, the endpoint contained in the virtual node is the same as the endpoint where the first cluster is located. The endpoints are the same. In other implementations, the above virtual node may be generated by the first relay device.

Referring to Figure 5, it is assumed that relay device 1 can provide control information relay services for service device 1 and service device 2, and the control information relay service provided by relay device 1 for service device 1 is for the business cluster in service device 1. 1, business cluster 1 is located in endpoint EP1 in node 1 in service device 1. In addition, the control information relay service provided by the relay device 1 to the service device 2 is for the service cluster 2 in the service device 2. The service cluster 2 is located in the endpoint EP1 in the node 0 in the service device 2.

Therefore, the relay device 1 includes two virtual nodes, virtual node 0 and virtual node 1. The virtual node 0 corresponds to the service device 1, and the virtual node 0 is configured with the endpoint EP1 in the node 1 and the target cluster 1, where the target cluster 1 can be the same as the business cluster 1. Virtual node 1 corresponds to service device 2, and virtual node 1 is provided with endpoint EP1 in node 0 and target cluster 2, where target cluster 2 can be the same as business cluster 2.

In some scenarios, different client devices may have different permissions to access the first service device. Therefore, in order to prevent the first relay device from relaying control information sent by a client device that does not have control permissions to the first service device, That is, unnecessary control information relay services are provided, and the same control authority as that of the node where the first cluster is located can be set for the virtual node of the first relay device.

In some implementations, the first relay may store an ACL of the first service device, where the ACL of the first service device is used to record whether the client device has the authority to control the first service device, or in other words, the first service device The ACL of the device is used to record whether the client device has the permissions required to control the first service device through the above control information. Furthermore, the virtual node of the first relay device can be associated with the ACL. Accordingly, before step S420, the above method further includes: the first relay device queries the ACL to determine that the client device has the authority to control the first service device. In other words, when it is determined based on the ACL that the client device has the authority to control the first service device, the first relay device sends control information to the service device.

There are many ways for the first relay device to obtain the ACL of the first service device. For example, the first relay device may send a subscription request to the first service device to request to subscribe to the ACL of the first service device. Correspondingly, after the first service device allows it, the first service device sends the ACL of the first service device to the first relay device.

The above describes the process of the first relay device providing the control information relay service with reference to Figure 4, and Figure 5 introduces the establishment phase of the control information relay service according to the embodiment of the present application. The following describes the configuration phase of the control information relay service and the triggering phase of the control information relay service in the embodiment of the present application with reference to the figures. Generally, the configuration phase of the control information relay service may be executed before the establishment phase of the control information relay service, and the triggering phase of the control information relay service may be executed after the establishment phase of the control information relay service.

In the configuration phase of the control information relay service, the user can configure the first relay device through the configuration device. For example, the configuration device can send the first configuration information to the first relay device to configure the first relay device as The first service device provides a control information relay service. In some implementations, the first configuration information may include an identification of the first service device.

Correspondingly, in order to provide a configuration interface for the configuration device, a first cluster may be set in the first relay device, where the first cluster is used to configure one or more devices that need to provide control information relay services for the first relay device. service devices, wherein one or more service devices include a first service device. Therefore, the above-mentioned first cluster can also be called "relay configuration cluster (relay configuration cluster)".

In some implementations, service devices that the first relay device can provide control information relay services may be recorded in a list in the relay configuration cluster. For example, the list may be called a "target list", and the node IDs of all service devices that the first relay device can provide control information relay services are recorded in the target list.

The above-mentioned relay configuration cluster may include the identification of the interwoven network where one or more service devices are located, so that when configuring the service device that the first relay device can provide control information relay services, the user can choose to be located in the same location as the first relay device. Service equipment on the same interwoven network.

It should be noted that since the first relay device needs to communicate with the service device, that is to say, the first relay device and the service device are usually located in the same interwoven network. Therefore, the above identification of the interwoven network can also be understood as The identification of the interwoven network where the service device is located.

Generally, a relay device located in the cloud can provide a wide range of control information relay services. Therefore, the relay configuration cluster includes first indication information to indicate whether the first relay device is located in the cloud, so that the user can configure it more reasonably. The first relay device may provide a service device that controls information relay service. In some implementations, when the first indication information indicates whether the first relay device is located in the cloud, the first indication information may be indicated by a Boolean value. For example, when the Boolean value is true, the first indication information indicates that the first relay device runs on the cloud platform. When the Boolean value is false, the first indication information indicates that the first relay device does not run on the cloud platform. Of course, in this embodiment of the present application, the first indication information may also indicate whether the first relay device is running on the cloud platform through a bitmap. The embodiments of the present application do not limit this.

In addition, there is a relay device with strong relay capability that can provide control information relay services for all service devices in the network. Therefore, the relay configuration cluster includes second indication information, where the second indication information is used to Indicates whether the first relay device can provide control information relay services for all service devices in the network where the first relay device is located, so that the user can more reasonably configure service devices where the first relay device can provide control information relay services. . In some implementations, the second indication information may use a Boolean value to indicate whether the first relay device can provide control information relay services for all service devices in the network. For example, when the Boolean value is true, the second indication information indicates that the first relay device can provide control information relay services for all service devices in the network. When the Boolean value is false, the second indication information indicates that the first relay device cannot provide control information relay services for all service devices in the network. Of course, in this embodiment of the present application, the second indication information may also indicate through a bitmap that the first relay device can provide control information relay services for all service devices in the network. The embodiments of the present application do not limit this.

It should be noted that if the second indication information indicates that the first relay device can provide control information relay services for all service devices in the network, at this time, the target list in the relay configuration cluster becomes invalid. Otherwise, if the second indication information indicates that the first relay device cannot provide control information relay services for all service devices in the network, at this time, the target list in the relay configuration cluster is valid, that is, the first relay device can only Provides control information relay services for service devices in the target list.

In addition, as mentioned above, relay devices usually located in the cloud can provide a wide range of control information relay services. Therefore, the above-mentioned second indication information can be used in conjunction with the first indication information. That is to say, the above-mentioned first indication information The information may be represented by the second indication information, that is, whether the first relay device is located in the cloud may be indicated by the second indication information. For example, when the second indication information indicates that the first relay device can provide control information relay services for all service devices in the network, the first relay device is also a relay device located in the cloud. When the second indication information indicates that the first relay device cannot provide control information relay services for all service devices in the network, the first relay device is not a relay device located in the cloud at the same time.

For ease of understanding, the following uses Table 9 and Table 10 to introduce the attributes included in the relay configuration cluster, taking the relay configuration cluster in relay device 0 as an example. It should be noted that the meanings of the data quality columns (for example, access, consistency, default, constraints, etc.) included in the attributes in Tables 9 and 10 have been explained in detail above, and for the sake of brevity, they will not be repeated below.

Table 9

logo name type scope quality access default consistency 0 Configuration list list[configuration structure] all N RW null M

Referring to Table 9, the relay configuration cluster can include the identification of the attribute (ID), the name of the attribute (name), the type of the attribute (type), the range of the attribute (range), the quality of the attribute (quality), and the access of the attribute (access). ), the default value of the attribute (default), and the conformance of the attribute (conformance).

Among them, attribute ID 0 is used to identify attribute 0 in the relay configuration cluster; the name of attribute 0 is the configuration list; the type of attribute 0 is a list presented in a structure; the scope of attribute 0 is all (all); attribute 0 The quality of is none (none), the access of attribute 0 is RW; the default value of attribute 0 is empty; the consistency of the attribute is M.

Table 10

logo name type constraint quality access default consistency 0 Identification of intertwined networks web index all N RW null M 1 Relay all nodes Boolean value desc N RW false M 2 target list list[nodeid] desc N RW null M

Table 10 shows the information contained in the list presented as a structure. Referring to Table 10, the information contained in the structure includes the identification of the attribute, the name of the attribute, the type of the attribute, the scope of the attribute, the quality of the attribute, access to the attribute, the default value of the attribute and the consistency of the attribute.

The name of the attribute corresponding to attribute identifier 0 is the identifier of the interwoven network to which relay device 0 is connected. The type of this attribute is the fabric-idx.

The name of the attribute corresponding to attribute identification 1 is relay all nodes, which is used to indicate whether relay device 0 can provide control information relay services for all service devices in the network. The type of this attribute is Boolean ( bool). Generally, when the Boolean value is "true", it means that relay device 0 can provide control information relay services for all service devices in the network. When the Boolean value is "false", it means that relay device 0 cannot provide control information relay services for all service devices in the network.

The attribute name of the attribute corresponding to attribute identifier 2 is a target list, and the type of the target list is a list containing a node identifier, where the node identifier is used to indicate that the relay device can provide a service device with a control information relay service.

It should be noted that when the Boolean value of the attribute "Relay All Nodes" is true, relay device 0 can provide control information relay services for all service devices in the network. At this time, the attribute "Target List" is invalid. attribute, or can be ignored. When the Boolean value of the attribute "Relay All Nodes" is false, relay device 0 cannot provide control information relay services for all service devices in the network. At this time, the attribute "Target List" is a valid attribute, that is to say , relay device 0 can only provide control information relay services for the service device corresponding to the node ID included in the target list.

The above describes that the first relay device can provide a configuration interface through the first cluster. However, in some cases, the user may not yet know which devices in the network can provide control information relay services. Therefore, before the user configures the first relay device through the configuration device, the user needs to know that the network can provide control information. Relay equipment for relay services.

In the example of this application, in order for users to obtain relay devices that can provide control information relay services in the network, the relay devices that can provide control information relay services in the network can be divided into a relay group in advance. In this way, the user The configuration device may send a third request to the relay group in the form of a multicast message to request discovery of relay devices in the network, or in other words, the third request is used to discover relay devices that can provide control information relay services. Correspondingly, after receiving the third request, the relay device in the relay group may return a third response to the third request to the configuration device to inform the configuration device that the control information relay service can be provided. In some implementations, the above third response may carry the node identification of the relay device.

Typically, different relay devices have different connectivity capabilities. For example, some relay devices can be connected to the local area network (LAN), some relay devices can be connected to the wide area network (WAN), and some relay devices can be located in the cloud. Therefore, in order to improve the accuracy of the relay device obtained by the user, the user can carry indication information 1 (also known as "fourth indication information") in the third request. The indication information 1 is used to indicate the connection of the relay device requested to be discovered. capabilities (e.g., secondary connectivity capabilities). Correspondingly, only the relay device in the relay group that meets the connection capability can send the third response to the configuration device.

In some implementations, the above third response may carry indication information indicating the connection capability of the relay device. In other implementations, only relay devices that are configured to meet the connection capability may send the third response to the configuration device. In this case, the third response may not carry the above indication information.

For example, the third request sent by the configuration device to the relay group is used to request a relay device with WAN connection capability. At this time, the relay device in the relay group that only has LAN connection capability cannot send the third response to the configuration device. , a relay device (for example, a router) with WAN connection capability in the relay group may send a third response to the configuration device.

It should be noted that the user can determine the connection capabilities of the relay device requested to be discovered in the third request through the network where the first service device to be controlled is located. For example, if the network where the first service device is located is a LAN, then the indication information 1 in the third request indicates a request to discover a relay device with LAN connection capabilities.

As mentioned above, different relay devices have different connectivity capabilities. The above-mentioned relay device with LAN connection capability can be understood as a relay device with private network connection capability, such as a smart speaker. Generally speaking, this type of relay device can only provide control information relay services for service devices in the local area network.

The above-mentioned relay device with WAN connection capability can be understood as a relay device with external network or public network connection capability, such as a router. Generally speaking, such relay devices can connect to a home network where the first service device is located and an external network. However, such relay devices may not be able to provide control information relay services for service devices located in multiple home networks. . For example, assuming that router 1 is located in home network 1, it can provide control information relay service for service device 1 in home network 1. However, for the service device 2 located in the home network 2, the router 1 cannot provide the control information relay service for the service device 2.

The above-mentioned relay device located in the cloud (or the relay device running on the cloud platform) can be understood as a virtual device in the cloud. Generally speaking, such relay devices can connect to some or all service devices on the cloud. For such relay devices, there is no need to consider whether multiple service devices in the cloud are located in different home networks. Relay devices located in the cloud All can provide control information relay services.

The above describes the configuration process of configuring the device as the first relay device in the configuration phase of the control information relay service. Correspondingly, the configuration device also needs to configure the first service device. The following describes the configuration process of the first service device by the configuration device.

In the configuration phase of the control information relay service, the user can configure the first service device by configuring the device. In some implementations, the configuration device can send configuration information (also called "second configuration information") to the first service device to configure a relay device that can provide control information relay services for the first service device, or in other words, The second configuration information is used to configure the first relay device to provide the control information relay service for the first service device. Correspondingly, in order to provide a configuration interface for the configuration device, a second cluster can be set in the first service device, where the second cluster is used to indicate one or more valid ones that can provide the control information relay service for the first service device. The relay device, one or more effective relay devices includes the first relay device. Therefore, the above-mentioned second cluster can also be called a "valid relay cluster".

In some implementations, effective relay devices that can provide control information relay services for the first service device may be recorded in a list in the effective relay cluster. For example, the list may be called a "valid relay list", and the node ID of the valid relay device is recorded in the valid relay list.

In order to facilitate the user to select a relay device located in the same interwoven network as the first service device when configuring an effective relay device for the first service device, the above-mentioned effective relay cluster may include an identifier of the interwoven network where the first service device is located.

It should be noted that since the effective relay device needs to communicate with the first service device, the effective relay device and the first service device are usually located in the same interwoven network. Therefore, the interwoven network where the above-mentioned first service device is located The identifier can also be understood as the identifier of the interwoven network where the effective relay device is located.

As mentioned above, different relay devices may have different connectivity capabilities. Therefore, the effective relay cluster can also record the connectivity (connectivity) of each relay device in one or more effective relay devices, and each The connection capability of the relay device is used to indicate the type of network to which each relay device is connected, where the network can be understood to include networks such as LAN and WAN.

For ease of understanding, the following uses Table 11 and Table 12 to introduce the attributes contained in an effective relay cluster, taking the effective relay cluster in service device 1 as an example. It should be noted that the meanings of the data quality columns (for example, access, consistency, default, constraints, etc.) included in the attributes in Table 11 and Table 12 have been explained in detail above, and for the sake of brevity, they will not be repeated below.

Table 11

logo name type scope quality access default consistency 0 Valid relay list list [valid relay structure] N/A N RW null M

Referring to Table 11, a valid relay cluster may include the identity of the attribute, the name of the attribute, the type of the attribute, the scope of the attribute, the quality of the attribute, the access to the attribute, the default value of the attribute, and the consistency of the attribute.

Among them, the identifier 0 of the attribute is used to identify the attribute 0 in the effective relay cluster; the name of the attribute 0 is the effective relay list; the type of the attribute 0 is the effective relay list presented in the structure; the scope of the attribute 0 is N/ A; the quality of attribute 0 is none (none), the access of attribute 0 is RW; the default value of attribute 0 is empty; the consistency of attribute 0 is M.

Table 12

logo name type constraint quality access default consistency 0 Identification of intertwined networks web index all N RW null M 1 Node ID Node index all N RW null M 2 Connectivity map8 desc N RW null M

Table 12 shows the information contained in the valid relay list presented as a structure. Referring to Table 12, the information contained in the structure includes the identification of the attribute, the name of the attribute, the type of the attribute, the scope of the attribute, the quality of the attribute, access to the attribute, the default value of the attribute and the consistency of the attribute.

The name of the attribute corresponding to attribute identifier 0 is the identifier of the interwoven network to which relay device 0 is connected. The type of this attribute is fabric-idx.

It should be noted that since the first service device needs to communicate with the effective relay device, that is to say, the first service device and the effective relay device are located in the same network, therefore, the above identification can also be understood as an effective relay. The identification of the interwoven network on which the device is located.

The name of the attribute corresponding to attribute identification 1 is node identification, which is used to indicate a valid relay device that can provide control information relay services for the first service device. The type of this attribute is the node index (node-idx) of the valid relay device. .

The attribute name of the attribute corresponding to attribute identification 2 is connection capability, and the type of connection capability is an 8-bit bitmap used to indicate the connection capability of each valid relay device. For example, each bit in the 8-bit bitmap can indicate the connection capability of the corresponding effective relay device, where BIT(0) indicates that the corresponding effective relay device has the connection capability of LAN, and BIT(1) indicates that the corresponding effective relay device has the connection capability of LAN. The effective relay device has WAN connection capabilities, and BIT(2) indicates that the corresponding effective relay device has the connection capabilities of the cloud platform (or, in other words, runs on the cloud platform).

It should be noted that an effective relay device may have multiple connection capabilities. For example, when the effective relay device is a router, the router's connection capabilities may include LAN and WAN connection capabilities. Of course, some effective relay devices may also have only one connection capability, which is not limited in the embodiments of the present application.

In this embodiment of the present application, the above-mentioned bitmap representing the connection capability of the effective relay device may also have other number of bits, for example, 4 bits, etc. In addition, in other implementations, other methods may be used to represent the connection capabilities of effective relay devices.

Correspondingly, after the user obtains the effective relay device by configuring the device, the user can identify the node of the effective relay device in the effective relay device list in the above-mentioned effective relay cluster. In addition, during the adding process, the connection capability of the effective relay device can also be recorded in the attribute 2 connection capability. For example, assuming that the effective relay device is a router, and the router's connection capability is to have LAN and WAN connection capabilities, then 00000011 can be stored in the router's corresponding connection capability, and the bit value 1 on bit 7 indicates that the router has LAN The connection capability, the bit value 1 in bit 8 indicates that the router has WAN connection capability.

As mentioned above, relay devices located in the cloud usually have a wider range of connection capabilities, or can be connected to a larger number of service devices. Therefore, in order to facilitate users to select relay devices, they can also directly Indicates whether the relay device is in the cloud or not. In other words, the effective relay cluster may also include a network location indication parameter of the corresponding relay device, where the network location indication parameter is used to indicate whether the relay device is located in the cloud.

Table 13 shows another implementation of a valid relay structure. It should be noted that the parts common to Table 13 and Table 12 (for example, the identification attributes and node identification attributes of the interwoven network) have the same functions and meanings. For the sake of simplicity, they will not be described again below.

Table 13

logo name type constraint quality access default consistency 0 Identification of intertwined networks web index all N RW null M 1 Node ID Node index all N RW null M 2 Cloud relay bool all N RW null M

The attribute name of the attribute corresponding to attribute identification 3 is cloud relay (Is cloud relay), and the type of cloud relay is a Boolean value, which is used to indicate whether the corresponding valid relay device is running on the cloud platform. For example, when the Boolean value is "true", it means that the corresponding effective relay device runs on the cloud platform, or is a cloud relay. When the Boolean value is "false", it means that the corresponding valid relay device does not run on the cloud platform, or is not a cloud relay. Among them, attribute identifier 3 can be used as an example of the above "network location indication parameter".

In addition, the configuration device also needs to configure the ACL of the first service device so that the first relay device can access the first service device.

The configuration phase of the control information relay service is introduced above in conjunction with Table 9 and Table 13, and the triggering phase of the control information relay service is introduced below in conjunction with Tables 14 to 17.

Before the first relay device provides the control information relay service for the first service device, the client device usually needs to select a relay device that provides the control information relay service for the first service device to trigger the control information relay. service, so it can be called the "control information relay service triggering phase". In the embodiment of this application, two methods of selecting the control information relay service are provided. These two methods of triggering the control information relay service will be introduced below.

In option one, the client device can obtain a relay device that can provide the control information relay service (ie, the effective relay device above) from the first service device to trigger the control information relay service.

In some implementations, in order to support the above query requirements of the client device, the active relay cluster may support the first request and the first response to the first request. Among them, the first request is used for the client device to request to query one or more valid relay devices. Therefore, the first request can also be called "get valid relays request (get valid relays request)" and the first response is used for the first The service device returns information about one or more valid relay devices to the client device. Therefore, the first response can also be called "get valid relays response".

For ease of understanding, the relevant content of the above-mentioned first request and first response supported in the effective relay cluster is shown below in conjunction with Table 14. It should be noted that the meanings of the data quality columns (for example, access, consistency, default, constraints, etc.) included in the commands in Table 14 have been explained in detail above, and for the sake of brevity, they will not be repeated below.

Table 14

Referring to Table 14, the first request and the first response may include the identification of the command, the name of the command, the direction of the command, the response of the command, the access of the command, and the consistency of the command.

Among them, the name of the command corresponding to command identifier 0 is to obtain a valid relay request. The direction of obtaining a valid relay request is sent by a client (for example, a client device) of the valid relay cluster to a server (for example, a service device) of the valid relay cluster. The response to the Get Valid Relay request is Get Valid Relay Response.

The name of the command corresponding to command identifier 1 is to obtain a valid relay response. The direction to obtain a valid relay response is sent by the server of the valid relay cluster to the client of the valid relay cluster. The response to getting a valid relay response is None.

As introduced above, different relay devices have different connection capabilities. Therefore, in order to improve the accuracy of the relay device obtained by the user, the user can carry indication information 2 (also known as "third indication information") in the request to obtain a valid relay. The indication information 2 is used to indicate the valid relay device of the request. connection capabilities. Correspondingly, only the effective relay devices that meet the connection capability among the effective relay devices recorded in the effective relay cluster can send the obtain effective relay response to the configuration device.

In some implementations, the above-mentioned response for obtaining a valid relay may carry indication information indicating the connection capability of the valid relay device. In other implementations, only valid relay devices that meet the connection capability may be configured to send the Get Valid Relay response to the configuration device. In this case, the Get Valid Relay response may not carry the above indication information.

For example, the obtain valid relay request sent by the client device to the first service device is used to request a relay device with WAN connection capability. At this time, the obtain valid relay response sent by the first service device to the client device only carries Information about valid relay devices with WAN connectivity capabilities (e.g., node ID).

In other implementations, the client device can directly read the information of the effective relay devices recorded in the effective relay cluster to select a relay device that can provide the control information relay service for the first service device.

It should be noted that the above information about the effective relay device may include all or part of the information recorded in the effective relay cluster. For example, it may include the node identification of the effective relay device, the connection capability of the effective relay device, etc.

Generally, in some cases (for example, the selected relay device fails), in order to facilitate the user to change the relay device that provides the control information relay service for the first service device through the client device, the client device can store the first service device Information about valid relay devices.

Selection method 2: The client device can obtain from the first relay device a service device that the first relay device can provide the control information relay service to trigger the control information relay service.

In some implementations, in order to support the client device's need to discover the relay device, a third cluster can be set up in the first relay device. The commands supported by the third cluster can be used by the client device to discover whether the first relay device can A control information relay service can be provided for the first service device. Therefore, the above third cluster can also be called "relay discovery cluster (relay discovery cluster)".

The command supported by the relay discovery cluster may include a second request and a second response to the second request. The second request is used by the client device to request to discover whether the first relay device can provide control information relay services for the first service device. Therefore, the second request can be called a "relay discovery request (relay discover request)" . The second response is used to indicate whether the first relay device can provide the control information relay service for the first service device. Therefore, the second response may be called a "relay discovery response (relay discover response)". In some implementations, the above-mentioned relay discovery response may also carry at least one of the connection capability of the first relay device, the identification of the first serving device, and the identification of the first relay device.

It should be noted that whether the first relay device can provide the control information relay service for the first service device may be indicated by sending or not sending the second response. For example, when the second response is sent, it may be indicated that the first relay device can provide the control information relay service for the first service device. Correspondingly, when the second response is not sent, it may be indicated that the first relay device is unable to provide the control information relay service for the first service device. Of course, whether the first relay device can provide the control information relay service for the first service device can also be determined directly through the content of the second response, which is not limited in the embodiments of the present application.

For ease of understanding, Tables 15 to 17 take the relay discovery cluster in the first relay device as an example to introduce the relay discovery request and the relay discovery response. It should be noted that the meanings of the data quality columns (for example, access, consistency, default, constraints, etc.) included in the commands in Table 15 to Table 17 have been explained in detail above, and for the sake of brevity, they will not be repeated below.

Table 15

Table 16

logo Field type constraint quality default value consistency 0 Target node ID Node ID all N null M

Table 17

logo Field type constraint quality default value consistency 0 Target node ID Node ID all N null M 1 Connectivity map8 desc N null M

Referring to Table 15, the relay discovery request and the relay discovery response may include the identification of the command, the name of the command, the direction of the command, the response of the command, the access of the command, and the consistency of the command.

Among them, the name of the command corresponding to command identifier 0 is relay discovery request. The direction of the relay discovery request is sent by the client of the relay discovery cluster to the service device (server) of the relay discovery cluster, for example, by the client device to the first relay device. The response to the relay discovery request is the relay discovery response.

The parameters carried by the relay discovery request can be seen in Table 16. The identifier of the parameters that can be carried by the relay discovery request is 0. The field of this parameter is the target node ID (target node id), which is used to indicate the first service device. The type is Node identification (node-id).

The name of the command corresponding to command identifier 1 is relay discovery response. The direction of the relay discovery response is sent by the server of the relay discovery cluster to the client of the relay discovery cluster, for example, by the first relay device to the client device. The response to the relay discovery response is None.

The parameters carried by the relay discovery response can be seen in Table 17. The parameters that can be carried by the relay discovery response include parameters marked with 0 and parameters marked with 1. The field of the parameter identified as 0 is the target node ID (target node id), which is used to indicate the first service device, and the type is node ID (node-id). The field of the parameter identified as 1 is the connection capability, which is used to indicate the connection capability of the first relay device, and the type is an 8-bit bitmap. For example, each bit in the 8-bit bitmap may indicate the connection capability of the first relay device, where BIT(0) indicates that the first relay device has the connection capability of LAN, and BIT(1) indicates that the first relay device has the connection capability of LAN. The device has WAN connection capabilities, and BIT(2) indicates that the first relay device is located in the cloud.

In some cases, the relay discovery request does not need to carry the target node identifier, or the field containing the target node identifier in the relay discovery request is empty. In this case, it can be understood that the relay that receives the relay discovery request The device is required to send a relay discovery response.

It should be noted that the first relay device may have multiple connection capabilities. For example, when the first relay device is a router, the connection capabilities of the router may include connection capabilities of LAN and WAN. Of course, the first relay device may also have only one connection capability, which is not limited in the embodiments of the present application.

In this embodiment of the present application, the above-mentioned bitmap representing the connection capability of the first relay device may also have other number of bits, for example, 4 bits, etc. In addition, in other implementations, other methods may be used to represent the connection capability of the first relay device.

In order to facilitate understanding, the method flow of the embodiment of the present application will be introduced below with reference to Figures 6 to 8, taking a communication scenario based on the Matter protocol as an example. It should be noted that in a communication scenario based on the Matter protocol, the client device mentioned above can also be called the "Matter client", and the first service device mentioned above can also be called the "first Matter service device". In addition, the clusters involved in the methods shown in Figures 6 to 8 are introduced in detail above, and for the sake of brevity, they will not be described again below.

Assume that the first Matter service device is smart home device 1 and needs to provide control information relay services for business cluster 1 in smart home device 1. The router and smart home device 1 are on the same home network. The configuration device and Matter client are app on the terminal device. The following describes the method of the embodiment of the present application in three stages with reference to Figure 6 . Figure 6 is a flow chart of a method for transmitting control information according to an embodiment of the present application. The method shown in Figure 6 includes steps S611 to S636.

The control information relay service configuration phase 610 includes steps S611 to S616.

In step S611, the user searches for the relay device in the network by configuring the device.

In some implementations, the user can configure the device to send a subscription request 1 to the group in the home network in the form of multicast to request to subscribe to the relay device. Among them, the group address GroupID can be 0xFFFC.

It should be noted that the above group may include all devices in the home network. Of course, the above group may include devices in the home network that can provide control information relay services. The embodiments of the present application do not limit this.

In step S612, the router returns response message 1 to the subscription request 1 to the configuration device.

In some implementations, response message 1 may carry router information, such as the router's node identifier and the router's connection capabilities.

In step S613, the user selects the router as the first relay device by configuring the device to provide control information relay services for the smart home device 1.

It is assumed that the relay device needs to have external network access capabilities at this time, so the user can select the router as the first relay device.

In step S614, the user configures the ACL of the smart home device 1 through the configuration device so that the router has the authority to access the smart home device 1.

In step S615, the user configures an effective relay cluster of the smart home device 1 through the configuration device to add the router as an effective relay device.

In some implementations, the router's connection capability may be recorded in the effective relay cluster as 00000011, indicating that the router has LAN and WAN connection capabilities.

In step S616, the user configures the relay configuration cluster of the router through the configuration device to add the node label of the smart home device 1 in the target list of the relay configuration cluster.

The control information relay service establishment phase 620 includes steps S621 to S625.

In step S621, the router obtains the information of the service cluster 1 in the smart home device 1.

In some implementations, the router can read the node, endpoint, and cluster information of the smart home device 1. And initiate a subscription request 2 to the business cluster 1 in the smart home device 1 to request to subscribe to the attribute list and command list contained in the business cluster 1. Correspondingly, after the smart home device 1 allows the above subscription request 2, the smart home device 1 sends the attribute list and command list contained in the service cluster 1 to the router.

In step S622, the router creates a virtual node.

The nodes, endpoints, and business clusters of the above virtual nodes are the same as those of the smart home device 1.

In step S623, the router sends a subscription request 3 to the smart home device 1 to request to subscribe to the ACL of the service cluster 1.

In step S624, after the smart home device 1 allows the subscription, the smart home device 1 sends the ACL of the service cluster 1 to the router.

In step S625, the relay device associates the ACL of service cluster 1 to the virtual node.

The control information relay service triggering phase 630 includes steps S631 to S636.

In step S631, the user obtains a relay device that can provide control information relay services for the smart home device 1 through the Matter client.

In some implementations, the Matter client can directly read the effective relay cluster of smart home device 1 to obtain information about all effective relay devices of smart home device 1. In addition, the Matter client can save information about valid relay devices.

In other implementations, the Matter client can also obtain the valid relay device of smart home device 1 by obtaining a valid relay request.

For example, when the parameter carrying the connection capability in the request to obtain a valid relay is 00000010, it means querying a valid relay device with WAN connection capability. At this time, the smart home device 1 can send a response to obtain a valid relay to the Matter client, and Router information.

In step S632, the Matter client sends control information to the router, and the control information is used to control the business cluster 1 of the smart home device 1.

When the Matter client is outside the home network, the Matter client cannot directly connect to the smart home device 1. The user can send the above control information to the virtual node of the router through the Matter client.

In step S633, the router queries the ACL associated with the virtual node and confirms that the Matter client has the permissions required to control the information.

In step S634, the router sends the above control information to the smart home device 1.

In step S635, after executing the command corresponding to the control information, the smart home device 1 returns a result or response to the router.

In step S636, the router returns the result or response to the Matter client.

Assume that the first Matter service device is smart home device 2, and needs to provide control information relay services for business cluster 1 in smart home device 2. The smart speaker and smart home device 2 are on the same home network, and the configuration device and Matter client For the app on the terminal device. The following describes the method of the embodiment of the present application in three stages with reference to Figure 7 . Figure 7 is a flow chart of a method for transmitting control information according to another embodiment of the present application. The method shown in Figure 7 includes steps S711 to S738.

The control information relay service configuration phase 810 includes steps S711 to S716.

In step S711, the user searches for the relay device in the network by configuring the device.

In some implementations, the user can configure the device to send a subscription request 1 to the group in the home network in the form of multicast to request to subscribe to the relay device. Among them, the group's address Group ID can be 0xFFFC.

It should be noted that the above group may include all devices in the home network. Of course, the above group may include devices in the home network that can provide control information relay services. The embodiments of the present application do not limit this.

In step S712, the smart speaker returns response message 1 to the subscription request 1 to the configuration device.

In some implementations, response message 1 may carry information about the smart speaker, such as the node identifier of the smart speaker and the connection capability of the smart speaker.

In step S713, the user selects the smart speaker as the first relay device to provide control information relay services for the smart home device 2.

It is assumed that the relay device needs to have external network access capabilities at this time. Therefore, the user can select the smart speaker as the first relay device.

In step S714, the user configures the ACL of the smart home device 2 through the configuration device so that the smart speaker has the authority to access the smart home device 2.

In step S715, the user configures an effective relay cluster of the smart home device 2 through the configuration device to add the smart speaker as an effective relay device.

In some implementations, the connection capability of the smart speaker can be recorded in the effective relay cluster as 00000011, indicating that the smart speaker has LAN and WAN connection capabilities.

In step S716, the user configures the relay configuration cluster of the smart speaker through the configuration device to add the node label of the smart home device 2 in the target list of the relay configuration cluster.

The control information relay service establishment phase 720 includes steps S721 to S725.

In step S721, the smart speaker obtains the information of the business cluster 1 in the smart home device 2.

In some implementations, the smart speaker can read the node, endpoint, and cluster information of the smart home device 2. And initiate a subscription request 2 to the business cluster 1 in the smart home device 2 to request to subscribe to the attribute list and command list contained in the business cluster 1. Correspondingly, after the smart home device 2 allows the above-mentioned subscription request 2, the smart home device 2 sends the attribute list and command list contained in the business cluster 1 to the smart speaker.

In step S722, the smart speaker creates a virtual node.

The nodes, endpoints, and business clusters of the above virtual nodes are the same as those of the smart home device 2.

In step S723, the smart speaker sends a subscription request 3 to the smart home device 2 to request to subscribe to the ACL of the service cluster 1.

In step S724, after the smart home device 2 allows the subscription, the smart home device 2 sends the ACL of the service cluster 1 to the smart speaker.

In step S725, the relay device associates the ACL of service cluster 1 to the virtual node.

The control information relay service triggering phase 730 includes steps S731 to S738.

In step S731, the Matter client sends a relay discovery request to request the discovery of a relay device that can provide control information relay services for the smart home device 2.

In some implementations, users can send relay discovery requests to groups in the home network in the form of multicast through the Matter client to request discovery of the above-mentioned relay devices. Among them, the group address GroupID can be 0xFFFC.

It should be noted that the above group may include all devices in the home network. Of course, the above group may include devices in the home network that can provide control information relay services. The embodiments of the present application do not limit this.

In step S732, the smart speaker returns a relay discovery response to the Matter client.

In some implementations, the relay discovery response may carry information about the smart speaker, such as the node identifier of the smart speaker and the connection capability of the smart speaker.

In step S733, the Matter client queries the target list of the smart speaker to select the smart home device 2 in the target list for control.

In some implementations, the Matter client can select a smart speaker to connect based on the connection capabilities of the relay device, as a relay device that provides relay services for control information for the smart home device 2.

In step S734, the Matter client sends control information to the smart speaker, and the control information is used to control the business cluster 1 of the smart home device 2.

When the Matter client is outside the home network, the Matter client cannot directly connect to the smart home device 2. The user can send the above control information to the virtual node of the smart speaker through the Matter client.

In step S735, the smart speaker queries the ACL associated with the virtual node and confirms that the Matter client has the permissions required to control the information.

In step S736, the smart speaker sends the above control information to the smart home device 2.

In step S737, after executing the command corresponding to the control information, the smart home device 2 returns a result or response to the smart speaker.

In step S738, the smart speaker returns the result or response to the Matter client.

Assume that the first Matter service device is smart home device 3 and needs to provide control information relay services for business cluster 1 in smart home device 3. The configuration device and Matter client are apps on the terminal device. The following describes the method of the embodiment of the present application in three stages with reference to Figure 8 . Figure 8 is a flow chart of a method for transmitting control information according to another embodiment of the present application. The method shown in Figure 8 includes steps S811 to S838.

The control information relay service configuration phase 810 includes steps S811 to S816.

In step S811, the user obtains the identity of cloud relay 1 on the cloud platform by configuring the device.

In step S812, the cloud platform sends the identification of cloud relay 1 to the configuration device.

In step S813, the user configures the ACL of the smart home device 3 through the configuration device, so that the cloud relay 1 has the permission to access the smart home device 3.

In step S814, the user configures the effective relay cluster of the smart home device 3 through the configuration device to add the cloud relay 1 as an effective relay device.

In some implementations, the Boolean value corresponding to the attribute named Cloud Relay in the effective relay cluster can be set to "true" to indicate that Cloud Relay 1 has the ability to connect to the cloud platform.

In step S815, the user configures the smart home device 3 to connect to the cloud platform through the configuration device.

In some implementations, the configuration device can send the address of the cloud platform to the smart home device 3 so that the smart home device 3 can access the cloud platform. In other implementations, the smart home device 3 can use a node operational certificate (NOC) to establish a CASE secure connection with the cloud platform.

In step S816, the user configures the relay configuration cluster of cloud relay 1 through the configuration device.

In some implementations, the configuration device can configure the relay configuration cluster of the cloud relay 1 to add the node label of the smart home device 3 in the target list of the relay configuration cluster.

In other implementations, the configuration device may configure the relay configuration cluster of cloud relay 1 to set the Boolean value of the attribute "relay all nodes" corresponding to cloud relay 1 in the relay configuration cluster to "true".

It should be noted that the execution order among the above-mentioned steps S816, S813 and S814 is not limited in the embodiment of the present application. For example, the execution order from early to late may be step S813, step S814 and step S816. For another example, the execution order from early to late may be step S813, step S816 and step S814.

The control information relay service establishment phase 820 includes steps S821 to S825.

In step S821, the cloud relay 1 obtains the information of the business cluster 1 in the smart home device 3.

In some implementations, the cloud relay 1 can read the node, endpoint, and cluster information of the smart home device 3. And initiate a subscription request 2 to the business cluster 1 in the smart home device 3 to request to subscribe to the attribute list and command list contained in the business cluster 1. Correspondingly, after the smart home device 3 allows the above-mentioned subscription request 2, the smart home device 3 sends the attribute list and command list contained in the business cluster 1 to the cloud relay 1.

In step S822, cloud relay 1 creates a virtual node.

The nodes, endpoints, and business clusters of the above virtual nodes are the same as those of the smart home device 3.

In step S823, the cloud relay 1 sends a subscription request 3 to the smart home device 3 to request to subscribe to the ACL of the service cluster 1.

In step S824, after the smart home device 3 allows the subscription, the smart home device 3 sends the ACL of the service cluster 1 to the cloud relay 1.

In step S825, the relay device associates the ACL of service cluster 1 with the virtual node.

The control information relay service triggering phase 830 includes steps S831 to S838.

In step S831, the Matter client sends a relay discovery request to request the discovery of a relay device that can provide control information relay services for the smart home device 3.

In some implementations, when the Boolean value of the parameter "cloud relay" carried in the relay discovery request is "true", it means that the Matter client requests to discover the cloud relay.

In step S832, cloud relay 1 returns a relay discovery response to the Matter client.

In some implementations, the relay discovery response may carry information about cloud relay 1, such as the node identifier of cloud relay 1.

In step S833, the Matter client queries the target list of the cloud relay 1 to select the smart home device 3 in the target list for control.

In some implementations, the Matter client can select the cloud relay 1 for connection based on the relay device's connection capabilities, as a relay device that provides relay services for control information for the smart home device 3.

In step S834, the Matter client sends control information to the cloud relay 1, and the control information is used to control the business cluster 1 of the smart home device 3.

When the Matter client is outside the home network, the Matter client cannot directly connect to the smart home device 3. The user can send the above control information to the virtual node of the cloud relay 1 through the Matter client.

In step S835, cloud relay 1 queries the ACL associated with the virtual node and confirms that the Matter client has the permissions required to control the information.

In step S836, the cloud relay 1 sends the above control information to the smart home device 3.

In step S837, after executing the command corresponding to the control information, the smart home device 3 returns a result or response to the cloud relay 1.

In step S838, cloud relay 1 returns the result or response to the Matter client.

The method embodiments of the present application are described in detail above with reference to FIGS. 1 to 8 , and the device embodiments of the present application are described in detail below with reference to FIGS. 9 to 13 . It should be understood that the description of the method embodiments corresponds to the description of the device embodiments. Therefore, the parts not described in detail can be referred to the previous method embodiments.

Figure 9 is a schematic diagram of a relay device according to an embodiment of the present application. The relay device 900 shown in Figure 9 (also known as the "first relay device") includes: a receiving unit 910 and a sending unit 920.

The receiving unit 910 is configured to receive control information sent by the client device, where the control information is used to control the first service device;

The sending unit 920 is configured to send the control information to the first service device.

In a possible implementation, the first relay device includes a first cluster, and the first cluster is used to configure one or more services that the first relay device can provide a control information relay service. Device, the one or more service devices include the first service device.

In a possible implementation, the first cluster includes the identity of the one or more service devices, and/or the identity of the interwoven network where the one or more service devices are located.

In a possible implementation, the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and/or the first cluster includes Second indication information, the second indication information is used to indicate whether the first relay device can provide control information relay services for all service devices connected to the first relay device.

In a possible implementation, the first service device includes a second cluster, the second cluster is used to indicate one or more effective relays that can provide control information relay services for the first service device. Device, the one or more effective relay devices include the first relay device.

In a possible implementation, the second cluster is used to indicate one or more of the following information of each of the one or more valid relay devices: each of the The connection capability of the relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; the network location indication parameter of each relay device; the network location indication parameter of each relay device The identification of the device; the identification of the interwoven network where each relay device is located.

In a possible implementation, the connection capability includes a connection capability to a local area network LAN, and/or a connection capability to a wide area network WAN.

In a possible implementation, the network indication parameter of each relay device indicates whether each relay device is located in the cloud.

In a possible implementation, the second cluster includes a first request and a first response to the first request, the first request is for the client device to request to query the one or more Valid relay device, the first response is used for the first service device to return the information of the one or more valid relay devices to the client device.

In a possible implementation, the first relay device includes a third cluster, and the third cluster is used by the client device to discover whether the first relay device can serve as the first service device. Provide control information relay services.

In a possible implementation, the third cluster includes a second request and a second response to the second request, where the second request is used for the client device to request discovery of the first relay. Whether the device can provide a control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide a control information relay service for the first service device.

In a possible implementation, the second response includes at least one of the connection capability of the first relay device, the identity of the first service device, and the identity of the first relay device.

In a possible implementation, the receiving unit is further configured to: receive a third request sent by the configuration device, where the third request is used to discover a relay device that can provide control information relay services; the sending A unit further configured to send a third response to the configuration device in response to the third request, where the third response is used to indicate that the first relay device can provide a control information relay service.

In a possible implementation, the receiving unit is further configured to receive first configuration information sent by the configuration device, where the first configuration information is used to configure the first relay device to be the first relay device. A service device provides control information relay services.

In a possible implementation, the first configuration information includes an identification of the first service device.

In a possible implementation, the first relay device stores an access control list ACL of the first service device, and the ACL of the first service device is used to record whether the client device controls all The permissions of the first service device.

In a possible implementation, the sending unit is further configured to: when it is determined according to the ACL that the client device has the authority to control the first service device, send the request to the service device. Describe control information.

In a possible implementation, the control information is used to control the first service cluster in the first service device, and the target cluster included in the first relay device is the same as the first service cluster. , the target cluster is located in the virtual node of the first relay device, and the ACL is associated with the virtual node.

In a possible implementation, the relay device further includes a generating unit, the generating unit being configured to generate the virtual node.

In a possible implementation, the sending unit is configured to send a subscription request to the first service device, where the subscription request is used to request to subscribe to the ACL; in response to the subscription request, the receiving unit , used to receive the ACL sent by the first service device.

Figure 10 is a schematic diagram of a client device according to an embodiment of the present application. The client device 1000 shown in Figure 10 includes a sending unit 1010.

The sending unit 1010 is configured to send control information to the first service device through the first relay device, where the control information is used to control the first service device.

In a possible implementation, the first relay device includes a first cluster, and the first cluster is used to configure one or more control information relay services for the first relay device. Service device, the one or more service devices include the first service device.

In a possible implementation, the first cluster includes the identity of the one or more service devices and/or the identity of the interwoven network where the multiple service devices are located.

In a possible implementation, the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and/or the first cluster includes Second indication information, the second indication information is used to indicate whether the first relay device provides control information relay services for all service devices in the network where the first relay device is located.

In a possible implementation, the first service device includes a second cluster, the second cluster is used to indicate one or more effective relays that can provide control information relay services for the first service device. Device, the one or more effective relay devices include the first relay device.

In a possible implementation, the second cluster is used to indicate one or more of the following information of each of the one or more valid relay devices: each of the The connection capability of the relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; the network location indication parameter of each relay device; the network location indication parameter of each relay device The identification of the device; the identification of the interwoven network where each relay device is located.

In a possible implementation, the connection capability includes a connection capability to a local area network LAN, and/or a connection capability to a wide area network WAN.

In a possible implementation, the network indication parameter of each relay device indicates whether each relay device is located in the cloud.

In a possible implementation, the second cluster includes a first request and a first response to the first request, the first request is for the client device to request to query the one or more Valid relay device, the first response is used for the first service device to return information of the one or more valid relay devices to the client device.

In a possible implementation, the sending unit is further configured to send the first request to the first service device, where the first request carries third indication information, and the third indication information is Instructing to request an effective relay device whose connection capability is the first connection capability among the one or more effective relay devices; the receiving unit is also configured to receive the first response sent by the first service device, The first response indicates that an effective relay device with the first connection capability among the one or more effective relay devices is the first relay device.

In a possible implementation, the client device further includes a processing unit, and the processing unit is further configured to read the second cluster to obtain the one or more valid relay devices.

In a possible implementation, the first relay device includes a third cluster, and the third cluster is used by the client device to discover whether the first relay device can serve as the first service device. Provide control information relay services.

In a possible implementation, the third cluster includes a second request and a second response to the second request, where the second request is used for the client device to request discovery of the first relay. Whether the device can provide a control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide a control information relay service for the first service device.

In a possible implementation, the second response includes at least one of the connection capabilities of the one or more relay devices, the identity of the first service device, and the identity of the first relay device. kind.

In a possible implementation, the first relay device stores an access control list ACL of the first service device, and the ACL of the first service device is used to record whether the client device controls all The permissions of the first service device.

In a possible implementation, the control information is used to control the first service cluster in the first service device, and the target cluster included in the first relay device is the same as the first service cluster. , the target service cluster is located at a virtual node of the first relay device, and the ACL is associated with the virtual node.

Figure 11 is a schematic diagram of a service device according to an embodiment of the present application. The service device 1100 shown in Figure 11 includes a receiving unit 1110.

The receiving unit 1110 is configured to receive control information sent by the client device through the first relay device, where the control information is used to control the first service device.

In a possible implementation, the first relay device includes a first cluster, and the first cluster is used to configure one or more control information relay services for the first relay device. Service device, the one or more service devices include the first service device.

In a possible implementation, the first cluster includes the identity of the one or more service devices and/or the identity of the interwoven network where the multiple service devices are located.

In a possible implementation, the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and/or the first cluster includes Second indication information, the second indication information is used to indicate whether the first relay device provides control information relay services for all service devices in the network where the first relay device is located.

In a possible implementation, the first service device includes a second cluster, the second cluster is used to indicate one or more effective relays that can provide control information relay services for the first service device. Device, the one or more effective relay devices include the first relay device.

In a possible implementation, the second cluster is used to indicate one or more of the following information of each of the one or more valid relay devices: each of the The connection capability of the relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; the network location indication parameter of each relay device; the network location indication parameter of each relay device The identification of the device; the identification of the interwoven network where each relay device is located.

In a possible implementation, the connection capability includes a connection capability to a local area network LAN, and/or a connection capability to a wide area network WAN.

In a possible implementation, the network indication parameter of each relay device indicates whether each relay device is located in the cloud.

In a possible implementation, the second cluster includes a first request and a first response to the first request, the first request is for the client device to request to query the one or more Valid relay device, the first response is used for the first service device to return information of the one or more valid relay devices to the client device.

In a possible implementation, the first service device further includes a first receiving unit, the first receiving unit is configured to: receive the first request sent by the client device, the first The request carries third indication information, and the third indication information is used to indicate requesting an effective relay device whose connection capability is the first connection capability among the one or more effective relay devices; the sending unit is configured to The client device sends the first response, and the first response indicates that among the one or more valid relay devices, the valid relay device with the first connection capability is the first relay device. .

In a possible implementation, the first relay device includes a third cluster, and the third cluster is used by the client device to discover whether the first relay device can serve as the first service device. Provide control information relay services.

In a possible implementation, the third cluster includes a second request and a second response to the second request, where the second request is used for the client device to request discovery of the first relay. Whether the device can provide a control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide a control information relay service for the first service device.

In a possible implementation, the second response includes at least one of the connection capabilities of the one or more relay devices, the identity of the first service device, and the identity of the first relay device. kind.

In a possible implementation, the first relay device stores an access control list ACL of the first service device, and the ACL of the first service device is used to record whether the client device controls all The permissions of the first service device.

In a possible implementation, the control information is used to control the first service cluster in the first service device, and the target cluster included in the first relay device is the same as the first service cluster. , the target cluster is located in the virtual node of the first relay device, and the ACL is associated with the virtual node.

In a possible implementation, the client device further includes a second receiving unit, the second receiving unit is configured to receive a subscription request sent by the first relay device, the subscription request is used to request Subscribe to the ACL; in response to the subscription request, the sending unit is configured to send the ACL to the first relay device.

Figure 12 is a schematic diagram of a configuration device according to an embodiment of the present application. The configuration device 1200 shown in Figure 12 includes a sending unit 1210.

The sending unit 1210 is configured to send second configuration information to the target device, where the second configuration information is used to configure the first relay device to provide a control information relay service for the first service device, wherein the target device is the The first relay device and the first service device, the control information is used by the client device to control the first service device.

In a possible implementation, the sending unit is further configured to send the second configuration information to the first cluster in the first relay device.

The first relay device includes a first cluster, and the first cluster is used to configure one or more service devices that need to provide control information relay services for the first relay device. The one or more The service device includes the first service device.

In a possible implementation, the first cluster includes an identity of the one or more service devices and/or an identity of the interwoven network in which the one or more service devices are located.

In a possible implementation, the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and/or the first cluster includes Second indication information, the second indication information is used to indicate whether the first relay device provides control information relay services for all service devices in the network where the first relay device is located.

In a possible implementation, the first service device includes a second cluster, the second cluster is used to indicate one or more effective relays that can provide control information relay services for the first service device. Device, the one or more effective relay devices include the first relay device.

In a possible implementation, the second cluster is used to indicate one or more of the following information of each of the one or more valid relay devices: each of the The connection capability of the relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; the network location indication parameter of each relay device; the network location indication parameter of each relay device The identification of the device; the identification of the interwoven network where each relay device is located.

In a possible implementation, the connection capability includes a connection capability to a local area network LAN, and/or a connection capability to a wide area network WAN.

In a possible implementation, the network indication parameter of each relay device indicates whether each relay device is located in the cloud.

In a possible implementation, the second cluster includes a first request and a first response to the first request, the first request is for the client device to request to query the one or more Valid relay device, the first response is used for the first service device to return information of the one or more valid relay devices to the client device.

In a possible implementation, the first request is used to carry third indication information, and the third indication information is used to indicate that the connection capability in the one or more effective relay devices is requested to be the first connection capability. valid relay device.

In a possible implementation, the target device is the first service device, and the sending unit is configured to send the second configuration information to the second cluster in the first service device.

In a possible implementation, the first relay device includes a third cluster, and the third cluster is used by the client device to discover whether the first relay device can serve as the first service device. Provide control information relay services.

In a possible implementation, the third cluster includes a second request and a second response to the second request, where the second request is used for the client device to request discovery of the first relay. Whether the device can provide a control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide a control information relay service for the first service device.

In a possible implementation, the second response includes at least one of the connection capabilities of the one or more relay devices, the identity of the first service device, and the identity of the first relay device. kind.

In a possible implementation, the target device is the first relay device, the configuration device includes a receiving unit, and the sending unit is configured to send a third request to the first relay device, so The third request is used to discover a relay device that can provide the control information relay service; in response to the third request, the receiving unit is used to receive a third response sent by the first relay device, so The third response is used to indicate that the first relay device can provide control information relay service.

In a possible implementation, the second configuration information includes an identification of the first service device.

In a possible implementation, the first relay device stores an access control list ACL of the first service device, and the ACL of the first service device is used to record whether the client device controls all The permissions of the first service device.

In a possible implementation, the control information is used to control the first service cluster in the first service device, and the target cluster included in the first relay device is the same as the first service cluster. , the target cluster is located at a virtual node of the first relay device, and the ACL is associated with the virtual node.

Figure 13 is a schematic structural diagram of a communication device according to an embodiment of the present application. The dashed line in Figure 13 indicates that the unit or module is optional. The device 1300 can be used to implement the method described in the above method embodiment. Device 1300 may be a chip, terminal device or network device.

Apparatus 1300 may include one or more processors 1310. The processor 1310 can support the device 1300 to implement the method described in the foregoing method embodiments. The processor 1310 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor can also be another general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or an off-the-shelf programmable gate array (FPGA) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

Apparatus 1300 may also include one or more memories 1320. The memory 1320 stores a program, which can be executed by the processor 1310, so that the processor 1310 executes the method described in the foregoing method embodiment. The memory 1320 may be independent of the processor 1310 or integrated in the processor 1310.

Apparatus 1300 may also include a transceiver 1330. Processor 1310 may communicate with other devices or chips through transceiver 1330. For example, the processor 1310 can transmit and receive data with other devices or chips through the transceiver 1330.

An embodiment of the present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.

An embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.

An embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or network device provided by the embodiments of the present application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.

It should be understood that the "cluster" in the embodiment of the present application can be called a "functional set" in addition to the above introduction, and can also be called a "cluster" or "cluster". The embodiments of this application do not limit the names of the above clusters.

In the embodiment of this application, the "interwoven network" can be understood as an ecological network of the Internet of Things. Of course, the interwoven network in the embodiment of this application can also be replaced by any ecological network in the future Internet of Things.

The terms "system" and "network" may be used interchangeably in this application. In addition, the terms used in this application are only used to explain specific embodiments of the application and are not intended to limit the application. The terms “first”, “second”, “third” and “fourth” in the description, claims and drawings of this application are used to distinguish different objects, rather than to describe a specific sequence. . Furthermore, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion.

In the embodiments of this application, the "instruction" mentioned may be a direct instruction, an indirect instruction, or an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.

In the embodiment of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B only based on A. B can also be determined based on A and/or other information.

In the embodiments of this application, the term "correspondence" can mean that there is a direct correspondence or indirect correspondence between the two, or it can also mean that there is an association between the two, or it can also mean indicating and being instructed, configuring and being configured, etc. relation.

In the embodiment of this application, "predefinition" or "preconfiguration" can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). The application does not limit its specific implementation method. For example, predefined can refer to what is defined in the protocol.

In the embodiment of this application, the "protocol" may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this.

The term "and/or" in the embodiment of this application is only an association relationship describing associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, and A and B exist simultaneously. , there are three situations of B alone. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

In the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be determined by the implementation process of the embodiments of the present application. constitute any limitation.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

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

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

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center integrated with one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVD)) or semiconductor media (e.g., solid state disks (SSD) )wait.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (151)

A method for transmitting control information, characterized by including: The first relay device receives control information sent by the client device, where the control information is used to control the first service device; The first relay device sends the control information to the first service device. The method of claim 1, wherein the first relay device includes a first cluster, and the first cluster is used to configure the first relay device to provide a control information relay service. or multiple service devices, the one or more service devices including the first service device. The method of claim 2, wherein the first cluster includes the identification of the one or more service devices, and/or the identification of the interwoven network where the one or more service devices are located. The method according to claim 2 or 3, characterized in that the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and/or The first cluster includes second indication information, and the second indication information is used to indicate whether the first relay device can provide control information relay services for all service devices connected to the first relay device. The method according to any one of claims 1 to 4, characterized in that the first service device includes a second cluster, the second cluster is used to indicate that the control information can be provided for the first service device. One or more effective relay devices of relay service, the one or more effective relay devices include the first relay device. The method of claim 5, wherein the second cluster is used to indicate one or more of the following information capable of each of the one or more valid relay devices: The connection capability of each relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; The network location indication parameter of each relay device; The identification of each relay device; The identification of the interwoven network where each relay device is located. The method of claim 6, wherein the connection capability includes a connection capability to a local area network (LAN), and/or a connection capability to a wide area network (WAN). The method of claim 6 or 7, wherein the network indication parameter of each relay device indicates whether each relay device is located in the cloud. The method of any one of claims 5-8, wherein the second cluster includes a first request and a first response to the first request, the first request is for the client The terminal device requests to query the one or more effective relay devices, and the first response is used for the first service device to return the information of the one or more effective relay devices to the client device. The method according to any one of claims 1-9, characterized in that the first relay device includes a third cluster, the third cluster is used for the client device to discover the first relay Whether the device can provide control information relay service for the first service device. The method of claim 10, wherein the third cluster includes a second request and a second response to the second request, the second request being for the client device to request discovery of the third cluster. Whether a relay device can provide a control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide a control information relay service for the first service device. . The method of claim 11, wherein the second response includes the connection capability of the first relay device, the identity of the first service device, and the identity of the first relay device. At least one. The method according to any one of claims 1-12, wherein the client device further includes: The first relay device receives a third request sent by the configuration device, where the third request is used to discover a relay device that can provide control information relay services; In response to the third request, the first relay device sends a third response to the configuration device, where the third response is used to indicate that the first relay device can provide a control information relay service. The method of claim 13, wherein after the first relay device sends the third response to the configuration device, the client device further includes: The first relay device receives first configuration information sent by the configuration device, and the first configuration information is used to configure the first relay device to provide a control information relay service for the first service device. The method of claim 14, wherein the first configuration information includes an identification of the first service device. The method according to any one of claims 1 to 15, characterized in that the first relay device stores an access control list ACL of the first service device, and the ACL of the first service device is used to Record whether the client device has the authority to control the first service device. The method of claim 16, wherein the first relay device sends the control information to the service device, including: If it is determined according to the ACL that the client device has the authority to control the first service device, the first relay device sends the control information to the service device. The method of claim 16 or 17, wherein the control information is used to control the first service cluster in the first service device, and the target cluster included in the first relay device is the same as the target cluster. The first service cluster is the same, the target cluster is located in the virtual node of the first relay device, and the ACL is associated with the virtual node. The method of claim 18, wherein the client device further includes: The first relay device generates the virtual node. The method according to any one of claims 16-19, wherein the client device further includes: The first relay device sends a subscription request to the first service device, where the subscription request is used to request to subscribe to the ACL; In response to the subscription request, the first relay device receives the ACL sent by the first service device. A method for transmitting control information, characterized by including: The client device sends control information to the first service device through the first relay device, where the control information is used to control the first service device. The method of claim 21, wherein the first relay device includes a first cluster, and the first cluster is used to configure the first relay device to provide control information relay services. One or more service devices, the one or more service devices including the first service device. The method of claim 22, wherein the first cluster includes identities of the one or more service devices and/or identities of the interwoven network where the multiple service devices are located. The method of claim 22 or 23, wherein the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and/or, The first cluster includes second indication information, and the second indication information is used to indicate whether the first relay device provides control information relay services for all service devices in the network where the first relay device is located. The method according to any one of claims 21-24, wherein the first service device includes a second cluster, the second cluster is used to indicate that the first service device can provide control information. One or more effective relay devices of relay service, the one or more effective relay devices include the first relay device. The method of claim 25, wherein the second cluster is used to indicate one or more of the following information capable of each of the one or more valid relay devices: The connection capability of each relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; The network location indication parameter of each relay device; The identification of each relay device; The identification of the interwoven network where each relay device is located. The method of claim 26, wherein the connection capability includes a connection capability to a local area network (LAN), and/or a connection capability to a wide area network (WAN). The method of claim 26 or 27, wherein the network indication parameter of each relay device indicates whether each relay device is located in the cloud. The method of any one of claims 25-28, wherein the second cluster includes a first request and a first response to the first request, the first request for the client The terminal device requests to query the one or more effective relay devices, and the first response is used for the first service device to return the information of the one or more effective relay devices to the client device. The method of claim 29, wherein the client device further includes: The client device sends the first request to the first service device, the first request carries third indication information, and the third indication information is used to indicate requesting the one or more effective relays. The connection capability of the device is an effective relay device with the first connection capability; The client device receives the first response sent by the first service device, the first response indicating an effective relay device with the first connection capability among the one or more effective relay devices. is the first relay device. The method according to any one of claims 25-30, wherein the client device further includes: The client device reads the second cluster to obtain the one or more valid relay devices. The client device according to any one of claims 21-31, characterized in that the first relay device includes a third cluster, the third cluster is used for the client device to discover the first Whether the relay device can provide control information relay service for the first service device. The method of claim 32, wherein the third cluster includes a second request and a second response to the second request, the second request being for the client device to request discovery of the third cluster. Whether a relay device can provide control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide control information relay for the first service device. Serve. The method of claim 33, wherein the second response includes the connection capabilities of the one or more relay devices, the identity of the first service device, and the identity of the first relay device. at least one of them. The method according to any one of claims 21 to 34, characterized in that the first relay device stores an access control list ACL of the first service device, and the ACL of the first service device is used to Record whether the client device has the authority to control the first service device. The method of claim 35, wherein the control information is used to control a first service cluster in the first service device, and the target cluster included in the first relay device is identical to the first service cluster. A service cluster is the same, the target service cluster is located at the virtual node of the first relay device, and the ACL is associated with the virtual node. A method for transmitting control information, characterized by including: The first service device receives control information sent by the client device through the first relay device, and the control information is used to control the first service device. The method of claim 37, wherein the first relay device includes a first cluster, and the first cluster is used to configure the first relay device to provide control information relay services. One or more service devices, the one or more service devices including the first service device. The method of claim 38, wherein the first cluster includes identities of the one or more service devices and/or identities of the interwoven network where the multiple service devices are located. The method of claim 38 or 39, wherein the first cluster includes first indication information, the first indication information being used to indicate whether the first relay device is located in the cloud, and/or, The first cluster includes second indication information, and the second indication information is used to indicate whether the first relay device provides control information relay services for all service devices in the network where the first relay device is located. The method according to any one of claims 37-40, wherein the first service device includes a second cluster, the second cluster is used to indicate that the first service device can provide control information. One or more effective relay devices of relay service, the one or more effective relay devices include the first relay device. The method of claim 41, wherein the second cluster is used to indicate one or more of the following information capable of each of the one or more valid relay devices: The connection capability of each relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; The network location indication parameter of each relay device; The identification of each relay device; The identification of the interwoven network where each relay device is located. The method of claim 42, wherein the connection capability includes a connection capability to a local area network (LAN), and/or a connection capability to a wide area network (WAN). The method of claim 42 or 43, wherein the network indication parameter of each relay device indicates whether each relay device is located in the cloud. The method of any one of claims 41-44, wherein the second cluster includes a first request and a first response to the first request, the first request for the client The terminal device requests to query the one or more effective relay devices, and the first response is used for the first service device to return the information of the one or more effective relay devices to the client device. The method of claim 45, further comprising: The first service device receives the first request sent by the client device, the first request carries third indication information, and the third indication information is used to indicate requesting the one or more valid Among the relay devices, the connection capability is an effective relay device with the first connection capability; The first service device sends the first response to the client device, and the first response indicates that the connection capability of the one or more valid relay devices is that the valid relay device with the first connection capability is the first relay device. The method according to any one of claims 37-46, characterized in that the first relay device includes a third cluster, the third cluster is used for the client device to discover the first relay Whether the device can provide control information relay service for the first service device. The method of claim 47, wherein the third cluster includes a second request and a second response to the second request, the second request being for the client device to request discovery of the third cluster. Whether a relay device can provide a control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide a control information relay service for the first service device. . The method of claim 48, wherein the second response includes the connection capabilities of the one or more relay devices, the identity of the first service device, and the identity of the first relay device. at least one of them. The method according to any one of claims 37 to 49, characterized in that the first relay device stores an access control list ACL of the first service device, and the ACL of the first service device is used to Record whether the client device has the authority to control the first service device. The method of claim 50, wherein the control information is used to control a first service cluster in the first service device, and the target cluster included in the first relay device is identical to the first service cluster. A service cluster is the same, the target cluster is located in the virtual node of the first relay device, and the ACL is associated with the virtual node. The method according to claim 50 or 51, characterized in that the method further includes: The first service device receives a subscription request sent by the first relay device, where the subscription request is used to request to subscribe to the ACL; In response to the subscription request, the first service device sends the ACL to the first relay device. A method for transmitting control information, characterized by including: The configuration device sends second configuration information to the target device, where the second configuration information is used to configure the first relay device to provide a control information relay service for the first service device, Wherein, the target device includes the first relay device and/or the first service device, and the control information is used by the client device to control the first service device. The method of claim 53, wherein the target device is the first relay device, and the configuration device sends second configuration information to the target device, including: The configuration device sends the second configuration information to the first cluster in the first relay device. The method according to claim 53 or 54, characterized in that the first relay device includes a first cluster, and the first cluster is used to provide control information relay for the configuration needs of the first relay device. One or more service devices of the service, the one or more service devices include the first service device. The method of claim 55, wherein the first cluster includes identities of the one or more service devices and/or identities of the interwoven network where the one or more service devices are located. The method of claim 55 or 56, wherein the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and/or, The first cluster includes second indication information, and the second indication information is used to indicate whether the first relay device provides control information relay services for all service devices in the network where the first relay device is located. The method according to any one of claims 53-57, wherein the first service device includes a second cluster, the second cluster is used to indicate that the first service device can provide control information. One or more effective relay devices of relay service, the one or more effective relay devices include the first relay device. The method of claim 58, wherein the second cluster is used to indicate one or more of the following information capable of each of the one or more valid relay devices: The connection capability of each relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; The network location indication parameter of each relay device; The identification of each relay device; The identification of the interwoven network where each relay device is located. The method of claim 59, wherein the connection capability includes a connection capability to a local area network (LAN), and/or a connection capability to a wide area network (WAN). The method of claim 59 or 60, wherein the network indication parameter of each relay device indicates whether each relay device is located in the cloud. The method of any one of claims 58-61, wherein the second cluster includes a first request and a first response to the first request, the first request for the client The terminal device requests to query the one or more effective relay devices, and the first response is used for the first service device to return the information of the one or more effective relay devices to the client device. The method of claim 62, wherein the first request is used to carry third indication information, and the third indication information is used to indicate that the connection capability of the one or more effective relay devices requested is Effective relay device for first connection capability. The method according to any one of claims 53-63, wherein the target device is the first service device, and the configuration device sends second configuration information to the target device, including: The configuration device sends the second configuration information to the second cluster in the first service device. The method according to any one of claims 53-64, wherein the first relay device includes a third cluster, the third cluster is used for the client device to discover the first relay Whether the device can provide control information relay service for the first service device. The method of claim 65, wherein the third cluster includes a second request and a second response to the second request, the second request being for the client device to request discovery of the third cluster. Whether a relay device can provide a control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide a control information relay service for the first service device. . The method of claim 66, wherein the second response includes the connection capabilities of the one or more relay devices, the identity of the first service device, and the identity of the first relay device. at least one of them. The method according to any one of claims 53-67, wherein the target device is the first relay device, and the method further includes: The configuration device sends a third request to the first relay device, where the third request is used to discover a relay device that can provide the control information relay service; In response to the third request, the configuration device receives a third response sent by the first relay device, where the third response is used to indicate that the first relay device can provide a control information relay service. The method of claim 68, wherein the second configuration information includes an identification of the first service device. The method according to any one of claims 53 to 69, characterized in that the first relay device stores an access control list ACL of the first service device, and the ACL of the first service device is used to Record whether the client device has the authority to control the first service device. The method of claim 70, wherein the control information is used to control a first service cluster in the first service device, and the target cluster included in the first relay device is identical to the first service cluster. A service cluster is the same, the target cluster is located at the virtual node of the first relay device, and the ACL is associated with the virtual node. A relay device, characterized by including: A receiving unit, configured to receive control information sent by a client device, where the control information is used to control the first service device; A sending unit, configured to send the control information to the first service device. The relay device of claim 72, wherein the first relay device includes a first cluster, and the first cluster is used to configure the first relay device to provide a control information relay service. One or more service devices, the one or more service devices include the first service device. The relay device according to claim 73, wherein the first cluster includes an identifier of the one or more service devices, and/or an identifier of the interwoven network where the one or more service devices are located. . The relay device according to claim 72 or 73, wherein the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and/ or The first cluster includes second indication information, and the second indication information is used to indicate whether the first relay device can provide control information relay services for all service devices connected to the first relay device. The relay device according to any one of claims 72-75, wherein the first service device includes a second cluster, the second cluster is used to indicate that control can be provided for the first service device. One or more effective relay devices of information relay service, the one or more effective relay devices include the first relay device. The relay device of claim 76, wherein the second cluster is used to indicate one or more of the following information capable of each of the one or more valid relay devices. : The connection capability of each relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; The network location indication parameter of each relay device; The identification of each relay device; The identification of the interwoven network where each relay device is located. The relay device according to claim 77, wherein the connection capability includes a connection capability to a local area network (LAN), and/or a connection capability to a wide area network (WAN). The relay device according to claim 77 or 78, wherein the network indication parameter of each relay device indicates whether each relay device is located in the cloud. The relay device according to any one of claims 76-79, wherein the second cluster includes a first request and a first response to the first request, the first request is for the The client device requests to query the one or more valid relay devices, and the first response is used for the first service device to return the information of the one or more valid relay devices to the client device. The relay device according to any one of claims 72-80, wherein the first relay device includes a third cluster, the third cluster is used for the client device to discover the first Whether the relay device can provide control information relay service for the first service device. The relay device of claim 81, wherein the third cluster includes a second request and a second response to the second request, the second request being used for the client device to request discovery of all Whether the first relay device can provide control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide control information for the first service device. Following service. The relay device of claim 82, wherein the second response includes the connection capability of the first relay device, the identification of the first service device, and the identification of the first relay device. at least one of them. The relay device according to any one of claims 72 to 83, characterized in that the receiving unit is further configured to: receive a third request sent by the configuration device, the third request is used to discover that the control device can provide Relay equipment for information relay services; The sending unit is further configured to send a third response to the configuration device in response to the third request, where the third response is used to indicate that the first relay device can provide a control information relay service. The relay device according to claim 84, characterized in that the receiving unit is also used to: Receive first configuration information sent by the configuration device, where the first configuration information is used to configure the first relay device to provide a control information relay service for the first service device. The relay device according to claim 85, wherein the first configuration information includes an identification of the first service device. The relay device according to any one of claims 72 to 86, wherein the first relay device stores an access control list (ACL) of the first service device, and the ACL of the first service device Used to record whether the client device has the authority to control the first service device. The relay device according to claim 87, characterized in that the sending unit is also used to: If it is determined according to the ACL that the client device has the authority to control the first service device, the control information is sent to the service device. The relay device according to claim 87 or 88, characterized in that the control information is used to control the first service cluster in the first service device, and the target cluster included in the first relay device Same as the first service cluster, the target cluster is located in the virtual node of the first relay device, and the ACL is associated with the virtual node. The relay device according to claim 89, characterized in that the relay device further includes a generating unit, The generating unit is used to generate the virtual node. The relay device according to any one of claims 87-90, characterized in that, The sending unit is configured to send a subscription request to the first service device, where the subscription request is used to request to subscribe to the ACL; In response to the subscription request, the receiving unit is configured to receive the ACL sent by the first service device. A client device, characterized by including: A sending unit, configured to send control information to the first service device through the first relay device, where the control information is used to control the first service device. The client device of claim 92, wherein the first relay device includes a first cluster, and the first cluster is used to provide control information relay for configuration needs of the first relay device. One or more service devices of the service, the one or more service devices include the first service device. The client device of claim 93, wherein the first cluster includes identities of the one or more service devices and/or identities of the interwoven network where the plurality of service devices are located. The client device according to claim 92 or 93, wherein the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and/ or, The first cluster includes second indication information, and the second indication information is used to indicate whether the first relay device provides control information relay services for all service devices in the network where the first relay device is located. The client device according to any one of claims 92-95, wherein the first service device includes a second cluster, the second cluster is used to indicate that control can be provided for the first service device One or more effective relay devices of information relay service, the one or more effective relay devices include the first relay device. The client device of claim 96, wherein the second cluster is configured to indicate one or more of the following information capable of each of the one or more valid relay devices : The connection capability of each relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; The network location indication parameter of each relay device; The identification of each relay device; The identification of the interwoven network where each relay device is located. The client device of claim 97, wherein the connectivity capability includes a connectivity capability to a local area network (LAN), and/or a connectivity capability to a wide area network (WAN). The client device of claim 97 or 98, wherein the network indication parameter of each relay device indicates whether each relay device is located in the cloud. The client device of any one of claims 96-99, wherein the second cluster includes a first request and a first response to the first request, the first request for the The client device requests to query the one or more valid relay devices, and the first response is used for the first service device to return the information of the one or more valid relay devices to the client device. The client device of claim 100, wherein: The sending unit is further configured to send the first request to the first service device, where the first request carries third indication information, and the third indication information is used to indicate requesting the one or more An effective relay device whose connection capability is the first connection capability among the valid relay devices; The receiving unit is also configured to receive the first response sent by the first service device, the first response indicating the validity of the first connection capability in the one or more valid relay devices. The relay device is the first relay device. The client device according to any one of claims 96-101, characterized in that the client device further includes a processing unit, the processing unit is further configured to read the second cluster to obtain the One or more valid relay devices. The client device according to any one of claims 92-102, wherein the first relay device includes a third cluster, the third cluster is used for the client device to discover the first Whether the relay device can provide control information relay service for the first service device. The client device of claim 103, wherein the third cluster includes a second request and a second response to the second request, the second request being for the client device to request discovery of the Whether the first relay device can provide control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide control information for the first service device. Following service. The client device of claim 104, wherein the second response includes the connection capabilities of the one or more relay devices, the identification of the first service device, the first relay device At least one of the identifiers. The client device according to any one of claims 92-105, wherein the first relay device stores an access control list (ACL) of the first service device, and the ACL of the first service device Used to record whether the client device has the authority to control the first service device. The client device of claim 106, wherein the control information is used to control a first service cluster in the first service device, and the target cluster included in the first relay device is the same as the target cluster. The first service cluster is the same, the target service cluster is located at the virtual node of the first relay device, and the ACL is associated with the virtual node. A service device, characterized by including: A sending unit, configured to receive control information sent by the client device through the first relay device, where the control information is used to control the first service device. The first service device according to claim 108, wherein the first relay device includes a first cluster, and the first cluster is used to provide control information for configuration needs of the first relay device. one or more service devices following the service, the one or more service devices including the first service device. The first service device according to claim 109, wherein the first cluster includes the identity of the one or more service devices and/or the identity of the interwoven network where the plurality of service devices are located. The first service device according to claim 108 or 109, wherein the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and /or, The first cluster includes second indication information, and the second indication information is used to indicate whether the first relay device provides control information relay services for all service devices in the network where the first relay device is located. The first service device according to any one of claims 108-111, characterized in that the first service device includes a second cluster, the second cluster is used to indicate that the first service device can be provided with One or more effective relay devices of the information relay service are controlled, and the one or more effective relay devices include the first relay device. The first service device according to claim 112, wherein the second cluster is used to indicate one or more of the following information of each relay device in the one or more valid relay devices. kind: The connection capability of each relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; The network location indication parameter of each relay device; The identification of each relay device; The identification of the interwoven network where each relay device is located. The first service device according to claim 113, wherein the connection capability includes a connection capability to a local area network (LAN), and/or a connection capability to a wide area network (WAN). The first service device according to claim 112 or 113, wherein the network indication parameter of each relay device indicates whether each relay device is located in the cloud. The first service device according to any one of claims 112-115, wherein the second cluster includes a first request and a first response to the first request, the first request is for The client device requests to query the one or more valid relay devices, and the first response is used for the first service device to return information about the one or more valid relay devices to the client device. . The first service device according to claim 116, characterized in that the first service device further includes a first receiving unit, and the first receiving unit is used for: Receive the first request sent by the client device, the first request carries third indication information, and the third indication information is used to indicate that the connection capability of the one or more effective relay devices requested is An effective relay device with first connection capability; The sending unit is configured to send the first response to the client device, where the first response indicates an effective relay device with the first connection capability among the one or more effective relay devices. is the first relay device. The first service device according to any one of claims 108-117, characterized in that the first relay device includes a third cluster, the third cluster is used for the client device to discover the first Whether a relay device can provide control information relay service for the first service device. The first service device of claim 118, wherein the third cluster includes a second request and a second response to the second request, the second request being for the client device to request discovery. Whether the first relay device can provide control information relay service for the first service device, and the second response is used to indicate whether the first relay device can provide control information for the first service device. Relay service. The first service device according to claim 119, characterized in that the second response includes the connection capabilities of the one or more relay devices, the identification of the first service device, the first relay At least one of the identifiers of the device. The first service device according to any one of claims 108 to 120, characterized in that the first relay device stores an access control list ACL of the first service device, and the first service device’s access control list ACL. The ACL is used to record whether the client device has the authority to control the first service device. The first service device according to claim 121, wherein the control information is used to control a first service cluster in the first service device, and the first relay device includes a target cluster and The first service clusters are the same, the target cluster is located in the virtual node of the first relay device, and the ACL is associated with the virtual node. The first service device according to claim 121 or 122, wherein the client device further includes a second receiving unit, The second receiving unit is configured to receive a subscription request sent by the first relay device, where the subscription request is used to request to subscribe to the ACL; In response to the subscription request, the sending unit is configured to send the ACL to the first relay device. A configuration device, characterized by including: a sending unit configured to send second configuration information to the target device, where the second configuration information is used to configure the first relay device to provide a control information relay service for the first service device, Wherein, the target device includes the first relay device and/or the first service device, and the control information is used by the client device to control the first service device. The configuration device according to claim 124, wherein the sending unit is further configured to send the second configuration information to the first cluster in the first relay device. The configuration device according to claim 124 or 125, characterized in that the first relay device includes a first cluster, and the first cluster is used to provide control information for the configuration needs of the first relay device. one or more service devices following the service, the one or more service devices including the first service device. The configuration device according to claim 126, wherein the first cluster includes an identifier of the one or more service devices and/or an identifier of the interwoven network in which the one or more service devices are located. The configuration device according to claim 126 or 127, wherein the first cluster includes first indication information, the first indication information is used to indicate whether the first relay device is located in the cloud, and/or , The first cluster includes second indication information, and the second indication information is used to indicate whether the first relay device provides control information relay services for all service devices in the network where the first relay device is located. The configuration device according to any one of claims 124-128, wherein the first service device includes a second cluster, the second cluster is used to indicate that the first service device can provide control information One or more effective relay devices of the relay service, the one or more effective relay devices including the first relay device. The configuration device of claim 129, wherein the second cluster is used to indicate one or more of the following information capable of each of the one or more valid relay devices: The connection capability of each relay device, the connection capability of each relay device is used to indicate the network type to which each relay device is connected; The network location indication parameter of each relay device; The identification of each relay device; The identification of the interwoven network where each relay device is located. The configuration device of claim 130, wherein the connection capability includes a connection capability to a local area network (LAN), and/or a connection capability to a wide area network (WAN). The configuration device according to claim 130 or 131, wherein the network indication parameter of each relay device indicates whether each relay device is located in the cloud. The configuration device of any one of claims 129-132, wherein the second cluster includes a first request and a first response to the first request, the first request for the The client device requests to query the one or more valid relay devices, and the first response is used for the first service device to return the information of the one or more valid relay devices to the client device. The configuration device of claim 133, wherein the first request is used to carry third indication information, and the third indication information is used to indicate requesting connection capabilities in the one or more effective relay devices. A valid relay device for the first connection capability. The configuration device according to any one of claims 129-134, wherein the target device is the first service device, and the sending unit is configured to send a message to the first service device in the first service device. The second cluster sends the second configuration information. The configuration device according to any one of claims 124-135, characterized in that the first relay device includes a third cluster, the third cluster is used for the client device to discover the first relay device. Whether the relay device can provide control information relay service for the first service device. The configuration device of claim 136, wherein the third cluster includes a second request and a second response to the second request, the second request being for the client device to request discovery of the Whether the first relay device can provide control information relay service for the first service device, the second response is used to indicate whether the first relay device can provide control information relay for the first service device. Serve. The configuration device of claim 137, wherein the second response includes the connection capabilities of the one or more relay devices, the identification of the first service device, the At least one of the identifiers. The configuration device according to any one of claims 124-138, wherein the target device is the first relay device, and the configuration device includes a receiving unit, The sending unit is configured to send a third request to the first relay device, where the third request is used to discover a relay device that can provide the control information relay service; In response to the third request, the receiving unit is configured to receive a third response sent by the first relay device, where the third response is used to indicate that the first relay device can provide a control information relay service. . The configuration device according to claim 139, wherein the second configuration information includes an identification of the first service device. The configuration device according to any one of claims 124 to 140, wherein the first relay device stores an access control list ACL of the first service device, and the ACL of the first service device is To record whether the client device has the authority to control the first service device. The configuration device of claim 141, wherein the control information is used to control a first service cluster in the first service device, and the target cluster included in the first relay device is the same as the target cluster in the first service device. The first service cluster is the same, the target cluster is located at the virtual node of the first relay device, and the ACL is associated with the virtual node. A relay device, characterized in that it includes a transceiver, a memory and a processor, the memory is used to store programs, and the processor is used to call the program in the memory to execute the claims through the transceiver. The method described in any one of 1-20. A client device, characterized in that it includes a transceiver, a memory and a processor, the memory is used to store a program, and the processor is used to call the program in the memory to execute the claims through the transceiver. The method described in any one of 21-36. A service device, characterized in that it includes a transceiver, a memory and a processor, the memory is used to store programs, and the processor is used to call the program in the memory to execute the claim 37 through the transceiver The method described in any one of -52. A configuration device, characterized in that it includes a transceiver, a memory and a processor, the memory is used to store a program, and the processor is used to call the program in the memory to execute the claim 53 through the transceiver The method described in any one of -71. A device, characterized by comprising a processor for calling a program from a memory to execute the method according to any one of claims 1-71. A chip, characterized in that it includes a processor for calling a program from a memory, so that a device installed with the chip executes the method according to any one of claims 1-71. A computer-readable storage medium, characterized in that a program is stored thereon, and the program causes the computer to execute the method according to any one of claims 1-71. A computer program product, characterized by comprising a program that causes a computer to execute the method according to any one of claims 1-71. A computer program, characterized in that the computer program causes a computer to perform the method according to any one of claims 1-71.

Images