A human-machine verification login method based on SIM card
The SIM card-based human-machine verification login method solves the problems of memory burden and insufficient security in the existing login method. Through UID field verification and identity authentication, user information security is ensured, information leakage is prevented, and the convenience and security of login are improved.
Patent Information
- Application Number
- CN202411504338.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-25
- Publication Date
- 2025-09-16
- Estimated Expiration
- 2044-10-25
AI Technical Summary
The existing login method has problems such as memory burden, information leakage and insufficient security of one-click login, especially when obtaining user information through one-click login after the mobile phone is lost.
Through the SIM card-based human-machine verification login method, including UID field verification, data SMS interaction, identity authentication and authorization code generation, the consistency and security of user identity information are ensured.
It has realized the addition of identity information consistency judgment on the basis of traditional one-click login, effectively preventing information leakage caused by inconsistency between machine and card, and improving login security and convenience.
Smart Images

Figure CN119232479B_ABST
Abstract
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 widespread use of the internet, user security authentication in various applications has become a major concern. Numerous login methods have emerged, including account-password login, dynamic verification codes, biometrics, and one-click login. However, each method presents its own challenges. Account-password login places an increased burden on users to remember passwords, impacting the login experience. Dynamic verification codes can cause login anomalies due to network latency or unauthorized access. Biometrics can leak user biometric information and take too long to log in. One-click login eliminates human-machine verification and allows anyone with a SIM card to log in and access 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, by taking out the mobile phone card A and putting it 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] Aiming at 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 aims to provide a SIM card-based human-machine verification login method, electronic device and storage medium to address 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 SIM card-based human-machine verification login method is provided, 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 the 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, initiate a number request, obtain the mobile phone number, masked mobile phone number, authentication code, and generate a UID;
[0016] S10, write the uid into the SIM card via a data SMS, triggering the operator SDK to execute step 3;
[0017] S11, authentication fails, re-execute step 6;
[0018] S12, returns 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 based on the uid and uidx; if they are inconsistent, executing step S16, and if they are consistent, executing step S17;
[0022] S16, if there is any inconsistency, a data SMS is sent to the SIM card, requesting personal information to be filled in page h5, and then proceeding to step S7;
[0023] S17, if they are consistent, return 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 user confirmation, returning confirmation information to the operator SDK;
[0027] S21, delivering 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 via the APP server using the mobile phone number;
[0032] S26, enter the APP application through the user side.
[0033] In some implementations, S1 labels the user and mobile phone through the uid field based on the pre-recorded number login request initiated by the user side.
[0034] In some implementations, the S6 further includes pre-downloading the card application to 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 character 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 using 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 to 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 determining whether the one-key login is used for the first time and triggering the identity information filling, and at the same time triggering the person-card consistency verification through the identity information. If the verification passes, the UID information generation and card writing operation are triggered; the operator server provides data interaction and service call capabilities to the SDK, and also provides the specific underlying 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 The present invention is a flowchart of a human-machine verification login method based on a SIM card. DETAILED DESCRIPTION
[0043] It should be noted that, in the absence of conflict, the embodiments and features of the embodiments in this 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] Example 1:
[0045] Figure 1 A flow chart showing a method for logging in by verifying the human-machine interface based on a SIM card is shown. Figure 1 As shown, the SIM card-based human-machine verification login method 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 the 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, initiate a number request, obtain the mobile phone number, masked mobile phone number, authentication code, and generate a UID;
[0055] S10, write the uid into the SIM card via a data SMS, triggering the operator SDK to execute step 3;
[0056] S11, authentication fails, re-execute step 6;
[0057] S12, returns 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 based on the uid and uidx; if they are inconsistent, executing step S16, and if they are consistent, executing step S17;
[0061] S16, if there is any inconsistency, a data SMS is sent to the SIM card, requesting personal information to be filled in page h5, and then proceeding to step S7;
[0062] S17, if they are consistent, return 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 user confirmation, returning confirmation information to the operator SDK;
[0066] S21, delivering 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 via the APP server using the mobile phone number;
[0071] S26, enter the APP application through the user side.
[0072] Furthermore, the S1 marks the user and mobile phone through the uid field according to the pre-recorded number login request initiated by the user side.
[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: if the user identity information is name, ID number and IMSI, then the user information and cellular network account verification information will be used to check whether they are 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] The carrier's server sends a data SMS to the SIM card, which starts the h5 page where you can fill in your personal information. This process requires pre-downloading the relevant card application on the SIM card, which is implemented using 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 regular 11-digit mobile phone number (e.g., 138 3534 2345); a masked mobile phone number is a number where the last four digits of the mobile phone number are marked with an *, primarily to indicate which mobile phone number is being obtained and ensure that the user knows which account to log in to (e.g., 1383534****); and an authentication code is a fixed-length string that establishes a key-value pair relationship, i.e., authentication code-mobile phone number and masked mobile phone number (key-value), with no mandatory length restriction. Furthermore, in S10, the UID is written to the SIM card using over-the-air card writing technology.
[0079] Writing and reading data to and from a SIM card typically involves Over-The-Air (OTA), a technology that allows SIM card data to be updated wirelessly. With traditional SIM cards, this isn't something users can do on their own, as it requires the carrier's network and specialized equipment. However, with eSIM (embedded SIM), users can download carrier profiles and activate services through remote provisioning without a physical SIM card.
[0080] Example 2:
[0081] This embodiment further provides an electronic device, comprising a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, use 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 Example 1.
[0084] Example 3:
[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 embodiment 1 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, magnetic disk or optical disk.
[0087] The method implemented in this embodiment is as shown in Example 1.
[0088] 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 art to which this application belongs.
[0089] It should be noted that the terms used herein are intended only to describe 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 intended to include the plural form. In addition, it should 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.
[0090] It should be noted that the terms "first," "second," and the like in the specification and claims of this application and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, such that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.
[0091] In addition, the terms "comprises" and "comprising" and any variations thereof are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, product, or apparatus.
[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 of a device or feature to other devices or features as shown in the figures. 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 figures. For example, if the device in the drawings is inverted, the device described as "above other devices or structures" or "above other devices or structures" will be subsequently positioned as "below other devices or structures" or "below other devices or structures". Thus, the exemplary term "above" can include both "above" and "below". The device can 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 hereof. In the drawings, similar symbols typically identify similar components, unless the context dictates 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 foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be within the scope of protection of the present invention.
Claims
1. A SIM card-based human-machine verification login method, 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 user's SIM card 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 the 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 SIM card through the operator server and requesting an h5 link; S7, accessing the h5 link through the card application of the SIM card, entering 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, initiate a number request, obtain the mobile phone number, masked mobile phone number, authentication code, and generate a UID; S10, write the uid into the SIM card via a data SMS, triggering the operator SDK to execute step 3; S11, authentication fails, re-execute step 6; S12, returns 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 based on the uid and uidx; if they are inconsistent, executing step S16, and if they are consistent, executing step S17; S16, if there is any inconsistency, a data SMS is sent to the SIM card, requesting personal information to be filled in page h5, and then proceeding to step S7; S17, if they are consistent, return 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 user confirmation, returning confirmation information to the operator SDK; S21, delivering 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 via the APP server using the mobile phone number; S26, entering the application APP through the user side.
2. The human-machine verification login method based on SIM card according to claim 1, characterized in that: Said S1, based on 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 on the SIM card through the over-the-air card writing technology.
4. The SIM card-based human-machine verification login method 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 is implemented as described in any one of claims 1 to 6.
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 human-machine verification and login method based on the SIM card as described in any one of claims 1 to 6.
Citation Information
Patent Citations
Security authentication method and device and storage medium
CN117579245A
Identity authentication method and device, equipment and storage medium
CN118138328A