Application login method, device and medium of cloud device

Abstract

The present disclosure provides an application login method and device of a cloud device, equipment and a medium, relates to the technical field of computers, and particularly relates to the technical field of application software, cloud mobile phones, cloud computing and cloud services. The specific implementation scheme is as follows: determining a candidate third-party application available for a to-be-logged-in application in a current cloud device to log in, and determining a candidate other device in which the candidate third-party application is installed; determining a target third-party application from the candidate third-party application according to a selection operation on the candidate third-party application, and determining a target other device in which the target third-party application is installed from the candidate other devices; obtaining target application data of the target third-party application from the target other device, and using the target application data to log in the to-be-logged-in application. The present disclosure realizes the effect of cross-device third-party login of an application, so that the third-party application required for login does not need to be installed in each cloud device, thereby reducing the storage pressure of a single cloud device.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more particularly to the fields of application software, cloud phones, cloud computing and cloud services, and especially to an application login method, apparatus, device and medium for a cloud device. Background Technology

[0002] Cloud devices refer to devices that users can remotely operate using a client on their local machine. As an emerging cloud service technology, cloud devices are gaining popularity among consumers because they are not constrained by local hardware conditions.

[0003] In existing technologies, to enable applications on a cloud device to log in via third-party applications, the necessary third-party applications must be installed on the cloud device. Summary of the Invention

[0004] This disclosure provides a cloud device application login method, apparatus, device, and medium for enabling third-party login for applications across devices, thereby reducing the storage pressure on a single cloud device.

[0005] According to one aspect of this disclosure, an application login method for a cloud device is provided, comprising:

[0006] Identify candidate third-party applications that can be used by the application to be logged in on the current cloud device, and identify other candidate devices that have the candidate third-party applications installed.

[0007] Based on the selection operation of the candidate third-party applications, a target third-party application is determined from the candidate third-party applications, and a target other device with the target third-party application installed is determined from the candidate other devices;

[0008] Obtain the target application data of the target third-party application from the target other devices, and use the target application data to log in to the application to be logged in.

[0009] According to another aspect of this disclosure, an application login device for a cloud device is provided, comprising:

[0010] The first information determination module is used to determine candidate third-party applications that can be logged into by the application to be logged into in the current cloud device, and to determine other candidate devices that have the candidate third-party applications installed.

[0011] The second information determination module is used to determine a target third-party application from the candidate third-party applications based on the selection operation of the candidate third-party applications, and to determine a target other device from the candidate other devices that has the target third-party application installed.

[0012] The application data acquisition module is used to acquire target application data of the target third-party application from the target other devices, and use the target application data to log in to the application to be logged in.

[0013] According to another aspect of this disclosure, an electronic device is provided, comprising:

[0014] At least one processor; and

[0015] A memory that is communicatively connected to at least one processor; wherein,

[0016] The memory stores instructions that can be executed by at least one processor to enable the at least one processor to perform any of the methods of this disclosure.

[0017] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause a computer to perform any of the methods of this disclosure.

[0018] According to another aspect of this disclosure, a computer program product is provided, including a computer program and a method for the computer program to be executed by a processor according to any of the methods disclosed herein.

[0019] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0020] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0021] Figure 1A This is a flowchart of some cloud device application login methods disclosed in the embodiments of this disclosure;

[0022] Figure 1B This is a schematic diagram illustrating some cloud device application login scenarios disclosed in the embodiments of this disclosure;

[0023] Figure 2A This is a flowchart of application login methods for some other cloud devices disclosed in embodiments of this disclosure;

[0024] Figure 2B This is a schematic diagram of a process for determining other candidate devices according to embodiments of this disclosure;

[0025] Figure 3A This is a flowchart of application login methods for some other cloud devices disclosed in embodiments of this disclosure;

[0026] Figure 3BThis is a schematic diagram of a process for obtaining target application data according to some embodiments of this disclosure;

[0027] Figure 3C These are schematic diagrams illustrating other processes for obtaining target application data according to embodiments of this disclosure;

[0028] Figure 4 This is a schematic diagram of the structure of an application login device for some cloud devices disclosed in the embodiments of this disclosure;

[0029] Figure 5 This is a block diagram of an electronic device used to implement the application login method for cloud devices disclosed in the embodiments of this disclosure. Detailed Implementation

[0030] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0031] With the development of cloud device technologies, many applications in cloud devices support login via third-party applications. When a user registers or logs in to an account in an application's interface, they can directly call the third-party application's login interface. After the third-party application authenticates the user, it usually returns relevant application data to the user, allowing the user to log in directly based on the relevant application data. This saves users from the tedious operations of entering usernames, passwords, or verification codes when registering or logging in.

[0032] In existing technologies, to enable applications on a cloud device to log in through a third-party application, it is necessary to install the required third-party application on the cloud device and log in to the account in the third-party application to ensure that other applications can use the third-party login service it provides.

[0033] However, since existing technology can only enable third-party login for applications on a single device, each cloud device needs to install the third-party application required for login. This undoubtedly consumes a large amount of storage space on each cloud device, exacerbating the storage pressure on each cloud device. Furthermore, since each third-party application needs to log in to ensure that other applications can use the third-party login service it provides, in order to avoid conflicts caused by the same account of a third-party application logging in on different cloud devices, it is necessary to assign an independent account to each third-party application, which undoubtedly brings more additional costs.

[0034] Figure 1A This is a flowchart illustrating application login methods for some cloud devices according to embodiments of this disclosure. This embodiment can be applied to third-party login scenarios involving applications across devices. The method in this embodiment can be executed by the application login device for cloud devices disclosed in this disclosure. This device can be implemented using software and / or hardware and can be integrated into any electronic device with computing capabilities.

[0035] like Figure 1A As shown, the application login method for cloud devices disclosed in this embodiment may include:

[0036] S101. Determine the candidate third-party applications that can be used for login by the application to be logged in on the current cloud device, and determine other candidate devices that have the candidate third-party applications installed.

[0037] In this context, cloud devices refer to devices that utilize cloud computing technology on the server side to provide cloud services. These devices, leveraging their built-in systems and the server-side infrastructure provided by the vendor, can perform numerous functions via the network, such as live video streaming, online education, or video games. Types of cloud devices include, but are not limited to, cloud phones, cloud computers, cloud tablets, and cloud TVs. This embodiment does not limit the specific type of cloud device.

[0038] The application to be logged in refers to the application that the user expects to log in to on the current cloud device. The application to be logged in can be the cloud device's system application or the cloud device's software application, such as social software application, game software application, office software application or shopping software application, etc.

[0039] Candidate third-party applications refer to other applications that are different from the application to be logged in but can be used to log in to the application to be logged in. This means that users can directly log in to the application to be logged in using the application data of the candidate third-party application, eliminating the need for users to enter usernames, passwords, or verification codes when logging in to the application to be logged in. For any application to be logged in, a candidate third-party application can be requested through the backend application. For example, if you want to use candidate third-party software B to log in to application A, you can apply for third-party login functionality for application A through the developer backend of candidate third-party software B. If the developer backend of candidate third-party software B approves the application, users can then use candidate third-party software B to log in to application A in the future.

[0040] Candidate other devices refer to devices that are different from the current cloud device and have the candidate third-party application installed. Candidate other devices can be either cloud devices or terminal devices. For example, if a user's terminal device A communicates with both cloud device A and cloud device B through an installed cloud device client, and cloud device A is the current cloud device, then both cloud device B and terminal device A can be candidate other devices; conversely, if cloud device B is the current cloud device, then both cloud device A and terminal device A can be candidate other devices.

[0041] In one implementation, the cloud device determines whether any application's interface is currently in the account registration or login state; if so, that application is designated as the application to be logged in. Based on pre-determined associations between each application and its corresponding third-party applications, candidate third-party applications available for login by the application to be logged in are determined. For example, assuming application A has associations with third-party applications B, C, and D, then when application A is the application to be logged in, the candidate third-party applications available for login can be directly determined as third-party applications B, C, and D.

[0042] The application to be logged in sends an application query request containing candidate application identifiers of candidate third-party applications to each of the other initial devices through the proxy application in the current cloud device. The number of candidate third-party applications may be one or more, and correspondingly, the number of candidate application identifiers may be one or more.

[0043] Each initial proxy application on other devices receives an application query request sent by the proxy application on the current cloud device and parses out the candidate application identifiers contained in the query request. Based on the candidate application identifiers, each initial proxy application on other devices queries whether at least one candidate third-party application is installed locally on the device, then generates query result information and sends it to the proxy application on the current cloud device. The query result information records whether a candidate third-party application is installed, and which candidate third-party applications are specifically installed.

[0044] The proxy application of the current cloud device sends query result information to the application to be logged in. The application to be logged in parses the query result information and selects the initial other devices with candidate third-party applications installed as candidate other devices based on the parsing results.

[0045] By identifying candidate third-party applications that can be used to log in to the application in the current cloud device, and identifying other candidate devices that have these candidate third-party applications installed, a foundation is laid for obtaining target application data from these other relevant devices in the future.

[0046] S102. Based on the selection operation of candidate third-party applications, determine the target third-party application from the candidate third-party applications, and determine the target other devices with the target third-party application installed from the candidate other devices.

[0047] The application to be logged in analyzes the information recorded in the query results. If any candidate third-party application is installed on at least one other initial device, a login button for that candidate third-party application will be displayed on the application interface of the application to be logged in. If no candidate third-party application is installed on any other initial device, its login button will not be displayed on the application interface of the application to be logged in. Users can touch the login button corresponding to any candidate third-party application on the application interface of the application to be logged in, thereby achieving the effect of selecting the corresponding candidate third-party application.

[0048] In one implementation, a user touches and selects the login button of any candidate third-party application on the application interface of the application to be logged in. The application to be logged in responds to the user's selection and uses the candidate third-party application corresponding to the selected login button as the target third-party application. For example, if the user touches and selects the login button of third-party application A, then third-party application A will be selected as the target third-party application.

[0049] The application to be logged in selects candidate other devices that have the target third-party application installed as target other devices based on the information recorded in the query results. The number of target other devices may be one, meaning that only one target other device has the target third-party application installed, or it may be multiple, meaning that at least two target other devices have the target third-party application installed simultaneously.

[0050] By selecting candidate third-party applications, the target third-party application is determined from the candidate applications, thus achieving the effect of determining the target third-party application that the user wants to use; by identifying other target devices that have the target third-party application installed from other candidate devices, the foundation is laid for obtaining the target third-party application data for third-party login in the future.

[0051] S103. Obtain the target application data of the target third-party application from other target devices, and use the target application data to log in to the application to be logged in.

[0052] The target application data refers to the application data generated by the target third-party application running on other target devices, including but not limited to user nicknames, user avatars, user profiles, message records, and the user's unique OpenID (Open Authentication Identifier). This target application data is the foundation for third-party login functionality; only by obtaining the target application data can the application's third-party login function be implemented.

[0053] In one implementation, the application to be logged in calls the third-party login request API (Application Programming Interface) of the proxy application of the current cloud device, and passes the target application identifier of the target third-party application when calling the third-party login request API. The proxy application of the current cloud device generates a data retrieval request based on the target application identifier.

[0054] If there is only one target device, the data acquisition request is sent directly to that target device. If there are at least two target devices, all target devices are displayed on the application interface of the application to be logged in, allowing the user to select one. The data acquisition request is then sent to the selected target device.

[0055] Other target devices receive and parse the data acquisition request, obtain the target application data of the target third-party application based on the target application identifier, and send the target application data to the proxy application of the current cloud device.

[0056] The proxy application on the current cloud device sends the target application data to the application to be logged in via a third-party login request API. The application to be logged in then uses the target application data to log in.

[0057] This disclosure achieves cross-device third-party login by identifying candidate third-party applications available for login on the current cloud device and identifying other candidate devices with these candidate third-party applications installed. Based on the selection of candidate third-party applications, a target third-party application is determined from the candidate third-party applications, and a target other device with the target third-party application installed is determined from the candidate other devices. The target application data of the target third-party application is obtained from the target other device, and the login is performed using the target application data. This eliminates the need to install the required third-party application on each cloud device, reducing the storage pressure on a single cloud device. Furthermore, it also eliminates the need to allocate a separate account for each third-party application, reducing additional costs.

[0058] Figure 1B These are schematic diagrams illustrating some cloud device application login scenarios disclosed in embodiments of this disclosure, such as... Figure 1B As shown:

[0059] The application 101 in the current cloud device 100 that is waiting to log in calls the third-party login request API and sends the target application identifier of the target third-party application to the proxy application 102.

[0060] The proxy application 102 generates a data acquisition request based on the target application identifier and sends the data acquisition request to other target devices. These other target devices can be either terminal device 103 or cloud device 104.

[0061] If proxy application 102 sends a data retrieval request to cloud device client 105 in terminal device 103, then cloud device client 105 retrieves the target application data of target third-party application 106 based on the target application identifier. Cloud device client 105 then sends the target application data to proxy application 102. Proxy application 102 calls the third-party login request API to send the target application data to application 101 to be logged in. Application 101 to be logged in uses the target application data to log in.

[0062] If proxy application 102 sends a data retrieval request to proxy application 107 in cloud device 104, then proxy application 107 retrieves the target application data of the target third-party application 106 based on the target application identifier. Proxy application 107 then sends the target application data to proxy application 102. Proxy application 102 calls the third-party login request API to send the target application data to the application to be logged in, 101. The application to be logged in, 101, uses the target application data to log in.

[0063] The specific implementation methods of each of the above steps are described in the relevant descriptions of the embodiments of this disclosure, and will not be repeated here.

[0064] Figure 2A This is a flowchart of another cloud device application login method disclosed in the embodiments of this disclosure. It is further optimized and extended based on the above technical solutions and can be combined with the above optional implementation methods.

[0065] like Figure 2A As shown, the application login method for cloud devices disclosed in this embodiment may include:

[0066] S201. Identify candidate third-party applications that can be used by the application waiting to log in in the current cloud device.

[0067] S202. Based on the current device identifier of the current cloud device, determine the auxiliary other devices that can be used for application login of the current cloud device from the initial other devices.

[0068] Here, the current device identifier represents the unique device identifier of the current cloud device. The initial other devices represent the set of devices that can interact with the current cloud device. In this embodiment, it is pre-defined which cloud devices each initial other device can provide application login services to. For example, if initial other device A is set to provide application login services to cloud devices B and C, then application login can only be performed using initial other device A when the current cloud device is device B or device C.

[0069] In one implementation, which initial other devices can provide application login services to the current cloud device are determined based on the current device identifier of the current cloud device, and are thus designated as auxiliary other devices. For example, assuming that initial other device 1 and initial other device 2 can provide application login services to the current cloud device, then initial other device 1 and initial other device 2 are designated as auxiliary other devices.

[0070] Optionally, S202 includes:

[0071] Generate a device query request containing the current device identifier and send the device query request to the cloud device management platform, so that the cloud device management platform can determine the auxiliary other devices that can be used for application login of the current cloud device from the initial other devices based on the current device identifier.

[0072] The cloud device management platform refers to a server that provides services to cloud devices. The platform records which cloud devices can initially access application login services from other devices, and establishes an association between the initial device identifiers of these other devices and the device identifiers of the cloud devices that can provide application login services. That is, if the device identifier of any cloud device is associated with the initial device identifier of any other device, it means that the other device can provide application login services to that cloud device.

[0073] In one implementation, the application waiting to log in to the current cloud device calls an API to send a device query command to the proxy application. The proxy application then generates a device query request containing the current device identifier. The proxy application then sends the device query request to the cloud device management platform.

[0074] The cloud device management platform parses device query requests to obtain the current device identifier, and matches it against stored associations. Based on the matching results, it determines auxiliary other devices from the initial list of other devices that can be used for application login by the current cloud device. For example, assuming the current device identifier is "001100", and the stored associations associate device identifier "001100" with initial device identifiers "000001" and "000002", then the initial other devices corresponding to initial device identifiers "001100" and "000001" are designated as auxiliary other devices.

[0075] The cloud device management platform will assist other devices in querying information and then feed it back to the agent application of the current cloud device.

[0076] By generating a device query request containing the current device identifier and sending it to the cloud device management platform, the platform can identify auxiliary devices from the initial pool of other devices that can be used for application login by the current cloud device. This filters out initial devices that cannot be used for application login by the current cloud device, ensuring that the current cloud device can successfully obtain application data from auxiliary devices for application login and avoiding application data acquisition obstacles. Furthermore, using the cloud device management platform to identify auxiliary devices avoids storing the association between the cloud device's device identifier and the initial device identifiers of the initial other devices locally on each cloud device, saving storage space on each cloud device. At the same time, it also allows users to update and maintain the association between device identifiers and initial device identifiers in a timely manner.

[0077] S203. Based on the candidate application identifier of the candidate third-party application, determine the candidate other devices from the auxiliary other devices.

[0078] Among them, the candidate application identifier represents the unique application identifier of the candidate third-party application.

[0079] In one implementation, the current cloud device sends an application query request containing candidate application identifiers to each auxiliary other device. Each auxiliary other device then queries whether a candidate third-party application is installed locally based on the candidate application identifier and returns the query results to the current cloud device. The current cloud device then determines the candidate other devices from among the auxiliary other devices based on the query results.

[0080] By identifying the current device identifier of the current cloud device from the initial pool of other devices, auxiliary other devices that can be used for application login by the current cloud device are determined. Then, by identifying the candidate application identifier of the candidate third-party application, candidate other devices are identified from the auxiliary other devices. This ensures that the candidate other devices not only enable the current cloud device to log in to the application, but also have the necessary candidate third-party application installed. This allows the current cloud device to successfully obtain application data from the candidate other devices for application login, avoiding problems such as application data acquisition obstruction and inability to log in. Furthermore, since both the current device identifier and the candidate application identifier are unique, the accuracy and reliability of the identified auxiliary and candidate other devices are guaranteed.

[0081] Optionally, after sending the device query request to the cloud device management platform, the following may also be included:

[0082] Obtain auxiliary address information for other devices from the cloud device management platform.

[0083] The auxiliary address information represents the unique communication address that enables data communication with other auxiliary devices. When the auxiliary device is a cloud device, the auxiliary address information can be the cloud device's internal network address.

[0084] Accordingly, S203 includes S2031 and S2032:

[0085] S2031. Generate an application query request containing candidate application identifiers, and send the application query request to other auxiliary devices according to the auxiliary address information, so that the other auxiliary devices can query whether candidate third-party applications are installed according to the candidate application identifiers, and generate query result information.

[0086] In one implementation, the proxy application of the current cloud device generates an application query request containing candidate application identifiers and sends the application query request to other auxiliary devices based on auxiliary address information.

[0087] The system assists other devices in parsing application query requests to obtain candidate application identifiers, and then matches the candidate application identifiers with the installed application identifiers of locally installed applications. If at least one installed application identifier matches a candidate application identifier, it is determined that a candidate third-party application is installed locally; otherwise, it is determined that no candidate third-party application is installed locally.

[0088] It assists other devices in generating query results and sends the query results to the agent application of the current cloud device.

[0089] S2032. Obtain query result information from other auxiliary devices, and determine candidate other devices from other auxiliary devices based on the query result information.

[0090] In one implementation, the proxy application of the current cloud device obtains the query results and sends them to the application to be logged in via an API. The application to be logged in parses the query results and then identifies auxiliary devices with candidate third-party applications installed as candidate other devices.

[0091] By generating an application query request containing candidate application identifiers and sending it to other auxiliary devices based on auxiliary address information, the other auxiliary devices can query whether candidate third-party applications are installed based on the candidate application identifiers and generate query results. The system then retrieves the query results from the other auxiliary devices and identifies candidate other devices based on these results. This effectively identifies candidate other devices that have the candidate third-party applications installed, ensuring that the application data required for login can be successfully obtained subsequently. Furthermore, since both the auxiliary address information and the candidate application identifiers are unique, the accuracy and reliability of the identified candidate other devices can be guaranteed.

[0092] S204. Based on the selection operation of candidate third-party applications, determine the target third-party application from the candidate third-party applications, and determine the target other devices with the target third-party application installed from the candidate other devices.

[0093] S205. If there are at least two other target devices, obtain the working attribute information of the other target devices.

[0094] The working attribute information includes at least one of memory usage, CPU usage, disk read / write speed, and network card load.

[0095] In one implementation, if the number of target other devices is at least two, the current cloud device obtains the working attribute information of each target other device from the cloud device management platform.

[0096] S206. Determine idle other devices from the target other devices based on the working attribute information, and obtain the target application data of the target third-party application from the idle other devices.

[0097] In one implementation, the current cloud device acquires the weights of various operational attribute information and performs a weighted calculation on the operational attribute information of each target other device based on these weights to determine the idle level of each target other device. Then, idle other devices are identified from among the target other devices based on their idle level. For example, target other devices with low memory usage, low CPU usage, high disk read / write speeds, and low network card load are preferentially identified as idle other devices.

[0098] The current cloud device obtains the target application data of the target third-party application from other idle devices.

[0099] By acquiring the working attribute information of other target devices, identifying idle other devices based on the working attribute information, and then acquiring the target application data of the target third-party application from the idle other devices, the system achieves the acquisition of target application data from idle other devices with a high degree of idleness, ensuring the timeliness and stability of target application data acquisition.

[0100] S207. Log in to the application to be logged in using the target application data.

[0101] Figure 2B This is a schematic diagram of a process for determining other candidate devices according to embodiments of this disclosure, such as... Figure 2B As shown, it includes:

[0102] S2001, Call AP I to send a device query command.

[0103] Specifically, the application waiting to log in to the current cloud device calls the API to send a device query command to the proxy application of the current cloud device.

[0104] S2002. Generate and send a device query request containing the current device identifier.

[0105] Specifically, the agent application of the current cloud device generates a device query request containing the current device identifier and sends the device query request to the cloud device management platform.

[0106] S2003. Identify other auxiliary devices and send auxiliary address information.

[0107] Specifically, the cloud device management platform determines other auxiliary devices based on the current device identifier and sends the auxiliary address information of the other auxiliary devices to the agent application of the current cloud device.

[0108] S2004. Generate and send an application query request containing candidate application identifiers.

[0109] Specifically, the proxy application of the current cloud device generates an application query request containing the candidate application identifier, and sends the application query request to other auxiliary devices based on the auxiliary address information.

[0110] S2005. Generate and send query result information.

[0111] Specifically, it assists other devices in generating query result information based on candidate application identifiers and sends the query result information to the agent application of the current cloud device.

[0112] S2006. Call the API to send query result information.

[0113] Specifically, the proxy application of the current cloud device calls the API to send query result information to the application to be logged in.

[0114] S2007. Determine other candidate devices based on the query results.

[0115] Specifically, the application to be logged in determines other candidate devices based on the query results.

[0116] The specific implementation methods of each of the above steps are described in the relevant descriptions of the embodiments of this disclosure, and will not be repeated here.

[0117] Figure 3A This is a flowchart of another cloud device application login method disclosed in the embodiments of this disclosure. It is further optimized and extended based on the above technical solutions and can be combined with the above optional implementation methods.

[0118] like Figure 3A As shown, the application login method for cloud devices disclosed in this embodiment may include:

[0119] S301. Identify candidate third-party applications that can be used for login by the application waiting to be logged in on the current cloud device.

[0120] S302. Based on the current device identifier of the current cloud device, determine the auxiliary other devices that can be used for application login of the current cloud device from the initial other devices.

[0121] S303. Based on the candidate application identifier of the candidate third-party application, determine the candidate other devices from the auxiliary other devices.

[0122] S304. Based on the selection operation of candidate third-party applications, determine the target third-party application from the candidate third-party applications, and determine the target other devices with the target third-party application installed from the candidate other devices.

[0123] S305. If the target other device is a cloud device, execute S3051; if the target other device is a terminal device, execute S3052.

[0124] Optionally, the target other devices can be cloud devices belonging to the same user as the current cloud device, or terminal devices where the cloud device client that is communicating with the current cloud device is located, such as mobile phones, computers, or tablets.

[0125] S3051. Based on the target device identifier of the target other device, determine the target address information of the target other device, and based on the target application identifier of the target third-party application and the target address information, obtain the target application data of the target third-party application from the target other device.

[0126] Among them, the target address information represents the internal network address of other target devices in the cloud device system.

[0127] In one implementation, target address information for other target devices is determined based on the target device identifier and the association between the device identifier and address information. The current cloud device generates a first data acquisition request containing the target application identifier and sends the first data acquisition request to other target devices based on the target address information, for the purpose of acquiring target application data from other target devices.

[0128] By determining the target address information of other target devices based on their target device identifiers, and obtaining the target application data of the third-party application from these devices based on its target application identifier and address information, the system achieves the goal of obtaining the target application data required for logging into the application to be logged in. Furthermore, since both the target device identifier and the target address information are unique, the accuracy and reliability of the obtained target application data can be guaranteed.

[0129] Optionally, based on the target device identifier of the other target devices, determine the target address information of the other target devices, including:

[0130] Generate an address query request containing the target device identifier and send the address query request to the cloud device management platform, so that the cloud device management platform can determine the target address information of other target devices based on the target device identifier; and obtain the target address information from the cloud device management platform.

[0131] The cloud device management platform records the relationship between the address information of any device and the identification information of that device, meaning that the address information of a device can be directly determined based on any identification information.

[0132] In one implementation, the application waiting to log in on the current cloud device calls an API to send an address query command to the proxy application. The proxy application then generates an address query request containing the target device identifier. The proxy application sends the address query request to the cloud device management platform.

[0133] The cloud device management platform parses the address query request to obtain the target device identifier, matches the target device identifier with the association between the device identifier and the address information, and determines the target address information of other target devices based on the matching results. The cloud device management platform then sends the target address information to the agent application.

[0134] The proxy application obtains the target address information from the cloud device management platform.

[0135] By generating an address query request containing the target device identifier and sending it to the cloud device management platform, the platform can determine the target address information of other target devices based on the target device identifier. Obtaining the target address information from the cloud device management platform ensures that the current cloud device can smoothly communicate with other target devices that are also cloud devices. Furthermore, using the cloud device management platform to determine the target address information avoids storing the association between device identifiers and address information locally on each cloud device, saving storage space. Simultaneously, it also facilitates timely updates and maintenance of the association between device identifiers and address information by users.

[0136] Optionally, based on the target application identifier of the target third-party application and the target address information, the target application data of the target third-party application can be obtained from other target devices, including:

[0137] A first data acquisition request containing the target application identifier is generated, and the first data acquisition request is sent to other target devices according to the target address information, so that the other target devices can determine the target application data according to the target application identifier; and the target application data is acquired from the other target devices.

[0138] In one implementation, the proxy application of the current cloud device generates a first data acquisition request containing the target application identifier, and sends the first data acquisition request to other target devices according to the target address information.

[0139] The target other devices parse the first data acquisition request and match the target application identifier and the association between the application identifier and the application data. Based on the matching result, the application data associated with the target application identifier is taken as the target application data. The target other devices then send the target application data to the current cloud device.

[0140] The current cloud device obtains target application data from other target devices.

[0141] By generating a first data acquisition request containing the target application identifier and sending the first data acquisition request to other target devices according to the target address information, the other target devices can determine the target application data based on the target application identifier and acquire the target application data from the other target devices. Due to the uniqueness of the target application identifier, the accuracy of acquiring the target application data of the target third-party application is guaranteed.

[0142] S3052. Generate a second data acquisition request containing the target application identifier, and send the second data acquisition request to the other target devices based on the communication connection between the current cloud device and the other target devices, so that the other target devices can determine the target application data according to the target application identifier; and acquire the target application data from the other target devices.

[0143] The terminal device maintains a constant communication connection with the current cloud device, allowing users to control the current cloud device through the terminal device.

[0144] In one implementation, the proxy application of the current cloud device generates a second data acquisition request containing the target application identifier, and sends the second data acquisition request to the target other devices according to the communication connection between the target other devices.

[0145] The target other devices parse the second data acquisition request and match the target application identifier and the association between the application identifier and the application data. Based on the matching result, the application data associated with the target application identifier is taken as the target application data. The target other devices then send the target application data to the current cloud device.

[0146] The current cloud device obtains target application data from other target devices.

[0147] By generating a second data acquisition request containing the target application identifier and sending the second data acquisition request to the target other devices based on the communication connection between the current cloud device and the target other devices, the target other devices can determine the target application data based on the target application identifier and obtain the target application data from the target other devices. This achieves the reuse of the communication connection between the current cloud device and the target other devices when the target other devices are terminal devices, thus eliminating the need to open a new communication link for data communication, reducing additional costs, and improving the efficiency of data communication.

[0148] S306. Log in to the application to be logged in using the target application data.

[0149] Figure 3B These are schematic diagrams illustrating some processes for obtaining target application data according to embodiments of this disclosure, such as... Figure 3B As shown, it includes:

[0150] S3001, Call the API to send an address query command.

[0151] Specifically, the application waiting to log in on the current cloud device calls the API to send an address query command to the proxy application.

[0152] S3002. Generate and send an address query request containing the target device identifier.

[0153] Specifically, the agent application of the current cloud device generates an address query request containing the target device identifier and sends the address query request to the cloud device management platform.

[0154] S3003. Determine the target address information and send the target address information.

[0155] Specifically, the cloud device management platform determines the target address information of other target devices based on the target device identifier, and sends the target address information to the agent application of the current cloud device.

[0156] S3004. Generate and send a first data acquisition request containing the target application identifier.

[0157] Specifically, the proxy application of the current cloud device generates a first data acquisition request containing the target application identifier, and sends the first data acquisition request to the proxy application of other target devices according to the target address information.

[0158] S3005, Send a third-party login request.

[0159] Specifically, the proxy application on other target devices sends a third-party login request to the local target third-party application based on the target application identifier.

[0160] S3006: Authorize third-party login and send target application data.

[0161] Specifically, the target third-party application authorizes third-party login and sends the target application data to proxy applications on other target devices.

[0162] S3007, Send target application data.

[0163] Specifically, the proxy application of the target other device sends the target application data to the proxy application of the current cloud device.

[0164] S3008, Call the API to send data to the target application.

[0165] Specifically, the proxy application of the current cloud device calls the API to send target application data to the application to be logged in.

[0166] S3009. Log in using the target application data.

[0167] Specifically, the application to be logged in uses the target application's data for login.

[0168] The specific implementation methods of each of the above steps are described in the relevant descriptions of the embodiments of this disclosure, and will not be repeated here.

[0169] Figure 3C These are schematic diagrams illustrating other processes for obtaining target application data according to embodiments of this disclosure, such as... Figure 3C As shown, it includes:

[0170] S4001, Call the API to send a data retrieval command.

[0171] Specifically, the application waiting to log in on the current cloud device calls the API to send a data retrieval command to the proxy application.

[0172] S4002. Generate and send a second data acquisition request containing the target application identifier.

[0173] Specifically, the proxy application of the current cloud device generates a second data acquisition request containing the target application identifier, and sends the second data acquisition request to the cloud device client based on the communication connection between the cloud device client and other target devices.

[0174] S4003, Send a third-party login request.

[0175] Specifically, the cloud device client sends a third-party login request to the local target third-party application based on the target application identifier.

[0176] S4004: Authorize third-party login and send target application data.

[0177] Specifically, the target third-party application authorizes third-party login and sends the target application data to the cloud device client.

[0178] S4005, Send target application data.

[0179] Specifically, the cloud device client sends the target application data to the proxy application of the current cloud device.

[0180] S4006, Call the API to send data to the target application.

[0181] Specifically, the proxy application of the current cloud device calls the API to send target application data to the application to be logged in.

[0182] S4007. Log in using the target application data.

[0183] Specifically, the application to be logged in uses the target application's data for login.

[0184] The specific implementation methods of each of the above steps are described in the relevant descriptions of the embodiments of this disclosure, and will not be repeated here.

[0185] Figure 4 This is a schematic diagram of the structure of an application login device for some cloud devices disclosed in embodiments of this disclosure, which can be applied to situations where third-party login for applications is performed across devices. The device in this embodiment can be implemented using software and / or hardware and can be integrated into any electronic device with computing capabilities.

[0186] like Figure 4 As shown, the cloud device application login device 40 disclosed in this embodiment may include a first information determination module 41, a second information determination module 42, and an application data acquisition module 43, wherein:

[0187] The first information determination module 41 is used to determine the candidate third-party applications that can be logged into by the application to be logged in in the current cloud device, and to determine other candidate devices that have the candidate third-party applications installed.

[0188] The second information determination module 42 is used to determine the target third-party application from the candidate third-party applications and determine the target other devices with the target third-party application installed from the candidate other devices based on the selection operation of the candidate third-party applications.

[0189] Application data acquisition module 43 is used to acquire target application data of the target third-party application from other target devices, and to use the target application data to log in to the application to be logged in.

[0190] Optionally, the first information determination module 41 is specifically used for:

[0191] Based on the current device identifier of the current cloud device, identify the auxiliary other devices that can be used for application login of the current cloud device from the initial other devices;

[0192] Candidate other devices are identified from the auxiliary other devices based on the candidate application identifier of the candidate third-party application.

[0193] Optionally, the first information determination module 41 is further used for:

[0194] Generate a device query request containing the current device identifier and send the device query request to the cloud device management platform, so that the cloud device management platform can determine the auxiliary other devices that can be used for application login of the current cloud device from the initial other devices based on the current device identifier.

[0195] Optionally, the device also includes an auxiliary address acquisition module, specifically used for:

[0196] Obtain auxiliary address information for other devices from the cloud device management platform;

[0197] The second information determination module 42 is specifically used for:

[0198] Generate an application query request containing candidate application identifiers, and send the application query request to other auxiliary devices based on the auxiliary address information, so that the other auxiliary devices can query whether candidate third-party applications are installed based on the candidate application identifiers and generate query result information;

[0199] Obtain query results from other auxiliary devices, and determine candidate other devices from other auxiliary devices based on the query results.

[0200] Optionally, when the number of other target devices is at least two, the application data acquisition module 43 is specifically used for:

[0201] Obtain the working attribute information of other target devices; wherein, the working attribute information includes at least one of memory usage, CPU usage, disk read / write speed, and network card load;

[0202] Based on the work attribute information, identify idle other devices from the target other devices, and obtain the target application data of the target third-party application from the idle other devices.

[0203] Optionally, when the target other devices are cloud devices, the application data acquisition module 43 is specifically used for:

[0204] Based on the target device identifier of other target devices, determine the target address information of other target devices;

[0205] Based on the target application identifier of the target third-party application and the target address information, obtain the target application data of the target third-party application from other target devices.

[0206] Optionally, the application data acquisition module 43 is further used for:

[0207] Generate an address query request containing the target device identifier and send the address query request to the cloud device management platform, so that the cloud device management platform can determine the target address information of other target devices based on the target device identifier;

[0208] Obtain the target address information from the cloud device management platform.

[0209] Optionally, the application data acquisition module 43 is further used for:

[0210] A first data acquisition request containing the target application identifier is generated, and the first data acquisition request is sent to other target devices according to the target address information, so that the other target devices can determine the target application data based on the target application identifier;

[0211] Obtain target application data from other target devices.

[0212] Optionally, when the target other device is a terminal device, the application data acquisition module 43 is specifically used for:

[0213] A second data acquisition request containing the target application identifier is generated, and based on the communication connection between the current cloud device and other target devices, the second data acquisition request is sent to other target devices, so that other target devices can determine the target application data based on the target application identifier;

[0214] Obtain target application data from other target devices.

[0215] The cloud device application login device 40 disclosed in this embodiment can execute the cloud device application login method disclosed in this embodiment, and has the corresponding functional modules and beneficial effects of executing the method. Content not described in detail in this embodiment can be referred to the description in the method embodiments of this disclosure.

[0216] The acquisition, storage, and application of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0217] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0218] Figure 5A schematic block diagram of an example electronic device 500 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0219] like Figure 5 As shown, device 500 includes a computing unit 501, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 502 or a computer program loaded from storage unit 508 into random access memory (RAM) 503. RAM 503 may also store various programs and data required for the operation of device 500. The computing unit 501, ROM 502, and RAM 503 are interconnected via bus 504. Input / output (I / O) interface 505 is also connected to bus 504.

[0220] Multiple components in device 500 are connected to I / O interface 505, including: input unit 506, such as keyboard, mouse, etc.; output unit 507, such as various types of monitors, speakers, etc.; storage unit 508, such as disk, optical disk, etc.; and communication unit 509, such as network card, modem, wireless transceiver, etc. Communication unit 509 allows device 500 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0221] The computing unit 501 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 501 performs the various methods and processes described above, such as the application login method for a cloud device. For example, in some embodiments, the application login method for a cloud device can be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program can be loaded and / or installed on device 500 via ROM 502 and / or communication unit 509. When the computer program is loaded into RAM 503 and executed by the computing unit 501, one or more steps of the application login method for a cloud device described above can be performed. Alternatively, in other embodiments, the computing unit 501 can be configured to perform the application login method for a cloud device by any other suitable means (e.g., by means of firmware).

[0222] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0223] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0224] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0225] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0226] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0227] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0228] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0229] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for application login of a cloud device, comprising: determining a candidate third-party application available for login of a to-be-logged application in a current cloud device, and determining a candidate other device in which the candidate third-party application is installed; determining a target third-party application from the candidate third-party application and a target other device in which the target third-party application is installed from the candidate other device according to a selection operation on the candidate third-party application; obtaining target application data of the target third-party application from the target other device, and logging in the to-be-logged application by using the target application data; wherein the determining of the candidate other device in which the candidate third-party application is installed comprises: determining an auxiliary other device available for application login of the current cloud device from initial other devices according to a current device identifier of the current cloud device; determining the candidate other device from the auxiliary other device according to a candidate application identifier of the candidate third-party application; wherein the initial other devices represent a set of devices that perform data interaction with the current cloud device, and the candidate other device represents an other device different from the current cloud device and in which the candidate third-party application is installed.

2. The method of claim 1, wherein, The determining of the auxiliary other device available for application login of the current cloud device from the initial other devices according to the current device identifier of the current cloud device comprises: generating a device query request containing the current device identifier, and sending the device query request to a cloud device management platform, so that the cloud device management platform determines the auxiliary other device available for application login of the current cloud device from the initial other devices according to the current device identifier.

3. The method of claim 2, after the sending of the device query request to the cloud device management platform, further comprising: obtaining auxiliary address information of the auxiliary other device from the cloud device management platform; The determining of the candidate other device from the auxiliary other device according to the candidate application identifier of the candidate third-party application comprises: generating an application query request containing the candidate application identifier, and sending the application query request to the auxiliary other device according to the auxiliary address information, so that the auxiliary other device queries whether the candidate third-party application is installed according to the candidate application identifier, and generates query result information; obtaining the query result information from the auxiliary other device, and determining the candidate other device from the auxiliary other device according to the query result information.

4. The method of claim 1, wherein, In a case where the number of the target other devices is at least two, the obtaining of the target application data of the target third-party application from the target other devices comprises: obtaining working attribute information of the target other devices; wherein the working attribute information comprises at least one of memory usage, CPU usage, disk read-write rate, and network card load; determining an idle other device from the target other devices according to the working attribute information, and obtaining the target application data of the target third-party application from the idle other device.

5. The method of claim 1, wherein, In a case where the target other device is a cloud device, the obtaining of the target application data of the target third-party application from the target other device comprises: determining target address information of the target other device according to a target device identifier of the target other device; obtaining the target application data of the target third-party application from the target other device according to a target application identifier of the target third-party application and the target address information.

6. The method of claim 5, wherein, The determining of the target address information of the target other device according to the target device identifier of the target other device comprises: generating an address query request containing the target device identifier, and sending the address query request to a cloud device management platform, so that the cloud device management platform determines the target address information of the target other device according to the target device identifier; obtaining the target address information from the cloud device management platform.

7. The method of claim 5, wherein, The obtaining of the target application data of the target third-party application from the target other device according to the target application identifier of the target third-party application and the target address information comprises: generating a first data obtaining request containing the target application identifier, and sending the first data obtaining request to the target other device according to the target address information, so that the target other device determines the target application data according to the target application identifier; obtaining the target application data from the target other device.

8. The method of claim 1, wherein, In a case where the target other device is a terminal device, the obtaining of the target application data of the target third-party application from the target other device comprises: generating a second data obtaining request containing the target application identifier, and sending the second data obtaining request to the target other device based on a communication connection between the current cloud device and the target other device, so that the target other device determines the target application data according to the target application identifier; obtaining the target application data from the target other device.

9. An application login apparatus of a cloud device, comprising: a first information determination module configured to determine candidate third-party applications available for a to-be-logged application of a current cloud device to log in, and determine candidate other devices on which the candidate third-party applications are installed; a second information determination module configured to determine a target third-party application from the candidate third-party applications according to a selection operation on the candidate third-party applications, and determine a target other device on which the target third-party application is installed from the candidate other devices; an application data obtaining module configured to obtain target application data of the target third-party application from the target other device, and log in the to-be-logged application by using the target application data; wherein the first information determination module is specifically configured to: determine auxiliary other devices available for the current cloud device to log in applications from initial other devices according to a current device identifier of the current cloud device. determine the candidate other device from the auxiliary other devices according to the candidate application identifier of the candidate third-party application; wherein the initial other devices represent a set of devices that perform data interaction with the current cloud device; and the candidate other device represents an other device that is different from the current cloud device and installs the candidate third-party application.

10. The apparatus of claim 9, wherein, The first information determination module is specifically further configured to: generate a device query request containing the current device identifier, and send the device query request to a cloud device management platform, so that the cloud device management platform determines auxiliary other devices available for the current cloud device to perform application login from initial other devices according to the current device identifier.

11. The apparatus of claim 10, further comprising an auxiliary address acquisition module, specifically configured to: acquire auxiliary address information of the auxiliary other devices from the cloud device management platform; The second information determination module is specifically configured to: generate an application query request containing the candidate application identifier, and send the application query request to the auxiliary other devices according to the auxiliary address information, so that the auxiliary other devices query whether the candidate third-party application is installed according to the candidate application identifier, and generate query result information; acquire the query result information from the auxiliary other devices, and determine the candidate other device from the auxiliary other devices according to the query result information.

12. The apparatus of claim 9, wherein, In a case where the number of the target other devices is at least two, the application data acquisition module is specifically configured to: acquire working attribute information of the target other devices; wherein the working attribute information includes at least one of memory usage, CPU usage, disk read / write rate, and network card load; determine an idle other device from the target other devices according to the working attribute information, and acquire target application data of the target third-party application from the idle other device.

13. The apparatus of claim 9, wherein, In a case where the target other device is a cloud device, the application data acquisition module is specifically configured to: determine target address information of the target other device according to a target device identifier of the target other device; acquire target application data of the target third-party application from the target other device according to a target application identifier of the target third-party application and the target address information.

14. The apparatus of claim 13, wherein, The application data acquisition module is specifically further configured to: generate an address query request containing the target device identifier, and send the address query request to a cloud device management platform, so that the cloud device management platform determines target address information of the target other device according to the target device identifier; acquire the target address information from the cloud device management platform.

15. The apparatus of claim 13, wherein, The application data acquisition module is specifically further configured to: generate a first data acquisition request containing the target application identifier, and send the first data acquisition request to the target other device according to the target address information, so that the target other device determines the target application data according to the target application identifier; acquire the target application data from the target other device.

16. The apparatus of claim 9, wherein, In a case where the target other device is a terminal device, the application data obtaining module is specifically configured to: generate a second data obtaining request containing the target application identifier, and send the second data obtaining request to the target other device based on a communication connection between the current cloud device and the target other device, so that the target other device determines the target application data according to the target application identifier; obtain the target application data from the target other device. 17.An electronic device, comprising: at least one processor; and a memory in communication with the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-8.

18. A non-transitory computer readable storage medium having stored thereon computer instructions, wherein, The computer instructions are used to enable the computer to perform the method according to any one of claims 1-8. 19.A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-8.

Images