Method, device, storage medium and equipment for supporting access to multiple cloud servers

Abstract

The application discloses a method, device, storage medium and equipment supporting access to multiple cloud servers. The method is applied to an equipment and includes that a service layer in a smart home equipment receives target cloud platform information transmitted by an application layer, and calls a cloud universal logic firmware in the service layer of the smart home equipment. Processing logic in the cloud universal logic firmware is executed to create a cloud agent object. According to the target cloud platform information, the cloud agent object is used to instantiate a target cloud configuration node corresponding to a target cloud platform. The target cloud configuration node includes a pre-encapsulated action set. The action set is obtained by abstracting access actions of the smart home equipment to multiple cloud servers. Access actions in the action set are executed to access target servers of the target cloud platform. The application uses one cloud universal logic firmware to support connection of the smart home equipment to multiple different cloud platforms, and improves the efficiency of connection to different cloud platforms, code maintenance efficiency and development efficiency.

Description

Technical Field

[0001] This application relates to the field of smart home technology, and in particular to a method, apparatus, storage medium and device that supports access to multiple cloud servers. Background Technology

[0002] As IoT devices become increasingly prevalent, more and more companies are involved in the development of devices such as smart home devices. Different companies develop their own unique cloud servers / platforms, mobile applications, and firmware for their smart home devices. Typically, a single firmware entry in a smart home device can only connect to one cloud server / platform. If it needs to connect to another cloud server / platform, it requires re-adaptation and the generation of a new firmware within the smart home device. These two firmware entries belong to two different sets of code, which exponentially increases the development and maintenance workload. Connecting to more than two cloud servers / platforms further complicates development and maintenance. Summary of the Invention

[0003] This application provides a method, apparatus, storage medium, and device that support access to multiple cloud servers, enabling smart home devices to connect to multiple different cloud platforms using a single firmware, thereby improving firmware maintenance efficiency.

[0004] This application provides a method for supporting access to multiple cloud servers, wherein one cloud server corresponds to one cloud platform. The method is applied to a smart home device, which includes an application layer and a service layer. The service layer includes cloud-based general logic firmware. The method includes:

[0005] After the service layer receives the target cloud platform information from the application layer, it invokes the cloud general logic firmware in the service layer.

[0006] Execute the generic program code in the cloud generic logic firmware to create a cloud proxy object;

[0007] Based on the target cloud platform information, the target cloud configuration node corresponding to the target cloud platform is instantiated using the cloud proxy object. The target cloud configuration node includes a pre-encapsulated set of actions, which is obtained by abstracting the access actions of the smart home device to multiple cloud servers.

[0008] Execute the access action in the action set to access the target cloud server corresponding to the target cloud platform.

[0009] This application embodiment also provides a device that supports access to multiple cloud servers, wherein one cloud server corresponds to one cloud platform. The device is applied in a smart home device, the smart home device including an application layer and a service layer, the service layer including cloud general logic firmware, and the device comprising:

[0010] The calling module is used to call the cloud general logic firmware in the service layer after the service layer receives the target cloud platform information passed by the application layer;

[0011] Create a module to execute the cloud general logic firmware to create a cloud proxy object;

[0012] The node instantiation module is used to instantiate the target cloud configuration node corresponding to the target cloud server using the cloud proxy object based on the target cloud platform information. The target cloud configuration node includes a pre-encapsulated set of actions, which is obtained by abstracting the access actions of the smart home device to access multiple cloud servers.

[0013] The access module is used to execute the access actions in the action set to access the target cloud server corresponding to the target cloud platform.

[0014] This application also provides a computer-readable storage medium storing a plurality of instructions adapted for loading by a processor to perform the steps of any of the above-described methods for supporting access to multiple cloud servers.

[0015] This application also provides an apparatus including a processor and a memory, the processor being electrically connected to the memory, the memory being used to store instructions and data, and the processor being used in the steps of the method for supporting access to multiple cloud servers described above.

[0016] This application provides a method, apparatus, storage medium, and smart home device that supports accessing multiple cloud servers. The smart home device receives target cloud server information from the application layer through a service layer, and invokes a cloud-based general logic firmware within the service layer. The processing logic within the cloud-based general logic firmware is executed to create a cloud proxy object. Based on the target cloud server information, a target cloud configuration node corresponding to the target cloud server is instantiated using the cloud proxy object. This target cloud configuration node includes a pre-encapsulated set of actions, which is an abstraction of the access actions of the smart home device accessing multiple cloud servers. Because the target cloud configuration node includes abstracted access actions of the smart home device accessing multiple cloud servers, the smart home device can access any of the multiple cloud servers by instantiating the target cloud configuration node and executing the pre-encapsulated set of actions within it. Thus, a single cloud-based general logic firmware can support smart home devices connecting to multiple different cloud platforms, improving the efficiency of connecting to different cloud platforms. Furthermore, only one cloud-based general logic firmware needs to be developed and maintained, improving code maintenance and development efficiency. Attached Figure Description

[0017] The technical solution and other beneficial effects of this application will become apparent from the following detailed description of specific embodiments in conjunction with the accompanying drawings.

[0018] Figure 1 This is a schematic diagram illustrating an application scenario provided in an embodiment of this application.

[0019] Figure 2 A hierarchical structure diagram of a smart home device provided in an embodiment of this application.

[0020] Figure 3 This is a flowchart illustrating a method for supporting access to multiple cloud servers provided in an embodiment of this application.

[0021] Figure 4 This is a timing diagram illustrating a method for supporting access to multiple cloud servers provided in an embodiment of this application.

[0022] Figure 5 This is a flowchart illustrating the method for supporting access to multiple cloud servers provided in an embodiment of this application.

[0023] Figure 6 This is another flowchart illustrating a method for supporting access to multiple cloud servers provided in an embodiment of this application.

[0024] Figure 7 This is a schematic diagram of the structure of an apparatus that supports access to multiple cloud servers, as provided in an embodiment of this application.

[0025] Figure 8This is a schematic diagram of the access module provided in an embodiment of this application.

[0026] Figure 9 This is a schematic diagram of the structure of a smart device provided in an embodiment of this application.

[0027] Figure 10 This is another structural schematic diagram of the smart device provided in an embodiment of this application. Detailed Implementation

[0028] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0029] This application provides a method, apparatus, storage medium, and smart device for supporting access to multiple cloud servers. Any of the apparatuses provided in this application that support access to multiple cloud servers can be integrated into a smart device. This smart device can be a smart home device, such as a smart refrigerator, smart TV, smart air conditioner, smart curtains, smart speaker, smart robot vacuum cleaner, etc., and may also include smart in-vehicle devices, wearable devices, smart robots, and other devices. This application uses a smart home device as an example for illustration.

[0030] In this application embodiment, the cloud server refers to the cloud server in the cloud platform. The cloud server can be an independent cloud server or a cloud server cluster. Correspondingly, one cloud server corresponds to one cloud platform, and multiple cloud servers correspond to multiple cloud platforms.

[0031] The firmware in this application embodiment includes at least program code that enables communication between the smart home device and the cloud server corresponding to the smart home device. The processing logic of the program code may include at least one or more of the following: connecting to the corresponding cloud server, registering with the corresponding cloud server, sending data to the corresponding cloud server, receiving data from the cloud server, and releasing / destroying the connection with the cloud server.

[0032] Because multiple cloud platforms are typically provided by different companies—for example, company A provides cloud platform A, and company B provides cloud platform B—the implementation logic and / or corresponding program code (also known as computer programs) for achieving the same effect differs. In other words, the firmware corresponding to each cloud platform is different. Assuming a smart home device partners with cloud platform A, or the smart home device is manufactured by the company corresponding to cloud platform A, then the smart home device connects to cloud server A corresponding to cloud platform A through the firmware corresponding to cloud platform A. If the smart home device wants to connect to cloud server B corresponding to cloud platform B, then it also needs to integrate / install / deploy the firmware corresponding to cloud platform B in the smart home device.

[0033] Therefore, for a smart home device to connect to both cloud server A and cloud server B, it needs to integrate / install / deploy firmware corresponding to both cloud platform A and cloud platform B. This means the smart home device requires two different firmware installations to connect to the cloud servers of two different cloud platforms. If it wants to connect to more cloud platforms, it needs to integrate / install / deploy even more different firmware installations. This increases the development difficulty of smart home devices and leads to a significant increase in the amount of code, adding to the complexity of the codebase. Furthermore, when integrating / installing / deploying firmware for other cloud platforms, these firmware installations may incorporate third-party code libraries, which may have potential security vulnerabilities, resulting in poor security and stability for the smart home device.

[0034] To address the aforementioned issues, this application provides a method, apparatus, storage medium, and smart device that supports access to multiple cloud servers. Only one firmware is required to support smart home devices accessing cloud servers on multiple cloud platforms, reducing the difficulty of program code maintenance and improving the security and stability of smart home devices.

[0035] Figure 1 This is a schematic diagram of an application scenario provided in the embodiments of this application. In this application scenario, a remote control, smart home devices, a cloud server, and a mobile terminal are included. The cloud server includes at least two cloud servers, such as cloud server A and cloud server B. The mobile terminal is held by user A. Cloud server A corresponds to cloud platform A, and cloud server B corresponds to cloud platform B. The remote control communicates with the smart home devices, the smart home devices communicate with the cloud servers, and the cloud servers communicate with the mobile terminal.

[0036] User A's mobile terminal has an application corresponding to cloud platform A installed or integrated. After the smart home device is configured to connect to the network, it connects to cloud server A using the method described in this embodiment. After user A's mobile terminal has an application corresponding to cloud platform B installed or integrated, the smart home device can be reconfigured to connect to cloud server B using the method described in this embodiment. In one embodiment, the method described in this embodiment can also connect to both cloud server A and cloud server B simultaneously.

[0037] The system allows for remote control of smart home devices. For example, a smart refrigerator can be controlled by adjusting its temperature using a remote control. The remote control sends the adjusted temperature to the refrigerator, which then transmits the updated temperature to the cloud server. Similarly, mobile devices can remotely control smart home devices via the cloud server. For instance, a mobile device can remotely adjust the temperature of a smart refrigerator via the cloud server. The cloud server then sends the temperature adjustment command to the smart home device, which in turn adjusts the temperature and transmits the updated temperature back to the remote control.

[0038] Figure 2 This is a block diagram illustrating the hierarchical architecture of a smart home device provided in an embodiment of this application. Figure 2 As shown, smart home devices include an application layer, a service layer, and a component layer. The application layer communicates with the mobile terminal's application and can obtain the smart home device's state machine, from which various current state information of the smart home device can be obtained. The service layer includes cloud common logic handlers, and the component layer includes common components, such as various transmission interfaces. The component layer will not be described further below.

[0039] The cloud-based general logic firmware includes at least general program code for communication between smart home devices and any one of the multiple cloud servers. This general program code refers to program code applicable to communication with any one of the multiple cloud servers. The general program code includes general processing logic, which includes processing logic applicable to communication with any one of the multiple cloud servers, including but not limited to any one or more of the following: connecting to any one of the multiple cloud servers, registering to any one of the multiple cloud servers, sending data to any one of the multiple cloud servers, receiving data from any one of the multiple cloud servers, and releasing / destroying the connection with any one of the multiple cloud servers.

[0040] The service layer includes cloud agents (cloud_agent) or cloud agent objects. Through cloud agents, transmit channels and cloud profiles can be instantiated. The transmit channels include Hyper Text Transfer Protocol (HTTP) channels, Message Queuing Telemetry Transport (MQTT) channels, Transmission Control Protocol (TCP) channels, User Datagram Protocol (UDP) channels, etc. The cloud profiles can include cloud profile A of cloud platform A, cloud profile B of cloud platform B, etc.

[0041] Figure 3 This is a flowchart illustrating a method for supporting access to multiple cloud servers in an embodiment of this application. The method is applied to smart devices such as smart home devices, which include an application layer and a service layer. The service layer includes cloud-based general logic firmware. The method specifically includes the following steps.

[0042] 101. After the service layer of the smart home device receives the target cloud platform information from the application layer, it calls the cloud general logic firmware in the service layer.

[0043] When the smart device is a smart home device, after successful network configuration and connection, the method described in this embodiment is automatically triggered. Smart home devices typically use mobile terminals for network configuration. These terminals usually have an application corresponding to the cloud platform installed. During network configuration, the smart home device obtains the target cloud platform information through the application. This information includes the current cloud platform and, further, the cloud platform type, such as cloud platform A. After obtaining the cloud platform information, the smart home device transmits it to the service layer through its application layer.

[0044] After receiving the target cloud platform information from the application layer, the service layer invokes the cloud-based general logic firmware within the service layer and passes the target cloud platform information to the corresponding cloud-based general logic firmware. This cloud-based general logic firmware can be pre-integrated / installed / deployed in smart home devices.

[0045] 102. Execute the generic program code in the cloud generic logic firmware to create a cloud proxy object.

[0046] The creation of cloud proxy objects, instantiation of target cloud configuration nodes, and execution of access actions in the action set are all functions implemented by the general program code in the cloud general logic firmware. In other words, once a smart home device is successfully configured and connected to the network, it automatically performs these actions, including creating cloud proxy objects, instantiating target cloud configuration nodes, and executing access actions in the action set.

[0047] After the smart home devices connect to the network, the application layer sends a cloud agent creation request to the service layer. For example, this cloud agent creation request can be an `epi_cloud_agent_create` request, such as... Figure 4 As shown, the cloud agent creation request includes information such as the cloud platform type. After receiving the request, the service layer calls the cloud agent's structure, which includes information such as the cloud platform type and related resources. Based on this structure, a new cloud agent object, `cloud_agent`, is created; or, in other words, the `cloud_agent` object is initialized using the cloud agent's structure. Subsequent operations will then be performed using this cloud agent object.

[0048] 103. Based on the target cloud platform information, instantiate the target cloud configuration node corresponding to the target cloud platform using the cloud proxy object. The target cloud configuration node includes a pre-encapsulated set of actions, which is obtained by abstracting the access actions of smart home devices to multiple cloud servers.

[0049] The target cloud configuration node refers to the node corresponding to the target cloud platform. This node includes configuration information and a pre-packaged set of actions for the target cloud server. This configuration information includes server information such as the target cloud server's URL and port number, as well as the types of transmission channel protocols supported by the target cloud server, such as HTTP.

[0050] The cloud proxy object instantiates / initializes the target cloud configuration node corresponding to the target cloud platform. For example, the cloud_profile_init function is used to instantiate / initialize the target cloud configuration node, and the configuration information and pre-encapsulated action set in the target cloud configuration node are initialized according to the target cloud platform information.

[0051] The pre-encapsulated action set is derived from abstracting the access actions of smart home devices to multiple cloud servers. "Abstracting" refers to obtaining the common logic shared by each access action across multiple cloud servers; an access action refers to various different operations / actions that interact with the cloud servers. For example, access actions include, but are not limited to, connecting to a cloud server, registering with a cloud server, sending data to a cloud server, receiving data from a cloud server, and releasing / destroying the connection with a cloud server. Since the action set is derived from abstracting the access actions of smart home devices to multiple cloud servers, it allows access to any one of the multiple cloud servers; in other words, the action set is applicable to accessing any one of the multiple cloud servers.

[0052] 104. Execute the access action in the action set to access the target cloud server corresponding to the target cloud platform.

[0053] For any cloud server, the configuration information of the target cloud server is passed into the action set, the access action in the action set is executed, and the target cloud server in the target cloud platform is accessed according to the configuration information of the target cloud server.

[0054] Since the target cloud configuration node includes abstract access actions for smart home devices to access multiple cloud servers, smart home devices can access any of the multiple cloud servers by instantiating the target cloud configuration node and executing the pre-encapsulated set of actions within it. In this way, a single cloud-based general logic firmware can support smart home devices connecting to multiple different cloud platforms, improving the efficiency of connecting to different cloud platforms. At the same time, only one cloud-based general logic firmware needs to be developed and maintained, improving code maintenance and development efficiency.

[0055] In one embodiment, such as Figure 3 As shown, after creating the cloud proxy object, the method further includes step 103a.

[0056] 103a, Instantiate multiple transmission channels based on multiple transmission channel protocols using cloud proxy objects.

[0057] Multiple transport channel protocols can be transport channel protocols supported by multiple cloud servers. For example, cloud server A supports the HTTP protocol, cloud server B supports the MQTT protocol, and cloud server C supports the TCP protocol. Thus, multiple transport channel protocols include HTTP, MQTT, and TCP protocols. Multiple transport channels are instantiated using a cloud proxy object based on these protocols. For example, there is an HTTP channel corresponding to the HTTP protocol, an MQTT channel corresponding to the MQTT protocol, and a TCP channel corresponding to the TCP protocol. One transport channel is instantiated for each transport protocol.

[0058] Since the specific transmission channel protocol types supported by the target cloud server are currently unknown, it is necessary to instantiate transmission channels based on the transmission channel protocols supported by multiple cloud servers. After obtaining the transmission channel protocol types supported by the target cloud platform, the target transmission channel that matches the supported protocol type is determined from among the multiple instantiated transmission channels. In some embodiments, the target transmission channel can be instantiated based on the transmission channel protocol type after obtaining it. Then, the target transmission channel is used to connect to the target cloud server and send data to it.

[0059] Among them, such as Figure 5 As shown, the steps in step 104 above include the following steps.

[0060] 201. For each access action in the pre-encapsulated action set, use the cloud proxy object to obtain the parameter information that the access action needs to process.

[0061] For example, for an access action to connect to a target cloud server, the step of obtaining the parameter information to be processed by the access action using a cloud proxy object includes: obtaining the transmission channel protocol type supported by the target cloud server using the cloud proxy object, so as to determine the target transmission channel supported by the transmission channel protocol type; obtaining the server information of the target cloud server; and using the target transmission channel and server information as the parameter information to be processed by the access action.

[0062] For example, for an access action registered with a target cloud server, the step of obtaining the parameter information required for the access action using a cloud proxy object includes: product information of smart home devices, such as product identifiers like productKey and device hardware addresses like devicemac, and using the product identifier and device hardware address as the parameter information required for the access action.

[0063] For example, for an access action that sends data to a target cloud server, the step of obtaining the parameter information required for the access action using a cloud proxy object includes: using the cloud proxy object to listen to the application layer; when parameter information is received from the application layer, obtaining the parameter information and using it as the parameter information required for the access action. For example, this parameter information may include status information of smart home devices.

[0064] 202. The parameter information is packaged to obtain the packaged output parameters of the access action.

[0065] Package assembly refers to encapsulating parameter information using a package assembly function to encapsulate the parameter information into parameters that the target cloud server can recognize, i.e., package output parameters, and then outputting the package output parameters.

[0066] For example, Figure 4 In the function `node->packet(action_step, out_pack_data1)`, `action_step` refers to the index number of a specific access action in the action set, and `out_pack_data1` refers to the output parameters of the packet assembly.

[0067] 203. Execute the access action according to the package output parameters to access the target cloud server corresponding to the target cloud platform.

[0068] Use the package output parameters as input parameters for the access action to execute the access action. For example... Figure 4 The `connect(out_pack_data1)` function in the code refers to the connection function corresponding to the access action to the target cloud server, where `connect` is the connection function corresponding to the access action to the target cloud server, and `out_pack_data1` is the packet output parameter obtained from the packet assembly process in the previous step. Executing `connect` connects to the target cloud server corresponding to the target cloud platform.

[0069] In one embodiment, step 104 above further includes the following steps.

[0070] 204 returns the response result of the target cloud server after the access action is executed through the callback function of the access action.

[0071] Each access action corresponds to a callback function, such as `callback`, which returns the response result `out_conn_data` from the target cloud server after the corresponding access action is executed. For example... Figure 4 As shown, after the connect function, the callback function returns the connection result to the target cloud server.

[0072] It should be noted that some target cloud servers may return connection results, while others may not.

[0073] 205. Use the cloud proxy object to obtain the response result, and unpack the response result to obtain the response unpacking result.

[0074] The unpacking process includes identifying the response from the target cloud server and performing format parsing and / or format conversion on the response. Unpacking is implemented using unpacking functions, and the resulting unpacked response is readable by smart home devices.

[0075] Understandably, different target cloud servers may respond differently to the same access action. For example, in the response to connecting to a target server, if the connection is successful, some servers return 1, while others return "success". Therefore, it is necessary to unpack the response to obtain the unpacked response result. The unpacked response result refers to the result obtained by unpacking the response.

[0076] like Figure 4 In the function `node->unpack(action_step, out_conn_data)`, `node->unpack` is the unpacking function, `action_step` refers to the index number of the current access action, and `out_conn_data` is the connection result returned by the callback function of the previous connection function, which is the connection result to the target cloud server.

[0077] 206. Send the unpacked response result to the application layer.

[0078] The application layer sends a callback function (such as a `callback` function) to the cloud proxy object. Therefore, after receiving the unpacked response, the cloud proxy object sends the unpacked response to the application layer's `callback` function, enabling the application layer to perform subsequent operations. These subsequent operations might include sending the connection result to the remote control for display.

[0079] The steps in this embodiment are steps that need to be performed for each access action. First, packet assembly is performed, and the packet output parameters obtained from the packet assembly are used as the input parameters for the access action. The access action is then executed to return a response result through a callback function. The response result is then unpacked to obtain the response unpacking result, and the response unpacking result is sent to the application layer.

[0080] Since the action set includes at least one access action, if the action set includes multiple access actions, the index number of the access action is incremented by 1 after each access action is executed, for example, action_step is incremented by 1, in order to execute the next access action.

[0081] Figure 6 This is a flowchart illustrating a method for supporting access to multiple cloud servers provided in an embodiment of this application. The method includes the following steps, specifically, which can be combined with... Figure 4 Let's understand the method in this embodiment together.

[0082] 301. After the service layer of the smart home device receives the target cloud platform information from the application layer, it calls the cloud general logic firmware in the service layer.

[0083] 302. Execute the generic program code in the cloud generic logic firmware to create a cloud proxy object.

[0084] 303, Instantiate multiple transport channels using cloud proxy objects based on multiple transport channel protocols.

[0085] 304. Based on the target cloud platform information, the target cloud configuration node corresponding to the target cloud platform is instantiated using a cloud proxy object. The target cloud configuration node includes a pre-encapsulated set of actions, which is obtained by abstracting the access actions of smart home devices to multiple cloud servers.

[0086] In one embodiment, before executing the access action to the target cloud server in the action set, the application layer needs to send a connection request to the service layer. This connection request can be an epi_cloud_agent_connect request, such as... Figure 4 As shown, after receiving the connection request, the service layer triggers the access action for the target cloud server in the action set. In some embodiments, a connection request may not be sent, and the access action for the target cloud server in the action set may be executed automatically.

[0087] 305. Use the cloud proxy object to obtain the target transmission channel and server information required to connect to the target cloud platform and the target cloud server, and perform packet processing on the target transmission channel and server information to obtain the packet output parameters for connecting to the target cloud server.

[0088] 306. Execute the access action to connect to the target cloud server according to the packet output parameters, and receive the connection result of the connection to the target cloud server returned by the callback function of the access action.

[0089] The response results include connection results, which include information such as whether the connection was successful or failed.

[0090] 307. Use the cloud proxy object to obtain the connection result, unpack the connection result to obtain the connection unpacking result, and send the connection unpacking result to the application layer.

[0091] The response unpacking result includes the connection unpacking result.

[0092] Steps 305 to 307 complete the access action to the target cloud server. In one embodiment, the parameter information for connecting to the target cloud server includes not only the target transmission channel and server information, but also product information of the smart home device, such as product identifier and device hardware address. Thus, after connecting to the target cloud server, the smart home device's product information is used to register with the target cloud server to complete the smart home device registration. Figure 4 The image shows this situation.

[0093] 308. Use the cloud proxy object to obtain product information of smart home devices, and package the product information to obtain the packaged output parameters registered with the target cloud server.

[0094] 309. Execute the access action to register with the target cloud server according to the package output parameters, and receive the registration result of registering with the target cloud server returned by the callback function of the access action.

[0095] The response results include registration results, which include information such as registration success or registration failure.

[0096] 310. Use the cloud proxy object to obtain the registration result, unpack the registration result to obtain the registration unpacking result, and send the registration unpacking result to the application layer.

[0097] The response unpacking result includes the registration unpacking result. Some target cloud servers may not return any registration result after successful registration of the smart home device, i.e., the registration result will be empty; others may return "registration successful" or similar identifiers. The returned registration unpacking result is then unpacked and processed, such as parsing and / or format conversion, to obtain the registration unpacking result, which is then sent to the application layer.

[0098] Steps 308 to 310 implement the access action of registering with the target cloud server. After connecting to and registering with the target cloud server, the subsequent steps involve using the cloud proxy object to listen for changes in the status information of the smart home devices input from the application layer or to listen for operation commands from the target cloud server, thus involving data transmission between the smart home devices and the target cloud server.

[0099] 311. Use a cloud proxy object to listen to the application layer. When the parameter information passed from the application layer is detected, obtain the parameter information and process the parameter information into a package to obtain the packaged output parameters.

[0100] The parameters passed in from the application layer include various status information of the smart home devices, including but not limited to power-on status, power-off status, current temperature information, current mode information, and current TV channel information. Any operation performed on the smart home devices, such as turning them on, turning them off, adjusting the temperature, changing the mode, or switching TV channels, will generate corresponding status information for the smart home devices, causing changes in their status.

[0101] In some embodiments, the parameter information passed in from the application layer may also include other parameter information, which may vary depending on the specific smart home device, and will not be elaborated here.

[0102] This status information is transmitted from the application layer of the smart home device to the service layer, and then retrieved by the cloud proxy object. After retrieving the status information, it is processed into packets to obtain the packet output parameters. For example, if the status information sent by the application layer is "1", which represents a powered-on state, after packet processing, "1" is converted into "powered" that the target cloud server can recognize, and "powered" is used as the packet output parameter.

[0103] It's important to note that even when indicating a device is powered on, the same status information might be represented differently by different target cloud servers. Therefore, packet processing is necessary to convert the same status information into information that can be recognized by different target cloud servers. For example, the application layer might receive a "1" status information for powering on, target cloud server A might receive "powered on," while target cloud server B might receive "0," and so on.

[0104] 312. Execute the access action to send data to the target cloud server according to the packet output parameters, and receive the processing response result of the target cloud server returned by the callback function of the access action.

[0105] The response result includes the processing response result. If the parameter information is various status information, the processing response result includes information such as whether the status synchronization was successful or failed.

[0106] For example, the packet output parameters can be used as input parameters for an access action that sends data to the target cloud server. This allows the access action to send the packet output parameters to the target cloud server, enabling the target cloud server to perform corresponding processing based on the packet output parameters, such as synchronization processing.

[0107] like Figure 4In this code, `transmit(out_pack_data2)` is the function that sends data to the target cloud server. `out_pack_data2` is the output parameter of the packet assembly function `node->packet(action_step, out_pack_data2)`. The index of `action_step` in the assembly function is different from the index of `action_step` in the connection to the target cloud server mentioned above. This `transmit` function performs the action of sending data to the target cloud server and receives the processing response from the target cloud server returned by the callback function. This processing response can be represented by `out_recv_data`.

[0108] 313. Use the cloud proxy object to obtain the processing response result, unpack the processing response result to obtain the processing unpacking result, and send the processing unpacking result to the application layer.

[0109] Steps 311 to 313 implement the access action of sending data to the target cloud server. When the cloud proxy object listens for changes in the status information of the smart home devices input from the application layer, it sends the changes in status information to the target cloud server so that the target cloud server can synchronize the status information of the smart home devices.

[0110] In one embodiment, after the smart home device connects to and registers with the target cloud server, the method further includes: using a cloud proxy object to listen for operation commands from the target cloud server; unpacking the operation commands to obtain the command unpacking result; and sending the command unpacking result to the application layer.

[0111] The operation command can be a command sent from a mobile terminal to a target cloud server via remote control. This command can perform any of the operations described above on the smart home device. For example, turning on the smart home device.

[0112] The cloud proxy object can listen for corresponding operation commands through callback functions returned by the target cloud server. Upon receiving the command, the proxy object unpacks it into parameters recognizable by the application layer of the smart home device, thus obtaining the command unpacking result. For example, listening for a "power on" command returned by the target cloud server, the `node->unpack` function is called to unpack the command, converting it to "1", and then sending it to the application layer's callback function. The application layer will then perform subsequent processing, such as powering on the smart device and synchronizing the power-on status to the remote control.

[0113] It should be noted that, in one embodiment, the unpacking and repacking processes in each of the above access actions appear in pairs. After each access action is completed, i.e. after the unpacking process is successful, the index number of the access action is incremented by 1.

[0114] In one embodiment, the smart home device further includes a default cloud configuration node, which also includes a pre-encapsulated set of actions. That is, in addition to the default cloud configuration node, it also includes a target cloud configuration node. The target cloud configuration node includes at least one cloud configuration node, and the default cloud configuration node includes at least one cloud configuration node. Generally, the target cloud configuration node includes one cloud configuration node, and the default cloud configuration node includes one cloud configuration node.

[0115] In one embodiment, after obtaining the target cloud configuration node, the method further includes: obtaining all cloud configuration nodes, including the default cloud configuration node and the target cloud configuration node; traversing each cloud configuration node among all cloud configuration nodes; and executing each access action in the action set corresponding to each cloud configuration node to access the cloud server corresponding to each cloud configuration node.

[0116] In this embodiment, at least two different cloud platforms can be connected to cloud servers simultaneously, enabling smart home devices to maintain communication connections with cloud servers on two different cloud platforms. This improves the efficiency of connecting cloud servers on different cloud platforms. At the same time, a single cloud-based universal logic firmware can support smart home devices to connect to multiple different cloud platforms simultaneously, improving code maintenance and development efficiency.

[0117] Based on the method described in the above embodiments, this embodiment will be further described from the perspective of a device that supports access to multiple cloud servers. Specifically, the device that supports access to multiple cloud servers can be implemented as an independent entity or integrated into a smart device.

[0118] Please see Figure 7 , Figure 7 This application provides a specific description of an apparatus that supports access to multiple cloud servers, applicable to smart devices such as smart home devices. The smart home device includes an application layer and a service layer, with the service layer including cloud-based general logic firmware. One cloud server corresponds to one cloud platform, and multiple cloud servers correspond to multiple different cloud platforms. Figure 7 As shown, the device that supports access to multiple cloud servers may include: a calling module 401, a creation module 402, a node instantiation module 403, and an access module 404.

[0119] The calling module 401 is used to call the cloud general logic firmware in the service layer after the service layer receives the target cloud platform information passed by the application layer.

[0120] Module 402 is created to execute the cloud general logic firmware to create a cloud agent object.

[0121] The node instantiation module 403 is used to instantiate the target cloud configuration node corresponding to the target cloud server using the cloud proxy object according to the target cloud platform information. The target cloud configuration node includes a pre-encapsulated action set, which is obtained by abstracting the access actions of the smart home device to access multiple cloud servers.

[0122] Access module 404 is used to execute the access action in the action set to access the target cloud server corresponding to the cloud platform.

[0123] Among them, such as Figure 8 As shown, the access module 404 includes an acquisition unit 4041, a packet assembly unit 4042, and an access execution unit 4043. In another embodiment, the access module 404 further includes a return acquisition unit 4044, an unpacking unit 4045, and a sending unit 4046.

[0124] The acquisition unit 4041 is used to obtain the parameter information that needs to be processed for each access action in the pre-encapsulated action set using the cloud proxy object.

[0125] The packet assembly unit 4042 is used to assemble the parameter information into packets to obtain the packet output parameters of the access action.

[0126] The access execution unit 4043 is used to execute the access action according to the package output parameters in order to access the target cloud server corresponding to the target cloud platform.

[0127] The return acquisition unit 4044 is used to return the response result of the target cloud server after the access action is executed through the callback function of the access action.

[0128] The unpacking unit 4045 is used to obtain the response result using the cloud proxy object and unpack the response result to obtain the response unpacking result.

[0129] The sending unit 4046 is used to send the response unpacking result to the application layer.

[0130] The device may further include a channel instantiation module 405. The channel instantiation module 405 is used to instantiate multiple transmission channels according to multiple transmission channel protocols using the cloud proxy object after the cloud proxy object is created. Wherein, the access action includes connecting to the target cloud server, correspondingly, when the acquisition unit 4041 performs the step of obtaining the parameter information required for the access action using the cloud proxy object, it is specifically used to: obtain the transmission channel protocol types supported by the target cloud server using the cloud proxy object, to determine the target transmission channels supported by the transmission channel protocol types; obtain the server information of the target cloud server; and use the target transmission channel and the server information as the parameter information required for the access action.

[0131] The access action includes sending data to the target cloud server. Correspondingly, when the acquisition unit 4041 performs the step of obtaining the parameter information required for the access action using the cloud proxy object, it is specifically used to: use the cloud proxy object to listen to the application layer; when the parameter information passed in by the application layer is heard, acquire the parameter information and use the parameter information as the parameter information required for the access action.

[0132] The return acquisition unit 4044 is further configured to listen for operation instructions from the target cloud server using the cloud proxy object. The unpacking unit 4045 is further configured to unpack the operation instructions to obtain the instruction unpacking result. The sending unit 4046 is further configured to send the instruction unpacking result to the application layer.

[0133] In one embodiment, the smart home device further includes a default cloud configuration node, which includes a pre-encapsulated set of actions. The default cloud configuration node includes at least one cloud configuration node, and the target cloud configuration node includes at least one cloud configuration node. Correspondingly, the device further includes an acquisition module and a traversal module. The acquisition module is used to acquire all cloud configuration nodes, including the default cloud configuration node and the target cloud configuration node. The traversal module is used to traverse each of the all cloud configuration nodes. Correspondingly, the access module 404 is used to execute each access action in the action set corresponding to each cloud configuration node to access the cloud server corresponding to each cloud configuration node.

[0134] In practice, the above modules can be implemented as independent entities or combined arbitrarily as the same or several entities. For the specific implementation of the above modules, please refer to the previous method embodiments. For the specific beneficial effects that can be achieved, please also refer to the beneficial effects in the previous method embodiments, which will not be repeated here.

[0135] In addition, embodiments of this application also provide a smart device, such as a smart home device, such as... Figure 9 As shown, the smart device 500 includes a processor 501 and a memory 502. The smart device includes an application layer and a service layer, with the service layer including cloud-based general logic firmware. The processor 501 and the memory 502 are electrically connected.

[0136] The processor 501 is the control center of the smart device 500. It connects various parts of the smart device through various interfaces and lines. By running or loading applications stored in the memory 502 and calling data stored in the memory 502, it performs various functions of the smart device and processes data, thereby monitoring the smart device as a whole.

[0137] In this embodiment, the processor 501 in the smart device 500 loads the instructions corresponding to the processes of one or more applications into the memory 502 according to the following steps, and the processor 501 runs the applications / computer programs stored in the memory 502 to achieve various functions, such as:

[0138] After the service layer receives the target cloud platform information from the application layer, it calls the cloud general logic firmware in the service layer; executes the general program code in the cloud general logic firmware to create a cloud proxy object; according to the target cloud platform information, it instantiates the target cloud configuration node corresponding to the target cloud platform using the cloud proxy object. The target cloud configuration node includes a pre-encapsulated set of actions, which is obtained by abstracting the access actions of the smart home device to access multiple cloud servers; and executes the access actions in the set of actions to access the target cloud server corresponding to the target cloud platform.

[0139] This smart device can implement the steps in any embodiment of the method for supporting access to multiple cloud servers provided in the embodiments of this application. Therefore, it can achieve the beneficial effects that any method for supporting access to multiple cloud servers provided in the embodiments of this invention can achieve, as detailed in the preceding embodiments, which will not be repeated here.

[0140] Figure 10 A specific structural block diagram of a smart device provided in an embodiment of the present invention is shown. This smart device 600 can be used to implement the method for supporting access to multiple cloud servers provided in the above embodiments. The smart device 600 includes at least one module / unit other than memory and processor.

[0141] RF circuit 610 is used to receive and transmit electromagnetic waves, converting electromagnetic waves into electrical signals and vice versa, thereby enabling communication with communication networks or other devices. RF circuit 610 may include various existing circuit elements used to perform these functions, such as antennas, radio frequency transceivers, digital signal processors, encryption / decryption chips, subscriber identity modules (SIM cards), memory, etc. RF circuit 610 can communicate with various networks such as the Internet, corporate intranets, and wireless networks, or communicate with other devices via wireless networks. The aforementioned wireless networks may include cellular telephone networks, wireless local area networks (WLANs), or metropolitan area networks (MANs). The aforementioned wireless networks may use various communication standards, protocols, and technologies, including but not limited to Global System for Mobile Communication (GSM), Enhanced Data GSM Environment (EDGE), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Wireless Fidelity (Wi-Fi) (such as IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n), Voice over Internet Protocol (VoIP), Worldwide Interoperability for Microwave Access (Wi-Max), other protocols for email, instant messaging, and short messages, and any other suitable communication protocols, including those that have not yet been developed.

[0142] The memory 620 can be used to store software programs (computer programs) and modules, such as the program instructions / modules corresponding to those in the above embodiments. The processor 680 executes various functional applications and data processing by running the software programs and modules stored in the memory 620. The memory 620 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 620 may further include memory remotely located relative to the processor 680, and these remote memories can be connected to the smart device 600 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0143] In one embodiment, the smart device may further include an input unit 630, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control. Specifically, the input unit 630 may include a touch-sensitive surface 631 and other input devices 632. The touch-sensitive surface 631, also known as a touch display screen (touchscreen) or touchpad, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch-sensitive surface 631) and drive corresponding connection devices according to a pre-set program. Optionally, the touch-sensitive surface 631 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to the processor 680, and can receive and execute commands sent by the processor 680. In addition, the touch-sensitive surface 631 can be implemented using various methods such as resistive, capacitive, infrared, and surface acoustic wave. Besides the touch-sensitive surface 631, the input unit 630 may also include other input devices 632. Specifically, other input devices 632 may include, but are not limited to, one or more of the following: a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick.

[0144] In one embodiment, the smart device may further include a display unit 640, which can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of the smart device 600. These graphical user interfaces can be composed of graphics, text, icons, videos, and any combination thereof. The display unit 640 may include a display panel 641, which may optionally be configured as an LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or similar display. Further, a touch-sensitive surface 631 may cover the display panel 641. When the touch-sensitive surface 631 detects a touch operation on or near it, it transmits the information to the processor 680 to determine the type of touch event. Subsequently, the processor 680 provides corresponding visual output on the display panel 641 according to the type of touch event. Although in the figures, the touch-sensitive surface 631 and the display panel 641 are implemented as two separate components to achieve the input and output functions, it is understood that the touch-sensitive surface 631 and the display panel 641 can be integrated to achieve the input and output functions.

[0145] In one embodiment, the smart device 600 may further include at least one sensor 650, such as a light sensor, an orientation sensor, a proximity sensor, and other sensors. Other sensors that may be configured in the smart device 600, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0146] In one embodiment, the smart device 600 may further include an audio circuit 660, a speaker 661, etc. The audio circuit 660, speaker 661, and microphone 662 provide an audio interface between the user and the smart device 600. The audio circuit 660 can convert received audio data into electrical signals and transmit them to the speaker 661, where the speaker 661 converts them into sound signals for output. On the other hand, the microphone 662 converts collected sound signals into electrical signals, which are received by the audio circuit 660, converted into audio data, and then processed by the processor 680. After processing, the audio data is transmitted via the RF circuit 610 to another device, or the audio data is output to the memory 620 for further processing. The audio circuit 660 may also include an earphone jack to provide communication between peripheral headphones and the smart device 600.

[0147] The smart device 600, through a transmission module 670 (such as a Wi-Fi module), can help users receive requests and send information, providing users with wireless broadband internet access. Although the transmission module 670 is shown in the figure, it is understood that it is not an essential component of the smart device 600 and can be omitted as needed without changing the essence of the invention.

[0148] The processor 680 is the control center of the smart device 600. It connects to various parts of the phone via various interfaces and lines, and performs various functions and processes data of the smart device 600 by running or executing software programs (computer programs) and / or modules stored in the memory 620, and by calling data stored in the memory 620, thereby providing overall monitoring of the smart device. Optionally, the processor 680 may include one or more processing cores; in some embodiments, the processor 680 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into the processor 680.

[0149] In one embodiment, the smart device 600 also includes a power supply 690 (such as a battery) to power the various components. In some embodiments, the power supply can be logically connected to the processor 680 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 690 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0150] Although not shown, in some embodiments, the smart device 600 also includes a camera, a Bluetooth module, etc., which will not be described in detail here. Specifically, in this embodiment, the display unit of the smart device is a touch screen display, and the device also includes a memory and one or more programs (computer programs), wherein one or more programs are stored in the memory and configured to be executed by one or more processors. One or more programs contain instructions for performing the following operations:

[0151] After the service layer receives the target cloud platform information from the application layer, it calls the cloud general logic firmware in the service layer; executes the general program code in the cloud general logic firmware to create a cloud proxy object; according to the target cloud platform information, it instantiates the target cloud configuration node corresponding to the target cloud platform using the cloud proxy object. The target cloud configuration node includes a pre-encapsulated set of actions, which is obtained by abstracting the access actions of the smart home device to access multiple cloud servers; and executes the access actions in the set of actions to access the target cloud server corresponding to the target cloud platform.

[0152] In practice, the above modules can be implemented as independent entities or combined in any way to be implemented as the same or several entities. For the specific implementation of the above modules, please refer to the previous method implementation examples, which will not be repeated here.

[0153] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by instructions (computer programs) or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor. Therefore, embodiments of the present invention provide a storage medium storing multiple instructions that can be loaded by a processor to execute the steps of any embodiment of the method for supporting access to multiple cloud servers provided by the embodiments of the present invention.

[0154] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0155] Since the instructions stored in the storage medium can execute the steps in any embodiment of the method for supporting access to multiple cloud servers provided in the embodiments of the present invention, the beneficial effects that can be achieved in any embodiment of the method for supporting access to multiple cloud servers provided in the embodiments of the present invention can be realized, as detailed in the preceding embodiments, and will not be repeated here.

[0156] The foregoing has provided a detailed description of a method, apparatus, storage medium, and device for supporting access to multiple cloud servers, as provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for supporting access to multiple cloud servers, wherein, One cloud server corresponds to one cloud platform. The method is characterized by being applied to smart home devices, which include an application layer and a service layer. The service layer includes cloud-based general logic firmware. The method includes: After the service layer receives the target cloud platform information from the application layer, it invokes the cloud general logic firmware in the service layer. Execute the generic program code in the cloud generic logic firmware to create a cloud proxy object; Based on the target cloud platform information, the target cloud configuration node corresponding to the target cloud platform is instantiated using the cloud proxy object. The target cloud configuration node includes a pre-encapsulated set of actions, which is obtained by abstracting the access actions of the smart home device to multiple cloud servers. Execute the access action in the action set to access the target cloud server corresponding to the target cloud platform.

2. The method according to claim 1, characterized in that, The step of executing the access action in the action set to access the target cloud server corresponding to the target cloud platform includes: For each access action in the pre-encapsulated set of actions, the cloud proxy object is used to obtain the parameter information that the access action needs to process. The parameter information is packaged to obtain the packaged output parameters of the access action; The access action is executed according to the package output parameters to access the target cloud server corresponding to the target cloud platform.

3. The method according to claim 2, characterized in that, After accessing the target cloud server, the following is also included: The callback function of the access action returns the response result of the target cloud server after the access action is executed; The response result is obtained using the cloud proxy object, and the response result is unpacked to obtain the response unpacking result; The unpacking result of the response is sent to the application layer.

4. The method according to claim 2, characterized in that, The access action includes connecting to the target cloud server. After creating the cloud proxy object, the method further includes: The cloud proxy object is used to instantiate multiple transmission channels according to multiple transmission channel protocols; The step of obtaining the parameter information required for the access action using the cloud proxy object includes: The cloud proxy object is used to obtain the transmission channel protocol types supported by the target cloud server, so as to determine the target transmission channel supported by the transmission channel protocol types; Obtain the server information of the target cloud server; The target transmission channel and the server information are used as parameters required for the access action.

5. The method according to claim 2, characterized in that, The access action includes sending data to the target cloud server, and the step of obtaining the parameter information required for the access action using the cloud proxy object includes: Use the cloud proxy object to monitor the application layer; When the parameter information passed from the application layer is detected, the parameter information is obtained and used as the parameter information to be processed for the access action.

6. The method according to any one of claims 1 to 5, characterized in that, Also includes: The cloud proxy object is used to listen for operation commands from the target cloud server. The operation instruction is unpacked to obtain the instruction unpacking result. The unpacking result of the instruction is sent to the application layer.

7. The method according to claim 1, characterized in that, The smart home device also includes a default cloud configuration node, which includes a pre-encapsulated set of actions. The default cloud configuration node includes at least one cloud configuration node, and the target cloud configuration node includes at least one cloud configuration node. The method further includes: Obtain all cloud configuration nodes, including the default cloud configuration node and the target cloud configuration node; Iterate through each of the cloud configuration nodes in all the cloud configuration nodes; The step of executing each access action in the action set to access the target cloud server of the target cloud platform includes: executing each access action in the action set corresponding to each cloud configuration node to access the cloud server corresponding to each cloud configuration node.

8. An apparatus that supports access to multiple cloud servers, wherein, One cloud server corresponds to one cloud platform. The device is characterized in that it is applied in a smart home device, the smart home device including an application layer and a service layer, the service layer including cloud-based general logic firmware, and the device comprising: The calling module is used to call the cloud general logic firmware in the service layer after the service layer receives the target cloud platform information passed by the application layer; Create a module to execute the cloud general logic firmware to create a cloud proxy object; The node instantiation module is used to instantiate the target cloud configuration node corresponding to the target cloud server using the cloud proxy object based on the target cloud platform information. The target cloud configuration node includes a pre-encapsulated set of actions, which is obtained by abstracting the access actions of the smart home device to access multiple cloud servers. The access module is used to execute the access actions in the action set to access the target cloud server corresponding to the target cloud platform.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of instructions adapted for loading by a processor to perform the steps of the method for supporting access to multiple cloud servers as described in any one of claims 1 to 7.

10. A device, characterized in that, The method includes a processor and a memory, the processor being electrically connected to the memory, the memory being used to store instructions and data, and the processor being used to perform the steps of the method for supporting access to multiple cloud servers as described in any one of claims 1 to 7.

Images