Remote control method and device of Matter equipment, storage medium, equipment and product

Abstract

The invention provides a remote control method and device of Matter equipment, a storage medium, equipment and a product. Under the condition that a cloud platform receives a remote control message reported by a terminal, an equipment identifier in the remote control message is obtained, and the remote control message is obtained by packaging a remote control instruction and the equipment identifier according to a preset protocol under the condition that the terminal receives the remote control instruction for Matter equipment; and acquiring a gateway identifier associated with the device identifier, and forwarding the remote control instruction to a gateway indicated by the gateway identifier, so that the gateway converts the remote control instruction based on a preset protocol into a local control instruction based on a Matter protocol, and sends the local control instruction to the Matter device indicated by the device identifier. The remote control instruction sent by the terminal to the Matter device through the cloud platform is forwarded through the gateway, remote control over the Matter device through the cloud platform following an own protocol is achieved, and transformation of a platform frame is avoided.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method, apparatus, storage medium, device and product for remote control of Matter devices. Background Technology

[0002] The Matter protocol is an open-source, local IoT protocol, and IoT devices that support the Matter protocol are called Matter devices. Currently, cloud platforms capable of remotely controlling Matter devices need to comply with the Matter protocol. However, for platform service providers that have already established their own protocol systems, controlling Matter devices requires rewriting the platform framework, application, and potential device interaction protocols to comply with the Matter protocol. This modification is very costly, and maintaining two sets of protocols simultaneously increases operational complexity and resource consumption. Summary of the Invention

[0003] In view of this, the present disclosure provides a method, apparatus, storage medium, device and product for remote control of Matter devices.

[0004] According to a first aspect of the present disclosure, a remote control method for a Matter device is provided. The method includes: when a cloud platform receives a remote control message sent from a terminal, obtaining a device identifier in the remote control message, wherein the remote control message is obtained by the terminal encapsulating the remote control instruction and the device identifier of the Matter device according to a preset protocol when the terminal receives a remote control instruction for the Matter device, the preset protocol being a protocol applied by the cloud platform; obtaining a gateway identifier associated with the device identifier, and forwarding the remote control instruction to a gateway indicated by the gateway identifier, causing the gateway to convert the remote control instruction based on the preset protocol into a local control instruction based on the Matter protocol, and sending the local control instruction to the Matter device indicated by the device identifier.

[0005] In some embodiments, the method further includes: when the cloud platform receives device status information reported by the gateway, obtaining a device identifier associated with the device status information, wherein the device status information is obtained by the gateway converting information based on the Matter protocol sent by the Matter device into information based on a preset protocol; and synchronizing the device attributes in the device status information to the terminal associated with the device identifier.

[0006] In some embodiments, the method further includes: when the cloud platform receives login user information corresponding to the terminal and device information corresponding to the Matter device sent by the terminal, establishing a binding relationship between the user and the Matter device based on the login user information and the device identifier in the device information, wherein the device information is obtained after the terminal establishes a connection with the Matter device; allocating a pre-created data model to the Matter device according to the device information, and associating the model identifier of the data model with the device identifier; converting the device type and device function contained in the device information into a target device type and target device function according to the data model; sending the target device type and target device function to the terminal, so that the terminal displays control options corresponding to the target device type and target device function in its user interface, and pulls device plugins corresponding to the control options; wherein the control options are used to adjust parameter information corresponding to the service functions of the Matter device; the device plugin is a plugin adapted to the preset protocol and used to support the function corresponding to the control options.

[0007] In some embodiments, the device information further includes a supplier identifier, a product identifier, and a public key for the Matter device; the device identifier is generated by concatenating the supplier identifier, the product identifier, and the public key to obtain a concatenated string; inputting the concatenated string into a cryptographic hash function to obtain a calculation result; and extracting a character at a specified position from the calculation result as the device identifier of the Matter device.

[0008] In some embodiments, before the cloud platform receives the login user information corresponding to the terminal and the device information corresponding to the Matter device sent by the terminal, the method further includes: when the cloud platform receives certificate applications sent by the gateway and the terminal, the cloud platform uses its root certificate to issue secondary certificates for the gateway and the terminal respectively, so that when the terminal establishes a connection with the Matter device, the terminal uses the secondary certificate to issue a tertiary certificate for the Matter device, and writes the gateway identifier of the gateway into the control permission list of the Matter device.

[0009] In some embodiments, after the cloud platform associates the model identifier of the data model with the device identifier, the method further includes: sending an instruction containing a device list to the gateway; or, upon receiving a request from the gateway to pull a device list, sending a response containing a device list to the gateway; wherein the device list includes a model identifier associated with the device identifier, causing the gateway to add the Matter device indicated by the device identifier, and converting information based on the Matter protocol and information based on a preset protocol according to the mapping relationship associated with the model identifier.

[0010] According to a second aspect of the present disclosure, a remote control method for a Matter device is provided. The method includes: when a terminal receives a remote control command for the Matter device, encapsulating the remote control command and a device identifier of the Matter device according to a preset protocol; sending the encapsulated remote control message to a cloud platform, causing the cloud platform to forward the remote control command to a gateway indicated by the gateway identifier when it obtains a gateway identifier associated with the device identifier; converting the remote control command based on the preset protocol into a local control command based on the Matter protocol through the gateway; and sending the local control command to the Matter device indicated by the device identifier, wherein the preset protocol is a protocol applied by the cloud platform.

[0011] In some embodiments, the method further includes: obtaining device status information associated with the device identifier from a cloud platform and displaying the device attributes in the device status information to a user; or receiving device status information associated with the device identifier pushed by a cloud platform and displaying the device attributes in the device status information to a user.

[0012] In some embodiments, the method further includes: when a connection is established between a terminal and a Matter device, generating a device identifier for the Matter device based on the device information of the Matter device; sending login user information corresponding to the terminal and device information including the device identifier to a cloud platform, so that the cloud platform establishes a binding relationship between the user and the Matter device based on the login user information and the device identifier, and allocates a pre-created data model to the Matter device according to the device information, and converts the device type and device function contained in the device information into a target device type and target device function according to the data model; receiving the target device type and target device function sent by the cloud platform, displaying control options corresponding to the target device type and target device function on the onboard user interface, and pulling device plugins corresponding to the control options; wherein, the control options are used to adjust parameter information corresponding to the service functions of the Matter device; the device plugins are plugins adapted to the preset protocol and are used to support the functions corresponding to the control options.

[0013] In some embodiments, the device information includes a supplier identifier, a product identifier, and a public key for the Matter device; generating a device identifier for the Matter device based on the device information includes: concatenating the supplier identifier, the product identifier, and the public key to obtain a concatenated string; inputting the concatenated string into a cryptographic hash function to obtain a calculation result; and extracting a character at a specified position from the calculation result as the device identifier for the Matter device.

[0014] In some embodiments, the method further includes: sending a certificate application to a cloud platform and receiving a secondary certificate issued by the cloud platform using its root certificate for the terminal; when establishing a connection with a Matter device, issuing a tertiary certificate for the Matter device using the secondary certificate, and writing the gateway identifier of the specified gateway into the control permission list of the Matter device.

[0015] According to a third aspect of the present disclosure, a remote control device for a Matter device is provided. The device includes: a receiving unit, configured to, upon receiving a remote control message from a terminal on a cloud platform, obtain a device identifier in the remote control message, wherein the remote control message is obtained by the terminal encapsulating the remote control instruction and the device identifier of the Matter device according to a preset protocol upon receiving a remote control instruction for the Matter device, the preset protocol being a protocol applied by the cloud platform; and a processing unit, configured to obtain a gateway identifier associated with the device identifier, and forward the remote control instruction to a gateway indicated by the gateway identifier, causing the gateway to convert the remote control instruction based on the preset protocol into a local control instruction based on the Matter protocol, and send the local control instruction to the Matter device indicated by the device identifier.

[0016] According to a fourth aspect of the present disclosure, a remote control device for a Matter device is provided. The device includes: a receiving unit, configured to encapsulate the remote control instruction and a device identifier of the Matter device according to a preset protocol when a terminal receives a remote control instruction for the Matter device; and a processing unit, configured to send the encapsulated remote control message to a cloud platform, wherein the cloud platform, upon obtaining a gateway identifier associated with the device identifier, forwards the remote control instruction to a gateway indicated by the gateway identifier, converts the remote control instruction based on the preset protocol into a local control instruction based on the Matter protocol through the gateway, and sends the local control instruction to the Matter device indicated by the device identifier, wherein the preset protocol is a protocol applied by the cloud platform.

[0017] According to a fifth aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the method described in either the first or second aspect.

[0018] According to a sixth aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to implement the method described in either the first or second aspect above.

[0019] According to a seventh aspect of the present disclosure, a computer program product is provided, including a computer program and instructions that, when executed by a processor, implement the method described in either the first or second aspect described above.

[0020] The technical solution provided in this disclosure can include the following beneficial effects: When the cloud platform receives a remote control message reported by the terminal, it obtains the device identifier in the remote control message. The remote control message is obtained by the terminal encapsulating the remote control command and the device identifier according to a preset protocol when it receives a remote control command for a Matter device. It then obtains the gateway identifier associated with the device identifier and forwards the remote control command to the gateway indicated by the gateway identifier. The gateway converts the remote control command based on the preset protocol into a local control command based on the Matter protocol and sends the local control command to the Matter device indicated by the device identifier. This disclosure achieves remote control of the Matter device using a cloud platform that follows its own protocol by forwarding the remote control command sent by the terminal to the Matter device through the cloud platform via a gateway. This avoids modifications to the platform framework and reduces implementation costs.

[0021] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0022] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0023] Figure 1 This is a framework diagram for implementing this disclosure;

[0024] Figure 2 This is a schematic diagram of a power distribution network process illustrated in an exemplary embodiment of this disclosure;

[0025] Figure 3 This disclosure is a flowchart illustrating a remote control method for a Matter device according to an exemplary embodiment;

[0026] Figure 4 This disclosure is a schematic diagram illustrating the control of a Matter device according to an exemplary embodiment;

[0027] Figure 5 This is a schematic diagram illustrating a Matter device reporting device status information according to an exemplary embodiment of this disclosure;

[0028] Figure 6 This is a schematic diagram of the structure of an electronic device according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0029] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0030] The Matter protocol, as an open-source smart home standard, is widely used in various devices collectively referred to as Matter devices. Matter devices can include door locks, cameras, lights, curtains, air conditioners, refrigerators, washing machines, dishwashers, and more. Through the Matter protocol, smart home devices from different manufacturers can interconnect, allowing users to manage and control different brands and types of Matter devices in a unified manner, greatly simplifying the operation process and improving the user experience.

[0031] With the increasing prevalence of Matter devices, user demand for remote control of these devices has also grown. Related technologies utilize cloud platforms that support the Matter protocol to achieve remote control. However, for platform service providers that have already established their own protocol systems, achieving compatibility and control of Matter devices requires significant modifications to their existing platform frameworks to embed the Matter protocol. Such modifications are not only costly but also necessitate the simultaneous maintenance of two protocol systems, increasing operational complexity and resource consumption.

[0032] Therefore, this disclosure provides a remote control method for Matter devices, applicable to scenarios where a user has installed an application supporting a preset protocol on their terminal and wants to remotely control the Matter device through that application. For example, the preset protocol could be the Mi protocol, in which case the application could be the Mi Home app.

[0033] Figure 1 This is a framework diagram for implementing this disclosure, such as Figure 1 As shown, after a user sends a remote control command to a Matter device through an application that supports the preset protocol, the application uploads the remote control command to a cloud platform that supports the preset protocol. The cloud platform then forwards the command to a designated gateway, which converts the remote control command based on the preset protocol into a local control command based on the Matter protocol and sends it to the Matter device. This enables remote control of the Matter device through a cloud platform that supports the preset protocol.

[0034] The following embodiments will first describe the network distribution process between the nodes involved in this disclosure in conjunction with the accompanying drawings.

[0035] Figure 2 This is a schematic diagram of a power distribution network process illustrated in an exemplary embodiment of this disclosure, such as... Figure 2 As shown, the power distribution process includes the following steps 201 to 206.

[0036] In step 201, the cloud platform receives certificate requests from the gateway and the terminal.

[0037] In step 202, the cloud platform uses its root certificate to issue secondary certificates for the gateway and the terminal respectively.

[0038] In step 203, the terminal uses the Level 2 certificate to issue a Level 3 certificate for the Matter device.

[0039] Through the Matter protocol, terminals with the application installed can automatically discover Matter devices. Once a terminal discovers a Matter device, the device sends its information to the terminal. The terminal then uses this information, along with a Level 2 certificate issued by the cloud platform, to issue a Level 3 certificate to the Matter device, thereby establishing a secure connection.

[0040] After a secure connection is established between the terminal and the Matter device, the terminal will encrypt and send information such as the WiFi account password to the Matter device according to the Matter protocol process, so that the Matter device can connect to the designated WiFi network based on the received account password.

[0041] When a terminal issues a certificate to a Matter device, it adds the gateway identifier of the specified gateway to the Matter device's access control list. This grants the gateway the authority to control the Matter device, and all subsequent interactions with that device will be proxied by the gateway. This access control list is a feature of the Matter protocol, and each Matter device has its own access control list.

[0042] In step 204, the terminal generates a device identifier for the Matter device based on the device information of the Matter device, and sends the login user information corresponding to the terminal, as well as the device information including the device identifier, to the cloud platform.

[0043] The application will generate a unique device identifier for the Matter device based on the device information, and send the login user information corresponding to the terminal, as well as the device information including the device identifier, to the cloud platform through a preset interface (such as the dev_bind interface).

[0044] In step 205, the cloud platform receives login user information corresponding to the terminal and device information corresponding to the Matter device sent by the terminal. Based on the login user information and the device identifier in the device information, it establishes a binding relationship between the user and the Matter device, allocates a pre-created data model to the Matter device according to the device information, and converts the device type and device function contained in the device information into a target device type and target device function according to the data model. Then, it sends the target device type and target device function to the terminal.

[0045] The cloud platform pre-stores multiple data models corresponding to different Matter device types. These data models enable the conversion between device information based on a preset protocol and device information based on the Matter protocol. Upon receiving device information, the cloud platform assigns a data model to the device, thus mapping the Matter device to a pre-configured data model on the cloud platform and associating the model identifier of the data model with the device identifier.

[0046] In step 206, the terminal receives the target device type and target device function sent by the cloud platform, displays control options corresponding to the target device type and target device function on the user interface, and retrieves device plugins corresponding to the control options. The control options are used to adjust parameter information corresponding to the service functions of the Matter device; the device plugins are plugins adapted to the preset protocol and used to support the functions corresponding to the control options. Subsequently, the user can issue remote control commands to the Matter device through touch operations on the user interface.

[0047] In the aforementioned network configuration process, after the cloud platform receives certificate requests from the gateway and the terminal with the installed application, it issues secondary certificates to the gateway and the terminal respectively using its own root certificate. These secondary certificates are signed by the cloud platform's root certificate, ensuring their authority and the integrity of the trust chain. When the terminal establishes a connection with the Matter device, the terminal uses its secondary certificate obtained from the cloud platform as the trust basis to issue a tertiary certificate for the Matter device. The tertiary certificate is signed by the terminal's secondary certificate, thus establishing a complete trust chain from the cloud platform's root certificate to the gateway, then to the terminal and the Matter device. In this way, the gateway, terminal, and Matter device share a common root of trust (i.e., the cloud platform's root certificate), and they can communicate based on this trust chain.

[0048] pass Figure 2 As can be seen, the power distribution process disclosed herein is mainly divided into two parts:

[0049] a. Network configuration for Matter devices: The cloud platform issues Level 2 certificates to the terminal and gateway, the terminal issues Level 3 certificates to the Matter device, and then the terminal sends the WiFi account password and other information to the Matter device according to the Matter protocol process, enabling it to access the WiFi network.

[0050] b. Matter device access to the cloud platform: The terminal generates a unique device identifier for the Matter device and sends the login user information corresponding to the terminal, as well as device information including the device identifier, to the cloud platform. The cloud platform will establish a binding relationship between the user and the Matter device based on the login user information and the device identifier, and allocate a data model to the Matter device according to the device information, so that the Matter device corresponds to a pre-configured data model on the cloud platform.

[0051] In the following embodiments, the power distribution process will be described using cloud platforms and terminals as the execution entities, respectively.

[0052] For the cloud platform, when it receives certificate requests from the gateway and the terminal, the cloud platform uses its root certificate to issue secondary certificates for the gateway and the terminal respectively. When the terminal establishes a connection with the Matter device, the terminal uses the secondary certificate to issue a tertiary certificate for the Matter device and writes the gateway identifier of the gateway into the control permission list of the Matter device.

[0053] After the terminal establishes a connection with the Matter device, it will send login user information corresponding to the terminal and device information including the device identifier to the cloud platform. For the cloud platform, upon receiving the login user information corresponding to the terminal and the device information including the device identifier sent by the terminal, it will establish a binding relationship between the user and the Matter device based on the login user information and the device identifier, allocate a pre-created data model to the Matter device according to the device information, associate the model identifier of the data model with the device identifier, and convert the device type and device function contained in the device information into target device type and target device function according to the data model, and then send the target device type and target device function to the terminal.

[0054] After the cloud platform associates the model identifier of the data model with the device identifier, the cloud platform needs to synchronize the model identifier associated with the device identifier to the gateway so that the gateway can obtain the mapping relationship corresponding to the model identifier when performing protocol conversion on the interaction information in the future.

[0055] In this embodiment, there are two methods for information synchronization between the cloud platform and the gateway. One is that the cloud platform sends an instruction containing a device list to the gateway, enabling the gateway to discover the Matter device locally. The other is that the gateway periodically pulls the device list from the cloud platform to promptly discover and add the Matter device. For the cloud platform, upon receiving a request from the gateway to pull the device list, it sends a response containing the device list to the gateway. This device list includes a model identifier associated with a device identifier, enabling the gateway to add the Matter device indicated by the device identifier and, based on the mapping relationship associated with the model identifier, convert information based on the Matter protocol and information based on a preset protocol.

[0056] For the terminal, the terminal sends a certificate application to the cloud platform and receives a secondary certificate issued by the cloud platform using its root certificate; when the terminal establishes a connection with the Matter device, it uses the secondary certificate to issue a tertiary certificate for the Matter device and writes the gateway identifier of the specified gateway into the control permission list of the Matter device.

[0057] When a connection is established between the terminal and the Matter device, a device identifier is generated for the Matter device based on the device information of the Matter device; the login user information corresponding to the terminal and the device information including the device identifier are sent to the cloud platform, so that the cloud platform establishes a binding relationship between the user and the Matter device based on the login user information and the device identifier, allocates a pre-created data model to the Matter device according to the device information, and converts the device type and device function contained in the device information into the target device type and target device function according to the data model.

[0058] The terminal receives the target device type and target device function sent by the cloud platform, displays control options corresponding to the target device type and target device function on the user interface, and pulls the device plugin corresponding to the control options; wherein, the control options are used to adjust the parameter information corresponding to the service function of the Matter device; the device plugin is a plugin adapted to the preset protocol and is used to support the function corresponding to the control options.

[0059] In some embodiments, the device information includes the supplier identifier, product identifier, and public key of the Matter device; generating a device identifier for the Matter device based on the device information includes: concatenating the supplier identifier, product identifier, and public key to obtain a concatenated string; inputting the concatenated string into a cryptographic hash function to obtain a calculation result; and extracting a character at a specified position from the calculation result as the device identifier of the Matter device. The cryptographic hash function may employ a Secure Hash Algorithm 256 (SHA-256 hash).

[0060] For example, the device's Vendor Identifier (VID), Product Identifier (PID), and the public key string of the authentication certificate are concatenated in sequence to form a long string. This long string is then hashed using SHA-256 to generate a 256-bit hash value (32 bytes of binary data). Finally, the lower 8 bytes (the lowest 64 bits) are extracted from the 256-bit hash value and used as the Device Identifier (DID) for the Matter device. Since each Matter standard device has a unique VID, PID, and public key, and the public key is unique, it can be guaranteed that the Matter device's DID will not conflict within a large range; that is, the DID can be considered unique on the current cloud platform.

[0061] The above embodiments will complete the network distribution process between the nodes involved in this disclosure. The following embodiments will describe the control process of the Matter device.

[0062] Figure 3 This disclosure is a flowchart illustrating a remote control method for a Matter device according to an exemplary embodiment, such as... Figure 3 As shown, for the cloud platform, the remote control method for Matter devices includes the following steps 301 to 302.

[0063] In step 301, when the cloud platform receives a remote control message sent from the terminal, the device identifier in the remote control message is obtained.

[0064] The remote control message is obtained by the terminal encapsulating the remote control command and the device identifier of the Matter device according to a preset protocol when it receives a remote control command for the Matter device. The preset protocol is the protocol applied by the cloud platform.

[0065] In this embodiment, the application installed on the terminal and the cloud platform support the same protocol. When the application receives a remote control command for the Matter device, it encapsulates the remote control command and the device identifier of the Matter device according to the internally supported standard protocol and reports it to the cloud platform.

[0066] In step 302, the gateway identifier associated with the device identifier is obtained, and the remote control command is forwarded to the gateway indicated by the gateway identifier, so that the gateway converts the remote control command based on the preset protocol into a local control command based on the Matter protocol, and sends the local control command to the Matter device indicated by the device identifier.

[0067] During network configuration, the cloud platform stores the gateway identifier associated with each device identifier. When the cloud platform retrieves the gateway identifier associated with a device identifier, if it finds it, it indicates that the device indicated by that device identifier belongs to the Matter device. In this case, the remote control command is forwarded to the gateway indicated by the gateway identifier, and then forwarded through the gateway. If it does not find the gateway identifier, it indicates that the device indicated by that device identifier uses the same protocol as the cloud platform. In this case, the control command is sent directly to the device indicated by that device identifier.

[0068] In some embodiments, a gateway with protocol conversion capabilities (i.e., mutual conversion between Matter protocol and preset protocol) may be referred to as a Matter gateway.

[0069] This disclosure, upon receiving a remote control message reported by a terminal on the cloud platform, obtains the device identifier from the remote control message. The remote control message is obtained by the terminal encapsulating the remote control command and the device identifier of the Matter device according to a preset protocol upon receiving a remote control command for the Matter device. The disclosure then obtains the gateway identifier associated with the device identifier and forwards the remote control command to the gateway indicated by the gateway identifier. The gateway converts the remote control command based on the preset protocol into a local control command based on the Matter protocol and sends the local control command to the Matter device indicated by the device identifier. This disclosure, by forwarding remote control commands sent by the terminal to the Matter device through the cloud platform via a gateway, achieves remote control of the Matter device using a cloud platform that adheres to its own protocol, avoiding modifications to the platform framework and reducing implementation costs.

[0070] For the terminal, when it receives a remote control command for the Matter device, it encapsulates the remote control command and the device identifier of the Matter device according to a preset protocol; the encapsulated remote control message is sent to the cloud platform, so that the cloud platform, upon obtaining the gateway identifier associated with the device identifier, forwards the remote control command to the gateway indicated by the gateway identifier, and the gateway converts the remote control command based on the preset protocol into a local control command based on the Matter protocol, and sends the local control command to the Matter device indicated by the device identifier.

[0071] Figure 4 This disclosure is a schematic diagram illustrating the control of a Matter device according to an exemplary embodiment, such as... Figure 4 As shown, the control process for the Matter device may include the following steps 401 to 404.

[0072] In step 401, the terminal receives a remote control command from the user for the Matter device.

[0073] In step 402, the terminal sends the remote control command to the cloud platform according to a preset protocol.

[0074] For example, the application could be the Mi Home APP, through which users can send remote control commands to Matter devices. These remote control commands will be encapsulated according to the Mi Home protocol and sent to the Mi Home Cloud.

[0075] In step 403, the cloud platform forwards the remote control command to the gateway.

[0076] In step 404, the gateway converts remote control commands based on a preset protocol into local control commands based on the Matter protocol, and sends the local control commands to the Matter device to control the Matter device.

[0077] The above embodiments describe the control process of the Matter device. In practical applications, the Matter device can also send device status information to the application in the terminal. The following embodiments will explain the process of the Matter device reporting device status information.

[0078] Figure 5 This is a schematic diagram illustrating a Matter device reporting device status information according to an exemplary embodiment of this disclosure, such as... Figure 5 As shown, the process of a Matter device reporting device status information may include the following steps 501 to 503.

[0079] In step 501, the Matter device reports its device status information to the gateway.

[0080] When a Matter device needs to report device status information, it will report the device status information to the gateway based on the Matter protocol.

[0081] In step 502, the gateway converts the device status information based on the Matter protocol into device status information based on a preset protocol and sends it to the cloud platform.

[0082] In step 503, the cloud platform receives device status information and synchronizes it to the terminal in a preset manner.

[0083] The cloud platform can save device status information and push it to applications on the terminal, or the application can retrieve device status information from the cloud platform and display it to the user.

[0084] For the cloud platform, the process of the Matter device reporting device status information involves the following steps: upon receiving the device status information reported by the gateway, the cloud platform obtains the device identifier associated with the device status information. The device status information is generated by the gateway converting the Matter protocol-based information into information based on a preset protocol after receiving information sent by the Matter device. The cloud platform then synchronizes the device attributes in the device status information to the terminal associated with the device identifier.

[0085] For the terminal, the process of the Matter device reporting device status information involves the terminal obtaining device status information associated with the device identifier from the cloud platform and displaying the device attributes in the device status information to the user; or the terminal receiving device status information associated with the device identifier pushed by the cloud platform and displaying the device attributes in the device status information to the user.

[0086] Because Matter devices operate under open-source licenses, their numbers will continue to grow. Integrating them into a proprietary protocol platform can expand the number of devices on that platform and increase user engagement. This disclosure not only enables remote control of Matter devices through a proprietary protocol platform but also reduces the manpower and server costs associated with maintaining two separate protocols.

[0087] For the foregoing method embodiments, in order to simplify the description, they are all described as a series of actions. However, those skilled in the art should know that this disclosure is not limited to the described order of actions, because according to this disclosure, some steps may be performed in other orders or simultaneously.

[0088] Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by this disclosure.

[0089] Corresponding to the aforementioned application function implementation method embodiments, this disclosure also provides embodiments of application function implementation apparatus and corresponding terminals.

[0090] This disclosure provides a remote control device for a Matter device, the device comprising:

[0091] The receiving unit is configured to obtain the device identifier in the remote control message when the cloud platform receives a remote control message sent from the terminal. The remote control message is obtained by the terminal encapsulating the remote control instruction and the device identifier of the Matter device according to a preset protocol when it receives a remote control instruction for the Matter device. The preset protocol is the protocol applied by the cloud platform.

[0092] The processing unit is configured to obtain the gateway identifier associated with the device identifier, forward the remote control command to the gateway indicated by the gateway identifier, and cause the gateway to convert the remote control command based on a preset protocol into a local control command based on the Matter protocol, and send the local control command to the Matter device indicated by the device identifier.

[0093] In some embodiments, the processing unit is further configured to, upon receiving device status information reported by the gateway on the cloud platform, obtain a device identifier associated with the device status information, wherein the device status information is obtained by the gateway converting information based on the Matter protocol sent by the Matter device into information based on a preset protocol; and synchronize the device attributes in the device status information to the terminal associated with the device identifier.

[0094] In some embodiments, the processing unit is further configured to, upon receiving login user information corresponding to the terminal and device information corresponding to the Matter device sent by the terminal to the cloud platform, establish a binding relationship between the user and the Matter device based on the login user information and the device identifier in the device information, wherein the device information is obtained after the terminal establishes a connection with the Matter device; allocate a pre-created data model to the Matter device according to the device information, and associate the model identifier of the data model with the device identifier; convert the device type and device function contained in the device information into a target device type and target device function according to the data model; send the target device type and target device function to the terminal, so that the terminal displays control options corresponding to the target device type and target device function in its user interface, and pulls device plugins corresponding to the control options; wherein the control options are used to adjust parameter information corresponding to the service function of the Matter device; and the device plugins are plugins adapted to the preset protocol to support the functions corresponding to the control options.

[0095] In some embodiments, the device information includes a supplier identifier, a product identifier, and a public key for the Matter device; the device identifier is generated by concatenating the supplier identifier, the product identifier, and the public key to obtain a concatenated string; inputting the concatenated string into a cryptographic hash function to obtain a calculation result; and extracting a character at a specified position from the calculation result as the device identifier of the Matter device.

[0096] This disclosure also provides a remote control device for a Matter device, the device comprising:

[0097] The receiving unit is configured to encapsulate the remote control command and the device identifier of the Matter device according to a preset protocol when the terminal receives a remote control command for the Matter device.

[0098] The processing unit is configured to send the encapsulated remote control message to the cloud platform, so that when the cloud platform obtains the gateway identifier associated with the device identifier, it forwards the remote control command to the gateway indicated by the gateway identifier, and the gateway converts the remote control command based on a preset protocol into a local control command based on the Matter protocol, and sends the local control command to the Matter device indicated by the device identifier. The preset protocol is the protocol applied by the cloud platform.

[0099] In some embodiments, the processing unit is further configured to obtain device status information associated with the device identifier from the cloud platform and display the device attributes in the device status information to the user; or receive device status information associated with the device identifier pushed by the cloud platform and display the device attributes in the device status information to the user.

[0100] In some embodiments, the processing unit is further configured to: generate a device identifier for the Matter device based on the device information of the Matter device when a connection is established between the terminal and the Matter device; send login user information corresponding to the terminal and device information including the device identifier to the cloud platform, so that the cloud platform establishes a binding relationship between the user and the Matter device based on the login user information and the device identifier; allocate a pre-created data model to the Matter device according to the device information; and convert the device type and device function contained in the device information into a target device type and target device function according to the data model; receive the target device type and target device function sent by the cloud platform; display control options corresponding to the target device type and target device function on the onboard user interface; and pull device plugins corresponding to the control options; wherein the control options are used to adjust parameter information corresponding to the service functions of the Matter device; and the device plugins are plugins adapted to the preset protocol to support the functions corresponding to the control options.

[0101] In some embodiments, the device further includes a network configuration unit, configured to send a certificate application to the cloud platform and receive a secondary certificate issued by the cloud platform for the terminal using its root certificate; when establishing a connection with the Matter device, to issue a tertiary certificate for the Matter device using the secondary certificate, and to write the gateway identifier of the specified gateway into the control permission list of the Matter device.

[0102] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this disclosure according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0103] Accordingly, this disclosure provides an electronic device, including: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to:

[0104] When the cloud platform receives a remote control message from the terminal, it obtains the device identifier from the remote control message. The remote control message is obtained by the terminal encapsulating the remote control command and the device identifier of the Matter device according to a preset protocol when it receives a remote control command for the Matter device. The preset protocol is the protocol applied by the cloud platform. The platform then obtains the gateway identifier associated with the device identifier and forwards the remote control command to the gateway indicated by the gateway identifier. The gateway converts the remote control command based on the preset protocol into a local control command based on the Matter protocol and sends the local control command to the Matter device indicated by the device identifier.

[0105] Alternatively, the processor described above can be configured to: when the terminal receives a remote control command for the Matter device, encapsulate the remote control command and the device identifier of the Matter device according to a preset protocol; send the encapsulated remote control message to the cloud platform, so that the cloud platform, upon obtaining the gateway identifier associated with the device identifier, forwards the remote control command to the gateway indicated by the gateway identifier, and through the gateway, converts the remote control command based on the preset protocol into a local control command based on the Matter protocol, and sends the local control command to the Matter device indicated by the device identifier, wherein the preset protocol is the protocol applied by the cloud platform.

[0106] Figure 6 This is a schematic diagram illustrating the structure of an electronic device 600 according to an exemplary embodiment. For example, the electronic device 600 may be a user device, specifically a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, wearable device such as smartwatch, smart glasses, smart bracelet, smart running shoes, etc.

[0107] Reference Figure 6 The electronic device 600 may include one or more of the following components: a processing component 602, a memory 604, a power supply component 606, a multimedia component 608, an audio component 610, an input / output (I / O) interface 612, a sensor component 614, and a communication component 616.

[0108] Processing component 602 typically controls the overall operation of electronic device 600, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 602 may include one or more modules to facilitate interaction between processing component 602 and other components. For example, processing component 602 may include a multimedia module to facilitate interaction between multimedia component 608 and processing component 602.

[0109] Memory 604 is configured to store various types of data to support the operation of device 600. Examples of this data include instructions for any application or method operating on electronic device 600, contact data, phonebook data, messages, pictures, videos, etc. Memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0110] Power supply component 606 provides power to various components of electronic device 600. Power supply component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 600.

[0111] Multimedia component 608 includes a screen that provides an output interface between the aforementioned electronic device 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 608 includes a front-facing camera and / or a rear-facing camera. When the electronic device 600 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0112] Audio component 610 is configured to output and / or input audio signals. For example, audio component 610 includes a microphone (MIC) configured to receive external audio signals when electronic device 600 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 604 or transmitted via communication component 616. In some embodiments, audio component 610 also includes a speaker for outputting audio signals.

[0113] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0114] Sensor assembly 614 includes one or more sensors for providing state assessments of various aspects of electronic device 600. For example, sensor assembly 614 can detect the on / off state of electronic device 600, the relative positioning of components such as the display and keypad of electronic device 600, changes in position of electronic device 600 or a component of electronic device 600, the presence or absence of user contact with electronic device 600, orientation or acceleration / deceleration of electronic device 600, and temperature changes of electronic device 600. Sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 614 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0115] Communication component 616 is configured to facilitate wired or wireless communication between electronic device 600 and other devices. Electronic device 600 can access wireless networks based on communication standards, such as WiFi, 4G or 5G, 4G LTE, 5G NR, or combinations thereof. In one exemplary embodiment, communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the aforementioned communication component 616 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0116] In an exemplary embodiment, the electronic device 600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0117] In an exemplary embodiment, a non-transitory computer-readable storage medium is also provided, such as a memory 604 including instructions, which, when executed by a processor 620 of an electronic device 600, enables the electronic device 600 to perform a remote control method for the Matter device.

[0118] The non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0119] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0120] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A remote control method for a Matter device, characterized in that, The method includes: When the cloud platform receives a remote control message from the terminal, it obtains the device identifier in the remote control message. The remote control message is obtained by the terminal encapsulating the remote control command and the device identifier of the Matter device according to a preset protocol when it receives a remote control command for the Matter device. The preset protocol is the protocol applied by the cloud platform. Obtain the gateway identifier associated with the device identifier, and forward the remote control command to the gateway indicated by the gateway identifier, so that the gateway converts the remote control command based on the preset protocol into a local control command based on the Matter protocol, and sends the local control command to the Matter device indicated by the device identifier.

2. The method according to claim 1, characterized in that, The method further includes: When the cloud platform receives device status information reported by the gateway, it obtains the device identifier associated with the device status information. The device status information is information that the gateway converts from Matter protocol-based information sent by Matter device to information based on a preset protocol after receiving Matter protocol-based information. The device attributes in the device status information are synchronized to the terminal associated with the device identifier.

3. The method according to claim 1, characterized in that, The method further includes: When the cloud platform receives login user information corresponding to the terminal and device information corresponding to the Matter device sent by the terminal, a binding relationship between the user and the Matter device is established based on the login user information and the device identifier in the device information. The device information is obtained after the terminal establishes a connection with the Matter device. Based on the device information, a pre-created data model is assigned to the Matter device, and the model identifier of the data model is associated with the device identifier; based on the data model, the device type and device function contained in the device information are converted into the target device type and target device function; The target device type and target device function are sent to the terminal, so that the terminal displays control options corresponding to the target device type and target device function on its user interface, and pulls device plugins corresponding to the control options; wherein, the control options are used to adjust parameter information corresponding to the service function of the Matter device; the device plugin is a plugin adapted to the preset protocol and is used to support the function corresponding to the control options.

4. The method according to claim 3, characterized in that, The device information also includes the Matter device's supplier identifier, product identifier, and public key; the device identifier is generated in the following way: The supplier identifier, the product identifier, and the public key are concatenated to obtain the concatenated string; Input the concatenated string into the password hash function to obtain the result; The character at a specified position is extracted from the calculation result and used as the device identifier of the Matter device.

5. The method according to claim 3, characterized in that, Before the cloud platform receives the login user information corresponding to the terminal and the device information corresponding to the Matter device sent by the terminal, the method further includes: When the cloud platform receives certificate requests from the gateway and the terminal, the cloud platform uses its root certificate to issue secondary certificates for the gateway and the terminal respectively. When the terminal establishes a connection with the Matter device, the terminal uses the secondary certificate to issue a tertiary certificate for the Matter device and writes the gateway identifier of the gateway into the control permission list of the Matter device.

6. The method according to claim 3, characterized in that, After associating the model identifier of the data model with the device identifier on the cloud platform, the method further includes: Send a command containing a list of devices to the gateway; or Upon receiving a request from the gateway to retrieve the device list, a response containing the device list is sent to the gateway. The device list includes model identifiers associated with device identifiers, enabling the gateway to add Matter devices indicated by the device identifiers, and to convert information based on the Matter protocol and information based on a preset protocol according to the mapping relationship associated with the model identifiers.

7. A remote control method for a Matter device, characterized in that, The method includes: When the terminal receives a remote control command for the Matter device, the remote control command and the device identifier of the Matter device are encapsulated according to a preset protocol; The encapsulated remote control message is sent to the cloud platform. When the cloud platform obtains the gateway identifier associated with the device identifier, it forwards the remote control command to the gateway indicated by the gateway identifier. The gateway converts the remote control command based on a preset protocol into a local control command based on the Matter protocol and sends the local control command to the Matter device indicated by the device identifier. The preset protocol is the protocol applied by the cloud platform.

8. The method according to claim 7, characterized in that, The method further includes: Retrieve device status information associated with the device identifier from the cloud platform, and display the device attributes in the device status information to the user; or Receive device status information associated with the device identifier pushed by the cloud platform, and display the device attributes in the device status information to the user.

9. The method according to claim 7, characterized in that, The method further includes: When a connection is established between the terminal and the Matter device, a device identifier is generated for the Matter device based on the device information of the Matter device. Send login user information corresponding to the terminal and device information including device identifier to the cloud platform, so that the cloud platform can establish a binding relationship between the user and the Matter device based on the login user information and the device identifier, allocate a pre-created data model to the Matter device according to the device information, and convert the device type and device function contained in the device information into the target device type and target device function according to the data model; The system receives the target device type and target device function sent by the cloud platform, displays control options corresponding to the target device type and target device function on the user interface, and pulls the device plugin corresponding to the control options; wherein, the control options are used to adjust the parameter information corresponding to the service function of the Matter device; the device plugin is a plugin adapted to the preset protocol and is used to support the function corresponding to the control options.

10. The method according to claim 9, characterized in that, The device information includes the Matter device's supplier identifier, product identifier, and public key; The process of generating a device identifier for the Matter device based on the device information of the Matter device includes: The supplier identifier, the product identifier, and the public key are concatenated to obtain the concatenated string; Input the concatenated string into the password hash function to obtain the result; The character at a specified position is extracted from the calculation result and used as the device identifier of the Matter device.

11. The method according to claim 9, characterized in that, The method further includes: Send a certificate application to the cloud platform and receive a secondary certificate issued by the cloud platform using its root certificate for the terminal; When establishing a connection with a Matter device, a Level 3 certificate is issued for the Matter device using the Level 2 certificate, and the gateway identifier of the specified gateway is written into the control permission list of the Matter device.

12. A remote control device for a Matter device, characterized in that, The device includes: The receiving unit is configured to obtain the device identifier in the remote control message when the cloud platform receives a remote control message sent from the terminal. The remote control message is obtained by the terminal encapsulating the remote control instruction and the device identifier of the Matter device according to a preset protocol when it receives a remote control instruction for the Matter device. The preset protocol is the protocol applied by the cloud platform. The processing unit is configured to obtain the gateway identifier associated with the device identifier, forward the remote control command to the gateway indicated by the gateway identifier, and cause the gateway to convert the remote control command based on a preset protocol into a local control command based on the Matter protocol, and send the local control command to the Matter device indicated by the device identifier.

13. A remote control device for a Matter device, characterized in that, The device includes: The receiving unit is configured to encapsulate the remote control command and the device identifier of the Matter device according to a preset protocol when the terminal receives a remote control command for the Matter device. The processing unit is configured to send the encapsulated remote control message to the cloud platform, so that when the cloud platform obtains the gateway identifier associated with the device identifier, it forwards the remote control command to the gateway indicated by the gateway identifier, and the gateway converts the remote control command based on a preset protocol into a local control command based on the Matter protocol, and sends the local control command to the Matter device indicated by the device identifier. The preset protocol is the protocol applied by the cloud platform.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the method of any one of claims 1 to 6, or the method of any one of claims 7 to 11.

15. An electronic device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to perform the method according to any one of claims 1 to 6, or the method according to any one of claims 7 to 11.

16. A computer program product, comprising a computer program and instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the method of any one of claims 1 to 6, or the method of any one of claims 7 to 11.

Images