A Method, Server and Storage Medium for One-Click Login with Cloud Mobile Phone Numbers

Abstract

The present application discloses a one-key login method, server and storage medium for cloud mobile phone numbers, belonging to the field of information security, including: after the application APP in the cloud mobile phone triggers one-key login, it calls the built-in one-key login SDK of the application APP to send an encrypted pre-number fetching request; the SDK authentication server judges the pre-number fetching request, and when the first condition is met, generates a redirect URL and returns it to the one-key login SDK; the one-key login SDK redirects the pre-number fetching request to the redirect URL and triggers the proxy pre-number fetching request of the cloud mobile phone, and sends the proxy pre-number fetching request to the SDK authentication server; the SDK authentication server verifies the proxy pre-number fetching request, and when the second condition is met, returns a response message body; the cloud mobile phone receives the response message body and returns it to the application APP, and the application APP displays the one-key login authorization page to complete one-key login. It can enhance the usability and security of one-key login of applications in the cloud mobile phone.

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;

[0005] 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.

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

[0007] To address the deficiencies of the existing technology described above, the present application provides a method, a server, and a storage medium for one-key login of cloud mobile phone numbers. In the scenario of one-key login for cloud mobile phone applications, by utilizing the signaling channel between the cloud mobile phone instance and the cloud mobile phone App, the one-key login SDK within the cloud mobile phone App is triggered to perform the pre-number fetching operation in real time on behalf of the user; and through mechanisms such as ciphertext serial numbers, the security of the number fetching information during transmission within the cloud mobile phone-related systems is ensured while being compatible with the communication rules of the existing one-key login SDK.

[0008] The technical effects to be achieved by the present application are realized through the following solutions:

[0009] According to the first aspect of the present application, there is provided a method for one-key login of cloud mobile phone numbers, including the following steps:

[0010] Step 1: After the application APP within the cloud mobile phone system triggers one-key login, it calls the built-in one-key login SDK of the application APP to send an encrypted pre-number fetching request.

[0011] Step 2: The SDK authentication server determines the pre-number fetching request. When the first condition is met, it generates a redirect URL and returns it to the one-key login SDK.

[0012] Step 3: The one-key login SDK redirects the pre-number fetching request to the corresponding redirect URL, triggers the cloud mobile phone App to perform the pre-number fetching operation on behalf of the user through the signaling channel between the cloud mobile phone system and the cloud mobile phone App, and the cloud mobile phone App sends the pre-number fetching request on behalf of the user to the SDK authentication server.

[0013] Step 4: The SDK authentication server verifies the pre-number fetching request on behalf of the user. When the second condition is met, it returns a response message body.

[0014] Step 5: After the cloud mobile phone App receives the response message, it returns to the cloud mobile phone system through the signaling channel. The cloud mobile phone system returns the response to the application APP, and the application APP displays the one-key login authorization page to complete one-key login.

[0015] Preferably, in Step 1, the specific method for calling the one-key login SDK to send an encrypted pre-number fetching request is as follows:

[0016] The one-key login SDK randomly generates a communication key key1, adds the communication key key1 and the encryption type to the request parameters, and then encrypts the request parameters using the built-in public key of the SDK by RAS to complete the encrypted pre-number fetching request.

[0017] Preferably, in Step 2, after the SDK authentication server receives the pre-number fetching request, it decrypts the pre-number fetching request using the private key to obtain the request parameters, generates a transaction serial number, and then determines whether the first condition is met.

[0018] Preferably, the specific method for determining that the first condition is met is as follows:

[0019] Compare the requesting IP with the whitelist of the cloud phone system server IP to determine whether the prefetch number request is initiated by an application App within the cloud phone;

[0020] Compare the AppID in the request parameters with the whitelist of the application App that enables the one - key login function for the cloud phone to determine whether the current application App allows one - key login within the cloud phone. If so, the first condition is met.

[0021] Preferably, in step 2, a redirect URL is generated and returned to the one - key login SDK. The specific method is as follows:

[0022] After caching the request parameters, encrypt to generate a ciphertext serial number, and calculate the signature information based on the ciphertext serial number and the timestamp;

[0023] Concatenate the ciphertext serial number, the timestamp, and the signature information into the redirect URL. The domain name of the redirect URL is the cloud phone system, and return the redirect URL to the one - key login SDK.

[0024] Preferably, in step 3, after the one - key login SDK redirects the prefetch number request to the redirect 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 - key login SDK integrated in the cloud phone APP to send a proxy prefetch number request;

[0025] After the SDK authentication service obtains the proxy prefetch number request, it verifies it. The second condition includes: the timestamp is within the valid time, and the signature information is calculated and verified correctly based on the cached request parameter information obtained by decrypting the ciphertext serial number.

[0026] Preferably, the specific method for returning the response message body is as follows: According to the cellular network connection information, complete the prefetch number request, and generate an accessCode and a mobile phone number mask information;

[0027] Use the communication key key1 and the encryption type in the cached request parameters to encrypt the accessCode and the mobile phone number mask information to generate the response message body;

[0028] The SDK authentication service returns the response message body. After being decrypted by the one - key login SDK according to the set communication key key1 and the encryption type, the accessCode and the mobile phone number mask information are returned to the cloud phone App as the response message.

[0029] Preferably, step 5 further includes number replacement: After the user agrees to authorize on the one - key login authorization page, send the accessCode to the application server for number replacement;

[0030] The application server sends the accessCode to the SDK authentication server for number replacement;

[0031] The SDK authentication server verifies the accessCode and returns the complete mobile phone number if the verification passes;

[0032] The application server receives the complete mobile phone number, completes the login operation, and returns the login result to the application App.

[0033] According to the second aspect of the present application, a server is provided, including: a memory and at least one processor;

[0034] 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-key cloud mobile phone number login method.

[0035] According to the third aspect of the present application, a computer-readable storage medium is provided, in which a computer program is stored, and when the computer program is executed, the above-mentioned one-key cloud mobile phone number login method is implemented.

[0036] According to an embodiment of the present application, the beneficial effects of adopting the one-key cloud mobile phone number login method are as follows: through the signaling channel between the cloud mobile phone instance and the cloud mobile phone App, the present method sends the prefetch number parameters to the cloud mobile phone App; the cloud mobile phone App is built-in with a customized one-key login SDK, which uses the SDK to complete the prefetch of the current SIM card number in real time, and returns the prefetch result to the cloud mobile phone instance and the application App within the instance through the signaling channel, and finally completes the one-key login process;

[0037] The SDK authentication server caches information such as the prefetch number communication key and encryption type, and generates a ciphertext serial number to ensure that the transaction parameters will not be intercepted by the cloud mobile phone-related systems when forwarding messages within the cloud mobile phone system, cloud mobile phone instance, and cloud mobile phone App, improving security;

[0038] The SDK authentication server caches information such as the prefetch number communication key and encryption type, and encrypts the fetched number result corresponding to the above information to ensure that the response result will not be intercepted by the cloud mobile phone-related systems when answering messages within the cloud mobile phone system, cloud mobile phone instance, and cloud mobile phone App, improving security. Description of the Drawings

[0039] To more clearly illustrate the embodiments of the present application or the existing technical solutions, the following will briefly introduce the drawings required for the description of the embodiments or the existing technical solutions. Obviously, the drawings in the following description are only some embodiments recorded in the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0040] Figure 1 It is a flowchart of a one - key login method for cloud mobile phone numbers in an embodiment of the present application;

[0041] Figure 2 It is a signal flow diagram of a one - key login method for cloud mobile phone numbers of the present application;

[0042] Figure 3 It is a structural block diagram of a server in an embodiment of the present application. Specific embodiments

[0043] To make the purpose, technical solutions, and advantages of the present application clearer, the following will clearly and completely describe the technical solutions of the present application in combination with specific embodiments and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0044] As Figure 1 and Figure 2 shown, the one - key login method for cloud mobile phone numbers in an embodiment of the present application includes the following steps:

[0045] Step 1: After the application APP in the cloud mobile phone triggers one - key login, it calls the built - in one - key login SDK of the application APP to send an encrypted pre - fetch number request;

[0046] In this step, the cloud mobile phone is installed with a cloud mobile phone App on the user's mobile device. Through the cloud mobile phone App, the cloud mobile phone system is operated. The cloud mobile phone system will create a cloud mobile phone instance, and each instance is equivalent to a virtual mobile phone device in the cloud. All network requests initiated by each App inside the cloud mobile phone instance are sent out through the cloud mobile phone system.

[0047] When the user triggers one - key login in a certain application App in the cloud mobile phone, the application App calls the one - key login SDK for the pre - fetch number method:

[0048] The one - key login SDK randomly generates a communication key key1, adds key1 and the encryption type (AES or SM4) to the request parameters, and uses the built - in public key of the one - key login SDK to perform RAS encryption on the request body.

[0049] Step 2: The SDK authentication server judges the prefetch number request. When the first condition is met, a redirect URL is generated and returned to the one-key login SDK.

[0050] In this step, after receiving the prefetch number request, the SDK authentication server decrypts the prefetch number request using the private key to obtain the request parameters, generates a transaction serial number (random number), and then judges whether the first condition is met.

[0051] The specific method for judging that the first condition is met is as follows:

[0052] Compare the request IP with the white list of the cloud mobile phone system server IP to judge whether the prefetch number request is initiated by the App in the cloud mobile phone; the request IP is the source IP of the network request initiated by each App, that is, the IP of the cloud mobile phone system server; the cloud mobile phone IP white list is a list reported by the cloud mobile phone manufacturer to the one-key login service provider in advance.

[0053] Compare the AppID in the request parameters with the white list of the application App that has enabled the one-key login function for the cloud mobile phone to judge whether the current application App allows one-key login in the cloud mobile phone.

[0054] When the request is initiated by the App in the cloud mobile phone and the current App allows one-key login for the cloud mobile phone, the first condition is met.

[0055] The specific method for generating the redirect URL is as follows:

[0056] Cache the request parameters, including AppID, SDK version number, key1, the cellular network IP encrypted with key1, the encryption algorithm used for key1 encryption, timestamp, signature, etc.; set the cache key as the transaction serial number, and the cache value as the request parameter information such as key1, encryption type, SDK version number, etc.

[0057] Use AES to encrypt the transaction serial number to generate a ciphertext serial number. The encryption uses the AES / ECB / PKCS5Padding mode, and the key is the fixed key of the server.

[0058] Calculate the signature information according to the ciphertext serial number and timestamp. The signature information concatenates the sorted parameters and values with &, and finally concatenates a random number as the salt (the random number is cached together with the cached request parameters) to generate a digest original string; use SHA256 to calculate the digest original string to generate the signature information.

[0059] Concatenate the ciphertext serial number, timestamp, and signature information into the redirect URL. The domain name of the redirect URL is the cloud mobile phone system service.

[0060] The SDK authentication service returns a prefetch number response. The response code is 302, and the content is the redirect URL.

[0061] Step 3: The one-key login SDK redirects the prefetch number request to the corresponding redirect URL, triggers the cloud phone App to perform the proxy prefetch number operation through the signaling channel between the cloud phone system and the cloud phone App, and the cloud phone App sends the proxy prefetch number request to the SDK authentication server;

[0062] In this step, when the one-key login SDK receives the prefetch number reply and determines that the reply code is 302, it redirects the request to the redirect URL;

[0063] After the cloud phone system accepts the redirect URL request, it sends information through the signaling channel between the cloud phone instance and the cloud phone App to trigger the proxy prefetch number logic of the cloud phone App;

[0064] The cloud phone App integrates the customized one-key login SDK. After receiving the instruction, it will call the proxy prefetch number method of the customized SDK. The input parameters include the ciphertext serial number, timestamp, and signature information; the SDK sends the proxy prefetch number request to the SDK authentication server.

[0065] Step 4: The SDK authentication server verifies the proxy prefetch number request and returns a response message body when the second condition is met;

[0066] In this step, the specific verification performed by the SDK authentication service after receiving the proxy prefetch number request includes:

[0067] Verify whether the timestamp is within the valid time. If it exceeds the validity period, an error message is returned;

[0068] Decrypt the ciphertext serial number to obtain the transaction serial number, and query the cached request parameter information through the transaction serial number;

[0069] Calculate and verify whether the signature information is correct according to the ciphertext serial number, timestamp, and random number information in the cache. If it is incorrect, an error message is returned; all verifications passed indicate that the second condition is met.

[0070] When the second condition is met, according to the cellular network connection information, complete the prefetch number request, generate the accessCode and mobile phone number mask information;

[0071] Use key1 and the encryption type in the cached request parameters to encrypt the accessCode and mobile phone number mask information, generate the response message body, and the SDK authentication service returns the response message body to the cloud phone APP.

[0072] Step 5: After the cloud phone App receives the response message, it returns 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-key login authorization page to complete one-key login;

[0073] In this step, the cloud phone App receives the prefetch 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;

[0074] The cloud phone system receives the response message body and returns the response message to the one-key login SDK in the application App;

[0075] The one-key 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 during the prefetch number request, and returns the decryption result to the application App;

[0076] After receiving the accessCode and mobile phone number mask, the application App displays the one-key login authorization page to the user. After the user agrees to authorize, the one-key login is completed, and at the same time, a number replacement request can be initiated;

[0077] Among them, the number replacement means that after one-key login authorization, the accessCode is sent to the application server for number replacement;

[0078] 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;

[0079] The application server receives the complete mobile phone number to complete the login operation and returns the login result to the application App.

[0080] As Figure 3 shown, a server in an embodiment of the present application includes: a memory 201 and at least one processor 202;

[0081] 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 cloud mobile phone number one-key login method.

[0082] According to the third aspect of the present application, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, and when the computer program is executed, the above-mentioned cloud mobile phone number one-key login method is implemented.

[0083] According to an embodiment of the present application, the beneficial effects of adopting the above-mentioned cloud mobile phone number one-key login method are as follows: Through the signaling channel between the cloud phone instance and the cloud phone App, this method sends the prefetch number parameters to the cloud phone App; the cloud phone App is built-in with a customized one-key login SDK, which uses the SDK to complete the current SIM card prefetch number in real time and returns the prefetch 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;

[0084] The SDK authentication server caches information such as the communication key and encryption type of the prefetch number, and generates a ciphertext serial number, ensuring that transaction parameters cannot be intercepted by the cloud phone-related systems during message forwarding within the cloud phone system, cloud phone instance, and cloud phone App, thereby enhancing security.

[0085] The SDK authentication server caches information such as the communication key and encryption type of the prefetch number, and encrypts the number fetching result corresponding to the above information. During message response within the cloud phone system, cloud phone instance, and cloud phone App, it ensures that the response result cannot be intercepted by the cloud phone-related systems, thereby enhancing security.

[0086] It should be noted that the above detailed description is exemplary and is 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 technical field to which the present application belongs.

[0087] 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, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0088] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above figures are used to distinguish similar objects and do not necessarily have to be used to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein.

[0089] In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or devices.

[0090] For ease of description, spatial relative terms such as "above", "over", "on the upper surface", "upper" etc. may be used herein to describe the spatial positional relationship of one device or feature to other devices or features as shown in the figures. It should be understood that the spatial relative terms are intended to encompass different orientations in use or operation in addition to the orientation depicted in the figures. For example, if the device in the figures is inverted, a device described as "above" or "over" other devices or structures will then be positioned "below" or "under" the other devices or structures. Thus, the exemplary term "above" can include both the orientations of "above" and "below". The device may also be positioned in other different ways, such as rotated 90 degrees or in other orientations, and the corresponding explanations are made for the spatial relative descriptions used herein.

[0091] In the foregoing detailed description, reference has been made to the accompanying drawings, which form a part hereof. In the drawings, like symbols typically identify like components, unless the context indicates otherwise. The illustrated embodiments described in the detailed description, the drawings, and the 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.

[0092] The above are only the preferred embodiments of the present invention and are not used to limit the present invention. For those skilled in the art, the present invention may have various changes and modifications. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A one-key login method for cloud mobile phone numbers, characterized in that, It includes the following steps: Step 1: After the application APP in the cloud mobile phone system triggers one-key login, it calls the built-in one-key login SDK of the application APP to send an encrypted pre-number fetching request; the one-key login SDK randomly generates a communication key key1, adds the communication key key1 and the encryption type to the request parameters, and then encrypts the request parameters using the built-in public key of the SDK to complete the encrypted pre-number fetching request; Step 2: The SDK authentication server judges the pre-number fetching request. When the first condition is met, it generates a redirect URL and returns it to the one-key login SDK; after receiving the pre-number fetching request, the SDK authentication server decrypts the pre-number fetching request using the private key to obtain the request parameters, generates a transaction serial number, and then judges whether the first condition is met; The specific method for judging that the first condition is met is: compare the request IP with the whitelist of the cloud mobile phone system server IP to judge whether the pre-number fetching request is initiated by the application App in the cloud mobile phone; compare the AppID in the request parameters with the whitelist of the application App that has enabled the one-key login function of the cloud mobile phone to judge whether the current application App allows one-key login in the cloud mobile phone. If so, the first condition is met; Step 4: The one-key login SDK redirects the pre-number fetching request to the corresponding redirect URL, triggers the cloud mobile phone App to perform a proxy pre-number fetching operation through the signaling channel between the cloud mobile phone system and the cloud mobile phone App, and the cloud mobile phone App sends the proxy pre-number fetching request to the SDK authentication server; after the one-key login SDK redirects the pre-number fetching request to the redirect URL, the cloud mobile phone system sends information through the signaling channel between the cloud mobile phone instance and the cloud mobile phone APP to trigger the customized one-key login SDK integrated in the cloud mobile phone APP to send a proxy pre-number fetching request; Step 5: The SDK authentication server verifies the proxy pre-number fetching request. When the second condition is met, it returns a response message body; after obtaining the proxy pre-number fetching request, the SDK authentication service verifies it. The second condition includes: the timestamp is within the valid time, and the signature information is calculated and verified correctly by decrypting the ciphertext serial number to obtain the cached request parameter information; The specific method for returning the response message body is: complete the pre-number fetching request according to the cellular network connection information, and generate an accessCode and a mobile phone number mask information; Encrypt the accessCode and the mobile phone number mask information using the communication key key1 and the encryption type in the cached request parameters to generate a response message body; The SDK authentication service returns the response message body, which is decrypted by the one-key login SDK according to the set communication key key1 and encryption type, and the accessCode and the mobile phone number mask information are returned to the cloud mobile phone App as a response message; Step 5: After the cloud mobile phone App receives the response message, it returns to the cloud mobile phone system through the signaling channel. The cloud mobile phone system returns the response to the application App, and the application APP displays the one-key login authorization page to complete one-key login.

2. The one-key login method for cloud mobile phone numbers according to claim 1, wherein, In step 2, the method for generating a redirect URL and returning it to the one-key login SDK is specifically: After caching the request parameters, encrypt and generate a ciphertext serial number, and calculate the signature information based on the ciphertext serial number and the timestamp; Concatenate the ciphertext serial number, the timestamp, and the signature information to the redirect URL. The domain name of the redirect URL is the cloud mobile phone system, and return the redirect URL to the one-key login SDK.

3. The one-key login method for cloud mobile phone numbers according to claim 2, wherein In step 5, number replacement is also included: after the user agrees to authorize on the one-key login authorization page, send the accessCode 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 is passed; The application server receives the complete mobile phone number to complete the login operation and returns the login result to the application App.

4. A server, characterized in that, Including: 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 cloud mobile phone number one-key login method according to any one of claims 1 to 3.

5. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, and when the computer program is executed, it implements the cloud mobile phone number one-key login method according to any one of claims 1 to 3.

Images