WO2024109405A1 - 支持访问多个云服务器的方法、装置、存储介质及设备 - Google Patents

支持访问多个云服务器的方法、装置、存储介质及设备 Download PDF

Info

Publication number
WO2024109405A1
WO2024109405A1 PCT/CN2023/125325 CN2023125325W WO2024109405A1 WO 2024109405 A1 WO2024109405 A1 WO 2024109405A1 CN 2023125325 W CN2023125325 W CN 2023125325W WO 2024109405 A1 WO2024109405 A1 WO 2024109405A1
Authority
WO
WIPO (PCT)
Prior art keywords
cloud
access
target
action
target cloud
Prior art date
Application number
PCT/CN2023/125325
Other languages
English (en)
French (fr)
Inventor
袁文健
Original Assignee
深圳Tcl新技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳Tcl新技术有限公司 filed Critical 深圳Tcl新技术有限公司
Publication of WO2024109405A1 publication Critical patent/WO2024109405A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/2871—Implementation details of single intermediate entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/2885—Hierarchically arranged intermediate devices, e.g. for hierarchical caching

Definitions

  • the present application relates to the field of smart home technology, and in particular to a method, apparatus, storage medium and device for supporting access to multiple cloud servers.
  • a firmware in a smart home device can only connect to one cloud server/cloud platform. If it needs to connect to another cloud server/cloud platform, it needs to be re-adapted and another firmware needs to be re-generated in the smart home device.
  • These two firmwares belong to two different sets of codes. The corresponding two different sets of codes increase the development workload and subsequent code maintenance workload exponentially. If it is necessary to connect to more than two cloud servers/cloud platforms, the development difficulty and code maintenance difficulty are further increased.
  • the embodiments of the present application provide a method, apparatus, storage medium and device that support access to multiple cloud servers, which can support smart home devices to use one firmware to connect to multiple different cloud platforms, thereby improving firmware maintenance efficiency.
  • the embodiment of the present application provides a method for supporting access to multiple cloud servers, wherein one cloud server corresponds to one cloud platform, and the method is applied to a smart home device, wherein the smart home device includes an application layer and a service layer, and the service layer includes a cloud general logic firmware, and the method includes:
  • the cloud general logic firmware in the service layer is called
  • the target cloud configuration node corresponding to the target cloud platform is instantiated using the cloud proxy object, wherein the target cloud configuration node includes a pre-packaged action set, and the action set is obtained by abstracting the access actions of the smart home device to access multiple cloud servers;
  • the embodiment of the present application further provides a device supporting access to multiple cloud servers, wherein one cloud server corresponds to one cloud platform, and the device is applied to a smart home device, wherein the smart home device includes an application layer and a service layer, and the service layer includes a cloud general logic firmware, and the device includes:
  • a calling module configured to call the cloud general logic firmware in the service layer after the service layer receives the target cloud platform information transmitted by the application layer;
  • a creation module used for executing the cloud universal logic firmware to create a cloud proxy object
  • a node instantiation module configured to instantiate a target cloud configuration node corresponding to a target cloud server using the cloud proxy object according to the target cloud platform information, wherein the target cloud configuration node includes a pre-packaged action set, and the action set is obtained by abstracting access actions of the smart home device to access multiple cloud servers;
  • the access module is used to execute the access action in the action set to access the target cloud server corresponding to the target cloud platform.
  • An embodiment of the present application also provides a computer-readable storage medium, in which a plurality of instructions are stored.
  • the instructions are suitable for being loaded by a processor to execute the steps of any of the above-mentioned methods for supporting access to multiple cloud servers.
  • An embodiment of the present application also provides a device, including a processor and a memory, wherein the processor is electrically connected to the memory, the memory is used to store instructions and data, and the processor is used to perform the steps in any of the above-mentioned methods for supporting access to multiple cloud servers.
  • the method, device, storage medium and smart home device for supporting access to multiple cloud servers receive target cloud server information transmitted by the application layer through the service layer in the smart home device, call the cloud general logic firmware in the service layer, execute the processing logic in the cloud general logic firmware to create a cloud proxy object, and instantiate the target cloud configuration node corresponding to the target cloud server according to the target cloud server information using the cloud proxy object.
  • the target cloud configuration node includes a pre-packaged action set, which is obtained by abstracting the access actions of the smart home device accessing multiple cloud servers.
  • the target cloud configuration node includes the abstracted access actions of the smart home device accessing multiple cloud servers, no matter which cloud server among the multiple cloud servers the smart home device accesses, it can be achieved by instantiating the target cloud configuration node and executing the pre-packaged action set in the target cloud configuration node.
  • one cloud general logic firmware can be used to support the smart home device to connect to multiple different cloud platforms, thereby improving the efficiency of connecting to different cloud platforms.
  • only one cloud general logic firmware needs to be developed and maintained, thereby improving the code maintenance efficiency and development efficiency.
  • FIG1 is a schematic diagram of an application scenario provided in an embodiment of the present application.
  • FIG. 2 is a block diagram of the hierarchical structure of a smart home device provided in an embodiment of the present application.
  • FIG3 is a flow chart of a method for supporting access to multiple cloud servers provided in an embodiment of the present application.
  • FIG4 is a timing diagram of a method for supporting access to multiple cloud servers provided in an embodiment of the present application.
  • FIG5 is a flowchart of a method for supporting access to multiple cloud servers provided in an embodiment of the present application.
  • FIG. 6 is another flowchart of a method for supporting access to multiple cloud servers provided in an embodiment of the present application.
  • FIG. 7 is a schematic diagram of the structure of a device supporting access to multiple cloud servers provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of the structure of an access module provided in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of the structure of a smart device provided in an embodiment of the present application.
  • FIG. 10 is another schematic diagram of the structure of the smart device provided in an embodiment of the present application.
  • the embodiments of the present application provide a method, apparatus, storage medium, and smart device that support access to multiple cloud servers.
  • Any device that supports access to multiple cloud servers provided in the embodiments of the present application can be integrated in a smart device, which can be a smart home device, such as a smart refrigerator, a smart TV, a smart air conditioner, a smart curtain, a smart speaker, a smart sweeper, etc., and can also include other devices such as smart vehicle-mounted devices, wearable devices, and smart robots.
  • a smart home device such as a smart refrigerator, a smart TV, a smart air conditioner, a smart curtain, a smart speaker, a smart sweeper, etc.
  • the embodiments of the present application are described by taking the smart device as a smart home device as an example.
  • the cloud server in the embodiment of the present application refers to a cloud server in a cloud platform.
  • the cloud server can be an independent cloud server or a cloud server cluster.
  • one cloud server corresponds to one cloud platform, and multiple cloud servers correspond to multiple cloud platforms.
  • the firmware in the embodiment of the present application includes at least a program code for implementing communication between a smart home device and a cloud server corresponding to the smart home device.
  • the processing logic of the program code may include at least any one or more of 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, releasing/destroying the connection with the cloud server, etc.
  • the smart home device wants to connect to both cloud server A and cloud server B, it is necessary to integrate/install/deploy the firmware corresponding to cloud platform A and the firmware corresponding to cloud platform B in the smart home device. That is, the smart home device needs to integrate/install/deploy two different firmwares to connect to the cloud servers of two different cloud platforms. If the smart home device wants to connect to the cloud servers of more cloud platforms, it needs to integrate/install/deploy more different firmwares. This increases the difficulty of developing smart home devices and the program code in smart home devices, increasing the difficulty of code dimension. At the same time, when integrating/installing/deploying the firmware corresponding to other cloud platforms in smart home devices, the firmware corresponding to other cloud platforms may introduce third-party code libraries, which may have potential security issues, resulting in poor security and stability of smart home devices.
  • the embodiments of the present application provide a method, apparatus, storage medium and smart device that support access to multiple cloud servers. Only one firmware is needed to support smart home devices to access cloud servers of multiple cloud platforms, which reduces the difficulty of program code maintenance and improves the security and stability of smart home devices.
  • FIG1 is a schematic diagram of an application scenario provided in an embodiment of the present application.
  • a remote controller a smart home device, 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, and the mobile terminal is held by user A.
  • Cloud server A corresponds to cloud platform A
  • cloud server B corresponds to cloud platform B.
  • the remote controller is connected to the smart home device in communication, the smart home device is connected to the cloud server in communication, and the cloud server is connected to the mobile terminal in communication.
  • the mobile terminal corresponding to user A has an application corresponding to cloud platform A installed or integrated therein. After the smart home device is networked, it is connected to cloud server A through the method in the embodiment of the present application. After the mobile terminal corresponding to user A has an application corresponding to cloud platform B installed or integrated therein, the smart home device can be networked again and then connected to cloud server B through the method in the embodiment of the present application. In one embodiment, cloud server A and cloud server B can also be connected simultaneously through the method in the embodiment of the present application.
  • the smart home device can be controlled by the remote control, for example, the smart refrigerator can be controlled to increase the temperature.
  • the smart refrigerator increases the temperature of the smart refrigerator through the operation instruction sent by the remote control, and the increased temperature is synchronously sent to the cloud server.
  • the mobile terminal can remotely control the smart home device through the cloud server.
  • the mobile terminal remotely increases the temperature of the smart refrigerator through the cloud server.
  • the cloud server sends the operation instruction of increasing the temperature of the smart refrigerator to the smart home device. After the smart home device increases the temperature of the smart refrigerator, it synchronizes the temperature of the smart refrigerator to the remote control.
  • FIG2 is a block diagram of the hierarchical architecture of the smart home device provided in the embodiment of the present application.
  • the smart home device includes an application layer (app layer), a service layer (service layer) and a component layer (component layer).
  • the application layer communicates with the application (application) of the mobile terminal, the application layer can obtain the state machine of the smart home device, and the current various status information of the smart home device can be obtained from the state machine of the smart home device.
  • the service layer includes a cloud common logic handler, and the component layer includes common components (common components), such as various transmission interfaces, etc. The component layer will not be described below.
  • the cloud general logic firmware at least includes a general program code for communication between the smart home device and any cloud server among multiple cloud servers, and the general program code refers to a program code suitable for communicating with any cloud server among multiple cloud servers.
  • the general program code includes a general processing logic, and the general processing logic includes a processing logic suitable for communicating with any cloud server among multiple cloud servers, including but not limited to connecting to any cloud server among multiple cloud servers, registering with any cloud server among multiple cloud servers, sending data to any cloud server among multiple cloud servers, receiving data from any cloud server among multiple cloud servers, releasing/destroying the connection with any cloud server among multiple cloud servers, etc. Any one or more of the above.
  • the service layer includes cloud agent (cloud_agent) or cloud agent object, through which transmission channel (transmit channel) and cloud configuration node (cloud_profile) can be instantiated, where transmission channel includes Hyper Text Transfer Protocol (HTTP) channel, Message Queuing Telemetry Transport Protocol (MQTT) channel, Transmission Control Protocol (TCP) channel, User Datagram Protocol (UDP) channel, etc.
  • Cloud configuration node may include cloud configuration node A of cloud platform A, cloud configuration node B of cloud platform B, etc.
  • FIG 3 is a flow chart of a method for supporting access to multiple cloud servers in an embodiment of the present application.
  • the method is applied to smart devices such as smart home devices.
  • the smart home devices include an application layer and a service layer.
  • the service layer includes cloud general logic firmware.
  • the method specifically includes the following steps.
  • the service layer of the smart home device After the service layer of the smart home device receives the target cloud platform information transmitted by the application layer, it calls the cloud general logic firmware in the service layer.
  • Smart home devices generally use mobile terminals to configure the network.
  • Mobile terminals usually have applications corresponding to the cloud platform installed.
  • the network is configured through the application.
  • the smart home device configures the network, the smart home device will obtain the corresponding target cloud platform information through the application.
  • the target cloud platform information includes which cloud platform is currently corresponding, and further, such as the cloud platform type, for example, cloud platform A. After the smart home device obtains the cloud platform information, it is transmitted to the service layer through the application layer of the smart home device.
  • the service layer After receiving the target cloud platform information transmitted by the application layer, the service layer calls the cloud universal logic firmware in the service layer and transmits the target cloud platform information to the corresponding cloud universal logic firmware.
  • the cloud universal logic firmware can be pre-integrated/installed/deployed in the smart home device.
  • creating a cloud proxy object, instantiating a target cloud configuration node, executing access actions in the action set, etc. are all functions implemented by the general program code in the general logic firmware of the execution cloud. It can be understood that after the smart home device is successfully configured and connected to the network, it automatically creates a cloud proxy object, instantiates a target cloud configuration node, executes access actions in the action set, etc.
  • the application layer After the smart home device is connected to the network, the application layer sends a cloud agent creation request to the service layer.
  • the cloud agent creation request can be an epi_cloud_agent_create request, as shown in Figure 4.
  • the cloud agent creation request includes information such as the cloud platform type.
  • the service layer After receiving the cloud agent creation request, the service layer calls the structure of the cloud agent, which includes information such as the cloud platform type and resources related to the cloud agent, and creates a new cloud agent object cloud_agent according to the structure of the cloud agent, or it can also be understood as initializing the cloud agent object cloud_agent according to the structure of the cloud agent. A series of operations will be performed using the cloud agent object later.
  • a 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-packaged action set, which is obtained by abstracting the access actions of smart home devices accessing multiple cloud servers.
  • the target cloud configuration node refers to the node corresponding to the target cloud platform, which includes some configuration information of the target cloud server corresponding to the target cloud platform and a pre-packaged action set.
  • the configuration information includes the server information of the target cloud server, such as the URL and port number of the target cloud server, and the transmission channel protocol type supported by the target cloud server, such as the HTTP protocol.
  • the cloud proxy object instantiates/initializes the target cloud configuration node corresponding to the target cloud platform, for example, using the cloud_profile_init function to instantiate/initialize the target cloud configuration node, and initializes the configuration information and pre-packaged action set in the target cloud configuration node according to the target cloud platform information.
  • the pre-packaged action set is obtained by abstracting the access actions of smart home devices accessing multiple cloud servers. Abstraction refers to obtaining the common logic of each access action of multiple cloud servers, and access actions refer to various different operations/actions for interacting with 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, releasing/destroying the connection with a cloud server, etc. Since the action set is obtained by abstracting the access actions of smart home devices accessing multiple cloud servers, access to any one of the multiple cloud servers can be achieved through the action set, or the action set is suitable for achieving access to any one of the multiple cloud servers.
  • 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.
  • the target cloud configuration node includes the abstracted access actions of smart furniture devices to multiple cloud servers, no matter which cloud server the smart home device accesses, it can be achieved by instantiating the target cloud configuration node and executing the pre-packaged action set in the target cloud configuration node.
  • one cloud-general logic firmware can support smart home devices to connect to multiple different cloud platforms, thereby improving the efficiency of connecting to different cloud platforms.
  • only one cloud-general logic firmware needs to be developed and maintained, thereby improving code maintenance efficiency and development efficiency.
  • the method further includes step 103a .
  • the multiple transmission channel protocols may be the transmission channel protocols currently supported by multiple cloud servers, for example, cloud server A supports HTTP protocol, cloud server B supports MQTT protocol, and cloud server C supports TCP protocol.
  • the multiple transmission channel protocols include HTTP protocol, MQTT protocol, and TCP protocol.
  • the cloud proxy object is used to instantiate multiple transmission channels according to the multiple transmission channel protocols, for example, HTTP channel corresponding to HTTP protocol, MQTT channel corresponding to MQTT protocol, and TCP channel corresponding to TCP protocol, etc.
  • One transmission channel is instantiated for each transmission protocol.
  • the transmission channel protocol type supported by the specific target cloud server is not known at present, it is necessary to instantiate the transmission channel according to the transmission channel protocols supported by multiple cloud servers. After obtaining the transmission channel protocol type supported by the target cloud platform, determine the target transmission channel supported by the transmission channel protocol type from the transmission channels obtained after multiple instantiations. In some embodiments, after obtaining the transmission channel protocol type supported by the target cloud platform, the target transmission channel supported by the transmission channel protocol type can be instantiated according to the transmission channel protocol type. Then, the target cloud server is connected according to the target transmission channel, data is sent to the target cloud server, etc.
  • step 104 includes the following steps.
  • the step of using a cloud proxy object to obtain parameter information required for processing the access action includes: using the cloud proxy object to obtain the transmission channel protocol type supported by the target cloud server to determine the target transmission channel supported by the transmission channel protocol type; obtaining server information of the target cloud server; and using the target transmission channel and server information as parameter information required for processing the access action.
  • the step of using a cloud proxy object to obtain parameter information required for processing the access action includes: product information of smart home devices, such as product identification such as productKey, and device hardware address such as devicemac, etc., using the product identification and device hardware address as parameter information required for processing the access action, etc.
  • the step of using a cloud proxy object to obtain parameter information required for processing the access action includes: using the cloud proxy object to monitor the application layer, and when monitoring the parameter information passed in by the application layer, obtaining the parameter information, and using the parameter information as the parameter information required for processing the access action.
  • the parameter information includes status information of a smart home device, etc.
  • Packaging refers to packaging parameter information using a packaging function to package the parameter information into parameters that can be recognized by the target cloud server, namely, packaging output parameters, and outputting the packaging output parameters.
  • node->packet(action_step, out_pack_data1) in FIG. 4 is a packet assembly function, wherein action_step refers to the index number of an access action in the action set, and out_pack_data1 refers to the packet assembly output parameter.
  • the output parameter of the package assembly is used as the input parameter of the access action to execute the access action.
  • connect(out_pack_data1) in Figure 4 where connect refers to the connection function corresponding to the access action of connecting to the target cloud server, and out_pack_data1 is the output parameter of the package assembly obtained in the previous step. Execute connect to connect to the target cloud server corresponding to the target cloud platform.
  • the above step 104 further includes the following steps.
  • Each access action corresponds to a callback function, such as the callback function, which returns the response result out_conn_data of the target cloud server after executing the corresponding access action.
  • the callback function returns the connection result of connecting to the target cloud server.
  • the unpacking process includes identifying the response result of the target cloud server and performing format parsing and/or format conversion on the response result.
  • the unpacking process is implemented using an unpacking function, and the response unpacking result obtained after the processing is a result that can be recognized by the smart home device.
  • the response unpacking result refers to the result obtained by unpacking the response result.
  • node->unpack(action_step, out_conn_data) node->unpack is the unpacking function
  • action_step refers to the index number of the current corresponding access action
  • out_conn_data is the callback function of the previous connection function, which returns the connection result of connecting to the target cloud server.
  • the application layer will pass a callback function such as a callback function to the cloud proxy object. Therefore, after obtaining the response unpacking result, the response unpacking result is sent to the callback function of the application layer through the cloud proxy object, so that the application layer can perform subsequent operations. Subsequent operations, for example, send the connection result to the remote control to display the connection result on the remote control.
  • a callback function such as a callback function
  • the steps in this embodiment are steps that need to be executed for each access action, that is, first perform package assembly processing, use the package assembly output parameters obtained by the package assembly processing as input parameters of the access action, execute the access action, return the response result through the callback function, unpack the response result to obtain the response unpacking result, and send the response unpacking result to the application layer.
  • the action set includes at least one access action
  • the index number of the access action is increased by 1, for example, action_step is increased by 1, to execute the next access action.
  • FIG6 is a flow chart of a method for supporting access to multiple cloud servers provided in an embodiment of the present application. The method includes the following steps. Specifically, the method in this embodiment can be understood in conjunction with FIG4 .
  • the service layer of the smart home device after the service layer of the smart home device receives the target cloud platform information transmitted by the application layer, it calls the cloud general logic firmware in the service layer.
  • a 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-packaged action set, which is obtained by abstracting the access actions of smart home devices accessing multiple cloud servers.
  • the application layer before executing the access action of connecting to the target cloud server in the action set, the application layer needs to send a connection request to the service layer, and the connection request may be an epi_cloud_agent_connect request, as shown in FIG4 .
  • the service layer After receiving the connection request, the service layer triggers the access action of connecting to the target cloud server in the action set.
  • the access action of connecting to the target cloud server in the action set may be automatically executed without sending a connection request.
  • the response result includes a connection result
  • the connection result includes information such as connection success or connection failure.
  • the response unpacking result includes the connection unpacking result.
  • the parameter information for connecting to the target cloud server includes not only the target transmission channel and server information, but also the product information of the smart home device such as the product identification and the device hardware address, etc.
  • the product information of the smart home device is used to register with the target cloud server to complete the registration of the smart home device, as shown in FIG4 , which is this situation.
  • the response result includes a registration result, and the registration result includes information such as registration success or registration failure.
  • the response unpacking result includes the registration unpacking result.
  • Some target cloud servers may not return any registration result after the smart home device is successfully registered, that is, the registration result is empty, and some target cloud servers may return "registration successful" and other similar identification information.
  • the returned registration unpacking result is unpacked, such as parsing and/or format conversion, to obtain the registration unpacking result and send it to the application layer.
  • Steps 308 to 310 implement the access action of registering with the target cloud server.
  • the cloud proxy object After connecting to the target cloud server and registering with the target cloud server, the cloud proxy object is used to monitor the changes in the status information of the smart home device input by the application layer or monitor the operation instructions from the target cloud server, which involves the steps of data transmission between the smart home device and the target cloud server.
  • the parameter information transmitted by the application layer includes various status information of the smart home device, including but not limited to the power-on status, power-off status, temperature information of the current smart home device, mode information of the current smart home device, and the TV station of the current smart home device.
  • various operations are performed on the smart home device, such as turning on the smart home device, turning off the smart home device, raising the temperature, lowering the temperature, adjusting the mode, adjusting the TV station, etc., the corresponding status information of the smart home device will be generated, causing the status information of the smart home device to change.
  • the parameter information transmitted by the application layer may also include other parameter information, which may vary depending on the specific smart home device and will not be described in detail here.
  • the status information is transmitted to the service layer through the application layer of the smart home device, and is obtained by the cloud proxy object. After obtaining the status information, the status information is packaged to obtain the package output parameter.
  • the status information sent by the application layer is "1", which means the power-on state.
  • the package is packaged, "1" is converted into “power-on” that can be recognized by the target cloud server, and "power-on” is used as the package output parameter.
  • the same status information corresponding to different target cloud servers may have different representations, so it is packaged so that the same status information can be converted into information that can be recognized by different target cloud servers.
  • the power-on status information received by the application layer is "1”
  • the power-on status information corresponding to target cloud server A is "powered on”
  • the power-on status information corresponding to target cloud server B is "0”, etc.
  • the response result includes a processing response result. If the parameter information is various status information, the processing response result includes information such as status synchronization success or status synchronization failure.
  • the package output parameter is used as an input parameter of an access action for sending data to a target cloud server, so that the access action sends the package output parameter to the target cloud server, so that the target cloud server performs corresponding processing according to the package output parameter, such as synchronization processing.
  • transmit(out_pack_data2) is a sending function that sends data to the target cloud server, where out_pack_data2 is a packet output parameter obtained after packet processing by the packet assembly function node->packet(action_step, out_pack_data2), where the current index number of action_step in the packet assembly function is different from the index number of action_step in the connection target cloud server mentioned above.
  • the sending function transmit is used to implement the access action of sending data to the target cloud server, and receive the processing response result of the target cloud server returned by the callback function, which can be represented by out_recv_data.
  • steps 311 to 313 implement the access action of sending data to the target cloud server.
  • the cloud proxy object monitors the changes in the status information of the smart home device input by the application layer, the changes in the status information are sent to the target cloud server, so that the target cloud server synchronizes the status information of the smart home device.
  • the method further includes: using a cloud proxy object to monitor operation instructions from the target cloud server; unpacking the operation instructions to obtain an instruction unpacking result of the operation instructions; and sending the instruction unpacking result to the application layer.
  • the operation instruction may be an operation instruction sent by the mobile terminal to the target cloud server through remote control, and the operation instruction may implement any one of the various operations described above on the smart home device, for example, turning on the smart home device.
  • the cloud proxy object can listen to the corresponding operation instruction through the callback function such as callback function returned by the target cloud server. After receiving the operation instruction, the cloud proxy object unpacks the operation instruction and processes it into parameters that can be recognized by the application layer of the smart home device to obtain the instruction unpacking result of the operation instruction. For example, listen to the "power on" instruction returned by the target cloud server, call the node->unpack function to unpack it, process it as "1", and send it to the callback function of the application layer such as callback function.
  • the application layer will perform subsequent processing, such as turning on the smart device and synchronizing the power-on status to the remote control.
  • the unpacking process and the packing process in each of the above access actions appear in pairs, and the index number of each access action is increased by 1 after each access action is executed, that is, after the unpacking process is successful.
  • the smart home device further includes a default cloud configuration node, which also includes a pre-packaged action set, 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.
  • the target cloud configuration node includes one cloud configuration node, and the default cloud configuration node includes one cloud configuration node.
  • the method further includes: obtaining all cloud configuration nodes, which include a default cloud configuration node and a target cloud configuration node, traversing each cloud configuration node in all cloud configuration nodes, and executing each access action in the corresponding action set in each cloud configuration node to access the cloud server corresponding to each cloud configuration node.
  • At least two cloud servers of different cloud platforms can be connected at the same time, so that the smart home device can maintain communication connections with the cloud servers of two different cloud platforms, thereby improving the efficiency of connecting between cloud servers of different cloud platforms.
  • one cloud universal logic firmware can support smart home devices to connect to multiple different cloud platforms at the same time, thereby improving code maintenance efficiency and development efficiency.
  • this embodiment will be further described from the perspective of a device supporting access to multiple cloud servers.
  • the device supporting access to multiple cloud servers can be implemented as an independent entity or integrated in a smart device.
  • Figure 7 specifically describes the device for supporting access to multiple cloud servers provided by an embodiment of the present application, which is applied to smart devices such as smart home devices, wherein the smart home devices include an application layer and a service layer, and the service layer includes cloud general logic firmware.
  • one cloud server corresponds to one cloud platform
  • multiple cloud servers correspond to multiple different cloud platforms.
  • the device for supporting 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.
  • 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 transmitted by the application layer.
  • the creation module 402 is used to execute the cloud general logic firmware to create a cloud proxy object.
  • 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, wherein the target cloud configuration node includes a pre-packaged action set, and the action set is obtained by abstracting the access actions of the smart home device to access multiple cloud servers.
  • the 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.
  • the access module 404 includes an acquisition unit 4041, a packaging unit 4042, and an access execution unit 4043. In another embodiment, the access module 404 also includes a return acquisition unit 4044, an unpacking unit 4045, and a sending unit 4046.
  • the acquisition unit 4041 is used to use the cloud proxy object to acquire parameter information required to be processed for each access action in the pre-packaged action set.
  • the packaging unit 4042 is used to package the parameter information to obtain the packaged output parameters of the access action.
  • the access execution unit 4043 is used to execute the access action according to the package output parameter to access the target cloud server corresponding to the target cloud platform.
  • the return acquisition unit 4044 is used to return the response result of the target cloud server after executing the access action through the callback function of the access action.
  • the unpacking unit 4045 is used to obtain the response result by using the cloud proxy object, and unpack the response result to obtain a response unpacking result.
  • the sending unit 4046 is used to send the response unpacking result to the application layer.
  • 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 creating the cloud proxy object.
  • the access action includes connecting to the target cloud server.
  • the acquisition unit 4041 executes the step of using the cloud proxy object to obtain the parameter information required for processing the access action, it is specifically used to: use the cloud proxy object to obtain the transmission channel protocol type supported by the target cloud server to determine the target transmission channel supported by the transmission channel protocol type; 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 processing the access action.
  • the access action includes sending data to the target cloud server.
  • the acquisition unit 4041 executes the step of using the cloud proxy object to obtain the parameter information required for processing the access action, it is specifically used to: use the cloud proxy object to monitor the application layer; when the parameter information transmitted by the application layer is monitored, obtain the parameter information, and use the parameter information as the parameter information required for processing the access action.
  • the return acquisition unit 4044 is further used to use the cloud proxy object to monitor the operation instruction from the target cloud server.
  • the unpacking unit 4045 is further used to unpack the operation instruction to obtain the instruction unpacking result of the operation instruction.
  • the sending unit 4046 is further used to send the instruction unpacking result to the application layer.
  • the smart home device further includes a default cloud configuration node, the default cloud configuration node includes a pre-packaged action set, 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 device further includes an acquisition module and a traversal module, wherein the acquisition module is used to acquire all cloud configuration nodes, the all cloud configuration nodes include the default cloud configuration node and the target cloud configuration node, and the traversal module is used to traverse each cloud configuration node in the all cloud configuration nodes.
  • 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.
  • the above modules can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities.
  • the specific implementation of the above modules can refer to the previous method embodiments.
  • the specific beneficial effects that can be achieved can also refer to the beneficial effects in the previous method embodiments, which will not be repeated here.
  • the embodiment of the present application also provides a smart device such as a smart home device, as shown in FIG9 , the smart device 500 includes a processor 501 and a memory 502.
  • the smart device includes an application layer and a service layer, and the service layer includes a cloud general logic firmware.
  • the processor 501 is electrically connected to the memory 502.
  • Processor 501 is the control center of smart device 500. It uses various interfaces and lines to connect various parts of the entire smart device. It executes various functions of the smart device and processes data by running or loading applications stored in memory 502 and calling data stored in memory 502, thereby monitoring the smart device as a whole.
  • the processor 501 in the smart device 500 will load instructions corresponding to the processes of one or more applications into the memory 502 according to the following steps, and the processor 501 will run the application/computer program stored in the memory 502 to implement various functions, such as:
  • the cloud general logic firmware in the service layer is called; the general program code in the cloud general logic firmware is executed to create a cloud proxy object; according to the target cloud platform information, the cloud proxy object is used to instantiate a target cloud configuration node corresponding to the target cloud platform, wherein the target cloud configuration node includes a pre-packaged action set, and the action set is obtained by abstracting the access actions of the smart home device to access multiple cloud servers; the access actions in the action set are executed to access the target cloud server corresponding to the target cloud platform.
  • the smart device can implement the steps in any embodiment of the method for supporting access to multiple cloud servers provided in the embodiments of the present application. Therefore, it can achieve the beneficial effects that can be achieved by any method for supporting access to multiple cloud servers provided in the embodiments of the present invention. Please refer to the previous embodiments for details and will not be repeated here.
  • Fig. 10 shows a specific structural block diagram of a smart device provided in an embodiment of the present invention, and the smart device 600 can be used to implement the method for supporting access to multiple cloud servers provided in the above embodiment.
  • the smart device 600 includes at least one module/unit other than a memory and a processor.
  • the RF circuit 610 is used to receive and send electromagnetic waves, realize the mutual conversion between electromagnetic waves and electrical signals, and thus communicate with a communication network or other devices.
  • the RF circuit 610 may include various existing circuit elements for performing these functions, such as antennas, radio frequency transceivers, digital signal processors, encryption/decryption chips, user identity modules (SIM) cards, memories, etc.
  • the RF circuit 610 can communicate with various networks such as the Internet, corporate intranets, wireless networks, or communicate with other devices through wireless networks.
  • the above-mentioned wireless networks may include cellular telephone networks, wireless local area networks, or metropolitan area networks.
  • the above-mentioned wireless networks may use various communication standards, protocols, and technologies, including but not limited to the 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 Institute of Electrical and Electronics Engineers standards IEEE 802.11a, IEEE 802.11b, IEEE802.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 messaging, and any other suitable communication protocols, even those that have not yet been developed.
  • GSM Global System for Mobile Communication
  • EDGE Enhanced Data GSM Environment
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • Wi-Fi Wireless Fidelity
  • IEEE 802.11a Institute of Electrical and Electronics Engineers standards IEEE 802.11a,
  • the memory 620 can be used to store software programs (computer programs) and modules, such as the corresponding program instructions/modules 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 a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 620 may further include a memory remotely arranged relative to the processor 680, and these remote memories may be connected to the smart device 600 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • the smart device may further include an input unit 630, which may be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.
  • 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 (touch screen) or a touchpad, may collect user touch operations on or near it (such as operations performed by the user using any suitable object or accessory such as a finger, stylus, etc. on or near the touch-sensitive surface 631), and drive the corresponding connection device according to a pre-set program.
  • the touch-sensitive surface 631 may include a touch detection device and a touch controller.
  • the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into touch point coordinates, and then sends it to the processor 680, and can receive and execute commands sent by the processor 680.
  • the touch-sensitive surface 631 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave.
  • the input unit 630 may further include other input devices 632.
  • the other input devices 632 may include, but are not limited to, one or more of a physical keyboard, a function key (such as a volume control key, a switch key, etc.), a trackball, a mouse, a joystick, and the like.
  • a function key such as a volume control key, a switch key, etc.
  • a trackball such as a mouse, a joystick, and the like.
  • the smart device may further include a display unit 640, which may be used to display information input by a user or information provided to a user and various graphical user interfaces of the smart device 600, which may be composed of graphics, text, icons, videos, and any combination thereof.
  • the display unit 640 may include a display panel 641, and optionally, the display panel 641 may be configured in the form of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), etc.
  • the touch-sensitive surface 631 may cover the display panel 641, and when the touch-sensitive surface 631 detects a touch operation on or near it, it is transmitted to the processor 680 to determine the type of the touch event, and then the processor 680 provides a corresponding visual output on the display panel 641 according to the type of the touch event.
  • the touch-sensitive surface 631 and the display panel 641 are implemented as two independent components to implement the input and output functions, it can be understood that the touch-sensitive surface 631 is integrated with the display panel 641 to implement the input and output functions.
  • the smart device 600 may further include at least one sensor 650, such as a light sensor, a direction sensor, a proximity sensor, and other sensors.
  • sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., they are not described in detail here.
  • the smart device 600 may further include an audio circuit 660, a speaker 661, etc.
  • the audio circuit 660, the speaker 661, and the microphone 662 may provide an audio interface between the user and the smart device 600.
  • the audio circuit 660 may transmit the electrical signal converted from the received audio data to the speaker 661, which is converted into a sound signal for output; on the other hand, the microphone 662 converts the collected sound signal into an electrical signal, which is received by the audio circuit 660 and converted into audio data, and then the audio data is output to the processor 680 for processing, and then sent to another device through the RF circuit 610, or the audio data is output to the memory 620 for further processing.
  • the audio circuit 660 may also include an earplug jack to provide communication between an external headset and the smart device 600.
  • the smart device 600 can help users receive requests, send information, etc. through the transmission module 670 (such as a Wi-Fi module), which provides users with wireless broadband Internet access.
  • the transmission module 670 is shown in the figure, it is understandable that it is not a necessary component of the smart device 600 and can be omitted as needed without changing the essence of the invention.
  • the processor 680 is the control center of the smart device 600. It uses various interfaces and lines to connect various parts of the entire mobile phone. By running or executing software programs (computer programs) and/or modules stored in the memory 620, and calling data stored in the memory 620, it executes various functions of the smart device 600 and processes data, thereby monitoring the smart device as a whole.
  • 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 processes the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communications. It can be understood that the above-mentioned modem processor may not be integrated into the processor 680.
  • the smart device 600 further includes a power supply 690 (such as a battery) for supplying power to various components.
  • the power supply can be logically connected to the processor 680 through a power management system, so that the power management system can manage charging, discharging, and power consumption management.
  • the power supply 690 can also include any components such as one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, and power status indicators.
  • the smart device 600 further includes a camera, a Bluetooth module, etc., which will not be described in detail herein.
  • the display unit of the smart device is a touch screen display
  • the device further includes a memory, and one or more programs (computer programs), wherein one or more programs are stored in the memory and are configured to be executed by one or more processors.
  • One or more programs include instructions for performing the following operations:
  • the cloud general logic firmware in the service layer is called; the general program code in the cloud general logic firmware is executed to create a cloud proxy object; according to the target cloud platform information, the cloud proxy object is used to instantiate a target cloud configuration node corresponding to the target cloud platform, wherein the target cloud configuration node includes a pre-packaged action set, and the action set is obtained by abstracting the access actions of the smart home device to access multiple cloud servers; the access actions in the action set are executed to access the target cloud server corresponding to the target cloud platform.
  • the above modules can be implemented as independent entities, or can be arbitrarily combined and implemented as the same or several entities.
  • the specific implementation of the above modules can be found in the previous method embodiments, which will not be repeated here.
  • an embodiment of the present invention provides a storage medium in which multiple instructions are stored, and the instructions 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 an embodiment of the present invention.
  • the storage medium may include: read-only memory (ROM), random access memory (RAM), disk or CD, etc.
  • 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 achieved. Please refer to the previous embodiments for details and will not be repeated here.

Landscapes

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

Abstract

一种支持访问多个云服务器的方法包括：智能家居设备中的服务层接收应用层传入的目标云平台信息，并调用服务层中的云通用逻辑固件，执行云通用逻辑固件中的处理逻辑，根据目标云平台信息，利用云代理对象实例化目标云平台对应的目标云配置节点，执行动作集合中的访问动作。提高了连接不同云平台的效率。

Description

支持访问多个云服务器的方法、装置、存储介质及设备
本申请要求申请日为2022年11月25日、申请号为202211494503.X、发明名称为“支持访问多个云服务器的方法、装置、存储介质及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及智能家居技术领域，尤其涉及一种支持访问多个云服务器的方法、装置、存储介质及设备。
背景技术
随着物联网设备越来越普及，越来越多的企业参与到设备如智能家居设备的开发中来，而不同的企业会开发独有的云服务器/云平台，独有的手机应用程序，独有的智能家居设备端固件。
技术问题
智能家居设备中的一个固件只能连接一个云服务器/云平台，如果需要连接另外一个云服务器/云平台，需要重新适配，重新在智能家居设备中生成另外一个固件，这两个固件分别属于两套不同代码，对应的两套不同代码对于开发工作量以及后续代码维护工作量来说，都是成倍增加的；若需要连接两个以上的云服务器/云平台，更是进一步增加了开发难度和代码维护难度。
技术解决方案
本申请实施例提供一种支持访问多个云服务器的方法、装置、存储介质及设备，能支持智能家居设备使用一个固件连接多个不同的云平台，提高固件维护效率。
本申请实施例提供了一种支持访问多个云服务器的方法，其中，一个云服务器对应一个云平台，所述方法应用于智能家居设备中，所述智能家居设备中包括应用层和服务层，所述服务层中包括云通用逻辑固件，所述方法包括：
当所述服务层接收到所述应用层传入的目标云平台信息之后，调用所述服务层中的云通用逻辑固件；
执行所述云通用逻辑固件中的通用程序代码，以创建云代理对象；
根据所述目标云平台信息，利用所述云代理对象实例化目标云平台对应的目标云配置节点，所述目标云配置节点中包括预先封装的动作集合，所述动作集合是抽象所述智能家居设备访问多个云服务器的访问动作得到的；
执行所述动作集合中的访问动作，以访问所述目标云平台对应的目标云服务器。
本申请实施例还提供了一种支持访问多个云服务器的装置，其中，一个云服务器对应一个云平台，所述装置应用于智能家居设备中，所述智能家居设备中包括应用层和服务层，所述服务层中包括云通用逻辑固件，所述装置包括：
调用模块，用于当所述服务层接收到所述应用层传入的目标云平台信息之后，调用所述服务层中的云通用逻辑固件；
创建模块，用于执行所述云通用逻辑固件，以创建云代理对象；
节点实例化模块，用于根据所述目标云平台信息，利用所述云代理对象实例化目标云服务器对应的目标云配置节点，所述目标云配置节点中包括预先封装的动作集合，所述动作集合是抽象所述智能家居设备访问多个云服务器的访问动作得到的；
访问模块，用于执行所述动作集合中的访问动作，以访问所述目标云平台对应的目标云服务器。
本申请实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有多条指令，所述指令适于由处理器加载以执行上述任一项支持访问多个云服务器的方法的步骤。
本申请实施例还提供了一种设备，包括处理器和存储器，所述处理器与所述存储器电性连接，所述存储器用于存储指令和数据，所述处理器用于上述任一项所述的支持访问多个云服务器的方法中的步骤。
有益效果
本申请提供的支持访问多个云服务器的方法、装置、存储介质及智能家居设备，通过智能家居设备中的服务层接收应用层传入的目标云服务器信息，并调用服务层中的云通用逻辑固件，执行云通用逻辑固件中的处理逻辑，以创建云代理对象，根据目标云服务器信息，利用云代理对象实例化目标云服务器对应的目标云配置节点，该目标云配置节点中包括预先封装的动作集合，该动作集合是抽象智能家居设备访问多个云服务器的访问动作得到的，由于目标云配置节点中包括抽象出的智能家具设备访问多个云服务器的访问动作，因此，智能家居设备无论访问多个云服务器中的哪个云服务器，都可以通过实例化目标云配置节点，并执行目标云配置节点中预先封装的动作集合来实现，如此，使用一个云通用逻辑固件即可支持智能家居设备连接多个不同的云平台，提高了连接不同云平台的效率，同时只需要开发和维护一个云通用逻辑固件，提高了代码维护效率和开发效率。
附图说明
下面结合附图，通过对本申请的具体实施方式详细描述，将使本申请的技术方案及其它有益效果显而易见。
图1为本申请实施例提供的应用场景示意图。
图2为本申请实施例提供的智能家居设备的层级结构框图。
图3为本申请实施例提供的支持访问多个云服务器的方法的流程示意图。
图4为本申请实施例提供的支持访问多个云服务器的方法的时序示意图。
图5为本申请实施例提供的支持访问多个云服务器的方法的字流程示意图。
图6为本申请实施例提供的支持访问多个云服务器的方法的另一流程示意图。
图7为本申请实施例提供的支持访问多个云服务器的装置的结构示意图。
图8为本申请实施例提供的访问模块的结构示意图。
图9为本申请实施例提供的智能设备的结构示意图。
图10为本申请实施例提供的智能设备的另一结构示意图。
本发明的实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例提供一种支持访问多个云服务器的方法、装置、存储介质及智能设备。本申请实施例提供的任一种支持访问多个云服务器的装置，可以集成在智能设备中，该智能设备可以是智能家居设备，如包括智能冰箱、智能电视、智能空调、智能窗帘、智能音响、智能扫地机等，还可以包括智能车载设备、穿戴式设备、智能机器人等其他设备。本申请实施例以智能设备为智能家居设备为例进行说明。
本申请实施例中的云服务器指的是云平台中的云服务器，该云服务器可以是独立的云服务器，也可以是云服务器集群，对应地，一个云服务器对应一个云平台，多个云服务器对应多个云平台。
本申请实施例中的固件至少包括实现智能家居设备与智能家居设备对应的云服务器之间通信的程序代码，该程序代码的处理逻辑至少可以包括连接对应的云服务器、向对应的云服务器注册、向对应的云服务器发送数据、接收来自于云服务器的数据、释放/销毁与云服务器之间的连接等中的任意一个或多个。
由于多个云平台通常由不同企业提供，例如，企业A提供云平台A，企业B提供云平台B，由于是不同企业提供企业自己的云平台，因此，云平台中实现同样效果的实现逻辑和/或对应程序代码(也可称为计算机程序)存在差异，即云平台对应的固件存在不同。假设智能家居设备与云平台A合作或者智能家居设备由云平台A对应的企业生产，那么智能家居设备通过云平台A对应的固件连接云平台A对应的云服务器A，智能家居设备若想连接云平台B对应的云服务器B的话，那么则需要同时在智能家居设备中集成/安装/部署云平台B对应的固件。
因此，智能家居设备若想既能连接云服务器A，也能连接云服务器B，则需要在智能家居设备中集成/安装/部署云平台A对应的固件和云平台B对应的固件，即智能家居设备中需要集成/安装/部署两个不同的固件才可以连接两个不同的云平台的云服务器，智能家居设备中若想连接更多个云平台的云服务器，则需要集成/安装/部署更多个不同的固件。如此，导致智能家居设备的开发难度增加，也导致智能家居设备中的程序代码大量增加，增加了代码维度难度。同时在智能家居设备中集成/安装/部署其他云平台对应的固件时，其他云平台对应的固件中可能会引入第三方的代码库，这些代码库可能会存在潜在的安全性问题，导致智能家居设备的安全性和稳定性较差。
基于上述问题，本申请实施例提供了一种支持访问多个云服务器的方法、装置、存储介质及智能设备，只需提供一个固件即可支持智能家居设备访问多个云平台的云服务器，降低了程序代码维护难度，提高了智能家居设备的安全性和稳定性。
图1是本申请实施例中提供的应用场景示意图。在该应用场景中，包括遥控器、智能家居设备、云服务器和移动终端。其中，云服务器包括至少两个云服务器，如云服务器A和云服务器B，移动终端由用户A持有，云服务器A对应云平台A，云服务器B对应云平台B。遥控器与智能家居设备通信连接，智能家居设备与云服务器之间通信连接，云服务器与移动终端通信连接。
用户A对应的移动终端中安装或者集成有云平台A对应的应用程序，当智能家居设备配网后，通过本申请实施例中的方法连接云服务器A，当用户A对应的移动终端中安装或者集成有云平台B对应的应用程序之后，智能家居设备可重新配网，再通过本申请实施例中的方法连接云服务器B。在一实施例中，通过本申请实施例中的方法还可以同时连接云服务器A和云服务器B。
其中，通过遥控器可以对智能家居设备进行控制，例如，控制智能冰箱调高温度，智能冰箱通过遥控器发送的操作指令调高智能冰箱的温度，并将调高后的温度同步发送至云服务器。移动终端可以远程通过云服务器控制智能家居设备，例如，移动终端远程通过云服务器调高智能冰箱的温度，云服务器将调高智能冰箱温度的操作指令发送至智能家居设备，智能家居设备调高智能冰箱的温度后，并将智能冰箱的温度同步至遥控器。
图2为本申请实施例提供的智能家居设备的层级架构框图。如图2所示，智能家居设备中包括应用层(app layer)、服务层(service layer)和组件层(component layer)。其中，应用层与移动终端的应用程序(application)进行通信，应用层中可获取智能家居设备的状态机，从智能家居设备的状态机中可获取智能家居设备当前的各种状态信息，服务层中包括云通用逻辑固件(cloud common logic handler)，组件层中包括通用组件(common component)，如各种传输接口等，组件层在下文中将不再描述。
其中，云通用逻辑固件至少包括智能家居设备与多个云服务器中的任一云服务器之间通信的通用程序代码，该通用程序代码指的是适用于与多个云服务器中的任一云服务器之间进行通信的程序代码，该通用程序代码中包括了通用处理逻辑，该通用处理逻辑包括适用于与多个云服务器中的任一云服务器之间通信的处理逻辑，包括但不限于连接多个云服务器中的任一云服务器、向多个云服务器中的任一云服务器注册、向多个云服务器中的任一云服务器发送数据、接收来自于多个云服务器中的任一云服务器的数据、释放/销毁与多个云服务器中的任一云服务器之间的连接等中的任意一个或多个。
在服务层中包括云代理(cloud_agent)或者云代理对象，通过云代理可以实例化传输通道(transmit channel)，以及实例化云配置节点(cloud_profile)，其中，传输通道包括超文本传输协议(Hyper Text Transfer Protocol，HTTP)通道、消息队列遥测传输协议(Message Queuing Telemetry Transport，MQTT)通道、传输控制协议(Transmission Control Protocol，TCP)通道、用户数据报协议(User Datagram Protocol，UDP)通道等，云配置节点可包括云平台A的云配置节点A，云平台B的云配置节点B等。
图3是本申请实施例中的支持访问多个云服务器的方法的流程示意图，该方法应用于智能设备如智能家居设备中，该智能家居设备中包括应用层和服务层，服务层中包括云通用逻辑固件，该方法具体包括如下步骤。
101，当智能家居设备的服务层接收到应用层传入的目标云平台信息之后，调用服务层中的云通用逻辑固件。
当智能设备为智能家居设备时，在智能家居设备配网成功，智能家居设备连接上网络后，自动触发执行本申请实施例中的方法。智能家居设备一般通过移动终端来进行配网，移动终端中通常安装有云平台所对应的应用程序，通过应用程序来进行配网，当智能家居设备配网时，智能家居设备会通过应用程序获取对应的目标云平台信息，目标云平台信息中包括了当前对应的是哪个云平台，进一步地，如云平台类型，例如，云平台A。智能家居设备获取了云平台信息之后，通过智能家居设备的应用层传入至服务层。
服务层接收到应用层传入的目标云平台信息之后，调用服务层中的云通用逻辑固件，并将目标云平台信息传入至对应的云通用逻辑固件。其中，云通用逻辑固件可以预先集成/安装/部署在智能家居设备中。
102，执行云通用逻辑固件中的通用程序代码，以创建云代理对象。
其中，创建云代理对象、实例化目标云配置节点、执行动作集合中的访问动作等都是执行云通用逻辑固件中的通用程序代码实现的功能。可以理解地，智能家居设备配网成功，连接上网络后，自动实现创建云代理对象、实例化目标云配置节点、执行动作集合中的访问动作等。
其中，在智能家居设备连接上网络后，应用层向服务层发送云代理创建请求，例如，该云代理创建请求可以为epi_cloud_agent_create请求，如图4所示。该云代理创建请求中包括了云平台类型等信息，服务层接收到该云代理创建请求后，调用云代理的结构体，该结构体中包括云平台类型、以及云代理相关的资源等信息，根据云代理的结构体新建一个云代理对象cloud_agent，或者也可理解为根据云代理的结构体初始化云代理对象cloud_agent。后续将利用云代理对象进行一系列的操作。
103，根据目标云平台信息，利用云代理对象实例化目标云平台对应的目标云配置节点，该目标云配置节点中包括预先封装的动作集合，该动作集合是抽象智能家居设备访问多个云服务器的访问动作得到的。
其中，目标云配置节点指的是与目标云平台对应的节点，该目标云配置节点中包括目标云平台对应的目标云服务器的一些配置信息和预先封装的动作集合。其中，这些配置信息包括目标云服务器的服务器信息如目标云服务器的URL、端口号等，以及目标云服务器支持的传输通道协议类型，如HTTP协议。
云代理对象实例化/初始化目标云平台对应的目标云配置节点，例如使用cloud_profile_init函数来实例化/初始化目标云配置节点，并根据目标云平台信息初始化目标云配置节点中的配置信息和预先封装的动作集合。
其中，预先封装的动作集合是抽象智能家居设备访问多个云服务器的访问动作得到的。其中，抽象指的是得到多个云服务器的每个访问动作的共有通用逻辑，访问动作指的是与云服务器进行交互的各种不同操作/不同动作。例如，访问动作包括但不限于连接云服务器、向云服务器注册、向云服务器发送数据、接收来自于云服务器的数据、释放/销毁与云服务器之间的连接等。由于动作集合是抽象智能家居设备访问多个云服务器的访问动作得到的，因此，通过动作集合可以实现访问多个云服务器中的任意一个云服务器，或者说动作集合适用于实现访问多个云服务器中的任意一个云服务器。
104，执行动作集合中的访问动作，以访问目标云平台对应的目标云服务器。
对于任意一个云服务器来说，将目标云服务器的配置信息传入至动作集合中，执行动作集合中的访问动作，根据目标云服务器的配置信息访问目标云平台中的目标云服务器。
由于目标云配置节点中包括抽象出的智能家具设备访问多个云服务器的访问动作，因此，智能家居设备无论访问多个云服务器中的哪个云服务器，都可以通过实例化目标云配置节点，并执行目标云配置节点中预先封装的动作集合来实现，如此，使用一个云通用逻辑固件即可支持智能家居设备连接多个不同的云平台，提高了连接不同云平台的效率，同时只需要开发和维护一个云通用逻辑固件，提高了代码维护效率和开发效率。
在一实施例中，如图3所示，在创建云代理对象之后，所述方法还包括步骤103a。
103a，利用云代理对象根据多个传输通道协议实例化多个传输通道。
多个传输通道协议可以是当前多个云服务器支持的传输通道协议，例如，云服务器A支持HTTP协议，云服务器B支持MQTT协议，云服务器C支持TCP协议，如此，多个传输通道协议包括HTTP协议、MQTT协议和TCP协议，利用云代理对象根据多个传输通道协议实例化多个传输通道，例如，HTTP协议对应的HTTP通道、MQTT协议对应的MQTT通道、以及TCP协议对应的TCP通道等。每个传输协议对应实例化一个传输通道。
因为当前并不知晓具体的目标云服务器支持的传输通道协议类型，因此，此处需要根据多个云服务器支持的传输通道协议来实例化传输通道，在得到目标云平台支持的传输通道协议类型之后，从多个实例化之后得到的传输通道中确定与传输通道协议类型支持的目标传输通道。在一些实施例中，也可以在获取目标云平台支持的传输通道协议类型之后，再根据传输通道协议类型来实例化传输通道协议类型支持的目标传输通道。之后根据目标传输通道来连接目标云服务器、向目标云服务器发送数据等。
其中，如图5所示，上述104的步骤包括如下步骤。
201，对于预先封装的动作集合中的每一个访问动作，利用云代理对象获取访问动作所需处理的参数信息。
例如，对于连接目标云服务器的访问动作，所述利用云代理对象获取访问动作所需处理的参数信息的步骤，包括：利用云代理对象获取目标云服务器支持的传输通道协议类型，以确定传输通道协议类型支持的目标传输通道；获取目标云服务器的服务器信息；将目标传输通道和服务器信息作为访问动作所需处理的参数信息。
例如，对于向目标云服务器注册的访问动作，所述利用云代理对象获取访问动作所需处理的参数信息的步骤，包括：智能家居设备的产品信息，如产品标识如productKey、和设备硬件地址如devicemac等信息，将产品标识和设备硬件地址作为访问动作所需处理的参数信息等。
例如，对于向目标云服务器发送数据的访问动作，所述利用云代理对象获取访问动作所需处理的参数信息的步骤，包括：利用云代理对象监听应用层，当监听到应用层传入的参数信息时，获取参数信息，并将该参数信息作为访问动作所需处理的参数信息。例如，该参数信息包括智能家居设备的状态信息等。
202，将参数信息进行组包处理，以得到访问动作的组包输出参数。
组包处理指的是将参数信息进行封装处理，利用组包函数来进行组包处理，以将参数信息封装为目标云服务器可以识别的参数，即组包输出参数，并将组包输出参数进行输出。
例如，图4中的node->packet(action_step，out_pack_data1)即为一个组包函数，其中，action_step指的是动作集合中的某一个访问动作的索引号，out_pack_data1指的是组包输出参数。
203，根据组包输出参数执行访问动作，以访问目标云平台对应的目标云服务器。
将组包输出参数作为访问动作的输入参数，以执行访问动作。如图4中的connect(out_pack_data1)，其中，connect指的是连接目标云服务器的访问动作对应的连接函数，out_pack_data1即为上一步进行组包处理得到的组包输出参数。执行connect以连接目标云平台对应的目标云服务器。
在一实施例中，上述104的步骤还包括如下步骤。
204，通过访问动作的回调函数返回执行访问动作后目标云服务器的响应结果。
每个访问动作对应有一个回调函数，如callback函数，通过callback函数返回执行对应访问动作后目标云服务器的响应结果out_conn_data。如图4所示，connect的连接函数之后，紧接着callback函数返回的是连接目标云服务器的连接结果。
需要注意的是，有的目标云服务器可能返回连接结果，有的目标云服务器可能不返回连接结果。
205，利用云代理对象获取响应结果，并将响应结果进行解包处理，以得到响应解包结果。
其中，解包处理包括识别目标云服务器的响应结果，并将响应结果进行格式解析和/或格式转换等的处理。解包处理使用解包函数来实现，处理后得到的响应解包结果为智能家居设备可以识别的结果。
可以理解地，不同目标云服务器对于同一个访问动作的响应结果可能存在不同，例如，对于连接目标服务器的响应结果中，如果连接成功，有的服务器返回的是1，有的服务器返回的是“成功”等，因此，需要对响应结果进行解包处理，以得到响应解包结果。响应解包结果指的是对响应结果进行解包处理得到的结果。
如图4中的node->unpack(action_step，out_conn_data)，node->unpack即为解包函数，action_step指的是当前对应的访问动作的索引号，out_conn_data即为上一步连接函数的callback函数返回的是连接目标云服务器的连接结果。
206，将响应解包结果发送至应用层。
其中，应用层会传一个回调函数如callback函数给云代理对象，因此，得到响应解包结果之后，通过云代理对象将响应解包结果发送至应用层的callback函数，以使得应用层进行后续操作。后续操作例如将连接结果发送至遥控器，以在遥控器上显示连接结果等。
该实施例中的步骤是每个访问动作都需要执行的步骤，即先进行组包处理，将组包处理得到的组包输出参数作为访问动作的输入参数，执行访问动作，以通过回调函数返回响应结果，并将响应结果进行解包处理，以得到响应解包结果，并将响应解包结果发送至应用层。
其中，由于动作集合中包括至少一个访问动作，若动作集合中包括多个访问动作，则每执行完一个访问动作之后，将访问动作的索引号加1，例如将action_step加1，以执行下一 个访问动作。
图6是本申请实施例提供的支持访问多个云服务器的方法的流程示意图，该方法包括如下步骤，具体地，可结合图4一起来理解该实施例中的方法。
301，当智能家居设备的服务层接收到应用层传入的目标云平台信息之后，调用服务层中的云通用逻辑固件。
302，执行云通用逻辑固件中的通用程序代码，以创建云代理对象。
303，利用云代理对象根据多个传输通道协议实例化多个传输通道。
304，根据目标云平台信息，利用云代理对象实例化目标云平台对应的目标云配置节点，该目标云配置节点中包括预先封装的动作集合，该动作集合是抽象智能家居设备访问多个云服务器的访问动作得到的。
在一实施例中，在执行动作集合中的连接目标云服务器的访问动作之前，还需要应用层向服务层发送一个连接请求，该连接请求可以是epi_cloud_agent_connect请求，如图4所示，服务层接收到该连接请求后，触发执行动作集合中的连接目标云服务器的访问动作。在一些实施例中，也可以不发送连接请求，自动执行动作集合中的连接目标云服务器的访问动作。
305，利用云代理对象获取连接目标云平台的目标云服务器所需处理的目标传输通道和服务器信息，并将目标传输通道和服务器信息进行组包处理，以得到连接目标云服务器的组包输出参数。
306，根据组包输出参数执行连接目标云服务器的访问动作，以连接目标云服务器，并接收访问动作的回调函数返回的连接目标云服务器的连接结果。
其中，响应结果包括连接结果，连接结果包括连接成功或连接失败等信息。
307，利用云代理对象获取连接结果，将连接结果进行解包处理，以得到连接解包结果，并将连接解包结果发送至应用层。
其中，响应解包结果中包括连接解包结果。
通过步骤305至步骤307实现了连接目标云服务器的访问动作。在一实施例中，在连接目标云服务器的参数信息中除了包括目标传输通道和服务器信息之外，还包括智能家居设备的产品信息如产品标识和设备硬件地址等，如此，在连接上目标云服务器之后，紧接着利用智能家居设备的产品信息向目标云服务器注册，以完成智能家居设备的注册，如图4所示，即为该种情形。
308，利用云代理对象获取智能家居设备的产品信息，并将产品信息进行组包处理，以得到向目标云服务器注册的组包输出参数。
309，根据组包输出参数执行向目标云服务器注册的访问动作，并接收访问动作的回调函数返回的向目标云服务器注册的注册结果。
其中，响应结果包括注册结果，注册结果包括注册成功或注册失败等信息。
310，利用云代理对象获取注册结果，将注册结果进行解包处理，以得到注册解包结果，并将注册解包结果发送至应用层。
其中，响应解包结果中包括注册解包结果。其中，有些目标云服务器在智能家居设备注册成功后，可能不返回任何注册结果，即注册结果为空，有些目标云服务器可能返回“注册成功”等类似的标识信息等。将返回的注册解包结果进行解包处理如解析处理和/或格式转换等，以得到注册解包结果，并发送至应用层。
步骤308至步骤310实现了向目标云服务器注册的访问动作。连接目标云服务器且向目标云服务器注册之后，则后续则是利用云代理对象监听应用层输入的智能家居设备的状态信息的变化或者是监听来自于目标云服务器的操作指令，如此涉及智能家居设备与目标云服务器之间的数据传输的步骤。
311，利用云代理对象监听应用层，当监听到应用层传入的参数信息时，获取参数信息， 并将参数信息进行组包处理，以得到组包输出参数。
其中，应用层传入的参数信息包括智能家居设备的各种状态信息，各种状态信息包括但不限于开机状态、关机状态、当前智能家居设备的温度信息、当前智能家居设备所处的模式信息、智能家居设备当前所处的电视台等信息。只要是对智能家居设备进行各种操作，如打开智能家居设备、关闭智能家居设备、调高温度、调低温度、调整模式、调整电视台等等操作，都会生成对应的智能家居设备的状态信息，引起智能家居设备的状态信息的变化。
在一些实施例中，应用层传入的参数信息还可以包括其他的参数信息，根据具体智能家居设备的不同而存在不同，在此不再赘述。
该状态信息会通过智能家居设备的应用层传入服务层，并由云代理对象获取该状态信息。获取该状态信息后，将状态信息进行组包处理，以得到组包输出参数。例如，应用层发送的状态信息为“1”，1表示开机状态，进行组包处理之后，将“1”转换为目标云服务器可以识别的“开机”，并将“开机”作为组包输出参数。
需要注意的是，同样是开机状态，不同目标云服务器所对应的同一状态信息可能会有不同的表示，因此，将其进行组包处理，以使得将同一状态信息转换为不同目标云服务器可以识别的信息。例如，应用层接收到的开机的状态信息为“1”，目标云服务器A对应的开机的状态信息为“开机”，而目标云服务器B所对应的开机的状态信息为“0”等。
312，根据组包输出参数执行向目标云服务器发送数据的访问动作，并接收访问动作的回调函数返回的目标云服务器的处理响应结果。
其中，响应结果包括处理响应结果，若参数信息为各种状态信息，则处理响应结果包括状态同步成功或状态同步失败等信息。
例如，将组包输出参数作为向目标云服务器发送数据的访问动作的输入参数，以使得访问动作将该组包输出参数发送至目标云服务器，以使得目标云服务器根据组包输出参数进行相应处理，如同步处理等。
如图4中，transmit(out_pack_data2)即为向目标云服务器发送数据的发送函数，其中，out_pack_data2是通过组包函数node->packet(action_step，out_pack_data2)进行组包处理后得到的组包输出参数，其中，组包函数中的action_step当前的索引号与上文中的连接目标云服务器中的action_step的索引号不同。通过该发送函数transmit实现向目标云服务器发送数据的访问动作，并接收callback函数返回的目标云服务器的处理响应结果，该处理响应结果可以用out_recv_data来表示。
313，利用云代理对象获取处理响应结果，将处理响应结果进行解包处理，以得到处理解包结果，并将处理解包结果发送至应用层。
其中，步骤311至步骤313实现了向目标云服务器发送数据的访问动作。当云代理对象监听应用层输入的智能家居设备的状态信息的变化时，将状态信息的变化发送至目标云服务器，以使得目标云服务器进行智能家居设备的状态信息的同步。
在一实施例中，在智能家居设备连接目标云服务器且向目标云服务器注册之后，所述方法还包括：利用云代理对象监听来自于目标云服务器的操作指令；将操作指令进行解包处理，以得到操作指令的指令解包结果；将指令解包结果发送至应用层。
其中，该操作指令可以是移动终端通过远程控制时向目标云服务器发送的操作指令，该操作指令可以实现对智能家居设备进行上述所述的各种操作中的任意一个操作。例如，打开智能家居设备等。
云代理对象可通过目标云服务器返回的回调函数如callback函数来监听对应的操作指令，云代理对象接收到操作指令后，将操作指令进行解包处理，处理为智能家居设备的应用层可以识别的参数，以得到操作指令的指令解包结果。例如，监听目标云服务器返回的“开机”指令，调用node->unpack函数来进行解包处理，处理为“1”，并发送至应用层的回调函数如callback函数。应用层将进行后续处理，如将智能设备进行开机，并将开机状态同步至遥控器等。
需要注意的是，在一实施例中，上述每一个访问动作中的解包处理和组包处理都是成对出现，每一个访问动作执行完了，即解包处理成功之后都会将访问动作的索引号加1。
在一实施例中，智能家居设备中还包括默认云配置节点，该默认云配置节点中也包括预先封装的动作集合，即除了默认云配置节点之外，还包括目标云配置节点。目标云配置节点中包括至少一个云配置节点，默认云配置节点中包括至少一个云配置节点，一般情况下，目标云配置节点中包括一个云配置节点，默认云配置节点中包括一个云配置节点。
在一实施例中，在得到目标云配置节点之后，所述方法还包括：获取所有云配置节点，该所有云配置节点包括默认云配置节点和目标云配置节点，遍历所有云配置节点中的每一个云配置节点，执行每一个云配置节点中对应的动作集合中的每一个访问动作，以访问每一个云配置节点对应的云服务器。
该实施例中可以同时连接至少两个不同的云平台的云服务器，使得智能家居设备可以保持与两个不同云平台的云服务器之间的通信连接，提高了连接不同云平台的云服务器之间的效率，同时使用一个云通用逻辑固件即可支持智能家居设备同时连接多个不同的云平台，提高了代码维护效率和开发效率。
根据上述实施例所描述的方法，本实施例将从支持访问多个云服务器的装置的角度进一步进行描述，该支持访问多个云服务器的装置具体可以作为独立的实体来实现，也可以集成在智能设备中来实现。
请参阅图7，图7具体描述了本申请实施例提供的支持访问多个云服务器的装置，应用于智能设备如智能家居设备中，该智能家居设备中包括应用层和服务层，所述服务层中包括云通用逻辑固件。其中，一个云服务器对应一个云平台，多个云服务器对应多个不同的云平台。如图7所示，该支持访问多个云服务器的装置可以包括：调用模块401、创建模块402、节点实例化模块403、访问模块404。
调用模块401，用于当所述服务层接收到所述应用层传入的目标云平台信息之后，调用所述服务层中的云通用逻辑固件。
创建模块402，用于执行所述云通用逻辑固件，以创建云代理对象。
节点实例化模块403，用于根据所述目标云平台信息，利用所述云代理对象实例化目标云服务器对应的目标云配置节点，所述目标云配置节点中包括预先封装的动作集合，所述动作集合是抽象所述智能家居设备访问多个云服务器的访问动作得到的。
访问模块404，用于执行所述动作集合中的访问动作，以访问所述云平台对应的目标云服务器。
其中，如图8所示，访问模块404包括获取单元4041、组包单元4042、访问执行单元4043。在另一实施例中，访问模块404还包括返回获取单元4044、解包单元4045以及发送单元4046。
获取单元4041，用于对于预先封装的动作集合中的每一个访问动作，利用所述云代理对象获取所述访问动作所需处理的参数信息。
组包单元4042，用于将所述参数信息进行组包处理，以得到所述访问动作的组包输出参数。
访问执行单元4043，用于根据所述组包输出参数执行所述访问动作，以访问所述目标云平台对应的目标云服务器。
返回获取单元4044，用于通过所述访问动作的回调函数返回执行所述访问动作后所述目标云服务器的响应结果。
解包单元4045，用于利用所述云代理对象获取所述响应结果，并将所述响应结果进行解包处理，以得到响应解包结果。
发送单元4046，用于将所述响应解包结果发送至所述应用层。
其中，所述装置还可以包括通道实例化模块405。通道实例化模块405，用于在创建云代理对象之后，利用所述云代理对象根据多个传输通道协议实例化多个传输通道。其中，访问动作包括连接所述目标云服务器，对应地，获取单元4041在执行利用所述云代理对象获取所述访问动作所需处理的参数信息的步骤时，具体用于：利用所述云代理对象获取所述目标云服务器支持的传输通道协议类型，以确定所述传输通道协议类型支持的目标传输通道；获取所述目标云服务器的服务器信息；将所述目标传输通道和所述服务器信息作为所述访问动作所需处理的参数信息。
其中，访问动作包括向所述目标云服务器发送数据，对应地，获取单元4041在执行利用所述云代理对象获取所述访问动作所需处理的参数信息的步骤时，具体用于：利用所述云代理对象监听所述应用层；当监听到所述应用层传入的参数信息时，获取所述参数信息，并将所述参数信息作为所述访问动作所需处理的参数信息。
其中，返回获取单元4044，还用于利用所述云代理对象监听来自于所述目标云服务器的操作指令。解包单元4045，还用于将所述操作指令进行解包处理，以得到所述操作指令的指令解包结果。以及发送单元4046，还用于将述指令解包结果发送至所述应用层。
其中，在一实施例中，所述智能家居设备中还包括默认云配置节点，所述默认云配置节点中包括预先封装的动作集合，所述默认云配置节点中包括至少一个云配置节点，所述目标云配置节点中包括至少一个云配置节点。对应地，所述装置还包括获取模块和遍历模块，其中，获取模块，用于获取所有云配置节点，所述所有云配置节点包括默认云配置节点和目标云配置节点，遍历模块，用于遍历所述所有云配置节点中的每一个云配置节点。对应地，访问模块404，用于执行每一个云配置节点中对应的所述动作集合中的每一个访问动作，以访问每一个云配置节点对应的云服务器。
具体实施时，以上各个模块可以作为独立的实体来实现，也可以进行任意组合，作为同一或若干个实体来实现，以上各个模块的具体实施可参见前面的方法实施例，具体可以达到的有益效果也请参看前面的方法实施例中的有益效果，在此不再赘述。
另外，本申请实施例还提供一种智能设备如智能家居设备，如图9所示，智能设备500包括处理器501、存储器502。在智能设备中包括应用层和服务层，服务层中包括云通用逻辑固件。其中，处理器501与存储器502电性连接。
处理器501是智能设备500的控制中心，利用各种接口和线路连接整个智能设备的各个部分，通过运行或加载存储在存储器502内的应用程序，以及调用存储在存储器502内的数据，执行智能设备的各种功能和处理数据，从而对智能设备进行整体监控。
在本实施例中，智能设备500中的处理器501会按照如下的步骤，将一个或一个以上的应用程序的进程对应的指令加载到存储器502中，并由处理器501来运行存储在存储器502中的应用程序/计算机程序，从而实现各种功能，如：
当所述服务层接收到所述应用层传入的目标云平台信息之后，调用所述服务层中的云通用逻辑固件；执行所述云通用逻辑固件中的通用程序代码，以创建云代理对象；根据所述目标云平台信息，利用所述云代理对象实例化目标云平台对应的目标云配置节点，所述目标云配置节点中包括预先封装的动作集合，所述动作集合是抽象所述智能家居设备访问多个云服务器的访问动作得到的；执行所述动作集合中的访问动作，以访问所述目标云平台对应的目标云服务器。
该智能设备可以实现本申请实施例所提供的支持访问多个云服务器的方法任一实施例中的步骤，因此，可以实现本发明实施例所提供的任一支持访问多个云服务器的方法所能实现的有益效果，详见前面的实施例，在此不再赘述。
图10示出了本发明实施例提供的智能设备的具体结构框图，该智能设备600可以用于实施上述实施例中提供的支持访问多个云服务器的方法。该智能设备600包括以下中的除存储器和处理器之外的至少一个模块/单元。
RF电路610用于接收以及发送电磁波，实现电磁波与电信号的相互转换，从而与通讯网络或者其他设备进行通讯。RF电路610可包括各种现有的用于执行这些功能的电路元件，例如，天线、射频收发器、数字信号处理器、加密/解密芯片、用户身份模块(SIM)卡、存储器等等。RF电路610可与各种网络如互联网、企业内部网、无线网络进行通讯或者通过无线网络与其他设备进行通讯。上述的无线网络可包括蜂窝式电话网、无线局域网或者城域网。上述的无线网络可以使用各种通信标准、协议及技术，包括但并不限于全球移动通信系统(Global System for Mobile Communication，GSM)、增强型移动通信技术(Enhanced Data GSM Environment，EDGE)，宽带码分多址技术(Wideband Code Division Multiple Access，WCDMA)，码分多址技术(Code Division Access，CDMA)、时分多址技术(Time Division Multiple Access，TDMA)，无线保真技术(Wireless Fidelity，Wi-Fi)(如美国电气和电子工程师协会标准IEEE 802.11a，IEEE 802.11b，IEEE802.11g和/或IEEE 802.11n)、网络电话(Voice over Internet Protocol，VoIP)、全球微波互联接入(Worldwide Interoperability for Microwave Access，Wi-Max)、其他用于邮件、即时通讯及短消息的协议，以及任何其他合适的通讯协议，甚至可包括那些当前仍未被开发出来的协议。
存储器620可用于存储软件程序(计算机程序)以及模块，如上述实施例中对应的程序指令/模块，处理器680通过运行存储在存储器620内的软件程序以及模块，从而执行各种功能应用以及数据处理。存储器620可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器620可进一步包括相对于处理器680远程设置的存储器，这些远程存储器可以通过网络连接至智能设备600。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
在一实施例中，智能设备还可以包括输入单元630，输入单元630可用于接收输入的数字或字符信息，以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、光学或者轨迹球信号输入。具体地，输入单元630可包括触敏表面631以及其他输入设备632。触敏表面631，也称为触摸显示屏(触摸屏)或者触控板，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触敏表面631上或在触敏表面631附近的操作)，并根据预先设定的程式驱动相应的连接装置。可选的，触敏表面631可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器680，并能接收处理器680发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触敏表面631。除了触敏表面631，输入单元630还可以包括其他输入设备632。具体地，其他输入设备632可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆等中的一种或多种。
在一实施例中，智能设备还可以包括显示单元640，显示单元640可用于显示由用户输入的信息或提供给用户的信息以及智能设备600的各种图形用户接口，这些图形用户接口可以由图形、文本、图标、视频和其任意组合来构成。显示单元640可包括显示面板641，可选的，可以采用LCD(Liquid Crystal Display，液晶显示器)、OLED(Organic Light-Emitting Diode，有机发光二极管)等形式来配置显示面板641。进一步的，触敏表面631可覆盖显示面板641，当触敏表面631检测到在其上或附近的触摸操作后，传送给处理器680以确定触摸事件的类型，随后处理器680根据触摸事件的类型在显示面板641上提供相应的视觉输出。虽然在图中，触敏表面631与显示面板641是作为两个独立的部件来实现输入和输出功能，但是可以理解地，将触敏表面631与显示面板641集成而实现输入和输出功能。
在一实施例中，智能设备600还可包括至少一种传感器650，比如光传感器、方向传感器、接近传感器以及其他传感器。至于智能设备600还可配置的陀螺仪、气压计、湿度计、温度计、红外线传感器等其他传感器，在此不再赘述。
在一实施例中，智能设备600还可以包括音频电路660、扬声器661等，音频电路660、扬声器661，传声器662可提供用户与智能设备600之间的音频接口。音频电路660可将接收到的音频数据转换后的电信号，传输到扬声器661，由扬声器661转换为声音信号输出；另一方面，传声器662将收集的声音信号转换为电信号，由音频电路660接收后转换为音频数据，再将音频数据输出处理器680处理后，经RF电路610以发送给比如另一设备，或者将音频数据输出至存储器620以便进一步处理。音频电路660还可能包括耳塞插孔，以提供外设耳机与智能设备600的通信。
智能设备600通过传输模块670(例如Wi-Fi模块)可以帮助用户接收请求、发送信息等，它为用户提供了无线的宽带互联网访问。虽然图示出了传输模块670，但是可以理解的是，其并不属于智能设备600的必须构成，完全可以根据需要在不改变发明的本质的范围内而省略。
处理器680是智能设备600的控制中心，利用各种接口和线路连接整个手机的各个部分，通过运行或执行存储在存储器620内的软件程序(计算机程序)和/或模块，以及调用存储在存储器620内的数据，执行智能设备600的各种功能和处理数据，从而对智能设备进行整体监控。可选的，处理器680可包括一个或多个处理核心；在一些实施例中，处理器680可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解地，上述调制解调处理器也可以不集成到处理器680中。
在一实施例中，智能设备600还包括给各个部件供电的电源690(比如电池)，在一些实施例中，电源可以通过电源管理系统与处理器680逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。电源690还可以包括一个或一个以上的直流或交流电源、再充电系统、电源故障检测电路、电源转换器或者逆变器、电源状态指示器等任意组件。
尽管未示出，在一些实施例中，智能设备600还包括摄像头、蓝牙模块等，在此不再赘述。具体在本实施例中，智能设备的显示单元是触摸屏显示器，设备还包括有存储器，以及一个或者一个以上的程序(计算机程序)，其中一个或者一个以上程序存储于存储器中，且经配置以由一个或者一个以上处理器执行一个或者一个以上程序包含用于进行以下操作的指令：
当所述服务层接收到所述应用层传入的目标云平台信息之后，调用所述服务层中的云通用逻辑固件；执行所述云通用逻辑固件中的通用程序代码，以创建云代理对象；根据所述目标云平台信息，利用所述云代理对象实例化目标云平台对应的目标云配置节点，所述目标云配置节点中包括预先封装的动作集合，所述动作集合是抽象所述智能家居设备访问多个云服务器的访问动作得到的；执行所述动作集合中的访问动作，以访问所述目标云平台对应的目标云服务器。
具体实施时，以上各个模块可以作为独立的实体来实现，也可以进行任意组合，作为同一或若干个实体来实现，以上各个模块的具体实施可参见前面的方法实施例，在此不再赘述。
本领域普通技术人员可以理解，上述实施例的各种方法中的全部或部分步骤可以通过指令(计算机程序)来完成，或通过指令控制相关的硬件来完成，该指令可以存储于一计算机可读存储介质中，并由处理器进行加载和执行。为此，本发明实施例提供一种存储介质，其中存储有多条指令，该指令能够被处理器进行加载，以执行本发明实施例所提供的支持访问多个云服务器的方法中任一实施例的步骤。
其中，该存储介质可以包括：只读存储器(ROM，Read Only Memory)、随机存取记忆体(RAM，Random Access Memory)、磁盘或光盘等。
由于该存储介质中所存储的指令，可以执行本发明实施例所提供的支持访问多个云服务器的方法任一实施例中的步骤，因此，可以实现本发明实施例所提供的支持访问多个云服务器的方法任一实施例中所能实现的有益效果，详见前面的实施例，在此不再赘述。
以上对本申请实施例所提供的一种支持访问多个云服务器的方法、装置、存储介质和设备进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (20)

  1. 一种支持访问多个云服务器的方法，其中，一个云服务器对应一个云平台，其中，所述方法应用于智能家居设备中，所述智能家居设备中包括应用层和服务层，所述服务层中包括云通用逻辑固件，所述方法包括：
    当所述服务层接收到所述应用层传入的目标云平台信息之后，调用所述服务层中的云通用逻辑固件；
    执行所述云通用逻辑固件中的通用程序代码，以创建云代理对象；
    根据所述目标云平台信息，利用所述云代理对象实例化目标云平台对应的目标云配置节点，所述目标云配置节点中包括预先封装的动作集合，所述动作集合是抽象所述智能家居设备访问多个云服务器的访问动作得到的；
    执行所述动作集合中的访问动作，以访问所述目标云平台对应的目标云服务器。
  2. 根据权利要求1所述的方法，其中，所述执行所述动作集合中的访问动作，以访问所述目标云平台对应的目标云服务器的步骤，包括：
    对于预先封装的动作集合中的每一个访问动作，利用所述云代理对象获取所述访问动作所需处理的参数信息；
    将所述参数信息进行组包处理，以得到所述访问动作的组包输出参数；
    根据所述组包输出参数执行所述访问动作，以访问所述目标云平台对应的目标云服务器。
  3. 根据权利要求2所述的方法，其中，在访问所述目标云服务器之后，还包括：
    通过所述访问动作的回调函数返回执行所述访问动作后所述目标云服务器的响应结果；
    利用所述云代理对象获取所述响应结果，并将所述响应结果进行解包处理，以得到响应解包结果；
    将所述响应解包结果发送至所述应用层。
  4. 根据权利要求2所述的方法，其中，所述访问动作包括连接所述目标云服务器，在创建云代理对象之后，所述方法还包括：
    利用所述云代理对象根据多个传输通道协议实例化多个传输通道；
    所述利用所述云代理对象获取所述访问动作所需处理的参数信息的步骤，包括：
    利用所述云代理对象获取所述目标云服务器支持的传输通道协议类型，以确定所述传输通道协议类型支持的目标传输通道；
    获取所述目标云服务器的服务器信息；
    将所述目标传输通道和所述服务器信息作为所述访问动作所需处理的参数信息。
  5. 根据权利要求2所述的方法，其中，所述访问动作包括向所述目标云服务器发送数据，所述利用所述云代理对象获取所述访问动作所需处理的参数信息的步骤，包括：
    利用所述云代理对象监听所述应用层；
    当监听到所述应用层传入的参数信息时，获取所述参数信息，并将所述参数信息作为所述访问动作所需处理的参数信息。
  6. 根据权利要求1至5任一项所述的方法，其中，还包括：
    利用所述云代理对象监听来自于所述目标云服务器的操作指令；
    将所述操作指令进行解包处理，以得到所述操作指令的指令解包结果；
    将所述指令解包结果发送至所述应用层。
  7. 根据权利要求4所述的方法，其中，在所述将所述目标传输通道和所述服务器信息作为所述访问动作所需处理的参数信息之后，还包括：
    根据连接所述目标云服务器的组包输出参数执行连接所述目标云服务器的访问动作，以连接所述目标云服务器，并接收所述连接所述目标云服务器的访问动作的回调函数返回的连接所述目标云服务器的连接结果；
    利用所述云代理对象获取所述连接结果，将所述连接结果进行解包处理，以得到连接解包结果，并将所述连接解包结果发送至所述应用层。
  8. 根据权利要求7所述的方法，其中，在所述利用所述云代理对象获取所述连接结果，将所述连接结果进行解包处理，以得到连接解包结果，并将所述连接解包结果发送至所述应用层之后，还包括：
    利用所述云代理对象获取智能家居设备的产品信息，并将所述产品信息进行组包处理，以得到向所述目标云服务器注册的组包输出参数；
    根据所述向所述目标云服务器注册的组包输出参数执行向所述目标云服务器注册的访问动作，并接收所述注册的访问动作的回调函数返回的向目标云服务器注册的注册结果；
    利用所述云代理对象获取所述注册结果，将所述注册结果进行解包处理，以得到注册解包结果，并将所述注册解包结果发送至所述应用层。
  9. 根据权利要求8所述的方法，其中，在所述将所述注册解包结果发送至所述应用层之后，还包括：
    利用所述云代理对象监听所述应用层，当监听到所述应用层传入的参数信息时，获取所述参数信息，并将所述参数信息进行组包处理，以得到所述组包输出参数；
    根据所述组包输出参数执行向所述目标云服务器发送数据的访问动作，并接收所述发送数据的访问动作的回调函数返回的所述目标云服务器的处理响应结果；
    利用所述云代理对象获取所述处理响应结果，将所述处理响应结果进行解包处理，以得到处理解包结果，并将所述处理解包结果发送至所述应用层。
  10. 根据权利要求9所述的方法，其中，所述参数信息包括所述智能家居设备的状态信息，所述利用所述云代理对象监听所述应用层，当监听到所述应用层传入的参数信息时，获取所述参数信息，并将所 述参数信息进行组包处理，以得到所述组包输出参数，包括：
    通过所述智能家居设备的应用层将所述状态信息传入至所述服务层；
    基于所述云代理对象获取所述状态信息，将所述状态信息进行组包处理，得到所述状态信息对应的组包输出参数。
  11. 根据权利要求7所述的方法，其中，在所述根据所述连接所述目标云服务器的组包输出参数执行连接所述目标云服务器的访问动作之前，还包括：
    基于所述应用层发送连接请求至所述服务层，当所述服务层在接收到所述连接请求后，触发执行动作集合中连接所述目标云服务器的访问动作。
  12. 根据权利要求1所述的方法，其中，所述执行所述云通用逻辑固件中的通用程序代码，以创建云代理对象，包括：
    基于所述应用层向所述服务层发送云代理创建请求；
    当所述服务层接收到所述云代理创建请求后，调用云代理的结构体，根据所述结构体初始化所述云代理对象。
  13. 根据权利要求2所述的方法，其中，所述将所述参数信息进行组包处理，以得到所述访问动作的组包输出参数，包括：
    利用组包函数将所述参数信息封装为所述目标云服务器可以识别的参数，得到所述组包输出参数，输出所述组包输出参数。
  14. 根据权利要求3所述的方法，其中，所述将所述响应结果进行解包处理，以得到响应解包结果，包括：
    根据解包函数识别所述目标云服务器的响应结果；
    将所述响应结果进行格式解析和/或格式转换处理，得到所述响应解包结果。
  15. 根据权利要求1所述的方法，其中，所述智能家居设备中还包括默认云配置节点，所述默认云配置节点中包括预先封装的动作集合，所述默认云配置节点中包括至少一个云配置节点，所述目标云配置节点中包括至少一个云配置节点，所述方法还包括：
    获取所有云配置节点，所述所有云配置节点包括默认云配置节点和目标云配置节点；
    遍历所述所有云配置节点中的每一个云配置节点；
    所述执行所述动作集合中的每一个访问动作，以访问所述目标云平台的目标云服务器的步骤，包括：执行每一个云配置节点中对应的所述动作集合中的每一个访问动作，以访问每一个云配置节点对应的云服务器。
  16. 一种支持访问多个云服务器的装置，其中，一个云服务器对应一个云平台，其中，所述装置应用于智能家居设备中，所述智能家居设备中包括应用层和服务层，所述服务层中包括云通用逻辑固件，所述装置包括：
    调用模块，用于当所述服务层接收到所述应用层传入的目标云平台信息之后，调用所述服务层中的云通用逻辑固件；
    创建模块，用于执行所述云通用逻辑固件，以创建云代理对象；
    节点实例化模块，用于根据所述目标云平台信息，利用所述云代理对象实例化目标云服务器对应的目标云配置节点，所述目标云配置节点中包括预先封装的动作集合，所述动作集合是抽象所述智能家居设备访问多个云服务器的访问动作得到的；
    访问模块，用于执行所述动作集合中的访问动作，以访问所述目标云平台对应的目标云服务器。
  17. 根据权利要求16所述的装置，其中，所述访问模块包括：
    获取单元，用于对于预先封装的动作集合中的每一个访问动作，利用所述云代理对象获取所述访问动作所需处理的参数信息；
    组包单元，用于将所述参数信息进行组包处理，以得到所述访问动作的组包输出参数；
    访问执行单元，用于根据所述组包输出参数执行所述访问动作，以访问所述目标云平台对应的目标云服务器。
  18. 根据权利要求16所述的装置，其中，所述访问模块还包括：
    返回获取单元，用于通过所述访问动作的回调函数返回执行所述访问动作后所述目标云服务器的响应结果；
    解包单元，用于利用所述云代理对象获取所述响应结果，并将所述响应结果进行解包处理，以得到响应解包结果；
    发送单元，用于将所述响应解包结果发送至所述应用层。
  19. 一种计算机可读存储介质，其中，所述计算机可读存储介质中存储有多条指令，所述指令适于由处理器加载以执行权利要求1至15任一项所述的支持访问多个云服务器的方法中的步骤。
  20. 一种设备，其中，包括处理器和存储器，所述处理器与所述存储器电性连接，所述存储器用于存储指令和数据，所述处理器用于执行权利要求1至15任一项所述的支持访问多个云服务器的方法中的步骤。
PCT/CN2023/125325 2022-11-25 2023-10-19 支持访问多个云服务器的方法、装置、存储介质及设备 WO2024109405A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211494503.X 2022-11-25
CN202211494503.XA CN117119036A (zh) 2022-11-25 2022-11-25 支持访问多个云服务器的方法、装置、存储介质及设备

Publications (1)

Publication Number Publication Date
WO2024109405A1 true WO2024109405A1 (zh) 2024-05-30

Family

ID=88806164

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/125325 WO2024109405A1 (zh) 2022-11-25 2023-10-19 支持访问多个云服务器的方法、装置、存储介质及设备

Country Status (2)

Country Link
CN (1) CN117119036A (zh)
WO (1) WO2024109405A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107528898A (zh) * 2017-08-23 2017-12-29 绵阳美菱软件技术有限公司 一种实现物联网模块的方法及装置
CN111163144A (zh) * 2019-12-23 2020-05-15 海信集团有限公司 物联网模块、物联控制方法及智能设备
CN111176859A (zh) * 2019-11-26 2020-05-19 腾讯云计算（北京）有限责任公司 服务的调用方法、装置及电子设备
US10880743B1 (en) * 2018-06-05 2020-12-29 Equinix, Inc. Interconnection and activation for internet of things devices in multi-tenant data center facilities
CN113489799A (zh) * 2021-07-14 2021-10-08 深圳市集贤科技有限公司 一种物联网设备同时对接多个iot平台的方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107528898A (zh) * 2017-08-23 2017-12-29 绵阳美菱软件技术有限公司 一种实现物联网模块的方法及装置
US10880743B1 (en) * 2018-06-05 2020-12-29 Equinix, Inc. Interconnection and activation for internet of things devices in multi-tenant data center facilities
CN111176859A (zh) * 2019-11-26 2020-05-19 腾讯云计算（北京）有限责任公司 服务的调用方法、装置及电子设备
CN111163144A (zh) * 2019-12-23 2020-05-15 海信集团有限公司 物联网模块、物联控制方法及智能设备
CN113489799A (zh) * 2021-07-14 2021-10-08 深圳市集贤科技有限公司 一种物联网设备同时对接多个iot平台的方法

Also Published As

Publication number Publication date
CN117119036A (zh) 2023-11-24

Similar Documents

Publication Publication Date Title
WO2018103484A1 (zh) 直播页面的数据处理方法、装置和系统
CN110032512B (zh) 一种小程序的调试方法、相关设备及终端
EP2870520B1 (en) Method and apparatus for identifying wireless peripherals and their states at a docking host for wireless docking
CN104754003B (zh) 传输数据的方法及系统
WO2016127795A1 (zh) 业务处理方法、服务器及终端
WO2019037724A1 (zh) 一种移动终端应用程序升级方法、存储设备及移动终端
JP2009087361A (ja) コンポーネントベースの無線アプリケーションを作成して同アプリケーションと通信するためのシステム及び方法
US20140010220A1 (en) Method and apparatus for enabling wireless dockees to find and dock with a wireless docking host being used by another dockee
IL271056B2 (en) A method for transmitting data and a product related to it
WO2018233473A1 (zh) 一种用于配置无线路由设备的方法与设备
CN112242972B (zh) 网络请求处理方法、装置、存储介质及终端
WO2019165983A1 (zh) 一种蓝牙传输控制方法、控制系统及存储介质
WO2017211260A1 (zh) 一种访问数据的方法及相关设备
CN111359210B (zh) 一种数据处理方法、装置、电子设备以及存储介质
WO2024109405A1 (zh) 支持访问多个云服务器的方法、装置、存储介质及设备
WO2022183550A1 (zh) 网络切换方法、存储介质及网关设备
CN110225106B (zh) 一种数据传输方法、装置及存储介质
WO2019140565A1 (zh) 云存储命令管理方法及系统
WO2021237936A1 (zh) Ims 注册方法、存储介质及电子终端
CN105279175B (zh) 数据传输的方法和装置
WO2019140578A1 (zh) 数据备份指令管理方法及系统
WO2024055293A1 (en) Technologies for user equipment group mobility caused by inter-donor full migration
WO2022170849A1 (zh) 开发包认证方法及相关设备
US11606249B1 (en) System and method for communication management in distributed system
KR101658310B1 (ko) 휴대폰 단말장치의 인터넷 네트워크 상태정보를 소켓서버와 실시간 동기화하는 시스템 및 방법