One-key password-free login method and system for cloud mobile phone, electronic device and storage medium

Abstract

This application provides a method, system, electronic device, and storage medium for one-click passwordless login on cloud phones. The method includes: upon receiving trigger information from a target app sent by a cloud phone front-end system, generating a one-time password for the target app, wherein the trigger information indicates that one-click passwordless login of the target app is triggered, and the target app is any one of multiple apps installed on the cloud phone front-end system; sending the one-time password and preset app authentication information to an operator server through the cloud phone front-end system, the cloud phone cloud system, and the target app application server, so that the operator server can verify the mobile phone authentication module based on the one-time password, and the target app application server can authenticate the one-click passwordless login of the target app based on the app authentication information. This method solves the technical problems of low efficiency in one-click passwordless login on cloud phones caused by insecure and easily problematic data transmission and high maintenance costs in existing technologies.

Description

Technical Field

[0001] This application relates to the field of one-click login for cloud phones, and more particularly to a method, system, electronic device, and storage medium for one-click passwordless login for cloud phones. Background Technology

[0002] A cloud phone is a mobile phone that applies cloud computing technology to network terminal services. It makes full use of the characteristics of mobile broadband networks, the always-on nature of mobile phones, and cloud technology to closely connect the mobile phone with the entire network system, making the use of mobile phones more convenient and efficient.

[0003] In existing cloud phone technologies, users can log in by entering their account and password; or they can use their mobile phone number as a credential to request the operator's network, thereby achieving the purpose of authentication; or cloud phone-related services can be used as operator proxy services to block the operator from the application and achieve the purpose of one-click login-free.

[0004] By requiring users to enter their account, password, or mobile phone number as credentials to request network authentication from the operator, the operator needs to send the authentication information to the mobile phone via SMS or token, making one-click login impossible. Using cloud phone services as a proxy service for the operator essentially blocks the connection between the operator and the application (APP) server, resulting in insecure data transmission and a high risk of problems. Furthermore, the cloud phone needs to simulate both the operator and the APP server, increasing maintenance costs. All of these factors contribute to the low efficiency of one-click passwordless login on cloud phones. Summary of the Invention

[0005] This application provides a method, system, electronic device, and storage medium for one-click passwordless login on cloud phones. This addresses the problem that when users input their account, password, or mobile phone number as credentials to request network authentication from the operator, the operator needs to send the authentication information to the phone via SMS or token information, making one-click login impossible. Furthermore, using cloud phone services as a proxy service for the operator essentially blocks the connection between the operator and the app server, resulting in insecure data transmission and a high risk of problems. Additionally, the cloud phone needs to simulate both the operator and the app server, increasing maintenance costs. All these factors contribute to the technical problem of low efficiency in one-click passwordless login on cloud phones.

[0006] Firstly, this application provides a method for one-click passwordless login to a cloud phone, which is applied to a mobile phone authentication module and includes:

[0007] When the target APP is received from the cloud phone front-end system, a one-time password for the target APP is generated. The trigger information is used to indicate that the one-click passwordless login of the target APP is triggered. The target APP is any one of the multiple APPs installed on the cloud phone front-end system.

[0008] The system uses a cloud phone front-end system, a cloud phone cloud system, and a target APP application server to send a one-time password and preset APP authentication information to the operator's server. This allows the operator's server to verify the mobile phone authentication module based on the one-time password, and the target APP application server to authenticate the target APP's one-click passwordless login based on the APP authentication information.

[0009] In one possible design, before generating the one-time password for the target app, the method also includes:

[0010] Upon receiving the startup information sent by the cloud phone front-end system, a communication link is established between the phone authentication module and the operator server;

[0011] The mobile phone authentication information is sent to the operator's server through the communication link, so that the operator's server can provide verification information based on the mobile phone authentication information.

[0012] In one possible design, the verification information includes: token information and a one-time password generation algorithm;

[0013] Generate a one-time password for the target app, including:

[0014] A one-time password generation algorithm is used to generate a one-time password for the target app based on token information and app authentication information.

[0015] In one possible design, the verification information also includes: the public key and the public key algorithm;

[0016] After generating a one-time password for the target app based on token information and app authentication information using a one-time password generation algorithm, the method further includes:

[0017] The one-time password is encrypted using a public-key algorithm based on the public key, so that the operator's server can decrypt the encrypted one-time password using the pre-stored private key.

[0018] Secondly, this application provides a one-click passwordless login method for cloud phones, which is applied to cloud phone cloud systems and includes the following:

[0019] Upon receiving the one-time password and APP authentication information from the cloud phone front-end system, the one-time password and APP authentication information are sent to the operator's server through the target APP application server.

[0020] When the operator's server verifies the one-time password and the target APP's application server verifies the target APP's one-click password-free access, the display information of the target APP is generated;

[0021] Control the information displayed by the cloud phone's front-end system.

[0022] In one possible design, the cloud phone cloud system includes: multiple cloud phone containers, and at least one cloud phone APP deployed in each cloud phone container;

[0023] The APP authentication information includes: the container identifier of the target APP, and the APP identifier of the target APP;

[0024] Before sending the one-time password and app authentication information to the operator's server via the target app application server, the method also includes:

[0025] Based on the container identifier, locate the target cloud phone container from multiple cloud phone containers;

[0026] Based on the APP identifier, locate the target cloud phone APP from at least one cloud phone APP deployed in the target cloud phone container;

[0027] The target app server is located based on the target cloud mobile app.

[0028] In one possible design, the display information for the target app is generated, including:

[0029] The target app server receives the phone number information fed back by the operator server based on the app authentication information.

[0030] Receive user information from the target app server based on the phone number information;

[0031] Based on the phone number and user information, obtain application information from the target APP's application server;

[0032] Generate display information for the target app based on application information.

[0033] Thirdly, this application provides a cloud phone one-click password-free login system, which includes a mobile phone authentication module and a cloud phone cloud system. The mobile phone authentication module is used to implement the content of the first aspect of the invention, and the cloud phone cloud system is used to implement the content of the second aspect of the invention.

[0034] Fourthly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0035] The memory stores the instructions that the computer executes;

[0036] When the processor executes computer execution instructions stored in the memory, it is used to implement the first aspect or the second aspect of the invention: a cloud phone one-click password-free login method.

[0037] Fifthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement a cloud phone one-click password-free login method according to the first or second aspect of the invention.

[0038] Sixthly, this application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement a cloud phone one-click password-free login method according to the first aspect or the second aspect of the invention.

[0039] This application provides a method, system, electronic device, and storage medium for one-click passwordless login on cloud phones. The method includes: upon receiving trigger information from a target app sent by a cloud phone front-end system, generating a one-time password for the target app. The trigger information indicates that the one-click passwordless login of the target app is triggered. The target app is any one of multiple apps installed on the cloud phone front-end system. The one-time password and preset app authentication information are sent to an operator server via the cloud phone front-end system, the cloud phone cloud system, and the target app application server. This allows the operator server to verify the mobile phone authentication module based on the one-time password, and the target app application server to authenticate the one-click passwordless login of the target app based on the app authentication information. Compared to existing technologies that require users to input an account, password, or mobile phone number as credentials to request operator network authentication, where the operator needs to send authentication information to the mobile phone via SMS or token information, one-click passwordless login is not possible. Using cloud phone services as a proxy service for operators essentially blocks the connection between the operator and the app server, resulting in insecure data transmission and a high risk of problems. Furthermore, the cloud phone needs to simulate both the operator and the app server, increasing maintenance costs. All of these factors contribute to the low efficiency of one-click passwordless login on cloud phones. This application addresses this by using a cloud phone authentication module that generates different one-time passwords for different apps based on the token information returned by the operator and a one-time password generation method. This avoids multiple interactions with the operator to obtain token information. The one-time password is used to verify the operator server and the app server, obtaining phone number and user information, thus ensuring the accuracy of the phone number and user information and improving the efficiency of one-click passwordless login on cloud phones. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 A flowchart illustrating a one-click passwordless login method for cloud phones provided in Embodiment 1 of this application. Figure 1 ;

[0042] Figure 2 A flowchart illustrating a one-click passwordless login method for cloud phones provided in Embodiment 1 of this application. Figure 2 ;

[0043] Figure 3 A flowchart illustrating a one-click password-free login method for cloud phones provided in Embodiment 2 of this application. Figure 3 ;

[0044] Figure 4 A flowchart illustrating a one-click password-free login method for cloud phones provided in Embodiment 2 of this application. Figure 4 ;

[0045] Figure 5 This is a schematic diagram illustrating the specific steps of a cloud phone one-click password-free login method provided in Embodiment 3 of this application;

[0046] Figure 6 This application provides a schematic diagram of the structure of a cloud phone one-click password-free login system.

[0047] Figure 7 This is a schematic diagram of the structure of an electronic device provided in this application. Detailed Implementation

[0048] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0049] In the embodiments of this application, the terms "first" and "second" are used to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, nor do they necessarily imply difference. It should be noted that in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner. In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more.

[0050] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0051] It should be noted that the phrase "at...time" in the embodiments of this application can refer to the instant at which a certain situation occurs, or to a period of time after the occurrence of a certain situation; the embodiments of this application do not specifically limit this. Furthermore, the one-click passwordless login method for cloud phones provided in the embodiments of this application is only an example, and the one-click passwordless login method for cloud phones may also include more or less content.

[0052] To facilitate a clear description of the technical solutions in the embodiments of this application, some terms and technologies involved in the embodiments of this application will be briefly introduced below:

[0053] Token information refers to a data unit used in authentication, authorization, or secure communication. This data unit contains a series of information used to verify a user's identity, authorize access to resources, or ensure the integrity and authenticity of messages.

[0054] Tokens typically contain encoded information such as user identifiers (IDs), roles, permissions, and expiration times. This information can be in plaintext or encrypted, depending on how the token is generated and verified.

[0055] A token typically has one issuer (such as an authentication server) and one or more receivers (such as an API server). The issuer is responsible for generating and signing the token, while the receiver is responsible for verifying the token's validity.

[0056] The security of tokens is paramount. They should be signed using strong cryptographic algorithms to prevent tampering. Furthermore, appropriate security measures, such as HTTPS, should be implemented during the storage and transmission of tokens.

[0057] Tokens typically have a limited lifespan, meaning they expire after a certain period. After expiration, users need to re-authenticate to obtain a new token.

[0058] Tokens are widely used in various scenarios, such as:

[0059] Authentication: Proving the user's identity.

[0060] Authorization: Determines whether a user has the right to access a resource or perform an operation.

[0061] Stateless session management: In distributed systems, it is used to record the session state of users.

[0062] One-time passwords (OTPs) are unpredictable, random number combinations related to an event, generated periodically using a specific algorithm. Each OTP can only be used once and is invalid afterward, thus enhancing security.

[0063] Cloud phone: A type of smartphone that applies cloud computing technology to network terminal services, providing cloud services through cloud servers. It fully utilizes the mobile broadband network, the always-on connectivity of the phone, and the features of cloud technology brought by 5G (5th Generation Mobile Networks), connecting the phone to the entire network system and making the phone no longer an isolated entity.

[0064] SIM Card: A Subscriber Identity Module (SIM) is a smart card used to store mobile phone user identity information and is an important component of mobile communication systems. It mainly consists of a microprocessor, program memory, working memory, data memory, and a serial communication unit.

[0065] A public key is a pair of keys that are linked together, as opposed to a private key. They are typically used in security applications such as encrypted communication and digital signatures. The public key is public and can be widely shared, while the private key is private and known only to its holder.

[0066] Public and private keys are mathematically closely related; information encrypted with a public key can only be decrypted with the corresponding private key, and vice versa. This property makes public and private keys extremely useful in encrypted communication.

[0067] A private key is a concept in blockchain technology and a set of cryptographic keys that users must use for operations such as encrypted transactions and digital signatures. In a blockchain network, each user has a public key and a private key pair. The public key can be made public, while the private key must be kept strictly confidential. The private key is primarily used to generate digital signatures, proving the legitimacy of transactions, and can also be used to unlock funds. If the private key is lost or stolen, the user may lose control over the encryption; therefore, protecting the private key is crucial.

[0068] Cloud phone containers are a technology that allows a single cloud phone to be split into two independent cloud phones, thereby reducing user costs. Containerization technology achieves application isolation and security by packaging the application and all its dependencies into a shared runtime environment, thus improving application security.

[0069] In practice, cloud phone containers are managed through container orchestration tools to achieve automated deployment, scaling, and operation and maintenance. Container orchestration needs to consider container creation, operation, storage, and security to ensure efficient, stable, and secure operation. Simultaneously, cloud phone containers must also meet storage requirements for high availability, scalability, and high reliability to ensure data integrity and security.

[0070] In existing cloud phone technologies, users primarily request network authentication from operators by entering their account, password, or phone number. Operators then need to send the authentication information to the phone via SMS or token, making one-click login impossible. Using cloud phone services as a proxy for operator services essentially blocks the connection between the operator and the app server, resulting in insecure data transmission and a high risk of problems. Furthermore, cloud phones need to simulate both the operator and the app server, increasing maintenance costs. This leads to the technical problem of inefficient one-click passwordless login in cloud phones.

[0071] To address the aforementioned technical problems, this application provides a one-click passwordless login method for cloud phones, aiming to solve the above-mentioned technical issues in the prior art. The inventive concept of this application lies in: how to effectively improve the efficiency of one-click passwordless login for cloud phones.

[0072] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0073] Figure 1 A flowchart illustrating a one-click passwordless login method for cloud phones provided in Embodiment 1 of this application. Figure 1 ,like Figure 1 As shown, applied to the mobile phone authentication module, the method includes:

[0074] S101. Upon receiving the trigger information from the target APP sent by the cloud phone front-end system, a one-time password for the target APP is generated. The trigger information is used to indicate that the one-click passwordless login of the target APP is triggered. The target APP is any one of the multiple APPs installed on the cloud phone front-end system.

[0075] In this embodiment, the mobile phone authentication module generates a one-time password for the target APP based on the trigger information received from the cloud mobile phone front-end system.

[0076] The mobile phone authentication module and the cloud phone front-end system are both on the physical mobile phone. The cloud phone front-end system is the front-end system of the cloud phone on the physical mobile phone device. Users can operate the cloud phone by operating on the cloud phone front-end system.

[0077] This trigger information is generated when the user triggers the one-click login-free function of the target APP in the cloud phone front-end system.

[0078] It should be noted that this mobile phone authentication module can be programmed or configured to automatically start the one-click login function when the cloud phone starts up. This saves users time in triggering the target APP, speeds up the overall one-click login speed of the cloud phone APP, makes the cloud phone APP smoother to use, and improves the user's cloud phone experience.

[0079] S102. Through the cloud phone front-end system, cloud phone cloud system and target APP application server, send the one-time password and preset APP authentication information to the operator server so that the operator server can verify the mobile phone authentication module according to the one-time password, and the target APP application server can authenticate the one-click passwordless login of the target APP according to the APP authentication information.

[0080] Figure 2 A flowchart illustrating a one-click passwordless login method for cloud phones provided in Embodiment 1 of this application. Figure 2 ,like Figure 2 As shown, this method, applied to a cloud-based mobile phone system, includes:

[0081] S201. Upon receiving the one-time password and APP authentication information sent by the cloud phone front-end system, the one-time password and APP authentication information are sent to the operator server through the target APP application server.

[0082] The cloud phone cloud system receives the one-time password and APP authentication information sent by the cloud phone front-end system. Through the APP authentication information, it finds the target APP application server and sends the one-time password and APP authentication information to the target APP application server. The target APP application server then sends the one-time password and APP authentication information to the operator server.

[0083] S202. When the operator's server verifies the one-time password and the target APP's application server verifies the target APP's one-click password-free access, generate the target APP's display information.

[0084] In this embodiment, the operator server verifies the one-time password. After successful verification, the verification information is sent to the target APP application server. When the target APP application server verifies the one-click password-free access of the target APP, the cloud phone cloud system generates the display information of the target APP.

[0085] S203, Control the display of information on the front-end system of the cloud phone.

[0086] In this embodiment, the cloud phone cloud system sends the display information of the target APP to the cloud phone front-end system and the mobile phone authentication module, and displays the display information on the cloud phone front-end system.

[0087] This application provides a method for one-click passwordless login on a cloud phone, comprising: upon receiving trigger information from a target APP sent by a cloud phone front-end system, generating a one-time password for the target APP, wherein the trigger information is used to indicate that the one-click passwordless login of the target APP is triggered, and the target APP is any one of multiple APPs installed on the cloud phone front-end system; sending the one-time password and preset APP authentication information to the operator server through the cloud phone front-end system, the cloud phone cloud system, and the target APP application server, so that the operator server can verify the mobile phone authentication module according to the one-time password, and the target APP application server can authenticate the one-click passwordless login of the target APP according to the APP authentication information. Compared with the prior art, which requires the user to enter an account, password, or mobile phone number as credentials to request operator network authentication, the operator needs to send the authentication information to the mobile phone in the form of SMS or token information, which cannot achieve one-click passwordless login. Using cloud phone services as a proxy service for operators essentially blocks the connection between the operator and the app server, resulting in insecure data transmission and a high risk of problems. Furthermore, the cloud phone needs to simulate both the operator and the app server, increasing maintenance costs. All of these factors contribute to the low efficiency of one-click passwordless login on cloud phones. This application addresses this by using a cloud phone authentication module that generates different one-time passwords for different apps based on the token information returned by the operator and a one-time password generation method. This avoids multiple interactions with the operator to obtain token information. The one-time password is used to verify the operator server and the app server, obtaining phone number and user information, thus ensuring the accuracy of the phone number and user information and improving the efficiency of one-click passwordless login on cloud phones.

[0088] Figure 3 A flowchart illustrating a one-click password-free login method for cloud phones provided in Embodiment 2 of this application. Figure 3 ,like Figure 3 As shown, applied to the mobile phone authentication module, the method includes:

[0089] S301. Upon receiving the startup information sent by the cloud phone front-end system, a communication link is established between the phone authentication module and the operator server.

[0090] In this embodiment, when the cloud phone front-end system first receives the trigger information generated by the user when triggering the one-click login function of the target APP in the cloud phone front-end system, the cloud phone front-end system will first send the mobile phone authentication module startup information. The startup information instructs the mobile phone authentication module to establish a communication link with the operator server and exchange data.

[0091] S302. The mobile phone authentication information is sent to the operator's server through the communication link so that the operator's server can provide verification information based on the mobile phone authentication information.

[0092] In this embodiment, the mobile phone authentication module sends the mobile phone authentication information to the operator server through a communication link. The operator server generates verification information based on the mobile phone authentication information and sends the verification information back to the mobile phone authentication module through the communication link.

[0093] The mobile phone authentication information verified by the operator's server includes: cloud phone provider identifier, mobile phone model identifier, public IP, private IP, and SIM card information.

[0094] Optionally, public IP, private IP, and SIM card information can be replaced with mobile phone number, mobile phone identifier, and user biometric information to avoid failure under Wi-Fi network.

[0095] Optionally, the phone model and phone identifier are very important in phone authentication information, because future phone systems will be increasingly strict in obtaining phone number information. Only by using specific phone models and phone identifiers can phone number information be successfully obtained.

[0096] Specifically, the above two steps enable the operator's server to grant one-click login-free authorization to the cloud phone. This authorization can be used on multiple containers and applications for the user, but is limited to this cloud phone provider.

[0097] S303. Upon receiving the trigger information of the target APP sent by the cloud phone front-end system, a one-time password for the target APP is generated based on the token information and APP authentication information using a one-time password generation algorithm.

[0098] Among them, the triggering information is used to indicate that the one-click passwordless login of the target APP is triggered. The target APP is any one of the multiple APPs installed on the cloud phone front-end system; the verification information includes: token information and one-time password generation algorithm.

[0099] Specifically, after the operator's server verifies the mobile phone authentication information, it sends verification information back to the mobile phone authentication module. This verification information includes token information and a one-time password generation algorithm. The mobile phone authentication module then uses the token information, app authentication information, and a random number to generate a one-time password for the target app using the algorithm.

[0100] More specifically, the mobile authentication module can generate one-time passwords multiple times based on the token information. These one-time passwords can be used to log in to multiple different apps under different cloud containers for the same user.

[0101] In addition, the token information needs to have an expiration time to prevent personal information from being stolen if the phone is lost. The one-time password generated by this mobile authentication module can change dynamically and is controlled by the operator. Ultimately, the operator also reclaims the authentication.

[0102] S304. The one-time password is encrypted using a public key algorithm based on the public key, so that the operator's server can decrypt the encrypted one-time password using the pre-stored private key.

[0103] The verification information also includes: the public key and the public key algorithm.

[0104] Specifically, the verification information returned by the operator's server also includes the public key and public key algorithm. When the mobile phone authentication module generates a one-time password, it also encrypts the generated one-time password using the public key algorithm and public key. Simultaneously, when the generated one-time password is transmitted to the operator's server, the operator's server decrypts the encrypted one-time password using a pre-stored private key.

[0105] S305: Through the cloud phone front-end system, cloud phone cloud system, and target APP application server, a one-time password and preset APP authentication information are sent to the operator server so that the operator server can verify the mobile phone authentication module according to the one-time password, and the target APP application server can authenticate the one-click passwordless login of the target APP according to the APP authentication information.

[0106] In this embodiment, the mobile phone authentication module generates a one-time password based on the token information in the verification information fed back by the operator server and the one-time password generation algorithm. One token information can generate different one-time passwords for different target apps. The one-time password can be used for multiple different apps under different cloud containers of the user. It is no longer necessary to interact with the operator server to generate a token information every time you log in to an app. This reduces the number of interactions in one-click login and improves the authentication speed and success rate of one-click login, thereby improving the efficiency of one-click passwordless login for cloud phones.

[0107] Figure 4 A flowchart illustrating a one-click password-free login method for cloud phones provided in Embodiment 2 of this application. Figure 4 ,like Figure 4 As shown, this method, applied to a cloud-based mobile phone system, includes:

[0108] S401. Locate the target cloud phone container from multiple cloud phone containers based on the container identifier.

[0109] The cloud phone cloud system includes: multiple cloud phone containers, and at least one cloud phone APP deployed in each cloud phone container.

[0110] Specifically, the cloud-based front-end system locates the target cloud phone container from multiple cloud phone containers based on the container identifier of the target APP in the APP authentication information, and then sends the one-time password and APP authentication information to the target cloud phone container.

[0111] S402. Based on the APP identifier, locate the target cloud mobile APP from at least one cloud mobile APP deployed in the target cloud mobile container.

[0112] The APP authentication information includes: the container identifier of the target APP, and the APP identifier of the target APP.

[0113] Specifically, the target cloud phone container locates the target cloud phone app from at least one cloud phone app deployed in the target cloud phone container based on the app identifier, and then sends a one-time password and app authentication information to the target cloud phone app.

[0114] S403. Locate the target app application server based on the target cloud mobile app.

[0115] Specifically, the cloud phone system locates the target app server based on the target cloud phone app, and then sends a one-time password and app authentication information to the target app server.

[0116] Furthermore, the APP authentication information transmitted by the cloud phone cloud system also includes corresponding authentication information such as the cloud vendor identifier. The target cloud phone APP sends a one-time password, random number, APP identifier, container identifier, and cloud vendor identifier to the target APP application server, eliminating the need for the cloud phone to act as a proxy for the target APP application server to perform additional parsing work.

[0117] Furthermore, the target app's application server sends a one-time password, a random number, the app identifier, the container identifier, and the cloud provider identifier to the operator's server. This allows the operator's server to verify the one-time password, eliminating the need for the cloud phone to perform additional parsing work on behalf of the target app's application server. The target app itself needs to use its own private key for signature authentication to confirm that the action was initiated by the app itself.

[0118] S404. Upon receiving the one-time password and APP authentication information from the cloud phone front-end system, the one-time password and APP authentication information are sent to the operator server through the target APP application server.

[0119] S405. When the one-time password verification is successful on the operator server and the one-click password-free verification is successful on the target APP application server, the mobile phone number information fed back by the operator server based on the APP authentication information is received through the target APP application server.

[0120] Specifically, after the operator's server completes the verification of the one-time password, it returns a verification success message and the mobile phone number information to the target APP application server based on the APP authentication information.

[0121] S406: Receive user information from the target APP application server based on the mobile phone number information.

[0122] Specifically, the target app server returns user information to the cloud phone system based on the successful verification information and the phone number information. This user information mainly includes the user account, password, and personal information corresponding to the phone number.

[0123] S407. Obtain application information from the target APP application server based on the mobile phone number information and user information.

[0124] Specifically, the cloud-based mobile phone system retrieves application information from the target app's application server based on the phone number and user information. This application information includes cached and favorited data related to the app within the target app, corresponding to the phone number and user information.

[0125] S408. Generate display information for the target APP based on the application information.

[0126] Specifically, the cloud phone cloud system generates display information for the target APP based on the application information. This includes the successful one-click passwordless login of the target APP and the display of application information corresponding to the mobile phone number, all of which are displayed on the cloud phone front-end system.

[0127] S409, Control the display of information on the front-end system of the cloud phone.

[0128] In this embodiment, based on the container identifier and APP identifier of the target APP in the APP authentication information, the one-time password and APP authentication information are sent to the target APP application server through the target cloud phone container and the target cloud phone APP. Then, the target APP application server sends the one-time password and APP authentication information to the operator server. At the same time, based on the mobile phone number information provided by the operator server, the user information is obtained from the target APP application server. The cloud phone cloud system then obtains the application information from the target APP application server based on the mobile phone number information and user information sent by the target APP application server. There is no need for the cloud phone to proxy the target APP application server to perform additional parsing work. This achieves natural interaction between third-party servers, which not only saves maintenance costs but also ensures the security and accuracy of data transmission, thereby improving the efficiency of one-click passwordless login for cloud phones.

[0129] Figure 5This is a schematic diagram illustrating the specific steps of a one-click passwordless login method for cloud phones provided in Embodiment 3 of this application, as shown below. Figure 5 As shown, the method includes:

[0130] S501, the cloud phone front-end system sends startup information to the phone authentication module.

[0131] S502, the mobile phone authentication module establishes a communication link with the operator's server.

[0132] S503: The mobile phone authentication module sends mobile phone authentication information to the operator's server through the communication link.

[0133] S504: The operator server sends verification information to the mobile phone authentication module based on the mobile phone authentication information.

[0134] S505, the cloud phone front-end system sends the target APP's trigger information to the mobile phone authentication module.

[0135] S506 The mobile phone authentication module generates and sends a one-time password for the target APP to the cloud phone front-end system.

[0136] S507, the cloud phone front-end system locates the target cloud phone container from multiple cloud phone containers based on the container identifier.

[0137] S508. Based on the APP identifier, the target cloud phone container locates the target cloud phone APP from at least one cloud phone APP deployed in the target cloud phone container.

[0138] S509, The target cloud mobile APP locates the target APP application server based on the target cloud mobile APP.

[0139] The S510 cloud phone front-end system sends a one-time password and APP authentication information to the operator's server through the target cloud phone container, the target cloud phone APP, and the target APP application server.

[0140] S511, the operator's server verifies the one-time password.

[0141] S512: The operator server sends the mobile phone number information back to the target APP application server based on the APP authentication information.

[0142] S513, The target APP application server verifies the target APP's one-click password-free pass.

[0143] S514. The target APP application server sends user information back to the target cloud mobile APP based on the mobile phone number information.

[0144] S515 The target cloud mobile APP obtains application information from the target APP application server based on the mobile phone number information and user information.

[0145] S516. The target cloud phone APP generates the display information of the target APP based on the application information and sends it to the cloud phone front-end system.

[0146] The S517, cloud phone front-end system, and mobile phone authentication module display information.

[0147] In this embodiment, when the mobile phone authentication module receives trigger information from the target APP sent by the cloud phone front-end system, it generates a one-time password for the target APP. The trigger information indicates that the one-click passwordless login of the target APP is triggered. The target APP is any one of multiple APPs installed on the cloud phone front-end system. The one-time password and preset APP authentication information are sent to the operator server through the cloud phone front-end system, the cloud phone cloud system, and the target APP application server. This allows the operator server to verify the mobile phone authentication module based on the one-time password, and the target APP application server to authenticate the one-click passwordless login of the target APP based on the APP authentication information. Compared to existing technologies that require users to enter their account, password, or mobile phone number as credentials to request operator network authentication, where the operator needs to send authentication information to the mobile phone via SMS or token information, one-click passwordless login is not possible. Using cloud phone services as a proxy service for operators essentially blocks the connection between the operator and the app server, resulting in insecure data transmission and a high risk of problems. Furthermore, the cloud phone needs to simulate both the operator and the app server, increasing maintenance costs. All of these factors contribute to the low efficiency of one-click passwordless login on cloud phones. This application addresses this by using a cloud phone authentication module that generates different one-time passwords for different apps based on the token information returned by the operator and a one-time password generation method. This avoids multiple interactions with the operator to obtain token information. The one-time password is used to verify the operator server and the app server, obtaining phone number and user information, thus ensuring the accuracy of the phone number and user information and improving the efficiency of one-click passwordless login on cloud phones.

[0148] In this embodiment of the invention, electronic devices or main control devices can be divided into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the module division in this embodiment of the invention is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0149] Figure 6 This application provides a schematic diagram of the structure of a cloud phone one-click password-free login system, as shown in the embodiments. Figure 6As shown, the system includes: a mobile phone authentication module 61 and a cloud mobile phone cloud system 62.

[0150] The mobile phone authentication module 61 generates a one-time password for the target APP when it receives the trigger information from the cloud phone front-end system. The trigger information is used to indicate that the one-click passwordless login of the target APP is triggered. The target APP is any one of the multiple APPs installed on the cloud phone front-end system.

[0151] When the cloud phone cloud system 62 receives the one-time password and APP authentication information sent by the cloud phone front-end system, it sends the one-time password and APP authentication information to the operator server through the target APP application server.

[0152] The cloud phone cloud system 62 is also used to generate display information for the target APP when the operator server verifies the one-time password and the target APP application server verifies the one-click password-free access of the target APP.

[0153] The cloud phone cloud system 62 is also used to generate display information for the target APP when the operator server verifies the one-time password and the target APP application server verifies the one-click password-free access of the target APP.

[0154] In one possible design, the method further includes the following steps before generating the one-time password for the target app:

[0155] Mobile phone authentication module 61 is also used for:

[0156] Upon receiving the startup information sent by the cloud phone front-end system, a communication link is established between the phone authentication module and the operator server;

[0157] The mobile phone authentication information is sent to the operator's server through the communication link, so that the operator's server can provide verification information based on the mobile phone authentication information.

[0158] In one possible design, the verification information includes: token information and a one-time password generation algorithm;

[0159] Generate a one-time password for the target app, including:

[0160] Mobile phone authentication module 61 is also used for:

[0161] A one-time password generation algorithm is used to generate a one-time password for the target app based on token information and app authentication information.

[0162] In one possible design, the verification information also includes: the public key and the public key algorithm;

[0163] After generating a one-time password for the target app based on the token information and app authentication information using a one-time password generation algorithm, the method also includes:

[0164] Mobile phone authentication module 61 is also used for:

[0165] The one-time password is encrypted using a public-key algorithm based on the public key, so that the operator's server can decrypt the encrypted one-time password using the pre-stored private key.

[0166] In one possible design, the cloud phone cloud system includes: multiple cloud phone containers, and at least one cloud phone APP deployed in each cloud phone container;

[0167] The APP authentication information includes: the container identifier of the target APP, and the APP identifier of the target APP;

[0168] Before sending the one-time password and app authentication information to the operator's server via the target app's application server, the method also includes:

[0169] The cloud phone cloud system 62 is also used for:

[0170] Based on the container identifier, locate the target cloud phone container from multiple cloud phone containers;

[0171] Based on the APP identifier, locate the target cloud phone APP from at least one cloud phone APP deployed in the target cloud phone container;

[0172] The target app server is located based on the target cloud mobile app.

[0173] In one possible design, the display information for the target app is generated, including:

[0174] The cloud phone cloud system 62 is also used for:

[0175] The target app server receives the phone number information fed back by the operator server based on the app authentication information.

[0176] Receive user information from the target app server based on the phone number information;

[0177] Based on the phone number and user information, obtain application information from the target APP's application server;

[0178] Generate display information for the target app based on application information.

[0179] This embodiment provides a cloud phone one-click password-free login system that can execute a cloud phone one-click password-free login method described in the above embodiment. Its implementation principle and technical effect are similar, and will not be repeated here.

[0180] In the aforementioned specific implementation of a cloud phone one-click password-free login method, each module can be implemented as a processor. The processor can execute computer execution instructions stored in the memory, thereby enabling the processor to execute the aforementioned cloud phone one-click password-free login method.

[0181] Figure 7 A schematic diagram of the structure of an electronic device provided in this application. See also... Figure 7 The electronic device 70 includes at least one processor 71 and a memory 72. The electronic device 70 also includes a communication component 73. The processor 71, memory 72, and communication component 73 are connected via a bus 74.

[0182] In the specific implementation process, at least one processor 71 executes the computer execution instructions stored in the memory 72, causing at least one processor 71 to execute the cloud phone one-click passwordless login method of claims 1 to 4 or the cloud phone one-click passwordless login method of claims 5 to 7 as executed on the electronic device side.

[0183] The specific implementation process of processor 71 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0184] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

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

[0186] The second bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0187] The above description of the functions implemented by electronic devices and main control devices has introduced the solutions provided by the embodiments of the present invention. It is understood that, in order to implement the above functions, the electronic device or main control device includes hardware structures and / or software modules corresponding to the execution of each function. By combining the units and algorithm steps of the various examples described in the embodiments of the present invention, the embodiments of the present invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the technical solutions of the embodiments of the present invention.

[0188] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement a cloud phone one-click password-free login method as described in claims 1 to 4 or claims 5 to 7.

[0189] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0190] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in an electronic device or a host device.

[0191] This application also provides a computer program product, comprising: a computer program stored in a readable storage medium, wherein at least one processor of an electronic device can read the computer program from the readable storage medium, and the at least one processor executes the computer program to cause the electronic device to perform the scheme provided in any of the above embodiments.

[0192] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disk, or optical disk.

[0193] The technical solutions of this application have been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it is readily understood by those skilled in the art that the scope of protection of this application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for one-click passwordless login to a cloud phone, characterized in that, The method is applied to a mobile phone authentication module, and the method includes: Upon receiving the trigger information from the target APP sent by the cloud phone front-end system, a one-time password for the target APP is generated. The trigger information is used to indicate that the one-click passwordless login of the target APP is triggered. The target APP is any one of the multiple APPs installed on the cloud phone front-end system. The one-time password and preset APP authentication information are sent to the operator server through the cloud phone front-end system, cloud phone cloud system and target APP application server, so that the operator server can verify the mobile phone authentication module according to the one-time password, and the target APP application server can authenticate the one-click passwordless login of the target APP according to the APP authentication information.

2. The method according to claim 1, characterized in that, Before generating the one-time password for the target APP, the method further includes: Upon receiving the startup information sent by the cloud phone front-end system, a communication link is established between the phone authentication module and the operator server; The mobile phone authentication information is sent to the operator's server through the communication link, so that the operator's server can provide verification information based on the mobile phone authentication information.

3. The method according to claim 2, characterized in that, The verification information includes: token information and a one-time password generation algorithm; The generation of the one-time password for the target APP includes: The one-time password generation algorithm generates a one-time password for the target APP based on the token information and the APP authentication information.

4. The method according to claim 3, characterized in that, The verification information also includes: a public key and a public key algorithm; After generating a one-time password for the target app based on the token information and the app authentication information using the one-time password generation algorithm, the method further includes: The one-time password is encrypted using the public key algorithm and the public key, so that the operator server can decrypt the encrypted one-time password using the pre-stored private key.

5. A method for one-click passwordless login to a cloud phone, characterized in that, The method is applied to a cloud-based mobile phone system, and the method includes: Upon receiving the one-time password and APP authentication information sent by the cloud phone front-end system, the one-time password and APP authentication information are sent to the operator server through the target APP application server. When the operator server verifies the one-time password and the target APP application server verifies the one-click password-free access of the target APP, the display information of the target APP is generated; Control the cloud phone's front-end system to display the information.

6. The method according to claim 5, characterized in that, The cloud phone cloud system includes: multiple cloud phone containers, and at least one cloud phone APP deployed in each of the cloud phone containers; The APP authentication information includes: the container identifier of the target APP, and the APP identifier of the target APP; Before sending the one-time password and the APP authentication information to the operator's server via the target APP application server, the method further includes: Based on the container identifier, locate the target cloud phone container from among the multiple cloud phone containers; Based on the APP identifier, the target cloud phone APP is located from at least one cloud phone APP deployed in the target cloud phone container; The target cloud mobile app is used to locate the target app application server.

7. The method according to claim 6, characterized in that, The generation of the display information for the target app includes: The target APP application server receives the mobile phone number information fed back by the operator server based on the APP authentication information; Receive user information fed back by the target APP application server based on the mobile phone number information; Based on the mobile phone number information and the user information, obtain application information from the target APP application server; The display information of the target APP is generated based on the application information.

8. A cloud phone one-click password-free login system, characterized in that, The system includes a mobile phone authentication module and a cloud phone cloud system, wherein the mobile phone authentication module is used to implement the cloud phone one-click passwordless login method according to any one of claims 1 to 4, and the cloud phone cloud system is used to implement the cloud phone one-click passwordless login method according to any one of claims 5 to 7.

9. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; When the processor executes the computer execution instructions stored in the memory, it is used to implement the cloud phone one-click passwordless login method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the cloud phone one-click password-free login method as described in any one of claims 1 to 7.

Images