Number login method of cloud phone

Abstract

The application discloses a number login method of a cloud mobile phone, comprising the following steps: receiving a login authentication request of a target application on the cloud mobile phone; sending the login authentication request to a terminal device corresponding to the cloud mobile phone, so that the terminal device requests a number one-key login authentication of the target application from an authentication platform; receiving an authentication token returned by the terminal device in response to the login authentication request, the authentication token being associated with a mobile phone number of the terminal device; sending, through an application service end corresponding to the target application, a login request carrying the authentication token to the authentication platform, so as to perform number one-key login of the target application.

Description

Technical Field

[0001] This application relates to the field of cloud phone technology, and in particular to a method for logging into a cloud phone using a phone number. Background Technology

[0002] Cloud phones are based on edge-cloud integrated virtualization technology. Through cloud networking, security, AI, and other digital capabilities, they flexibly adapt to users' personalized needs, freeing up the hardware resources of terminal devices, such as the user's own mobile phone, and allowing them to load massive amounts of cloud applications on demand. Because cloud phones are based on 5G networks, they can store complex calculations and large amounts of data in the cloud. Users can remotely control cloud phones in real time via video streaming, ultimately enabling native applications installed on the terminal device to run in the cloud. With the arrival of the 5G era, the application scenarios for cloud phones are increasing, and users are installing and using more and more applications on cloud phones.

[0003] Currently, applications (APPs) on cloud phones cannot achieve one-click login through number authentication. One-click login is a unified Internet user login authentication system built by operators using their own identification technology. When the user's mobile phone is connected to the Internet with mobile data enabled, it relies on the operator's mobile data network, through the mobile data gateway to obtain evidence and the user's mobile phone SIM card identification. The user only needs to allow the APP to obtain the mobile phone number and upload it through the operator's network to complete the user identity verification, so that the mobile phone user can register / log in with one click without entering an account password.

[0004] Cloud phone apps can only obtain dynamic passwords via SMS, which users must enter on the login page to log in. While SMS authentication largely balances user account security and ease of use, it requires users to enter their phone number and dynamic password, which is inefficient and inconvenient. Furthermore, sending passwords via SMS increases operational costs for app operators. Summary of the Invention

[0005] The purpose of this application is to provide a method for logging into a cloud phone using a phone number, in order to solve the problems of low efficiency and high cost associated with the traditional number login method for cloud phones.

[0006] To solve the above-mentioned technical problems, this specification is implemented as follows:

[0007] Firstly, a method for logging into a cloud phone using a phone number is provided, applicable to cloud phones, the method comprising:

[0008] Receive login authentication request from the target application on the cloud phone;

[0009] The login authentication request is sent to the terminal device corresponding to the cloud phone, so that the terminal device requests the number of the target application for one-click login authentication from the authentication platform;

[0010] The terminal device receives an authentication token returned in response to the login authentication request, and the authentication token is associated with the mobile phone number of the terminal device.

[0011] The application server corresponding to the target application sends a login request carrying the authentication token to the authentication platform to perform one-click login for the target application's number.

[0012] Secondly, a method for logging into a cloud phone using a phone number is provided, applicable to cloud phone applications on terminal devices. The method includes:

[0013] Receive user input for a one-click login control on the target application on the cloud phone;

[0014] In response to the input, receive the login authentication request for the target application sent by the cloud phone;

[0015] Send the login authentication request to the authentication platform to request one-click login authentication of the target application's number;

[0016] Receive the authentication token returned by the authentication platform, the authentication token being associated with the mobile phone number of the terminal device;

[0017] The authentication token is sent to the cloud phone so that the target application sends a login request carrying the authentication token to the authentication platform through the corresponding application server to perform one-click login of the target application's number.

[0018] In this embodiment, the cloud phone receives a login authentication request from a target application on the cloud phone; sends the login authentication request to the terminal device corresponding to the cloud phone, so that the terminal device requests one-click login authentication of the target application's phone number from the authentication platform; receives an authentication token returned by the terminal device in response to the login authentication request, the authentication token being associated with the terminal device's phone number; and sends a login request carrying the authentication token to the authentication platform via the application server corresponding to the target application to execute one-click login of the target application's phone number, thereby connecting the independent network environments between the cloud phone and the user's terminal device. This solution addresses the issue where authentication platforms on cloud phones cannot recognize phone numbers when apps directly request one-click login via the cloud phone's network environment. Users no longer need to enter their phone number or dynamic password on the cloud phone; instead, they can log in with a single click, just like on a real device. This reduces cumbersome login steps, improves user experience, and eliminates the need for users to receive SMS verification codes, thus lowering the operational costs for app operators. It also encourages app operators to actively integrate with carrier number authentication products and ensure compatibility with cloud phone products, further benefiting the ecosystem development of cloud phone products. Attached Figure Description

[0019] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0020] Figure 1 This is a flowchart illustrating a cloud phone number login method according to an embodiment of this application.

[0021] Figure 2 This is a schematic diagram illustrating an application scenario of the cloud phone number login method according to the first embodiment of this application.

[0022] Figure 3 This is a flowchart illustrating the number login method for a cloud phone according to the first embodiment of this application.

[0023] Figure 4 This is a schematic diagram illustrating an application scenario of the cloud phone number login method according to the second embodiment of this application.

[0024] Figure 5 This is a flowchart illustrating the number login method for a cloud phone according to the second embodiment of this application.

[0025] Figure 6 This is a schematic diagram illustrating an application scenario of the cloud phone number login method according to the third embodiment of this application.

[0026] Figure 7 This is a flowchart illustrating the number login method for a cloud phone according to the third embodiment of this application.

[0027] Figure 8 This is a flowchart illustrating a cloud phone number login method according to another embodiment of this application.

[0028] Figure 9 This is a schematic diagram of the number login page of the target application on the cloud phone displayed on the terminal device in this application embodiment.

[0029] Figure 10 This is a structural block diagram of the cloud phone number login system according to an embodiment of this application.

[0030] Figure 11 This is a structural block diagram of the number login device for a cloud phone according to an embodiment of this application. Detailed Implementation

[0031] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. The drawing numbers in this application are only used to distinguish the various steps in the solution and are not used to limit the execution order of the various steps. The specific execution order is subject to the description in the specification.

[0032] To address the problems existing in the prior art, this application provides a method, apparatus, system, and readable storage medium for logging into a cloud phone number.

[0033] Figure 1 This is a flowchart illustrating a cloud phone number login method according to an embodiment of this application. In this embodiment, the cloud phone number login method is applied to a cloud phone. Figure 1 As shown, the method of this embodiment includes steps 102 to 108.

[0034] Step 102: Receive the login authentication request from the target application on the cloud phone.

[0035] Multiple applications can be installed on a cloud phone, and users can remotely control these applications via a cloud phone app installed on their mobile device. A login authentication request is a request from the target application to register for the application or access its page using an account password, dynamic verification code, or one-click login via phone number. The login authentication request may include the target application's identifier, key, and the address of the authentication platform.

[0036] Based on the solution provided in the above embodiments, optionally, in step 102 above, receiving the login authentication request of the target application on the cloud phone includes: responding to the user's input of the one-click login control of the target application through the cloud phone application on the terminal device, receiving the login authentication request of the target application.

[0037] In other words, the target application requests to register or log in using a one-click login method. The login authentication request carries the target application's identifier (ID), key, and the address of the authentication platform, which is used to authenticate the one-click login request.

[0038] Existing one-click login authentication technology requires the app's network environment to be connected via mobile data, and the authentication platform needs to obtain the phone number through a mobile data gateway to enable one-click login. However, the network environment used by the app installed on the cloud phone is independent of the user's mobile data network environment. The app's network environment on the cloud phone does not use the user's SIM card's mobile data, which prevents the app on the cloud phone from achieving one-click login through number authentication.

[0039] Step 104: Send the login authentication request to the terminal device corresponding to the cloud phone, so that the terminal device requests the number of the target application for one-click login authentication from the authentication platform.

[0040] Since apps on cloud phones cannot achieve one-click login via phone number authentication, upon receiving a login authentication request from the target application on the cloud phone, the cloud phone sends the login authentication request to the corresponding terminal device. The terminal device can send the login authentication request directly to the authentication platform, or via a mobile data gateway, or through other network entities; the embodiments in this specification do not impose any limitations on this. When the terminal device accesses the internet via mobile data from the user's SIM card, it can send the login authentication request for the target application to the authentication platform via the mobile data gateway, thereby achieving one-click login authentication for the target application via phone number.

[0041] Step 106: Receive the authentication token returned by the terminal device in response to the login authentication request, wherein the authentication token is associated with the mobile phone number of the terminal device.

[0042] The authentication platform can obtain the mobile phone number of the terminal device corresponding to the login authentication request through the mobile traffic gateway, perform authentication, and return an authentication token for the terminal device's mobile phone number. The authentication token is sent to the terminal device via the mobile traffic gateway, and the terminal device sends the obtained authentication token to the cloud phone, thereby the cloud phone receives the authentication token corresponding to the login authentication request of the target application.

[0043] Step 108: The application server corresponding to the target application sends a login request carrying the authentication token to the authentication platform to perform one-click login of the target application's number.

[0044] The application server is used to provide services for various needs of the target application on the cloud phone. For the login service, the application server can receive the login request from the target application, send the login request to the authentication platform, receive the login result information returned by the authentication platform, and return the login result information to the target application.

[0045] Based on the solution provided in the above embodiments, optionally, in step 108 above, sending a login request carrying the authentication token to the authentication platform via the application server corresponding to the target application to execute one-click login of the target application by number includes: sending a login request carrying the authentication token to the application server through the target application, wherein the application server forwards the login request to the authentication platform and forwards the login result returned by the authentication platform carrying the mobile phone number associated with the authentication token to the target application; and executing one-click login by number based on the mobile phone number through the target application.

[0046] After obtaining the authentication token for one-click login of the target application, the cloud phone can send a login request carrying the authentication token to the application server. The application server then interacts with the authentication platform to perform the relevant data exchange for one-click login. The authentication platform obtains the mobile phone number of the terminal device associated with the authentication based on the authentication token and returns it to the target application in the login result. The target application can then perform one-click login based on the mobile phone number returned by the authentication platform.

[0047] In one embodiment, optionally, in step 104 above, sending the login authentication request to the terminal device includes: determining, through the network processing layer of the cloud phone, whether the address carried in the login authentication request matches the preset address of the authentication platform; if they match, sending the login authentication request to the terminal device through a preset channel established between the network processing layer and the terminal device; otherwise, sending the login authentication request to the address carried in the login authentication request through the network processing layer.

[0048] All network communications on cloud phones need to be processed through the system's network processing layer, combined with... Figure 2In this embodiment, an authentication network processing module 7 can be added to the network processing layer. The authentication network processing module 7 analyzes all network requests sent by apps on the cloud phone 4, extracts the destination address of the network request, and determines whether the domain name or IP address of the destination address matches the domain name or IP address of the authentication platform. If they do not match, the request is sent directly to the original destination address; if they match, the data stream of this network request, i.e., the login authentication request data stream, is filtered out and sent to the user's mobile phone 1.

[0049] Therefore, the authentication network processing module 7 on the cloud phone 4 analyzes network requests and filters out login authentication requests. Then, the login authentication request is sent to the terminal device through a pre-established channel between the cloud phone and the terminal device. For example... Figure 2 In the example, the cloud phone establishes a preset channel between itself and the user's phone 1 through the authentication network processing module 7 and the proxy module 3, which is used for the interaction of data related to login authentication requests.

[0050] Below, on Figure 2 The functions of each module in the embodiment are explained below:

[0051] (1) User mobile phone 1: The terminal device used by the user, which needs to use mobile data to access the Internet;

[0052] (2) Cloud phone APP 2: The cloud phone application installed on the user's mobile phone 1. The user can remotely control the cloud phone 4 in real time through video streaming. The cloud phone APP 2 integrates the agent module 3.

[0053] (3) Proxy module 3: The proxy module in cloud phone APP 2 is used to send the login authentication request of the authentication network processing module 7 of cloud phone 4 to the authentication platform 10 via the mobile traffic gateway 8, and at the same time send the authentication token returned by the authentication platform 10 to the authentication network processing module 7 of cloud phone 4, so as to realize the bridging function between cloud phone 4 and cloud phone APP 2, and between cloud phone APP 2 and authentication platform 10.

[0054] (4) Cloud Phone 4: A mobile phone form based on end-to-end virtualization technology. The system network processing layer of Cloud Phone 1 integrates the authentication network processing module 7.

[0055] (5) APP 5 on cloud phone: The APP installed on the cloud phone realizes the function of one-click login authentication by number, sends the login authentication request to the authentication SDK 6 integrated in APP 5, and sends the login request to the APP server 9 corresponding to APP 5 and receives the login result information returned by APP server 9;

[0056] (6) Authentication SDK 6: The authentication SDK integrated in APP 5 installed on the cloud phone is responsible for sending the login authentication request to the authentication network processing module 7 and sending the authentication token returned by the authentication network processing module 7 to APP 5 on the cloud phone;

[0057] (7) Authentication network processing module 7: The authentication network processing module 7 integrated in the network processing layer of the cloud phone system is responsible for analyzing and filtering login authentication requests, and sending the login authentication request of authentication SDK 6 to the proxy module 3 of cloud phone APP 2 on user phone 1, and at the same time sending the authentication token returned by the proxy module 3 of cloud phone APP 2 on user phone 1 to the authentication SDK 6 of APP 5 on cloud phone 4.

[0058] (8) Mobile traffic gateway 8: A service unit provided by the mobile operator for mobile terminals to access the Internet via mobile traffic. It is responsible for sending the login authentication request of the proxy module 3 of the cloud mobile APP 2 on the user's mobile phone 1 to the authentication platform 10, and at the same time sending the authentication token returned by the authentication platform 10 to the proxy module 3 of the cloud mobile APP 2 on the user's mobile phone 1.

[0059] (9) APP server 9: The server of APP 5 on cloud phone 4 is responsible for receiving the login request of APP 5 on cloud phone 4, sending the login request to the authentication platform 10, receiving the login result information returned by the authentication platform 10, and returning the login result information to APP 5 on cloud phone 4.

[0060] (10) Authentication Platform 10: The server for number authentication login, responsible for verifying number login authentication requests and login requests, and returning authentication tokens and login result information accordingly.

[0061] Figure 3 yes Figure 2 The flowchart of the cloud phone number login method in the corresponding application scenario of the embodiment is shown below. Figure 3 As shown, the data interaction process between the modules is as follows:

[0062] (1) APP 5 on cloud phone 4 sends a login authentication request, namely a one-click login authentication request (carrying the application identifier appid and application key appkey of APP 5) to the authentication SDK 6 integrated in APP 5;

[0063] (2) The authentication SDK integrated in the APP 5 on the cloud phone sends a login authentication request (carrying appid, appkey and signature) to the authentication network processing module 7 on the cloud phone 4;

[0064] (3) The authentication network processing module 7 on the cloud phone 4 analyzes network requests and filters login authentication requests.

[0065] (4) The authentication network processing module 7 on the cloud phone 4 sends a login authentication request (carrying appid, appkey and signature) to the proxy module 3 integrated in the cloud phone APP 2 on the user's phone 1;

[0066] (5) The proxy module 3 integrated in the cloud mobile APP 2 sends a login authentication request (carrying appid, appkey and signature) to the authentication platform 10, which will pass through the mobile traffic gateway 8;

[0067] (6) Mobile traffic gateway 8 sends a login authentication request (carrying appid, appkey and signature) to authentication platform 10;

[0068] (7) The authentication platform 10 verifies the login authentication request information. If the verification is successful, it returns the authentication token to the mobile traffic gateway 8.

[0069] (8) The mobile traffic gateway 8 returns the authentication token to the cloud mobile APP 2 integrated proxy module 3;

[0070] (9) The proxy module 3 integrated in the cloud phone APP 2 returns the authentication token to the authentication network processing module 7 on the cloud phone 4;

[0071] (10) The authentication network processing module 7 on the cloud phone returns the authentication token to the authentication SDK 6 integrated in the APP5 on the cloud phone;

[0072] (11) The authentication SDK 6 integrated in APP 5 on the cloud phone returns an authentication token to APP 5 on the cloud phone;

[0073] (12) The APP 5 on the cloud phone sends a login request (carrying the appid and authentication token) to the APP server 9;

[0074] (13) The APP server 9 sends a login request (carrying the appid and authentication token) to the authentication platform 10;

[0075] (14) The authentication platform 10 verifies the login request. If the verification is successful, it returns the successful login result information (including the mobile phone number of the user's mobile phone 1) to the APP server 9.

[0076] (15) The APP server 9 returns the login result information (including the mobile phone number) to the APP 5 on the cloud phone. At this point, the APP 5 on the cloud phone has successfully achieved one-click login.

[0077] exist Figure 2 and Figure 3In this embodiment, cloud phone 4 needs to be modified to set up authentication network processing module 7 in the network processing layer of cloud phone 4. The cloud phone APP 2 on user phone 1 also needs to be modified to set up proxy module 3 in cloud phone APP 2. APP 5 and authentication SDK 6 on cloud phone 4 do not require modification.

[0078] In another embodiment, optionally, in step 104 above, sending the login authentication request to the terminal device includes: determining whether the target application is running on a cloud phone environment through the authentication SDK of the target application; if so, sending the login authentication request to the proxy module of the cloud phone through the authentication SDK, and sending the login authentication request to the terminal device through a preset channel established between the proxy module and the terminal device; otherwise, sending the login authentication request to the authenticated platform through the authentication SDK.

[0079] Combination Figure 4 In this embodiment, the authentication SDK integrated into each APP on the cloud phone 4 determines whether the corresponding APP is running on the cloud phone environment through the interface or status flag provided by the cloud phone 4. If so, it sends a login authentication request to the proxy module 11 on the cloud phone, and the proxy module 11 then sends the login authentication request to the user's mobile phone 1. If it is not in the cloud phone environment, it means that the target application where the authentication SDK is located is a terminal device, for example... Figure 4 If the device is installed on the user's mobile phone 1, it can directly perform one-click login authentication of the terminal device's normal number through the mobile traffic gateway 8 and the authentication platform 10.

[0080] Therefore, by analyzing the network environment through the authentication SDK integrated in the APP on the cloud phone 4, the login authentication request received under the cloud phone's network environment is determined. Then, the login authentication request is sent to the terminal device through a preset channel established between the cloud phone and the terminal device. For example... Figure 4 In the example, cloud phone 4 establishes a preset channel between itself and user phone 1 through proxy module 11 and through proxy module 3, which is used for the interaction of data related to login authentication requests.

[0081] Below, on Figure 5 The functions of each module in the embodiment are explained below:

[0082] (1) User mobile phone 1: The terminal device used by the user, which needs to use mobile data to access the Internet;

[0083] (2) Cloud phone APP 2: The cloud phone application installed on the user's mobile phone 1. The user can remotely control the cloud phone 4 in real time through video streaming. The cloud phone APP 2 integrates the agent module 3.

[0084] (3) Proxy module 3 on cloud phone APP 2: The proxy module in cloud phone APP 2 is used to send the login authentication request of the proxy module 11 of cloud phone 4 to the authentication platform 10 via the mobile traffic gateway 8, and at the same time send the authentication token returned by the authentication platform 10 to the proxy module 11 of cloud phone 4, so as to realize the bridging function between cloud phone 4 and cloud phone APP 2, and between cloud phone APP 2 and authentication platform 10;

[0085] (4) Cloud Phone 4: A mobile phone form based on end-to-end virtualization technology. The system network processing layer of Cloud Phone 1 integrates the agent module 11.

[0086] (5) APP 5 on cloud phone: The APP installed on the cloud phone realizes the function of one-click login authentication by number, sends the login authentication request to the authentication SDK 6 integrated in APP 5, and sends the login request to the APP server 9 corresponding to APP 5 and receives the login result information returned by APP server 9;

[0087] (6) Authentication SDK 6: The authentication SDK integrated in APP 5 installed on the cloud phone is responsible for sending the login authentication request to the proxy module 11 and sending the authentication token returned by the proxy module 11 to APP 5 on the cloud phone;

[0088] (7) Proxy module 11 on cloud phone 4: The system-integrated proxy module 11 of the cloud phone is responsible for sending the login authentication request of authentication SDK 6 to the proxy module 3 of cloud phone APP 2 on user phone 1, and at the same time sending the authentication token returned by the proxy module 3 of cloud phone APP 2 on user phone 1 to the authentication SDK 6 of APP 5 on cloud phone 4.

[0089] (8) Mobile traffic gateway 8: A service unit provided by the mobile operator for mobile terminals to access the Internet via mobile traffic. It is responsible for sending the login authentication request of the proxy module 3 of the cloud mobile APP 2 on the user's mobile phone 1 to the authentication platform 10, and at the same time sending the authentication token returned by the authentication platform 10 to the proxy module 3 of the cloud mobile APP 2 on the user's mobile phone 1.

[0090] (9) APP server 9: The server of APP 5 on cloud phone 4 is responsible for receiving the login request of APP 5 on cloud phone 4, sending the login request to the authentication platform 10, receiving the login result information returned by the authentication platform 10, and returning the login result information to APP 5 on cloud phone 4.

[0091] (10) Authentication Platform 10: The server for number authentication login, responsible for verifying number login authentication requests and login requests, and returning authentication tokens and login result information accordingly.

[0092] Figure 5 yes Figure 4 The flowchart of the cloud phone number login method in the corresponding application scenario of the embodiment is shown below. Figure 5 As shown, the data interaction process between the modules is as follows:

[0093] (1) APP 5 on cloud phone 4 sends a login authentication request, namely a one-click login authentication request (carrying the application identifier appid and application key appkey of APP 5) to the authentication SDK 6 integrated in APP 5;

[0094] (2) The authentication SDK 6 integrated in APP 5 on the cloud phone determines whether APP 5 is running on the cloud phone environment through the interface or status flag provided by cloud phone 4. If so, it sends a login authentication request (carrying appid, appkey and signature) to the proxy module 11 on cloud phone 4.

[0095] (3) The proxy module 11 on the cloud phone 4 sends a login authentication request (carrying appid, appkey and signature) to the proxy module 3 integrated in the cloud phone APP 2 on the user's phone 1;

[0096] (4) The proxy module 3 integrated in the cloud mobile APP 2 sends a login authentication request (carrying appid, appkey and signature) to the authentication platform 10, which will pass through the mobile traffic gateway 8;

[0097] (5) Mobile traffic gateway 8 sends a login authentication request (carrying appid, appkey and signature) to authentication platform 10;

[0098] (6) The authentication platform 10 verifies the login authentication request information. If the verification is successful, it returns the authentication token to the mobile traffic gateway 8.

[0099] (7) The mobile traffic gateway 8 returns the authentication token to the cloud mobile APP 2 integrated proxy module 3;

[0100] (8) The proxy module 3 integrated in the cloud phone APP 2 returns the authentication token to the proxy module 11 on the cloud phone 4;

[0101] (9) The proxy module 11 on the cloud phone returns the authentication token to the authentication SDK 6 integrated in the APP5 on the cloud phone;

[0102] (10) The authentication SDK 6 integrated in APP 5 on the cloud phone returns the authentication token to APP 5 on the cloud phone;

[0103] (11) The APP 5 on the cloud phone sends a login request (carrying the appid and authentication token) to the APP server 9;

[0104] (12) The APP server 9 sends a login request (carrying the appid and authentication token) to the authentication platform 10;

[0105] (13) The authentication platform 10 verifies the login request. If the verification is successful, it returns the successful login result information (including the mobile phone number of the user's mobile phone 1) to the APP server 9.

[0106] (14) The APP server 9 returns the login result information (including the mobile phone number) to the APP 5 on the cloud phone. At this point, the APP 5 on the cloud phone has successfully achieved one-click login.

[0107] exist Figure 4 and Figure 5 In this embodiment, cloud phone 4 needs to be modified by setting up a proxy module 11 in its network processing layer. The authentication SDK 6 also needs to be modified to determine the network environment of the corresponding APP 5. Furthermore, the cloud phone APP 2 on user phone 1 needs to be modified by setting up a proxy module 3 within it. APP 5 on cloud phone 4 does not require modification.

[0108] In another embodiment, the method further includes: after the target application performs one-click login by number, in response to a login authentication request from a first application associated with the target application on the cloud phone, obtaining an authentication token of the target application; sending a single sign-on authentication request carrying the authentication token to the authentication platform; receiving a single sign-on authentication token returned by the authentication platform in response to the single sign-on authentication request, the single sign-on authentication token being associated with the mobile phone number of the terminal device; and sending a login request carrying the single sign-on authentication token to the authentication platform via the application server corresponding to the first application to perform one-click login by number of the first application.

[0109] In this embodiment, a single sign-on (SSO) scheme based on the number-based one-click login authentication service can be used to authenticate other applications on the cloud phone using a single number. Single Sign-On (SSO) is a user authentication and authorization solution that allows users to log in to multiple interconnected applications and websites using a single set of credentials (such as a user's mobile phone number and password) without having to re-enter credentials in each application and website.

[0110] In this embodiment of the application, if the target application is already logged in, the first application associated with the target application can log in using the login information of the target application.

[0111] Optionally, the step of obtaining the authentication token of the target application in response to a login authentication request from the first application associated with the target application on the cloud phone includes: determining whether the first application is running on the cloud phone environment in response to a login authentication request from the first application associated with the target application on the cloud phone; if so, obtaining the authentication token of the target application.

[0112] For applications running on cloud phone environments, one-click login by phone number can be achieved using the authentication token of the associated logged-in application. If the first application is running on a network environment where the user's mobile data is enabled, one-click login by phone number can be achieved directly by relying on the operator's mobile data network, through mobile data gateway authentication and user's SIM card identification.

[0113] Combination Figure 6 In this embodiment, the authentication module 12 on the cloud phone 4 provides an interface for the APP 5 on the cloud phone 4 to request single sign-on authentication and obtain the returned single sign-on authentication token, and communicate with the authentication platform 10.

[0114] Below, on Figure 6 The functions of each module in the embodiment are explained below:

[0115] (1) Cloud Phone 4: A mobile phone form based on end-to-end virtualization technology. The Cloud Phone 4 integrates an authentication module 12;

[0116] (2) Authentication module 12 on the cloud phone: The authentication module integrated on the cloud phone 4 is responsible for providing an interface to the login authentication request of the APP 5 on the cloud phone 4 and obtaining the returned single sign-on authentication token, and communicating with the authentication platform 10. It receives the login request of the APP 5 on the cloud phone 4, sends the single sign-on authentication request to the authentication platform 10, and returns the single sign-on authentication token to the APP 5 on the cloud phone 4.

[0117] (3) APP 5 on cloud phone: When the APP installed on the cloud phone starts the function of one-click login with number authentication, it sends the login authentication request to the authentication module 12 on the cloud phone and receives the single sign-on authentication token returned by the authentication module 12 on the cloud phone. At the same time, it sends the login request and carries the single sign-on token to the APP server 9 and receives the login result information returned by the APP server 9.

[0118] (4) APP server 9: The server of the APP on the cloud phone 4 is responsible for receiving the login request and single sign-on token of the APP 5 on the cloud phone 4, sending the login request and carrying the single sign-on token to the authentication platform 10, receiving the login result information returned by the authentication platform 10, and returning the login result information to the APP 5 on the cloud phone 4.

[0119] (5) Authentication Platform 10: The server for number authentication login, responsible for verifying login authentication requests and login requests, and returning authentication tokens and login result information accordingly.

[0120] Figure 7 yes Figure 6 The flowchart of the cloud phone number login method in the corresponding application scenario of the embodiment is shown below. Figure 7 As shown, the data interaction process between the modules is as follows:

[0121] (1) The APP 5 on the cloud phone determines whether it is running on the cloud phone environment through the interface or status flag provided by the cloud phone 4. If so, it sends a login request to the authentication module 12 on the cloud phone.

[0122] (2) The authentication module 12 on the cloud phone sends a single sign-on authentication request (carrying the cloud phone login authentication token obtained from the target application that has been logged in with one click) to the authentication platform 10;

[0123] (3) The authentication platform 10 verifies the single sign-on authentication request information. If the verification is successful, it returns the single sign-on authentication token to the authentication module 12 on the cloud phone.

[0124] (4) The authentication module 12 on the cloud phone returns the single sign-on authentication token to the APP 5 on the cloud phone;

[0125] (5) The APP 5 on the cloud phone sends a login request (carrying a single sign-on authentication token) to the APP server 9;

[0126] (6) The APP server 9 sends a login request (carrying a single sign-on authentication token) to the authentication platform 10;

[0127] (7) The authentication platform 10 verifies the login request information. If the verification is successful, it returns the successful login result information (including the mobile phone number) to the APP server 9.

[0128] (8) The APP server 9 returns the login result information (including the mobile phone number) to the APP 5 on the cloud phone. At this point, the APP 5 on the cloud phone has successfully achieved one-click login.

[0129] exist Figure 6 and Figure 7 In this embodiment, cloud phone 4 needs to be modified to set up authentication module 12. APP 5 on cloud phone 4 also needs to be modified to interact with authentication module 12. The authentication SDK of APP 5 on cloud phone 4 does not need to be modified.

[0130] In this embodiment, the cloud phone receives a login authentication request from a target application on the cloud phone; sends the login authentication request to the terminal device corresponding to the cloud phone, so that the terminal device requests one-click login authentication of the target application's phone number from the authentication platform; receives an authentication token returned by the terminal device in response to the login authentication request, the authentication token being associated with the terminal device's phone number; and sends a login request carrying the authentication token to the authentication platform via the application server corresponding to the target application to execute one-click login of the target application's phone number, thereby connecting the independent network environments between the cloud phone and the user's terminal device. This solution addresses the issue where authentication platforms on cloud phones cannot recognize phone numbers when apps directly request one-click login via the cloud phone's network environment. Users no longer need to enter their phone number or dynamic password on the cloud phone; instead, they can log in with a single click, just like on a real device. This reduces cumbersome login steps, improves user experience, and eliminates the need for users to receive SMS verification codes, thus lowering the operational costs for app operators. It also encourages app operators to actively integrate with carrier number authentication products and ensure compatibility with cloud phone products, further benefiting the ecosystem development of cloud phone products.

[0131] Optionally, such as Figure 8 As shown, this application embodiment also provides a method for logging into a cloud phone using a phone number. This embodiment is applied to cloud phone applications on terminal devices and includes:

[0132] Step 202: Receive user input for the one-click login control of the target application on the cloud phone;

[0133] Step 204: In response to the input, receive the login authentication request for the target application sent by the cloud phone;

[0134] Step 206: Send the login authentication request to the authentication platform to request one-click login authentication of the target application's number;

[0135] Step 208: Receive the authentication token returned by the authentication platform, the authentication token being associated with the mobile phone number of the terminal device;

[0136] Step 210: Send the authentication token to the cloud phone so that the target application sends a login request carrying the authentication token to the authentication platform through the corresponding application server to perform one-click login of the target application's number.

[0137] Optionally, the login authentication request for the target application sent by the cloud phone is determined by the cloud phone's network processing layer to match the address carried in the login authentication request with a preset address of the authentication platform, and then sent to the terminal device through a preset channel established between the cloud phone and the terminal device. Alternatively, the login authentication request for the target application sent by the cloud phone is determined by the target application's authentication SDK to be running on the cloud phone environment, and then sent to the terminal device through a preset channel established between the cloud phone and the terminal device.

[0138] It is understood that the terminal device in this embodiment is the one described above. Figures 1 to 7 The terminal device involved in any embodiment refers to the user mobile phone 1 in the figure; the cloud mobile phone application is as described above. Figures 1 to 7 The terminal device involved in any embodiment refers to the cloud mobile APP 2 in the figure. The functions or steps implemented by the corresponding modules are the same or similar, and relevant descriptions are omitted appropriately to avoid repetition.

[0139] Combination Figure 9 Users can log in to various applications on the cloud phone 4 associated with the cloud phone application installed on their terminal device. Specifically, by clicking the "One-Click Login" control on the target application's interface displayed on the terminal device, users can input operation commands to the target application on the cloud phone through the cloud phone application. This allows for remote login to the target application directly via the one-click login function, similar to the one-click login for applications installed on the terminal device. Therefore, users do not need to enter a mobile phone number or dynamic password on the cloud phone; they can directly log in to applications on the cloud phone with a single click. This reduces cumbersome login steps, improves user experience, and reduces the need for users to receive SMS dynamic verification codes, thereby lowering the operating costs for app operators using SMS fees. App operators will be more proactive in integrating operator number authentication products and ensuring compatibility with cloud phone products, further benefiting the ecosystem development of cloud phone products.

[0140] Optionally, such as Figure 10 As shown in the figure, this application embodiment also provides a cloud phone number login system 1000, including a cloud phone 1200 and a terminal device 1400.

[0141] The terminal device 1200 receives input from the user for a one-click login control of the target application on the cloud phone;

[0142] The cloud phone 1400, in response to the input, sends a login authentication request for the target application to the terminal device. The login authentication request carries the identifier, key, and address of the authentication platform of the target application.

[0143] The terminal device 1200 sends the login authentication request to the authentication platform to request one-click login authentication using the target application's number; it receives the authentication token returned by the authentication platform and sends it to the cloud phone, the authentication token being associated with the terminal device's phone number;

[0144] The cloud phone 1400 sends a login request carrying the authentication token to the authentication platform through the application server corresponding to the target application, so as to perform one-click login of the target application's number.

[0145] It is understood that the terminal device 1400 in this embodiment is the one described above. Figures 1 to 9 The terminal device involved in any of the embodiments, the cloud phone 1200 is as described above. Figures 1 to 9 The cloud phone involved in any of the embodiments. The functions or steps implemented by the corresponding modules are the same or similar, and relevant descriptions are omitted appropriately to avoid repetition.

[0146] Optionally, such as Figure 11 As shown in the figure, this application embodiment also provides a cloud phone number login device 2000, including a processor 2400 and a memory 2200. The memory 2200 stores a program or instructions that can run on the processor 2400. When the program or instructions are executed by the processor 2400, they implement the various steps of the above-described cloud phone number login method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0147] This application also provides a readable storage medium storing a program or instructions. When executed by a processor, the program or instructions implement the various processes of any of the above-described cloud phone number login method embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here. The readable storage medium includes computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0148] This application also provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. The computer program is operable to enable a computer to execute the various processes of any of the above-described cloud mobile phone number login method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0149] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0150] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0151] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for logging into a cloud phone using a phone number, characterized in that, Applied to cloud phones, the method includes: Receive login authentication request from the target application on the cloud phone; The login authentication request is sent to the terminal device corresponding to the cloud phone, so that the terminal device requests the number of the target application for one-click login authentication from the authentication platform; The terminal device receives an authentication token returned in response to the login authentication request, and the authentication token is associated with the mobile phone number of the terminal device. The application server corresponding to the target application sends a login request carrying the authentication token to the authentication platform to perform one-click login for the target application's number.

2. The method as described in claim 1, characterized in that, Receiving the login authentication request from the target application on the cloud phone includes: In response to a user's input of a one-click login control for the target application via a cloud mobile application on the terminal device, a login authentication request for the target application is received.

3. The method as described in claim 1, characterized in that, Sending the login authentication request to the terminal device includes: The network processing layer of the cloud phone determines whether the address carried in the login authentication request matches the preset address of the authentication platform. If a match is found, the login authentication request is sent to the terminal device through the preset channel established between the network processing layer and the terminal device. Otherwise, the login authentication request is sent to the address carried in the login authentication request through the network processing layer.

4. The method as described in claim 1, characterized in that, Sending the login authentication request to the terminal device includes: The authentication SDK of the target application is used to determine whether the target application is running on a cloud phone environment. If so, the login authentication request is sent to the proxy module of the cloud phone through the authentication SDK, and the login authentication request is sent to the terminal device through the preset channel established between the proxy module and the terminal device; Otherwise, the login authentication request is sent to the authenticated platform via the authentication SDK.

5. The method as described in claim 1, characterized in that, The step of sending a login request carrying the authentication token to the authentication platform via the application server corresponding to the target application to perform one-click login using the target application's account number includes: The target application sends a login request carrying the authentication token to the application server, wherein the application server forwards the login request to the authentication platform and forwards the login result returned by the authentication platform carrying the mobile phone number associated with the authentication token to the target application; The target application performs one-click login based on the mobile phone number.

6. The method as described in claim 1, characterized in that, Also includes: After the target application performs one-click login, in response to the login authentication request of the first application associated with the target application on the cloud phone, the authentication token of the target application is obtained. Send a single sign-on authentication request carrying the authentication token to the authentication platform; The system receives a single sign-on token returned by the authentication platform in response to the single sign-on authentication request, and the single sign-on token is associated with the mobile phone number of the terminal device. The application server corresponding to the first application sends a login request carrying the single sign-on token to the authentication platform to perform one-click login using the number of the first application.

7. The method as described in claim 6, characterized in that, The step of responding to a login authentication request from a first application associated with the target application on the cloud phone and obtaining the authentication token of the target application includes: In response to a login authentication request from a first application associated with the target application on the cloud phone, determine whether the first application is running on the cloud phone environment; If so, obtain the authentication token of the target application.

8. A method for logging into a cloud phone using a phone number, characterized in that, A cloud-based mobile application applied to terminal devices, the method comprising: Receive user input for a one-click login control on the target application on the cloud phone; In response to the input, receive the login authentication request for the target application sent by the cloud phone; Send the login authentication request to the authentication platform to request one-click login authentication of the target application's number; Receive the authentication token returned by the authentication platform, the authentication token being associated with the mobile phone number of the terminal device; The authentication token is sent to the cloud phone so that the target application sends a login request carrying the authentication token to the authentication platform through the corresponding application server to perform one-click login of the target application's number.

9. The method as described in claim 8, characterized in that, The login authentication request for the target application sent by the cloud phone is sent to the terminal device through a preset channel established between the cloud phone and the terminal device after the network processing layer of the cloud phone determines that the address carried in the login authentication request matches the preset address of the authentication platform.

10. The method as described in claim 8, characterized in that, The login authentication request for the target application sent by the cloud phone is sent to the terminal device through a preset channel established between the cloud phone and the terminal device after the authentication SDK of the target application determines that the target application is running on the cloud phone environment.

11. A number login device for a cloud phone, characterized in that, The device, used in cloud phones, includes: The first receiving module receives the login authentication request of the target application on the cloud phone; The first sending module sends the login authentication request to the terminal device corresponding to the cloud phone, so that the terminal device requests the number of the target application for one-click login authentication from the authentication platform; The second receiving module receives the authentication token returned by the terminal device in response to the login authentication request, and the authentication token is associated with the mobile phone number of the terminal device; The second sending module sends a login request carrying the authentication token to the authentication platform via the application server corresponding to the target application, so as to execute one-click login of the target application's number.

12. A number login device for a cloud phone, characterized in that, Cloud mobile applications applied to terminal devices, the device comprising: The first receiving module receives user input for the one-click login control of the target application on the cloud phone; The second receiving module, in response to the input, receives the login authentication request for the target application sent by the cloud phone; The first sending module sends the login authentication request to the authentication platform to request one-click login authentication of the target application's number; The third receiving module receives the authentication token returned by the authentication platform, and the authentication token is associated with the mobile phone number of the terminal device; The second sending module sends the authentication token to the cloud phone, so that the target application sends a login request carrying the authentication token to the authentication platform through the corresponding application server to perform one-click login of the target application's number.

13. A number login device for a cloud phone, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1-10.

14. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1-10.

Images