Natural person identity encryption real-name authentication method and system
By constructing a closed-loop encryption system consisting of a natural person, an encrypted terminal, and an authentication server, and collecting and encrypting identity keys and biometric features, the problem of sensitive information being transmitted nakedly and being counterfeited in existing technologies is solved, achieving a high-security and low-cost real-name authentication solution.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-25
- Publication Date
- 2026-04-14
AI Technical Summary
Existing real-name authentication technologies have risks of transmitting sensitive information without authorization, weak anti-counterfeiting capabilities, and are unable to build a closed-loop encryption system between individuals, terminals, and servers, leading to frequent security incidents, infringement on the privacy and property security of individuals, and failing to meet real-world needs.
A closed-loop encryption system is constructed, consisting of natural persons, encrypted terminals, and authentication servers. This system collects identity encryption keys and biometric templates created by natural persons themselves, and uses key fragmentation and isolated storage, along with national cryptographic algorithms for encrypted transmission. This ensures that identity recognition is unforgeable, identity authentication is uncounterable, and identity encryption is undeniable. Through encrypted communication between the encrypted terminal and the authentication server, a full lifecycle management system is built.
It achieves full lifecycle management of natural person identity, prevents leakage of sensitive information, has an anti-counterfeiting success rate of up to 99.99%, reduces compliance and protection costs, is suitable for real-name authentication scenarios in multiple fields, and complies with data security regulations.
Smart Images

Figure CN121864330A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of natural person identity and data security technology. Specifically, it relates to a method and system for encrypted real-name authentication of natural person identity, which is adapted to application scenarios that require real-name authentication of natural persons, such as government services, financial transactions, Internet of Things access, and network service registration identity authentication. It is compatible with various hardware carriers such as mobile APP, financial smart terminal, and Internet of Things terminal, and can be widely used in real-name authentication scenarios in multiple fields. Background Technology
[0002] As digital construction moves towards high-quality development, real-name authentication has become the core technical support for identity verification in the digital space and a key link in the personal information protection system. It has irreplaceable strategic value for protecting the legitimate rights and interests of natural persons, regulating industry market order, and safeguarding national data security.
[0003] Current mainstream real-name authentication technologies all have significant technical shortcomings. The main existing mainstream real-name authentication technologies include: ① ID card OCR + facial recognition verification (such as the common solution in government and financial apps), the core flaw of which is that ID card photos and facial images need to be transmitted to the server, which poses a risk of plaintext transmission; ② Third-party real-name authentication interfaces (such as operator interfaces), the core flaw of which is that sensitive identity data needs to be synchronized to the third-party platform, making the entire lifecycle uncontrollable; ③ Static password + SMS verification code verification, the core flaw of which is that static passwords are easy to leak, SMS verification codes are easy to be hijacked, and the ability to resist counterfeiting is weak. While the aforementioned existing technologies partially employ encryption or verification methods, they fail to construct a closed-loop encryption system encompassing "natural person—terminal—server," and do not achieve collaborative protection through "natural person encryption key + key fragmented isolated storage + TEE local secure computation + blockchain audit and evidence storage." Furthermore, they still require the collection or transmission of natural persons' original sensitive identity identifiers, leading to frequent security incidents, infringement upon natural persons' privacy and property security, and damage to the credibility of government departments and market entities. This is entirely contrary to the core principles of the "Personal Information Protection Law of the People's Republic of China" and the "Data Security Law of the People's Republic of China." Existing technologies are no longer suitable for real-world needs, and there is an urgent need to develop a new natural person identity encryption and real-name authentication scheme based on a closed-loop encryption architecture, adhering to the principle of minimum necessary collection, and enabling full lifecycle management of identity data. Summary of the Invention
[0004] To overcome the shortcomings of existing technologies, this invention is based on core cryptographic technologies, takes the identity of a natural person as the source of trust, strictly follows the principle of "minimum necessary collection", and only collects the identity encryption key and biometric template created by the natural person. It constructs a closed-loop encrypted full life cycle management system of "natural person - encrypted terminal - authentication server" to achieve six core security characteristics: identity recognition is unforgeable, identity authentication is uncounterable, identity encryption is undeniable, identity password resists attacks, identity information is traceable throughout the process, and audit evidence is objective and fair. This ensures that the identity and data of natural persons are strictly controlled and fully protected throughout the real-name authentication process.
[0005] This invention is a general-purpose real-name authentication system, employing a three-tier distributed architecture of "encrypted terminal—authentication server—application system." The core authentication logic relies on a closed-loop encryption system of "natural person—encrypted terminal—authentication server": the encrypted terminal only establishes an encrypted communication link with the authentication server and does not directly interact with the application system; after completing closed-loop authentication, the authentication server only synchronizes non-sensitive authentication results to the application system through a standardized interface. The system consists of two core components: the encrypted terminal and the authentication server, and is adaptable to various domain scenarios and types of hardware terminals.
[0006] 1. System Core Modules (1) Encrypted terminal The encrypted terminal possesses hardware and software collaborative security protection capabilities. As the core intermediate carrier in the closed loop of "natural person - encrypted terminal - authentication server", it has six built-in core functional modules, as follows: ① Information collection module: Collects identity encryption keys and biometric templates that natural persons set, create and manage themselves. During the first collection, a dynamic code encryption key is automatically generated. The entire collection process is encrypted locally on the terminal and the original collected data is not transmitted, ensuring that the natural person's original information is not leaked.
[0007] ② Local secure storage module: Built on the Trusted Execution Environment (TEE), it encrypts 60% of the identity encryption key fragments and 40% of the dynamic code encryption key fragments. It adopts isolated storage, supports mainstream TEE standards, and has anti-tampering and anti-illegal extraction capabilities. It complements the key fragments of the authentication server and supports closed-loop key management.
[0008] ③ Encryption Calculation Module: Performs ASCII code conversion, national cryptographic SM4 algorithm, SHA-256 hash algorithm operation and XOR operation to generate a session-unique dynamic identity password. The algorithm is compatible with mainstream terminal chips, and the encryption calculation time is ≤100ms. It supports the upgrading of national cryptographic algorithms and provides encryption support for closed-loop data transmission and verification.
[0009] ④ Interactive verification module: Provides an interactive interface adapted to the characteristics of the terminal, completes the verification of the natural person's identity encryption key input and biometric comparison, confirms the authenticity of the natural person's operation intention, and the biometric identification mode can be configured according to the security level of the scenario. It is the first verification checkpoint for the authenticity of the natural person's identity in the closed loop.
[0010] ⑤ Encrypted Communication Module: Establishes a dedicated encrypted communication link only with the authentication server, serving as a communication bridge in the closed loop of "natural person - encrypted terminal - authentication server". It receives encrypted dynamic codes and sends back encrypted dynamic identity passwords. Data transmission is encrypted using the national cryptographic SM4 algorithm and supports the HTTPS 1.2+TLS 1.3 standard to ensure data transmission security within the closed loop.
[0011] ⑥ Local Audit Module: Records all operations of natural persons, forming a traceable audit log. The log is stored locally after being digitally signed with SM2, and has the characteristics of being tamper-proof. It supports traceability verification and export, forming a closed-loop traceability system with the audit log of the authentication server.
[0012] (2) Authentication server The authentication server does not store any original sensitive information of natural persons. As the core verification and control carrier of the "natural person - encrypted terminal - authentication server" closed loop, it has six built-in core functional modules and can flexibly adjust the deployment method, as follows: ① Dynamic code generation module: Generates a one-time dynamic code based on the TOTP algorithm, which is then encrypted using the national cryptographic SM4 algorithm (CBC mode) and sent to the encrypted terminal. The SM4 algorithm IV is randomly generated using terminal hardware fingerprint + timestamp. The dynamic code parameters can be configured according to the scenario, providing dynamic verification basis for closed-loop identity verification.
[0013] ② Key Segmentation Management Module: It uses the national cryptographic SM4 algorithm to encrypt and store 40% identity encryption key segments and 60% dynamic code encryption key segments. It is responsible for key segment invocation, matching and dynamic updates, establishes a unique association between terminal identifier and key segment, and works with the key segments of encrypted terminals to realize closed-loop key lifecycle management of "natural person - encrypted terminal - authentication server".
[0014] ③ Verification and Confirmation Module: Decrypts the encrypted dynamic identity password returned by the encrypted terminal, restores the dynamic code and completes dual verification to realize the confirmation of natural person identity. The operation delay is ≤50ms and does not store intermediate operation data. It is the core verification checkpoint for the authenticity of natural person identity in the closed loop.
[0015] ④ Audit Log Module: Records the entire process of real-name authentication operation data (including natural person operation, terminal interaction, and server verification data). After the log is digitally signed by SM2, it is synchronously stored on the local server and the blockchain evidence storage node to provide support for judicial evidence storage and form a closed loop traceability with the terminal audit log.
[0016] ⑤ Anomaly Control Module: Monitors anomalies in the entire closed-loop authentication process of "natural person - encrypted terminal - authentication server", triggers a tiered anomaly handling mechanism, supports data continuation and cache clearing after communication interruption, ensures stable system operation, and maintains the integrity of the closed loop.
[0017] ⑥ Interface Adaptation Module: Provides standardized interfaces such as RESTful API and WebService API, only synchronizes non-sensitive authentication results, can be seamlessly integrated into multi-domain application systems, achieves plug-and-play functionality, does not participate in sensitive data interaction within the closed loop, and ensures closed-loop security isolation.
[0018] 2. Natural Person Identity Encryption Real-Name Authentication Method The method described in this invention is based on a closed-loop encryption architecture of "natural person - encrypted terminal - authentication server". It does not collect any identifiers that can directly identify the natural person. It includes five core steps from S10 to S50, with unified core logic and each step closely connected to form a complete authentication closed loop, as detailed below: (1) Information collection steps (S10) Individuals complete information collection through encrypted terminals, without collecting any identifiers that can directly identify the individual. The entire collection process is encrypted locally on the terminal, and the original collected data is not transmitted, laying the foundation for closed-loop authentication. The specific process is as follows: ① Identity encryption key acquisition, conversion and fragmented storage: Natural persons set an identity encryption key consisting of 3-26 unique Pinyin letters, and the terminal verifies the format; after the key is converted by ASCII code and encrypted with the national standard SM4 symmetric encryption, it is split into two fragments by the Shamir (2,2) threshold key fragmentation algorithm (both fragments must be obtained at the same time to recover the complete key), 60% of the fragments are encrypted locally and stored in the terminal TEE trusted execution environment, and 40% of the fragments are encrypted with the session key and uploaded to the authentication server; the 60% / 40% fragmentation ratio can balance the storage pressure of the terminal and the server, and at the same time avoid the risk of leakage caused by a single node storing the complete key.
[0019] ② Dynamic code encryption key generation and fragmented storage: Based on its unique hardware fingerprint, the terminal automatically generates a 128-bit dynamic code encryption key (generated only during the first acquisition or terminal reset). After being encrypted by the national cryptographic SM4 algorithm, it is split into two fragments by the Shamir (2,2) threshold key fragmentation algorithm. 60% of the fragments are uploaded to the authentication server with the terminal identifier, and 40% of the fragments are encrypted and stored in the terminal's independent partition, realizing closed-loop key fragmentation management.
[0020] ③ Biometric Template Collection and Storage: Natural persons collect biometric templates such as fingerprints (≥50 feature points) and faces (≥1080P) through the terminal. The templates are generated by irreversible feature extraction algorithms (fingerprints use minutiae feature extraction algorithm, and faces use deep learning feature encoding algorithm). After being encrypted by the national cryptographic SM4 algorithm, the templates are stored only in the local secure storage module of the terminal. The original biometric data is not transmitted, which further protects the privacy of natural persons.
[0021] (2) Initiate the authentication process (S20) As the starting point of the closed-loop authentication process of "natural person - encrypted terminal - authentication server", the specific process is as follows: ① Server side: When a natural person logs into the application system, they initiate a real-name authentication request. The application system only sends the request and the unique terminal identifier to the authentication server. The authentication server verifies the terminal identifier, matches the corresponding key fragment, generates a dynamic code based on the TOTP algorithm (with a validity period of 30 seconds), encrypts it using the national cryptographic SM4 algorithm (CBC mode), caches it, and sends it to the encrypted terminal. The SM4 algorithm IV is randomly generated using the terminal hardware fingerprint + timestamp. The dynamic code parameters can be configured according to the scenario.
[0022] ② Terminal side: After receiving the encrypted dynamic code, the encrypted terminal calls the local dynamic code encryption key to decrypt 40% of the fragments, and stores the plaintext dynamic code in the terminal's temporary secure buffer for subsequent dynamic identity password generation, thus completing the dynamic code transmission and decryption within the closed loop.
[0023] ③ Anomaly Protection: If an anomaly is detected (such as terminal identifier mismatch or timestamp deviation exceeding 5 minutes), authentication will be terminated immediately, the cache and intermediate calculation results will be cleared, an anomaly message will be returned, and a log will be recorded. If communication is interrupted, the terminal cached data will be retained for 5 minutes and will be automatically resumed after communication is restored to ensure the integrity of the closed loop.
[0024] (3) Identity verification step (S30) The application system jumps to the encrypted terminal, which is the core verification link for the authenticity of the natural person's identity in the closed loop of "natural person - encrypted terminal - authentication server". The natural person completes the identity encryption key comparison and biometric comparison: the identity encryption key is converted into ASCII code and compared with 60% of the key fragments on the terminal, with a comparison threshold of ≥99.9%; the biometric features are accurately compared with the local encrypted template on the terminal, and the comparison mode can be configured according to the security level of the scenario.
[0025] If an individual fails to verify 3-5 times consecutively, the encrypted terminal will automatically lock for a preset time, record the failure log, and report it to the server. Manual unlocking requires submission of a unique terminal identifier and an identity encryption key fragment for dual verification. After successful verification, the user will proceed to the dynamic identity password generation step.
[0026] (4) Dynamic identity password generation steps (S40) As the core credential generation step in the closed loop of "natural person - encrypted terminal - authentication server," the encrypted terminal calls a 60% fragment of its local identity encryption key (decimal data converted from ASCII code) and a cached plaintext dynamic code (decimal data). After padding with zeros to align the dynamic code length, it performs an XOR operation bit by bit. Then, it performs a SHA-256 hash operation on the result, extracting bits 16-32 from the 8th bit of the hash value to form a dynamic identity password (32 bits for high-security scenarios, 16 bits for low-security scenarios). The dynamic identity password is encrypted using the national cryptographic SM4 algorithm and transmitted back to the authentication server via an HTTPS 1.2+TLS 1.3 standard encrypted communication link, with the terminal simultaneously recording audit logs.
[0027] (5) Real-name authentication and closed-loop verification steps (S50) As the final step in the closed-loop authentication process of "natural person - encrypted terminal - authentication server", it completes the confirmation of natural person identity and closed-loop cleanup. The specific process is as follows: ① Server-side dual decryption: After receiving the encrypted dynamic identity password, the authentication server calls the session key to decrypt and obtain the hash digest password. Then, it calls the 40% fragment of the identity encryption key stored on the server to decrypt and restore the intermediate result of the XOR operation and the hash operation parameters.
[0028] ② Two-way comparison and verification: The authentication server decrypts its own cached encrypted dynamic code, restores the plaintext dynamic code, combines it with the identity encryption key in 40% fragmentation, and generates a hash digest for verification by reverse deduction using the same algorithm on the terminal side. This hash digest is then accurately compared with the decrypted hash digest state password to realize the confirmation of the natural person's identity.
[0029] ③ Result Processing and Auditing: If the comparison is consistent, real-name authentication and identity confirmation are completed, audit logs are recorded and uploaded to the blockchain evidence storage node, and non-sensitive authentication results are synchronized to the application system through a standardized interface; if the comparison is inconsistent, an authentication failure message is returned, an exception log is recorded and the result is synchronized; after the audit log is digitally signed by SM2, it is stored locally on the terminal, synchronously on the server, and on the blockchain evidence storage node, possessing the characteristics of being tamper-proof and traceable.
[0030] ④ Session cleanup: After authentication is completed, the server and terminal synchronously clear all cached data, intermediate calculation results and key call records, leaving only audit logs to ensure the independence and security of each authentication session in the closed loop of "natural person - encrypted terminal - authentication server".
[0031] ⑤ Authorization of permissions: After receiving the authentication result, the application system grants the corresponding operation permissions to the natural persons who pass the authentication and refuses to grant permissions to the natural persons who fail the authentication.
[0032] 3. The beneficial effects of this invention: ① This invention constructs a closed-loop encryption system encompassing "natural person—encrypted terminal—authentication server," achieving a technological leap from "passive verification" to "active authorization," thus overcoming the shortcomings of existing technologies in closed-loop management of identity data and hierarchical isolation of sensitive information. Compared to existing technologies, this invention does not collect any directly identifiable identifiers of natural persons. Through closed-loop key fragmentation management and local encrypted computation, it fundamentally prevents the leakage of sensitive information, effectively solving the pain point of the inability to verify the authenticity of the natural person operating entity in existing technologies.
[0033] ② Strengthen privacy protection and data security, follow the principle of "minimum necessary collection", adopt key fragmentation and isolated storage, and national cryptographic algorithm encryption transmission, with an anti-counterfeiting success rate of ≥99.99%, completely eliminating the risk of sensitive information leakage; biometric features are extracted using irreversible templates, so even if the template is leaked, the original biometric features cannot be restored, further protecting the privacy and security of natural persons.
[0034] ③ Construct an endogenous proactive defense system that blocks common network attacks through triple authentication, dynamic password generation, two-way comparison, and anomaly control, without the need for additional protection equipment, thus reducing security protection costs. Existing real-name authentication solutions require additional deployment of firewalls, intrusion detection systems (IDS), data desensitization equipment, etc., with a single-node deployment cost of approximately 50,000 to 100,000 yuan. This invention only relies on the native security modules of the encrypted terminal and authentication server, reducing the single-node deployment cost by 42% (data from Example 1), significantly reducing enterprise compliance and protection costs.
[0035] ④ Enhance non-repudiation and auditability. Audit logs are digitally signed and synchronized to the blockchain, ensuring that logs are tamper-proof and operations are traceable. This meets the high compliance requirements of finance, government affairs, and other sectors, and provides strong support for judicial evidence preservation.
[0036] ⑤ The architecture is lightweight and ecosystem-friendly, and can be seamlessly integrated into application systems in multiple fields and various types of terminals, significantly reducing enterprise deployment and compliance costs and improving industry applicability; relying on the closed-loop architecture of "natural person - encrypted terminal - authentication server", it is adaptable to different terminal forms and scenario requirements, and has strong versatility.
[0037] ⑥ Achieve closed-loop, full lifecycle management of identity data, fill existing technological gaps, ensure end-to-end authentication security, comply with the core principles of the "Personal Information Protection Law of the People's Republic of China" and the "Data Security Law of the People's Republic of China," and adapt to the needs of high-quality digital development. Attached Figure Description
[0038] The accompanying drawings are used to clearly illustrate the technical solution of the present invention and do not constitute a limitation on the scope of protection of the present invention; Figure 1The schematic diagram of the system of this invention shows a three-level distributed architecture of "encrypted terminal - authentication server - application system", which clarifies the dedicated encrypted communication link between the encrypted terminal and the authentication server, as well as the interface interaction logic between the authentication server and the application system, and reflects the core of the closed loop of "natural person - encrypted terminal - authentication server". Figure 2 The flowchart of the method of this invention shows the five core steps S10-S50 and the connection relationship of each step in the closed loop of "natural person - encrypted terminal - authentication server". Figure 3 This invention presents a schematic diagram of a closed-loop encrypted state management process, illustrating the entire process of identity data from collection, encrypted storage, encrypted transmission to verification and destruction, as well as the security protection logic for each stage. Figure 4 The diagram illustrating the six security features of this invention demonstrates the interrelationships between these six features: unforgeable, uncounterable, non-repudiable, attack-resistant, traceable, and audit-fair, as well as their role in ensuring the security of the closed loop of "natural person - encrypted terminal - authentication server". Detailed Implementation The following is in conjunction with the appendix Figure 1-4 The present invention will be further illustrated through specific embodiments. These embodiments are for illustrative purposes only and do not limit the scope of protection. Specific parameters and terminal forms in the embodiments can be adjusted according to actual needs. All embodiments of the present invention are implemented based on a closed-loop encryption architecture of "natural person - encrypted terminal - authentication server," with the core steps and logic remaining consistent, and only details adjusted according to scenario characteristics.
[0039] 1. Example 1: Deployment of mobile APP terminal + cloud server cluster (high concurrency scenarios in government / finance) The encrypted terminal uses a mobile app compatible with both iOS and Android platforms, serving as the terminal carrier in the closed loop of "natural person - encrypted terminal - authentication server". The authentication server uses a cloud server cluster with 3 redundant nodes, following the core steps of S10-S50, as follows: ① System Deployment: The encrypted terminal (mobile APP) is compatible with iOS 14.0 and above, and Android 10.0 and above. The six modules are adapted to the characteristics of mobile terminals (the local secure storage module is adapted to the mobile terminal TEE environment, and the encrypted communication module is adapted to the mobile network), making it convenient for natural persons to operate anytime and anywhere; the authentication server supports elastic expansion, with an interface concurrent processing capacity of ≥10000QPS. The six modules are adapted to the characteristics of cloud deployment (the key sharding management module supports distributed storage, and the verification and authorization module supports high-concurrency operation), supporting closed-loop authentication in high-concurrency scenarios.
[0040] ② Practical Procedure: S10, the individual downloads the APP and completes the collection of identity encryption key and biometric features (face / fingerprint). The dynamic code encryption key is automatically generated and stored in segments; S20, the individual logs into the government / financial APP to initiate authentication. The server generates an encrypted dynamic code and sends it to the mobile APP; S30, the individual completes dual verification of key and biometric features through the APP; S40, the APP generates an encrypted dynamic identity password and sends it back to the authentication server; S50, the server completes dual decryption and two-way comparison, synchronizes the authentication result to the government / financial APP, and completes session cleanup.
[0041] This embodiment achieves a 99.992% success rate against counterfeiting, with encryption computation taking only 85ms. It reduces compliance operation costs by 42% compared to existing technologies, making it suitable for high-concurrency scenarios such as government and finance. It fully demonstrates the efficiency and security of the closed loop of "natural person - encrypted terminal - authentication server".
[0042] 2. Example 2: Deployment of Financial Smart Terminal + Standalone Server (Offline Financial Scenarios) The encrypted terminal uses a financial smart terminal, and the authentication server is deployed on a single machine. The core process is consistent with Implementation Example 1, while the practical details are adapted to offline characteristics, conforming to the closed-loop logic of "natural person - encrypted terminal - authentication server": S10, the natural person inputs the identity encryption key through the terminal button, and the dedicated fingerprint collection module collects biometric features; S20, the teller assists the natural person in initiating authentication, and the server generates an 8-digit encrypted dynamic code and displays it on the terminal; S30, the natural person completes verification through the button and fingerprint; the remaining steps are consistent with Implementation Example 1. This implementation example is adapted to the high security and low concurrency requirements of offline scenarios, with a verification efficiency of ≤150ms, ensuring the security and convenience of natural person identity authentication in offline scenarios.
[0043] 3. Example 3: Deployment of IoT Terminals + Lightweight Servers (IoT Scenario) The encrypted terminal uses an IoT terminal, and the authentication server is deployed as a lightweight single machine. The core process is consistent with Example 1, but the practical details are adapted to the characteristics of IoT, following a closed-loop logic of "natural person - encrypted terminal - authentication server": S10, the terminal's preset identity encryption key can be modified by the natural person, and simple biometric features (such as fingerprints) are collected; S20, the terminal triggers an authentication request, and the server generates and sends an encrypted dynamic code; S30, the natural person completes single biometric verification (preferably using simple fingerprint verification, adapted to the hardware characteristics of IoT terminals); the remaining steps are consistent with Example 1. The encryption calculation time in this example is ≤100ms, adapting to the low-performance and high-security requirements of IoT, and realizing secure authentication of natural person identities in IoT scenarios.
[0044] The above embodiments fully demonstrate that the technical solution of the present invention possesses good versatility, scalability, and feasibility. Based on a closed-loop encryption architecture of "natural person—encrypted terminal—authentication server," it can be widely applied to various real-name authentication scenarios such as government affairs, finance, and the Internet of Things, adapting to different terminal forms and business needs. Simultaneously, it can reduce the compliance operation cost of a single node by 42%, and achieve an anti-counterfeiting success rate of over 99.99%, possessing clear and significant industrial application value. The above embodiments are merely for clearly illustrating the technical solution of the present invention and are not intended to limit the scope of protection; any equivalent substitutions or modifications based on the concept of the present invention should be covered within the scope of the claims of the present invention.
Claims
1. A method for encrypted real-name authentication of natural person identity, characterized in that, Implemented based on a closed-loop encryption architecture of "natural person - encrypted terminal - authentication server", without collecting any identifiers that can directly identify the natural person, including the following steps: S10. Information Collection: Natural persons complete the collection of identity encryption keys, generation of dynamic code encryption keys, and collection of biometric templates through encrypted terminals. The entire collection process is encrypted locally on the terminal and the original collected data is not transmitted. The identity encryption key and dynamic code encryption key are fragmented and stored in the encrypted terminal and the authentication server according to a preset ratio. The biometric template is only encrypted and stored locally on the encrypted terminal. S20. Initiate authentication: A natural person initiates a real-name authentication request through the application system. The application system sends the request and the unique identifier of the terminal to the authentication server. After verifying the terminal identifier, the authentication server generates an encrypted dynamic code and sends it to the encrypted terminal. The encrypted terminal decrypts the code and caches the plaintext dynamic code. S30. Identity Authentication: The application system jumps to the encrypted terminal, where the natural person completes the identity encryption key comparison and biometric comparison. If the dual comparison is successful, the next step is initiated. If the comparison fails, the authentication is terminated and a log is recorded. S40. Dynamic identity password generation: The encrypted terminal calls the locally stored identity encryption key fragment and the cached plaintext dynamic code, performs encryption operations to generate an encrypted dynamic identity password, and sends it back to the authentication server. S50, Closed-loop verification and result synchronization: The authentication server calls its own stored key fragments to decrypt the encrypted dynamic identity password and complete a two-way comparison. If the comparison matches, the non-sensitive authentication result is synchronized to the application system; if the comparison does not match, a failure message is returned. After authentication, the server and terminal synchronously clear the cache and intermediate data of the operation and retain an unalterable audit log.
2. The method according to claim 1, characterized in that, In step S10, the identity encryption key collection and fragmented storage specifically involves: the natural person sets an identity encryption key consisting of 3-26 unique Pinyin letters. After the terminal verifies the format, the key is converted to ASCII code, encrypted using the national standard SM4 symmetric encryption, and split into two fragments using the Shamir (2,2) threshold key fragmentation algorithm. 60% of the fragments are encrypted locally and stored in the terminal's TEE trusted execution environment, while the remaining 40% are encrypted using the session key and uploaded to the authentication server. The dynamic code encryption key generation and fragmented storage specifically involves: the terminal automatically generates a 128-bit dynamic code encryption key based on its unique hardware fingerprint. After encryption using the national standard SM4 algorithm, the key is split into two fragments using the Shamir (2,2) threshold key fragmentation algorithm. 60% of the fragments, carrying the terminal identifier, are uploaded to the authentication server, while the remaining 40% are encrypted and stored in a separate partition on the terminal. The dynamic code encryption key is only generated during the initial collection or when the terminal is reset.
3. The method according to claim 1, characterized in that, In step S10, the biometric template collection and storage specifically involves: collecting at least one biometric feature from natural persons, such as fingerprints (≥50 feature points) and faces (≥1080P), generating a feature template through an irreversible feature extraction algorithm, encrypting it using the national cryptographic SM4 algorithm, and storing it only in the terminal's local secure storage module without transmitting the original biometric data.
4. The method according to claim 1, characterized in that, In step S20, the dynamic code is generated based on the TOTP algorithm, encrypted using the national cryptographic SM4 algorithm (CBC mode), and then distributed. The SM4 algorithm IV is randomly generated using terminal hardware fingerprint + timestamp, and the validity period of the dynamic code is set to 30 seconds. The parameters can be configured according to the security level of the scenario. In step S40, the encryption operation is specifically as follows: the identity encryption key fragment (decimal data converted from ASCII code) and the plaintext dynamic code (decimal data) are aligned by padding with zeros according to the length of the dynamic code. The zero-padding decimal data is XORed bit by bit, and the result is subjected to SHA-256 hash operation. Starting from the 8th bit of the hash value, bits 16-32 are truncated to form the dynamic identity password. In high-security scenarios, 32 bits are truncated, and in low-security scenarios, 16 bits are truncated.
5. The method according to claim 1, characterized in that, In step S30, the identity encryption key comparison threshold is ≥99.9%; the biometric comparison mode can be configured according to the security level of the scenario. If a natural person fails to verify 3-5 times consecutively, the encryption terminal will automatically lock for a preset time, record the failure log and report it to the authentication server.
6. The method according to claim 1, characterized in that, In steps S20 and S50, the encrypted communication uses the national cryptographic algorithm SM4 and supports the HTTPS 1.2+TLS 1.3 standard; the audit log, after being digitally signed with SM2, is stored locally on the terminal, synchronously on the server, and on the blockchain evidence storage node, possessing the characteristics of being tamper-proof and traceable; the entire authentication process is monitored for abnormal scenarios and a graded processing mechanism is triggered; the abnormal scenarios include terminal identifier mismatch, dynamic code expiration, communication link tampering, and timestamp deviation exceeding 5 minutes; The tiered handling mechanism executes at least one of the following processing methods based on the anomaly level: logging, terminal locking, and anomaly reporting.
7. The method according to any one of claims 1-6, characterized in that, The encrypted terminal is compatible with at least one of mobile apps, financial smart terminals, and IoT terminals; the authentication server supports multiple deployment modes, including cloud server clusters, standalone machines, and lightweight standalone machines, and can be seamlessly integrated into multi-domain application systems through standardized interfaces.
8. A system for implementing the natural person identity encryption real-name authentication method according to any one of claims 1-7, characterized in that, Built on a closed-loop encryption architecture of "natural person - encrypted terminal - authentication server", it adopts a three-level distributed architecture of "encrypted terminal - authentication server - application system", including two core parts: encrypted terminal and authentication server. The application system does not participate in the interaction of sensitive data within the closed loop, but only receives non-sensitive authentication results.
9. The system according to claim 8, characterized in that, The encrypted terminal, as the core carrier in the closed loop, has built-in information collection module, local secure storage module, encrypted computing module, interactive verification module, encrypted communication module, and local auditing module. It has the ability to provide security protection through software and hardware collaboration and establishes an encrypted communication link only with the authentication server.
10. The system according to claim 8, characterized in that, The authentication server, serving as the core verification and control carrier in a closed loop, incorporates a dynamic code generation module, a key sharding management module, a verification and authorization module, an audit log module, an anomaly control module, and an interface adaptation module. It does not store any original sensitive information of natural persons and its deployment method can be flexibly adjusted. The encrypted terminal works in conjunction with the authentication server to achieve key sharding management, encrypted communication, closed-loop verification, and audit traceability, ensuring the secure control of natural persons' identities and data throughout the entire real-name authentication process.