[go: up one dir, main page]

WO2025060103A1 - Procédé et appareil de commande de dispositif, dispositif et support de stockage - Google Patents

Procédé et appareil de commande de dispositif, dispositif et support de stockage Download PDF

Info

Publication number
WO2025060103A1
WO2025060103A1 PCT/CN2023/120866 CN2023120866W WO2025060103A1 WO 2025060103 A1 WO2025060103 A1 WO 2025060103A1 CN 2023120866 W CN2023120866 W CN 2023120866W WO 2025060103 A1 WO2025060103 A1 WO 2025060103A1
Authority
WO
WIPO (PCT)
Prior art keywords
endpoint
server
command
functional unit
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/120866
Other languages
English (en)
Chinese (zh)
Inventor
茹昭
张军
吕小强
杨宁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority to PCT/CN2023/120866 priority Critical patent/WO2025060103A1/fr
Publication of WO2025060103A1 publication Critical patent/WO2025060103A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Definitions

  • the present application relates to the technical field of Internet of Things, and in particular to a device control method, apparatus, device and storage medium.
  • IoT Internet of Things
  • users can control server devices in IoT through client devices. For example, users can establish a connection with server devices through client devices, obtain various control functions and their status of server devices, and send control commands to server devices through client devices.
  • the embodiments of the present application provide a device control method, apparatus, device and storage medium.
  • the technical solution is as follows:
  • an embodiment of the present application provides a device control method, which is executed by a central device and includes:
  • a third command is sent to a server device corresponding to the server endpoint, where the third command is used to instruct the server endpoint to perform the first operation.
  • an embodiment of the present application provides a device control method, which is executed by a client device, and the method includes:
  • a second command is sent to the central device, wherein the second command is used to instruct the server endpoint; the second command is used to trigger the central device to send a third command to the server device of the server endpoint, wherein the third command is used to instruct the server endpoint to perform the first operation.
  • an embodiment of the present application provides a device control method, which is executed by a server device and includes:
  • the third command is sent by the hub device after receiving the first command and the second command, the first command is used to indicate the first operation, and the second command is used to indicate the server endpoint;
  • an embodiment of the present application provides a device control apparatus, the apparatus comprising:
  • a receiving module configured to receive a first command, where the first command is used to instruct a first operation
  • the receiving module is further used to receive a second command, where the second command is used to indicate a server endpoint;
  • the sending module is used to send a third command to the server device corresponding to the server endpoint, and the third command is used to instruct the server endpoint to perform the first operation.
  • an embodiment of the present application provides a device control apparatus, the apparatus comprising:
  • a sending module used for sending a first command to the central device, where the first command is used for indicating a first operation
  • the sending module is also used to send a second command to the central device, and the second command is used to instruct the execution of the server endpoint; the second command is used to trigger the central device to send a third command to the server device of the server endpoint, and the third command is used to instruct the server endpoint to execute the first operation.
  • an embodiment of the present application provides a device control apparatus, the apparatus comprising:
  • a receiving module used for receiving a third command sent by the central device; the third command is sent by the central device after receiving the first command and the second command, the first command is used to indicate a first operation, and the second command is used to indicate the execution of a server endpoint;
  • a control module is used to instruct the server endpoint to perform the first operation according to the third command.
  • an embodiment of the present application provides a hub device, the hub device comprising a processor, a memory, and a transceiver;
  • the memory stores a computer program, and the processor executes the computer program so that the central device implements the above-mentioned device control method.
  • an embodiment of the present application provides a client device, the client device comprising a processor, a memory, and a transceiver;
  • the memory stores a computer program
  • the processor executes the computer program so that the client device implements the above-mentioned device control method.
  • an embodiment of the present application provides a server device, the server device comprising a processor, a memory and a transceiver;
  • the memory stores a computer program
  • the processor executes the computer program to enable the network device to implement the above-mentioned Equipment control method.
  • the present application also provides a chip, which is used to run in a communication device so that the communication device executes the above-mentioned device control method.
  • the present application provides a computer program product, the computer program product comprising computer instructions, the computer instructions being stored in a computer-readable storage medium.
  • a processor of a communication device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the communication device executes the above-mentioned device control method.
  • the present application provides a computer program, which is executed by a processor of a communication device to implement the above-mentioned device control method.
  • An embodiment of the present application provides a device control scheme, which sets a central device in the Internet of Things.
  • a client device controls a server device, it can first send a first command to the central device to specify a first operation, and then send a second command to the central device to specify a server endpoint, thereby triggering the central device to send a third command to the server device corresponding to the server endpoint to instruct the server endpoint to perform the above-mentioned first operation;
  • the above-mentioned scheme allows the client device to first select the operation to be performed, and then select the server endpoint to perform the operation, thereby expanding the user's control method for the server device through the client device.
  • FIG1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • FIG2 is a diagram of a Matter device model involved in this application.
  • FIG3 is a model of a refrigerator device involved in the present application.
  • FIG4 is a flow chart of a device control method provided by an embodiment of the present application.
  • FIG5 is a flow chart of a device control method provided by an embodiment of the present application.
  • FIG6 is a flow chart of a device control method provided by an embodiment of the present application.
  • FIG7 is a flow chart of a device control method provided by an embodiment of the present application.
  • FIG8 is a possible structural diagram of a hub node involved in the present application.
  • FIG9 is a flow chart of a device control operation involved in the present application.
  • FIG10 is a flow chart of a device control operation involved in the present application.
  • FIG11 is a block diagram of a device control apparatus provided by an embodiment of the present application.
  • FIG12 is a block diagram of a device control apparatus provided by an embodiment of the present application.
  • FIG13 is a block diagram of a device control apparatus provided by an embodiment of the present application.
  • FIG. 14 is a schematic diagram of the structure of a communication device provided in one embodiment of the present application.
  • the network architecture of the Internet of Things may include: an Internet of Things device 110, a client device 120, and a hub device 130;
  • the IoT device 110 may be a device in the IoT that is used to provide a server function corresponding to the IoT protocol.
  • the source device may provide subscribable resources to the outside.
  • the IoT device 110 may be a smart home device, such as a smart lamp, a smart TV, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a sweeping robot, a smart speaker, a smart switch, and the like.
  • a smart home device such as a smart lamp, a smart TV, a smart air conditioner, a smart refrigerator, a smart microwave oven, a smart rice cooker, a sweeping robot, a smart speaker, a smart switch, and the like.
  • the IoT device 110 may be an industrial production equipment, such as a lathe, an industrial robot, a solar panel, a wind turbine, and the like.
  • the IoT device 110 may be a commercial service device, such as an unmanned vending machine, etc.
  • the IoT device 110 is an intelligent monitoring device, such as a monitoring camera, an infrared sensor, a sound sensor, or a temperature sensor.
  • the IoT device 110 may also be a user-side terminal device.
  • the IoT device 110 may be a smart controller, a smart remote controller, a smart phone, a tablet computer, a smart watch, a smart TV, a gateway, etc.; or, the IoT device 110 may also be a personal computer, such as a desktop computer, a portable computer, a personal workstation, etc.
  • the client device 120 may be a terminal device on the user side.
  • the client device 120 may be an intelligent controller, an intelligent remote controller, a smart phone, a tablet computer, a smart watch, a smart TV, etc.
  • the client device 120 may also be a client entity (which may be a virtual entity) running based on the terminal device.
  • the client device 120 may be an APP running in a smart phone for controlling or managing the IoT device 110.
  • the hub device 130 may be a software entity (may be a virtual entity) deployed in the client device 120 or other IoT devices.
  • the hub device 130 may be an APP running in a smart phone.
  • the hub device 130 may be an intermediate management device deployed in the Internet of Things. Gateway and other devices.
  • the central device 130 may also be a server deployed on the network side.
  • the server may be a single server, or the server may be a server cluster composed of multiple servers.
  • the central device 130 may be a computer device that provides cloud support for the management and control of IoT devices.
  • the above-mentioned Internet of Things device 110 can be an electronic device that meets the same or different Internet of Things protocols.
  • it can be an electronic device that meets the Matter protocol (or the Connected Home over IP Working Group (CHIP) project) under the Connectivity Standards Alliance (CSA) (or Zigbee Alliance).
  • Matter protocol or the Connected Home over IP Working Group (CHIP) project
  • CHIP Connected Home over IP Working Group
  • CSA Connectivity Standards Alliance
  • Zigbee Alliance Zigbee Alliance
  • Matter is an IP-based IoT connection standard that solves the compatibility, security, and connectivity issues in the current smart home market.
  • Figure 2 shows a diagram of the Matter device model involved in this application.
  • the model hierarchy from high to low is node (Node), endpoint (Endpoint), functional unit (Cluster) and attribute (Attribute)/command (Command)/event (Event).
  • 3Cluster is a functional unit, which can also be called a cluster or cluster. It is the most basic functional building element in the object model.
  • Cluster defines the rules for interaction between the server and the client.
  • Cluster can be regarded as an interface, service or object class, and is the lowest-level independent functional element in the data model.
  • Each Cluster has an independent specification definition, which includes attributes, events, commands, and behaviors. The mandatory or optional nature of the attributes, events, commands, and behaviors of the Cluster depends on the definition of the Cluster itself.
  • the Cluster specification should contain one or more Cluster identifiers.
  • a Cluster identifier should refer to a Cluster specification and guarantee compliance with the specification.
  • a Cluster instance should be represented and discoverable by the Cluster identifier on the endpoint.
  • the Cluster identifier also represents the function and purpose of the Cluster instance.
  • the server-side Cluster supports attributes, events, and command data, and the client-side Cluster is responsible for initiating interactions, including calling Cluster commands.
  • 5Command is the control of the specific functions of the functional unit and is transmitted between the Client and Server of the Cluster.
  • 6Event is an event, which means a record of what happened in the past.
  • An event can be regarded as a log entry, and an event stream can be regarded as a time view of the state evolution on a node. Events are readable because their event identifiers can be discovered by Cluster instances.
  • An event record is created by a node when an event occurs.
  • the record should have three metadata: event number, timestamp, and priority level. These metadata should be stored in the header of the event record.
  • Event Label A node-wide 64-bit label. This label should increase monotonically during the lifetime of the node and remain monotonic across device reboots. This monotonicity is reset after a factory reset. Each event record should have an event label that is exactly the label of the last event record created on the node plus one. When a node is restarted, the event label may increase by steps greater than 1.
  • a device type defines a set of requirements for a node or endpoint on the market.
  • a device type definition should specify the device type ID, the device version, and a set of one or more mandatory clusters, including specifying a minimum version for each cluster.
  • Each device type definition should specify the endpoint as either a utility or an application.
  • Utility Device Types support configuration and setup. Utility Device Types define the requirements of a Utility Device Cluster. Utility Device Types can also represent physical devices or products. There may be multiple endpoints on a node that support a Utility Device Type. Utility Cluster Example Categories: OTA Upgrade, Diagnostics, Basic Information. Utility Device Type Examples: Bridge, Proxy, Power Supply.
  • Application device type is usually the most common endpoint in nodes and networks.
  • the endpoint that supports application device type is application endpoint.
  • Application device type should be applicable to the endpoint.
  • Application endpoint should support the main application function of cluster endpoint.
  • Application category examples HVAC, lighting, home security, etc.
  • An interaction is a sequence of one or more transactions between nodes, and a transaction consists of one or more action sequences. Please refer to Table 1, which shows the definitions of various interaction operations.
  • FIG. 3 shows a model of a refrigerator device involved in the present application.
  • endpoint 1 represents the functional endpoint of the refrigerator device, including two refrigerator sub-endpoints: refrigerator EP2 and freezer EP3.
  • Each refrigerator endpoint includes a description, switch, and temperature control function unit.
  • the temperature control function unit includes the following attributes as shown in Table 2:
  • the temperature control function unit includes the following commands as shown in Table 3:
  • the cluster describes an endpoint instance on the node, independent of other endpoints, but also allows a combination of endpoints to conform to the model of complex device types.
  • the cluster contains the following properties as shown in Table 5:
  • DeviceTypeList is a list of one or more device type identifiers that conform to the specifications of the device type.
  • ServerList a list of one or more server functional units.
  • ClientList a list of one or more client functional units.
  • the PartsList attribute is a list of endpoints (empty or multiple) to support a composite device type.
  • TagList is a tag list, which should be used to disambiguate sibling endpoints that overlap in the supported device types when the sibling endpoints appear in the PartsList of their direct parent.
  • the relevant technical solution is applicable to operational scenarios with deterministic goals such as controlling a certain device or obtaining the status of a certain device.
  • the solution shown in the subsequent embodiments of the present application can dynamically call a certain target device according to user needs when there are multiple devices in the Internet that can provide the same service interface, that is, it is used for scenarios where the user first determines the operation and then selects the target device.
  • FIG. 4 shows a flow chart of a device control method provided by an embodiment of the present application.
  • the method may be executed by a hub device, which may be the hub device 130 in the network architecture shown in FIG. 1 ; the method may include the following steps:
  • Step 401 Receive a first command, where the first command is used to instruct a first operation.
  • the hub device may receive a first command sent by a client device, where the first command is used to indicate a first operation corresponding to a first functional unit in the hub device; the first functional unit corresponds to at least one server endpoint.
  • a functional unit may correspond to one server endpoint or multiple server endpoints.
  • Step 402 Receive a second command, where the second command is used to indicate a server endpoint.
  • the hub device may receive a second command sent by the client device, where the second command is used to instruct a server endpoint to perform the first operation.
  • the server endpoint indicated by the second command is part or all of the at least one server endpoint; that is, the server endpoint that performs the first operation is one or more of the at least one server endpoint corresponding to the first functional unit.
  • Step 403 Send a third command to the server device of the server endpoint, where the third command is used to instruct the server endpoint to perform the first operation.
  • a central device is set in the Internet of Things.
  • a client device controls a server device, it can first send a first command to the central device to specify a first operation, and then send a second command to the central device to specify a server endpoint, thereby triggering the central device to send a third command to the server device corresponding to the server endpoint to instruct the server endpoint to perform the above-mentioned first operation; the above-mentioned scheme allows the client device to first select the operation to be performed, and then select the server endpoint to perform the operation, thereby expanding the user's control method over the server device through the client device.
  • FIG. 5 shows a flow chart of a device control method provided by an embodiment of the present application.
  • the method may be executed by a client device, which may be the client device 120 in the network architecture shown in FIG. 1 ; the method may include the following steps:
  • Step 502 sending a second command to the central device, the second command is used to instruct the server endpoint; the second command is used to trigger the central device to send a third command to the server device corresponding to the server endpoint, the third command is used to instruct the server endpoint to perform the first operation.
  • FIG. 6 shows a flow chart of a device control method provided by an embodiment of the present application.
  • the method may be executed by a server device, which may be the Internet of Things device 110 in the network architecture shown in FIG. 1 ; the method may include the following steps:
  • Step 601 receiving a third command; the third command is sent by the central device after receiving the first command and the second command, the first command is used to indicate the first operation, and the second command is used to indicate the server endpoint.
  • Step 602 According to the third command, instruct the server endpoint to perform a first operation.
  • a central device is set in the Internet of Things.
  • a client device controls a server device, it can first send a first command to the central device to specify a first operation, and then send a second command to the central device to specify a server endpoint, thereby triggering the central device to send a third command to the server device corresponding to the server endpoint to instruct the server endpoint to perform the above-mentioned first operation; the above-mentioned scheme allows the client device to first select the operation to be performed, and then select the server endpoint to perform the operation, thereby expanding the user's control method over the server device through the client device.
  • FIG. 7 shows a flow chart of a device control method provided by an embodiment of the present application.
  • the method can be interactively executed by a client device, a hub device, and a server device, wherein the client device can be the client device 120 in the network architecture shown in FIG. 1 , the hub device can be the hub device 130 in the network architecture shown in FIG. 1 , and the server device can be the Internet of Things device 110 in the network architecture shown in FIG. 1 ; the method can include the following steps:
  • Step 701 The server device sends device information to the central device; correspondingly, the central device receives device information sent by at least one server device.
  • the device information includes: a device type of each server endpoint in the server device.
  • Step 702 The central device creates central sub-endpoints corresponding to each server endpoint in at least one server device according to the device information.
  • the central sub-endpoints include each functional unit of the corresponding server endpoint for device control.
  • the above device information is used by the hub device to create hub sub-endpoints corresponding to each server endpoint, and the hub sub-endpoint contains each functional unit of the corresponding server endpoint for device control.
  • the hub device contains hub sub-endpoints corresponding to each server endpoint in at least one server device, and the hub sub-endpoint contains each functional unit of the corresponding server endpoint for device control.
  • the central device can create corresponding functional units in the central device according to the device information of the server device, so that the server endpoints in the server device can be subsequently controlled through the functional units in the central device.
  • the central device can have its own node (which can be called a central node), which includes a root endpoint and sub-endpoints of each level under the root endpoint (i.e., the above-mentioned central sub-endpoints).
  • the central device can create central sub-endpoints corresponding to each server endpoint in the server device based on the device information of the server device.
  • the above-mentioned central sub-endpoints corresponding to each server endpoint in the server device include functional units corresponding to the functions of each server endpoint.
  • the functional units contained in the above-mentioned central sub-endpoints and corresponding to the functions of each server-side endpoint can be the functional units corresponding to the control functions in the functional units of each server-side endpoint.
  • the functional units corresponding to each server endpoint contained in the central sub-endpoint may include all or part of the contents of the functional units corresponding to each server endpoint in the server device; for example, the functional units corresponding to each server endpoint contained in the central sub-endpoint may include the commands and attributes of the functional units corresponding to each server endpoint in the server device, but do not include the events of the functional units corresponding to each server endpoint in the server device, thereby reducing the amount of data of the functional units in the central sub-endpoint, avoiding unnecessary data storage, and improving the utilization rate of the storage space of the central device; or, the functional units corresponding to each server endpoint contained in the central sub-endpoint may include the commands, attributes and events of the functional units corresponding to each server endpoint in the server device.
  • the central device can create a functional unit corresponding to the server endpoint in the server device in the central device based on the device information sent by the server device, so as to flexibly provide control services for various server endpoints and improve the access flexibility of the server device.
  • the multiple server devices when multiple server devices in at least one server device have the same device type, the multiple server devices correspond to the same hub sub-endpoint in the hub device.
  • the hub device when creating hub sub-endpoints corresponding to each server endpoint based on device information, can create a hub sub-endpoint corresponding to multiple server devices when multiple server devices in at least one server device have the same device type.
  • multiple server endpoints in each server endpoint have the same device type, and the multiple server endpoints have In the case of the same second functional unit, multiple server endpoints correspond to the same second functional unit in the central sub-endpoint, and there is no need to establish a central sub-endpoint for each server device in the central device. On the one hand, it can support the unified selection of the functional unit to be controlled, and on the other hand, it can simplify the complexity of the central sub-endpoints in the central device.
  • a second functional unit corresponding to the multiple server endpoints is created under the central sub-endpoint.
  • each server endpoint included in at least one server device there may be multiple server endpoints with the same function.
  • the central device creates a functional unit under a central sub-endpoint, it can establish a unified functional unit under the central sub-endpoint for multiple functional units with the same function and the same corresponding device type. There is no need to establish a functional unit for each function of each server endpoint in the central device. On the one hand, it can support the unified selection of the functional units to be controlled, and on the other hand, it can simplify the complexity of the functional units in the central device.
  • the hub sub-endpoints in the above-mentioned hub device can be set according to the level and function of the server endpoints in the server device; that is, each underlying hub sub-endpoint corresponds to a functional unit in a server device.
  • the refrigerator includes two server endpoints (corresponding to the freezer and the refrigerator respectively), and each server endpoint has a temperature control function.
  • the central device can be set with two levels of central sub-endpoints, wherein the upper-level central sub-endpoint corresponds to the refrigerator, which includes the lower-level central sub-endpoint, and the lower-level central sub-endpoint has a functional unit corresponding to the temperature control function, and the functional unit corresponds to the two server endpoints; further, assuming that each server endpoint in the refrigerator also has a lighting function, in this case, the central device can still be set with two levels of central sub-endpoints, wherein the upper-level central sub-endpoint corresponds to the refrigerator, which includes two lower-level central sub-endpoints, one of which has a functional unit corresponding to the temperature control function, and the functional unit corresponds to the two server endpoints; and, the other lower-level central sub-endpoint has a functional unit corresponding to the lighting function, and
  • the dishwasher has a temperature-controlled server endpoint
  • the central device can set a single-level central sub-endpoint, wherein the central sub-endpoint corresponds to the dishwasher, which contains a function unit corresponding to the temperature control function, and the function unit corresponds to the temperature-controlled server endpoint in the dishwasher.
  • refrigerator 1 includes two server endpoints (corresponding to the freezer and the refrigerator, respectively), each of which has a temperature control function and a lighting function
  • refrigerator 2 includes two server endpoints (corresponding to the freezer and the refrigerator, respectively), each of which has a temperature control function.
  • the central device can be set with two levels of central sub-endpoints, wherein the upper-level central sub-endpoint corresponds to refrigerator 1 and refrigerator 2, which includes a lower-level central sub-endpoint, and the lower-level central sub-endpoint has a functional unit 1 corresponding to the temperature control function, and a functional unit 2 corresponding to the lighting function.
  • the functional unit 1 corresponds to 4 server endpoints, namely the freezer and the refrigerator of refrigerator 1, and the freezer and the refrigerator of refrigerator 2.
  • the functional unit 2 corresponds to 2 server endpoints, namely the freezer and the refrigerator of refrigerator 1.
  • the central sub-endpoint also includes a descriptor functional unit, which includes an instance endpoint list attribute, and the instance endpoint list attribute includes endpoint information of each server endpoint corresponding to the functional unit in the central sub-endpoint.
  • the central sub-endpoint also includes an instance endpoint table of the corresponding server endpoint, which includes the functional units of the server endpoint corresponding to the central sub-endpoint, as well as the endpoint information of each server endpoint corresponding to the functional units in the central sub-endpoint.
  • Step 703 The hub device sends the information of the hub sub-endpoint to the client device, and correspondingly, the client device receives the information of the hub sub-endpoint sent by the hub device.
  • the information of the above-mentioned hub sub-endpoints may include each functional unit in the hub sub-endpoints.
  • the information of the above-mentioned hub sub-endpoints may be used to indicate which hub sub-endpoints are included in the hub device and which functional units are included in each hub sub-endpoint.
  • the information of the central sub-endpoint may also include endpoint information of each server-side endpoint corresponding to the functional unit in the central sub-endpoint.
  • the client device can display a device control interface based on the information of the above-mentioned hub sub-endpoint, so that the user can first select the function and control operation to be controlled, and then select the device to be controlled.
  • Step 704 the client device sends a first command to the central device, and the central device receives the first command sent by the client device; the first command is used to indicate a first operation corresponding to a first functional unit in the central device; the first functional unit corresponds to at least one server endpoint.
  • the client device can display the control operation selection interface based on the information of the above-mentioned central sub-endpoint to facilitate the user to select the first operation.
  • the client device can display a control operation selection interface containing control operations corresponding to each functional unit in the central sub-endpoint according to each functional unit in the central sub-endpoint.
  • the user can select the first operation from the control operation selection interface (for example, select the control operation of adjusting the temperature of the refrigerator, or select the control operation of turning on and off the lights. At this time, the user can temporarily not select the server endpoint to perform the first operation).
  • the client device sends the first command to the central device according to the user's selection operation.
  • Step 705 The client device sends a second command to the central device, and the central device receives the second command sent by the client device, where the second command is used to instruct the server endpoint to perform the first operation.
  • the server endpoint of the above-mentioned first operation may be one or more server endpoints determined by the client device from at least one server endpoint corresponding to the first functional unit; for example, the server endpoint indicated by the above-mentioned second command (also referred to as the server endpoint corresponding to the first operation) may be one or more server endpoints selected by the user in the client device, among the at least one server endpoint corresponding to the first functional unit; or, the server endpoint of the above-mentioned first operation may be one or more server endpoints selected by the client device from at least one server endpoint corresponding to the first functional unit according to a preset selection rule.
  • the client device may obtain endpoint information of at least one server endpoint corresponding to the first functional unit from the central device, so that the client device can determine the server endpoint indicated by the second command from the at least one server endpoint corresponding to the first functional unit.
  • the hub sub-endpoint also includes a descriptor function unit, and in the case where the descriptor function unit includes an instance endpoint list attribute, the hub device can send the instance endpoint list attribute in the descriptor function unit to the client device.
  • the client device receives the instance endpoint list attribute in the descriptor function unit sent by the hub device, and sends the second command to the hub device based on the instance endpoint list attribute in the descriptor function unit.
  • the client device can determine the server endpoint indicated by the second command from at least one server endpoint corresponding to the above-mentioned first function unit contained in the instance endpoint list attribute.
  • the above-mentioned central device can send the instance endpoint list attribute in the descriptor functional unit before step 704.
  • the instance endpoint list attribute in the descriptor functional unit is sent to the client device.
  • the hub device may also send the instance endpoint list attribute in the descriptor function unit after receiving the first command and before receiving the second command.
  • the central device can send the endpoint information of at least one server endpoint corresponding to the first functional unit to the client device.
  • the client device receives the endpoint information of at least one server endpoint corresponding to the first functional unit sent by the central device, and sends the second command to the central device based on the endpoint information of at least one server endpoint corresponding to the first functional unit; for example, the client device can determine the server endpoint indicated by the second command from the at least one server endpoint of the above-mentioned first functional unit.
  • the above-mentioned central device can send endpoint information of at least one server endpoint corresponding to the first functional unit before step 704.
  • the endpoint information of at least one server endpoint corresponding to the first functional unit is sent to the client device.
  • the above-mentioned central device may also send endpoint information of at least one server endpoint corresponding to the first functional unit after receiving the first command and before receiving the second command.
  • the functional unit in the hub sub-endpoint includes a current instance attribute, and the current instance attribute is used to indicate the server endpoint currently receiving control among each server endpoint corresponding to the functional unit in the hub sub-endpoint; the method further includes:
  • the central device When the current instance attribute in the first functional unit is empty, the central device writes the endpoint information of the server endpoint indicated by the second command into the current instance attribute in the first functional unit.
  • the client device can control one or more of the server endpoints to perform the first operation.
  • the central device when it receives the second command, it can write the endpoint information of the server endpoint indicated by the second command into the current instance attribute in the first functional unit if the current instance attribute in the first functional unit is empty, so as to indicate the server endpoint corresponding to the first operation.
  • the central device when the central device receives the second command, if the current instance attribute in the first functional unit is not empty, the second command can be discarded and an error message can be returned to the client device, or the endpoint information of the server endpoint indicated by the second command can be used to replace the endpoint information in the current instance attribute in the first functional unit.
  • the command attribute of the functional unit in the hub sub-endpoint includes a current instance parameter
  • the current instance parameter is used to indicate the server endpoint currently receiving control among each server endpoint corresponding to the functional unit in the hub sub-endpoint
  • the method further includes:
  • the endpoint information of the server endpoint indicated by the second command is written into the current instance parameter in the command attribute in the first functional unit.
  • the central device when the central device receives the second command, it can also write the endpoint information of the server endpoint indicated by the second command into the current instance parameter in the command attribute in the first functional unit to indicate the server endpoint corresponding to the first operation.
  • the endpoint information includes at least one of the following information:
  • the above endpoint information also includes: tag information of the corresponding server endpoint, which is used to describe the server endpoint.
  • tag information can describe the manufacturer, device model, and device location (such as living room, kitchen) of the corresponding server endpoint.
  • Step 706 The central device sends a third command to the server device corresponding to the server endpoint indicated by the second command, and the server device receives the third command; the third command is used to instruct the server endpoint to perform the first operation.
  • the central device may send a third command to the server device of the server endpoint indicated by the second command according to the endpoint information in the current instance attributes after writing the endpoint information of the server endpoint indicated by the second command into the current instance attributes in the first functional unit.
  • the central device may also include current instance parameters in the command attributes of the functional unit in the central sub-endpoint, and write the endpoint information of the server endpoint indicated by the second command into the current instance parameters in the command attributes in the first functional unit, and then send a third command to the server device of the server endpoint indicated by the second command according to the endpoint information in the current instance parameters.
  • Step 707 The server device instructs the server endpoint to perform the first operation according to the third command.
  • the central device after the central device writes the endpoint information of the server endpoint indicated by the second command into the current instance attributes in the first functional unit, it can also clear the current instance attributes in the first functional unit after the server endpoint indicated by the second command completes the first operation.
  • the above-mentioned clearing of the current instance attributes in the first functional unit after the server endpoint indicated by the second command completes the execution of the first operation may refer to clearing the current instance attributes in the first functional unit after sending the third command, or may refer to clearing the current instance attributes in the first functional unit after the server device that receives the server endpoint indicated by the second command returns a response of successful execution of the first operation.
  • the central device writes the endpoint information of the server endpoint indicated by the second command into the current instance attribute in the first functional unit, then after the server endpoint completes the first operation, the current instance attribute in the first functional unit is cleared so that the new endpoint information can be reset in the next control process to ensure the accurate execution of subsequent operations.
  • the central device when the central device writes the endpoint information of the server endpoint indicated by the second command into the current instance attribute in the first functional unit, it can also receive a fourth command sent by the client device, and the fourth command is used to indicate the second operation corresponding to the first functional unit; when the value of the current instance attribute in the first functional unit is the endpoint information of the server endpoint indicated by the second command, a fifth command is sent to the server device of the server endpoint indicated by the second command, and the fifth command is used to instruct the server endpoint indicated by the second command to perform the second operation.
  • the endpoint information in the current instance attributes can be stored for a period of time. During this period of time, multiple control operations can be supported. Multiple control operations point to the same server endpoint. There is no need to clear the current instance attributes after each operation, which improves the communication efficiency during multiple consecutive operations on the same function of the same server endpoint.
  • the method further comprises:
  • the central device clears the current instance attributes in the first functional unit.
  • the parameter clearing condition includes at least one of the following conditions:
  • the central device receives a clear command, and the clear command is used to trigger the clearing of the current instance attribute in the first functional unit; accordingly, the client device can send the above clear command to the central device, for example, when it is detected that the user exits the operation corresponding to the first functional unit on the current server endpoint, the above situation command is sent;
  • the central device does not receive a command indicating an operation corresponding to the first functional unit within a specified time period.
  • the current instance attributes in the first functional unit can be cleared so that the user can reset new endpoint information in the subsequent control process to ensure the accurate execution of subsequent operations.
  • EP00 represents the node root, and the other endpoints are its sub-endpoints.
  • Sub-endpoint EP11 represents a hub device type endpoint, which includes sub-endpoints EP12, EP13, and EP14.
  • EP12 represents a refrigerator type endpoint, which includes sub-endpoint EP13 (representing a temperature control cabinet).
  • EP14 represents a dishwasher type endpoint.
  • the attribute InstanceList is the target server endpoint (one or more of Endpoint1, Endpoint2, Endpoint3) corresponding to the hub child endpoint (such as EP12, EP13, or EP14), presented in the form of a list of endpoint structures.
  • min 1 means that the list contains at least one item.
  • HC means that this attribute is required in the functional unit of the hub endpoint.
  • the attribute CurrentInstance indicates the target server endpoint corresponding to the current hub endpoint, which should be included in the above InstanceList.
  • CurrentInstance defaults to null.
  • CurrentInstance is null, the other attributes of the functional unit are all default values.
  • NodeID is the ID of the target node where the functional unit is located.
  • Endpoint is the endpoint number of the target endpoint where the functional unit is located.
  • EndpointLabel is the semantic label of the endpoint, which is defined in the TagList attribute of the Descriptor Cluster of the server device, such as Refrigerator Freezer.
  • the dishwasher has an endpoint Endpoint1.
  • the refrigerator device node includes Endpoint2
  • the user uses a mobile phone as a client, and can connect to the server device through the central node and initiate an operation.
  • a device control operation flow chart involved in this application can be shown in Figure 9:
  • the central node obtains the device type and command set of the server device. This step can be achieved by the central node reading the Descriptor Cluster on each level of the device endpoint. For example, read the Refrigerator and Temperature Controlled Cabinet device types from the refrigerator device; read the Dishwasher device type from the dishwasher device.
  • the central node generates central sub-endpoints according to the acquired server device information. For example, it generates two sub-endpoints EP12 and EP13 of Refrigerator type and Temperature Controlled Cabinet type according to the information read from the refrigerator; and generates a sub-endpoint EP14 of Dishwasher type according to the information read from the dishwasher.
  • the central node creates a central functional unit in the generated central sub-endpoint, that is, adds the CurrentInstance attribute to the functional unit contained in the original endpoint.
  • the hub node creates a descriptor function unit in the generated hub sub-endpoint.
  • the descriptor function unit also contains the target server endpoint attribute InstanceList.
  • the InstanceList of EP13 contains Endpoint2 and Endpoint3 of the refrigerator device node; the InstanceList of EP14 contains Endpoint1 of the dishwasher device node.
  • the mobile client obtains the functional unit of the hub node.
  • the client reads the Descriptor Cluster of each endpoint of the hub node step by step, and obtains the functional units on the hub nodes EP12, EP13, and EP14.
  • the user calls the central command on the mobile phone to control the dishwasher and adjust the temperature of the dishwasher to 50 degrees.
  • the mobile phone sends SetTemperature to the central endpoint EP14 with a parameter of 50.
  • the hub confirms that the CurrentInstance attribute of the temperature control function unit of the EP14 endpoint is empty and suspends the command.
  • the mobile phone provides a control display interface according to the number of instances of the obtained central endpoint. If EP14 only includes one instance, the dishwasher control interface of the mobile phone can directly display the dishwasher device information (such as the dishwasher device ID or location, etc.).
  • the mobile phone sends a write attribute to the temperature control function unit of the hub EP14 endpoint, setting the CurrentInstance attribute value to Endpoint1.
  • the central node corresponds to the dishwasher device node Endpoint1 according to the CurrentInstance attribute value, sends the calling command to the dishwasher, and adjusts the temperature of the dishwasher to 50 degrees.
  • the central node returns the execution result to the mobile client through a response.
  • the mobile phone when the endpoint corresponds to multiple instances (such as EP13), the mobile phone does not display the corresponding server device information on the control interface.
  • the user operates the hub on the mobile phone to control the refrigerator and adjust the temperature of the temperature control cabinet to 0 degrees.
  • the mobile phone sends the hub command SetTemperature to the hub EP13 endpoint with a parameter of 0.
  • the hub After receiving the command, the hub confirms that the CurrentInstance attribute of the temperature control function unit of the EP13 endpoint is empty and suspends the command.
  • S15 if there are multiple target endpoints, all target endpoints are displayed; specifically, the mobile phone displays that the mobile phone confirms that the endpoint has multiple (2) instances, corresponding to the refrigerator device nodes Endpoint2 and Endpoint3.
  • the semantic labels of the endpoints are displayed on the interface for the user to select, such as displaying "refrigerator refrigerator” and "refrigerator freezer”.
  • the user selects a target endpoint, for example, the user further selects “refrigerator and freezer”.
  • the mobile phone sets the EndpointStruct corresponding to the "refrigerator and freezer" as the CurrentInstance attribute value of the EP13 temperature control function unit.
  • the central node sends a call command according to the CurrentInstance attribute value, for example, according to the CurrentInstance attribute value of the EP13 temperature control function unit, determines the SetTemperature command to send to Endpoint2.
  • the central node sends the SetTemperature command to Endpoint2 corresponding to the refrigerator and freezer.
  • Endpoint2 executes the command to adjust the temperature to 0 degrees and returns a response.
  • the central node returns the execution result to the mobile client through a response.
  • Embodiment 2 The hub node acts as a server management node, maps the server functional unit interface through the hub endpoint, and provides centralized calling capabilities to the client.
  • the hub endpoint merges the functional units of other controllable server nodes into the same type, and reflects the target endpoint where the functional unit is located. For example, a possible structure of the hub node can be shown in Figure 8.
  • Server is a server functional unit on the central endpoint, such as the temperature control functional unit on the dishwasher endpoint.
  • InstanceList is the original target server endpoint where the server functional unit is located, presented in the form of a list of endpoint structures. min 1 means that the list contains at least one item.
  • the central endpoint EP14 concentrates two dishwasher endpoints Endpoint1 and Endpoint4. Among them, Endpoint1 implements On/Off cluster, Temperature Control cluster and Operational State cluster; Endpoint4 implements Dishwasher Mode cluster and Operational State cluster. Then all the above clusters are included in the central endpoint EP14.
  • the InstanceList corresponding to On/Off cluster and Temperature Control cluster only contains Endpoint1; the InstanceList corresponding to Dishwasher Mode cluster only contains Endpoint4; the InstanceList corresponding to Operational State cluster contains Endpoint1 and Endpoint4.
  • a parameter is added to the command included in the functional unit included in each of the above endpoints.
  • the parameter of the SetTemperature command included in the temperature control functional unit of the temperature control cabinet is changed to the parameter shown in Table 10:
  • the parameter CurrentInstance indicates the target server endpoint corresponding to the current central endpoint command.
  • the target server endpoint should be included in the InstanceList corresponding to the functional unit where the command is located in the InstanceTable.
  • CurrentInstance defaults to empty.
  • CurrentInstance is empty, if the functional unit where the command is located corresponds to only one Instance in the InstanceTable, the command can also be executed; if the functional unit where the command is located corresponds to more than one Instance in the InstanceTable, the command cannot be executed.
  • NodeID is the ID of the target node where the functional unit is located.
  • Endpoint is the endpoint number of the target endpoint where the functional unit is located.
  • EndpointLabel is the semantic label of the endpoint, which is defined in the TagList attribute of the Descriptor Cluster of the server device, such as Refrigerator Freezer.
  • the dishwasher has an endpoint, Endpoint1.
  • the refrigerator device node includes two temperature control cabinets, Endpoint2 and Endpoint3.
  • the user uses a mobile phone as a client and can connect to the server device through the central node and initiate an operation.
  • a device control operation flow chart involved in this application can be shown in Figure 10:
  • the central node obtains the device type and command set of the server device. This step can be achieved by the central node reading the Descriptor Cluster on each level of the device endpoint. For example, read the Refrigerator and Temperature Controlled Cabinet device types from the refrigerator device; read the Dishwasher device type from the dishwasher device.
  • the central node generates central sub-endpoints according to the acquired server device information. For example, it generates two sub-endpoints EP12 and EP13 of Refrigerator type and Temperature Controlled Cabinet type according to the information read from the refrigerator; and generates a sub-endpoint EP14 of Dishwasher type according to the information read from the dishwasher.
  • the central node creates a central functional unit in the generated central sub-endpoint, and adds a CurrentInstance parameter to each command of the functional unit contained in the original endpoint.
  • the hub node creates an instance endpoint table in the generated hub sub-endpoint.
  • the instance endpoint table takes each server functional unit of the hub sub-endpoint as a table item, and also includes the target server endpoint list InstanceList where the functional unit is located.
  • the InstanceList corresponding to the temperature control functional unit of EP13 includes Endpoint2 and Endpoint3 of the refrigerator device node; the InstanceList corresponding to the temperature control functional unit of EP14 includes Endpoint1 of the dishwasher device node.
  • the mobile client obtains the functional unit of the hub node.
  • the client reads the Descriptor Cluster of each endpoint of the hub node step by step, and obtains the functional units on the hub nodes EP12, EP13, and EP14.
  • the user uses the mobile phone to call the command of the hub to control the dishwasher and adjust the temperature of the dishwasher to 50 degrees.
  • the mobile phone sends SetTemperature to the hub EP14 endpoint with a parameter of 50.
  • the central node After receiving the command, the central node confirms according to the instance endpoint table that there is only one Instance for the endpoint, which corresponds to the dishwasher device node Endpoint1.
  • the central node sends the call command to the dishwasher node Endpoint1, adjusts the dishwasher temperature to 50 degrees, and receives the response returned by the dishwasher.
  • the central node returns the execution result to the mobile client through a response.
  • the user operates the central control refrigerator on the mobile phone and adjusts the temperature of the temperature control cabinet to 0 degrees.
  • the mobile phone sends the command SetTemperature to the central endpoint EP13, with the parameter 0.
  • the central node After receiving the command, the central node confirms according to the instance endpoint table that the endpoint has multiple (2) instances, corresponding to the refrigerator device nodes Endpoint2 and Endpoint3.
  • the central node returns all target endpoints corresponding to the command, and returns the EndpointStruct corresponding to the refrigerator device nodes Endpoint2 and Endpoint3 to the mobile client.
  • step Descriptor Cluster may not include InstanceList.
  • step S5 the mobile client cannot obtain the EndpointStruct corresponding to Endpoint2 and Endpoint3.
  • the central node may return the EndpointStruct corresponding to Endpoint2 and Endpoint3 to the mobile client.
  • the mobile phone after receiving multiple available endpoints, displays the semantic labels of the endpoints on the interface for the user to select, such as displaying "refrigerator and freezer” and “refrigerator and freezer”. The user further selects "refrigerator and freezer", and the mobile phone sets the EndpointStruct corresponding to "refrigerator and freezer” as the CurrentInstance parameter value of the SetTemperature command.
  • the SetTemperature command is resent, which includes the target endpoint selected by the user.
  • the central node parses the incoming target endpoint and determines that the SetTemperature command is sent to Endpoint2 based on the CurrentInstance parameter value of the SetTemperature command.
  • the central node sends a SetTemperature command to Endpoint2 corresponding to the refrigerator.
  • Endpoint2 executes the command to adjust the temperature to 0 degrees and returns a response.
  • the central node returns the execution result to the mobile client through a response.
  • FIG. 11 shows a block diagram of a device control device provided by an embodiment of the present application.
  • the device control device has the function of implementing the method shown in FIG. 4 or FIG. 7 above, which is performed by the central device.
  • the device may include:
  • the receiving module 1101 is used to receive a first command, where the first command is used to instruct a first operation;
  • the receiving module 1101 is further used to receive a second command, where the second command is used to indicate a server endpoint;
  • the sending module 1102 is used to send a third command to the server device of the server endpoint, where the third command is used to instruct the server endpoint to perform the first operation.
  • the first command is used to indicate the first operation corresponding to a first functional unit in the hub device; the first functional unit corresponds to at least one server endpoint;
  • the server endpoint indicated by the second command is part or all of the at least one server endpoint.
  • the receiving module is further used to receive device information sent by the at least one server device; the apparatus further includes:
  • a creation module is used to create a central sub-endpoint corresponding to each server endpoint in the at least one server device according to the device information, and the central sub-endpoint includes a functional unit of the corresponding server endpoint.
  • the device information includes: a device type of each server endpoint in the server device, and description information of each server endpoint;
  • the creation module is used to create a second functional unit under the central sub-endpoint when multiple server endpoints among the various server endpoints have the same device type and the multiple server endpoints have the same second functional unit for device control.
  • the device information includes: the device type of each server endpoint in the server device; when multiple server devices in the at least one server device have the same device type, the multiple server devices correspond to the same central sub-endpoint in the central device.
  • the device information includes: the device type of each server endpoint in the server device, and the description information of each server endpoint; the description information is used to indicate the functional unit of the corresponding server endpoint; when multiple server endpoints in each server endpoint have the same device type and the multiple server endpoints have the same second functional unit, the multiple server endpoints correspond to the same second functional unit in the central sub-endpoint.
  • the hub sub-endpoint further includes a descriptor functional unit, the descriptor functional unit includes an instance endpoint list attribute, and the instance endpoint list attribute includes endpoint information of each server-side endpoint corresponding to the functional unit in the hub sub-endpoint;
  • the sending module is further used to send the instance endpoint list attribute in the descriptor function unit to the client device.
  • the functional unit of the hub sub-endpoint also includes an instance endpoint table of a corresponding server endpoint, wherein the instance endpoint table includes the functional unit of the server endpoint corresponding to the hub sub-endpoint, and the endpoint information of each server endpoint corresponding to the functional unit in the hub sub-endpoint;
  • the sending module is further used to send endpoint information of at least one server endpoint corresponding to the first functional unit to the client device.
  • the functional unit in the hub sub-endpoint includes a current instance attribute, and the current instance attribute is used to indicate the currently controlled server endpoint among each server endpoint corresponding to the functional unit in the hub sub-endpoint;
  • the device also includes:
  • a first writing module configured to write the endpoint information of the server endpoint indicated by the second command into the current instance attribute in the first functional unit when the current instance attribute in the first functional unit is empty;
  • the sending module is used to send the third command to the server device of the server endpoint indicated by the second command according to the endpoint information in the current instance attribute.
  • the apparatus further comprises:
  • the first clearing module is used to clear the current instance attribute in the first functional unit after the server endpoint instructed by the second command completes executing the first operation.
  • the receiving module is further used to receive a fourth command sent by a client device, where the fourth command is used to indicate a second operation corresponding to the first functional unit;
  • the sending module is also used to send a fifth command to the server device of the server endpoint indicated by the second command when the value of the current instance attribute in the first functional unit is the endpoint information of the server endpoint indicated by the second command, and the fifth command is used to instruct the server endpoint indicated by the second command to perform the second operation.
  • the apparatus further comprises:
  • the second clearing module is used to clear the current instance attribute in the first functional unit when the first functional unit meets the clearing condition.
  • the parameter clearing condition includes at least one of the following conditions:
  • a command indicating an operation corresponding to the first functional unit is not received within a specified time period.
  • the device also includes:
  • a second writing module used for writing the endpoint information of the server endpoint indicated by the second command into the current instance parameter in the command attribute in the first functional unit;
  • the sending module is used to send the third command to the server device of the server endpoint indicated by the second command according to the endpoint information in the current instance parameters.
  • the endpoint information includes at least one of the following information:
  • the endpoint information further includes:
  • the tag information of the corresponding server endpoint is used to describe the corresponding server endpoint.
  • FIG. 12 shows a block diagram of a device control device provided by an embodiment of the present application.
  • the device control device has the function of implementing the method shown in FIG. 5 or FIG. 7 above, which is performed by the client device.
  • the device may include:
  • the sending module 1201 is used to send a first command to the central device, where the first command is used to instruct a first operation;
  • the sending module 1201 is also used to send a second command to the central device, and the second command is used to indicate the server endpoint; the second command is used to trigger the central device to send a third command to the server device of the server endpoint, and the third command is used to instruct the server endpoint to perform the first operation.
  • the first command is used to indicate the first operation corresponding to a first functional unit in the hub device; the first functional unit corresponds to at least one server endpoint;
  • the server endpoint indicated by the second command is part or all of the at least one server endpoint.
  • the hub device includes hub sub-endpoints corresponding to each server endpoint in at least one server device, and the hub sub-endpoints include each functional unit corresponding to the server endpoint.
  • the multiple server devices when multiple server devices in the at least one server device have the same device type, the multiple server devices correspond to the same hub sub-endpoint in the hub device.
  • the multiple server endpoints when multiple server endpoints among the respective server endpoints have the same device type and the multiple server endpoints have the same second functional unit, the multiple server endpoints correspond to the same second functional unit in the central sub-endpoint.
  • the central sub-endpoint further includes a descriptor function unit, the descriptor function unit includes an instance endpoint list attribute, and the instance endpoint list attribute includes endpoint information of each server endpoint corresponding to the function unit in the central sub-endpoint; the device also includes:
  • a receiving module used for receiving the instance endpoint list attribute in the descriptor function unit sent by the hub device
  • the sending module is used to send the second command to the central device according to the instance endpoint list attribute in the descriptor function unit.
  • the hub sub-endpoint also includes an instance endpoint table of a corresponding server endpoint, the instance endpoint table includes a functional unit of a server endpoint corresponding to the hub sub-endpoint, and endpoint information of each server endpoint corresponding to the functional unit in the hub sub-endpoint;
  • the device also includes:
  • a receiving module used for receiving endpoint information of at least one server endpoint corresponding to the first functional unit, sent by the central device;
  • the sending module is used to send the second command to the central device according to the endpoint information of at least one server endpoint corresponding to the first functional unit.
  • the functional unit in the central sub-endpoint includes a current instance attribute, and the current instance attribute is used to indicate the server endpoint currently accepting control among each server endpoint corresponding to the functional unit in the central sub-endpoint.
  • the sending module is further used to send a clear command to the central device, and the clear command is used to trigger clearing of the endpoint information in the current instance attributes in the first functional unit.
  • the command attributes of the functional unit in the central sub-endpoint include a current instance parameter, and the current instance parameter is used to indicate the server endpoint currently accepting control among the server endpoints corresponding to the functional unit in the central sub-endpoint.
  • the endpoint information includes at least one of the following information:
  • the endpoint information further includes:
  • the tag information of the corresponding server endpoint is used to describe the corresponding server endpoint.
  • FIG. 13 shows a block diagram of a device control device provided by an embodiment of the present application.
  • the device control device has the function of implementing the method shown in FIG. 6 or FIG. 7 above, which is performed by the server device.
  • the device may include:
  • the receiving module 1301 is used to receive a third command sent by the central device; the third command is sent by the central device after receiving the first command and the second command, the first command is used to indicate the first operation, and the second command is used to indicate the server endpoint;
  • the control module 1302 is used to instruct the server endpoint to perform the first operation according to the third command.
  • the first command is used to indicate the first operation corresponding to a first functional unit in the hub device; the first functional unit corresponds to at least one server endpoint;
  • the server endpoint indicated by the second command is part or all of the at least one server endpoint.
  • a sending module is used to send device information to the central device; the device information is used by the central device to create a central sub-endpoint corresponding to each server endpoint in at least one server device, and the central sub-endpoint contains each functional unit corresponding to the server endpoint.
  • the device information includes: the device type of each server endpoint in the server device; when multiple server devices in at least one server device have the same device type, the multiple server devices correspond to the same central sub-endpoint in the central device.
  • the device information includes: the device type of each server endpoint in the server device, and the description information of each server endpoint; the description information is used to indicate the functional unit of the corresponding server endpoint; when multiple server endpoints in each server endpoint have the same device type and the multiple server endpoints have the same second functional unit, the multiple server endpoints correspond to the same second functional unit in the central sub-endpoint.
  • the central sub-endpoint also includes a descriptor functional unit, which includes an instance endpoint list attribute, and the instance endpoint list attribute includes endpoint information of each server endpoint corresponding to the functional unit in the central sub-endpoint.
  • the functional unit in the central sub-endpoint includes a current instance attribute, and the current instance attribute is used to indicate the server endpoint currently accepting control among each server endpoint corresponding to the functional unit in the central sub-endpoint.
  • the command attributes of the functional unit in the central sub-endpoint include a current instance parameter, and the current instance parameter is used to indicate the server endpoint currently accepting control among the server endpoints corresponding to the functional unit in the central sub-endpoint.
  • the endpoint information includes at least one of the following information:
  • the endpoint information further includes:
  • the device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example to implement its functions.
  • the above-mentioned functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.
  • FIG14 shows a schematic diagram of the structure of a communication device 1400 provided in one embodiment of the present application.
  • the communication device 1400 may include: a processor 1401 , a receiver 1402 , a transmitter 1403 , a memory 1404 and a bus 1405 .
  • the processor 1401 includes one or more processing cores.
  • the processor 1401 executes various functional applications and information processing by running software programs and modules.
  • the receiver 1402 and the transmitter 1403 may be implemented as a communication component, which may be a communication chip.
  • the communication chip may also be referred to as a transceiver.
  • the memory 1404 is connected to the processor 1401 via a bus 1405.
  • the memory 1404 may be used to store a computer program, and the processor 1401 may be used to execute the computer program to implement each step in the above method embodiment.
  • memory 1404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, and volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, static access memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.
  • the communication device 1400 when the communication device 1400 is implemented as the above-mentioned hub device, the receiver 1402, the transmitter 1403 and the processor 1401 execute the computer program so that the communication device implements the various steps performed by the hub device in the method shown in either Figure 4 or Figure 7.
  • the receiver 1402 when the communication device 1400 is implemented as the above-mentioned server device, the receiver 1402, the transmitter 1403 and the processor 1401 execute the computer program so that the communication device implements each step performed by the server device in the method shown in either Figure 6 or Figure 7.
  • An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored.
  • the computer program is loaded and executed by a processor to implement all or part of the steps performed by a central device, a client device or a server device in any of the methods shown in Figures 4 to 7 above.
  • Computer-readable media include computer storage media and communication media, wherein the communication media include any media that facilitates the transmission of a computer program from one place to another.
  • the storage medium can be any available medium that a general or special-purpose computer can access.

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé et un appareil de commande de dispositif, ainsi qu'un dispositif et un support de stockage, qui relèvent du domaine technique de l'Internet des objets. Le procédé est exécuté par un dispositif concentrateur et consiste à : recevoir une première commande (401), la première commande servant à indiquer une première opération ; recevoir une deuxième commande (402), la deuxième commande servant à indiquer un point de terminaison serveur ; et envoyer une troisième commande à un dispositif serveur correspondant au point de terminaison serveur (403), la troisième commande servant à demander au point de terminaison serveur d'exécuter la première opération.
PCT/CN2023/120866 2023-09-22 2023-09-22 Procédé et appareil de commande de dispositif, dispositif et support de stockage Pending WO2025060103A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/120866 WO2025060103A1 (fr) 2023-09-22 2023-09-22 Procédé et appareil de commande de dispositif, dispositif et support de stockage

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/120866 WO2025060103A1 (fr) 2023-09-22 2023-09-22 Procédé et appareil de commande de dispositif, dispositif et support de stockage

Publications (1)

Publication Number Publication Date
WO2025060103A1 true WO2025060103A1 (fr) 2025-03-27

Family

ID=95073420

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/120866 Pending WO2025060103A1 (fr) 2023-09-22 2023-09-22 Procédé et appareil de commande de dispositif, dispositif et support de stockage

Country Status (1)

Country Link
WO (1) WO2025060103A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10120354B1 (en) * 2015-04-07 2018-11-06 SmartHome Ventures, LLC Coordinated control of home automation devices
US20190372799A1 (en) * 2017-03-10 2019-12-05 Tencent Technology (Shenzhen) Company Limited Device control method, storage medium, and computer device
CN112887177A (zh) * 2019-11-29 2021-06-01 北京京东尚科信息技术有限公司 智能设备控制系统、方法、设备和计算机可读介质
WO2021147109A1 (fr) * 2020-01-23 2021-07-29 华为技术有限公司 Procédé de transmission d'informations et dispositif associé
CN114244644A (zh) * 2021-12-16 2022-03-25 珠海格力电器股份有限公司 智能家居的控制方法和装置、存储介质、电子装置
WO2023082113A1 (fr) * 2021-11-10 2023-05-19 Oppo广东移动通信有限公司 Procédé et appareil pour configurer un dispositif de pontage, dispositif et support de stockage

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10120354B1 (en) * 2015-04-07 2018-11-06 SmartHome Ventures, LLC Coordinated control of home automation devices
US20190372799A1 (en) * 2017-03-10 2019-12-05 Tencent Technology (Shenzhen) Company Limited Device control method, storage medium, and computer device
CN112887177A (zh) * 2019-11-29 2021-06-01 北京京东尚科信息技术有限公司 智能设备控制系统、方法、设备和计算机可读介质
WO2021147109A1 (fr) * 2020-01-23 2021-07-29 华为技术有限公司 Procédé de transmission d'informations et dispositif associé
WO2023082113A1 (fr) * 2021-11-10 2023-05-19 Oppo广东移动通信有限公司 Procédé et appareil pour configurer un dispositif de pontage, dispositif et support de stockage
CN114244644A (zh) * 2021-12-16 2022-03-25 珠海格力电器股份有限公司 智能家居的控制方法和装置、存储介质、电子装置

Similar Documents

Publication Publication Date Title
EP2712118A1 (fr) Procédé et système pour gérer des dispositifs par lots
US10454994B2 (en) Mapping an action to a specified device within a domain
CN115296948A (zh) 场景信息的更新方法和装置、存储介质及电子装置
CN114826869B (zh) 设备管理方法和设备管理系统
CN116156005A (zh) 物联网中的设备控制方法、装置、网关设备及存储介质
US20090024727A1 (en) Network system management method
WO2023082113A1 (fr) Procédé et appareil pour configurer un dispositif de pontage, dispositif et support de stockage
WO2025060103A1 (fr) Procédé et appareil de commande de dispositif, dispositif et support de stockage
US8005915B2 (en) Method for providing download and upload service in network control system
KR20070119013A (ko) 네트워크 시스템의 디바이스 장치 및 프로파일 전송 방법
WO2018113184A1 (fr) Procédé de commande et de gestion de dispositif intelligent en fonction d'un protocole forces
WO2023201587A1 (fr) Procédé et appareil de commande de dispositif, dispositif et support de stockage
CN118605961A (zh) 设备管理方法、装置、设备及计算机可读存储介质
WO2023092504A1 (fr) Procédé et appareil de gestion d'abonnement, et dispositif informatique et support de stockage
CN118140497A (zh) 订阅权限信息处理方法、装置、计算机设备及存储介质
CN116962116A (zh) 网关联动方法、装置、设备及存储介质
US20080172481A1 (en) Method of Configuring Network Profile of Network System
WO2025081438A1 (fr) Procédé et appareil de mise à niveau d'un dispositif, dispositif et support de stockage
CN118103838A (zh) 信息上报方法、装置、设备及存储介质
CN119654600A (zh) 设备控制方法、装置、设备、存储介质及程序产品
WO2025145434A1 (fr) Procédé et appareil de traitement de scènes d'objets connectés, dispositif, support de stockage et produit
CN118435639A (zh) 安全域管理方法、装置、设备、存储介质及程序产品
WO2024103374A1 (fr) Procédé et appareil de traitement pour un abonnement par procuration, et dispositif informatique et support de stockage
CN118694624A (zh) 智能设备控制路径的选择方法、电子设备、可读存储介质和程序产品
WO2025081489A1 (fr) Procédés et appareils de traitement de message, dispositifs et support de stockage

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23952755

Country of ref document: EP

Kind code of ref document: A1