WO2024050832A1

WO2024050832A1 - Command transmission method and apparatus, chip, storage medium and computer program

Info

Publication number: WO2024050832A1
Application number: PCT/CN2022/118195
Authority: WO
Inventors: 茹昭
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-09-09
Filing date: 2022-09-09
Publication date: 2024-03-14

Abstract

Provided are a command transmission method and apparatus, a chip, a storage medium, and a computer program. The method comprises: a relay device receiving a first command sent by a client device; the relay device forwarding the first command to a server device, a node identifier of the server device being recorded in one or more of the following items of information: device information of a first virtual device, the first virtual device being a virtual device in the relay device having a mapping relationship with the server device; encoding information of a command path information block corresponding to the first command. In the embodiments of the present application, the node identifier of the server device can be recorded in the first virtual device of the relay device or the encoding information of the command path information block corresponding to the first command, so that the client device can use the relay device to accurately control the server device, thereby improving a customer experience.

Description

Command transmission method, device, chip, storage medium and computer program

Technical field

The present application relates to the technical field of the Internet of Things, and more specifically, to a command transmission method, device, chip, storage medium and computer program.

Background technique

In certain scenarios (for example, the client device leaves the communication network where the server device is located), the client device can send commands to the server device through the relay device to control the server device. In this case, how the client device uses the relay device to accurately control the server device is an issue that needs to be solved urgently.

Contents of the invention

This application provides a command transmission method, device, chip, storage medium and computer program. Each aspect involved in this application is introduced below.

In a first aspect, a command transmission method is provided, including: a relay device receiving a first command sent by a client device; the relay device forwarding the first command to a server device; wherein, the server The node identification of the device is recorded in one or more of the following information: device information of the first virtual device, where the first virtual device is one of the relay devices that has a mapping relationship with the server device. Virtual device; encoding information of the command path information block corresponding to the first command.

In a second aspect, a command transmission method is provided, including: the client device sends a first command to the relay device, the first command is used to control the server device, and the first command is transmitted through the forwarded by the relay device to the server device; wherein the node identifier of the server device is recorded in one or more of the following information: device information of the first virtual device, where the first virtual device It is a virtual device in the relay device that has a mapping relationship with the server device; and the encoding information of the command path information block corresponding to the first command.

In a third aspect, a command transmission method is provided, including: a server device receiving a first command sent by a relay device, and the first command is forwarded by the client device to the server device through the relay device. ; wherein the node identification of the server device is recorded in one or more of the following information: device information of the first virtual device, where the first virtual device is the same as all the relay devices in the relay device. The server device has a virtual device with a mapping relationship; and the encoding information of the command path information block corresponding to the first command.

In a fourth aspect, a command transmission device is provided. The device is configured in a relay device. The relay device includes: a first receiving module for receiving the first command sent by the client device; a first sending module , used to forward the first command to the server device; wherein the node identifier of the server device is recorded in one or more of the following information: device information of the first virtual device, wherein the first The virtual device is a virtual device in the relay device that has a mapping relationship with the server device; the encoding information of the command path information block corresponding to the first command.

In a fifth aspect, a command transmission device is provided. The device is configured on a client device. The client device includes: a first sending module for sending a first command to a relay device. The first command Used to control the server device, the first command is forwarded to the server device through the relay device; wherein the node identification of the server device is recorded in one or more of the following information: Center: device information of the first virtual device, where the first virtual device is a virtual device in the relay device that has a mapping relationship with the server device; the command path information block corresponding to the first command encoded information.

In a sixth aspect, a command transmission device is provided. The device is configured on a server device. The server device includes: a receiving module configured to receive a first command sent by a relay device. The first command is The client device forwards it to the server device through the relay device; wherein the node identifier of the server device is recorded in one or more of the following information: device information of the first virtual device, where, The first virtual device is a virtual device in the relay device that has a mapping relationship with the server device; the encoding information of the command path information block corresponding to the first command.

In a seventh aspect, a command transmission device is provided. The device is configured in a relay device. The relay device includes a processor, a memory, and a communication interface. The memory is used to store one or more computer programs. The processor is configured to call a computer program in the memory so that the relay device performs some or all of the steps in the method of the first aspect.

In an eighth aspect, a command transmission device is provided. The device is configured on a client device. The client device includes a processor, a memory, and a communication interface. The memory is used to store one or more computer programs. The processor is configured to call a computer program in the memory so that the client device executes some or all of the steps in the method of the second aspect.

In a ninth aspect, a command transmission device is provided. The device is configured on a server device. The server device includes a processor, a memory, and a communication interface. The memory is used to store one or more computer programs. The processor is configured to call a computer program in the memory to cause the server device to execute some or all of the steps in the method of the third aspect.

In a tenth aspect, embodiments of the present application provide a communication system, which includes one or more of the above-mentioned relay devices, client devices, and server devices. In another possible design, the system may also include other devices that interact with the relay device, client device, or server device in the solution provided by the embodiments of the present application.

In an eleventh aspect, embodiments of the present application provide a computer-readable storage medium that stores a computer program. The computer program causes a relay device, a client device, or a server device to execute each of the above. Some or all of the steps in a method.

In a twelfth 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 relay device to , the client device or the server device performs some or all of the steps in the methods of the above aspects. In some implementations, the computer program product can be a software installation package.

In a thirteenth 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. .

In this embodiment of the present application, the node identifier of the server device can be recorded in the first virtual device in the relay device, so that the client device can realize the mapping relationship by querying the mapping relationship between the node identifiers of the first virtual device and the server device. Accurate control of the server device; or, the node identification of the server device can be recorded in the encoding information of the command path information block corresponding to the first command, so that the relay device can accurately control the first command according to the node identification corresponding to the first command. It is forwarded directly to the server device to improve customer experience.

Description of the drawings

Figure 1 is a schematic diagram of the model structure of a Matter device applicable to the embodiment of the present application.

FIG. 2 is an example system architecture diagram of a communication system applicable to the embodiment of the present application.

Figure 3 is an example system architecture diagram of a communication system to which the relay communication mechanism is applicable.

FIG. 4 is a schematic flowchart of a command transmission method provided by an embodiment of the present application.

Figure 5 shows an example in which a relay device maps an endpoint of a server device.

Figure 6 shows another example of a relay device mapping an endpoint of a server device.

FIG. 7 is a schematic flowchart of a command transmission method provided by another embodiment of the present application.

Figure 8 shows an example in which a relay device maps a node of a server device.

FIG. 9 is a schematic flowchart of a command transmission method provided by yet another embodiment of the present application.

Figure 10 is a schematic flowchart of a command transmission method provided by yet another embodiment of the present application.

Figure 11 is a schematic flowchart of a command transmission method provided by yet another embodiment of the present application.

Figure 12 is a schematic flowchart of a command transmission method provided by yet another embodiment of the present application.

Figure 13 is a schematic structural diagram of a relay device provided by an embodiment of the present application.

Figure 14 is a schematic structural diagram of a client device provided by an embodiment of the present application.

Figure 15 is a schematic structural diagram of a server device provided by an embodiment of the present application.

Figure 16 is a schematic structural diagram of a communication device provided by 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 FIGS. 1 to 3 . 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.

Data model for Matter devices

Figure 1 is the data model structure of the 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 functional 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.

A physical entity (for example, Matter device) may be a node 110, or the node 110 may refer to a Matter device node. It should be noted that a node can have multiple node identifiers (identifiers, 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, which define the functional clusters supported by the endpoint. In some embodiments, the endpoint may be understood to be a service/virtual device indicated by the device type. Functional clusters, on the other hand, are object classes that are instantiated on endpoints.

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

Each endpoint 120 may be a collection of functions, which may include one or more function clusters 130 .

The functional cluster 130 is a functional building block element of the data model. In some embodiments, the functional cluster can also be called a functional set, a cluster, a cluster, etc., and the embodiments of the present application are not limited to this. Functional cluster specifications define clients and servers that interact with each other. Functional cluster 130 can be viewed as an interface, service or object class, which is the lowest independent functional element in the data model. Each functional cluster 130 may be defined by a functional cluster specification that defines elements of the functional cluster 130, including attributes, events, commands, and behaviors related to interactions with these elements. In some embodiments, attributes, commands, and events can also be called interface units of the functional cluster 130, and corresponding functions can be provided through these three interface units.

In some embodiments, whether attributes, events, commands, and behaviors in functional cluster 130 are mandatory or optional depends on the definition of functional cluster 130 .

Generally, the above functional clusters can be divided into two categories: utility functional clusters (utility clusters) and application functional clusters (application clusters).

Utility feature clusters are not part of the endpoint's main application operation. Clusters of utility functions can be used for configuration, discovery, addressing, diagnostics, monitoring device health, software updates, and more. A utility functional cluster may have a temporary relationship with its functional cluster counterpart. In this embodiment of the present application, the utility cluster may include one or more of a descriptor function cluster (descriptor cluster) and a relay configuration cluster (relay configuration cluster). Of course, the embodiments of the present application are not limited to this. The utility function cluster may also include other functional clusters such as a binding function cluster.

The application function cluster supports the main operations of the endpoint. In some embodiments, the application function cluster may also be called a business function cluster. Application function clusters can support the interaction of one or more persistent applications between clients and servers. For example, in the switch function cluster (On/Off cluster) in a smart light, the client can send control commands to the server (ie, the switch function cluster) to control the switch of the smart light.

In some embodiments, the business function cluster may refer to the functional cluster on other endpoints except endpoint 0 in the node (which can be understood as the first endpoint in the node, and the device type of this endpoint is "root node") .

An application function cluster is not a utility function cluster, even though it may itself support utility functions such as calibration, operating modes, etc. Application functional cluster specifications should not involve layers and processes outside their application domain.

The following is a brief introduction to the main elements of functional clusters such as commands, properties, and events.

A functional cluster command (also known as a "command", command) is a set of data fields, each data type 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) ), conformance. Accordingly, a command can indicate zero or more fields defined in a table. Each command field is defined as a row in the table.

Attributes are functional cluster data. Currently, the agreement stipulates that each attribute can be listed in a table. The data quality columns of the attributes defined in the table can include: ID, name, (data) type (type), constraint (constraint), other qualities, access, Default (value) and conformance. 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.

An event defines a record of something that happened in the past. In this regard, an event record can be thought of as a log entry that provides a chronological view of events on a node through an event record stream. Unlike attributes, which do not provide any edge-preserving functionality (that is, there is no guarantee that every attribute change will be passed to observers), events allow each individual edge or change to be captured, and Reliably delivered to observers. This is critical for security and safety applications that rely on guarantees of correct behavior. Currently, the agreement stipulates that each functional cluster event can be listed in a table, and the data quality columns of the event defined in the table can include: ID, priority, access, and compliance.

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

Identity represents the unique field ID of the field, or the unique identifier of the command (or attribute or event).

Name represents the unique name of the field, or the name of the command (or attribute).

Type represents the data type of the field, or in other words, represents the data type of the command parameter (or attribute parameter).

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 server returns to the factory refresh settings. Default values can indicate that compliance specified for a 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.

Conformance, which 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, and "O" indicates that the corresponding command is part of the optional feature set.

For commands, client-to-server command compliance means that the server should recognize and support client-to-server commands and generate responses as defined. Server-to-client command compliance means that the server should send commands in a manner defined by cluster behavior, e.g., in response to client-to-server commands. Compliance of the command depends on 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 (range) represents the value range of the field. Range can support two forms: explicit constraint and width constraint. Among them, explicit constraints can give the minimum and maximum values corresponding to the value of the field. For example, the value range of a certain field is (0,128). Width constraints can limit the value of a field to a specific number of bytes. For example, the value of a certain field can be limited to 8 bytes. In some embodiments, the value of the range may include "N/A" to indicate not applicable. Of course, "N/A" can also appear in other parts (other data qualities), such as defaults, constraints, etc.

Priority: Each event record has an associated priority. This priority can be used to describe the usage semantics of the event.

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 device 210, a Matter server device 220, and a configuration device 230. It should be noted that the data structure model of the Matter client device 210 and the Matter server device 220 may be as shown in Figure 1 .

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

In some embodiments, the above-mentioned Matter client device 210 may refer to a terminal device with a Matter client installed, where the terminal device may be a mobile phone, a computer, a tablet, a smart bracelet, a smart watch, etc. This embodiment of the present application will Not limited. It should be understood that the Matter client can be an application (application, APP) or a small program, etc., and the embodiments of the present application are not limited to this.

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

For example, when the Matter server device 220 is a smart air conditioner that supports the Matter standard protocol, the Matter client device 210 can control the switch of the smart air conditioner and set the air conditioner temperature, wind speed, etc. When the Matter server device 220 is a sweeping robot that supports the Matter standard protocol, the Matter client device 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 server device 220 mainly include control and subscribe and report. Among them, control can be understood as a set of functional clusters that can modify or retrieve one or more attribute values of the Matter server device. For example, the Matter client device is a smart speaker and the Matter server device is a smart air conditioner. The user 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.

The configuration (commissioner) device 230 can be used to configure the Matter server device 220. In other words, the configuration device can be understood as a terminal device installed with a configuration terminal through which the user can configure the Matter server device 120 . The terminal device may be a mobile phone, a computer, a tablet, a smart bracelet, a smart watch, etc., which are not limited in the embodiments of the present application. In some embodiments, the configuration terminal may be an application program or an applet, which is not limited in the embodiments of the present application.

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

Path and command path information blocks

Paths can be used to represent various entities defined in the data model. The format of the path can be expressed as:

<cluster element>::=<attribute>|<event>|<command>.

It can be seen that the path can include several elements: target, functional cluster, and functional cluster element. In other words, the path can be composed of three elements: target, functional cluster, and functional cluster element.

In some embodiments, the target may be a group target. Group goals can be used to identify a group of goals, and this group of goals can be represented by a group ID (group ID).

In some embodiments, the target may be an endpoint target. The endpoint target can be composed of a node and an endpoint. The node can also be called a path node (corresponding to the path node mentioned later, that is, the node corresponding to the recipient of the first command, which is in the command is omitted from the encoding information of the path information block). In some embodiments, endpoints can be divided into two types: wildcard endpoints and concrete endpoints. Wildcard endpoints can represent multiple target paths, and concrete endpoints can represent a single target path.

Functional clusters can be divided into two types: wildcard functional clusters and concrete functional clusters. Wildcard functional clusters can represent multiple target paths, while concrete functional clusters can represent a single target path.

Functional cluster elements can be any of three types: attributes, events, and commands. According to different functional cluster elements, paths can be divided into attribute paths, event paths and command paths.

Property paths can be used to represent properties within a functional cluster. The format of the attributes in the attribute path can be expressed as:

<attribute>::＝<attribute ID><field>*

<field>::＝<struct field ID>|<list entry index>.

Among them, attribute ID refers to the identification (for example, number) of the target attribute in the functional cluster. Field is optional. If the attribute is not composite data, the field can be left blank. If the attribute is composite data, the field should contain the field ID. For example, if the attribute is structure data, then the field should be the structure field ID (struct field ID), and if the attribute is a list, then the field should be the list field ID (list entry index).

In the embodiment of the present application, no specific distinction is made between the identifier and the index, and they can be replaced equally. That is to say, the identifier mentioned in the embodiment of this application can be replaced by an index, or the ID in the embodiment of this application can refer to an identifier or an index.

Event paths can be used to represent a functional cluster event. The format of events in the event path can be expressed as: <event>::=<event ID>. Among them, event ID refers to the identification (for example, number) of the target event in the functional cluster.

The command path can be used to represent a functional cluster command. The format of the command in the command path can be expressed as: <command>::=<command ID>. Among them, command ID refers to the identification (for example, number) of the target command in the functional cluster.

A path can be associated with an information block (IB). For example, a command path can be associated with a command path information block (CommandPathIB). The command path information block represents the path information block of a command. The content contained in the command path information block can be seen in Table 1.

Table 1

路径字段path field	类型type	质量quality	符合性Conformity
ClusterPath(功能集群路径)ClusterPath (functional cluster path)	ClusterPathIBClusterPathIB		MM
Command(命令)Command	command-idcommand-id		MM

Among them, ClusterPathIB is the path information block of the functional cluster. command-id indicates the identification of the target command in the functional cluster. M indicates that the corresponding path field is a required field. For example, the path field ClusterPathIB is a required field.

The contents of ClusterPathIB can be seen in Table 2.

Table 2

路径字段path field	类型type	质量quality	符合性Conformity
Group(组)Group	group-idgroup-id		！Endpoint! Endpoint
Node(节点)Node	node-idnode-id		！Group! Group
Endpoint(端点)Endpoint	endpoint-idendpoint-id	AA	！Group! Group
Cluster(功能集群)Cluster (functional cluster)	cluster-idcluster-id	AA	MM

in,! Endpoint indicates that if the target of the path is an endpoint target, the path field "Group" will not be supported. ! Group means that if the target of the path is a group target, the path field "Node" and the path field "Endpoint" will not be supported. A means wildcardable, that is, wildcard characters can be used in this field.

It should be noted that the "node" field in Table 2 corresponds to the node corresponding to the recipient of the first command, that is, the path node mentioned later, which is omitted in the encoding information of the command path information block.

In some embodiments, Table 1 and Table 2 can be understood as the contents of the command path information block and the function cluster path information block defined by the data model layer.

In some embodiments, during the process of encoding the command path information block, the content of ClusterPathIB can be extended to CommandPathIB to improve encoding efficiency. Table 3 shows the contents of CommandPathIB after the contents of ClusterPathIB are expanded into CommandPathIB during coding implementation.

table 3

元素element	解释explain	标签类型Tag type	标签号tag number	TLV类型TLV type	范围scope
Endpoint(端点)Endpoint		上下文标签contextual tags	00	无符号整数unsigned integer	16比特16 bits
Cluster(功能集群)Cluster (functional cluster)		上下文标签 contextual tags	11	无符号整数unsigned integer	32比特32 bits
Command(命令)Command		上下文标签contextual tags	22	无符号整数unsigned integer	32比特32 bits

In Table 3, if an element is missing, it means that multiple elements can be wildcarded, that is, the element is a wildcard element. For example, if the endpoint element is missing, it can mean that multiple endpoints can be wildcarded.

Continuing to refer to Table 3, it can be seen that compared with Table 2, in Table 3 the node ID can be omitted in the encoding layer. This is because, for the message containing this element, the corresponding node ID (that is, the ID of the path node, or the ID of the node corresponding to the recipient of the first command) can be obtained from the message layer, so it can be omitted when encoding. . In the same way, the Group field can also be obtained from the DST (target node ID) field of the message header, so it can also be omitted during encoding.

Communication mechanism based on relay equipment

In some scenarios, for example, when the client device leaves the communication network where the server device is located, the client device can send commands (or control information, control instructions, etc.) to the server device through the relay device to Control server devices to improve customer experience.

Referring to Figure 3, communication based on relay devices usually involves Matter client devices, Matter server devices and relay devices. Among them, the relay device can forward the command sent by the client device to the server device. Moreover, the relay device can further forward the command response returned by the server device to the client device. That is to say, the relay device can provide a command relay service (which can also be called a control information relay service, a control instruction relay service, etc.), so that commands sent by the client device can pass through the relay chain provided by the command relay service. sent to the server device.

As mentioned above, the relay device can forward the commands sent by the client device to the server device. Therefore, the relay device usually has the ability to connect to the network. In other words, the relay device can be any device with network connection capabilities. For example, the relay device can be a router, a smart speaker, etc., which is not limited in the embodiments of the present application.

As a possible implementation method, after the relay device is configured with a corresponding server device, it can obtain relevant information of the server device (or target server device, target device, etc.) to communicate with the server device. The device establishes a relay relationship. For example, the relay device can obtain one or more of the following information to establish a relay relationship between the relay device and the server device: node information of the server device, endpoint information of the server device, and functional cluster of the server device. information, as well as the attribute list and command list contained in the functional cluster of the server device.

For example, the relay device can create a virtual device corresponding to the server device relayed by the relay device. In some embodiments, the correspondence between the virtual device and the server device can also be understood to mean that there is a mapping relationship between the virtual device and the server device. In some embodiments, correspondence between the virtual device and the server device may mean that the data model structure of the virtual device is consistent with the data model structure of the server device. As an implementation method, the relay device can create a virtual device to carry the service resources of the server device, and subscribe to the server device to maintain the data model structure of the virtual device consistent with the data model structure of the server device.

In this way, when the client device sends a command to the virtual device in the relay device, the relay device can forward the command to the server device corresponding to the virtual device to complete the relay of the command.

Then, when the client device provides command relay services through the relay device, how the client device uses the relay device to accurately control the server device is an urgent problem that needs to be solved. For example, a relay device can relay multiple server devices. How does the client device accurately send commands corresponding to the server devices it wants to control to the relay device.

In order to solve the above problem, embodiments of the present application provide a command transmission solution that can ensure that the client device can use the relay device to accurately control the server device. The solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

FIG. 4 is a schematic flowchart of a command transmission method provided by an embodiment of the present application. The method shown in Figure 4 is described from the perspective of interaction between a client device, a relay device, and a server device. For example, the client device and the server device may be the client device 210 and the server device 220 shown in FIG. 2 , and the relay device may be the relay device shown in FIG. 3 . The method in Figure 4 may include step S410 and step S420, and these steps will be introduced in detail below.

In step S410, the client device sends a first command to the relay device.

In step S420, the relay device forwards the first command to the server device.

The first command may be used to control the server device. For example, the first command may be used to operate a functional cluster (for example, a business function cluster) of the server device. As a specific example, assuming that the server device is a smart light, the first command can be used to operate the switch function cluster in the smart light to control the switch of the smart light. As another specific example, assuming that the server device is a smart air conditioner, the first command can be used to operate the air conditioning temperature function cluster in the smart air conditioner to control the adjustment of the temperature of the smart air conditioner.

In some embodiments, when the relay device can forward the first command to the server device, the server device can be understood as the server device relayed by the relay device. Therefore, the server device also It can be called the target server device, or simply the target device.

In some embodiments, the identity information of the server device may be indicated using the node ID of the server device. Generally speaking, in the same network, the node ID of the server device is unique, which can be used to indicate the unique identity of the server device in the network. In different networks, server devices can use different node IDs.

That is to say, in a certain network, the client device or relay device can uniquely determine its corresponding server device through the node ID of the server device.

In order to further improve the customer experience, when the relay device receives the first command sent by the client device, it can promptly feed back to the client device the command response given by the server device in response to the first command (the response result to the first command), The functional cluster in the server device corresponding to the first command can be set in the relay device. That is to say, assuming that the first command is used to control the target function cluster in the server device, the relay device may include a mapping function cluster, and the mapping function cluster is the same as the target function cluster in the server device. It should be noted that the target function cluster and the mapping function cluster are just names, which are used to indicate the mapping relationship between the two function clusters, and can also be replaced with other names.

There are many implementation methods for configuring the above target function cluster and the mapping function cluster to be the same, and the embodiments of this application are not limited to this. For example, the relay device can obtain the node, endpoint, function cluster of the server device, and the attribute list and command list contained in the function cluster, and then send a subscription request to the server device to request to subscribe to the above target function. The cluster, for example, subscribes to a list of properties and a list of commands for the target functional cluster.

In order to improve the resource utilization of the relay device, in some embodiments, the relay device can provide command relay services for multiple server devices. Therefore, a functional cluster with multiple server devices can be set up in the relay device.

As an implementation manner, the relay device may be provided with one or more virtual devices, and there is a mapping relationship between each virtual device and the server device, or in other words, each virtual device corresponds to a server device. Moreover, for the virtual devices in the relay device, each virtual device may be provided with the same functional cluster as the service function cluster in the node of the server device.

In other words, the above mapping function cluster can be set in the virtual device, and the mapping function cluster is the same as the target function cluster of the server device.

In some embodiments, the above-mentioned virtual device may be created by a relay device.

In some embodiments, the above-mentioned virtual device may include a virtual endpoint that has a mapping relationship with the service endpoint of the server device, or that the above-mentioned virtual device refers to a virtual endpoint that has a mapping relationship with the service endpoint of the server device.

In some embodiments, the above-mentioned virtual device may include a virtual node that has a mapping relationship with a node of the server device, or that the above-mentioned virtual device refers to a virtual node that has a mapping relationship with a node of the server device.

In this embodiment of the present application, the client device and/or the relay device can use the node ID of the server device to achieve accurate control of the server device.

In some embodiments, the node ID of the server device may be recorded in the device information of the first virtual device. The first virtual device is a virtual device in the relay device that has a mapping relationship with the server device. In this way, the client device can obtain the mapping relationship between the node IDs of the first virtual device and the server device by querying the device information of the first virtual device, thereby achieving accurate control of the server device and improving customer experience.

In some embodiments, the node ID of the server device may be recorded in the encoded information of the command path information block corresponding to the first command. In this way, the relay device can accurately forward the first command to the server device according to the node ID corresponding to the first command, thereby improving customer experience.

A more detailed description of how to achieve accurate control of the server device based on the node ID of the server device will be described below in conjunction with Embodiment 1 and Embodiment 2. It should be noted that Embodiment 1 and Embodiment 2 can be used partially or completely in combination, and the embodiments of the present application are not limited to this.

Embodiment 1: The node ID of the server device is recorded in the device information of the first virtual device

In some embodiments, the device information of the first virtual device may refer to the functional cluster of the first virtual device, that is, the node ID of the server device may be recorded in the functional cluster of the first virtual device.

As mentioned above, the server device may include one or more service endpoints. In some embodiments, the first virtual device may include a virtual endpoint that has a mapping relationship with the service endpoint of the server device (hereinafter, the server device includes the third A service endpoint, the first virtual device includes a first virtual endpoint that has a mapping relationship with the first service endpoint, as an example for illustration).

In some embodiments, the virtual endpoint (for example, the first virtual endpoint) in the first virtual device may include one or more functional clusters, such as a first functional cluster, a second functional cluster, etc.

In some embodiments, the node ID of the server device may be recorded in the endpoint information of the first virtual endpoint. The endpoint information of the first virtual endpoint may include, for example, the endpoint identifier of the first virtual endpoint, the functional cluster in the first virtual endpoint, and the attribute list and command list included in the functional cluster. The embodiments of the present application are not limited to this. .

In some embodiments, the node ID of the server device may be recorded in the functional cluster of the first virtual endpoint, for example, in the first functional cluster.

The first functional cluster may be any functional cluster in the first virtual endpoint, which is not specifically limited in the embodiments of this application. Several preferred embodiments of the first functional cluster are given below.

In some embodiments, the first functional cluster may be a functional cluster describing the first virtual endpoint. In some embodiments, the first functional cluster is a functional cluster used to describe the first virtual endpoint, which may mean that the first functional cluster is a functional cluster used to describe (or report) basic information of the first virtual endpoint, for example , used to describe the device type information and functional cluster information of the first virtual endpoint. In some embodiments, the first functional cluster is a functional cluster used to describe the first virtual endpoint. It can also be understood that the first functional cluster is used to describe the endpoint instance of the first virtual endpoint.

In some embodiments, the first functional cluster may be an existing functional cluster. In this case, you can add a field (for example, attribute field) to the existing functional cluster, and use this field to indicate the node ID of the server device corresponding to the first virtual endpoint.

For example, the first functional cluster may be a descriptor cluster. The descriptor function cluster can be understood as an existing function cluster, which is used to describe an endpoint in the node. In the prior art, the attributes included in the descriptor function cluster can be seen in Table 4.

Table 4

Among them, F means that the field is a fixed value; R means read permission; V means view permission; M means required.

Specifically, the device type list can give the device types and corresponding versions that the endpoint conforms to (for example, contained in the DeviceTypeStruct structure). It should be noted that the device type list should contain at least one device type. For example: the extended color light device type might support device type IDs for dimmable and switch lights because they are a subset of the extended color light.

The server list can give all functional cluster IDs on the endpoint that have the server role.

The client list can give all functional cluster IDs on the endpoint that have the client role.

The parts list gives all the endpoints that make up an instance of the device type. For example: a refrigerator device type can be defined as consisting of multiple temperature sensor endpoints, a metering endpoint, and two thermostat endpoints.

In this embodiment of the present application, a field may be added to the descriptor function cluster, and the added field may be used to indicate the node ID of the server device corresponding to the first virtual endpoint. For example, the attribute field of the original node identification (for example, represented by OriginNodeID) can be added to indicate. Specifically, when the first functional cluster in the embodiment of this application is a descriptor functional cluster, the attributes included in the descriptor functional cluster can be seen in Table 5.

table 5

Among them, O indicates that this attribute is optional, that is, this attribute only exists in some cases (such as in relay equipment).

In some embodiments, after the relay device completes the creation of the first virtual endpoint and maps the first service endpoint to the first virtual endpoint, the relay device may set the value of the attribute of the original node identification to the location where the first service endpoint is located. The node ID of the target node (or the node ID of the server device).

Figure 5 shows a specific example of a relay device mapping an endpoint of a server device. Referring to Figure 5, it is assumed that the relay device has an original endpoint EP0. The endpoint EP0 contains relay capabilities such as a relay configuration function cluster and a relay discovery function cluster. When the relay device needs to establish a relay relationship with a server device with switching capabilities, the relay device obtains the service endpoint EP1 of the server device (or node of the server device) and the function clusters and function clusters it contains. attribute list, command list and other information. Then, the relay device can create a virtual endpoint EP11, and map all the functional clusters on the endpoint EP1 of the server device and the attribute list and command list it contains to the virtual endpoint EP11. Further, the relay device may set the value of the original node identification attribute in the descriptor function cluster of the virtual endpoint EP11 to the node ID of the server device where the first service endpoint is located.

In this example, the switch (OnOff) function cluster in virtual endpoint EP11 is the same as the switch function cluster of endpoint EP1, the label (Label) function cluster in virtual endpoint EP11 is the same as the label function cluster of endpoint EP1, and the In addition to all the information of the descriptor function cluster of endpoint EP1, the descriptor function cluster also includes the node ID of the server device.

In some embodiments, the first functional cluster may be a function of a node specifically used to record the server device relayed by the first virtual endpoint (which can be understood as the node where the first service endpoint corresponding to the first virtual endpoint is located). Cluster, the first functional cluster includes the node ID of the server device relayed by the first virtual endpoint.

In some embodiments, the first functional cluster may be a newly added functional cluster, which is specially used to record the nodes of the server device relayed by the first virtual endpoint, or in other words, the new functional cluster The cluster is used to specifically record the node ID of the server device. In other words, the first functional cluster may be a new functional cluster added by the relay device to the first virtual endpoint after creating the first virtual endpoint and mapping the first service endpoint to the first virtual endpoint.

For example, after creating the first virtual endpoint and mapping the first service endpoint to the first virtual endpoint, the relay device can add a functional cluster named relayed node (RelayedNode) to the first virtual endpoint. The functional cluster The included attributes can be found in Table 6.

Table 6

The OriginNodeID attribute field may be used to indicate the node ID of the server device where the service endpoint mapped by the first virtual node is located.

In some embodiments, after the relay device adds the first functional cluster (for example, the RelayedNode functional cluster) to the first virtual endpoint, the value of the attribute identifying the original node in the first functional cluster can be set as the first service The node ID of the server device where the endpoint is located.

Figure 6 shows another specific example of a relay device mapping an endpoint of a server device. Referring to Figure 6, it is assumed that the relay device has an original endpoint EP0. The endpoint EP0 contains relay capabilities such as a relay configuration function cluster and a relay discovery function cluster. When the relay device needs to establish a relay relationship with a server device with switching capabilities, the relay device obtains information such as the service endpoint EP1 of the server device and the function cluster it contains, as well as the attribute list and command list contained in the function cluster. Then, the relay device can create a virtual endpoint EP11, and map all the functional clusters on the endpoint EP1 of the server device and the attribute list and command list it contains to the virtual endpoint EP11. Further, the relay device can add a new functional cluster named relayed node (RelayedNode) in the virtual endpoint EP11, and the node ID of the server device is recorded in the functional cluster.

In this example, the switch (OnOff) function cluster in virtual endpoint EP11 is the same as the switch function cluster of endpoint EP1, the label (Label) function cluster in virtual endpoint EP11 is the same as the label function cluster of endpoint EP1, and the The descriptor function cluster is the same as the descriptor function cluster of the endpoint EP1, and the virtual endpoint EP11 also includes a function cluster named the relayed node, and the node ID of the server device is recorded in the function cluster.

In some embodiments, the endpoint information of the first virtual endpoint may also record the network identifier of the network where the server device is located. For example, the network identifier may be recorded in the first functional cluster of the first virtual endpoint (for example, the above descriptor functional cluster or the relayed node functional cluster).

Taking the first functional cluster as the relayed node functional cluster mentioned above as an example, in addition to the original node identification attribute field, the functional cluster may also include a network identification (FabricID) attribute field. The attributes included in the first functional cluster can be found in Table 7 for details.

Table 7

The FabricID attribute field can be used to indicate the network where the server device is located, or it can also be understood as indicating the network where the node of the server device is located.

In some embodiments, the server device can be uniquely associated by combining the node ID of the server device and the network identifier of the network where the server device is located.

In the case where the node ID of the server device is recorded in the endpoint information of the first virtual endpoint, when the client device sends the first command to the relay device, the first command may be associated with the first command path information block. The encoded information of the first command path information block may include an endpoint identifier of the first virtual endpoint, an identifier of the functional cluster where the first command is located, and an identifier of the first command. For example, the encoding information of the first command path information block may be expressed as: <endpoint identification of the first virtual endpoint>/<identification of the functional cluster where the first command is located>/<identification of the first command>.

In some embodiments, the path node corresponding to the first command sent by the client device to the relay device is the relay device (or relay device node), that is, the path node is used to indicate the recipient of the first command. node.

In the case where the node ID of the server device is recorded in the endpoint information of the first virtual endpoint, when the relay device forwards the first command to the server device, the first command may be associated with the second command path information block. The encoding information of the second command path information block may include the endpoint identifier of the first service endpoint, the identifier of the functional cluster where the first command is located, and the identifier of the first command. For example, the encoding information of the second command path information block may be expressed as: <endpoint identifier of the first service endpoint>/<identifier of the functional cluster where the first command is located>/<identifier of the first command>.

In some embodiments, before sending the first command to the relay device, the client device may also query the device information of the virtual device (for example, the first virtual device) in the relay device to determine the mapping relationship between the virtual device and the server device, and then accurately sends the first command to the relay device according to the mapping relationship.

FIG. 7 is a schematic flowchart of a command transmission method provided by another embodiment of the present application. As shown in Figure 7, the method of Figure 7 may include steps S710 to S740. These steps are described below.

In step S710, the client device sends a first message to the relay device, where the first message is used to query the first functional cluster. The first functional cluster refers to a functional cluster in the relay device that records the node ID of the server device.

In some embodiments, the first functional cluster may refer to the functional cluster mentioned above for describing the first virtual endpoint, for example, the descriptor functional cluster.

In some embodiments, the first functional cluster may refer to the functional cluster mentioned above that is specially used to record the node to which the first virtual endpoint is relayed, for example, the relayed node functional cluster.

In step S720, the relay device sends a first response to the client device, where the first response includes the information of the above-mentioned first functional cluster.

In some embodiments, the first response may mean that the relay device returns the first functional cluster to the client device. The client device may obtain the server device corresponding to the first virtual endpoint according to the attribute field in the first functional cluster. Node ID.

However, the embodiments of the present application are not limited to this. In some embodiments, the client device may directly request to query the attribute field used to record the node ID of the server device in the first functional cluster. For example, directly request to query the first functional cluster. The original node identification attribute in the functional cluster to obtain the node ID of the server device.

In some embodiments, the information of the first functional cluster can be used by the client device to display the server device corresponding to the node identifier according to the node identifier. For example, the client device only displays the server device corresponding to the node identifier for convenience. User control.

In step S730, the client device sends a first command to the relay device.

In step S740, the relay device forwards the first command to the server device.

For detailed description of step S730 and step S740, please refer to the previous description of step S410 and step S420, which will not be described again here.

In some embodiments, after the client device obtains the node ID of the server device corresponding to the first virtual endpoint in the relay device, it can also establish a direct connection between the first virtual endpoint and the client device based on the node ID of the server device. The pointing relationship between connected server devices. In some embodiments, the pointing relationship can be used by the client device to display the server device corresponding to the node identifier according to the node identifier. For example, the client device only displays the server device corresponding to the node identifier to facilitate user control.

Continuing to refer to Figure 7, in some embodiments, the method shown in Figure 7 may further include step S725. In step S725, the client device establishes a pointing relationship between the first virtual endpoint and the server device directly connected to the client device according to the node ID of the server device.

For example, the server device is smart air conditioner A. When the connection is discovered locally, the client device has established a control relationship with the server device and displays the server device in the client device's controllable device list (controllable device). The list can be used to indicate information about server devices directly connected to the client device). When the client device discovers the first virtual endpoint whose device type is an air conditioner through the relay device, and the value of the attribute field in the first virtual endpoint used to record the node ID of the server device is the same as the value of the previously locally connected smart air conditioner A If the node IDs are the same, the client device can point the first virtual endpoint of the relay device to the smart air conditioner A in the controllable device list to establish a pointing relationship between the first virtual endpoint and the server device directly connected to the client device. .

In some embodiments, if the endpoint information of the first virtual endpoint also records the network identifier of the network where the server device is located, the network identifier and the node ID of the server device can be combined to uniquely associate the server device.

That is to say, in some embodiments, when establishing the pointing relationship between the first virtual endpoint and the server device directly connected to the client device, the network identifier of the network where the server device is located may also be considered. For example, the client device may compare the network identifier obtained from the endpoint information of the first virtual endpoint with the network identifier of the network where the actual server device is located to determine whether there is a match.

By establishing a pointing relationship between the virtual endpoint in the relay device and the server device directly connected to the client device, it can solve the problem that the client device cannot identify the server device relayed by the relay device, so as to communicate with the client device. Corresponding issues found on the server device during direct connection enable users to maintain a consistent experience of relay control and direct connection control.

Embodiment 2: The node ID of the server device is recorded in the encoding information of the command path information block corresponding to the first command.

In some embodiments, the first virtual device may include a virtual node that has a mapping relationship with the server device (the first virtual node is used as an example for description below).

In some embodiments, a virtual node (eg, a first virtual node) in the first virtual device may include one or more endpoints (eg, a service endpoint), and each endpoint may include one or more functional clusters, such as First functional cluster, second functional cluster, etc.

In some embodiments, after obtaining the node information of the server device, the relay device can create a first virtual node corresponding to the server device, and map the node of the server device to the first virtual node.

Figure 8 shows a specific example of a relay device mapping a node of a server device. Referring to Figure 8, it is assumed that the relay device includes the original node Node0, that is, the node that provides relay services. The original node Node0 of the relay device contains 3 endpoints. When the relay device needs to establish a relay relationship with the node Node0 of the server device with switching capability, the relay device can obtain 2 service endpoints EP1 and EP2 among the 3 endpoints of the node Node0 of the server device, as well as two services Information such as the functional clusters contained in endpoints EP1 and EP2, the attribute list and command list contained in the functional clusters. Then, the relay device can create a virtual node Node1, and map the endpoints EP1 and EP2 on the node Node0 of the server device and the functional clusters they contain, as well as the attribute list and command list contained in the functional clusters, to the virtual node Node1.

In this example, the virtual node Node1 contains two service endpoints EP1 and EP2 in the node Node0 of the server device. However, the embodiments of the present application are not limited to this. In some embodiments, the relay device can connect all endpoints of the node Node0 of the server device (3 endpoints in this example), as well as the function clusters and functions contained in all endpoints. The attribute list, command list and other information contained in the cluster are mapped to the virtual node Node1.

In some embodiments, after the relay device adds the first virtual node, the node ID of the server device can be added to the relay configuration cluster (RelayConfiguration Cluster) of the relay device. For example, it can be added to the relay configuration cluster. In the target node (or target list, TargetList) field.

The relay configuration cluster included in the relay device can be used to allow users to configure the server devices that the relay device relays. The attributes included in the relay configuration cluster can be seen in Table 8.

Table 8

Among them, N means that the attribute is non-volatile and remains valid after the device is restarted. W means write permission.

The fields that ConfigurationStruct can include can be found in Table 9.

Table 9

Among them, the network identifier is used to indicate the index of the network where the device is located. The target list is a list indicating node IDs of server devices to which the relay device relays.

In some embodiments, the relay device may extend the encoding information of the command path information block of its own command. Specifically, a first element (node element) may be added to the encoding information of the command path information block. The first element may be used to indicate node information of the server device corresponding to the command sent to the relay device.

For example, the content of the encoding information of the command path information block can be seen in Table 10.

Table 10

元素element	解释explain	标签类型Tag type	标签号tag number	TLV类型TLV type	范围scope
Node(节点)Node		上下文标签contextual tags	00	无符号整数unsigned integer	64比特64 bits
Endpoint(端点)Endpoint		上下文标签 contextual tags	11	无符号整数unsigned integer	16比特16 bits
Cluster(功能集群)Cluster (functional cluster)		上下文标签contextual tags	22	无符号整数unsigned integer	32比特32 bits
Command(命令)Command		上下文标签contextual tags	33	无符号整数unsigned integer	32比特32 bits

In this way, after the relay device receives the command sent by the client device, it can accurately know which server device the command is sent to based on the encoding information of the command path information block corresponding to the command, and then accurately forward the command to the server device. Forwarded to the corresponding server device.

As a possible implementation method, after receiving the command sent by the client device, the relay device can determine whether the command is sent to the center based on the node ID recorded in the "node" element in the encoding information of the command path information block. The first virtual node in the relay device, and then forwards the command to the corresponding server device according to the mapping relationship between the first virtual node and the node of the server device.

As another possible implementation, after receiving the command sent by the client device, the relay device can directly determine whether the command is sent based on the node ID recorded in the "node" element in the encoding information of the command path information block. Which server device it is for, and forward the command to the corresponding server device.

In the case where the relay device creates the first virtual node mapping server device, when the client device sends the first command to the relay device, the first command may be associated with the third command path information block. The encoding information of the third command path information block may include the node ID of the server device, the endpoint identifier of the endpoint where the first command is located, the identifier of the functional cluster where the first command is located, and the identifier of the first command. For example, the encoding information of the third command path information block can be expressed as: <node ID of the server device>/<endpoint identification of the endpoint where the first command is located>/<identification of the functional cluster where the first command is located>/<first command The logo>.

In some embodiments, the path node corresponding to the first command sent by the client device to the relay device is the relay device node, and the relay device node can be understood as the original node of the relay device.

In the case where the relay device creates the first virtual node mapping server device, when the relay device forwards the first command to the server device, the first command may be associated with the fourth command path information block. The encoding information of the fourth command path information block may include an endpoint identifier of the endpoint where the first command is located, an identifier of the functional cluster where the first command is located, and an identifier of the first command. For example, the encoding information of the fourth command path information block can be expressed as: <endpoint identifier of the endpoint where the first command is located>/<identification of the functional cluster where the first command is located>/<identification of the first command>.

FIG. 9 is a schematic flowchart of a command transmission method provided by yet another embodiment of the present application. As shown in Figure 9, the method in Figure 9 may also include steps S910 to S940. These steps are described below.

In step S910, the client device sends a second message to the relay device. The second message is used to query the target node information in the relay configuration cluster. The target node information records the node ID of the server device.

In some embodiments, the target node information may refer to information related to the target list mentioned above, and the target list may record the node IDs of one or more relayed server devices.

In step S920, the relay device sends the target node information to the client device.

The client device can determine whether a server device is relayed by the relay device by querying the target list in the configured cluster, so that commands can be forwarded through the relay device.

In some embodiments, the target node information can be used by the client device to display the server device corresponding to the node identifier according to the node identifier. For example, the client device only displays the server device corresponding to the node identifier to facilitate user control.

In step S930, the client device sends a first command to the relay device.

In step S940, the relay device forwards the first command to the server device.

For relevant descriptions of step S930 and step S940, please refer to the previous description of step S410 and step S420, which will not be described again here.

In some embodiments, after the client device obtains the node ID of the server device corresponding to the first virtual node in the relay device, it can also establish a direct connection between the first virtual node and the client device based on the node ID of the server device. The pointing relationship between connected server devices. In some embodiments, the pointing relationship can be used by the client device to display the server device corresponding to the node identifier according to the node identifier. For example, the client device only displays the server device corresponding to the node identifier to facilitate user control.

Continuing to refer to Figure 9, in some embodiments, the method shown in Figure 9 may further include step S925. In step S925, the client device establishes a pointing relationship between the first virtual node and the server device directly connected to the client device according to the node ID of the server device.

For example, the server device is smart air conditioner A. When the connection is discovered locally, the client device has established a control relationship with the server device and displays the server device in the controllable device list of the client device. When the client device obtains the first node ID from the target node information of the relay device, the first node ID corresponds to the first virtual node, and the first node ID is the same as the node ID of the previously locally connected smart air conditioner A, then The client device can point the first virtual node of the relay device to the smart air conditioner A in the controllable device list to establish a pointing relationship between the first virtual node and the server device directly connected to the client device.

In some embodiments, the relay device, client device, and server device may all be in the same network. In some embodiments, the relay device, client device, and server device may be located in different networks, which is not limited in the embodiments of the present application.

For ease of understanding, the method flow of the embodiment of the present application will be introduced below with reference to Figures 10 to 12, 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 above client device can also be called a Matter client device, and the above server device can also be called a Matter server device. In addition, the functional clusters involved in the methods shown in Figures 10 to 12 have been introduced in detail above, and for the sake of simplicity, they will not be described again below.

It should be noted that the embodiments of the present application do not specifically limit the execution order of each step. The following sequence is an illustration only. During actual execution, only some of the listed steps may be executed, or more steps than the listed steps may be executed. Alternatively, during actual execution, the order of execution may be exchanged. Taking the steps shown in Figure 10 as an example, step S1060 may not be executed in some solutions, or S1060 may be executed after step S1070 or S1080 in some solutions. The embodiments of the present application are not limited to this. .

In some embodiments, the server device may refer to a smart home device in the user's home, for example, the relay device may refer to a router, and the user may act as a client through an APP on the terminal device (that is, the client device is a terminal device) Realize the control of smart home devices through the router.

Figure 10 is a schematic flowchart of a command transmission method provided by yet another embodiment of the present application. The method shown in FIG. 10 may include steps S1010 to S1080.

In step S1010, the relay device obtains information about the first service endpoint of the server device.

The server device can be understood as a relayed target device corresponding to the relay device, or a target server device.

In some embodiments, the relay device can read the information of nodes, endpoints, and functional clusters of the server device, and initiate a subscription request to the business function cluster in the server device to request to subscribe to the information contained in the business function cluster. Property list and command list. Correspondingly, when the server device allows the above subscription request, the server device can send the attribute list and command list included in the business function cluster to the relay device.

In step S1020, the relay device creates a first virtual endpoint.

The first virtual endpoint has a mapping relationship with the above-mentioned first service endpoint. In other words, the relay device can map all functional clusters of the first service endpoint and the attributes and commands it contains to the created first virtual endpoint.

Further, the relay device may set the original node identification (OriginNodeID) attribute value of the descriptor function cluster in the first virtual endpoint to the node ID of the server device.

In step S1030, the client device queries the endpoint information of the first virtual endpoint.

The client device can obtain description information such as the controllable interface of the first virtual endpoint by querying the endpoint information of the first virtual endpoint.

In step S1040, the relay device returns the descriptor function cluster attribute of the first virtual endpoint to the client device.

In step S1050, the client device obtains the original node identification attribute information from the descriptor function cluster attribute of the first virtual endpoint, that is, obtains the node ID of the server device.

In some embodiments, the client device can also directly query the original node identification attribute of the descriptor function cluster of the first virtual endpoint to obtain the node ID of the server device.

In step S1060, the client device establishes a pointing relationship with the server device obtained in the local discovery connection through the obtained node ID of the server device.

For example, if the server device is smart air conditioner A, the client device has established a control relationship with the device when the connection is discovered locally, and the device is displayed in the controllable device list of the client device. When the client device passes If the relay device discovers an endpoint whose device type is an air conditioner, and the value of the original node identification attribute is the same as the node ID of the previously locally connected smart air conditioner A, the client device can transfer the corresponding endpoint (first virtual endpoint) of the relay device to Point to smart air conditioner A in the controllable device list.

In step S1070, the client device sends a first command to the first virtual endpoint of the relay device.

The node of the path corresponding to the first command is a relay device node. The encoding information of the command path information block corresponding to the first command includes <endpoint identification of the first virtual endpoint>/<identification of the functional cluster where the first command is located>/<th The identifier of a command>.

In step S1080, the relay device forwards the first command to the server device.

After receiving the first command, the relay device may forward the first command to the server device according to the mapping relationship (or relay relationship) between the first virtual endpoint and the first service endpoint. Specifically, the relay device may send the first command to the following path of the server device: the node of the path corresponding to the first command is the server device node, and the encoding information of the command path information block corresponding to the first command includes <first Endpoint identification of the business endpoint>/<Identity of the functional cluster where the first command is located>/<Identity of the first command>.

Figure 11 is a schematic flowchart of a command transmission method provided by yet another embodiment of the present application. The method shown in FIG. 11 may include steps S1110 to S1190.

In step S1110, the relay device obtains the information of the first service endpoint of the server device.

In step S1120, the relay device creates a first virtual endpoint.

For the first service endpoint of the server device, the relay device creates a first virtual endpoint, and the first virtual endpoint has a mapping relationship with the first service endpoint. In other words, the relay device can map all functional clusters of the first service endpoint and the attributes and commands they contain to the first virtual endpoint.

Further, the relay device can add a first functional cluster to the first virtual endpoint. The first functional cluster is a new functional cluster. The new functional cluster is used to specifically record the server device relayed by the first virtual endpoint. node information.

In step S1130, the client device queries the information of the first functional cluster.

The client device can obtain the node ID of the server device corresponding to the first virtual endpoint by querying the information of the first functional cluster.

In step S1140, the relay device returns the attributes of the first functional cluster to the client device.

In step S1150, the client device obtains the original node identification attribute information from the first functional cluster attribute, that is, obtains the node ID of the server device.

In some embodiments, the client device can also directly query the original node identification attribute in the first functional cluster to obtain the node ID of the server device.

In step S1160, the client device obtains the network identifier of the network where the original node is located from the attribute information of the first functional cluster, that is, the client device obtains the network identifier of the network where the server device is located.

In step S1170, the client device establishes a pointing relationship with the server device obtained in the local discovery connection through the obtained node ID of the server device.

Further, if it is necessary to uniquely associate the server device with the network identifier and the node ID, the obtained identifier of the network where the original node is located can also be compared with the network identifier of the network where the node of the actual server device is located to determine whether there is a match, where, The identity of the network where the original node is located is obtained from the network identity attribute in the first functional cluster of the first virtual endpoint.

In step S1180, the client device sends a first command to the first virtual endpoint of the relay device.

In step S1190, the relay device forwards the first command to the server device.

Figure 12 is a schematic flowchart of a command transmission method provided by yet another embodiment of the present application. The method shown in FIG. 12 may include steps S1210 to S1280.

In step S1210, the relay device obtains node information of the server device, and the node ID of the server device is AAA.

In step S1220, the relay device creates a first virtual node.

For the node of the server device, the relay device creates a first virtual node, and maps the business endpoint contained in the node of the server device (as well as all the functional clusters contained in the business endpoint and the attributes and commands it contains) to the first virtual node .

Further, the relay device can establish an association between the first virtual node and the node ID of the server device, that is, establish an association between the first virtual node and the node ID AAA.

In step S1230, the client device checks the relay configuration function cluster of the original node of the relay device to check the target list attribute of the relay configuration function cluster.

For example, the client device can view the endpoint EP0 in the original node. The device type of the endpoint EP0 is "root node". The endpoint EP0 includes the relay configuration function cluster mentioned above.

The client device can determine whether the relay device can relay the server device whose node ID is AAA by querying the target list attribute.

In step S1240, the relay device returns the target node list of the target list attribute to the client device.

In step S1250, the client device obtains the node ID AAA from the target node list of the target list attribute, that is, obtains the node ID of the server device.

In step S1260, the client device establishes a pointing relationship with the server device obtained in the local discovery connection through the obtained node ID of the server device.

For example, if the server device is smart air conditioner A, the client device has established a control relationship with the device when the connection is discovered locally, and displays the device in the controllable device list of the client device. The node ID AAA is obtained in the target node list of the device, and AAA is the same as the node ID of the previously locally connected smart air conditioner A, then the client device can point the corresponding node (first virtual node) of the relay device to the controllable device list Smart air conditioner in A.

In step S1270, the client device sends the first command to the original node of the relay device.

The node of the path corresponding to the first command is a relay device node. The encoding information of the command path information block corresponding to the first command includes <node ID of the server device>/<endpoint identifier of the endpoint where the first command is located>/<first The identifier of the functional cluster where the command is located>/<the identifier of the first command>.

In step S1280, the relay device forwards the first command to the server device.

Specifically, after receiving the first command, the relay device can determine that the first command is sent to the first virtual node according to the mapping relationship (or association relationship) between the first virtual node and the node ID AAA, and determine the first command according to the first virtual node. The mapping relationship between the virtual node and the server device forwards the first command to the server device. Specifically, the first command can be sent to the following path of the server device: the node of the path corresponding to the first command is the server device node, and the encoding information of the command path information block corresponding to the first command includes <endpoint where the first command is located The endpoint identifier>/<the identifier of the functional cluster where the first command is located>/<the identifier of the first command>.

The method embodiments of the present application are described in detail above with reference to FIGS. 1 to 12 , and the device embodiments of the present application are described in detail below with reference to FIGS. 13 to 16 . It should be understood that the description of the method embodiments corresponds to the description of the device embodiments. Therefore, for parts not described in detail, please refer to the previous method embodiments.

Figure 13 is a schematic structural diagram of a relay device provided by an embodiment of the present application. The relay device 1300 shown in Figure 13 can be used for command transmission. The relay device 1300 includes a first receiving module 1310 and a first sending module 1320.

The first receiving module 1310 may be used to receive the first command sent by the client device.

The first sending module 1320 may be used to forward the first command to the server device, where the node identifier of the server device is recorded in one or more of the following information: device information of the first virtual device, where , the first virtual device is a virtual device in the relay device that has a mapping relationship with the server device; and the encoding information of the command path information block corresponding to the first command.

Optionally, the server device includes a first service endpoint, the first virtual device includes a first virtual endpoint that has a mapping relationship with the first service endpoint, and the node identification is recorded in the endpoint of the first virtual endpoint. information.

Optionally, the first virtual endpoint includes a first functional cluster, and the node identification is recorded in the first functional cluster; wherein the first functional cluster is one of the following functional clusters: used to describe the A functional cluster of the first virtual endpoint; and a functional cluster dedicated to recording the node to which the first virtual endpoint is relayed.

Optionally, the relay device 1300 further includes: a second receiving module, configured to receive a first message sent by the client device, where the first message is used to query the first functional cluster; a second sending module, Used to send a first response to the client device, where the first response contains information about the first functional cluster.

Optionally, the information of the first functional cluster is used by the client device to display the server device corresponding to the node identifier according to the node identifier.

Optionally, the endpoint information of the first virtual endpoint records the network identifier of the network where the server device is located.

Optionally, the first command received by the relay device is associated with a first command path information block, and the encoding information of the first command path information block includes the endpoint identification of the first virtual endpoint, and the The identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or the first command sent by the relay device to the server device is associated with the second command path information block, so The encoding information of the second command path information block includes the endpoint identifier of the first service endpoint, the identifier of the functional cluster where the first command is located, and the identifier of the first command.

Optionally, the first virtual device includes a first virtual node that has a mapping relationship with the server device.

Optionally, the relay device 1300 further includes: a third receiving module, configured to receive a second message sent by the client device, where the second message is used to query the target node information in the relay configuration cluster, the The target node information is recorded with the node identifier; a third sending module is used to send the target node information to the client device.

Optionally, the target node information is used by the client device to display the server device corresponding to the node identifier according to the node identifier.

Optionally, the first command received by the relay device is associated with a third command path information block, the encoding information of the third command path information block includes the node identifier, and the endpoint where the first command is located The endpoint identifier, the identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or, the first command and the fourth command sent by the relay device to the server device Path information block association, the encoding information of the fourth command path information block includes the endpoint identifier of the endpoint where the first command is located, the identifier of the functional cluster where the first command is located, and the identifier of the first command.

Figure 14 is a schematic structural diagram of a client device provided by an embodiment of the present application. The client device 1400 shown in FIG. 14 can be used for command transmission, and the client device 1400 includes a first sending module 1410.

The first sending module 1410 may be used to send a first command to the relay device. The first command is used to control the server device. The first command is forwarded to the server device through the relay device. ; wherein the node identification of the server device is recorded in one or more of the following information: device information of the first virtual device, where the first virtual device is the same as all the relay devices in the relay device. The server device has a virtual device with a mapping relationship; and the encoding information of the command path information block corresponding to the first command.

Optionally, the client device 1400 further includes: a second sending module 1420, used to send a first message to the relay device, where the first message is used to query the first functional cluster; a first receiving module, Used to receive a first response sent by the relay device, where the first response contains information about the first functional cluster.

Optionally, the first command sent by the client device to the relay device is associated with a first command path information block, and the encoding information of the first command path information block includes the first virtual endpoint. The endpoint identifier, the identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or the first command and the second command path sent by the relay device to the server device Information block association, the encoding information of the second command path information block includes the endpoint identifier of the first service endpoint, the identifier of the functional cluster where the first command is located, and the identifier of the first command.

Optionally, the client device 1400 further includes: a first establishment module, configured to establish a pointing relationship between the first virtual endpoint and the server device directly connected to the client device according to the node identifier.

Optionally, the pointing relationship is used for the client device to display the server device corresponding to the node identifier according to the node identifier.

Optionally, the client device 1400 further includes: a third sending module, configured to send a second message to the relay device, where the second message is used to query target node information in the relay configuration cluster. The target The node information is recorded with the node identifier; the second receiving module is used to receive the target node information sent by the relay device.

Optionally, the first command sent by the client device to the relay device is associated with a third command path information block, and the encoding information of the third command path information block includes the node identifier, and the The endpoint identifier of the endpoint where the first command is located, the identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or the first message sent by the relay device to the server device. The command is associated with a fourth command path information block, and the encoding information of the fourth command path information block includes an endpoint identifier of the endpoint where the first command is located, an identifier of the functional cluster where the first command is located, and the first command logo.

Optionally, the client device 1400 further includes: a second establishment module, configured to establish a pointing relationship between the first virtual node and the server device directly connected to the client device according to the node identifier.

Figure 15 is a schematic structural diagram of a server device provided by an embodiment of the present application. The server device 1500 shown in Figure 15 can be used for command transmission. The server device 1500 includes a receiving module 1510.

The receiving module 1510 may be used to receive the first command sent by the relay device, which is forwarded by the client device to the server device through the relay device; wherein, the node identifier of the server device Recorded in one or more of the following information: device information of a first virtual device, where the first virtual device is a virtual device in the relay device that has a mapping relationship with the server device; The encoding information of the command path information block corresponding to the first command.

Optionally, the first command received by the relay device is associated with a first command path information block, and the encoding information of the first command path information block includes the endpoint identification of the first virtual endpoint, and the The identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or the first command received by the server device is associated with a second command path information block, and the second command path The encoded information of the information block includes the endpoint identifier of the first service endpoint, the identifier of the functional cluster where the first command is located, and the identifier of the first command.

Optionally, the first command received by the relay device is associated with a third command path information block, the encoding information of the third command path information block includes the node identifier, and the endpoint where the first command is located The endpoint identifier, the identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or, the first command received by the server device is associated with the fourth command path information block, The encoding information of the fourth command path information block includes the endpoint identifier of the endpoint where the first command is located, the identifier of the functional cluster where the first command is located, and the identifier of the first command.

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

Apparatus 1600 may include one or more processors 1610. The processor 1610 can support the device 1600 to implement the method described in the foregoing method embodiments. The processor 1610 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 1600 may also include one or more memories 1620. The memory 1620 stores a program, which can be executed by the processor 1610, so that the processor 1610 executes the method described in the foregoing method embodiment. The memory 1620 may be independent of the processor 1610 or integrated in the processor 1610.

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

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 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

A command transmission method, characterized by including:

The relay device receives the first command sent by the client device;

The relay device forwards the first command to the server device;

Wherein, the node identification of the server device is recorded in one or more of the following information:

Device information of a first virtual device, wherein the first virtual device is a virtual device in the relay device that has a mapping relationship with the server device;

Encoding information of the command path information block corresponding to the first command.
The method of claim 1, wherein the server device includes a first service endpoint, the first virtual device includes a first virtual endpoint that has a mapping relationship with the first service endpoint, and the node The identification is recorded in the endpoint information of the first virtual endpoint.
The method of claim 2, wherein the first virtual endpoint includes a first functional cluster, and the node identifier is recorded in the first functional cluster;

Wherein, the first functional cluster is one of the following functional clusters:

a functional cluster describing the first virtual endpoint; and

A functional cluster dedicated to recording the nodes relayed by the first virtual endpoint.
The method of claim 3, further comprising:

The relay device receives a first message sent by the client device, where the first message is used to query the first functional cluster;

The relay device sends a first response to the client device, where the first response includes information about the first functional cluster.
The method according to claim 3 or 4, characterized in that the information of the first functional cluster is used by the client device to display the server device corresponding to the node identifier according to the node identifier.
The method according to any one of claims 2 to 5, characterized in that the endpoint information of the first virtual endpoint records a network identifier of the network where the server device is located.
The method according to any one of claims 2-6, characterized in that:

The first command received by the relay device is associated with a first command path information block, and the encoding information of the first command path information block includes an endpoint identifier of the first virtual endpoint, where the first command is located. The identification of the functional cluster, and the identification of the first command; and/or

The first command sent by the relay device to the server device is associated with a second command path information block, and the encoding information of the second command path information block includes the endpoint identification of the first service endpoint, so The identifier of the functional cluster where the first command is located, and the identifier of the first command.
The method of claim 1, wherein the first virtual device includes a first virtual node that has a mapping relationship with the server device.
The method of claim 8, further comprising:

The relay device receives the second message sent by the client device, the second message is used to query the target node information in the relay configuration cluster, and the target node information records the node identifier;

The relay device sends the target node information to the client device.
The method according to claim 9, characterized in that the target node information is used by the client device to display the server device corresponding to the node identifier according to the node identifier.
The method according to any one of claims 8-10, characterized in that:

The first command received by the relay device is associated with a third command path information block, and the encoding information of the third command path information block includes the node identifier, the endpoint identifier of the endpoint where the first command is located, The identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or

The first command sent by the relay device to the server device is associated with a fourth command path information block, and the encoding information of the fourth command path information block includes an endpoint identifier of the endpoint where the first command is located, The identifier of the functional cluster where the first command is located, and the identifier of the first command.
A command transmission method, characterized by including:

The client device sends a first command to the relay device, the first command is used to control the server device, and the first command is forwarded to the server device through the relay device;

Wherein, the node identification of the server device is recorded in one or more of the following information:

Device information of a first virtual device, wherein the first virtual device is a virtual device in the relay device that has a mapping relationship with the server device;

Encoding information of the command path information block corresponding to the first command.
The method of claim 12, wherein the server device includes a first service endpoint, the first virtual device includes a first virtual endpoint that has a mapping relationship with the first service endpoint, and the node The identification is recorded in the endpoint information of the first virtual endpoint.
The method of claim 13, wherein the first virtual endpoint includes a first functional cluster, and the node identification is recorded in the first functional cluster;

Wherein, the first functional cluster is one of the following functional clusters:

a functional cluster describing the first virtual endpoint; and

A functional cluster dedicated to recording the nodes relayed by the first virtual endpoint.
The method of claim 14, further comprising:

The client device sends a first message to the relay device, where the first message is used to query the first functional cluster;

The client device receives a first response sent by the relay device, where the first response contains information of the first functional cluster.
The method according to any one of claims 13 to 15, characterized in that the endpoint information of the first virtual endpoint records a network identifier of the network where the server device is located.
The method according to any one of claims 13-16, characterized in that:

The first command sent by the client device to the relay device is associated with a first command path information block, and the encoding information of the first command path information block includes an endpoint identification of the first virtual endpoint, so The identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or

The first command sent by the relay device to the server device is associated with a second command path information block, and the encoding information of the second command path information block includes the endpoint identification of the first service endpoint, so The identifier of the functional cluster where the first command is located, and the identifier of the first command.
The method according to any one of claims 13-17, characterized in that the method further includes:

The client device establishes a pointing relationship between the first virtual endpoint and the server device directly connected to the client device according to the node identifier.
The method according to claim 18, wherein the pointing relationship is used for the client device to display the server device corresponding to the node identifier according to the node identifier.
The method of claim 12, wherein the first virtual device includes a first virtual node having a mapping relationship with the server device.
The method of claim 20, further comprising:

The client device sends a second message to the relay device, the second message is used to query target node information in the relay configuration cluster, and the target node information records the node identifier;

The client device receives the target node information sent by the relay device.
The method according to claim 20 or 21, characterized in that:

The first command sent by the client device to the relay device is associated with a third command path information block, and the encoding information of the third command path information block includes the node identifier, where the first command is located. The endpoint identifier of the endpoint, the identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or

The first command sent by the relay device to the server device is associated with a fourth command path information block, and the encoding information of the fourth command path information block includes an endpoint identifier of the endpoint where the first command is located, The identifier of the functional cluster where the first command is located, and the identifier of the first command.
The method according to any one of claims 20-22, characterized in that the method further includes:

The client device establishes a pointing relationship between the first virtual node and the server device directly connected to the client device according to the node identifier.
The method according to claim 23, characterized in that the pointing relationship is used for the client device to display the server device corresponding to the node identifier according to the node identifier.
A command transmission method, characterized by including:

The server device receives the first command sent by the relay device, and the first command is forwarded by the client device to the server device through the relay device;

Wherein, the node identification of the server device is recorded in one or more of the following information:

Device information of a first virtual device, wherein the first virtual device is a virtual device in the relay device that has a mapping relationship with the server device;

Encoding information of the command path information block corresponding to the first command.
The method of claim 25, wherein the server device includes a first service endpoint, the first virtual device includes a first virtual endpoint that has a mapping relationship with the first service endpoint, and the node The identification is recorded in the endpoint information of the first virtual endpoint.
The method of claim 26, wherein the first virtual endpoint includes a first functional cluster, and the node identification is recorded in the first functional cluster;

Wherein, the first functional cluster is one of the following functional clusters:

a functional cluster describing the first virtual endpoint; and

A functional cluster dedicated to recording the nodes relayed by the first virtual endpoint.
The method according to claim 26 or 27, characterized in that the endpoint information of the first virtual endpoint records a network identifier of the network where the server device is located.
The method according to any one of claims 26-28, characterized in that:

The first command received by the relay device is associated with a first command path information block, and the encoding information of the first command path information block includes an endpoint identifier of the first virtual endpoint, where the first command is located. The identification of the functional cluster, and the identification of the first command; and/or

The first command received by the server device is associated with a second command path information block, and the encoding information of the second command path information block includes the endpoint identifier of the first service endpoint, where the first command is located. The identifier of the functional cluster, and the identifier of the first command.
The method of claim 25, wherein the first virtual device includes a first virtual node having a mapping relationship with the server device.
The method according to claim 30, characterized in that:

The first command received by the relay device is associated with a third command path information block, and the encoding information of the third command path information block includes the node identifier, the endpoint identifier of the endpoint where the first command is located, The identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or

The first command received by the server device is associated with a fourth command path information block. The encoding information of the fourth command path information block includes an endpoint identifier of the endpoint where the first command is located. The first command The identifier of the functional cluster where it is located, and the identifier of the first command.
A command transmission device, characterized in that the device is configured in a relay device, and the relay device includes:

A first receiving module, configured to receive the first command sent by the client device;

A first sending module, configured to forward the first command to the server device;

Wherein, the node identification of the server device is recorded in one or more of the following information:

Device information of a first virtual device, wherein the first virtual device is a virtual device in the relay device that has a mapping relationship with the server device;

Encoding information of the command path information block corresponding to the first command.
The apparatus according to claim 32, wherein the server device includes a first service endpoint, the first virtual device includes a first virtual endpoint having a mapping relationship with the first service endpoint, and the node The identification is recorded in the endpoint information of the first virtual endpoint.
The device according to claim 33, wherein the first virtual endpoint includes a first functional cluster, and the node identification is recorded in the first functional cluster;

Wherein, the first functional cluster is one of the following functional clusters:

a functional cluster describing the first virtual endpoint; and

A functional cluster dedicated to recording the nodes relayed by the first virtual endpoint.
The device of claim 34, further comprising:

a second receiving module, configured to receive the first message sent by the client device, where the first message is used to query the first functional cluster;

The second sending module is configured to send a first response to the client device, where the first response contains information about the first functional cluster.
The apparatus according to claim 34 or 35, wherein the information of the first functional cluster is used by the client device to display the server device corresponding to the node identifier according to the node identifier.
The device according to any one of claims 33 to 36, characterized in that the endpoint information of the first virtual endpoint records a network identifier of the network where the server device is located.
The device according to any one of claims 33-37, characterized in that:

The first command received by the relay device is associated with a first command path information block, and the encoding information of the first command path information block includes an endpoint identifier of the first virtual endpoint, where the first command is located. The identification of the functional cluster, and the identification of the first command; and/or

The first command sent by the relay device to the server device is associated with a second command path information block, and the encoding information of the second command path information block includes the endpoint identification of the first service endpoint, so The identifier of the functional cluster where the first command is located, and the identifier of the first command.
The apparatus according to claim 32, wherein the first virtual device includes a first virtual node having a mapping relationship with the server device.
The device of claim 39, further comprising:

A third receiving module, configured to receive a second message sent by the client device, where the second message is used to query target node information in the relay configuration cluster, where the target node information is recorded with the node identifier;

The third sending module is used to send the target node information to the client device.
The apparatus according to claim 40, wherein the target node information is used by the client device to display the server device corresponding to the node identifier according to the node identifier.
The device according to any one of claims 39-41, characterized in that:

The first command received by the relay device is associated with a third command path information block, and the encoding information of the third command path information block includes the node identifier, the endpoint identifier of the endpoint where the first command is located, The identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or

The first command sent by the relay device to the server device is associated with a fourth command path information block, and the encoding information of the fourth command path information block includes an endpoint identifier of the endpoint where the first command is located, The identifier of the functional cluster where the first command is located, and the identifier of the first command.
A command transmission device, characterized in that the device is configured on a client device, and the client device includes:

The first sending module is used to send a first command to the relay device. The first command is used to control the server device. The first command is forwarded to the server device through the relay device. ;

Wherein, the node identification of the server device is recorded in one or more of the following information:

Device information of a first virtual device, wherein the first virtual device is a virtual device in the relay device that has a mapping relationship with the server device;

Encoding information of the command path information block corresponding to the first command.
The apparatus according to claim 43, wherein the server device includes a first service endpoint, the first virtual device includes a first virtual endpoint having a mapping relationship with the first service endpoint, and the node The identification is recorded in the endpoint information of the first virtual endpoint.
The device according to claim 44, wherein the first virtual endpoint includes a first functional cluster, and the node identification is recorded in the first functional cluster;

Wherein, the first functional cluster is one of the following functional clusters:

a functional cluster describing the first virtual endpoint; and

A functional cluster dedicated to recording the nodes relayed by the first virtual endpoint.
The device of claim 45, further comprising:

a second sending module, configured to send a first message to the relay device, where the first message is used to query the first functional cluster;

A first receiving module, configured to receive a first response sent by the relay device, where the first response contains information about the first functional cluster.
The device according to any one of claims 44 to 46, characterized in that the endpoint information of the first virtual endpoint records a network identifier of the network where the server device is located.
The device according to any one of claims 44-47, characterized in that:

The first command sent by the client device to the relay device is associated with a first command path information block, and the encoding information of the first command path information block includes an endpoint identification of the first virtual endpoint, so The identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or

The first command sent by the relay device to the server device is associated with a second command path information block, and the encoding information of the second command path information block includes the endpoint identification of the first service endpoint, so The identifier of the functional cluster where the first command is located, and the identifier of the first command.
The device according to any one of claims 44-48, characterized in that the device further includes:

A first establishment module, configured to establish a pointing relationship between the first virtual endpoint and the server device directly connected to the client device according to the node identifier.
The apparatus according to claim 49, wherein the pointing relationship is used for the client device to display the server device corresponding to the node identifier according to the node identifier.
The apparatus according to claim 43, wherein the first virtual device includes a first virtual node having a mapping relationship with the server device.
The device of claim 51, further comprising:

A third sending module, configured to send a second message to the relay device, where the second message is used to query target node information in the relay configuration cluster, where the target node information is recorded with the node identifier;

The second receiving module is used to receive the target node information sent by the relay device.
The device according to claim 51 or 52, characterized in that:

The first command sent by the client device to the relay device is associated with a third command path information block, and the encoding information of the third command path information block includes the node identifier, where the first command is located. The endpoint identifier of the endpoint, the identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or

The first command sent by the relay device to the server device is associated with a fourth command path information block, and the encoding information of the fourth command path information block includes an endpoint identifier of the endpoint where the first command is located, The identifier of the functional cluster where the first command is located, and the identifier of the first command.
The device according to any one of claims 51-53, characterized in that the device further includes:

The second establishment module is configured to establish a pointing relationship between the first virtual node and the server device directly connected to the client device according to the node identifier.
The apparatus according to claim 54, wherein the pointing relationship is used for the client device to display the server device corresponding to the node identifier according to the node identifier.
A command transmission device, characterized in that the device is configured on a server device, and the server device includes:

A receiving module, configured to receive the first command sent by the relay device, where the first command is forwarded by the client device to the server device through the relay device;

Wherein, the node identification of the server device is recorded in one or more of the following information:

Device information of a first virtual device, wherein the first virtual device is a virtual device in the relay device that has a mapping relationship with the server device;

Encoding information of the command path information block corresponding to the first command.
The apparatus according to claim 56, wherein the server device includes a first service endpoint, the first virtual device includes a first virtual endpoint having a mapping relationship with the first service endpoint, and the node The identification is recorded in the endpoint information of the first virtual endpoint.
The device according to claim 57, wherein the first virtual endpoint includes a first functional cluster, and the node identification is recorded in the first functional cluster;

Wherein, the first functional cluster is one of the following functional clusters:

a functional cluster describing the first virtual endpoint; and

A functional cluster dedicated to recording the nodes relayed by the first virtual endpoint.
The apparatus according to claim 57 or 58, wherein the endpoint information of the first virtual endpoint records a network identifier of the network where the server device is located.
The device according to any one of claims 57-59, characterized in that:

The first command received by the relay device is associated with a first command path information block, and the encoding information of the first command path information block includes an endpoint identifier of the first virtual endpoint, where the first command is located. The identification of the functional cluster, and the identification of the first command; and/or

The first command received by the server device is associated with a second command path information block, and the encoding information of the second command path information block includes the endpoint identifier of the first service endpoint, where the first command is located. The identifier of the functional cluster, and the identifier of the first command.
The apparatus according to claim 56, wherein the first virtual device includes a first virtual node having a mapping relationship with the server device.
The device according to claim 61, characterized in that:

The first command received by the relay device is associated with a third command path information block, and the encoding information of the third command path information block includes the node identifier, the endpoint identifier of the endpoint where the first command is located, The identifier of the functional cluster where the first command is located, and the identifier of the first command; and/or

The first command received by the server device is associated with a fourth command path information block. The encoding information of the fourth command path information block includes an endpoint identifier of the endpoint where the first command is located. The first command The identifier of the functional cluster where it is located, and the identifier of the first command.
A command transmission device, characterized in that the device is configured in a relay device, the relay device includes a memory, a processor and a transceiver, the memory is used to store programs, and the processor is used to call the A program in the memory to cause the relay device to perform the method according to any one of claims 1-11.
A command transmission device, characterized in that the device is configured on a client device, the client device includes a memory, a processor and a transceiver, the memory is used to store programs, and the processor is used to call the A program in the memory to cause the client device to perform the method according to any one of claims 12-24.
A command transmission device, characterized in that the device is configured on a server device, the server device includes a memory, a processor and a transceiver, the memory is used to store programs, and the processor is used to call the The program in the memory enables the server device to execute the method according to any one of claims 25-31.
A device, characterized by comprising a processor for calling a program from a memory, so that the device executes the method according to any one of claims 1-31.
A chip, characterized in that it includes a processor for calling a program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1-31.
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-31.
A computer program product, characterized by comprising a program that causes a computer to execute the method according to any one of claims 1-31.
A computer program, characterized in that the computer program causes the computer to perform the method according to any one of claims 1-31.