Man-machine verification login method based on SIM card

Abstract

The invention relates to a man-machine verification login method based on an SIM (Subscriber Identity Module) card, and relates to the technical field of communication. According to the method, a preposed identity information consistency judgment process is added on the basis of traditional one-key login. The method mainly comprises the following steps: an application APP is responsible for triggering a one-key login function and activating an operator sdk to work; the APP server is responsible for supporting all operations of the APP; the operator sdk is responsible for judging that one-key login is used for the first time, triggering identity information filling, triggering human-card consistency verification through the identity information, and triggering uid information generation and card writing operation if the verification is passed; and the operator server provides data interaction and service calling capabilities for the sdk, and provides specific code implementation of a bottom layer of the method at the same time. According to the invention, the problem of information leakage caused by one-key login due to inconsistent machine and card can be effectively solved.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a human-machine verification login method based on a SIM card. Background Art

[0002] With the rapid development and popularization of the Internet, the security authentication of users in various applications has become a focus of attention. Various login methods have emerged one after another, such as account and password login, dynamic verification code, biometrics, one-click login, etc., but each login method has problems. Account and password login will increase the burden of remembering passwords for users, affecting the login experience; dynamic verification codes may cause account login abnormalities due to network delays and illegal theft; biometrics may leak user biometric information and consume too long login time; one-click login does not perform human-machine verification, as long as you get a mobile phone card, you can log in to the application with one click and obtain user information.

[0003] The specific scenario is: when user a's mobile phone is accidentally lost and picked up by user b, although mobile phone a has high-security login methods such as face and fingerprint, it is impossible to obtain the user's mobile phone content normally. However, as a large number of users adopt the one-click login method, the SIM card a is taken out and put into mobile phone b, the information of user a in various software can be obtained, which may cause information leakage at the least and even lead to loss of funds at worst.

[0004] In view of the above scenario, a SIM card-based human-machine verification login method is proposed, which realizes human-machine verification without affecting the advantage of convenient login. Summary of the invention

[0005] The present invention is intended to provide a human-machine verification login method, electronic device and storage medium based on a SIM card to solve the deficiencies in the prior art. The technical problem to be solved by the present invention is achieved through the following technical solutions.

[0006] In a first aspect, a human-machine verification login method based on a SIM card, the method comprising:

[0007] S1, the user initiates a pre-acquisition number login request;

[0008] S2, receiving the login request through the application APP and calling the operator SDK;

[0009] S3, obtaining the uid field of the SIM card of the user's mobile device according to the operator sdk; if the uid field exists, executing step S12; if the uid field does not exist, executing step S4;

[0010] S4, when the uid field does not exist, returning non-existence information to the operator sdk;

[0011] S5, returning the non-existence information of the uid field to the operator server;

[0012] S6, sending a data SMS to the corresponding mobile device SIM through the operator server and requesting an h5 link;

[0013] S7, accessing the h5 link through the SIM card application, entering personal information into the page and returning it to the operator server;

[0014] S8, calling the identity authentication interface to verify the authenticity of the information;

[0015] S9, authentication is successful, a number acquisition request is initiated, the mobile phone number, masked mobile phone number, authentication code are obtained, and a UID is generated;

[0016] S10, write the uid into the SIM card via a data SMS, triggering the operator's SDK to execute step 3;

[0017] S11, authentication failed, re-execute step 6;

[0018] S12, return the uidx read from the SIM card to the operator SDK;

[0019] S13, passing the uidx to the operator server through the operator sdk, and accessing the number acquisition request;

[0020] S14, obtaining the mobile phone number, masked mobile phone number, and authentication code through the operator server, and generating a UID;

[0021] S15, performing consistency comparison between the uid and uidx; if they are inconsistent, executing step S16, and if they are consistent, executing step S17;

[0022] S16, if inconsistent, send a data SMS to the SIM card, request personal information to fill in the h5 page, and then continue to execute step S7;

[0023] S17, when they are consistent, returning the masked mobile phone number and the authentication code to the operator SDK;

[0024] S18, pull up the authorization page to the application APP through the operator SDK;

[0025] S19, displaying the masked mobile phone number to the user through the authorization page;

[0026] S20, based on the user's confirmation, returning the confirmation information to the operator's SDK;

[0027] S21, passing the authentication code to the application APP through the operator SDK;

[0028] S22, transmitting the authentication code to the APP server through the application APP;

[0029] S23, initiating a replacement request to the operator server through the APP server;

[0030] S24, returning the mobile phone number to the APP server through the operator server;

[0031] S25, completing the login using the mobile phone number through the APP server;

[0032] S26, entering the APP application through the user side.

[0033] In some implementations, S1, based on a pre-recorded number login request initiated by the user side, marks the user and the mobile phone through the uid field.

[0034] In some implementations, S6 further includes pre-downloading the card application on the SIM card of the mobile device by using an over-the-air card writing technology.

[0035] In some implementations, in S8, the user authentication interface includes an interface provided by a third party or an operator.

[0036] In some implementations, in S9, the mobile phone number includes an 11-digit mobile phone number, and the masked mobile phone number includes marking the last four digits of the 11-digit mobile phone number with *; the authentication code includes a set of fixed-length strings, and establishes a key-value pair relationship with the mobile phone number.

[0037] In some implementations, in S10, the uid is written into the SIM card by using an over-the-air card writing technology.

[0038] In a second aspect, an embodiment of the present invention provides an electronic device, comprising a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein when the one or more computer instructions are executed by the processor, the method described in the first aspect above is implemented.

[0039] In a third aspect, an embodiment of the present invention provides a computer storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it is used to implement the method described in the first aspect.

[0040] The embodiments of the present invention include the following advantages:

[0041] The method of the present invention adds a pre-identity information consistency judgment process on the basis of the traditional one-key login. It mainly includes: the application APP is responsible for triggering the one-key login function and activating the operator SDK; the application APP server is responsible for supporting all operations of the application APP; the operator SDK is responsible for judging the first use of the one-key login and triggering the identity information filling, and at the same time triggering the person-card consistency check through the identity information, and triggering the uid information generation and card writing operation if the check passes; the operator server provides the SDK with data interaction and service call capabilities, and provides the underlying specific code implementation of the method. The present invention can effectively solve the information leakage problem caused by inconsistent machine-card one-key login. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 It is an implementation flow chart of a human-machine verification login method based on a SIM card of the present invention. DETAILED DESCRIPTION

[0043] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0044] Embodiment 1:

[0045] Figure 1 A flow chart of the implementation of a human-machine verification login method based on a SIM card is shown, as Figure 1 As shown, the human-machine verification login method based on the SIM card provided in this embodiment includes:

[0046] S1, the user initiates a pre-acquisition number login request;

[0047] S2, receiving the login request through the application side and calling the operator SDK;

[0048] S3, obtaining the uid field of the SIM card of the user's mobile device according to the operator sdk; if the uid field exists, executing step S12; if the uid field does not exist, executing step S4;

[0049] S4, when the uid field does not exist, returning non-existence information to the operator sdk;

[0050] S5, returning the non-existence information of the uid field to the operator server;

[0051] S6, sending a data SMS to the corresponding mobile device SIM through the operator server and requesting an h5 link;

[0052] S7, accessing the h5 link through the SIM card application, entering personal information into the page and returning it to the operator server;

[0053] S8, calling the identity authentication interface to verify the authenticity of the information;

[0054] S9, authentication is successful, a number acquisition request is initiated, the mobile phone number, masked mobile phone number, authentication code are obtained, and a UID is generated;

[0055] S10, write the uid into the SIM card via a data SMS, triggering the operator's SDK to execute step 3;

[0056] S11, authentication failed, re-execute step 6;

[0057] S12, return the uidx read from the SIM card to the operator SDK;

[0058] S13, passing the uidx to the operator server through the operator sdk, and accessing the number acquisition request;

[0059] S14, obtaining the mobile phone number, masked mobile phone number, and authentication code through the operator server, and generating a UID;

[0060] S15, performing consistency comparison between the uid and uidx; if they are inconsistent, executing step S16, and if they are consistent, executing step S17;

[0061] S16, if inconsistent, send a data SMS to the SIM card, request personal information to fill in the h5 page, and then continue to execute step S7;

[0062] S17, when they are consistent, returning the masked mobile phone number and the authentication code to the operator SDK;

[0063] S18, pull up the authorization page to the application APP through the operator SDK;

[0064] S19, displaying the masked mobile phone number to the user through the authorization page;

[0065] S20, based on the user's confirmation, returning the confirmation information to the operator's SDK;

[0066] S21, passing the authentication code to the application APP through the operator SDK;

[0067] S22, transmitting the authentication code to the APP server through the application APP;

[0068] S23, initiating a replacement request to the operator server through the APP server;

[0069] S24, returning the mobile phone number to the APP server through the operator server;

[0070] S25, completing the login using the mobile phone number through the APP server;

[0071] S26, entering the APP application through the user side.

[0072] Furthermore, S1, according to the pre-recorded number login request initiated by the user side, marks the user and the mobile phone through the uid field.

[0073] Among them, uid (Unique Identifier) ​​is used to mark the relationship between the user and the mobile phone; this content is implemented through the mobile phone number and user identity information, the specific implementation method is not specified, and the form of providing user identity information is not specified. For example: the user identity information is the name, ID number and IMSI, then the user information and the cellular network account will be checked to see if the information is consistent. If they are consistent, uid is generated, and a unique identifier is generated based on the mobile phone number + IMSI (such as: using SHA256 or SM3, etc.), and then stored in the SIM card

[0074] Furthermore, the S6 also includes pre-downloading the card application on the SIM card of the mobile device through the over-the-air card writing technology.

[0075] Send a data SMS to the SIM card through the operator's server to start filling in the h5 page for personal information. This process requires the relevant card application to be pre-downloaded on the SIM card, based on the Over-the-Air (OTA) technology;

[0076] Furthermore, in said S8, the user authentication interface includes an interface provided by a third party or an operator.

[0077] Furthermore, in said S9, said mobile phone number comprises an 11-digit mobile phone number, said masked mobile phone number comprises marking the last four digits of said 11-digit mobile phone number with *; said authentication code comprises a set of fixed-length character strings, and establishes a key-value pair relationship with said mobile phone number.

[0078] For example, a mobile phone number is a common 11-digit mobile phone number (such as 138 3534 2345); a masked mobile phone number is a mobile phone number with the last four digits marked by *, mainly to indicate which mobile phone number is obtained and ensure that the user knows which account to log in (such as 1383534****); an authentication code is a set of fixed-length strings, which establishes a key-value pair relationship, namely, authentication code-mobile phone number and masked mobile phone number (key-value), and there is no mandatory limit on its length. Further, in the S10, the uid is written into the SIM card through the air card writing technology.

[0079] Writing and reading data to a SIM card usually involves the technology of Over-The-Air (OTA), which is a technology that allows SIM card data to be updated wirelessly. For traditional SIM cards, this is usually not something that users can do by themselves, because it requires the operator's network and specific equipment to implement. But for eSIM (embedded SIM card), users can download operator profiles and activate services through remote configuration without a physical SIM card.

[0080] Embodiment 2:

[0081] This embodiment further provides an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor using the method of embodiment 1;

[0082] In practical applications, the processor can be an application specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a controller, a microcontroller unit (MCU), a microprocessor or other electronic components to execute the methods in the above embodiments.

[0083] The method implemented in this embodiment is as shown in the first embodiment.

[0084] Embodiment three:

[0085] This embodiment further provides a computer storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by one or more processors, the method of the first embodiment is implemented;

[0086] Among them, the computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, disk or optical disk.

[0087] The method implemented in this embodiment is as shown in the first embodiment.

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

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

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

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

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

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

[0094] The above description is only a preferred embodiment of the present invention and is 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 human-machine verification login method based on a SIM card, characterized in that: The method includes: S1, the user initiates a pre-acquisition number login request; S2, receiving the login request through the application APP and calling the operator SDK; S3, obtaining the uid field of the SIM card of the user's mobile device according to the operator sdk; if the uid field exists, executing step S12; if the uid field does not exist, executing step S4; S4, when the uid field does not exist, returning non-existence information to the operator sdk; S5, returning the non-existence information of the uid field to the operator server; S6, sending a data SMS to the corresponding mobile device SIM through the operator server and requesting an h5 link; S7, accessing the h5 link through the SIM card application, inputting personal information into the page and returning it to the operator server; S8, calling the identity authentication interface to verify the authenticity of the information; S9, authentication is successful, a number acquisition request is initiated, the mobile phone number, masked mobile phone number, authentication code are obtained, and a UID is generated; S10, write the uid into the SIM card via a data SMS, triggering the operator's SDK to execute step 3; S11, authentication failed, re-execute step 6; S12, return the uidx read from the SIM card to the operator SDK; S13, passing the uidx to the operator server through the operator sdk, and accessing the number acquisition request; S14, obtaining the mobile phone number, masked mobile phone number, and authentication code through the operator server, and generating a UID; S15, performing consistency comparison between the uid and uidx; if they are inconsistent, executing step S16, and if they are consistent, executing step S17; S16, if inconsistent, send a data SMS to the SIM card, request personal information to fill in the h5 page, and then continue to execute step S7; S17, when they are consistent, returning the masked mobile phone number and the authentication code to the operator SDK; S18, pull up the authorization page to the application APP through the operator SDK; S19, displaying the masked mobile phone number to the user through the authorization page; S20, based on the user's confirmation, returning the confirmation information to the operator's SDK; S21, passing the authentication code to the application APP through the operator SDK; S22, transmitting the authentication code to the APP server through the application APP; S23, initiating a replacement request to the operator server through the APP server; S24, returning the mobile phone number to the APP server through the operator server; S25, completing the login using the mobile phone number through the APP server; S26, entering the APP application through the user side.

2. The human-machine verification login method based on SIM card according to claim 1, characterized in that: The S1, according to the pre-recorded number login request initiated by the user side, marks the user and the mobile phone through the uid field.

3. The human-machine verification login method based on SIM card according to claim 1, characterized in that: The S6 also includes pre-downloading the card application in the SIM of the mobile device through the over-the-air card writing technology.

4. The human-machine verification login method based on SIM card according to claim 1, characterized in that: In S8, the user authentication interface includes an interface provided by a third party or an operator.

5. The human-machine verification login method based on SIM card according to claim 1, characterized in that: In S9, the mobile phone number includes an 11-digit mobile phone number, and the masked mobile phone number includes marking the last four digits of the 11-digit mobile phone number with *; the authentication code includes a set of fixed-length character strings, and establishes a key-value pair relationship with the mobile phone number.

6. The human-machine verification login method based on SIM card according to claim 1, characterized in that: In S10, the uid is written into the SIM card through the over-the-air card writing technology.

7. An electronic device, characterized in that: It comprises a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein when the one or more computer instructions are executed by the processor, the human-machine verification login method based on the SIM card as described in any one of claims 1 to 6 above is implemented.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, it is used to implement the SIM card-based human-machine verification login method as described in any one of claims 1 to 6.

Images