Improved cloud mobile phone number one-key login method, server and storage medium

Abstract

The application discloses an improved cloud mobile phone number one-key login method, a server and a storage medium, and comprises the following steps: after an application APP triggers one-key login, a one-key login SDK is called to send an encrypted pre-fetching number request; a cloud mobile phone system intercepts all pre-fetching number requests sent by cloud mobile phone instances, and adds a cloud mobile phone instance ID in the header of the pre-fetching number request; a SDK authentication server generates a cloud mobile phone pre-fetching number request according to the cloud mobile phone instance ID, and sends the cloud mobile phone pre-fetching number request to the cloud mobile phone system; the cloud mobile phone system receives the cloud mobile phone pre-fetching number request, a cloud mobile phone App performs a pre-fetching number operation, and the cloud mobile phone App sends a pre-fetching number request to the SDK authentication server; the SDK authentication server returns a response message body to the cloud mobile phone APP; the SDK authentication server returns the response message body to the one-key login SDK, and the one-key login SDK decrypts the response message body, and displays a one-key login authorization page to complete one-key login by the application APP. The application can enhance the availability and security of one-key login of applications in the cloud mobile phone.

Description

Technical Field

[0001] This application belongs to the field of information security, and specifically relates to a method for one-click login to a cloud mobile phone number, a server, and a storage medium. Background Technology

[0002] Cloud phones are an emerging technology that allows users to remotely access and operate a virtual phone instance (hereinafter referred to as a "cloud phone instance") running on a cloud server through a local client application (hereinafter referred to as a "cloud phone app"). Users can install and run various third-party applications in the cloud phone instance, just like on a physical phone.

[0003] One-click login is a convenient authentication method commonly used in mobile applications. Its core principle is that the carrier SDK (Software Development Kit) integrated within the application sends a request to the carrier's authentication server via the physical phone's cellular network. The authentication server can then directly obtain the phone number from this cellular network connection, thus enabling passwordless login. However, because cloud phone instances run in a cloud environment without physical SIM cards or cellular network connections, the standard one-click login process cannot be directly applied.

[0004] In existing technologies, a solution for cloud phone scenarios (e.g., prior application 202510202096.8) proposes a "pre-retrieval number" mechanism. The general process of this solution is as follows: The one-click login SDK within the cloud phone instance initiates a pre-retrieval number request to the SDK authentication server; after recognizing that the request originates from the cloud phone, the SDK authentication server returns an HTTP 302 redirect response, redirecting the request to the cloud phone system server; the SDK within the cloud phone instance follows this redirection and initiates a request to the cloud phone system server, enabling the cloud phone system to identify which cloud phone instance is requesting login; subsequently, the cloud phone system, through its signaling channel with the cloud phone app on the physical phone, instructs the customized SDK within the cloud phone app to utilize the physical phone's cellular network to complete the actual "pre-retrieval number" operation, and then transmits the obtained credentials (such as accessCode) back through a complex link.

[0005] However, in practical applications, the inventors have discovered that the above-mentioned prior art has at least the following technical problems: 1. Undermines the SDK's independence and security: In this scheme, the one-click login SDK, which should only communicate with the SDK authentication server, is forced to interact with the cloud phone system via network redirection. This compromises the SDK's encapsulation and independence as a trusted component, introduces the cloud phone system as an intermediary, and increases the risk that critical data in the authentication process may be intercepted or tampered with by third parties.

[0006] 2. The authentication process is lengthy and prone to timeouts: The introduced network redirection steps and the multi-layered data forwarding between the "cloud phone instance - SDK authentication server - cloud phone system - physical phone app" significantly increase the communication link length and time delay of the entire one-click login process, resulting in a higher timeout failure rate in the authentication process and affecting the user experience.

[0007] Therefore, a technical solution for one-click login using a cloud-based mobile phone number is needed to solve the above problems. Summary of the Invention

[0008] To address the shortcomings of the existing technology, this application provides a one-click login method, server, and storage medium for cloud mobile phone numbers. In the one-click login scenario of cloud mobile phone applications, the signaling channel between the cloud mobile phone instance and the cloud mobile phone App is used to trigger the one-click login SDK within the cloud mobile phone App to complete the pre-retrieval of numbers in real time. Furthermore, by using mechanisms such as encrypted serial numbers, the security of the number retrieval information during transmission within the cloud mobile phone-related systems is ensured while maintaining compatibility with existing one-click login SDK communication rules.

[0009] The technical effect to be achieved in this application is accomplished through the following solution: According to a first aspect of this application, a method for one-click login using a cloud mobile phone number is provided, comprising the following steps: Step 1: After the application APP in the cloud phone system triggers one-click login, it calls the one-click login SDK built into the application APP to send an encrypted pre-retrieval number request; Step 2: The cloud phone system intercepts all pre-fetch number requests sent by cloud phone instances, identifies the SDK pre-fetch number identifier, appends the cloud phone instance ID to the header of the pre-fetch number request, and then sends a pre-fetch number request with the cloud phone instance ID. Step 3: The SDK authentication server judges the pre-fetch number request. When the first condition is met, it generates a cloud phone pre-fetch number request based on the cloud phone instance ID and sends it to the cloud phone system. Step 4: The cloud phone system receives the cloud phone pre-fetch number request and obtains the cloud phone instance ID. It then triggers the cloud phone app to perform the pre-fetch number operation through the signaling channel between the corresponding cloud phone instance and the cloud phone app. The cloud phone app then sends the pre-fetch number request to the SDK authentication server. Step 5: The SDK authentication server verifies the pre-registration number request, and returns a response message to the cloud mobile APP when the second condition is met; Step 6: The cloud phone APP returns the response message body to the cloud phone system through the signaling channel. The cloud phone system sends the response message body to the SDK authentication server. The SDK authentication server returns the response message body to the one-click login SDK. After the one-click login SDK decrypts the message body, the application APP displays the one-click login authorization page to complete the one-click login.

[0010] Preferably, in step 1, the specific method for calling the one-click login SDK to send an encrypted pre-retrieval number request is as follows: The one-click login SDK randomly generates a communication key key1. The communication key key1 and the encryption type are added to the request parameters. The request parameters are then encrypted using the SDK's built-in public key using RAS to complete the encrypted pre-number retrieval request.

[0011] Preferably, in step 3, after receiving the pre-fetch number request, the SDK authentication server uses its private key to decrypt the pre-fetch number request to obtain the request parameters, generates a transaction serial number, and then determines whether the first condition is met.

[0012] Preferably, the specific method for determining whether the first condition is met is as follows: The request IP is compared with the whitelist of cloud phone system server IPs to determine whether it is a pre-fetching request initiated by an application app within the cloud phone. The system compares the AppID in the request parameters with the whitelist of applications that have enabled one-click login for cloud phones to determine whether the current application allows one-click login within the cloud phone. If so, the first condition is met.

[0013] Preferably, in step 3, a cloud phone pre-fetching request is generated based on the cloud phone instance ID. The specific method is as follows: After caching the request parameters, encrypt them to generate a ciphertext serial number, and calculate the signature information based on the ciphertext serial number and the timestamp; The encrypted serial number, timestamp, signature information, and cloud phone instance ID are concatenated into the URL to form a cloud phone pre-fetch number request.

[0014] Preferably, in step 4, the cloud phone system sends information through the signaling channel between the corresponding cloud phone instance and the cloud phone APP to trigger the customized one-click login SDK integrated in the cloud phone APP to issue a pre-registration number request. After obtaining the pre-fetch number request, the SDK authentication service verifies it. The second condition includes: the timestamp is within the valid time period, and the cache request parameter information obtained by decrypting the ciphertext serial number is used to calculate and verify that the signature information is correct.

[0015] Preferably, the specific method for returning the response message body is as follows: based on the cellular network connection information, complete the pre-fetching request and generate accessCode and mobile phone number mask information; Encrypt the accessCode and phone number mask information using the communication key1 and encryption type from the cached request parameters to generate a response message body; The SDK authentication service returns a response message body, which is then decrypted by the one-click login SDK based on the set communication key1 and encryption type. The accessCode and phone number mask information are then returned to the cloud phone app as a response message.

[0016] Preferably, step 6 further includes number replacement: after the user agrees to authorization on the one-click login authorization page, the accessCode is sent to the application server for number replacement; The application server sends an accessCode to the SDK authentication server to perform number replacement; The SDK authentication server verifies the accessCode; if the verification is successful, it returns the complete mobile phone number. The application server receives the complete mobile phone number to complete the login operation and returns the login result to the application (App).

[0017] According to a second aspect of this application, a server is provided, comprising: a memory and at least one processor; The memory stores a computer program, and the at least one processor executes the computer program stored in the memory to implement the above-mentioned one-click login method for cloud mobile phone numbers.

[0018] According to a third aspect of this application, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed, it implements the above-described one-click login method for cloud mobile phone numbers.

[0019] Compared with the prior art, the technical solution provided by the present invention has at least the following beneficial effects: This invention ensures the independence and security of the SDK: By proactively intercepting and transparently injecting the instance ID through the cloud phone system, the one-click login SDK avoids direct data interaction with the cloud phone system via network redirection. The SDK's communication target is always the SDK authentication server it trusts, maintaining the SDK's original security model and encapsulation, and reducing the risk of data tampering in the authentication process.

[0020] The process is simplified and the risk of timeouts is reduced: This invention eliminates the network redirection step in existing technologies, moving the "identification of cloud phone instances" step forward to the network request interception stage, shortening the entire pre-fetching communication link. This simplified process directly reduces end-to-end response time, effectively reducing timeout errors caused by network latency and improving the success rate of one-click login and user experience.

[0021] The robustness and maintainability of the system are improved: Since the one-click login SDK does not need to concern itself with whether it runs in a cloud phone environment, nor does it require special logic adaptation for cloud phone scenarios (such as handling 302 redirects), the SDK's logic is purer and more universal. This reduces the complexity of SDK development and maintenance, and improves the robustness of the entire authentication system. Attached Figure Description

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

[0023] Figure 1 This is a flowchart of an improved cloud mobile phone number one-click login method according to an embodiment of this application; Figure 2 The signal flow diagram for an improved one-click login method for cloud mobile phone numbers according to this application; Figure 3 This is a structural block diagram of a server according to one embodiment of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0025] like Figure 1 and Figure 2 As shown, a cloud mobile phone number one-click login method in one embodiment of this application includes the following steps: Step 1: After the application APP in the cloud phone triggers one-click login, it calls the one-click login SDK built into the application APP to send an encrypted pre-retrieval number request; In this step, cloud phones are created by installing a cloud phone app on the user's mobile device. The user then operates the cloud phone system in the cloud through the cloud phone app. The cloud phone system creates cloud phone instances, each of which is equivalent to a virtual mobile phone device in the cloud. All network requests initiated by the various apps within the cloud phone instance are sent out through the cloud phone system.

[0026] When a user triggers one-click login in an app within the cloud phone, the app calls the one-click login SDK to pre-retrieve a login number. The one-click login SDK randomly generates a communication key1. Add key1 and the encryption type (AES or SM4) to the request parameters, and use the one-click login SDK's built-in public key to encrypt the request body using RAS.

[0027] Step 2: The cloud phone system intercepts all pre-fetch number requests sent by cloud phone instances, identifies the SDK pre-fetch number identifier, appends the cloud phone instance ID to the header of the pre-fetch number request, and then sends a pre-fetch number request with the cloud phone instance ID. In this step, after the prefetch number request is sent from the cloud phone instance, it is first intercepted by the cloud phone system hosting that instance before reaching the internet. The cloud phone system, acting as a network gateway, can monitor the external network traffic of all cloud phone instances on it.

[0028] The cloud phone system actively intercepts all outgoing network requests and determines that the current request is a pre-fetching number request for one-click login by using preset identification rules (such as the target address, port, or specific identifier in the request body).

[0029] Upon successful identification, the cloud phone system injects a unique ID (instance identifier) ​​identifying the current cloud phone instance into the HTTP request header of the request. In a preferred embodiment, for security reasons, the instance identifier can be encrypted ciphertext.

[0030] After injecting the instance identifier, the cloud phone system forwards the modified pre-fetch number request to its original target address, namely the SDK authentication server. For the SDK within the cloud phone instance, this interception and modification process is completely transparent; it completes the request sending without being aware of it.

[0031] Step 3: The SDK authentication server judges the pre-fetch number request. When the first condition is met, it generates a cloud phone pre-fetch number request based on the cloud phone instance ID and sends it to the cloud phone system. In this step, after receiving the pre-fetch number request, the SDK authentication server uses its private key to decrypt the pre-fetch number request to obtain the request parameters, generates a transaction serial number (random number), and then determines whether the first condition is met.

[0032] The specific method for determining whether the first condition is met is as follows: The requesting IP is compared with the cloud phone system server IP whitelist to determine whether it is a pre-fetching request initiated by an App within the cloud phone; the requesting IP is the source IP of the network request initiated by each App, i.e., the IP of the cloud phone system server; the cloud phone IP whitelist is a list that the cloud phone manufacturer has reported to the one-click login service provider in advance. Based on the AppID in the request parameters, compare it with the whitelist of applications that have enabled the one-click login function for cloud phones to determine whether the current application allows one-click login within the cloud phone. The first condition is met if the request is initiated by an app within the cloud phone and the current app allows one-click login to the cloud phone.

[0033] The server checks the request header for an instance identifier injected by the cloud phone system. If the instance identifier exists, the SDK authentication server confirms that this is a legitimate request from the cloud phone.

[0034] The specific method for generating a cloud phone number pre-fetching request is as follows: Cache request information, with the transaction serial number as the cache key and request parameter information such as key1, encryption type, and SDK version number as the cache value; The ciphertext serial number is generated by encrypting the transaction serial number using AES encryption. The encryption mode is AES / ECB / PKCS5Padding, and the key is a fixed key on the server side. The signature information is calculated based on the encrypted serial number and timestamp. The signature information is generated by concatenating the sorted parameters and values ​​with '&', and finally concatenating a random number as the salt (the random number is cached together with the parameters in step a), generating the original digest string; the original digest string is then calculated using SHA256 to generate the signature information. Concatenate the encrypted serial number, timestamp, signature information, and encrypted cloud phone instance ID into the URL to initiate a cloud phone number pre-fetching request to the cloud phone system.

[0035] Step 4: The cloud phone system receives the cloud phone pre-fetch number request and obtains the cloud phone instance ID. It then triggers the cloud phone app to perform the pre-fetch number operation through the signaling channel between the corresponding cloud phone instance and the cloud phone app. The cloud phone app then sends the pre-fetch number request to the SDK authentication server. In this step, after receiving the request, the cloud phone system decrypts the cloud phone instance ID, sends information through the signaling channel between the cloud phone instance and the cloud phone app, and triggers the cloud phone app's pre-fetching logic. The cloud phone app integrates a customized one-click login SDK. Upon receiving the instruction, it will call the customized SDK's pre-retrieval number method. The input parameters include the encrypted serial number, timestamp, and signature information. The SDK will then send the pre-retrieval number request to the SDK authentication server.

[0036] Step 5: The SDK authentication server verifies the pre-registration number request and returns a response message body when the second condition is met; In this step, the SDK authentication service verifies the request for a pre-registration number after receiving it, specifically including: Verify that the timestamp is within the valid time; return an error message if the timestamp has expired. Decrypt the ciphertext serial number to obtain the transaction serial number, and then use the transaction serial number to query the cached request parameter information; The signature information is calculated and verified based on the encrypted serial number, timestamp, and random number information in the cache. If it is incorrect, an error message is returned; if all verifications pass, the second condition is met.

[0037] Once the second condition is met, the pre-number retrieval request is completed based on the cellular network connection information, and the accessCode and mobile number mask information are generated. The SDK authentication service uses the cached request parameters key1, encryption type, accessCode, and phone number mask information to generate a response message body. The response message body is then returned to the cloud mobile APP by the SDK authentication service.

[0038] Step 6: The cloud phone APP returns the response message body to the cloud phone system through the signaling channel. The cloud phone system sends the response message body to the SDK authentication server. The SDK authentication server returns the response message body to the one-click login SDK. After the one-click login SDK decrypts the response message body, the application APP displays the one-click login authorization page to complete the one-click login. In this step, the cloud phone app receives the pre-retrieval number response message body returned by the customized one-click login SDK, and returns the message body to the cloud phone system through the channel; the cloud phone system receives the response message body and returns the response message to the SDK authentication server; The SDK authentication server returns a pre-fetch number response message to the one-click login SDK; the one-click login SDK decrypts the accessCode and phone number mask information in the response message according to the random key1 and encryption type set during the pre-fetch number request; and returns the decryption result to the application App. After receiving the accessCode and phone number mask, the app displays a one-click login authorization page to the user. After the user agrees to the authorization, the one-click login is completed, and at the same time, a number replacement request can be initiated. The number replacement process involves sending the accessCode to the application server after one-click login authorization to replace the number. The application server sends an accessCode to the SDK authentication server to replace the phone number; the SDK authentication server verifies the accessCode, and returns the complete phone number if the verification is successful. The application server receives the complete mobile phone number to complete the login operation and returns the login result to the application (App).

[0039] like Figure 3 As shown, a server in one embodiment of this application includes: a memory 201 and at least one processor 202; The memory 201 stores a computer program, and the at least one processor 202 executes the computer program stored in the memory 201 to implement the above-mentioned one-click login method for cloud mobile phone numbers.

[0040] According to a third aspect of this application, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed, it implements the above-described one-click login method for cloud mobile phone numbers.

[0041] According to one embodiment of this application, the beneficial effect of using this cloud mobile phone number one-click login method is that: in the cloud mobile phone application one-click login scenario, the cloud mobile phone system actively intercepts and identifies the one-click login SDK pre-fetching number request, reduces the network redirection steps in the pre-fetching number request, avoids the SDK directly interacting with the cloud mobile phone system, and ensures the independence and encapsulation of the SDK. This method sends the number retrieval parameters to the cloud phone app through the signaling channel between the cloud phone instance and the cloud phone app; the cloud phone app has a built-in customized one-click login SDK, which is used to complete the number retrieval of the current SIM card in real time, and returns the number retrieval result to the cloud phone instance and the application app within the instance through the signaling channel, thus completing the one-click login process. The SDK authentication server caches information such as the pre-fetched number communication key and encryption type, and generates a ciphertext serial number. When forwarding messages in the cloud phone system, cloud phone instance, and cloud phone App, it ensures that the transaction parameters will not be intercepted by the cloud phone-related system, thereby improving security. The SDK authentication server caches information such as the pre-fetched number communication key and encryption type, and uses this information to encrypt the number retrieval result of the response. When responding to messages in the cloud phone system, cloud phone instance, and cloud phone App, it ensures that the response result will not be intercepted by the cloud phone-related system, thereby improving security.

[0042] It should be noted that the above detailed descriptions are exemplary and intended to provide further explanation of this application. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains.

[0043] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments according to this application. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0044] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that the embodiments of this application described herein can be implemented in sequences other than those illustrated or described herein.

[0045] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product, or apparatus.

[0046] For ease of description, spatial relative terms such as "above," "on top of," "on the upper surface of," "above," etc., are used herein to describe the spatial positional relationship of a device or feature as shown in the figures to other devices or features. It should be understood that spatial relative terms are intended to encompass different orientations in use or operation beyond the orientation of the device as described in the figures. For example, if the device in the figures were inverted, a device described as "above" or "on top of" other devices or structures would subsequently be positioned as "below" or "under" other devices or structures. Thus, the exemplary term "above" can include both "above" and "below." The device may also be positioned in other different ways, such as rotated 90 degrees or in other orientations, and the spatial relative descriptions used herein will be interpreted accordingly.

[0047] In the detailed description above, reference has been made to the accompanying drawings, which form part of this document. In the drawings, similar symbols typically identify similar parts unless the context otherwise indicates otherwise. The illustrated embodiments described in the detailed specification, drawings, and claims are not intended to be limiting. Other embodiments may be used and other changes may be made without departing from the spirit or scope of the subject matter presented herein.

[0048] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for one-click login using a cloud mobile phone number, characterized in that, The steps include the following: Step 1: After the application APP in the cloud phone system triggers one-click login, it calls the one-click login SDK built into the application APP to send an encrypted pre-retrieval number request; Step 2: The cloud phone system intercepts all pre-fetch number requests sent by cloud phone instances, identifies the SDK pre-fetch number identifier, appends the cloud phone instance ID to the header of the pre-fetch number request, and then sends the pre-fetch number request with the cloud phone instance ID. The cloud phone system acts as a network gateway, intercepting the pre-fetch number request before it reaches the internet, and forwards the pre-fetch number request with the appended cloud phone instance ID to the original target address of the request, i.e., the SDK authentication server. The above interception and cloud phone instance ID appending process is transparent to the one-click login SDK within the cloud phone instance. Step 3: The SDK authentication server judges the pre-fetch number request. When the first condition is met, it generates a cloud phone pre-fetch number request based on the cloud phone instance ID and sends it to the cloud phone system. Step 4: The cloud phone system receives the cloud phone pre-fetch number request and obtains the cloud phone instance ID. It then triggers the cloud phone app to perform the pre-fetch number operation through the signaling channel between the corresponding cloud phone instance and the cloud phone app. The cloud phone app then sends the pre-fetch number request to the SDK authentication server. Step 5: The SDK authentication server verifies the pre-registration number request, and returns a response message to the cloud mobile APP when the second condition is met; Step 6: The cloud phone APP returns the response message body to the cloud phone system through the signaling channel. The cloud phone system sends the response message body to the SDK authentication server. The SDK authentication server returns the response message body to the one-click login SDK. After the one-click login SDK decrypts the message body, the application APP displays the one-click login authorization page to complete the one-click login.

2. The cloud mobile phone number one-click login method according to claim 1, characterized in that, In step 1, the specific method for calling the one-click login SDK to send an encrypted pre-retrieval number request is as follows: The one-click login SDK randomly generates a communication key key1. The communication key key1 and the encryption type are added to the request parameters. The request parameters are then encrypted using the SDK's built-in public key using RAS to complete the encrypted pre-number retrieval request.

3. The cloud mobile phone number one-click login method according to claim 2, characterized in that, In step 3, after receiving the pre-fetch number request, the SDK authentication server uses its private key to decrypt the pre-fetch number request to obtain the request parameters, generates a transaction serial number, and then determines whether the first condition is met.

4. The cloud mobile phone number one-click login method according to claim 3, characterized in that, The specific method for determining whether the first condition is met is as follows: The request IP is compared with the whitelist of cloud phone system server IPs to determine whether it is a pre-fetching request initiated by an application app within the cloud phone. The system compares the AppID in the request parameters with the whitelist of applications that have enabled one-click login for cloud phones to determine whether the current application allows one-click login within the cloud phone. If so, the first condition is met.

5. The cloud mobile phone number one-click login method according to claim 4, characterized in that, In step 3, a cloud phone pre-fetching request is generated based on the cloud phone instance ID. The specific method is as follows: After caching the request parameters, encrypt them to generate a ciphertext serial number, and calculate the signature information based on the ciphertext serial number and the timestamp; The encrypted serial number, timestamp, signature information, and cloud phone instance ID are concatenated into the URL to form a cloud phone pre-fetch number request.

6. The cloud mobile phone number one-click login method according to claim 5, characterized in that, In step 4, the cloud phone system sends information through the signaling channel between the corresponding cloud phone instance and the cloud phone APP to trigger the customized one-click login SDK integrated in the cloud phone APP to send a pre-registration number request. After obtaining the pre-fetch number request, the SDK authentication service verifies it. The second condition includes: the timestamp is within the valid time period, and the cache request parameter information obtained by decrypting the ciphertext serial number is used to calculate and verify that the signature information is correct.

7. The cloud mobile phone number one-click login method according to claim 6, characterized in that, The specific method for returning the response message body is as follows: based on the cellular network connection information, complete the pre-fetch number request and generate accessCode and mobile number mask information; Encrypt the accessCode and phone number mask information using the communication key1 and encryption type from the cached request parameters to generate a response message body; The SDK authentication service returns a response message body, which is then decrypted by the one-click login SDK based on the set communication key1 and encryption type. The accessCode and phone number mask information are then returned to the cloud phone app as a response message.

8. The cloud mobile phone number one-click login method according to claim 6, characterized in that, Step 6 also includes number replacement: after the user agrees to the authorization on the one-click login authorization page, the accessCode is sent to the application server for number replacement; The application server sends an accessCode to the SDK authentication server to perform number replacement; The SDK authentication server verifies the accessCode; if the verification is successful, it returns the complete mobile phone number. The application server receives the complete mobile phone number to complete the login operation and returns the login result to the application (App).

9. A server, characterized in that, include: Memory and at least one processor; The memory stores a computer program, and the at least one processor executes the computer program stored in the memory to implement the cloud mobile phone number one-click login method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed, implements the cloud mobile phone number one-click login method according to any one of claims 1 to 8.

Images