Protocol access method, communication method, development equipment, gateway and storage medium

By developing and pushing Connector drivers, the problem of insufficient scalability of the gateway communication protocol is solved, and the gateway interacts with Mesh devices of different communication protocols is realized, reducing communication limitations.

CN115442913BActive Publication Date: 2024-11-12ZHEJIANG MAOJING ARTIFICIAL INTELLIGENCE TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210972647.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-08-15
Publication Date
2024-11-12
Estimated Expiration
2042-08-15

AI Technical Summary

Technical Problem

The existing gateway agrees that communication protocols limit their scalability during production, resulting in the inability to interact with Mesh devices with new standard or non-standard communication protocols, resulting in communication limitations.

Method used

The Connector SDK is obtained through the development device, and the Connector driver corresponding to the communication protocol used by the Mesh device is developed and uploaded to the cloud server. The cloud server is pushed to the gateway. The gateway loads and registers the Connector driver to interact with Mesh devices with different communication protocols.

Benefits of technology

The gateway's communication protocol dynamic expansion and update is realized, reducing communication limitations, allowing the gateway to support multiple communication protocols, and improving the scalability of the communication protocol.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115442913B_ABST
    Figure CN115442913B_ABST
Patent Text Reader

Abstract

The embodiment of the present application provides a protocol access method, a communication method, a development device, a gateway and a storage medium, wherein the protocol access method includes: obtaining a Connector SDK from a cloud server, and registering a Mesh device that needs to develop a Connector driver to the cloud server; wherein the Connector SDK defines an SDK specification for developing a Connector driver; based on the SDK specification and the development requirements corresponding to the communication protocol used by the Mesh device, developing a Connector driver corresponding to the communication protocol; the communication protocol used by the Mesh device is a newly added communication protocol of the gateway; uploading the Connector driver to the cloud server so that after the cloud server associates the Connector driver with the registered Mesh device, the cloud server pushes the Connector driver to the gateway; wherein the gateway loaded with the Connector driver uses the Connector driver to communicate with the Mesh device using the corresponding communication protocol. The embodiment of the present application can improve the communication protocol scalability of the gateway and reduce the communication limitations of the gateway.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and specifically to a protocol access method, a communication method, a development device, a gateway, and a storage medium. Background Art

[0002] Mesh (wireless mesh) network is a mesh network used for communication between devices, such as Bluetooth Mesh network. As the scale of Mesh network expands, the number of Mesh devices (such as Bluetooth Mesh devices) in the Mesh network increases accordingly. Due to the intelligent management requirements of Mesh devices, the gateway can be used as an intelligent central control device to intervene in the Mesh network to manage Mesh devices.

[0003] The premise for the gateway to manage Mesh devices is that the gateway can interact with Mesh devices based on the communication protocol of the Mesh devices; therefore, how to provide the gateway with an access solution for the communication protocol to improve the scalability of the gateway's communication protocol, thereby ensuring the smooth interaction between the gateway and the Mesh devices, has become a technical problem that technical personnel in this field urgently need to solve. Summary of the invention

[0004] In view of this, the embodiments of the present application provide a protocol access method, a communication method, a development device, a gateway and a storage medium, so that the gateway can expand the communication protocol and improve the scalability of the communication protocol of the gateway.

[0005] To achieve the above objectives, the embodiments of the present application provide the following technical solutions.

[0006] In a first aspect, an embodiment of the present application provides a protocol access method, which is applied to a development device, including:

[0007] Obtain the Connector SDK from the cloud server and register the Mesh device for which the Connector driver needs to be developed with the cloud server; wherein the Connector SDK defines the SDK specification for developing the Connector driver;

[0008] Based on the SDK specification and the development requirements corresponding to the communication protocol used by the Mesh device, develop a Connector driver corresponding to the communication protocol; the communication protocol used by the Mesh device is a newly added communication protocol of the gateway;

[0009] The Connector driver is uploaded to the cloud server so that the cloud server associates the Connector driver with the registered Mesh device, and then the cloud server pushes the Connector driver to the gateway; wherein the gateway loaded with the Connector driver uses the Connector driver to communicate with the Mesh device using the corresponding communication protocol.

[0010] In a second aspect, an embodiment of the present application provides a communication method, applied to a gateway, including:

[0011] Obtaining the Connector driver corresponding to the communication protocol used by the Mesh device from the cloud server; the communication protocol used by the Mesh device is a newly added communication protocol of the gateway, and the Connector driver is developed based on the SDK specification of the Connector SDK and the development requirements of the communication protocol;

[0012] Load the Connector driver and register the Connector driver with the Connector manager;

[0013] The Connector is used to drive the unified interface set by the scheduling gateway to communicate with Mesh devices using the corresponding communication protocol.

[0014] In a third aspect, an embodiment of the present application provides a development device comprising at least one memory and at least one processor, wherein the memory stores one or more computer executable instructions, and the processor calls the one or more computer executable instructions to execute the protocol access method as described in the first aspect above.

[0015] In a fourth aspect, an embodiment of the present application provides a gateway, comprising at least one memory and at least one processor, wherein the memory stores one or more computer executable instructions, and the processor calls the one or more computer executable instructions to execute the communication method as described in the second aspect above.

[0016] In a fifth aspect, an embodiment of the present application provides a storage medium, which stores one or more computer-executable instructions. When the one or more computer-executable instructions are executed, the protocol access method described in the first aspect above, or the communication method described in the second aspect above is implemented.

[0017] In a sixth aspect, an embodiment of the present application provides a computer program, which, when executed, implements the protocol access method as described in the first aspect above, or the communication method as described in the second aspect above.

[0018] In the embodiment of the present application, when the communication protocol used by the Mesh device is a newly added communication protocol of the gateway, the development device can develop a Connector driver corresponding to the communication protocol for the Mesh device. When developing the Connector driver corresponding to the communication protocol for the Mesh device, the development device can obtain the Connector SDK from the cloud server and register the Mesh device that needs to develop the Connector driver to the cloud server, wherein the Connector SDK defines an SDK specification for developing the Connector driver; thus, the development device can develop the Connector driver corresponding to the communication protocol based on the SDK specification of the Connector SDK and the development requirements corresponding to the communication protocol used by the Mesh device, so that for Mesh devices using different communication protocols, the embodiment of the present application can develop corresponding different Connector drivers to achieve dynamic development of Connector drivers for different communication protocols. Furthermore, the Connector driver developed by the development device can be uploaded to the cloud server, so that after the cloud server associates the Connector driver with the registered Mesh device, the cloud server can push the Connector driver to the gateway; after the gateway loads the Connector driver, the Connector driver can be used to schedule a unified interface to communicate with the Mesh device using the corresponding communication protocol, thereby achieving the effect of the gateway accessing the communication protocol.

[0019] It can be seen that after the development device develops the Connector drivers corresponding to different communication protocols, the gateway can obtain the Connector drivers corresponding to different communication protocols through the push of the cloud server, and then the gateway can load the Connector drivers corresponding to different communication protocols to achieve access to different communication protocols; therefore, the gateway can realize dynamic expansion and update of the Connector driver based on the Connector driver pushed by the cloud server during use, so as to realize dynamic expansion and update of the communication protocol supported by the gateway when the communication protocol used by the Mesh device is a new communication protocol of the gateway, so that the gateway is not limited to the communication protocol agreed upon when the gateway is produced, so as to improve the scalability of the communication protocol of the gateway and reduce the communication limitations of the gateway. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0021] Figure 1 This is an example diagram of a Mesh network.

[0022] Figure 2 A flow chart of a method for developing a Connector driver provided in an embodiment of the present application.

[0023] Figure 3 A flowchart of a communication method provided in an embodiment of the present application.

[0024] Figure 4 An example diagram of a hierarchical design framework for a gateway provided in an embodiment of the present application.

[0025] Figure 5 An example diagram for implementing protocol access provided in an embodiment of the present application.

[0026] Figure 6 A block diagram of a communication device provided in an embodiment of the present application.

[0027] Figure 7 A block diagram of a gateway.

[0028] Figure 8 A block diagram of a protocol access device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0030] Figure 1 An example diagram of a Mesh network is shown as follows: Figure 1 As shown, the Mesh network may include: multiple node devices 101 that have been configured, and the node devices may be regarded as Mesh devices that have joined the Mesh network (for example, Bluetooth Mesh devices that have joined the Bluetooth Mesh network). Figure 1 As shown, the gateway 102 serves as an intelligent central control device of the Mesh network. In addition to configuring and controlling the provisioned node devices, it can also add unprovisioned devices (Unprovisioned Device) 103 to the Mesh network. The unprovisioned devices can be regarded as Mesh devices that have not yet been added to the Mesh network.

[0031] It can be seen that the gateway manages Mesh devices mainly in the following aspects: the gateway interacts with the networked node devices to configure, control and manage the node devices; the gateway discovers unnetworked devices and interacts with them to network the unnetworked devices into the Mesh network. Furthermore, the gateway can also serve as a springboard for the node devices to connect to the Internet to achieve remote control of the node devices. In one example, the gateway can be, for example, a smart speaker that can connect to the Internet, a multi-mode gateway, etc.

[0032] The premise for the gateway to interact with Mesh devices is that the gateway supports the communication protocol of Mesh devices. One way to access the communication protocol for the gateway is to agree on the communication protocol supported by the gateway in advance when the gateway is produced and set the corresponding protocol specifications for the gateway; this way of agreeing on the communication protocol for the gateway in advance when the gateway is produced makes the communication protocol that the gateway can support limited when the gateway is produced, resulting in the inability to expand the communication protocol when the gateway is used, and then the gateway can only communicate and interact with Mesh devices with limited communication protocols, resulting in greater communication limitations for the gateway.

[0033] For example, the mainstream standard communication protocols of Mesh devices include: WiFi communication protocol, Bluetooth communication protocol, ZigBee communication protocol, etc.; among them, the Bluetooth communication protocol can be further divided into classic Bluetooth communication protocol, BLE (BluetoothLow Energy)-GATT (Generic Attribute Profile) communication protocol, BLE-Mesh communication protocol, etc. In order to enable the gateway to support the mainstream standard communication protocols of Mesh devices, standard communication protocols such as WiFi communication protocol, Bluetooth communication protocol, ZigBee communication protocol, etc. can be agreed upon for the gateway in advance when the gateway is produced. This method allows the gateway to support the pre-agreed standard communication protocols and interact with mainstream Mesh devices. However, when new standard communication protocols appear or Mesh devices use non-standard communication protocols, the gateway will not be able to interact with Mesh devices using new standard communication protocols or non-standard communication protocols, resulting in limitations in the communication of the gateway.

[0034] Based on this, the embodiment of the present application provides an improvement scheme so that when the gateway is in use (for example, when the gateway communicates with a Mesh device), it can support dynamic extended communication protocols, improve the scalability of the gateway's communication protocols, and reduce the communication limitations of the gateway.

[0035] In the embodiment of the present application, the development device can develop a Connector driver corresponding to the communication protocol used by the Mesh device based on the communication protocol used by the Mesh device. The Connector driver can be considered as the device driver corresponding to the communication protocol used by the Mesh device; as an optional implementation, the communication protocol used by the Mesh device can be a newly added communication protocol of the gateway (such as a new standard communication protocol or a non-standard communication protocol used by the Mesh device). After the development device develops the Connector driver, the development device can upload the Connector driver to the cloud server; then, the cloud server can push the Connector driver to the gateway. After the gateway loads the Connector driver, it can use the Connector driver to interact with the Mesh device using the corresponding communication protocol.

[0036] In the embodiment of the present application, the development device develops the Connector driver corresponding to the communication protocol used by the Mesh device, and pushes the Connector driver to the gateway through the cloud server, so that the gateway can interact with the Mesh device using the corresponding communication protocol through the loaded Connector driver, and realizes the gateway accessing the communication protocol of the Mesh device by loading the Connector driver pushed by the cloud server. It can be seen that since the Connector driver is developed by the development device and pushed to the gateway by the cloud server, the gateway can dynamically expand different communication protocols based on different Connector drivers developed by the development device and pushed by the cloud server when in use, avoiding the problems caused by agreeing on the communication protocol for the gateway in advance when the gateway is produced, and can improve the scalability of the communication protocol of the gateway, so that the gateway can interact with Mesh devices using different communication protocols through different Connector drivers, reducing the communication limitations of the gateway.

[0037] Based on the above ideas, in the embodiment of the present application, the development device can develop the corresponding Connector driver based on the communication protocol used by the Mesh device (the communication protocol used by the Mesh device can be the newly added communication protocol of the gateway), and push the Connector driver to the gateway to achieve the protocol access of the gateway. As an optional implementation, Figure 2The exemplary flow chart of the optional method for developing a Connector driver provided in an embodiment of the present application to implement protocol access to a gateway is shown. The method flow can be implemented by a development device and a cloud server; in one example, the development device can be an electronic device used by developers such as ISVs (Independent Software Vendors) or third-party manufacturers that produce Mesh devices to develop drivers; in one example, the cloud server can be a cloud service device that can communicate with the gateway over the Internet. Optionally, the cloud server can be a cloud service platform that provides Mesh management services, such as a cloud computing platform that provides intelligent interconnection services for devices such as smart homes and smart offices, an IoT (Internet of Things) cloud platform, etc.

[0038] Reference Figure 2 As shown, the method flow may include the following steps.

[0039] In step S210, the development device requests a Connector SDK (Software Development Kit) from the cloud server.

[0040] In step S211, the cloud server feeds back the Connector SDK to the development device.

[0041] Connector SDK can be an SDK for developing Connector drivers, and is a collection of documents, examples, and tools that assist in developing Connector drivers. In some embodiments, Connector SDK can define SDK specifications, and a unified interface can be abstracted through the SDK specifications. The unified interface can be used to unify the communication protocols for accessing Mesh devices, thereby adapting to different communication protocols of Mesh devices. As an optional implementation, the embodiment of the present application can abstract the unified interface based on the object model of the Mesh device through the SDK specification of the Connector SDK; thus, through the unified interface, the embodiment of the present application can support operations such as setting properties of Mesh devices and reporting device status. The object model of the Mesh device can be an abstraction of the capabilities of the Mesh device, including properties, services, events, etc. corresponding to the Mesh device.

[0042] When the development device needs to develop the corresponding Connector driver for the communication protocol used by the Mesh device, the development device can obtain the Connector SDK for developing the Connector driver from the cloud server, so that the development device can develop the Connector driver corresponding to the communication protocol based on the unified interface abstracted by the SDK specification. Optionally, the development device can develop the Connector driver corresponding to the communication protocol based on the unified interface and the development requirements of the communication protocol.

[0043] In step S212, the development device sends a registration request for the Mesh device to the cloud server.

[0044] In step S213, the cloud server registers the Mesh device.

[0045] The development device can register the Mesh device that needs to develop the Connector driver with the cloud server as a product. In some embodiments, the development device can determine the registration information of the Mesh device and send a registration request carrying the registration information of the Mesh device to the cloud server, so that the cloud server can register the Mesh device based on the registration information of the Mesh device.

[0046] As an optional implementation, the registration information of the Mesh device may include the ternary information of the Mesh device, the communication protocol used, etc. The ternary information of the Mesh device may be the identity information for uniquely identifying the Mesh device, including the PID (Product ID) of the Mesh device, the product identification code, the MAC (Media Access Control) address, the Device Secret (device unique key), etc.

[0047] In one example, the development device can send a registration request carrying the registration information of the Mesh device, such as the triplet information and the communication protocol, to the cloud server, so that the cloud server can register the Mesh device and set a registration record for the Mesh device. The cloud server can indicate the triplet information, the communication protocol, and other information of the Mesh device in the registration record. In a further optional implementation, for the Mesh device registered by the cloud server, the cloud server can provide a device page, and the device page can introduce the relevant information of the registered Mesh device.

[0048] As an optional implementation, step S210 and step S211, as well as step S212 and step S213 may not distinguish the order of execution; for example, the embodiment of the present application may first execute step S210 and step S211, and then execute step S212 and step S213. The embodiment of the present application may also first execute step S212 and step S213, and then execute step S210 and step S211; of course, the embodiment of the present application may also support the simultaneous execution of step S210 and step S211, as well as step S212 and step S213.

[0049] In step S214, the development device uses the Connector SDK to develop a Connector driver corresponding to the communication protocol of the Mesh device.

[0050] After the development device obtains the Connector SDK and registers the Mesh device with the cloud server, it can use the Connector SDK and the communication protocol used by the Mesh device to develop a Connector driver corresponding to the communication protocol of the Mesh device. As an optional implementation, based on the unified interface abstracted by the SDK specification of the Connector SDK, the development device can develop a corresponding Connector driver according to the development requirements of the communication protocol of the Mesh device; that is, based on the unified interface abstracted by the SDK specification, the development device can develop a Connector driver corresponding to the communication protocol based on the development requirements of the communication protocol, so that the Connector driver adapts to the communication protocol of the Mesh device based on the unified interface.

[0051] In a further optional implementation, the SDK specification of the Connector SDK can define development documents and development code samples (Sample Code) for developing Connector drivers; thus, when developing a Connector driver, the development device can write driver code corresponding to the development requirements of the communication protocol of the Mesh device based on the unified interface abstracted by the SDK specification, using the development documents and development code samples of the Connector driver, and then develop the corresponding Connector driver.

[0052] It should be noted that the communication interaction between the gateway and the Mesh device requires the support of the communication protocol, and a certain type of communication protocol may rely on multiple layered protocols (for example, the WiFi communication protocol relies on CoAP and other protocols at the application layer). Therefore, the development requirements of the communication protocol can indicate the requirements such as the multiple layered protocols that the communication protocol relies on.

[0053] As an optional implementation, based on the development documents and development code samples defined by the SDK specification, the development device can write the protocol codes of multiple layered protocols that the communication protocol depends on based on the unified interface abstracted by the SDK specification, thereby developing the Connector driver corresponding to the communication protocol according to the protocol codes of the multiple layered protocols written. In one example, for different types of communication protocols, the SDK specification can define the development code samples of each layered protocol of the communication protocol, so that when the development device develops a Connector driver for a certain type of communication protocol, it can call the development code samples of each layered protocol of the type of communication protocol; based on the development documents defined by the SDK specification, the development device can write the protocol code of each layered protocol for the type of communication protocol; and then adapt the protocol code of each layered protocol written to the unified interface abstracted by the SDK specification to develop the Connector driver for the type of communication protocol.

[0054] It should be noted that different types of communication protocols (e.g., different types of standard communication protocols, different types of non-standard communication protocols, etc.) may have different development requirements. For example, different types of communication protocols rely on different layered protocols. Therefore, the embodiments of the present application may set the development requirements of the communication protocol according to actual conditions, and the embodiments of the present application do not limit the specific content of the development requirements of the communication protocol. In addition, the development documents and development code samples defined by the SDK specification can be set according to actual conditions, and the embodiments of the present application do not limit them. It is understandable that when the SDK specification defines the development documents and development code samples, and the SDK specification abstracts a unified interface, based on the development requirements specified by the communication protocol, the developer has the ability to write the corresponding driver.

[0055] In step S215 , the development device uploads the developed Connector driver to the cloud server.

[0056] In step S216, the cloud server associates the Connector driver with the registered Mesh device.

[0057] After developing the Connector driver, the development device can upload the Connector driver to the cloud server to request the cloud server to associate the Connector driver with the registered Mesh device, so that the cloud server can provide the gateway with the Connector driver corresponding to the communication protocol of the Mesh device. In some further embodiments, if the cloud server provides a device page for the registered Mesh device, the development device can upload the Connector driver on the device page to upload the developed Connector driver to the cloud server; so that the cloud server can associate the Mesh device corresponding to the device page with the uploaded Connector driver based on the Connector driver uploaded on the device page, so as to associate the Connector driver with the registered Mesh device. In a further optional implementation, in addition to introducing basic information such as registration information of the registered Mesh device, the device page can further indicate the Connector driver corresponding to the communication protocol of the Mesh device.

[0058] The embodiment of the present application can provide a Connector SDK for developing Connector drivers, so that when developers need to develop corresponding Connector drivers for the communication protocol used by Mesh devices, they can use the development device to obtain the Connector SDK and register the Mesh device to the cloud server; further, the developer can use the development device to develop the corresponding Connector driver based on the SDK specification of the Connector SDK and the development requirements of the communication protocol; the development device can upload the Connector driver to the cloud server and associate it with the corresponding Mesh device registered with the cloud server. It can be seen that the embodiment of the present application can develop a Connector driver for the communication protocol used by the Mesh device through the interaction between the development device and the cloud server, so that for Mesh devices using different communication protocols, the embodiment of the present application can develop corresponding different Connector drivers, realize dynamic development of Connector drivers for different communication protocols, and provide a technical basis for the gateway to support dynamic expansion of communication protocols.

[0059] Furthermore, after obtaining the Connector driver developed by the developer for the Mesh device, the cloud server can push the Connector driver to the gateway, so that the gateway uses the Connector driver to support the corresponding communication protocol and communicate with the Mesh device using the communication protocol.

[0060] That is to say, in the embodiment of the present application, when the communication protocol used by the Mesh device is a new communication protocol of the gateway, the development device can develop a Connector driver corresponding to the communication protocol for the Mesh device. When developing the Connector driver corresponding to the communication protocol for the Mesh device, the development device can obtain the Connector SDK from the cloud server, and register the Mesh device for which the Connector driver needs to be developed to the cloud server, wherein the Connector SDK defines an SDK specification for developing the Connector driver; thereby, the development device can develop the Connector driver corresponding to the communication protocol based on the SDK specification of the Connector SDK and the development requirements corresponding to the communication protocol used by the Mesh device. For Mesh devices using different communication protocols, the embodiment of the present application can develop corresponding different Connector drivers to realize dynamic development of Connector drivers for different communication protocols. Furthermore, the Connector driver developed by the development device can be uploaded to the cloud server, so that after the cloud server associates the Connector driver with the registered Mesh device, the cloud server can push the Connector driver to the gateway; after the gateway loads the Connector driver, the Connector driver can be used to schedule a unified interface to communicate with the Mesh device using the corresponding communication protocol, thereby achieving the effect of gateway access to the communication protocol.

[0061] It can be seen that after the development device develops the Connector drivers corresponding to different communication protocols, the gateway can obtain the Connector drivers corresponding to different communication protocols through the push of the cloud server, and then the gateway can load the Connector drivers corresponding to different communication protocols to achieve access to different communication protocols; therefore, the gateway can realize dynamic expansion and update of the Connector driver based on the Connector driver pushed by the cloud server during use, so as to realize dynamic expansion and update of the communication protocol supported by the gateway when the communication protocol used by the Mesh device is a new communication protocol of the gateway, so that the gateway is not limited to the communication protocol agreed upon when the gateway is produced, so as to improve the scalability of the communication protocol of the gateway and reduce the communication limitations of the gateway.

[0062] As an optional implementation, Figure 3 The optional flow chart of the communication method provided by the embodiment of the present application is shown as an example. In the method flow, the gateway can load the Connector driver corresponding to the communication protocol and communicate with the Mesh device using the communication protocol. The method flow can be implemented by the cloud server, the gateway and the Mesh device, refer to Figure 3 The method flow may include the following steps.

[0063] In step S310, the cloud server pushes the Connector driver to the gateway.

[0064] In step S311, the gateway loads the Connector driver and registers the Connector driver with the Connector manager.

[0065] The cloud server can push the Connector driver corresponding to the communication protocol of the Mesh device to the gateway; thus, the gateway can obtain the Connector driver corresponding to the communication protocol of the Mesh device from the cloud server; further, the gateway can load the obtained Connector driver and register the Connector driver to the Connector manager used to manage the Connector driver.

[0066] It should be noted that different types of communication protocols may correspond to different Connector drivers. Therefore, when the gateway supports multiple different types of communication protocols (for example, multiple different types of standard communication protocols, and / or multiple different types of non-standard communication protocols), the gateway needs to load multiple different Connector drivers; in order to manage the multiple Connector drivers loaded by the gateway, the gateway can set a Connector manager (referred to as Connector Mgr for short) for managing Connector drivers.

[0067] In some embodiments, the gateway may set up a Connector library for storing the Connector drivers loaded by the gateway; the Connector drivers stored in the Connector library may be connected to the Connector manager, so that the Connector manager is responsible for discovering Mesh devices using the Connector drivers and performing management tasks such as data distribution with Mesh devices. Based on this, in an optional implementation of registering the Connector driver to the Connector manager, the embodiment of the present application may store the Connector driver in the Connector library, and set the Connector driver in the Connector library to be connected to the Connector manager. Optionally, the Connector manager can be considered as a driver manager in the form of a software program.

[0068] In step S312, the gateway uses the Connector driver to communicate with the Mesh device using the corresponding communication protocol.

[0069] After the gateway loads the Connector driver and registers the Connector driver with the Connector manager, the gateway can use the Connector driver to access the corresponding communication protocol. In an embodiment of the present application, the gateway can use the Connector driver to communicate with the Mesh device using the corresponding communication protocol to achieve interaction between the gateway and the Mesh device. It should be noted that the embodiment of the present application can implement the use of the Connector driver after the gateway registers the Connector driver with the Connector manager, so that the gateway supports the communication protocol corresponding to the Connector driver and achieves the effect of the gateway accessing the communication protocol; and, the Connector driver is pushed to the gateway by the cloud server, and is not set in advance when the gateway is produced. Therefore, the Connector driver loaded by the gateway can be dynamically expanded and updated according to the push of the cloud server, so that the gateway can dynamically expand different Connector drivers and realize dynamic expansion of different communication protocols, thereby improving the scalability of the communication protocol of the gateway.

[0070] As an optional implementation, the gateway using the Connector driver to communicate with the Mesh device using the corresponding communication protocol may include: the gateway using the Connector driver to discover the Mesh device using the corresponding communication protocol, and then adding the discovered Mesh device to the Mesh network; for example, the gateway may set up a Mesh device management center, and the gateway using the Connector driver, after discovering the Mesh device using the corresponding communication protocol, can add the Mesh device to the Mesh network and add it to the gateway's Mesh device management center.

[0071] Furthermore, for Mesh devices that have joined the Mesh network, the gateway can use the Connector driver to send control commands to Mesh devices that use the corresponding communication protocol to achieve operations such as control and configuration of the Mesh devices. For example, the user can transmit the control command of the Mesh device to the gateway through the control panel (such as the device control interface displayed on the user terminal) or voice command; thus, the gateway can use the Connector driver to send the user's control command to the Mesh device that uses the corresponding communication protocol.

[0072] In some embodiments, the embodiments of the present application can perform a layered framework design on the gateway side. In the case of an abstract unified interface in the SDK specification, the gateway side can use the abstract unified interface to match the Connector driver loaded by the gateway to adapt to different communication protocols; thus, the gateway can use the Connector driver to dispatch the unified interface set by the gateway to communicate with the Mesh device using the corresponding communication protocol, thereby achieving the interactive effect between the gateway and the Mesh device. As an optional implementation, Figure 4 An exemplary diagram of a hierarchical design framework of a gateway provided in an embodiment of the present application is shown as follows: Figure 4 As shown, the gateway can be set at the framework level (e.g., software framework level):

[0073] Connector API (Application Programming Interface) 410, Connector library 420, Connector manager 430, and business logic 440 of Mesh device.

[0074] The Connector API may be a unified interface abstracted by SDK specifications based on the object model of the Mesh device. In one example, the gateway side may set up an SDK, and based on the object model of the Mesh device, set up a unified interface abstracted by SDK specifications to adapt to a variety of different types of communication protocols.

[0075] The Connector library can store the Connector drivers loaded by the gateway; and the Connector drivers are connected to the Connector manager so that the Connector drivers can be managed through the Connector manager;

[0076] The business logic of the Mesh device can define the business implementation logic of the Mesh device at the business level, such as device discovery, data transmission and reception, etc. of the Mesh device; the business logic of the Mesh device can be determined according to the functions that the gateway needs to support for the Mesh device, and the embodiments of the present application are not limited thereto; for ease of understanding, Figure 4 Some examples of the business logic of Mesh devices are shown exemplarily. For example, the functions that the gateway needs to support for Mesh devices may include: data sending and receiving, data conversion, message forwarding, device discovery and authentication, event notification, and device adaptation.

[0077] In the hierarchical design framework of the embodiment of the present application, the Connector API is responsible for accessing the Mesh device, and the gateway mainly implements the business logic of the Mesh device to achieve communication with the Mesh device. Based on this, as an optional implementation, the gateway can use the Connector to drive the unified interface, and use the Connector to drive the corresponding communication protocol to implement the business logic of the Mesh device, thereby achieving the effect of the gateway interacting with the Mesh device using the corresponding communication protocol.

[0078] In the solution provided in the embodiment of the present application, the developer can develop a corresponding Connector driver for the communication protocol used by the Mesh device, and the Connector driver is developed based on the SDK specification of the Connector SDK and the development requirements of the communication protocol; thus, after the developer develops the Connector driver corresponding to the communication protocol, the gateway can obtain the Connector driver corresponding to the communication protocol from the cloud server; the gateway can load the obtained Connector driver and register the Connector driver to the Connector manager so that the gateway can use the Connector driver; when the gateway sets a unified interface abstracted by the SDK specification, and the unified interface is used to unify the communication protocol for accessing the Mesh device, the gateway can use the Connector driver to schedule the unified interface to communicate with the Mesh device using the corresponding communication protocol, thereby enabling the gateway to communicate with the Mesh device when accessing the communication protocol of the Mesh device.

[0079] In the embodiment of the present application, the developer can develop the Connector driver corresponding to the communication protocol based on the SDK specification of the Connector SDK and the development requirements of the communication protocol of the Mesh device; thus, for Mesh devices using different communication protocols, the embodiment of the present application can develop corresponding different Connector drivers to realize the dynamic development of Connector drivers for different communication protocols; further, the Connector driver developed by the developer can be pushed to the gateway through the cloud server. After the gateway loads the Connector driver, the Connector driver can be used to schedule a unified interface to communicate with the Mesh device using the corresponding communication protocol, thereby achieving the effect of the gateway accessing the communication protocol. It can be seen that after the developer develops the Connector driver corresponding to different communication protocols, the gateway can obtain the Connector driver corresponding to different communication protocols through the push of the cloud server, and then the gateway can load the Connector driver corresponding to different communication protocols to achieve access to different communication protocols; therefore, the gateway can realize the dynamic expansion and update of the Connector driver based on the Connector driver pushed by the cloud server during use, so as to realize the dynamic expansion and update of the communication protocol supported by the gateway, so that the gateway is not limited to the communication protocol agreed upon when the gateway is produced, so as to achieve the effect of improving the extensibility of the communication protocol of the gateway and reducing the communication limitations of the gateway.

[0080] In one example, Figure 5 The following is an exemplary diagram showing an implementation example of protocol access provided by an embodiment of the present application. Figure 5 As shown, the gateway needs to interact with the Mesh devices of the direct ecosystem, the Mesh devices of the open alliance, and the Mesh devices of third-party manufacturers, and these Mesh devices support interconnection; among them, the Mesh devices of the direct ecosystem can be, for example, Mesh devices belonging to the same manufacturer as the gateway; the Mesh devices of the open alliance can be, for example, Mesh devices developed by developers based on open technology when the manufacturer to which the gateway belongs opens technology; the third-party manufacturer can be, for example, a different manufacturer from the manufacturer to which the gateway belongs, and the Mesh devices produced by the third-party manufacturer can be called Mesh devices of the third-party manufacturer.

[0081] Mesh devices, open alliance Mesh devices, and third-party manufacturers' Mesh devices may use different communication protocols. For example, these Mesh devices may use mainstream standard communication protocols such as WiFi communication protocol, Bluetooth communication protocol, ZigBee communication protocol, etc., or they may use non-standard communication protocols specified by third-party manufacturers or ISVs, which requires the gateway to support different types of communication protocols (including non-standard communication protocols). Based on this, the solution provided by this application can support the gateway to dynamically expand the communication protocol, so that the gateway can access different types of communication protocols, and realize the communication interaction between the gateway and Mesh devices using different communication protocols.

[0082] In the embodiment of the present application, a third-party manufacturer or developer can develop a Connector driver corresponding to the communication protocol used by the Mesh device. Figure 5 As shown, third-party manufacturers or developers can use development equipment to obtain the Connector SDK from the cloud server and register the Mesh device on the cloud server; thus, third-party manufacturers or developers can use development equipment to develop the Connector driver corresponding to the communication protocol based on the SDK specification of the Connector SDK and the development requirements of the communication protocol (the development process of the Connector driver can refer to the description of the corresponding part of the previous text, which will not be expanded here); further, third-party manufacturers or developers can use development equipment to upload the Connector driver to the cloud server, and the cloud server can associate the Connector driver with the corresponding registered Mesh device. For example, the development device can upload the Connector driver to the cloud server through the device page of the Mesh device, so that the cloud server can associate the Connector driver with the Mesh device; in one example, the development device can upload the Connector driver to the corresponding device page based on the device model of the Mesh device.

[0083] After obtaining the Connector driver developed by a third-party manufacturer or developer, the cloud server can push the Connector driver to the gateway; further, the cloud server can also inform the gateway of the Mesh device associated with the Connector driver. In some embodiments, the cloud server can obtain the device type supported by the gateway, and then push the Connector driver corresponding to the device type to the gateway to implement the communication protocol extension supported by the gateway; as an optional implementation, the device type supported by the gateway can indicate the communication protocol type supported by the gateway at the communication hardware level.

[0084] The gateway can load the Connector driver pushed by the cloud server and register the Connector driver to the Connector manager for management. Furthermore, the Connector library of the gateway can store the Connector driver loaded and registered by the gateway. Furthermore, the gateway can abstract the unified interface through the SDK specification based on the object model of the Mesh device; then the gateway can use the Connector driver in the Connector library to schedule the unified interface to communicate and interact with the Mesh device using the corresponding communication protocol, so that the gateway can communicate with the Mesh device when the communication protocol of the Mesh device is connected. For example, the gateway can use the Connector driver to schedule the unified interface and implement the device discovery logic with the corresponding communication protocol, so as to discover unconfigured devices around the gateway that use the corresponding communication protocol; then, the gateway can add the discovered unconfigured devices to the Mesh network and the device management center of the gateway.

[0085] For Mesh devices that have joined the Mesh network, users can pass the control commands of the Mesh devices to the gateway through the control panel of the user terminal or voice commands; thus, the gateway can use the Connector driver to schedule the unified interface and send the control commands to the Mesh devices using the corresponding communication protocol, so that users can control the Mesh devices through the control panel or voice commands.

[0086] In some further embodiments, when there is an update to the Connector driver loaded by the gateway (for example, the developer updates the developed Connector driver to optimize or increase the functionality of the Connector driver), the cloud server may send a Connector driver update notification to the gateway, so that the gateway can pull the updated Connector driver from the cloud server, and load and register the updated Connector driver; then, the gateway can use the updated Connector driver to interact with Mesh devices that use the corresponding communication protocol. In some further embodiments, for the newly added Connector driver of the cloud server (for example, the newly developed Connector driver by the developer), the cloud server can push the new Connector driver to the gateway so that the gateway supports the communication protocol corresponding to the new Connector driver.

[0087] Furthermore, the embodiment of the present application may also set up a third-party manufacturer server of a third-party manufacturer, and the third-party manufacturer server may authenticate and authorize the communication protocol used by the Mesh device of the third-party manufacturer, so that the communication protocol (including non-standard communication protocol) used by the Mesh device of the third-party manufacturer can be authenticated; and, the third-party manufacturer server may also be connected to the cloud server referred to in the embodiment of the present application, so as to upload the third-party manufacturer information, the information of the Mesh device of the third-party manufacturer, etc. to the cloud server.

[0088] The embodiment of the present application can be based on the object model of the Mesh device, and the unified interface for the communication protocol of the unified access Mesh device can be abstracted through the SDK specification, and on the basis of the unified interface, the Connector driver corresponding to the communication protocol is developed based on the SDK specification of the Connector SDK and the development requirements of the communication protocol; that is, on the basis of the unified interface, the Connector driver corresponding to different communication protocols is developed so that the unified interface is adapted to different communication protocols. The Connector driver developed by the embodiment of the present application can be pushed to the gateway by the cloud server, so that the gateway can load and register the Connector driver to realize the use and access of the Connector driver; further, when the gateway uses the Connector driver, it can use the Connector driver to dispatch the unified interface set by the gateway to communicate with the Mesh device using the corresponding communication protocol, so as to achieve the effect that the gateway supports interaction with Mesh devices of different communication protocols. It can be seen that the embodiment of the present application can dynamically load and update the Connector driver for the gateway through the cloud server to realize the dynamic expansion and update of the communication protocol for the gateway, which improves the extensibility of the communication protocol of the gateway, so that the gateway can quickly access Mesh devices of different communication protocols and reduce the communication limitations of the gateway.

[0089] The following is an introduction to the communication device provided in the embodiment of the present application from the perspective of the gateway. The communication device can realize communication with the Mesh device when the gateway accesses the communication protocol. The device content described below can be considered as the functional module that the gateway needs to set up to implement the communication method provided in the embodiment of the present application. The device content described below can be referenced to the content described above.

[0090] As an optional implementation, Figure 6 The block diagram of the communication device provided in the embodiment of the present application is exemplarily shown. The device can be applied to a gateway, referring to Figure 6 , the device may include:

[0091] The driver acquisition module 610 is used to obtain the Connector driver corresponding to the communication protocol used by the Mesh device from the cloud server; the communication protocol used by the Mesh device is a newly added communication protocol of the gateway, and the Connector driver is developed based on the SDK specification of the Connector SDK and the development requirements of the communication protocol;

[0092] The loading and registration module 611 is used to load the Connector driver and register the Connector driver with the Connector manager;

[0093] The driver utilization module 612 is used to utilize the Connector to drive the unified interface set by the scheduling gateway to communicate with the Mesh device using the corresponding communication protocol.

[0094] In some embodiments, the unified interface is based on a physical model of the Mesh device and is abstracted through the SDK specification, and the unified interface is used to unify the communication protocol for accessing the Mesh device.

[0095] In some embodiments, the driver utilization module 612 is used to utilize the Connector to drive the unified interface set by the scheduling gateway to communicate with the Mesh device using the corresponding communication protocol, including:

[0096] The unified interface is scheduled by the Connector driver, and the business logic of the Mesh device is implemented by the corresponding communication protocol driven by the Connector; wherein the gateway communicates with the Mesh device by implementing the business logic of the Mesh device.

[0097] In some embodiments, the gateway is provided with a Connector library, which is used to store the Connector driver loaded by the gateway. Accordingly, the loading and registration module 611, which is used to register the Connector driver with the Connector manager, includes:

[0098] The Connector driver is stored in the Connector library, and the Connector driver stored in the Connector library is set to be connected with a Connector manager; the Connector manager is a driver manager for managing the Connector driver.

[0099] The present application also provides a gateway, which can be configured to execute the communication method provided by the present application from the perspective of the gateway. For example, the gateway can implement the communication method provided by the present application by setting the communication device described above. As an optional implementation, Figure 7 An optional block diagram of a gateway is shown as an example. Figure 7 As shown, the gateway may include: at least one processor 71 , at least one communication interface 72 , at least one memory 73 and at least one communication bus 74 .

[0100] In the embodiment of the present application, the number of the processor 71 , the communication interface 72 , the memory 73 , and the communication bus 74 is at least one, and the processor 71 , the communication interface 72 , and the memory 73 communicate with each other through the communication bus 74 .

[0101] Optionally, the communication interface 72 may be an interface of a communication module for network communication. Optionally, the processor 71 may be a CPU, a GPU (Graphics Processing Unit), an NPU (embedded neural network processor), an FPGA (Field Programmable Gate Array), a TPU (tensor processing unit), an AI chip, an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application.

[0102] The memory 73 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0103] The memory 73 stores one or more computer executable instructions, and the processor 71 calls the one or more computer executable instructions to execute the communication method performed by the gateway as provided in the embodiment of the present application.

[0104] An embodiment of the present application also provides a storage medium, which can store one or more computer-executable instructions. When the one or more computer-executable instructions are executed, the communication method performed by the gateway as provided in the embodiment of the present application is implemented.

[0105] The embodiment of the present application also provides a computer program, which, when executed, implements the communication method performed by the gateway as provided in the embodiment of the present application.

[0106] The following is an introduction to the protocol access device provided in the embodiment of the present application from the perspective of the development device. The device content described below can be considered as the functional module that the development device needs to set up to implement the protocol access method provided in the embodiment of the present application. The device content described below can be referenced to the content described above.

[0107] As an optional implementation, Figure 8 The block diagram of the protocol access device provided in the embodiment of the present application is exemplarily shown. The device can be applied to the development equipment, referring to Figure 8 , the device may include:

[0108] SDK acquisition and registration module 810, used to obtain Connector SDK from the cloud server and register the Mesh device that needs to develop Connector driver to the cloud server; wherein the Connector SDK defines SDK specifications for developing Connector driver;

[0109] The driver development module 811 is used to develop a Connector driver corresponding to the communication protocol based on the SDK specification and the development requirements corresponding to the communication protocol used by the Mesh device; the communication protocol used by the Mesh device is a newly added communication protocol of the gateway;

[0110] The driver uploading module 812 is used to upload the Connector driver to the cloud server, so that after the cloud server associates the Connector driver with the registered Mesh device, the cloud server pushes the Connector driver to the gateway; wherein, the gateway loaded with the Connector driver uses the Connector driver to communicate with the Mesh device using the corresponding communication protocol.

[0111] In some embodiments, the driver development module 811 is used to develop a Connector driver corresponding to the communication protocol based on the SDK specification and the development requirements corresponding to the communication protocol used by the Mesh device, including:

[0112] Based on the object model of the Mesh device, a unified interface is abstracted through the SDK specification, and the unified interface is used to unify the communication protocol of accessing the Mesh device;

[0113] On the basis of the unified interface and based on the development requirements of the communication protocol, a Connector driver corresponding to the communication protocol is developed so that the Connector driver adapts to the communication protocol on the basis of the unified interface.

[0114] In some embodiments, the SDK specification defines development documents and development code samples for developing Connector drivers; the development requirements of the communication protocol include: multiple layered protocols that the communication protocol depends on. Accordingly, the driver development module 811 is used to develop the Connector driver corresponding to the communication protocol based on the unified interface and the development requirements of the communication protocol, including:

[0115] Based on the development documents and development code samples defined in the SDK specification, and on the basis of the unified interface, protocol codes of multiple layered protocols that the communication protocol depends on are written; and according to the protocol codes of the multiple layered protocols, Connector drivers corresponding to the communication protocol are developed.

[0116] In some embodiments, the SDK acquisition and registration module 810 is used to register the Mesh device that needs to develop a Connector driver to the cloud server, including:

[0117] A registration request carrying the registration information of the Mesh device is sent to the cloud server so that the cloud server registers the Mesh device and enables the cloud server to provide a device page of the Mesh device.

[0118] In some embodiments, the driver uploading module 812, for uploading the Connector driver to the cloud server, includes:

[0119] The Connector driver is uploaded on the device page so that the cloud server associates the Connector driver uploaded on the device page with the Mesh device corresponding to the device page.

[0120] The present application also provides a development device, which can be configured to execute the protocol access method implemented by the development device in the present application. For example, the development device can implement the protocol access method provided by the present application by setting the protocol access device described above. As an optional implementation, the block diagram of the development device can be combined with Figure 7 As shown, it includes at least one memory and at least one processor, the memory stores one or more computer-executable instructions, and the processor calls the one or more computer-executable instructions to execute the protocol access method performed by the development device as provided in the embodiment of the present application.

[0121] An embodiment of the present application also provides a storage medium, which can store one or more computer-executable instructions. When the one or more computer-executable instructions are executed, the protocol access method performed by the development device as provided in the embodiment of the present application is implemented.

[0122] The embodiment of the present application also provides a computer program, which, when executed, implements the protocol access method performed by the development device as provided in the embodiment of the present application.

[0123] The above describes multiple embodiments provided by the embodiments of the present application, and each optional method introduced in each embodiment can be combined and cross-referenced with each other without conflict, thereby extending a variety of possible embodiments, which can be considered as embodiments disclosed and disclosed by the embodiments of the present application. Although the embodiments of the present application are disclosed as above, the present application is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present application, so the scope of protection of the present application should be based on the scope defined by the claims.

Claims

1. A protocol access method, wherein: Used in development equipment, including: Obtain the Connector SDK from the cloud server and register the Mesh device that needs to develop the Connector driver with the cloud server; wherein the Connector SDK defines an SDK specification for developing the Connector driver, and the SDK specification abstracts a unified interface; Based on the SDK specification and the development requirements corresponding to the communication protocol used by the Mesh device, a Connector driver corresponding to the communication protocol is developed; the Connector driver adapts the communication protocol of the Mesh device on the basis of the unified interface; the communication protocol used by the Mesh device is a newly added communication protocol of the gateway; The Connector driver is uploaded to the cloud server so that the cloud server associates the Connector driver with the registered Mesh device, and then the cloud server pushes the Connector driver to the gateway; wherein the gateway loaded with the Connector driver uses the Connector driver to communicate with the Mesh device using the corresponding communication protocol.

2. The method according to claim 1, wherein: Based on the SDK specification and the development requirements corresponding to the communication protocol used by the Mesh device, developing the Connector driver corresponding to the communication protocol includes: Based on the object model of the Mesh device, a unified interface is abstracted through the SDK specification, and the unified interface is used to unify the communication protocol of the access Mesh device; On the basis of the unified interface and based on the development requirements of the communication protocol, a Connector driver corresponding to the communication protocol is developed so that the Connector driver adapts to the communication protocol on the basis of the unified interface.

3. The method according to claim 2, wherein: The SDK specification defines development documents and development code samples for developing Connector drivers; The development requirements of the communication protocol include: multiple layered protocols that the communication protocol depends on; based on the unified interface and the development requirements of the communication protocol, developing a Connector driver corresponding to the communication protocol includes: Based on the development documents and development code samples defined in the SDK specification, and on the basis of the unified interface, protocol codes of multiple layered protocols that the communication protocol depends on are written; and according to the protocol codes of the multiple layered protocols, Connector drivers corresponding to the communication protocol are developed.

4. The method according to claim 1, wherein: The Mesh devices that need to develop Connector drivers to register with the cloud server include: Sending a registration request carrying the registration information of the Mesh device to the cloud server so that the cloud server registers the Mesh device and enables the cloud server to provide a device page of the Mesh device; The uploading of the Connector driver to the cloud server includes: The Connector driver is uploaded on the device page so that the cloud server associates the Connector driver uploaded on the device page with the Mesh device corresponding to the device page.

5. A communication method, wherein: Applied to gateways, including: Obtain the Connector driver corresponding to the communication protocol used by the Mesh device from the cloud server; the communication protocol used by the Mesh device is a newly added communication protocol of the gateway, and the Connector driver is developed based on the SDK specification of the Connector SDK and the development requirements of the communication protocol. The SDK specification abstracts a unified interface, and the Connector driver adapts the communication protocol of the Mesh device based on the unified interface; Load the Connector driver and register the Connector driver with the Connector manager; The Connector is used to drive the unified interface set by the scheduling gateway to communicate with Mesh devices using the corresponding communication protocol.

6. The method according to claim 5, wherein: The unified interface is based on the object model of the Mesh device and is abstracted through the SDK specification, and the unified interface is used to unify the communication protocol for accessing the Mesh device; The unified interface set by the Connector-driven scheduling gateway to communicate with the Mesh device using the corresponding communication protocol includes: The unified interface is scheduled by the Connector driver, and the business logic of the Mesh device is implemented by the corresponding communication protocol driven by the Connector; wherein the gateway communicates with the Mesh device by implementing the business logic of the Mesh device.

7. The method according to claim 5, wherein: The gateway is provided with a Connector library, and the Connector library is used to store the Connector driver loaded by the gateway; The registering the Connector driver to the Connector manager includes: The Connector driver is stored in the Connector library, and the Connector driver stored in the Connector library is set to be connected with a Connector manager; the Connector manager is a driver manager for managing the Connector driver.

8. A development device, wherein: It comprises at least one memory and at least one processor, wherein the memory stores one or more computer executable instructions, and the processor calls the one or more computer executable instructions to execute the protocol access method as described in any one of claims 1 to 4.

9. A gateway, wherein: The system comprises at least one memory and at least one processor, wherein the memory stores one or more computer executable instructions, and the processor calls the one or more computer executable instructions to execute the communication method according to any one of claims 5 to 7.

10. A storage medium, wherein: The storage medium stores one or more computer executable instructions, and when the one or more computer executable instructions are executed, the protocol access method as described in any one of claims 1-4, or the communication method as described in any one of claims 5-7 is implemented.