System configuration and communication method that enable the ability to control and communicate with an ad-hoc device after acquisition

Abstract

The present disclosure provides a communication method, apparatus, device, and system in the technical field of communications. During communication between a controlled device and a control terminal, conversion can be performed by a controller. Since the SDP of the controlled device and the SDPID of the SDP are created in advance, the controller can convert all functions corresponding to the SDP into the native execution coding of the controller. If any function needs to be changed or any function needs to be added, it is only necessary to recreate a new SDP and the SDPID of the SDP according to the same process. That is, the functions of all devices can be redefined in an ad hoc manner, and the counterpart of the controller can respond on demand based on exactly the same mechanism. All these processes can be automatically performed without user intervention or awareness. From the user's perspective, they do not need to worry about the FW compatibility with their controller, and all they need to do is add a "different" new controlled device to their system.

Description

Technical Field

[0001] The present disclosure relates to the technical field of communications, and in particular, to communication methods, apparatuses, devices, and systems.

Background Art

[0002] Over the past few decades, smart home gadgets and IoT (Internet of Things) products have emerged and are spreading at an amazing pace. Implementations are diverse, and most of them are based on some well-known industrial standards that have achieved great success, such as wireless communication, BLE, Wi-Fi, Z-Wave, and Zigbee. They are implemented based on pre-defined protocols to achieve data security and interoperability between products from different vendors, and the function control codes of compatible devices (generally referring to intelligent devices such as sensors and actuators, hereinafter referred to as "controlee devices") need to be pre-defined. When a controller (e.g., a gateway HUB) is generated, it means that it needs to be programmed to support a specific communication protocol to execute all the necessary functions of any "known" controlee device. They have been able to maintain backward compatibility in some way. In other words, a new generation of controllers with updated protocol libraries can support old-generation controlee devices, but this is one-way compatibility and not vice versa.

[0003] In reality, regardless of "industrial standards" or "proprietary protocols", they all need to release protocol revisions to address the deficiencies of old designs or enable more advanced applications. As a result, many new generations of controlled devices have been developed and become available to consumers. These new generations of controlled devices have more advanced functions and are not compatible or completely incompatible with the controllers that consumers already own, which were initially made and may not necessarily be upgradable to support the new protocol.

[0004] In summary, one of the most common problems with the conventional interoperability protocols implemented so far is the lack of self - adaptability to technological progress and new innovations, which has created many compatibility frustrations and wastes in the real world. In this regard, creating an adaptive protocol and implementation mechanism to realize practical and future - oriented "forward - compatibility" IoT applications will be a game - changer.

Summary of the Invention

[0005] The objective of the embodiments of the present disclosure includes providing a communication method, apparatus, device, and system to solve the technical problem that existing technologies cannot effectively control all functions of all devices by a controller.

[0006] To solve the above problems, the embodiments of the present disclosure can be realized as follows.

[0007] In a first aspect, an embodiment of the present disclosure provides a communication method. Here, structured device control / communication protocol information (hereinafter referred to as SDP) of a controlled device is created in advance, and the SDP includes at least one of an SDP identifier (hereinafter referred to as SDPID) and a Data Encapsulation Format description table (hereinafter referred to as SDPDEF) information defined and registered by a developer of the controlled device. Corresponding to each SDPDEF information in the SDP, there are a decode / encode tool, an SDPDEF identifier (hereinafter referred to as SDPDEFID), and a user interface control and display generation tool (hereinafter referred to as UI tool) used in a control terminal. The method includes After the controller passes the identity authentication, it obtains one or more SDPIDs transmitted by the paired controlled device. Then, the controller uses the obtained SDPIDs to obtain corresponding SDP and SDPDEF information from an SDP data storage (hereinafter referred to as SDPDS) device for analyzing information necessary for controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPIDs provided by the paired controlled device is at least one, and the corresponding SDP is created by a device developer, or created by an SDP submission portal interface (hereinafter referred to as SDPSP) from the input of the device developer, or created by adding SDPDEF information from a developer of another compatible controlled device via the SDPSP. An optional user control terminal obtains control information including the assigned name of such a compatible controlled device with a caption from the controller, and corresponding information of a user interface created by the developer with a caption, whereby this control terminal can generate an appropriate user interface, generate control data, and analyze a status report between the controlled device via the controller. The controller receives a first control command, and the first control command is generated by a corresponding controlled device user interface in a control terminal created by a developer of the target controlled device, or is generated by an automatic preset condition from the controller, packaged into a corresponding UI tool, and includes at least one of a target controlled device ID and first control data; The controller analyzes a first encoding / decoding tool corresponding to the first control command based on the target SDP and SDPDEF information, decodes the first control command based on the first encoding / decoding tool to obtain a second control command including at least one of a target controlled device ID, a first SDPID, a first SDPDEF, and second control data, and thereby the controller transmits the second control command to the target controlled device.

[0008] In an optional embodiment, the method The controller receives a first status report transmitted by the target controlled device, the first status report includes at least one of a target controlled device ID, a second SDPID, a second SDPDEFID, and first status data, and the first SDPID and the second SDPID are the same or the first SDPID and the second SDPID are different; The controller analyzes a second encoding / decoding tool corresponding to the first status report based on the target SDP and SDPDEF information, decodes the first status report based on the second encoding / decoding tool to obtain a second status report including at least one of a target controlled device ID and second status data; The controller transmits the second status report to the control terminal, and thereby the control terminal renders a user interface created by a developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report.

[0009] In an optional embodiment, after passing the identity authentication, the controller obtains one or more SDPIDs sent by the paired controlled device. Then, the controller uses the obtained SDPIDs to obtain corresponding SDP and SDPDEF information from an SDP data storage (hereinafter referred to as SDPDS) device in order to analyze the information necessary for the method of controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPIDs provided by the paired controlled device is at least one. The corresponding SDP is created by the device developer, or created by an SDP submission portal interface (hereinafter referred to as SDPSP) from the input of the device developer, or created by adding SDPDEF information from the developer of another compatible controlled device via the SDPSP. The method includes: The controller sends a polling request to the target controlled device, and the polling request is used to fetch the first status report encoded based on the SDP and the SDPDEF information defined and registered by the developer of the target controlled device. The first status report includes at least one of a target controlled device ID, a second SDPID, a second SDPDEFID, and second status data. The first SDPID and the second SDPID are the same or different steps; The controller analyzes a second encoding / decoding tool corresponding to the first status report based on the target SDP and SDPDEF information, and decodes the first status report based on the second encoding / decoding tool to obtain a second status report including at least one of a target controlled device ID and second status data; The controller further includes a step of transmitting a second status report to the control terminal, whereby the control terminal renders a user interface created by a developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report.

[0010] In a second aspect, an embodiment of the present disclosure provides a communication method. The method includes: After the target controlled device passes identity authentication, it receives a second control command transmitted by a pairing controller that has obtained one or more SDPIDs. The controller then uses the obtained SDPIDs to obtain corresponding SDP and SDPDEF information from an SDPDS device in order to analyze information necessary for controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPIDs provided by the paired controlled device is at least one, and the corresponding SDP is created by a device developer, or created by an SDPSP from the input of the device developer, or created by adding SDPDEF information from a developer of another compatible controlled device via the SDPSP. The second control command includes at least one of a target controlled device ID, a first SDPID, a first SDPDEFID, and second control data obtained by the controller encoding a first control command based on a first corresponding encoding / decoding tool. The target controlled device executes the second control instruction, reports third state data reflecting the execution result, and the target controlled device transmits the third state report obtained by the decapsulation tool to the peer controller. The third state report includes at least one of a target controlled device ID, a third SDPID, a third SDPDEFID, and third state data. Thereby, the controller analyzes a third encoding / decoding tool corresponding to the third state report based on the target SDP and SDPDEF information, decodes the third state report to obtain a fourth state report, and whether the first SDPID, the second SDPID, and the third SDPID are the same, or the first SDPID, the second SDPID, and the third SDPID are different steps, The step that the controller transmits the fourth state report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target controlled device using the UI tool and updates the state of the target controlled device based on the fourth state report.

[0011] In an optional embodiment, the method is The step that the target controlled device receives a polling request transmitted by the peer controller, and the polling request is used to fetch the first state report encoded based on SDP and SDPDEF information, and the first state report includes at least one of a target controlled device ID, a second SDPID, a second SDPDEFID, and first state data. The target controlled device transmits a first status report to the counterpart controller, whereby the controller analyzes a second encoding / decoding tool corresponding to the first status report based on the SDP and SDPDEF information, decodes the first status report based on the second encoding / decoding tool to obtain a second status report, the second status report includes at least one of a target controlled device ID and second status data, and the first SDPID, the second SDPID, and the third SDPID are the same or the first SDPID, the second SDPID, and the third SDPID are different steps, The controller transmits the second status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report.

[0012] In a third aspect, an embodiment of the present disclosure provides a communication method. This method includes The SDPSP receives an SDP creation request sent by a controlled device developer, and the creation request is sent by the developer when compatible or appropriate SDPDEF information for the target controlled device cannot be found. The SDPSP provides a creation page or an application programming interface (hereinafter referred to as an API), whereby the developer of the target controlled device defines and creates information from the input based on the creation information, the creation information includes at least one SDPDEF information defined by the developer of the controlled device, and corresponding to each SDPDEF information, includes an encoding / decoding tool, an SDPDEFID, and a UI tool used on the control terminal. The SDPSP receives an SDP registration request sent by the controlled device developer, and the registration request is sent by the developer after inputting the creation information into the creation page or the provided API on the SDPSP. The SDPSP sends the SDP registration request to the SDPDS device, whereby the SDPDS device registers the target creation information, generates an SDP including at least one of the SDPID and the SDPDEF information defined by the developer of the target controlled device, and sends the SDP to the developer via the SDPSP, and the step that the SDPSP and the SDPDS device are arranged on the same device or the SDPSP and the SDPDS device are arranged on different devices.

[0013] In a fourth aspect, an embodiment of the present disclosure provides a communication method. This method is The SDPDS device receives the SDP registration request sent by the SDPSP, and the registration request with the creation information includes at least one SDPDEF information defined by the developer of the controlled device, whereby the SDPDS generates an SDP including at least one of the SDPID and the SDPDEF information, and sends it back to the developer via the SDPSP, and the step that the SDPSP and the SDPDS device are arranged on the same device or the SDPSP and the SDPDS device are arranged on different devices.

[0014] In an optional embodiment, the method is The step that the SDPDS device receives a request request sent by a controller, where the request request includes one or more SDPIDs sent by a paired controlled device after passing identity authentication The step that the SDPDS device identifies an SDP data package corresponding to the target SDPID and sends it to the controller, where the SDP data package includes an SDPID and at least one of the SDPDEF information defined and registered by the developer of the controlled device, and corresponding to each SDPDEF information in the SDP, includes a decode-encode tool, an SDPDEFID, and a UI tool.

[0015] In a fifth aspect, an embodiment of the present disclosure provides a controller. The controller includes a transceiver, a memory, and a processor. The memory stores a computer program executable on the processor. When executing the computer program, the processor implements the steps of the method according to any one of the above embodiments.

[0016] In a sixth aspect, an embodiment of the present disclosure provides a controlled device. The controlled device includes a transceiver, a memory, and a processor. The memory stores a computer program executable on the processor. When executing the computer program, the processor implements the steps of the method according to any one of the above embodiments.

[0017] In a seventh aspect, an embodiment of the present disclosure provides an SDPSP. The SDPSP includes a transceiver, a memory, and a processor. The memory stores a computer program executable on the processor. When executing the computer program, the processor implements the steps of the method according to any one of the above embodiments.

[0018] In an eighth aspect, an embodiment of the present disclosure provides an SDPDS device. The SDPDS device includes a transceiver, a memory, and a processor. The memory stores a computer program executable on the processor. When executing the computer program, the processor implements the steps of the method according to any one of the above embodiments.

[0019] In a ninth aspect, an embodiment of the present disclosure provides a communication system. The communication system includes the controller according to claim 9, the controlled device according to claim 10, the SDPSP according to claim 11, and the SDPDS device according to the above embodiment.

[0020] In the tenth aspect, an embodiment of the present disclosure provides a communication method. Here, the SDP of the controlled device is created in advance, and the SDP includes at least one of an SDPID and SDPDEF information defined and registered by the developer of the controlled device. Corresponding to each SDPDEF information in the SDP, it includes a decoding / encoding tool, an SDPDEFID, and a UI tool used in the control terminal. The method includes a determination module, a reception module, an encoding / decoding module, and a transmission module. The determination module is configured to analyze the SDPID transmitted by the paired controlled device after passing the identity authentication. Then, the controller uses the obtained SDPID to obtain the corresponding SDP and SDPDEF information from the SDPDS device in order to analyze the information necessary for the method of controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of the SDPIDs provided by the paired controlled device is at least one, and the corresponding SDP is created by the device developer, or created by the SDPSP from the input of the device developer, or created by adding SDPDEF information from the developers of other compatible controlled devices via the SDPSP. The reception module is configured to receive a first control command generated by the corresponding controlled device user interface of the control terminal created by the developer of the target controlled device, or generated by the automatic preset conditions from the controller. The first control command includes at least one of a target controlled device ID and first control data. The encoding / decoding module is configured to render a first encoding / decoding tool corresponding to the first control command based on the target SDP and SDPDEF information, and encode the first control command based on the first encoding / decoding tool to obtain a second control command. The transmission module is configured to transmit the second control instruction to the target controlled device, whereby the target controlled device executes the second control instruction.

[0021] In an optional embodiment, the receiving module is further configured to receive a first status report transmitted by the target controlled device, and the first status report includes at least one of a target controlled device ID, a second SDPID, a second SDPDEFID, and first status data. The encoding / decoding module is further configured to render a second encoding / decoding tool corresponding to the first status report based on the target SDP and SDPDEF information, and decode the first status report based on the second encoding / decoding tool to obtain a second status report. The transmission module is further configured to transmit the second status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report.

[0022] In an optional embodiment, the transmission module is further configured to transmit a polling request to the target controlled device, and the polling request is used to fetch the first status report encoded based on the SDP and SDPDEF information defined and registered by the developer of the target controlled device, and the first status report includes at least one of a target controlled device ID, a second SDPID, a second SDPDEFID, and second status data. The encoding / decoding module is further configured to analyze based on the target SDP and SDPDEF information from the target controlled device, and decode the first status report based on the second encoding / decoding tool to obtain a second status report. The transmission module is further configured to transmit a second status report to the control terminal, whereby the control terminal renders the user interface created by the developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report.

[0023] In an eleventh aspect, an embodiment of the present disclosure provides a communication device. The device includes a determination module, a reception module, an execution module, and a transmission module, The determination module is configured to analyze a registered SDPID and an encapsulation tool, The reception module is configured to receive a second control command transmitted by a pairing controller from which one or more SDPIDs are obtained after passing identity authentication. The controller then uses the obtained SDPIDs to obtain corresponding SDP and SDPDEF information from the SDPDS device to analyze information necessary for controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPIDs provided by the paired controlled device is at least one, and the corresponding SDP is created by a device developer, or created by the SDPSP from the input of the device developer, or created by adding SDPDEF information from the developer of another compatible controlled device via the SDPSP. The second control command includes at least one of the second control data obtained by the controller that encodes the first control command based on the target controlled device ID, the first SDPID, the first SDPDEFID, and the first corresponding encoding / decoding tool. The execution module is configured to execute the second control command to obtain third status data. The transmission module is configured to transmit the third status report obtained by the decapsulation tool to the peer controller, and the third status report includes at least one of the target controlled device ID, the third SDPID, the third SDPDEFID, and the third status data. Thereby, the controller analyzes the third encoding / decoding tool corresponding to the third status report based on the target SDP and SDPDEF information, decodes the third status report to obtain a fourth status report before transmitting it to the control terminal. Thereby, the control terminal uses the UI tool to render the user interface created by the developer of the target controlled device and updates the status of the target controlled device based on the fourth status report.

[0024] In an optional embodiment, the receiving module is further configured to receive a polling request transmitted by the peer controller. The polling request is used to obtain the first status report encoded based on the SDP and SDPDEF information. The first status report includes at least one of the target controlled device ID, the second SDPID, the second SDPDEFID, and the first status data. The transmission module is further configured to transmit the first status report to the peer controller. Thereby, the controller analyzes the second encoding / decoding tool corresponding to the first status report based on the SDP and SDPDEF information, and decodes the first status report based on the second encoding / decoding tool to obtain a second status report.

[0025] In a twelfth aspect, an embodiment of the present disclosure provides a communication device. The device includes a receiving module, a rendering module, and a transmission module. The receiving module is configured to receive an SDP creation request transmitted by a controlled device developer, and the creation request is transmitted by the developer. The rendering module is configured to generate a creation page or an API, whereby a developer of a target controlled device inputs and defines the information based on the creation information, and the creation information includes at least one SDPDEF information defined by the developer of the controlled device. Corresponding to each SDPDEF information, it includes a decode / encode tool, an SDPDEFID, and a UI tool used on a control terminal. The receiving module is further configured to receive a registration request sent by the developer of the controlled device, and the registration request is sent by the developer after inputting the creation information into a creation page on the SDPSP or the provided API. The sending module is further configured to send the registration request to the SDPDS device, whereby the SDPDS device registers the target creation information and generates an SDP including an SDPID and at least one of the SDPDEF information defined by the developer of the target controlled device, and sends the SDP to the developer via the SDPSP.

[0026] In a 13th aspect, an embodiment of the present disclosure provides a communication device. This device includes a receiving module, a registration module, and a sending module. The receiving module is configured to receive a registration request sent by the SDPSP, and the registration request with the creation information includes at least one SDPDEF information defined by the developer of the controlled device. Thereby, the SDPDS generates an SDP including an SDPID and at least one of the SDPDEF information and sends it back to the developer via the SDPSP. The registration module is configured to register the target SDP and generate a target SDPID of the target SDP creation information. The sending module is configured to send the target SDP to the developer of the controlled device.

[0027] In an optional embodiment, the receiving module is further configured to receive a request sent by a controller, the request including a target SDPID, The determining module is further configured to identify an SDP corresponding to the target SDPID, the SDP including an SDPID and at least one piece of SDPDEF information defined and registered by the developer of the controlled device, and corresponding to each piece of SDPDEF information in the SDP, including a decode / encode tool, an SDPDEFID, and a UI tool, The transmitting module is configured to transmit the target SDP to the controller.

[0028] The present disclosure provides a communication method, apparatus, device, and system related to the technical field of communications. During communication between a controlled device and a control terminal, conversion can be performed by a controller. Since the SDP of the controlled device and the SDPID of the SDP are created in advance, the controller can convert all functions corresponding to the SDP into the native execution coding of the controller. If any function needs to be changed or any function needs to be added, it is only necessary to recreate a new SDP and the SDPID of the SDP according to the same process. That is, the functions of all devices can be redefined in an ad hoc manner, and the counterpart of the controller can respond on demand based on exactly the same mechanism. All these processes can be automatically performed without user intervention or awareness. From the user's perspective, they do not need to worry about the FW compatibility with their controller, and all they need to do is add a "different" new controlled device to their system.

[0029] To make the above objects, features, and advantages of the present disclosure more clear and understandable, preferred embodiments are specifically illustrated below and detailed descriptions are provided in conjunction with the accompanying drawings.

Brief Description of the Drawings

[0030] To more clearly illustrate the technical solutions of the embodiments of the present disclosure, the accompanying drawings necessary for use in the embodiments of the present disclosure are briefly introduced below. However, the following accompanying drawings only show some embodiments of the present disclosure, and therefore, they should not be regarded as limiting the scope. It should be understood that those skilled in the art can obtain other related accompanying drawings according to these accompanying drawings without creative efforts.

[0031]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Embodiments for Carrying Out the Invention

[0032] To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure clearer, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings of the embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, not all of the embodiments of the present disclosure. Generally, the components of the embodiments of the present disclosure can be arranged and designed in various different configurations as described in this specification and shown in the accompanying drawings.

[0033] Therefore, the following detailed description of the embodiments of the present disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed present disclosure, but merely to illustrate selected embodiments of the present disclosure. All other embodiments obtained by those skilled in the art without creative efforts based on the embodiments of the present disclosure shall be included within the protection scope of the present disclosure.

[0034] In the following accompanying drawings, since the same reference numerals and characters represent the same items, if an item is defined in one accompanying drawing, there is no need to further define or explain it in subsequent accompanying drawings.

[0035] Some embodiments of the present disclosure will be described in detail below in combination with the drawings. The following embodiments and features within the embodiments can be combined with each other without conflict.

[0036] It should be noted that: SDP (Structured Device Control / Communication Protocol Information) is information that has been pre-created by the controlled device developer via the SDPSP (SDP Submission Portal interface) and stored in the SDPDS (SDP Data Storage) device. Basically, SDP includes at least one of an SDPID (SDP Identifier) and SDPDEF (SDP Data Encapsulation Format description table) information.

[0037] SDPDEF is defined and registered by the developer of the controlled device and may include a decode / encode tool, an SDPDEFID (SDPDEF Identifier), and a UI tool (user interface control and display generation tool) used on the control terminal.

[0038] SDPDEF is a format that is encapsulated during data exchange in the controller, the controlled device, and the SDPDS. Each SDP may include one or more SDPDEF information. All data can be modified by itself according to the requirements of the controlled device or application.

[0039] For example, the basic format of SDPDEF may be as follows: JPEG2025519085000002.jpg40170 In the above, the content of the payload is defined according to the requirements of the controlled device of the controlled device developer, where the developer needs to define the format and valid range of the values in the payload.

[0040] As an example of SDPDEF: The following SDPDEF information is defined for the switch control of the on and off states of the controlled device and is specifically as follows: JPEG2025519085000003.jpg40170

[0041] In the above, the format and valid range of the values in the payload list are as follows: JPEG2025519085000004.jpg26170

[0042] As another example of SDPDEF information, the following SDPDEF information is used to report the switch state with the on and off states of the controlled device. This is specifically as follows: JPEG2025519085000005.jpg29170

[0043] In the above, the format and valid range of the values in the payload list are as follows: JPEG2025519085000006.jpg22170 Note that SDPDEF information can include a version number, and different versions of SDPDEF information may or may not be compatible. Subsequent controlled device developers can update the old version of SDPDEF information to support the new version of SDPDEF information in the controlled device.

[0044] Decoder and encoder for SDPDEF information: Each SDPDEF information has a corresponding decoding / encoding tool, which can be generated by SDPSP or written in a computer language by the SDPDEF information developer via SDPSP. The decoding tool is used to decode the reports sent by the controlled device to obtain the data used by the control terminal. The encoding tool is used to encode the control commands sent by the control terminal to obtain the data for controlling the controlled device.

[0045] The functions of the SDPDS (i.e., SDP Database Storage Server) device may include: storing data related to SDP; registering and allocating SDP IDs; storing data registered by developer input via SDPSP or API, and storing developer accounts. In some embodiments, the SDPDS may include decoding data encapsulated in SDPDEF information and encoding data encapsulated in SDPDEF. In some embodiments, the SDPDS may be further configured to store data registered by the controlled device, store developer accounts, connect the controller and the control terminal, and generate an encapsulation tool (i.e., the development kit code of SDPDEF) for the controlled device. In some embodiments, the SDPDS may be further configured to store all encryption keys (DKEY, device key, and encryption key of the controlled device), and the identifier (DID, device id) of the controlled device, and generate and allocate DKEY and DID.

[0046] In one embodiment of the present disclosure, the controller may be a local control gateway (Hub) having network communication capabilities, or an online control server that communicates directly with the controlled device. The specific form of the above controller is not limited to the embodiments of the present disclosure.

[0047] In one embodiment of the present disclosure, the controlled device may be various devices (e.g., sensors or actuators, or a plurality of hybrids of these devices (i.e., the device includes sensors, actuators, or hybrids)) that can support communication and control via SDP. The communication between the controller and the controlled device may be implemented wired or wirelessly.

[0048] In one embodiment of the present disclosure, the control terminal may be an APP within a mobile phone terminal, or may also be a computer terminal, a dedicated controller terminal, the controller in the text, or a third-party control panel of an unknown device. The form of the control terminal is not particularly limited in the embodiments of the present disclosure.

[0049] One embodiment of the present disclosure provides a communication system. This system includes at least one controller, at least one controlled device, at least one control terminal, at least one SDPSP, and at least one SDPDS device. As described above, the SDPSP and the SDPDS device cooperate with each other to implement functions such as the development, registration, storage, and distribution of SDP, the APP UI tool of the control terminal, and the SDP encoding / decoding tool.

[0050] Referring to FIG. 1, FIG. 1 is a structural schematic diagram of a communication system provided in one embodiment of the present disclosure. As shown in FIG. 1, the controller may be a Hub, and is also called a control gateway. There may be one or more controllers. The controlled device may be an added device, for example, devices A to F shown in FIG. 1. Devices A to F communicate with the Hub based on SDPDEF. The server may be SDPDS. SDPDS and the Hub may also communicate based on SDPDEF. The APP shown in FIG. 1 may be installed on a control terminal (for example, a smart phone terminal).

[0051] In some embodiments, SDPDS stores information such as SDP, SDP ID, DID, DKEY, and SDK, and the HUB may download information such as SDP and DKEY from SDPDS based on information such as SDP ID or DID. Devices A to F may download information such as SDPID, DID, DKEY, and SDK from SDPDS.

[0052] In some embodiments, the HUB may have an editing (encoding / decoding) function. In this case, the HUB may perform communication editing between Devices A - F and the APP.

[0053] In some embodiments, the SDPDS may have an editing function. In this case, the SDPDS may perform communication editing between Devices A - F and the APP.

[0054] The editing here mainly refers to encoding or decoding via an encoder and a decoder.

[0055] In some embodiments, as shown in FIG. 1, the registration portal interface included in the system may be the SDPSP. The developers of Devices A - F shown in FIG. 1 may refer to the developers corresponding to different controlled devices, SDP, and SDPDEF. Also, the development devices used by other different controlled devices SDPDEF (i.e., the communication system may also include development devices), for example, the development devices used by the SDPDEF of Devices A - F may be used.

[0056] In some embodiments, the developer or the development device mainly develops the SDP corresponding to the controlled device by the SDPSP, and registers and issues the developed SDP to the server by the SDPSP or the like.

[0057] As described above, when registering with the server, the server may generate an SDP ID, return the SDP ID to the SDPSP, and finally present the SDP ID to the developers of Devices A - F.

[0058] Referring to FIG. 2, FIG. 2 is a structural schematic diagram of a controller provided in an embodiment of the present disclosure. As shown in FIG. 2, the controller includes a transceiver 201, a memory 202, and a processor 203. For example, the memory 202 that may include the aforementioned HUB stores a computer program executable on the processor 203. When the computer program is executed, the processor 203 performs the following steps. After passing the identity authentication, the SDPID sent by the paired controlled device is analyzed. Then, the controller uses the obtained SDPID to obtain the corresponding SDP and SDPDEF information from the SDPDS device in order to analyze the information necessary for the method of controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPIDs provided by the paired controlled device is at least one, and the corresponding SDP is created by the device developer, or created by the SDPSP from the input of the device developer, or created by adding SDPDEF information from the developer of other compatible controlled devices via the SDPSP. Receive a first control command generated by the corresponding controlled device user interface of the control terminal created by the developer of the target controlled device, or generated by the automatic preset conditions from the controller. The first control command includes at least one of the target controlled device ID and the first control data. Render a first encoding / decoding tool corresponding to the first control command based on the target SDP and SDPDEF information, and encode the first control command based on the first encoding / decoding tool to obtain a second control command. Send the second control command to the target controlled device, whereby the target controlled device executes the second control command.

[0059] Specifically, the SDP of the device to be controlled is created in advance. The SDP includes at least one of the SDPID and the SDPDEF information defined and registered by the developer of the device to be controlled. Corresponding to each SDPDEF information in the SDP, a decoding / encoding tool, an SDPDEFID, and a UI tool used on the control terminal are included. The controller uses the SDPID to obtain the corresponding SDP and SDPDEF information from the SDPDS. After sending the UI tool to the control terminal, thereby, the control terminal sends a first control command based on the UI tool of the SDPDEF information.

[0060] In the above, since the number of SDPIDs sent by the target control device is at least one, there may be one or more target SDPs corresponding to the target device to be controlled used.

[0061] Note that the information included in the above first control command can analyze a unique first encoding / decoding tool corresponding to the first control command. Specifically, the first encoding / decoding tool corresponding to the first control command may specifically be the first encoding / decoding tool corresponding to the first SDPDEFID and the first SDPID in the first control command. Further, it may be the first encoding / decoding tool corresponding to the identifier of the target device to be controlled in the first control command in the first control command. The first encoding / decoding tool is uniquely analyzed by specific information included in the first control command.

[0062] In some embodiments, the following steps can be further realized: Receive a first status report sent by the target device to be controlled. The first status report includes at least one of the target device to be controlled ID, the second SDPID, the second SDPDEFID, and the first status data. Render a second encoding / decoding tool corresponding to the first status report based on the target SDP and SDPDEF information, and decode the first status report based on the second encoding / decoding tool to obtain a second status report. Send the second status report to the control terminal, whereby the control terminal uses the UI tool to render the user interface created by the developer of the target controlled device and updates the status of the target controlled device based on the second status report.

[0063] Note that the information included in the above first status report can analyze the unique second encoding and decoding tool corresponding to the first status report. Specifically, the second encoding and decoding tool corresponding to the first status report may specifically be the second encoding and decoding tool corresponding to the second SDPDEFID and the second SDPID in the first status report. Furthermore, it may also be the second encoding and decoding tool corresponding to the identifier of the target controlled device in the first status report. The second encoding and decoding tool is uniquely analyzed by the specific information included in the first status report.

[0064] In some embodiments, after the controller receives one or more SDPIDs sent by the controlled device to be paired after passing the identity authentication, the controller then uses the obtained SDPIDs to obtain the corresponding SDP and SDPDEF information from the SDPDS device. The following steps can be further realized: Send a polling request to the target controlled device. The polling request is used to fetch the first status report encoded based on the SDP and the SDPDEF information defined and registered by the developer of the target controlled device. The first status report includes at least one of the target controlled device ID, the second SDPID, the second SDPDEFID, and the second status data. Analyze the second encoding and decoding tool corresponding to the first status report based on the target SDP and SDPDEF information, and decode the first status report based on the second encoding and decoding tool to obtain the second status report. The second status report includes at least one of the target controlled device ID and the second status data. Send a second status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report.

[0065] Note that the above first status report may or may not be an initial status report (original status report). (This may also be the above first status report.) This is not particularly limited in the embodiments of the present disclosure.

[0066] Referring to FIG. 3, FIG. 3 is a structural schematic diagram of a controlled device provided in an embodiment of the present disclosure. As shown in FIG. 3, the controlled device may include a transceiver 301, a memory 302, and a processor 303. The memory 302 stores a computer program that can be executed on the processor 303. When the computer program is executed, the processor 303 performs the following method steps: Determine the registered SDP ID and the encapsulation tool. Receive a second control instruction sent by a paired controller that obtains one or more SDPIDs after passing the identity authentication. The second control instruction includes at least one of the target controlled device ID, the first SDPID, the first SDPDEFID, and the second control data obtained by the controller encoding the first control instruction based on the first corresponding encoding / decoding tool. Execute the second control instruction and report third status data reflecting the execution result. The target controlled device sends the third status report obtained by the decapsulation tool to the counterpart controller. Analyze the third encoding / decoding tool corresponding to the third status report based on the target SDP and SDPDEF information, and decode the third status report to obtain a fourth status report. Send a fourth status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target controlled device using a UI tool and updates the state of the target controlled device based on the fourth status report.

[0067] Specifically, the first SDPID, the second SDPID, and the third SDPID are the same, or the first SDPID, the second SDPID, and the third SDPID are different. This is not particularly limited in the embodiments of the present disclosure.

[0068] In some embodiments, the method is Receiving a polling request sent by a peer controller, the polling request being used to fetch a first status report encoded based on SDP and SDPDEF information, the first status report including at least one of a target controlled device ID, a second SDPID, a second SDPDEFID, and first status data; Analyzing a second encoding / decoding tool corresponding to the first status report based on SDP and SDPDEF information, and decoding the first status report based on the second encoding / decoding tool to obtain a second status report; Sending the second status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target controlled device using a UI tool and updates the state of the target controlled device based on the second status report.

[0069] Referring to FIG. 4, FIG. 4 is a structural schematic diagram of an SDPSP provided in an embodiment of the present disclosure. As shown in FIG. 4, the SDPSP may include a transceiver 401, a memory 402, and a processor 403. The memory 402 stores a computer program executable on the processor 403. When the computer program is executed, the processor 403 performs the following method steps: Receiving an SDP creation request sent by a controlled device developer. This creation request is sent by the developer. Render the created page or API, whereby the developer of the target controlled device inputs and defines information based on the created information for creation. The created information includes at least one SDPDEF information defined by the developer of the controlled device. Corresponding to each SDPDEF information, a decode-encode tool, an SDPDEFID, and a UI tool used on the control terminal are included. Receive a registration request sent by the developer of the controlled device. The registration request is sent by the developer after inputting the created information into the created page on the SDPSP or the provided API. Send the registration request to the SDPDS device, whereby the SDPDS device registers the target created information, generates an SDP including an SDPID and at least one of the SDPDEF information defined by the developer of the target controlled device, and sends the SDP to the developer via the SDPSP.

[0070] Specifically, the above developer may further be a development controlled device. In addition to creating the target SDPDEF information using the encode-decode tool and the SDPDEFID, the developer can further create a UI tool corresponding to the target SDPDEF information based on the SDPDEF input. Specifically, the UI module provided by the SDPSP may be used to establish an independent UI tool used by each target SDPDEF information. The target SDP may further include a UI tool corresponding to each target SDPDEF information.

[0071] Referring to FIG. 5, FIG. 5 is a structural schematic diagram of an SDPDS device provided in an embodiment of the present disclosure. As shown in FIG. 5, the server may include a transceiver 501, a memory 502, and a processor 503. The memory 502 stores a computer program executable on the processor 503. When the computer program is executed, the processor 503 implements the following method steps: Receive the SDP registration request sent by the SDPSP. The registration request with creation information includes at least one SDPDEF information defined by the developer of the controlled device. Register the target SDP and SDP ID. Send the SDPID and SDPDEF information to the developer via the SDPSP.

[0072] Specifically, the target SDP file may further include a UI tool corresponding to each target SDPDEF information.

[0073] In some embodiments, the method includes receiving, by a controller, a request request including one or more SDPIDs sent by a paired controlled device after passing identity authentication, which is sent by the controller; identifying an SDP data package corresponding to the target SDPID and sending it to the controller.

[0074] Specifically, the SDP may further include a UI tool corresponding to each SDPDEF information.

[0075] In the above, the memories in FIGS. 2-5 may include a high-speed random access memory (RAM), and may also include a non-volatile memory, for example, at least one disk memory. The communication connection between this system network element and at least one other network element is realized via at least one communication interface (which may be wired or wireless), and the Internet, wide area network, local network, metropolitan area network, etc. may be used.

[0076] The bus may be an ISA bus, a PCI bus, or an EISA bus, etc. The bus may be a bus, a data bus, a control bus, etc. For the sake of simplicity of expression, the bus is represented by only one bidirectional arrow in FIGS. 2-5, but this does not mean that there is only one bus or only one type of bus.

[0077] In the above, the memory is configured to store a program, and the processor executes the program when receiving an execution instruction. The method executed by the apparatus defined by the process disclosed in any embodiment of the present disclosure can be applied to the processor or implemented by the processor.

[0078] The processor may be an integrated circuit with signal processing functions. In the implementation process, various steps of the above method may be completed by the integrated logic circuit of the hardware in the processor or instructions in the form of software. The above processor may be a general-purpose processor including a central processing unit (abbreviated as CPU), a network processor (abbreviated as NP), etc., or may also be a digital signal processor (abbreviated as DSP), an application-specific integrated circuit (abbreviated as ASIC), a field programmable gate array (abbreviated as FPGA) or other programmable logic devices, discrete gates, transistor logic devices, or discrete hardware components that can implement or execute various methods, steps, and logic blocks disclosed in the present disclosure. The general-purpose processor may be a microprocessor, or the processor may also be any conventional processor, etc. The steps in the method disclosed in the present disclosure may be directly executed and completed by a hardware decoding processor, or may be executed and completed by combining the hardware with a software module in the decoding processor. The software module may be arranged in a mature storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers. The storage medium is arranged in the memory, and the processor reads the information in the memory and combines it with its hardware to complete the steps of the above method.

[0079] Referring to FIG. 6, FIG. 6 is a schematic flowchart of a communication method provided in an embodiment of the present disclosure. The SDP of the controlled device is created in advance. The SDP includes at least one of an SDPID and SDPDEF information defined and registered by the developer of the controlled device. Corresponding to each SDPDEF information in the SDP, a decode / encode tool, an SDPDEFID, and a UI tool used on the control terminal are included. As shown in FIG. 6, the method may be applied to a controller such as a HUB, and this method may include the following steps S610 to S640.

[0080] In S610, after passing the identity authentication, the SDPID sent by the paired controlled device is analyzed. Using the obtained SDPID, the controller then obtains the corresponding SDP and SDPDEF information from the SDPDS device in order to analyze the information necessary for the method of controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPIDs provided by the paired controlled device is at least one, and the corresponding SDP is created by the device developer, or created by the SDPSP from the device developer's input, or created by adding SDPDEF information from the developers of other compatible controlled devices via the SDPSP.

[0081] In S620, a first control command generated by the corresponding controlled device user interface of the control terminal created by the developer of the target controlled device or generated by the automatic preset condition from the controller is received. The first control command is packaged in the corresponding UI tool and includes at least one of the target controlled device ID and the first control data.

[0082] In S630, the first encoding / decoding tool corresponding to the first control command is analyzed based on the target SDP and SDPDEF information, and the first control command is encoded based on the first encoding / decoding tool to obtain a second control command. The second control command includes at least one of the target controlled device ID, the first SDPID, the first SDPDEF, and the second control data.

[0083] In S640, the second control command is sent to the target controlled device.

[0084] Specifically, the SDP of the controlled device is created in advance, and the SDP includes at least one of the SDPID and the SDPDEF information defined and registered by the developer of the controlled device. Corresponding to each SDPDEF information in the SDP, a decoding / encoding tool, an SDPDEFID, and a UI tool used in the control terminal are included. The controller obtains the corresponding SDP and SDPDEF information from the SDPDS using the SDPID, and after sending the UI tool to the control terminal, thereby, the control terminal sends the first control command based on the UI tool of the SDPDEF information.

[0085] In the above, since the number of SDPIDs sent by the target control device is at least one, there may be one or more target SDPs corresponding to the target controlled device to be used.

[0086] Note that the information included in the above first control command can analyze a unique first encoding / decoding tool corresponding to the first control command. Specifically, the first encoding / decoding tool corresponding to the first control command may specifically be the first encoding / decoding tool corresponding to the first SDPID and the first SDPDEFID in the first control command, and further, it may be the first encoding / decoding tool corresponding to the identifier of the target controlled device in the first control command. The first encoding / decoding tool is uniquely analyzed by specific information included in the first control command.

[0087] Through the embodiments of the present disclosure, a communication method, apparatus, device, and system in the technical field of communication are provided. During communication between a controlled device and a control terminal, conversion can be performed by a controller. Since the SDP information of the controlled device and the SDPID of the SDP information are created in advance, the controller can convert all functions corresponding to the SDP information into the native execution coding of the controller. If any function needs to be changed or any function needs to be added, it is only necessary to recreate the new SDP information and the SDPID of the SDP information according to the same process. That is, the functions of all devices can be redefined in an ad hoc manner, and the counterpart of the controller can respond on demand based on exactly the same mechanism. All these processes can be automatically performed without user intervention or awareness. From the user's perspective, they do not need to worry about the FW compatibility with their controller, and all they need to do is add a "different" new controlled device to their system.

[0088] In some embodiments, the method further includes the following steps S650 to S670. In S650, a first status report sent by a target controlled device is received. The first status report includes at least one of a target controlled device ID, a second SDPID, a second SDPDEFID, and first status data.

[0089] In S660, based on the target SDP and SDPDEF information, a second encoding / decoding tool corresponding to the first status report is analyzed, and the first status report is decoded based on the second encoding / decoding tool to obtain a second status report. The second status report includes at least one of a target controlled device ID and second status data.

[0090] In the S670, a second status report is sent to the control terminal, whereby the control terminal renders the user interface created by the developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report.

[0091] Note that the information included in the above first status report can analyze a unique second encoding / decoding tool corresponding to the first status report. Specifically, the second encoding / decoding tool corresponding to the first status report may specifically be the second encoding / decoding tool corresponding to the second SDPDEFID and the second SDPID in the first status report. Furthermore, it may also be the second encoding / decoding tool corresponding to the identifier of the target controlled device in the first status report. The second encoding / decoding tool is uniquely analyzed by specific information included in the first status report.

[0092] Note that the above first status report may be an initial status report (original status report) or may not be an initial status report (this may also be the above first status report). This is not particularly limited in the embodiments of the present disclosure.

[0093] Furthermore, as shown in FIG. 7, after the controller obtains one or more SDPIDs transmitted by the controlled device to be paired after passing the identity authentication, the controller then uses the obtained SDPIDs to obtain the corresponding SDP and SDPDEF information from the SDP device. Furthermore, the controller may send a polling request to the target controlled device to obtain the status through the following steps S710 to S730: In S710, a polling request is sent to the target controlled device. The polling request is used to fetch a first status report encoded based on the SDP and the SDPDEF information defined and registered by the developer of the target controlled device. The first status report includes at least one of the target controlled device ID, the second SDPID, the second SDPDEFID, and the second status data.

[0094] In S720, based on the target SDP and SDPDEF information, the second encoding / decoding tool corresponding to the first status report is analyzed, and the first status report is decoded based on the second encoding / decoding tool to obtain a second status report. The second status report includes at least one of the target controlled device ID and the second status data.

[0095] In S730, the second status report is sent to the control terminal, whereby the control terminal renders the user interface created by the developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report.

[0096] Note that the above first status report may or may not be an initial status report (original status report) (this may also be the above first status report). This is not particularly limited in the embodiments of the present disclosure.

[0097] Referring to FIG. 8, FIG. 8 is a schematic flowchart of a communication method provided in an embodiment of the present disclosure. As shown in FIG. 8, the method may include the following steps S810 to S840: In S810, the registered SDPID and the encapsulation tool are analyzed.

[0098] In S820, after passing the identity authentication, the controller receives a second control command sent by one or more pairing controllers that claim one or more SDPIDs. Then, the controller uses the obtained SDPIDs to obtain corresponding SDP and SDPDEF information from the SDPDS device in order to analyze the information necessary for controlling the controlled device and communicating with it. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPIDs provided by the paired controlled device is at least one, and the corresponding SDP is created by the device developer, or created by the SDPSP from the device developer's input, or created by adding SDPDEF information from the developers of other compatible controlled devices via the SDPSP. The second control command includes at least one of the target controlled device ID, the first SDPID, the first SDPDEFID, and the second control data obtained by the controller encoding the first control command based on the first corresponding encoding / decoding tool.

[0099] In S830, execute the second control command to obtain third state data.

[0100] In S840, send the third state report obtained by the decapsulation tool to the peer controller. The third state report includes at least one of the target controlled device ID, the third SDPID, the third SDPDEFID, and the third state data. Thereby, the controller analyzes the third encoding / decoding tool corresponding to the third state report based on the target SDP and SDPDEF information, decodes the third state report before sending it to the control terminal to obtain a fourth state report, and thereby the control terminal uses the UI tool to render the user interface created by the developer of the target controlled device and updates the state of the target controlled device based on the fourth state report.

[0101] Specifically, the third SDP ID may be the same as the first SDP ID or different from the first SDP ID. Similarly, the third SDPDEF ID may be the same as the first SDPDEF ID or different from the first SDPDEF ID. This is not particularly limited in the embodiments of the present disclosure.

[0102] In some embodiments, the method receives a polling request sent by a peer controller, the polling request being used to obtain a first status report encoded based on SDP and SDPDEF information, the first status report including at least one of a target controlled device ID, a second SDP ID, a second SDPDEF ID, and first status data;

[0103] analyzes a second encoding / decoding tool corresponding to the first status report based on the SDP and SDPDEF information, and decodes the first status report based on the second encoding / decoding tool to obtain a second status report.

[0104] Referring to FIG. 9, FIG. 9 is a schematic flowchart of another communication method provided in an embodiment of the present disclosure. As shown in FIG. 9, the method may include the following steps S910 to S940. In S910, an SDP creation request sent by a controlled device developer is received. This creation request is sent by the developer.

[0105] In S920, a rendering module is configured to generate a creation page or API, whereby a developer of a target controlled device inputs and defines information based on the creation information. The creation information includes at least one SDPDEF information defined by the developer of the controlled device. Corresponding to each SDPDEF information, a decoding / encoding tool, an SDPDEF ID, and a UI tool used on a control terminal are included.

[0106] In S930, a registration request sent by the controlled device developer is received. The registration request is sent by the developer after inputting creation information on the creation page on the SDPSP or the provided API.

[0107] In S940, the registration request is sent to the SDPDS device, whereby the SDPDS device registers the target creation information, generates an SDP including at least one of the SDPID and the SDPDEF information defined by the developer of the target controlled device, and sends the SDP to the developer via the SDPSP.

[0108] Specifically, the above developer may further be a development device. In addition to creating the target SDPDEF information and the encoding / decoding tool corresponding to the target SDPDEF information, the developer can further create a UI tool corresponding to the target SDPDEF information based on the SDPDEF input. Specifically, the UI module provided by the SDPSP may be used to establish an independent UI tool used by each target SDPDEF information. The target SDP may further include a UI tool corresponding to each target SDPDEF information.

[0109] Referring to FIG. 10, FIG. 10 is a schematic flowchart of another communication method provided in an embodiment of the present disclosure. As shown in FIG. 10, the method may include the following steps S1010 to S1030. In S1010, a registration request sent by the SDPSP is received. The registration request having creation information includes at least one SDPDEF information defined by the developer of the controlled device. Thereby, the SDPDS generates an SDP including at least one of the SDPID and the SDPDEF information and sends it back to the developer via the SDPSP.

[0110] In S1020, the target SDP is registered and the target SDPID of the target SDP creation information is generated.

[0111] In S1030, the target SDP is sent to the developer of the controlled device.

[0112] Specifically, the target SDP may further include a UI tool corresponding to each target SDPDEF information.

[0113] In some embodiments, the method is receiving a request request including one or more SDPIDs sent by the paired controlled device after passing identity authentication and sent by the controller; identifying an SDP data package corresponding to the target SDPID and sending it to the controller, where the SDP data package includes an SDPID and at least one of SDPDEF information defined and registered by the developer of the controlled device, and corresponding to each SDPDEF information in the SDP, further including steps of including a decode / encode tool, an SDPDEFID, and a UI tool.

[0114] Referring to FIG. 11, FIG. 11 is a schematic flowchart of a method for developing a target controlled device provided in an embodiment of the present disclosure.

[0115] When developing a target controlled device, the developer or development device of the target controlled device needs to define the requirements of the target controlled device, that is, the functions to be registered. For example, the functions registered by an air conditioner controller include wind speed control, wind speed reporting, mode control, mode reporting, temperature control, and temperature reporting.

[0116] Next, the developer or development device of the target controlled device searches for the above-registered functions on the SDPSP and determines whether there is target SDPDEF information that matches the above-registered functions. For example, the search results are as follows: JPEG2025519085000007.jpg59170

[0117] This shows the target SDPDEF information for temperature control and temperature reporting, but there is no target SDPDEF information for wind speed control, wind speed reporting, mode control, and mode reporting. Next, the developer or development device of the target device to be controlled sends an SDP creation request to the SDPSP. As a specific implementation method, it is possible for the developer to create an SDP from the input of the SDPSP including the SDPDEF information corresponding to the requirements of the device to be controlled. For ease of understanding, the target SDPDEF information corresponding to the above wind speed control, wind speed reporting, mode control, and mode reporting is shown below by way of example respectively (note that what is shown here is only one encapsulation form of SDPDEF, and SDPDEF may further include other forms, and the encapsulation form of SDPDEF is not particularly limited in the embodiments of the present disclosure).

[0118] Function: Wind speed control JPEG2025519085000008.jpg32170

[0119] Payload list: JPEG2025519085000009.jpg29170

[0120] Function: Wind speed reporting JPEG2025519085000010.jpg29170

[0121] JPEG2025519085000011.jpg29170

[0122] Function: Mode control JPEG2025519085000012.jpg29170

[0123] Payload list: JPEG2025519085000013.jpg44170

[0124] Function: Mode reporting JPEG2025519085000014.jpg29170

[0125] Payload list: JPEG2025519085000015.jpg44170

[0126] After the target SDPDEF information is established and obtained, the decoder and encoder of each SDPDEF information can be generated by the SDPSP or written in a computer language on the SDPSP.

[0127] For example, the SDPDEF status data of the wind speed report is as follows: JPEG2025519085000016.jpg29170

[0128] The corresponding decoding result is as follows: JPEG2025519085000017.jpg48170

[0129] The SDPDEF status data of the mode report is as follows: JPEG2025519085000018.jpg29170

[0130] The corresponding decoding result is as follows: JPEG2025519085000019.jpg43170

[0131] The control command for wind speed control (UI data sent by the APP of the control terminal) is as follows: JPEG2025519085000020.jpg56170

[0132] The corresponding encoding result is as follows: JPEG2025519085000021.jpg29170

[0133] The control command for mode control (UI data sent by the APP of the control terminal) is as follows: JPEG2025519085000022.jpg56170

[0134] The encoding result is as follows: JPEG2025519085000023.jpg29170

[0135] After obtaining the decoders and encoders for each target SDPDEF information, the developer or development device of the target controlled device uses the UI development module provided by the SDPSP to establish an independent UI tool used by each target SDPDEF information.

[0136] The developer or development device needs to design according to each target SDPDEF information so that the content decoded at the control terminal can be displayed on the SDPSP using the provided UI development module and the generated data can be sent out. The developer may develop one or more UI tools for the same SDPDEF information using the UI tool.

[0137] The UI development module provided on the SDPSP includes, but is not limited to, the following modules: 1) Toggle switch module; 2) Bidirectional switch module; 3) Circular numerical bar (circular progress control bar) module; 4) Long numerical bar module; 5) Text display column module; 6) List-type text display column module; 7) Drop-down list module.

[0138] For example, as shown in Figure 12, the switch control UI developed using the module on the SDPSP includes the content as shown in the following table. JPEG2025519085000024.jpg82170

[0139] For example, as shown in Figure 13, the dimming control UI developed using the module on the SDPSP includes the content as shown in the following table. JPEG2025519085000025.jpg63170

[0140] For example, the wind speed control UI and the report display UI are as follows: JPEG2025519085000026.jpg63170

[0141] The UI tools used for mode control and reporting are as follows: JPEG2025519085000027.jpg63170

[0142] After the above design is completed, the controlled device developer sends a registration request for the target SDP to the SDPDS device via the SDPSP. The target SDP includes at least one SDPDEF information defined by the developer of the controlled device. Corresponding to each SDPDEF information, a decode-encode tool, an SDPDEFID, and a UI tool used on the control terminal are included. For the above example, the target SDP includes: the first SDPDEF information of wind speed control including the encode-decode tool and UI tool of the wind speed control SDPDEFID, the second SDPDEF information of wind speed report including the SDPDEFID, the encode-decode tool, and the UI tool, the third SDPDEF information of mode control including the SDPDEFID, the encode-decode tool, and the UI tool, and the fourth SDPDEF information of mode report including the SDPDEFID, the encode-decode tool, and the UI tool.

[0143] After receiving the registration request for the target SDP and passing the check, the SDPDS device registers the target creation information, generates an SDP including the SDPID and at least one of the SDPDEF information defined by the developer of the target controlled device, and sends the SDP to the developer via the SDPSP. Specifically, it is possible for the SDPSP to send the target SDPID and the encapsulation tool to the developer of the target controlled device, or for the developer of the target controlled device to download the target SDPID and the encapsulation tool from the SDPDS device via the SDPSP. In this way, when reporting a success report corresponding to the above registration request, the SDP and the SDPDEF information for registering the requirements of the controlled device are completed.

[0144] After the software development of the target controlled device is completed, the hardware version number, battery mode, used SDPDEF, and default name are further registered in the SDPSP. For example: JPEG2025519085000028.jpg22170

[0145] These controlled device information is registered in the SDPSP and stored in the SDPDS device. For example, the controlled device information is as follows: JPEG2025519085000029.jpg70170

[0146] The software data may further include the method and numerical values displayed in at least one APP list, at least one control interface formed using the SDPDEF component, all used SDPDEF, the SDPDEF sent during addition, the software version number, and the encoded software archive.

[0147] When the target controlled device is manufactured, the following data needs to be obtained from the SDPDS device: the identifier (DID) of the target controlled device, the encryption key (DKEY), the manufacturing date, and the SN.

[0148] After the development of the above-mentioned target controlled device is completed, the target controlled device may be added to the controller. Referring to FIG. 14, FIG. 14 is a schematic flowchart of the method for adding and controlling a target controlled device provided in an embodiment of the present disclosure. After the user of the control terminal (APP) presses a button, the addition process is started within the APP. The APP moves to the two-dimensional code reading page and instructs the user to read the two-dimensional code provided on the target controlled device. The user reads the two-dimensional code on the target controlled device according to the instruction. Next, the APP of the control terminal can obtain the identifier (DID) of the target controlled device.

[0149] Next, the APP of the control terminal sends a request to add a target controlled device with an identifier (DID) of the target controlled device to the SDPDS device. The SDPDS device determines a corresponding encryption key (DKEY) according to the identifier (DID) of the target controlled device in the addition request. Further, the SDPDS device sends an addition command to the controller along with the identifier (DID) and the encryption key (DKEY) of the target controlled device, so that the controller enters the addition mode.

[0150] Also, the APP of the control terminal can send a request to add a target controlled device with an identifier of the target controlled device to the controller, and the controller can obtain the encryption key (DKEY) of the target controlled device from the SDPDS device based on the identifier of the target controlled device.

[0151] After the controller obtains the encryption key (DKEY) of the target controlled device, the user pairs the target controlled device and sends test report data to the controller according to the method provided in the user manual. The data is encrypted with the encryption key, and the controller decrypts the test status data using the encryption key (DKEY) from the SDPDS device. If the decryption is successful, the target controlled device passes the identity authentication, and a report indicating that the identity authentication has passed is returned to the SDPDS device. The SDPDS device determines the registration information of the target controlled device including the UI tool, all SDPDEFs supported on the target controlled device, and the SDP corresponding to the controller according to the identifier (DID) of the target controlled device. Then, the UI tool, SN, and preset name are sent to the control terminal via the controller or the SDPDS.

[0152] The controller sends at least one polling request to the device under control. Here, the polling request is used to fetch the first status report based on the device information under control registered in the SDPDS. Next, the target device under control returns the first status report encoded based on the SDPDEF to the controller.

[0153] For example, the returned first status report is as follows: JPEG2025519085000030.jpg43170

[0154] The controller analyzes the encoding / decoding tool from the above status report. Specifically, the controller analyzes the corresponding encoding / decoding tool (specifically, the decoding tool) in the SDPDEF of the SDP based on the SDPID and SDPDEFID (class, id) in the first status report, and uses the target decoding tool to decode the first status report (specifically, the value of the first status report) to obtain the second status report. The second status report is as follows: JPEG2025519085000031.jpg51170

[0155] Next, the controller sends the second status report to the control terminal. Thereby, the control terminal uses the UI tool to render the user interface created by the developer of the target device under control and updates the status of the target device under control based on the second status report.

[0156] After that, when the user controls the target device under control, the controller determines the SDPID of the first control command generated by the corresponding device user interface in the control terminal, and the first control command correspondingly has the SDPID of the target device under control, the first SDPDEFID (including class and Id), and the first control data.

[0157] For example, the first control command generated by the corresponding device user interface in the control terminal is as follows: JPEG2025519085000032.jpg71170

[0158] The controller analyzes the encoding / decoding tool from the above control data. Specifically, the controller analyzes the corresponding encoding / decoding tool (specifically, the encoding tool) in the SDPDEF of the SDP based on the SDPID and SDPDEFID (class, id) in the first control instruction, and encodes the first control instruction (specifically, the value of the first control instruction) using the target encoding tool to obtain a second control instruction. That is: JPEG2025519085000033.jpg43170

[0159] Next, the controller sends the second control instruction to the target controlled device, whereby the target controlled device executes the second control instruction.

[0160] Referring to FIG. 15, FIG. 15 is a structural schematic diagram of a communication device provided in an embodiment of the present disclosure. The SDP of the controlled device is created in advance. The SDP includes at least one of an SDPID and SDPDEF information defined and registered by the developer of the controlled device. Corresponding to each SDPDEF information in the SDP, a decoding / encoding tool, an SDPDEFID, and a UI tool used at the control terminal are included. The method includes a determination module 1501, a reception module 1502, an encoding / decoding module 1503, and a transmission module 1504. The decision module 1501 is configured to analyze the SDPID sent by the paired controlled device after passing the identity authentication. Using the obtained SDPID, the controller then obtains the corresponding SDP and SDPDEF information from the SDPDS device in order to analyze the information necessary for the method of controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPIDs provided by the paired controlled device is at least one, and the corresponding SDP is created by the device developer, or created by the SDPSP from the device developer's input, or created by adding SDPDEF information from the developers of other compatible controlled devices via the SDPSP. The receiving module 1502 is configured to receive a first control command generated by the corresponding controlled device user interface of the control terminal created by the developer of the target controlled device, or generated by the automatic preset conditions from the controller. The first control command includes at least one of the target controlled device ID and the first control data. The encoding / decoding module 1503 is configured to render a first encoding / decoding tool corresponding to the first control command based on the target SDP and SDPDEF information, and encode the first control command based on the first encoding / decoding tool to obtain a second control command. The transmitting module 1504 is configured to transmit the second control command to the target controlled device, whereby the target controlled device executes the second control command.

[0161] In some embodiments, the receiving module 1502 is further configured to receive a first status report transmitted by the target controlled device. The first status report includes at least one of the target controlled device ID, the second SDPID, the second SDPDEFID, and the first status data. The encoding / decoding module is further configured to render a second encoding / decoding tool corresponding to the first status report based on the target SDP and SDPDEF information, and decode the first status report based on the second encoding / decoding tool to obtain a second status report. The sending module is further configured to send the second status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report.

[0162] Referring to FIG. 16, FIG. 16 is a structural schematic diagram of another communication device provided in an embodiment of the present disclosure. As shown in FIG. 16, the device includes the following determination module 1601, receiving module 1602, execution module 1603, and sending module 1604: The determination module 1601 is configured to analyze the registered SDPID and the encapsulation tool. The receiving module 1602 is configured to receive a second control instruction transmitted by a pairing controller that obtains one or more SDPIDs after passing the identity authentication. Using the obtained SDPIDs, the controller then obtains corresponding SDP and SDPDEF information from the SDPDS device to analyze the information necessary for controlling the controlled device and communicating with it. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPIDs provided by the controlled device to be paired is at least one, and the corresponding SDP is created by the device developer, or created by the SDPSP from the device developer's input, or created by adding SDPDEF information from the developer of another compatible controlled device via the SDPSP. The second control instruction includes at least one of the target controlled device ID, the first SDPID, the first SDPDEFID, and the second control data obtained by the controller encoding the first control instruction based on the first corresponding encoding / decoding tool. The execution module 1603 is configured to execute the second control instruction to obtain third state data. The transmitting module 1604 is configured to transmit the third state report obtained by the decapsulation tool to the peer controller. The third state report includes at least one of the target controlled device ID, the third SDPID, the third SDPDEFID, and the third state data. Thereby, the controller analyzes the third encoding / decoding tool corresponding to the third state report based on the target SDP and SDPDEF information, decodes the third state report before transmitting it to the control terminal to obtain a fourth state report, and thereby the control terminal uses the UI tool to render the user interface created by the developer of the target controlled device and updates the state of the target controlled device based on the fourth state report.

[0163] In some embodiments, the receiving module 1602 is further configured to receive a polling request transmitted by the peer controller. The polling request is used to obtain a first status report encoded based on the SDP and SDPDEF information. The first status report includes at least one of a target controlled device ID, a second SDP ID, a second SDPDEF ID, and first status data. The transmitting module 1604 is further configured to transmit the first status report to the peer controller, whereby the controller analyzes a second encoding / decoding tool corresponding to the first status report based on the SDP and SDPDEF information, and decodes the first status report based on the second encoding / decoding tool to obtain a second status report.

[0164] Referring to FIG. 17, FIG. 17 is a structural schematic diagram of another communication device provided in an embodiment of the present disclosure. As shown in FIG. 17, the device includes a receiving module 1701, a rendering module 1702, and a transmitting module 1702. The receiving module 1701 is configured to receive an SDP creation request transmitted by the controlled device developer. The creation request is transmitted by the developer. The rendering module 1702 is configured to generate a creation page or an API, whereby the developer of the target controlled device inputs and defines information based on the creation information. The creation information includes at least one SDPDEF information defined by the developer of the controlled device. Corresponding to each SDPDEF information, a decoding / encoding tool, an SDPDEF ID, and a UI tool used on the control terminal are included. The receiving module 1701 is further configured to receive a registration request transmitted by the controlled device developer. The registration request is transmitted by the developer after inputting the creation information into the creation page on the SDPSP or the provided API. The sending module 1702 is further configured to send a registration request to the SDPDS device, whereby the SDPDS device registers the target creation information and generates an SDP including an SDPID and at least one of the SDPDEF information defined by the developer of the target controlled device, and sends the SDP to the developer via the SDPSP. Referring to FIG. 18, FIG. 18 is a structural schematic diagram of another communication device provided in an embodiment of the present disclosure. As shown in FIG. 18, the device includes a receiving module 1801, a registration module 1802, and a sending module 1803. The receiving module 1801 is configured to receive a registration request sent by the SDPSP. The registration request with creation information includes at least one SDPDEF information defined by the developer of the controlled device, whereby the SDPDS generates an SDP including an SDPID and at least one of the SDPDEF information and sends it back to the developer via the SDPSP. The registration module 1802 is configured to register the target SDP and generate a target SDPID for the target SDP creation information. The sending module 1803 is configured to send the target SDP to the developer of the controlled device.

[0165] In some embodiments, the receiving module 1801 is further configured to receive an acquisition request sent by the controller. The acquisition request includes a target SDP ID. The determination module is further configured to identify the SDP corresponding to the target SDPID. The SDP includes an SDPID and at least one of the SDPDEF information defined and registered by the developer of the controlled device. Corresponding to each SDPDEF information in the SDP, it includes a decoding / encoding tool, an SDPDEFID, and a UI tool. The sending module is configured to send the target SDP to the controller.

[0166] One embodiment of the present disclosure further provides a machine-executable storage medium. The machine-executable storage medium stores machine-executable instructions. When the machine-executable instructions are called and executed by a processor, the machine-executable instructions cause the processor to execute the above-described communication method provided by the embodiments of the present disclosure.

[0167] In some embodiments provided by the present disclosure, it should be understood that the disclosed devices and methods may be implemented in other ways. The above-described device embodiments are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings illustrate the possible system architectures, functions, and operations of devices, methods, and computer program products according to multiple embodiments of the present disclosure. In this regard, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, and the module, program segment, or part of code includes one or more executable instructions configured to implement the specified logical function. Also, in some embodiments, it should be noted that, alternatively, the functions shown in the blocks may be executed in an order different from the order shown in the drawings. For example, two consecutive blocks may be executed substantially in parallel, but may also be executed in the reverse order depending on the related functions. Additionally, each block in the block diagram and / or flowchart, as well as combinations of blocks in the block diagram and / or flowchart, can be realized by a dedicated hardware-based system configured to execute the specified function or action, or by a combination of dedicated hardware and computer instructions.

[0168] Finally, it should be noted that the above various embodiments do not limit the present disclosure, but are only used to explain the technical solutions of the present disclosure. Although the present disclosure has been described in detail with reference to various prior embodiments, those skilled in the art should understand that they can modify the technical solutions described in various prior embodiments, or perform equivalent substitutions for some or all of the technical features therein. These changes or substitutions do not cause the corresponding technical solutions to deviate from the scope of the technical solutions of various embodiments of the present disclosure.

[0169] Industrial Applicability The present disclosure provides a communication method, apparatus, device, and system related to the technical field of communication. During communication between a controlled device and a control terminal, conversion can be performed by a controller. Since the SDP of the controlled device and the SDPID of the SDP are created in advance, the controller can convert all functions corresponding to the SDP into the native execution coding of the controller. If it is necessary to change any function or add any function, it is only necessary to recreate the new SDP and the SDPID of the SDP according to the same process. That is, the functions of all devices can be redefined in an ad hoc manner, and the counterpart of the controller can respond on demand based on exactly the same mechanism. All of these processes can be automatically performed without the user's intervention or awareness. From the user's perspective, they do not need to worry about the FW compatibility with their controller, and all they need to do is add a "different" new controlled device to their system.

Claims

1. A communication method, wherein structured device control / communication protocol information (hereinafter referred to as SDP) of a controlled device is created in advance, and the SDP includes at least one of an SDP identifier (hereinafter referred to as SDPI) and an SDP data encapsulation format description table (hereinafter referred to as SDPDEF) information defined and registered by a developer of the controlled device. Corresponding to each SDPDEF information in the SDP, there are a decode / encode tool, an SDPDEF identifier (hereinafter referred to as SDPDEFI), and a user interface control and display generation tool (hereinafter referred to as UI tool) used in a control terminal. The method includes: After a controller passes identity authentication, it obtains one or more SDPI sent by a paired controlled device. Then, the controller uses the obtained SDPI to obtain corresponding SDP and SDPDEF information from an SDP data storage (hereinafter referred to as SDPS) device in order to analyze information necessary for a method of controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPI provided by the paired controlled device is at least one. The corresponding SDP is created by a device developer, or created by an SDP submission portal interface (hereinafter referred to as SDPSP) from the input of the device developer, or created by adding SDPDEF information from a developer of another compatible controlled device via the SDPSP. An optional user control terminal obtains control information including the assigned name of such a compatible controlled device with a caption from the controller, and corresponding information of a user interface created by a developer with a caption. Thereby, this control terminal can generate an appropriate user interface, generate control data, and analyze a status report between the control terminal and the controlled device via the controller. The controller receives a first control command, and the first control command is generated by a corresponding controlled device user interface in a control terminal created by a developer of the target controlled device, or is generated by an automatic preset condition from the controller, packaged into a corresponding UI tool, and includes at least one of a target controlled device ID and first control data; The controller analyzes a first encoding / decoding tool corresponding to the first control command based on the target SDP and SDPDEF information, decodes the first control command based on the first encoding / decoding tool to obtain a second control command including at least one of a target controlled device ID, a first SDP ID, a first SDPDEF, and second control data, and thereby the controller transmits the second control command to the target controlled device; A communication method characterized by including the above.

2. The controller receives a first status report transmitted by the target controlled device, and the first status report includes at least one of a target controlled device ID, a second SDP ID, a second SDPDEF ID, and first status data, and the first SDP ID and the second SDP ID are the same or the first SDP ID and the second SDP ID are different; The controller analyzes a second encoding / decoding tool corresponding to the first status report based on the target SDP and SDPDEF information, decodes the first status report based on the second encoding / decoding tool to obtain a second status report including at least one of a target controlled device ID and second status data; The controller transmits the second status report to the control terminal, and thereby the control terminal renders a user interface created by a developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report; The method according to claim 1, further characterized by including the above.

3. After passing the identity authentication, the controller acquires one or more SDP IDs transmitted by the paired controlled device. The controller then uses the acquired SDP IDs to obtain corresponding SDP and SDPDEF information from an SDP data storage (hereinafter referred to as SDPS) device in order to analyze the information necessary for the method of controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDP IDs provided by the paired controlled device is at least one. The corresponding SDP is created by the device developer, or is created by an SDP submission portal interface (hereinafter referred to as SDPSP) from the input of the device developer, or is created by adding SDPDEF information from the developer of another compatible controlled device via the SDPSP. The method includes: The controller sends a polling request to the target controlled device, and the polling request is used to fetch the first status report encoded based on the SDP and the SDPDEF information defined and registered by the developer of the target controlled device. The first status report includes at least one of a target controlled device ID, a second SDP ID, a second SDPDEF ID, and second status data. The first SDP ID and the second SDP ID are the same, or the first SDP ID and the second SDP ID are different steps, The controller analyzes a second encoding / decoding tool corresponding to the first status report based on the target SDP and SDPDEF information, and decodes the first status report based on the second encoding / decoding tool to obtain a second status report including at least one of a target controlled device ID and second status data. The controller sends the second status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target controlled device using the UI tool and updates the status of the target controlled device based on the second status report. The method according to any one of claims 1 to 2, further comprising

4. The target controlled device receives a second control command transmitted by a pairing controller that obtains one or more SDP IDs after passing identity authentication, and the controller then uses the obtained SDP IDs to control the controlled device and analyze information necessary for communicating with it. To do so, the controller obtains corresponding SDP and SDPDEF information from an SDPS device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDP IDs provided by the paired controlled device is at least one. The corresponding SDP is created by a device developer, or is created by SDPS based on the input of the device developer, or is created by adding SDPDEF information from the developer of another compatible controlled device via the SDPS. The second control command includes at least one of a target controlled device ID, a first SDP ID, a first SDPDEF ID, and second control data obtained by the controller encoding a first control command based on a first corresponding encoding / decoding tool. The target controlled device executes the second control command and reports third state data reflecting the execution result. The target controlled device transmits the third state report obtained by a decapsulation tool to the peer controller. The third state report includes at least one of a target controlled device ID, a third SDP ID, a third SDPDEF ID, and third state data. Thereby, the controller analyzes a third encoding / decoding tool corresponding to the third state report based on the target SDP and SDPDEF information, decodes the third state report to obtain a fourth state report. The first SDP ID, the second SDP ID, and the third SDP ID are the same, or the first SDP ID, the second SDP ID, and the third SDP ID are different. The controller transmits a fourth status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target device to be controlled using the UI tool and updates the status of the target device to be controlled based on the fourth status report; A communication method including the above. **Claim 5** The target device to be controlled receives a polling request transmitted by the other controller, and the polling request is used to fetch the first status report encoded based on SDP and SDPDEF information, and the first status report includes at least one of a target device to be controlled ID, a second SDP ID, a second SDPDEF ID, and first status data; The target device to be controlled transmits a first status report to the other controller, whereby the controller analyzes a second encoding / decoding tool corresponding to the first status report based on the SDP and SDPDEF information, decodes the first status report based on the second encoding / decoding tool to obtain a second status report, the second status report includes at least one of a target device to be controlled ID and second status data, and the first SDPI D, the second SDPI D, and the third SDPI D are the same or the first SDPI D, the second SDPI D, and the third SDPI D are different; The controller transmits a second status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target device to be controlled using the UI tool and updates the status of the target device to be controlled based on the second status report; The method according to claim 4, further comprising the above. **Claim 6** SDPSP receives an SDP creation request transmitted by the developer of the device to be controlled, and the creation request is transmitted by the developer when compatible or appropriate SDPDEF information for the target device to be controlled cannot be found; The SDPSP provides a creation page or an application programming interface (hereinafter referred to as an API), whereby the developer of the target controlled device defines and creates information from the input based on the creation information, and the creation information includes at least one SDDEF information defined by the developer of the controlled device. Corresponding to each SDDEF information, a step including a decode / encode tool, an SDDEFID, and a UI tool used on the control terminal, The SDPSP receives an SD registration request sent by the developer of the controlled device, and the registration request is sent by the developer after inputting the creation information into a creation page on the SDPSP or the provided API. The SDPSP sends the SD registration request to the SDDS device, whereby the SDDS device registers the target creation information and generates an SD including an SDID and at least one of the SDDEF information defined by the developer of the target controlled device, and sends the SD to the developer via the SDPSP. The SDPSP and the SDDS device are arranged on the same device, or the SDPSP and the SDDS device are arranged on different devices. A communication method including.

7. A communication method, wherein the SDDS device receives an SD registration request sent by the SDPSP, and the registration request with the creation information includes at least one SDDEF information defined by the developer of the controlled device. Thereby, the SDDS generates an SD including an SDID and at least one of the SDDEF information, and sends it back to the developer via the SDPSP. The SDPSP and the SDDS device are arranged on the same device, or the SDPSP and the SDDS device are arranged on different devices.

8. The step in which the SDDS device receives a request sent by a controller, and the request includes one or more SDIDs sent by a paired controlled device after passing identity authentication. The step in which the SDPS device identifies an SDP data package corresponding to a target SDPIID and transmits it to the controller, where the SDP data package includes at least one of an SDPIID and SDPDEF information defined and registered by a developer of a device to be controlled, and corresponding to each SDPDEF information in the SDP, includes a decoding / encoding tool, an SDPDEFID, and a UI tool. The communication method according to claim 7, further comprising this.

9. A controller including a transceiver, a memory, and a processor, where the memory stores a computer program executable on the processor, and when the computer program is executed, the processor implements the steps of the method according to any one of claims 1 to 3.

10. A device to be controlled including a transceiver, a memory, and a processor, where the memory stores a computer program executable on the processor, and when the computer program is executed, the processor implements the steps of the method according to any one of claims 4 to 5.

11. An SDPSP including a transceiver, a memory, and a processor, where the memory stores a computer program executable on the processor, and when the computer program is executed, the processor implements the steps of the method according to claim 6.

12. An SDPS device including a transceiver, a memory, and a processor, where the memory stores a computer program executable on the processor, and when the computer program is executed, the processor implements the steps of the method according to any one of claims 7 to 8.

13. A communication system including the controller according to claim 9, the device to be controlled according to claim 10, the SDPSP according to claim 11, and the SDPS device according to claim 12.

14. A communication method, wherein the SDP of the controlled device is created in advance, and the SDP includes at least one of an SDPI and SDDEF information defined and registered by the developer of the controlled device. Corresponding to each SDDEF information in the SDP, it includes a decode / encode tool, an SDDEFID, and a UI tool used in the control terminal. The method includes a determination module, a reception module, an encode / decode module, and a transmission module. The determination module is configured to analyze the SDPI sent by the paired controlled device after passing the identity authentication. Then, the controller uses the obtained SDPI to obtain the corresponding SDP and SDDEF information from the SDDS device in order to analyze the information necessary for the method of controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of the SDPI provided by the paired controlled device is at least one. The corresponding SDP is created by the device developer, or created by the SDSP based on the input of the device developer, or created by adding SDDEF information from the developer of another compatible controlled device via the SDSP. The reception module is configured to receive a first control command generated by the corresponding controlled device user interface of the control terminal created by the developer of the target controlled device, or generated by the automatic preset condition from the controller. The first control command includes at least one of a target controlled device ID and first control data. The encode / decode module is configured to render a first encode / decode tool corresponding to the first control command based on the target SDP and SDDEF information, and encode the first control command based on the first encode / decode tool to obtain a second control command. The transmission module is configured to transmit the second control command to the target controlled device, whereby the target controlled device executes the second control command. This is the characteristic of the communication method.

15. The receiving module is further configured to receive a first status report transmitted by the target device to be controlled, and the first status report includes at least one of a target device to be controlled ID, a second SDPI ID, a second SDPDEF ID, and first status data. The encoding / decoding module is further configured to render a second encoding / decoding tool corresponding to the first status report based on the target SDP and SDPDEF information, and decode the first status report based on the second encoding / decoding tool to obtain a second status report. The transmitting module is further configured to transmit the second status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target device to be controlled using the UI tool, and updates the status of the target device to be controlled based on the second status report. The apparatus according to claim 14, characterized in that.

16. The transmitting module is further configured to transmit a polling request to the target device to be controlled, and the polling request is used to fetch the first status report encoded based on the SDP and the SDPDEF information defined and registered by the developer of the target device to be controlled. The first status report includes at least one of a target device to be controlled ID, a second SDPI ID, a second SDPDEF ID, and second status data. The encoding / decoding module is further configured to analyze based on the target SDP and SDPDEF information from the target device to be controlled, and decode the first status report based on the second encoding / decoding tool to obtain a second status report. The transmitting module is further configured to transmit a second status report to the control terminal, whereby the control terminal renders a user interface created by the developer of the target device to be controlled using the UI tool, and updates the status of the target device to be controlled based on the second status report. The apparatus according to any one of claims 14 to 15, characterized in that.

17. A communication device, comprising a determination module, a receiving module, an execution module, and a transmitting module. The determination module is configured to analyze the registered SDPI D and the encapsulation tool. The receiving module is configured to receive a second control instruction transmitted by a pairing controller that obtains one or more SDPI Ds after passing identity authentication. The controller then uses the obtained SDPI D to obtain corresponding SDP and SDPDEF information from the SDPS device to analyze the information necessary for controlling and communicating with the controlled device. Up to this stage, this controlled device is interoperable with the controller and is known as a compatible controlled device. The number of SDPI Ds provided by the paired controlled device is at least one. The corresponding SDP is created by the device developer, or is created by the SDSP based on the input of the device developer, or is created by adding SDPDEF information from the developer of another compatible controlled device via the SDSP. The second control instruction includes at least one of the target controlled device ID, the first SDPI D, the first SDPDEF ID, and the second control data obtained by the controller encoding the first control instruction based on the first corresponding encoding / decoding tool. The execution module is configured to execute the second control instruction to obtain third state data. The transmitting module is configured to transmit the third state report obtained by the decapsulation tool to the peer controller. The third state report includes at least one of the target controlled device ID, the third SDPI D, the third SDPDEF ID, and the third state data. Thereby, the controller analyzes the third encoding / decoding tool corresponding to the third state report based on the target SDP and SDPDEF information, decodes the third state report to obtain a fourth state report before transmitting it to the control terminal. Thereby, the control terminal renders the user interface created by the developer of the target controlled device using the UI tool and updates the state of the target controlled device based on the fourth state report. A communication device characterized by this.

18. The receiving module is further configured to receive a polling request transmitted by the counterpart controller, the polling request being used to obtain the first status report encoded based on the SDP and SDPDEF information, the first status report including at least one of a target controlled device ID, a second SDPIID, a second SDPDEFID, and first status data. The transmitting module is further configured to transmit a first status report to the counterpart controller, whereby the controller analyzes a second encoding / decoding tool corresponding to the first status report based on the SDP and SDPDEF information, and decodes the first status report based on the second encoding / decoding tool to obtain a second status report. The apparatus according to claim 17, characterized in that.

19. A communication device, comprising a receiving module, a rendering module, and a transmitting module. The receiving module is configured to receive an SDP creation request transmitted by a controlled device developer, the creation request being transmitted by the developer. The rendering module is configured to generate a creation page or API, whereby a developer of a target controlled device inputs and defines the information based on the creation information, the creation information including at least one SDPDEF information defined by the developer of the controlled device, and corresponding to each SDPDEF information, including a decoding / encoding tool, an SDPDEFID, and a UI tool used in a control terminal. The receiving module is further configured to receive a registration request transmitted by the controlled device developer, the registration request being transmitted by the developer after inputting the creation information into a creation page on the SDPSP or the provided API. The transmitting module is further configured to transmit the registration request to the SDPDS device, whereby the SDPDS device registers the target creation information, generates an SDP including an SDPIID and at least one of the SDPDEF information defined by the developer of the target controlled device, and transmits the SDP to the developer via the SDPSP. A communication device characterized by that.

20. A communication device, comprising a receiving module, a registration module, and a transmitting module, wherein the receiving module is configured to receive a registration request transmitted by an SDPSP, the registration request having creation information includes at least one SDDEF information defined by a developer of a controlled device, whereby, an SDPSD generates an SDP including an SDID and at least one of the SDDEF information, and sends it back to the developer via the SDPSP, the registration module is configured to register the target SDP and generate a target SDID of target SDP creation information, the transmitting module is configured to transmit the target SDP to the developer of the controlled device, and a communication device characterized by this.

21. the receiving module is further configured to receive a request request transmitted by a controller, the request request includes the target SDID, the determination module is further configured to identify an SDP corresponding to the target SDID, the SDP includes an SDID and at least one of the SDDEF information defined and registered by the developer of the controlled device, and corresponding to each SDDEF information in the SDP, includes a decode / encode tool, an SDDEFID, and a UI tool, the transmitting module is configured to transmit the target SDP to the controller, and the device according to claim 20, characterized by this.

Images