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

Abstract

The invention discloses a cloud mobile phone number one-key login method, a server and a storage medium, and belongs to the field of information security, and the method comprises the steps: calling a built-in one-key login SDK of an application APP to send an encrypted number prefetching request after the application APP in a cloud mobile phone triggers one-key login; the SDK authentication server judges the number prefetching request, and when a first condition is met, a redirection URL is generated and returned to the one-key login SDK; the one-key login SDK redirects the number prefetching request to a redirection URL, triggers a number prefetching request of the cloud mobile phone, and sends the number prefetching request to an SDK authentication server; the SDK authentication server verifies the number prefetching request and returns a response message body when a second condition is met; and the cloud mobile phone receives the response message body and returns the response message body to the application APP, and the application APP displays a one-key login authorization page to complete one-key login. The availability and security of application one-key login in the cloud mobile phone can be enhanced.

Description

Technical Field

[0001] The present application belongs to the field of information security, and in particular relates to a one-click login method for a cloud mobile phone number, a server, and a storage medium. Background Art

[0002] The operator's mobile phone number one-click login uses the smartphone's cellular network to initiate a data request to the operator's SDK authentication server, and the SDK authentication server obtains the complete mobile phone number information from the cellular network connection. In the cloud phone application scenario, users operate cloud phone instances through cloud phone apps on their smartphones. Cloud phone instances run in the cloud phone system on the cloud and do not have a real cellular network. Therefore, the mobile phone number one-click login process for third-party apps in cloud phone instances is different from ordinary one-click login.

[0003] Currently, in the one-click login scenario of the application App in the cloud phone, the one-click login with the mobile phone number is forcibly triggered when the cloud phone App is started, and the binding relationship between the cloud phone instance and the mobile phone number is established; when a third-party application in the cloud phone instance performs one-click login, the SDK authentication service intercepts the pre-number request through the cloud phone system IP whitelist and redirects the request to the cloud phone system. The cloud phone system adds the cloud phone instance information in the request and forwards the request to the SDK authentication server. The SDK authentication server queries the binding information through the cloud phone instance information to obtain the mobile phone number, returns the pre-number result, and finally completes the number replacement operation; when the user exits the cloud phone instance, the system will release the binding relationship with the mobile phone number.

[0004] The above one-click login method for cloud phones has the following disadvantages: First, the cloud phone app must be forced to use one-click login to complete the binding of the cloud phone instance and the mobile phone number. After logging in using other methods, the one-click login of the cloud phone application app will not be able to complete the number acquisition operation normally, which limits the use scenario of the cloud phone one-click login; Secondly, after the cloud phone App completes the binding operation between the cloud phone instance and the mobile phone number through one-click login, if you change the SIM card of the smartphone, the old mobile phone number will still be obtained when you log in to the cloud phone application App with one click, which may pose security risks such as incorrect number acquisition.

[0005] Therefore, a technical solution for one-click login with a cloud phone number is needed to solve the above problems. Summary of the invention

[0006] In order to address the deficiencies of the prior art, the present application provides a one-click login method, server and storage medium for a cloud phone number. In the one-click login scenario of a cloud phone application, the signaling channel between the cloud phone instance and the cloud phone App is utilized to trigger the one-click login SDK in the cloud phone App to complete the pre-number acquisition operation in real time; and through mechanisms such as encrypted serial numbers, the security of the number acquisition information during transmission within the cloud phone-related system is ensured while being compatible with the existing one-click login SDK communication rules.

[0007] The technical effects to be achieved by this application are achieved through the following solutions: According to the first aspect of the present application, a one-click login method for a cloud 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 SDK authentication server judges the pre-number request, generates a redirection URL when the first condition is met, and returns to the one-click login SDK; Step 3: Log in to the SDK with one click to redirect the pre-number request to the corresponding redirection URL, trigger the cloud phone app to perform the pre-number operation through the signaling channel between the cloud phone system and the cloud phone app, and the cloud phone app sends the pre-number request to the SDK authentication server; Step 4: The SDK authentication server verifies the request for pre-number acquisition and returns a response message body when the second condition is met; Step 5: After the cloud phone App receives the response message, it returns it to the cloud phone system through the signaling channel. The cloud phone system returns the response to the application App, and the application App displays the one-click login authorization page to complete the one-click login.

[0008] Preferably, in step 1, the specific method of calling the one-click login SDK to issue an encrypted pre-retrieval number request is: The one-click login SDK randomly generates a communication key key1, adds the communication key key1 and the encryption type to the request parameters, and then uses the SDK's built-in public key to perform RAS encryption on the request parameters to complete the encrypted pre-number request.

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

[0010] Preferably, the specific method for determining whether the first condition is met is: Compare the request IP with the whitelist of the cloud phone system server IP to determine whether it is a pre-number request initiated by the application App in the cloud phone; By comparing the AppID in the request parameter with the whitelist of application apps that have enabled the one-click login function on the cloud phone, it is determined whether the current application app allows one-click login on the cloud phone. If so, the first condition is met.

[0011] Preferably, in step 2, a redirection URL is generated and returned to the one-click login SDK, the specific method is: After caching the request parameters, encrypt and generate a ciphertext serial number, and calculate the signature information based on the ciphertext serial number and timestamp; The ciphertext serial number, timestamp and signature information are concatenated into the redirection URL, the redirection URL domain name is the cloud phone system, and the redirection URL is returned to the one-click login SDK.

[0012] Preferably, in step 3, after the one-click login SDK redirects the pre-number acquisition request to the redirection URL, the cloud phone system sends information through the signaling channel between the 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-number acquisition request on behalf of the cloud phone APP; The SDK authentication service obtains the pre-number request and verifies it, and the second condition includes: the timestamp is within the valid time, and the cache request parameter information obtained by decrypting the ciphertext serial number calculates and verifies that the signature information is correct.

[0013] Preferably, the specific method of returning the response message body is: completing the pre-number acquisition request according to the cellular network connection information, and generating the accessCode and the mobile phone number mask information; Use the communication key key1 and encryption type in the cache request parameters to encrypt the accessCode and mobile phone number mask information and generate a response message body; The SDK authentication service returns a response message body, which is decrypted by the one-click login SDK according to the set communication key key1 and encryption type, and then the accessCode and mobile phone number mask information are returned to the cloud phone App as a response message.

[0014] Preferably, step 5 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 the accessCode to the SDK authentication server to replace the number; The SDK authentication server verifies the accessCode and returns the complete mobile 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.

[0015] According to a second aspect of the present 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 a cloud phone number.

[0016] According to a third aspect of the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed, the one-click login method for the cloud phone number is implemented.

[0017] According to an embodiment of the present application, the beneficial effects of using the one-key login method of the cloud phone number are: the method sends the pre-acquired number 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-key login SDK, which uses the SDK to complete the current SIM card pre-acquired number in real time, and returns the pre-acquired number result to the cloud phone instance and the application App in the instance through the signaling channel, and finally completes the one-key login process; The SDK authentication server caches the pre-fetched communication key and encryption type information, and generates a ciphertext serial number to ensure that transaction parameters will not be intercepted by cloud phone related systems when forwarding messages within the cloud phone system, cloud phone instance, and cloud phone App, thereby improving security; The SDK authentication server caches information such as the pre-acquisition communication key and encryption type, and uses the above information to encrypt the number acquisition result of the response. When the message response is made 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present application or the existing technical solutions, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0019] Figure 1 This is a flow chart of a one-click login method for a cloud phone number in an embodiment of the present application; Figure 2 A signal flow diagram of a one-click login method for a cloud mobile phone number for this application; Figure 3 This is a structural block diagram of a server in an embodiment of the present application. DETAILED DESCRIPTION

[0020] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0021] like Figure 1 and Figure 2 As shown, the one-key login method of the cloud phone number in an embodiment of the present 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, the cloud phone is installed on the user's mobile phone device, and the cloud phone system in the cloud is operated through the cloud phone App. The cloud phone system will create cloud phone instances. Each instance is equivalent to a virtual mobile device in the cloud. The network requests initiated by each App within the cloud phone instance are sent through the cloud phone system.

[0022] The user triggers one-click login in an app in the cloud phone, and the app calls the one-click login SDK to pre-fetch the number: The One-Click Login SDK randomly generates a communication key key1, adds key1 and encryption type (AES or SM4) to the request parameters, and uses the One-Click Login SDK's built-in public key to perform RAS encryption on the request body.

[0023] Step 2: The SDK authentication server judges the pre-number request, generates a redirection URL when the first condition is met, and returns to the one-click login SDK; In this step, after receiving the pre-retrieval request, the SDK authentication server uses the private key to decrypt the pre-retrieval request to obtain the request parameters, and generates a transaction serial number (random number), and then determines whether the first condition is met.

[0024] The specific method for judging whether the first condition is met is: Compare the request IP with the cloud phone system server IP whitelist to determine whether it is a pre-number request initiated by an App in the cloud phone; the request IP is the source IP of the network request initiated by each App, that is, the IP of the cloud phone system server; the cloud phone IP whitelist is a list reported in advance by the cloud phone manufacturer to the one-click login service provider; Compare the AppID in the request parameter with the whitelist of apps that have enabled the one-click login function on the cloud phone to determine whether the current app allows one-click login on the cloud phone. When the request is initiated by an App in the cloud phone and the current App allows one-click login to the cloud phone, the first condition is met.

[0025] The specific method to generate a redirect URL is: Cache request parameters, including AppID, SDK version number, key1, cellular network IP encrypted with key1, encryption algorithm used for key1 encryption, timestamp, signature, etc.; set the cache key to the transaction serial number, and the cache value to key1, encryption type, SDK version number and other request parameter information; Use AES to encrypt the transaction serial number to generate a ciphertext serial number. The encryption adopts AES / ECB / PKCS5Padding mode, and the key is the server-side fixed key. The signature information is calculated based on the ciphertext serial number and timestamp. The signature information concatenates the sorted parameters and values ​​with &, and finally concatenates a random number as a salt (the random number is cached together with the cache request parameter) to generate the digest original string; SHA256 is used to calculate the digest original string to generate the signature information; The ciphertext serial number, timestamp, and signature information are concatenated into the redirection URL, and the redirection URL domain name is the cloud phone system service; The SDK authentication service returns a pre-retrieval number response with a response code of 302 and a redirection URL.

[0026] Step 3: Log in to the SDK with one click to redirect the pre-number request to the corresponding redirection URL, trigger the cloud phone app to perform the pre-number operation through the signaling channel between the cloud phone system and the cloud phone app, and the cloud phone app sends the pre-number request to the SDK authentication server; In this step, after the one-click login SDK receives the pre-retrieved number response, if the response code is 302, it redirects the request to the redirection URL; After the cloud phone system receives the redirection URL request, it sends information through the signaling channel between the cloud phone instance and the cloud phone App to trigger the cloud phone App's logic for pre-fetching numbers; The cloud phone App integrates a customized one-click login SDK. After receiving the command, it will call the customized SDK pre-number method. The input parameters include the ciphertext serial number, timestamp, and signature information; the SDK sends the pre-number request to the SDK authentication server.

[0027] Step 4: The SDK authentication server verifies the request for pre-number acquisition and returns a response message body when the second condition is met; In this step, after receiving the request for pre-ordering number, the SDK authentication service performs verification including: Verify whether the timestamp is within the valid period, and return an error message if it exceeds the valid period; Decrypt the ciphertext serial number to obtain the transaction serial number, and query the cache request parameter information through the transaction serial number; The signature information is calculated and verified to be correct based on the ciphertext serial number, timestamp, and random number information in the cache. If it is incorrect, an error message is returned; if all verifications pass, it means that the second condition is met.

[0028] When the second condition is met, the pre-number request is completed according to the cellular network connection information, and the accessCode and mobile phone number mask information are generated; Use key1 and encryption type in the cache request parameters to encrypt accessCode and mobile phone number mask information, generate a response message body, and the SDK authentication service returns the response message body to the cloud phone APP.

[0029] Step 5: After the cloud phone App receives the response message, it returns it to the cloud phone system through the signaling channel. The cloud phone system returns the response to the application App, and 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-order number response message body returned by the customized one-key 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 one-click login SDK in the application App; The one-click login SDK decrypts the accessCode and mobile phone number mask information in the response message according to the random key key1 and encryption type set when the pre-retrieval number request is made, and returns the decryption result to the application App; After receiving the accessCode and mobile phone number mask, the App displays the one-click login authorization page to the user. After the user agrees to the authorization, the one-click login is completed and a number replacement request can be initiated at the same time. The number replacement means that after one-click login authorization, the accessCode is sent to the application server for number replacement; The application server sends the accessCode to the SDK authentication server for number replacement; the SDK authentication server verifies the accessCode and returns the complete mobile phone number if the verification passes; The application server receives the complete mobile phone number to complete the login operation and returns the login result to the application App.

[0030] like Figure 3 As shown, a server in an embodiment of the present 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 a cloud phone number.

[0031] According to a third aspect of the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed, the one-click login method for the cloud phone number is implemented.

[0032] According to an embodiment of the present application, the beneficial effects of using the one-key login method of the cloud phone number are: the method sends the pre-acquired number 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-key login SDK, which uses the SDK to complete the current SIM card pre-acquired number in real time, and returns the pre-acquired number result to the cloud phone instance and the application App in the instance through the signaling channel, and finally completes the one-key login process; The SDK authentication server caches the pre-fetched communication key and encryption type information, and generates a ciphertext serial number to ensure that transaction parameters will not be intercepted by cloud phone related systems when forwarding messages within the cloud phone system, cloud phone instance, and cloud phone App, thereby improving security; The SDK authentication server caches information such as the pre-acquisition communication key and encryption type, and uses the above information to encrypt the number acquisition result of the response. When the message response is made 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.

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

[0034] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should also be understood that when the terms "comprise" and / or "include" are used in this specification, it indicates the presence of features, steps, operations, devices, components and / or combinations thereof.

[0035] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein.

[0036] In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. 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 explicitly listed, but may include other steps or units that are not explicitly listed or inherent to these processes, methods, products, or apparatuses.

[0037] For ease of description, spatially relative terms, such as "above", "above", "on the upper surface of", "above", etc., may be used herein to describe the spatial positional relationship between a device or feature and other devices or features as shown in the figure. It should be understood that spatially relative terms are intended to include different orientations of the device in use or operation in addition to the orientation described in the figure. For example, if the device in the accompanying drawings is inverted, the device described as "above other devices or structures" or "above other devices or structures" will be positioned as "below other devices or structures" or "below other devices or structures". Thus, the exemplary term "above" may 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 spatially relative descriptions used herein are interpreted accordingly.

[0038] In the above detailed description, reference is made to the accompanying drawings, which form a part of this document. In the accompanying drawings, similar symbols typically identify similar components unless the context indicates otherwise. The illustrated embodiments described in the detailed description, drawings, and claims are not meant 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.

[0039] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A one-click login method for a cloud phone number, characterized in that: The steps include: 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 SDK authentication server judges the pre-number request, generates a redirection URL when the first condition is met, and returns to the one-click login SDK; Step 3: Log in to the SDK with one click to redirect the pre-number request to the corresponding redirection URL, trigger the cloud phone app to perform the pre-number operation through the signaling channel between the cloud phone system and the cloud phone app, and the cloud phone app sends the pre-number request to the SDK authentication server; Step 4: The SDK authentication server verifies the request for pre-number acquisition and returns a response message body when the second condition is met; Step 5: After the cloud phone App receives the response message, it returns it to the cloud phone system through the signaling channel. The cloud phone system returns the response to the application App, and the application App displays the one-click login authorization page to complete the one-click login.

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

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

4. The one-key login method for cloud mobile phone number according to claim 3 is characterized in that: The specific method for judging whether the first condition is met is: Compare the request IP with the whitelist of the cloud phone system server IP to determine whether it is a pre-number request initiated by the application App in the cloud phone; By comparing the AppID in the request parameter with the whitelist of application apps that have enabled the one-click login function on the cloud phone, it is determined whether the current application app allows one-click login on the cloud phone. If so, the first condition is met.

5. The one-key login method for cloud mobile phone number according to claim 4 is characterized in that: In step 2, generate a redirect URL and return to the One-Click Login SDK. The specific method is as follows: After caching the request parameters, encrypt and generate a ciphertext serial number, and calculate the signature information based on the ciphertext serial number and timestamp; The ciphertext serial number, timestamp and signature information are concatenated into the redirection URL, the redirection URL domain name is the cloud phone system, and the redirection URL is returned to the one-click login SDK.

6. The one-key login method for cloud phone number according to claim 5, characterized in that: In step 3, after the one-click login SDK redirects the pre-number acquisition request to the redirection URL, the cloud phone system sends information through the signaling channel between the 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-number acquisition request on behalf of the cloud phone APP; The SDK authentication service obtains the pre-number request and verifies it, and the second condition includes: the timestamp is within the valid time, and the cache request parameter information obtained by decrypting the ciphertext serial number calculates and verifies that the signature information is correct.

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

8. The one-key login method for cloud phone number according to claim 6, characterized in that: Step 5 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 the accessCode to the SDK authentication server to replace the number; The SDK authentication server verifies the accessCode and returns the complete mobile 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.

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 one-click login method for a cloud phone number as described in 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, and when the computer program is executed, the one-click login method for a cloud phone number described in any one of claims 1 to 8 is implemented.

Images