A method and apparatus for accessing privacy data based on a WeChat mini-program

Abstract

The application provides a kind of private data calling method and device based on applet, user identity information is collected and encrypted, and is packaged into unsigned digital pass; Front-end SDK checks whether there is corresponding private key, if there is user, input information to be verified and is verified by preset mode;After verification, front-end SDK and back-end SDK are signed to form signed digital pass;The whole encrypted digital pass after signing is encrypted;Data request carrying encrypted digital pass is sent to digital pass management system to obtain returned private data.In this scheme, under the premise of reasonable, legal and user authorization, the user's private data is called to the applet, more personalized content and services are pushed to the user, the user experience is improved, in addition, the security and privacy of private data in the calling process are ensured by using data encryption related technology, and the purpose of balancing user experience and data privacy protection is finally realized.

Description

Technical Field

[0001] This invention relates to the field of data encryption technology, specifically to a method and apparatus for accessing private data based on a mini-program. Background Technology

[0002] With the rapid development of the mobile internet, mini-programs, as lightweight applications, have become an indispensable part of users' daily lives due to their characteristics of requiring no installation and being usable instantly. However, while providing convenient services, mini-programs also involve the processing and sharing of a large amount of users' private data.

[0003] In existing technologies, due to privacy protection measures to prevent privacy leaks, even when a user-authorized mini-program needs access to their private data, it is unable to provide certain services, thus affecting the user experience.

[0004] Therefore, how to balance user experience and data privacy protection has become an urgent problem to be solved. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a method and apparatus for accessing privacy data based on mini-programs, so as to achieve a balance between user experience and data privacy protection.

[0006] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0007] The first aspect of this invention discloses a method for retrieving privacy data based on a mini-program, applied to a data user, the method comprising:

[0008] In response to user authorization via the mini-program, the user's identity information is collected;

[0009] The identity information is encrypted using the SM2 public key issued by the digital pass management system, and the encrypted identity information is then encapsulated to obtain an unsigned digital pass.

[0010] Call the front-end SDK of the mini-program to query whether there is a first private key corresponding to the encrypted identity information;

[0011] If so, the front-end SDK of the mini-program is called to obtain the verification information input by the user, and the verification information is verified based on the pre-set verification method. When the verification information passes the verification, the front-end SDK of the mini-program performs a collaborative signature on the unsigned digital pass based on the first private key and the second private key obtained from the back-end SDK of the mini-program based on the encrypted identity information, to obtain a signed digital pass; the complete private key composed of the first private key and the second private key corresponds to the public key pre-registered in the digital signature support system.

[0012] Using the SM4 symmetric key issued by the digital pass management system, the signed digital pass is encrypted as a whole to obtain an encrypted digital pass;

[0013] The system sends a data request carrying the encrypted digital pass to the digital pass management system and receives privacy data returned by the digital pass management system based on the data request. The privacy data is used by the digital pass management system to verify the encrypted digital pass. Once the verification is successful, the system forwards the data request to the data provider, and the data provider returns the data to the digital pass management system based on the data request.

[0014] Preferably, the unsigned digital pass obtained by encapsulating and encrypting the identity information includes:

[0015] The encrypted identity information is encapsulated into an unsigned digital pass in JSON format.

[0016] Preferably, if a first private key corresponding to the encrypted identity information does not exist, the method further includes:

[0017] If the time elapsed since the last verification of a user's identity was more than the preset validity period, then a verification of the user's identity will be initiated and the verification result obtained.

[0018] When the verification result is passed, the digital certificate in the backend SDK of the mini program is called to sign the verification result, and the signed verification result is obtained.

[0019] If the time since the last verification of the user's identity was passed is within the preset validity period, or if the verification result is valid after calling the front-end SDK of the mini-program to verify the signature, then the front-end SDK of the mini-program sends the public key corresponding to the encrypted identity information to the digital signature support system, so that the digital signature support system allocates the first private key corresponding to the encrypted identity information to the front-end SDK of the mini-program, and allocates the second private key corresponding to the encrypted identity information to the back-end SDK of the mini-program;

[0020] In response to the user's settings, a verification method is set; the verification method is used to verify the information to be verified by the user, so as to collaboratively sign the unsigned digital pass when the verification is successful.

[0021] The front-end SDK of the mini-program performs collaborative signing on the unsigned digital pass based on the first private key and the second private key obtained from the back-end SDK of the mini-program based on the encrypted identity information, to obtain a signed digital pass, and writes the verification result of the signature into the signed digital pass.

[0022] Preferably, the method further includes:

[0023] If the verification of the information to be verified fails based on the pre-set verification method, then return to the step of obtaining the user-input information to be verified and verifying the information to be verified based on the pre-set verification method, and record the number of times the process is returned;

[0024] When the number of returns exceeds the threshold, a real-person verification for the user is initiated to obtain the verification result.

[0025] When the verification result is passed, the digital certificate in the backend SDK of the mini program is called to sign the verification result, and the signed verification result is obtained.

[0026] If the front-end SDK of the mini-program verifies the signature and the verification result is valid, then based on the first private key and the second private key obtained from the back-end SDK of the mini-program based on the encrypted identity information, the unsigned digital pass is collaboratively signed to obtain a signed digital pass.

[0027] Preferably, after sending a data request carrying the encrypted digital pass to the digital pass management system, the digital pass management system performs a signature verification operation on the encrypted digital pass, and stores it locally after successful verification. The method further includes:

[0028] In response to a user's search command for a target encrypted digital pass, a search request is generated; the target encrypted digital pass includes the encrypted digital pass used when accessing the privacy data;

[0029] The retrieval request is sent to the digital pass management system, and the target encrypted digital pass is received from the digital pass management system.

[0030] A second aspect of this invention discloses a privacy data retrieval device based on a mini-program, applied to a data user, the device comprising:

[0031] The authorization unit is used to collect the user's identity information in response to the user's authorization operation through the mini-program;

[0032] The encapsulation unit is used to encrypt the identity information using the SM2 public key issued by the digital pass management system, and encapsulate the encrypted identity information to obtain an unsigned digital pass.

[0033] The query unit is used to call the front-end SDK of the mini-program to query whether the first private key corresponding to the encrypted identity information exists;

[0034] The first collaborative signature unit is used to, if a first private key corresponding to the encrypted identity information exists, call the front-end SDK of the mini-program to obtain the verification information input by the user, and verify the verification information based on a pre-set verification method. When the verification information passes the verification, the front-end SDK of the mini-program performs collaborative signing on the unsigned digital pass based on the first private key and a second private key obtained from the back-end SDK of the mini-program based on the encrypted identity information to obtain a signed digital pass. The complete private key composed of the first private key and the second private key corresponds to the public key pre-registered in the digital signature support system.

[0035] The overall encryption unit is used to encrypt the signed digital pass using the SM4 symmetric key issued by the digital pass management system to obtain an encrypted digital pass.

[0036] The calling unit is used to send a data request carrying the encrypted digital pass to the digital pass management system, and to receive privacy data returned by the digital pass management system based on the data request; the privacy data is used by the digital pass management system to verify the encrypted digital pass, and when the verification is successful, the data request is forwarded to the data provider, and the data provider returns the data to the digital pass management system based on the data request.

[0037] Preferably, the encapsulation unit for encapsulating the encrypted identity information to obtain the unsigned digital pass is specifically used for:

[0038] The encrypted identity information is encapsulated into an unsigned digital pass in JSON format.

[0039] Preferably, the device further includes:

[0040] The key registration and signing unit is used to initiate a verification of the user's identity information if there is no first private key corresponding to the encrypted identity information and the time between the last verification result of the user's real person verification and the current time exceeds a preset validity period.

[0041] When the verification result is passed, the digital certificate in the backend SDK of the mini program is called to sign the verification result, and the signed verification result is obtained.

[0042] If the time since the last verification of the user's identity was passed is within the preset validity period, or if the verification result is valid after calling the front-end SDK of the mini-program to verify the signature, then the front-end SDK of the mini-program sends the public key corresponding to the encrypted identity information to the digital signature support system, so that the digital signature support system allocates the first private key corresponding to the encrypted identity information to the front-end SDK of the mini-program, and allocates the second private key corresponding to the encrypted identity information to the back-end SDK of the mini-program;

[0043] In response to the user's settings, a verification method is set; the verification method is used to verify the information to be verified by the user, so as to collaboratively sign the unsigned digital pass when the verification is successful.

[0044] The front-end SDK of the mini-program performs collaborative signing on the unsigned digital pass based on the first private key and the second private key obtained from the back-end SDK of the mini-program based on the encrypted identity information, to obtain a signed digital pass, and writes the verification result of the signature into the signed digital pass.

[0045] Preferably, the method further includes:

[0046] The second collaborative signature unit is used to return to the step of obtaining the user-inputted information to be verified and verifying the information to be verified based on the pre-set verification method if the verification of the information to be verified fails based on the pre-set verification method, and to record the number of times the verification is returned.

[0047] When the number of returns exceeds the threshold, a real-person verification for the user is initiated to obtain the verification result.

[0048] When the verification result is passed, the digital certificate in the backend SDK of the mini program is called to sign the verification result, and the signed verification result is obtained.

[0049] If the front-end SDK of the mini-program verifies the signature and the verification result is valid, then based on the first private key and the second private key obtained from the back-end SDK of the mini-program based on the encrypted identity information, the unsigned digital pass is collaboratively signed to obtain a signed digital pass.

[0050] Preferably, after sending a data request carrying the encrypted digital pass to the digital pass management system, the digital pass management system performs a signature verification operation on the encrypted digital pass, and stores it locally after successful verification. The device further includes:

[0051] A retrieval unit is used to generate a retrieval request in response to a user's retrieval instruction for a target encrypted digital pass; the target encrypted digital pass includes the encrypted digital pass used when accessing the privacy data;

[0052] The retrieval request is sent to the digital pass management system, and the target encrypted digital pass is received from the digital pass management system.

[0053] Based on the above embodiments of the present invention, a method and apparatus for retrieving privacy data based on a mini-program is provided. In response to a user's authorization operation through a mini-program, the method collects the user's identity information; encrypts the identity information using an SM2 public key issued by a digital pass management system, and encapsulates the encrypted identity information to obtain an unsigned digital pass; it calls the mini-program's front-end SDK to query whether a first private key corresponding to the encrypted identity information exists; if so, it calls the mini-program's front-end SDK to obtain the user-input verification information, and verifies the verification information based on a pre-set verification method; when the verification information passes, the mini-program's front-end SDK, based on the first private key and a second private key obtained from the mini-program's back-end SDK based on the encrypted identity information, performs the following steps: An unsigned digital pass is collaboratively signed to obtain a signed digital pass. The complete private key, composed of the first and second private keys, corresponds to a public key pre-registered in the digital signature support system. Using the SM4 symmetric key issued by the digital pass management system, the signed digital pass is encrypted to obtain an encrypted digital pass. A data request carrying the encrypted digital pass is sent to the digital pass management system, and the system returns privacy data based on the data request. The privacy data is verified by the digital pass management system using the encrypted digital pass. Upon successful verification, the data request is forwarded to the data provider, who then returns the data to the digital pass management system. In this solution, under reasonable, legal, and user-authorized conditions, by calling the user's privacy data into the mini-program, more personalized content and services are pushed to the user, improving the user experience. Furthermore, data encryption technologies are used to ensure the security and privacy of the privacy data during the calling process, ultimately achieving a balance between user experience and data privacy protection. Attached Figure Description

[0054] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0055] Figure 1 This is an architecture diagram of a privacy data retrieval system based on a mini-program, as disclosed in an embodiment of the present invention.

[0056] Figure 2 This is a business process diagram disclosed in an embodiment of the present invention;

[0057] Figure 3 This is a flowchart of a method for retrieving privacy data based on a mini-program, as disclosed in an embodiment of the present invention.

[0058] Figure 4 This is a flowchart of another method for accessing privacy data based on a mini-program, as disclosed in an embodiment of the present invention.

[0059] Figure 5 This is an interactive diagram of privacy data retrieval based on a mini-program, as disclosed in an embodiment of the present invention.

[0060] Figure 6 This is a structural diagram of a privacy data device based on a mini-program disclosed in an embodiment of the present invention. Detailed Implementation

[0061] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0062] In this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0063] First, the technical terms appearing in this application are explained as follows:

[0064] (a) Real Person Verification

[0065] In this application, the mini-program integrates and uses the real-person verification capabilities built into common applications on the market to prove that the privacy data was accessed by the user, ensuring that the user was present and real-person verification was performed.

[0066] 1. Face detection: It adopts WeChat's face detection capability, which captures the user's face image through the camera and automatically locates the face region using face recognition algorithms.

[0067] 2. Liveness Detection: By detecting the user's face, it prevents deception using non-live information such as photos and videos, ensuring that the user is present and undergoing verification.

[0068] 3. Face comparison: The captured face image is compared with the ID photo submitted by the user or an image in an authoritative database to determine whether the two belong to the same person.

[0069] (ii) Certificate Signature

[0070] CA certificate signing was used to sign the results of the real-person verification, ensuring the accuracy of the real-person verification results uploaded in this call.

[0071] 1. Identity Verification: CA digital certificates contain the identity information of the certificate holder. This information is used to prove the user's identity in digital transactions and ensure that both parties to the transaction can confirm each other's identity.

[0072] 2. Digital Signature: By using a digital certificate issued by a CA, individuals can digitally sign electronic documents. This signature has legal effect and can guarantee the integrity and non-repudiation of the document.

[0073] 3. Electronic Seal: In legal documents such as electronic contracts, CA digital certificates can act as electronic seals, giving electronic documents the same legal effect as traditional paper documents.

[0074] 4. Trust Foundation: As an authoritative and trustworthy third-party organization, the certificates issued by CA are widely recognized, providing an important trust foundation for online business.

[0075] (iii) Collaborative signature

[0076] 1. Key splitting: A key is split into multiple parts (i.e., subkeys) and distributed to different participants or devices (in this application, the private key is split into two parts, one for the front-end SDK and one for the back-end SDK), to ensure that the complete key can only be restored when all subkeys are merged.

[0077] 2. Key signing: After triggering the signing request, the mini-program SDK obtains the other half of the private key by calling the backend SDK, and together they encrypt the digest of the digital pass information.

[0078] 3. Signature Verification: The signature value is decrypted using the corresponding public key to obtain the decryption digest value. The original digest value is then obtained by performing a digest calculation on the digital pass. If the two are the same, it means that the data has not been tampered with during transmission; if they are different, it means that the data may have been tampered with or the signature is invalid.

[0079] (iv) National Cryptographic Algorithm

[0080] 1. SM2 Asymmetric Key Encryption Algorithm: The sender encrypts the private data in the digital pass using the SM2 public key, and the receiver decrypts it using the corresponding private key, ensuring security during data transmission.

[0081] 2. SM3 Digest Algorithm: The sender calculates a digest of the digital pass and then signs the digest value to ensure that the data is not tampered with during transmission.

[0082] 3. SM4 Symmetric Key Encryption Algorithm: The sender uses the SM4 symmetric key to encrypt the signed digital pass as a whole, ensuring data security during data transmission.

[0083] As the background technology indicates, existing technologies are generally limited by privacy protection measures to prevent privacy leaks. Even with user authorization, mini-programs cannot access users' private data when needed, thus hindering the provision of certain services and impacting user experience. Therefore, balancing user experience and data privacy protection has become an urgent problem to be solved.

[0084] Therefore, this invention discloses a method and apparatus for retrieving privacy data based on a mini-program. In this solution, under the premise of being reasonable, legal and authorized by the user, the user's privacy data is retrieved to the mini-program to push more personalized content and services to the user, thereby improving the user experience. In addition, data encryption technology is used to ensure the security and privacy of the privacy data during the retrieval process, ultimately achieving the goal of balancing user experience and data privacy protection.

[0085] It should be noted that in the process of accessing privacy data in this embodiment of the invention, the mini-program must strictly comply with relevant laws and regulations.

[0086] like Figure 1 The diagram shown is an architecture diagram of a privacy data retrieval system based on a mini-program disclosed in an embodiment of the present invention.

[0087] The system architecture is mainly divided into three layers: basic support, service support, and capability access.

[0088] 1. Basic Support: This mainly includes the shared support system and data gateway service. Leveraging the existing capabilities of the shared support system, it supports data users in applying for privacy data resources and data providers in registering privacy data resources and reviewing related resource applications. Based on the existing capabilities of the data gateway service, it supports the secure transmission and exchange of various data information in the privacy data sharing process, mainly including interface authentication, routing and forwarding, result data forwarding, and traffic control capabilities, ensuring the secure and efficient flow of sensitive personal data.

[0089] 2. Service Support: This mainly includes the digital pass management system and the digital signature support system. The digital pass management system provides digital pass-related services and management capabilities; the digital signature support system provides key registration and signing, certificate issuance and signing, signature verification, and other related services and management capabilities.

[0090] The digital signature support system comprises three layers: the access layer, the service layer, and the data layer, supporting mini-program scenarios. Figure 1 Taking the China-Israel government affairs mini-program scenario as an example, the integration of the front-end and server-side versions of the collaborative signature SDK was completed. The collaborative signature SDK (front-end version) works with the national platform's digital signature support system to complete key registration and digital signature of digital passes; the collaborative signature SDK (server-side version) works to complete the digital certificate issuance and digital signature of real-person verification results data. Meanwhile, the national platform's digital signature support system provides signature verification services for digital passes, which is an important support for realizing accurate authorization and data sharing processes.

[0091] The digital pass management system provides services such as digital pass encapsulation, encryption, and forwarding, and performs management tasks such as parsing, verification, and storage security of digital passes.

[0092] 3. Capability Integration: This mainly includes capability components such as digital pass, collaborative signature SDK (front-end version), and collaborative signature SDK (server-end version), which support the integration of government mini-programs and data sharing platforms.

[0093] Corresponding to the privacy data retrieval system based on a mini-program disclosed in the above embodiments of the present invention, such as... Figure 2 The diagram shown is a business process diagram disclosed in an embodiment of the present invention. This business process mainly includes 16 steps, as detailed below:

[0094] 1. Login and handle matters: Administrative counterparts (i.e. users) log in to the system through a browser or mini-program to handle relevant matters and authorize the access of their personal privacy data using their identity information.

[0095] To ensure the security of identity information during transmission, after authorizing the use of personal privacy data, the data user uses the SM2 public key issued by the digital pass management system to encrypt the identity information.

[0096] 2. Encapsulate digital credentials: The data user encapsulates the encrypted identity information into a digital credential.

[0097] To facilitate the encapsulation and parsing of digital passes and improve network transmission efficiency, data users need to encapsulate the content of the digital pass into a standard JSON format string based on the digital pass metadata.

[0098] 3. (Initial Authorization) Real Person Verification and Key Registration: If it is the first authorization, real person verification and key registration are required.

[0099] Once the real-person verification result is passed, the CA certificate issued by the digital signature support system is used to sign the real-person verification result information to ensure the non-repudiation of the real-person verification result information.

[0100] Then, after completing key registration in the digital signature support system, the collaborative signature SDK (server version) and the collaborative signature SDK (front-end version) will receive the private key assigned by the digital signature support system.

[0101] In addition, during key registration, users are guided to set up a verification method so that during the next authorization, process 4 can be executed directly for authorization verification without having to execute process 3 again.

[0102] 4. (Non-first authorization) Authorization verification: The verification method is set by the user when registering the key, and can be one of gesture, fingerprint and 3D face.

[0103] 5. Generate digest and key signature: The encapsulated digital pass is collaboratively signed by calling the collaborative signature SDK (front-end version). During the collaborative signing process, the private keys allocated to the collaborative signature SDK (server version) and the collaborative signature SDK (front-end version) by the digital signature support system are used respectively.

[0104] 6. Encryption Generation of X-ARQC: The signed digital pass is encrypted using the SM4 symmetric key issued by the digital pass management system to generate an encrypted digital pass X-ARQC.

[0105] 7. Call the API with X-ARQC: The data user sends a data request carrying an encrypted digital pass (X-ARQC) by calling the API.

[0106] 8. The data user sends a data request carrying an encrypted digital pass to the digital pass management system.

[0107] 9. The digital pass management system calls the digital signature support system to parse and verify the encrypted digital pass.

[0108] 10. After the digital pass management system verifies the encrypted digital pass, it stores the encrypted digital pass locally.

[0109] The storage of digital passes must ensure that sensitive personal data is not stored in plaintext, while also fully considering ease of use and convenience during data retrieval. The digital pass management system extracts non-sensitive data from digital passes and stores it in plaintext, while storing the complete content of the digital pass before decryption separately.

[0110] The retrieval function is primarily for auditing abnormal data usage by users later on. It involves retrieving the digital credentials used during the data usage process by querying the user's information to audit the call.

[0111] 11. Perform interface authentication on data requests.

[0112] Interface authentication refers to the process where, when a data user needs to use a certain interface of a data provider, an authorization code is issued in the data request. Authentication means verifying whether the authorization code is correct.

[0113] 12. The unified gateway service forwards data requests from data users.

[0114] 13. Verification Information: The data provider's precise authorization management center verifies the data request.

[0115] 14. After the data request is verified, return the privacy data indicated in the data request to the digital pass management system.

[0116] 15. The digital pass management system forwards privacy data to data users.

[0117] 16. Data users use private data to provide services to users.

[0118] In this embodiment of the invention, a privacy data access system based on mini-programs is constructed to provide related services and management capabilities such as digital passes and digital signatures, and to coordinate with basic support capabilities such as data sharing platforms and data service gateways to jointly ensure the secure and compliant sharing of privacy data.

[0119] Based on the above embodiments of the present invention, such as Figure 3 The diagram shown is a flowchart of a privacy data retrieval method based on a mini-program, disclosed in an embodiment of the present invention. Applied to data users, it includes the following steps:

[0120] Step S101: In response to the user's authorization operation through the mini-program, collect the user's identity information.

[0121] Step S102: Encrypt identity information using the SM2 public key issued by the digital pass management system, and encapsulate the encrypted identity information to obtain an unsigned digital pass.

[0122] In the specific implementation of step S102, the encrypted identity information is encapsulated into an unsigned digital pass in JSON format, which facilitates the encapsulation and parsing of the digital pass and improves network transmission efficiency.

[0123] Step S103: Call the mini-program's front-end SDK to query whether a first private key corresponding to the encrypted identity information exists; if yes, proceed to step S104; if no, register the key and then perform collaborative signing on the unsigned digital pass. For details, please refer to [link to relevant documentation]. Figure 4 The corresponding embodiments of the present invention.

[0124] It should be noted that if a user has registered a key in advance in the digital signature support system, the system will split the private key into a first private key and a second private key. The first private key will be distributed to the front-end SDK and the second private key will be distributed to the back-end SDK, enabling the front-end SDK and the back-end SDK to complete the collaborative signing of the digital pass.

[0125] It is understandable that if the user's first private key does not exist in the front-end SDK, it means that the user has not yet registered the key. Therefore, step S107 is executed to complete the key registration process. If the user's first private key exists in the front-end SDK, it means that the user has pre-registered the key. Therefore, step S104 is executed to complete the collaborative signature process.

[0126] In this embodiment of the invention, the front-end SDK is the collaborative signature SDK (front-end version) in the above embodiment of the invention, and the back-end SDK is the collaborative signature SDK (server version) in the above embodiment of the invention.

[0127] Step S104: Call the front-end SDK of the mini program to obtain the verification information input by the user, and verify the verification information based on the pre-set verification method. When the verification information passes the verification, the front-end SDK of the mini program performs collaborative signing on the unsigned digital pass based on the first private key and the second private key obtained from the back-end SDK of the mini program based on the encrypted identity information, and obtains the signed digital pass.

[0128] The complete private key, consisting of the first private key and the second private key, corresponds to the public key that has been pre-registered in the digital signature support system.

[0129] In step S104, the information to be verified can be gesture information, fingerprint information, facial information, etc., and the corresponding verification methods can be gesture verification, fingerprint verification, and facial verification.

[0130] These verification methods eliminate the need for real-person verification every time users access private data, ensuring privacy and security while improving the user experience.

[0131] However, in some special circumstances, such as when the process of collecting the information to be verified is affected, it may cause the verification of the information to fail. In this case, it is necessary to re-verify. If multiple verifications still fail, it is necessary to initiate real-person verification for the user.

[0132] In one embodiment, if the verification of the information to be verified fails based on the pre-set verification method, the process returns to the step of obtaining the user-input information to be verified and verifying it based on the pre-set verification method, and records the number of returns. When the number of returns exceeds the threshold (e.g., five times), a real-person verification for the user is initiated to obtain the verification result. When the verification result is successful, the digital certificate in the backend SDK of the mini-program is called to sign the verification result, resulting in a signed verification result. If the frontend SDK of the mini-program verifies that the signed verification result is valid, the unsigned digital pass is collaboratively signed based on the first private key and the second private key obtained from the backend SDK of the mini-program based on the encrypted identity information, resulting in a signed digital pass.

[0133] Among them, real-person verification can call the facial recognition verification provided by common applications to determine whether the user is the one who is accessing private data.

[0134] Step S105: Use the SM4 symmetric key issued by the digital pass management system to encrypt the signed digital pass as a whole, and obtain the encrypted digital pass.

[0135] In step S105, the signed digital pass is encrypted as a whole to ensure the security of the digital pass when subsequent data requests are transmitted with the digital pass.

[0136] Step S106: Send a data request carrying the encrypted digital pass to the digital pass management system and receive the privacy data returned by the digital pass management system based on the data request.

[0137] In this process, the privacy data is verified by the digital pass management system using encrypted digital passes. Once the verification is successful, the data request is forwarded to the data provider, who then returns the data to the digital pass management system based on the request.

[0138] Privacy data includes user browsing history, user preference settings, etc. Data users can use privacy data to push more personalized content and services to users, thereby improving user satisfaction and stickiness.

[0139] It should be noted that the digital pass management system parses and verifies the encrypted digital pass. After confirming that it is correct, the system stores the encrypted digital pass and forwards the data request to the data provider. The data provider verifies the relevant information, and after verification, forwards the privacy data to the digital pass management system through the data sharing support system. The digital pass management system then forwards the data to the mini-program to help users complete their tasks.

[0140] The purpose of storing encrypted digital credentials is to enable subsequent data users to initiate a retrieval request when they discover abnormalities in the access to privacy data, in order to audit whether the access to privacy data was authorized by the user.

[0141] In one embodiment, in response to a user's search instruction for a target encrypted digital pass, a search request is generated; the target encrypted digital pass includes the encrypted digital pass used when accessing privacy data; the search request is sent to the digital pass management system, and the target encrypted digital pass returned by the digital pass management system is received.

[0142] like Figure 4 The diagram shown is a flowchart of another method for retrieving privacy data based on a mini-program, as disclosed in an embodiment of the present invention. Figure 4 This illustrates the specific implementation process of registering a key and collaboratively signing an unsigned digital pass when the front-end SDK of a mini-program does not possess the first private key corresponding to the encrypted identity information. The main steps include:

[0143] Step S201: Determine whether the time elapsed since the last verification result for the user was passed exceeds the preset validity period; if yes, proceed to step S202; if no, proceed to step S205.

[0144] In step S201, since real-person verification not only takes time but also requires interaction with the user, multiple verification interactions with the user in a short period of time can easily affect the user experience. Therefore, a validity period for the verification result is set, generally ten minutes, which has little impact on security, ensuring both security and improving the user experience.

[0145] Step S202: Initiate real-person verification for the user and obtain the verification result.

[0146] Among them, real-person verification can call the facial recognition verification provided by common applications to determine whether the user is the one who is accessing private data.

[0147] Step S203: When the verification result is passed, call the digital certificate in the backend SDK of the mini program to sign the verification result and obtain the signed verification result.

[0148] In step S203, after the mini-program integrates the backend SDK, the mini-program's backend needs to apply for a digital certificate from the digital signature support system. The digital signature support system then issues the certificate to the mini-program's backend SDK based on the application.

[0149] Signing the verification result is essentially the process by which the user acknowledges the verification result, thus ensuring the non-repudiation of the verification result.

[0150] Step S204: Call the front-end SDK of the mini-program to verify the signature and check whether the result is valid; if yes, proceed to step S205; if no, proceed to step S202.

[0151] In step S204, the validity determination of the verification result includes determining whether it has exceeded the preset validity period.

[0152] Step S205: Call the front-end SDK of the mini-program to send the public key corresponding to the encrypted identity information to the digital signature support system, so that the digital signature support system allocates the first private key corresponding to the encrypted identity information to the front-end SDK of the mini-program and allocates the second private key corresponding to the encrypted identity information to the back-end SDK of the mini-program.

[0153] Step S206: In response to the user's setting operation, set the verification method; the verification method is used to verify the information to be verified by the user, so as to collaboratively sign the unsigned digital pass when the verification is successful.

[0154] In step S206, the verification method can be gesture verification, fingerprint verification, or face verification.

[0155] The verification method settings ensure that only the user-defined verification method is executed when step S104 is performed. Users do not need to undergo real-person verification every time they access private data, which not only ensures privacy and security but also improves the user experience.

[0156] Step S207: The front-end SDK of the mini-program performs collaborative signing on the unsigned digital pass based on the first private key and the second private key obtained from the back-end SDK of the mini-program based on the encrypted identity information, to obtain the signed digital pass, and writes the verification result of the signature into the signed digital pass.

[0157] In step S207, since this collaborative signing is performed immediately after registering the key and setting the verification method, and the user's real-person verification has been passed, in order to improve efficiency, there is no need to verify the verification method again. The verification result after signing is directly written into the digital pass after signing, indicating that the digital pass after signing has been confirmed by the user.

[0158] Based on the above-described method for retrieving privacy data from a mini-program, this solution, under the premise of being reasonable, legal, and authorized by the user, retrieves the user's privacy data to the mini-program to push more personalized content and services to the user, thereby improving the user experience. In addition, data encryption technologies are used to ensure the security and privacy of the privacy data during the retrieval process, ultimately achieving a balance between user experience and data privacy protection.

[0159] Based on the above embodiments of the present invention, such as Figure 5 The diagram shown is an interactive diagram of privacy data retrieval based on a mini-program, as disclosed in an embodiment of the present invention, taking a government affairs service scenario as an example.

[0160] The participants in the interaction include: administrative counterparts (i.e., users), data users, the mini-program's personal privacy data sharing support system, and data providers.

[0161] Data users include: government mini-programs, authoritative facial verification capabilities (components), collaborative signature SDK (front-end version), government mini-program server, collaborative signature SDK (server version), and the back-end management system of government mini-programs.

[0162] The support system for sharing personal privacy data in mini-programs includes: a digital signature support system and a digital pass management system.

[0163] This invention describes the interaction process of accessing privacy data based on a mini-program in five stages, as follows:

[0164] 1. Certificate Issuance Process: After the mini-program integrates the collaborative signature SDK (server version), it needs to apply for a digital certificate from the digital signature support system, which will then issue the digital certificate based on the application.

[0165] 2. Digital Password Encapsulation Step: When a user logs into the mini-program to handle a matter, if the matter requires access to private data, the user's authorization is required. The mini-program needs to forward the user information and other necessary information to the backend management system. The backend management system encrypts the user information, encapsulates it along with other information into an unsigned digital pass, and returns it to the mini-program.

[0166] 3. Face verification and key registration: After encapsulating the digital pass, it needs to be digitally signed. Before digital signing, it is necessary to determine whether a key has been registered based on the encrypted information string in the pass. If a key has been registered, the digital pass can be digitally signed directly; if no key is available, face verification and key registration are required.

[0167] Before registering the key, it is necessary to determine whether face verification is required based on whether the previous face verification information is still valid (i.e., within 10 minutes). If the previous face verification information is still valid, face verification is not required. If it has expired, face verification is required to obtain the verification result information. Then, the collaborative signature SDK (server version) is called to sign the verification result information, and the collaborative signature SDK (front-end version) is passed in to request the registration key.

[0168] The collaborative signature SDK performs signature verification on the signed verification result information and confirms the validity of the verification result. If it fails, the face verification needs to be performed again. If it passes, the user is guided to complete the verification method settings and then a key is generated.

[0169] 4. Digital Passport Signing and Encrypted Forwarding: When digitally signing a digital passport, the first signature is exempt from identity verification and the face verification result information is written into the digital passport after signing. For subsequent verifications, users need to be guided to verify their identity according to the verification method set during key registration. If the verification fails five times, face verification needs to be performed again. If the verification passes five times, the digital signature is completed (no need to write face verification result information), and the signed digital passport is returned to the government affairs mini-program.

[0170] After the mini-program forwards the signed digital pass to the backend management system, the backend management system will encrypt and forward it.

[0171] 5. Parsing and Verification: The digital pass management system parses and verifies the digital pass. After confirming that it is correct, it stores the digital pass and forwards the data request to the data provider. The data provider verifies the relevant information, and after verification, the privacy data is forwarded to the government affairs mini-program through the data sharing support system to help users complete the handling of matters.

[0172] It should be noted that the specific implementation process of the above-mentioned interaction process corresponds to the privacy data retrieval method based on a mini-program disclosed in the above-mentioned embodiment of the present invention, and they can be referred to each other.

[0173] Based on the privacy data retrieval and interaction method disclosed in the above embodiments of the present invention, under the premise of being reasonable, legal and authorized by the user, the user's privacy data is retrieved to the mini program to push more personalized content and services to the user, thereby improving the user experience. In addition, data encryption related technologies are used to ensure the security and privacy of privacy data during the retrieval process, ultimately achieving the goal of balancing user experience and data privacy protection.

[0174] Corresponding to the privacy data retrieval method based on a mini-program disclosed in the above embodiments of the present invention, such as... Figure 6The diagram shown is a structural diagram of a privacy data device based on a mini-program disclosed in an embodiment of the present invention. It is applied to a data user and includes: an authorization unit 601, an encapsulation unit 602, a query unit 603, a first collaborative signature unit 604, an overall encryption unit 605, and a calling unit 606.

[0175] The authorization unit 601 is used to collect the user's identity information in response to the user's authorization operation through the mini-program.

[0176] The encapsulation unit 602 is used to encrypt identity information using the SM2 public key issued by the digital pass management system, and encapsulate the encrypted identity information to obtain an unsigned digital pass.

[0177] In one embodiment, the encapsulation unit 602, used to encapsulate encrypted identity information to obtain an unsigned digital pass, is specifically used for:

[0178] Encapsulate the encrypted identity information into an unsigned digital pass in JSON format.

[0179] The query unit 603 is used to call the front-end SDK of the mini-program to query whether there is a first private key corresponding to the encrypted identity information.

[0180] In one embodiment, the device further includes:

[0181] The key registration and signing unit is used to initiate a verification of the user's identity if there is no first private key corresponding to the encrypted identity information, and the time between the last verification result of the user's real person verification and the current time exceeds the preset validity period.

[0182] When the verification result is passed, the digital certificate in the backend SDK of the mini program is called to sign the verification result, and the signed verification result is obtained.

[0183] If the time since the last verification of the user's identity was passed is within the preset validity period, or if the verification result is valid after calling the front-end SDK of the mini program to verify the signature, then the front-end SDK of the mini program sends the public key corresponding to the encrypted identity information to the digital signature support system, so that the digital signature support system allocates the first private key corresponding to the encrypted identity information to the front-end SDK of the mini program, and allocates the second private key corresponding to the encrypted identity information to the back-end SDK of the mini program;

[0184] In response to the user's settings, a verification method is set; the verification method is used to verify the information to be verified by the user, so as to collaboratively sign the unsigned digital pass when the verification passes.

[0185] The front-end SDK of the mini-program uses the first private key and the second private key obtained from the back-end SDK of the mini-program based on the encrypted identity information to collaboratively sign the unsigned digital pass, obtain the signed digital pass, and write the verification result of the signature into the signed digital pass.

[0186] The first collaborative signature unit 604 is used to call the front-end SDK of the mini-program to obtain the user-input verification information if a first private key corresponding to the encrypted identity information exists, and to verify the verification information based on a pre-set verification method. When the verification information passes the verification, the front-end SDK of the mini-program performs collaborative signature on the unsigned digital pass based on the first private key and the second private key obtained from the back-end SDK of the mini-program based on the encrypted identity information, to obtain a signed digital pass. The complete private key composed of the first private key and the second private key corresponds to the public key pre-registered in the digital signature support system.

[0187] In one embodiment, the device further includes:

[0188] The second collaborative signature unit is used to return to the step of obtaining the user-inputted information and verifying it based on the pre-set verification method if the verification of the information to be verified fails based on the pre-set verification method, and to record the number of times the verification is returned.

[0189] When the number of responses exceeds the threshold, a real-person verification for the user is initiated to obtain the verification result.

[0190] When the verification result is passed, the digital certificate in the backend SDK of the mini program is called to sign the verification result, and the signed verification result is obtained.

[0191] If the verification result of the front-end SDK of the mini-program is valid, then the unsigned digital pass is collaboratively signed based on the first private key and the second private key obtained from the back-end SDK of the mini-program based on the encrypted identity information, so as to obtain the signed digital pass.

[0192] The overall encryption unit 605 is used to encrypt the signed digital pass using the SM4 symmetric key issued by the digital pass management system, so as to obtain an encrypted digital pass.

[0193] Calling unit 606 is used to send a data request carrying an encrypted digital pass to the digital pass management system and receive privacy data returned by the digital pass management system based on the data request. The privacy data is used by the digital pass management system to verify the encrypted digital pass. After the verification is successful, the data request is forwarded to the data provider, and the data provider returns the data to the digital pass management system based on the data request.

[0194] In one embodiment, after sending a data request carrying an encrypted digital pass to the digital pass management system, the digital pass management system performs a signature verification operation on the encrypted digital pass. Once the verification is successful, the pass is stored locally. The device further includes:

[0195] The retrieval unit is used to generate a retrieval request in response to a user's retrieval instruction for a target encrypted digital pass; the target encrypted digital pass includes the encrypted digital pass used when accessing privacy data;

[0196] Send the retrieval request to the digital pass management system and receive the target encrypted digital pass returned by the digital pass management system.

[0197] Based on the privacy data retrieval device for mini-programs disclosed in the above embodiments of the present invention, under the premise of being reasonable, legal and authorized by the user, the user's privacy data is retrieved to the mini-program to push more personalized content and services to the user, thereby improving the user experience. In addition, data encryption-related technologies are used to ensure the security and privacy of privacy data during the retrieval process, ultimately achieving the goal of balancing user experience and data privacy protection.

[0198] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the descriptions in the method embodiments. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0199] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0200] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for calling privacy data based on applet, characterized in that, The method applied to a data user comprises: In response to a user's authorization operation through a mini-program, identity information of the user is collected; The identity information is encrypted by an SM2 public key issued by a digital pass management system, and the encrypted identity information is encapsulated to obtain an unsigned digital pass; A front-end SDK of the mini-program is called to query whether a first private key corresponding to the encrypted identity information exists; If yes, a front-end SDK of the mini-program is called to obtain verification information input by the user, and the verification information is verified based on a pre-set verification mode, and when the verification information passes the verification, the front-end SDK of the mini-program co-signs the unsigned digital pass based on the first private key and a second private key obtained from a back-end SDK of the mini-program based on the encrypted identity information, to obtain a signed digital pass; the complete private key composed of the first private key and the second private key has a corresponding relationship with a public key pre-registered in a digital signature support system; An SM4 symmetric key issued by the digital pass management system is used to encrypt the signed digital pass as a whole to obtain an encrypted digital pass; A data request carrying the encrypted digital pass is sent to the digital pass management system, and private data returned by the digital pass management system based on the data request is received; the private data is verified by the digital pass management system based on the encrypted digital pass, and when the verification passes, the data request is forwarded to a data provider, and the data provider returns to the digital pass management system based on the data request.

2. The method of claim 1, wherein, The encapsulation of the encrypted identity information to obtain the unsigned digital pass comprises: The encrypted identity information is encapsulated into a JSON format unsigned digital pass.

3. The method of claim 1, wherein, If the first private key corresponding to the encrypted identity information does not exist, the method further comprises: If the time when the last real person verification for the user passes the verification result exceeds a preset validity period from the current time, the real person verification for the user is initiated to obtain a verification result; When the verification result is passed, a digital certificate in a back-end SDK of the mini-program is called to sign the verification result to obtain a signed verification result; If the time when the last real person verification for the user passes the verification result does not exceed the preset validity period from the current time, or the front-end SDK of the mini-program verifies that the signed verification result is valid, the front-end SDK of the mini-program sends a public key corresponding to the encrypted identity information to the digital signature support system, so that the digital signature support system allocates a first private key corresponding to the encrypted identity information to the front-end SDK of the mini-program, and allocates a second private key corresponding to the encrypted identity information to a back-end SDK of the mini-program; In response to a user's setting operation, a verification mode is set; the verification mode is used to verify the verification information input by the user, so as to co-sign the unsigned digital pass when the verification passes. The front-end SDK of the applet performs collaborative signature on the unsigned digital pass based on the first private key and a second private key obtained from the back-end SDK of the applet based on the encrypted identity information, to obtain a signed digital pass, and writes the signed verification result into the signed digital pass.

4. The method of claim 1, wherein, The method further includes: If the verification of the to-be-verified information based on the pre-set verification mode fails, returning to perform the step of obtaining the to-be-verified information input by the user and verifying the to-be-verified information based on the pre-set verification mode, and recording the number of returns; When the number of returns exceeds a threshold number of times, initiating real-person verification on the user to obtain a verification result; When the verification result is passed, calling a digital certificate in the back-end SDK of the applet to sign the verification result to obtain a signed verification result; If the front-end SDK of the applet verifies that the signed verification result is valid, the front-end SDK of the applet performs collaborative signature on the unsigned digital pass based on the first private key and a second private key obtained from the back-end SDK of the applet based on the encrypted identity information, to obtain a signed digital pass.

5. The method according to any one of claims 1 to 4, characterized in that, After sending a data request carrying the encrypted digital pass to the digital pass management system, the digital pass management system performs a signature verification operation on the encrypted digital pass, and stores the encrypted digital pass locally when the signature verification passes, the method further includes: In response to a search instruction of a user for a target encrypted digital pass, generating a search request; the target encrypted digital pass includes the encrypted digital pass used when the private data is called; Sending the search request to the digital pass management system, and receiving the target encrypted digital pass returned by the digital pass management system.

6. An apparatus for calling privacy data based on an applet, characterized by comprising: The device is applied to a data user, and includes: An authorization unit configured to, in response to an authorization operation of a user through an applet, collect identity information of the user; An encryption unit configured to encrypt the identity information by using an SM2 public key issued by a digital pass management system, and package the encrypted identity information to obtain an unsigned digital pass; A query unit configured to call a front-end SDK of the applet to query whether a first private key corresponding to the encrypted identity information exists; A first collaborative signature unit configured to, if the first private key corresponding to the encrypted identity information exists, call the front-end SDK of the applet to obtain to-be-verified information input by the user, and verify the to-be-verified information based on a pre-set verification mode, and when the to-be-verified information passes the verification, the front-end SDK of the applet performs collaborative signature on the unsigned digital pass based on the first private key and a second private key obtained from a back-end SDK of the applet based on the encrypted identity information, to obtain a signed digital pass; the complete private key composed of the first private key and the second private key has a corresponding relationship with a public key pre-registered in a digital signature support system. An overall encryption unit is configured to encrypt the signed digital pass in its entirety by using an SM4 symmetric key issued by the digital pass management system, to obtain an encrypted digital pass; An invoking unit is configured to send a data request carrying the encrypted digital pass to the digital pass management system, and receive privacy data returned by the digital pass management system based on the data request; the privacy data is returned by the digital pass management system after signature verification of the encrypted digital pass is passed, and the data request is forwarded to a data provider; and the data provider returns the privacy data to the digital pass management system based on the data request.

7. The apparatus of claim 6, wherein, The packaging unit for packaging the encrypted identity information to obtain the unsigned digital pass is specifically configured to: package the encrypted identity information into an unsigned digital pass in JSON format.

8. The apparatus of claim 6, wherein, The apparatus further includes: A key registration and signature unit is configured to, if there is no first private key corresponding to the encrypted identity information, and the time when the last real person verification for the user is passed exceeds a preset validity period from the current time, initiate real person verification for the user to obtain a verification result; When the verification result is passed, a digital certificate in a backend SDK of the applet is called to sign the verification result to obtain a signed verification result; If the time when the last real person verification for the user is passed does not exceed the preset validity period from the current time, or the signed verification result is verified as valid by a front-end SDK of the applet, the front-end SDK of the applet is called to send a public key corresponding to the encrypted identity information to a digital signature support system, so that the digital signature support system allocates a first private key corresponding to the encrypted identity information to the front-end SDK of the applet, and allocates a second private key corresponding to the encrypted identity information to a backend SDK of the applet; In response to a setting operation of the user, a verification mode is set; the verification mode is used to verify the to-be-verified information input by the user, so as to co-sign the unsigned digital pass when the verification is passed; The front-end SDK of the applet co-signs the unsigned digital pass based on the first private key and the second private key obtained from the backend SDK of the applet based on the encrypted identity information, to obtain a signed digital pass, and writes the signed verification result into the signed digital pass.

9. The apparatus of claim 6, wherein, The apparatus further includes: A second co-signing unit is configured to, if the to-be-verified information is not verified based on the pre-set verification mode, return to execute the step of obtaining the to-be-verified information input by the user and verifying the to-be-verified information based on the pre-set verification mode, and record the number of returns; When the number of returns exceeds a threshold number of times, real person verification for the user is initiated to obtain a verification result; When the verification result is passed, a digital certificate in a backend SDK of the applet is called to sign the verification result to obtain a signed verification result; If the front-end SDK of the applet verifies the signature and the verification result is valid, the unsigned digital pass is co-signed based on the first private key and a second private key obtained from the back-end SDK of the applet based on the encrypted identity information, to obtain a signed digital pass.

10. The apparatus of any one of claims 6 to 9, wherein, After sending a data request carrying the encrypted digital pass to the digital pass management system, the digital pass management system performs a signature verification operation on the encrypted digital pass, and stores the encrypted digital pass locally when the signature verification passes. The retrieval unit is configured to generate a retrieval request in response to a retrieval instruction of a target encrypted digital pass issued by a user, the target encrypted digital pass including the encrypted digital pass used when the privacy data is called; The retrieval request is sent to the digital pass management system, and the target encrypted digital pass returned by the digital pass management system is received.

Images