The present disclosure relates to a data verification terminal and a data verification server, and in particular to a data verification terminal and a data verification server that improve data security.
In today's digital age, data verification systems are becoming more and more important in various applications, such as online banking, e-commerce, and smart cities. However, traditional verification systems face numerous challenges, including data security, system reliability and user experience issues. Therefore, developing a data verification system that can provide high security and high reliability has become an urgent technical issue that needs to be solved.
The present disclosure relates to a data verification technology, in particular to an improved system for a data verification server and a data verification terminal, aiming to improve the security and reliability of a verification process. The data verification server includes a server registration module, a database, a server verification module and a server authorization module. The server registration module is configured to receive a user's registration data and generate aggregated data to be stored in the database. The server verification module is configured to receive verification data from the data verification terminal and perform verification. The server authorization module is configured to select the aggregated data from the database based on a result of the verification and transmit the aggregated data to a requesting terminal or a third-party platform through a communication network.
The data verification terminal includes a terminal connection module, a terminal authorization module and a terminal verification module. The terminal connection module is configured to connect to the data verification server and a service platform server through a communication network. The terminal authorization module is configured to receive an authorization request from the service platform server, and the terminal verification module is configured to transmit the verification data to the data verification server through the terminal connection module, so that the data verification server transmits at least one piece of aggregated data to the service platform server.
In addition, the present disclosure discloses a specific operation process performed by the terminal connection module, and the specific operation process includes initialization of a network interface, establishment of a secure connection, data packet transmission and retransmission mechanisms, thus ensuring the stability and security of the communication process. These measures effectively enhance the security and reliability of the data verification system, thus solving the potential safety hazards in the existing technology and providing a safer and more reliable data verification solution.
In order to make the above-mentioned features and advantages of the present disclosure more obvious and understandable, embodiments are given below and described in detail with reference to the accompanying drawings.
A more comprehensive understanding of the present disclosure will be provided with reference to the drawings of the present embodiments. However, the present disclosure may also be embodied in various forms and should not be limited to the embodiments described herein. The same or similar reference numerals indicate the same or similar components, which will not be reiterated in the following paragraphs. For the following embodiments, those skilled in the art will understand that they can be combined or matched with each other and are not independent or mutually exclusive embodiments.
The server registration module 110 is configured to receive one or more pieces of registration data from the user 150. These registration data includes, but is not limited to, the user's personal privacy information, such as phone number and personal information on various certificates. The various certificates mentioned include, but are not limited to, identity (ID) cards, health insurance cards, passports, driver's licenses, credit cards, natural person certificates, etc. These registration data can also be biometric data, such as fingerprint data, facial recognition data, etc. Specifically, the ID card information may include name, ID card number, birthday, address, spouse's name and other information. Health insurance card information may include name, health insurance card number, birthday and other information. Passport information can include Chinese name, English name, passport number, birthday and other information. Driver's license information may include name, birthday, ID number, address, driver's license number and other information. Credit card information may include credit card number, credit card expiration date, credit card number, English name and other information.
The server registration module 110 is configured to process the received registration data, generate one or more pieces of aggregated data, and store the aggregated data in the database 120. Specifically, when the user 150 accesses data or obtains services on any service platform provided by government units or non-governmental organizations, the service platform will first provide a verification method to verify personal information of the user 150. The server registration module 110 needs to process the received registration data (e.g., performing combination of the received registration data) according to the verification method provided by the service platform to generate aggregated data, and the server registration module 110 then transmits the generated aggregated data to the service platform for verification. For example, when the user 150 would like to file a tax on a tax declaration platform, one verification method is to use the phone number, the ID card number, and the health insurance card number of the user 150 for verification. Therefore, the server registration module 110 can extract the ID card number from ID card information and the health insurance card number from the health insurance card information based on the verification method and combine these extracted numbers with the phone number of the user 150 to generate a set of aggregated data. Then, the server registration module 110 will transmit the aggregated data to the tax declaration platform. In addition, after the server registration module 110 transmits the aggregated data to the tax declaration platform, the server registration module 110 can store the aggregated data in the database 120. In other words, it is not necessary to provide all the information on the ID card and health insurance card for the verification. Instead, partial information can be extracted from various identity information and then combined to form the aggregated data for the verification. In such a way, the protection of user's personal data and the unpredictability of the data required by the verification of the service platform can be improved. In other embodiments, the verification method can generate different aggregated data through different combinations of the following multiple pieces of data. The multiple pieces of data includes, but are not limited to, at least any one piece of information extracted from the ID card information of the user 150 (e.g., at least any one of the name, ID card number, birthday, address, spouse's name, etc.), at least any one piece of information extracted from the health insurance card information of the user 150 (e.g., at least any one of the name, health insurance card number, birthday, etc.), at least any one piece of information extracted from the passport information of the user 150 (e.g., at least any one of the Chinese name, English name, passport number, birthday, etc.), at least any one piece of information extracted from the driver's license information of the user 150 (e.g., at least any one of the name, birthday, ID card number, address, driver's license number, etc.), at least any one piece of information extracted from the credit card information of the user 150 (e.g., at least any one of the credit card number, credit card expiration date, English name, etc.), the contact information of the user 150 (e.g., at least any one of the email, communication software account, etc.), the phone number of the user 150, and the biometric information of the user 150 (e.g., at least any one of the fingerprint data, facial recognition data, etc.).
In another embodiment, when the user 150 accesses data or obtains services on another service platform, another verification method provided by the service platform is to use the credit card number, driver's license number, and passport number for verification. Therefore, the server registration module 110 can extract the credit card number from the credit card information, extract the driver's license number from the driver's license information, and extract the passport number from the passport information based on another verification method to generate another set of aggregated data. Then, the server registration module 110 will transmit another set of aggregated data to the service platform. In addition, after the server registration module 110 transmits another set of aggregated data to the service platform, the server registration module 110 can also store the aggregated data in the database 120.
During a data registration process, the server registration module 110 will first format the biometric data submitted by the user 150 to ensure the uniformity and standardization of the data. Then, the server registration module 110 can perform a hash operation on the data, for example, by using the SHA-256 algorithm, to generate corresponding hash values. These hash values are stored in the database as part of the aggregate data for subsequent verification.
The server verification module 130 is configured to receive verification data from the data verification terminal 200 and verify whether the terminal 200 is operated by the user 150 based on the verification data. Specifically, the server verification module 130 can compare the received verification data with verification check data stored in the database 120 to determine a verification result. When the server verification module 130 compares the received verification data with the verification check data stored in the database 120, for example, to determine whether they are the same or match, the server authorization module 140 can selectively obtain one or more pieces of aggregated data from the database and transmit the obtained aggregated data to a service platform server (not shown) in the third-party platform 300 via a communication network. In order to improve verification efficiency, the server verification module 110 can implement multi-thread processing to process multiple verification requests concurrently.
In one embodiment, the server verification module 130 can be regarded as having a login verification service module 131, an electronic Know Your Customer (eKYC) service module 132, a data verification service module 133, and a verification kernel 135 that complies with the Fast Identity Online 2 (FIDO2) project.
The login verification service module 131 is configured to accept a login request from a network side and perform a verification procedure to ensure the legitimacy and privacy of an access request received by the data verification server 100. The data verification service module 133 is configured to verify the data of individual users (e.g., customers).
The ekYC service module 132, for example, is implemented as software or hardware that can utilize different technologies for recognizing users through images (e.g., by utilizing fingerprint scanning or face recognition technologies), voiceprints or other suitable personalized features. The verification kernel 135 that complies with the FIDO2) project uses, for example, the authentication standard of Universal 2nd Factor for verification. The method using the authentication standard of Universal 2nd Factor may include, for example, that the service provider supplies the user with a personalized near-field communication card or an electronic key suitable for universal serial bus. The near-field communication card or electronic key contains a specific authentication key, allowing the server to determine, during an authentication process, whether the near-field communication card or electronic key used by the user terminal corresponds to a specific user based on the authentication key.
The server authorization module 140 establishes a communication connection between the server verification module 130 and the database 120. The server authorization module 140 may include an authorization service module 141 and an authorization logging service module 143. The authorization service module 141 selectively obtains one or more pieces of aggregate data from the database 120 based on the verification result and transmits the obtained aggregate data to the requesting terminal or third-party platform through the communication network. The authorization logging service module 143 is configured to record detailed information of each authorization operation, including authorization time, authorization object, authorization result, etc. These pieces of information can be stored in authorization records for future queries and audits.
The data verification terminal 200 includes a terminal connection module 210, a terminal authorization module 220, a terminal verification module 230 and a terminal registration module 240.
The terminal connection module 210 is configured to establish a communication connection with the data verification server 100 through the communication network to ensure that data can be transmitted safely. The terminal connection module 210 implements support for multiple communication protocols, such as HTTPS, TLS, etc., to ensure the security and integrity of data during transmission.
The terminal authorization module 220 establishes a communication connection with the terminal connection module 210. When receiving an authorization request from a service platform server in a third-party platform in the communication network, the terminal authorization module 220 can process the authorization request and transmit it to the terminal verification module 230. The terminal authorization module 220 may further include an authorization module 221 and an authorization record module 222. The authorization record module 222 facilitates the user 150 to connect to the data verification server 100 to query previous authorization records from the authorization logging service module 143.
The terminal verification module 230 is configured to verify whether the data verification terminal 200 is operated by the user 150 corresponding to the authorization request. When the terminal authorization module 220 receives the authorization request, the terminal verification module 230 can, for example, use an ekYC module 231 to obtain biometric data (such as facial image, fingerprint and voiceprint) from the user 150, and generate verification data based on the obtained biometric data, and then transmit the generated verification data to the data verification server 100 through the terminal connection module 210, thus enabling the data verification server 100 to transmit one or more pieces of aggregated data to a service platform server (not shown) in the third-party platform 300. During the process of verification, the terminal verification module 230 can also perform multi-factor verification, such as user's password, SMS verification code, etc., to improve verification security.
The terminal registration module 240 is configured to obtain the registration information of the user 150 and transmit the registration information to the data verification server 100 through the terminal connection module 210 for registration. The terminal registration module 240 can guide the user 150 through a multi-step registration process to ensure that all necessary information is completely collected and submitted.
With this architecture, the holder (e.g., user) of the data verification terminal 200 can perform access operations to the data verification server 100 through the network and finally obtain the necessary identity verification, thus securely complete the submission of personal information or authorization with a third party (such as banks, travel agents, government units).
In summary, the entire process of verification can be shown in
Next, taking
In addition, taking
In the present embodiment, the data verification server 100 and the data verification terminal 200 work together to encrypt the biometric data by using a hash algorithm and TOTP (Time-based One-Time Password, TOTP), and the server slide than performs decryption and verification processes.
First, the identity verification is performed by the data verification terminal 200 for the user. The terminal verification module 230 obtains the user's biometric data, such as fingerprints, facial recognition data, etc. The terminal verification module 230 generates a one-time password TOTP at the current time and performs hash processing on the obtained biometric data through the SHA-256 algorithm to generate a hash value.
Subsequently, the terminal verification module 230 uses the generated TOTP as a key to encrypt the hashed biometric data, for example, by using the AES algorithm. The terminal connection module 210 packages the encrypted verification data into data packets and attaches necessary protocol headers to the data packets to ensure that the data can be correctly parsed and processed. Then, the terminal connection module 210 transmits the encrypted verification data to the data verification server 100.
After receiving the encrypted verification data, the server verification module 130 of the data verification server 100 generates the same TOTP as the one of the terminal based on the current time and shared key and uses the generated TOTP as a key to decrypt the received encrypted verification data to obtain the hash value of the biometric data. The server verification module extracts the hash value of the corresponding user's biometric data from the database 120 and compares the extracted hash value with the decrypted hash value. If the extracted hash value and the decrypted hash value match, the verification is successful.
During the process of verification, in order to improve security, the server verification module can double-encrypt the verification data, that is, in addition to using TOTP for encryption, a server-side public key can be used for asymmetric encryption. In such a way, even if the data is intercepted during transmission, the attacker cannot decrypt the intercepted data to obtain original data, thus further improving the security of the data transmission.
The terminal connection module 210 of the data verification terminal 200 can initialize a network interface upon being activated and select an appropriate communication protocol, such as HTTPS. The HTTPS protocol provides a transmission encryption function that can protect a transmission process of sensitive data. During an initialization process, the terminal connection module can load necessary security credentials. These credentials are used to establish a secure SSL/TLS connection to ensure the integrity and confidentiality of data during the communication process.
After establishing an initial connection, the terminal connection module 210 queries the IP address of the server through a domain name system DNS and initiates a connection request with the data verification server 100. In order to improve the reliability of the connection, the terminal connection module implements an automatic reconnection mechanism. If the initial connection fails, the system can automatically retry within a short period of time until the connection is successfully established.
The terminal connection module 210 also provides a data packet function, which encapsulates the data to be transmitted into data packets that comply with the protocol format and attaches necessary protocol headers to ensure that the data can be correctly parsed on the server side. The data packets contains encrypted verification information, timestamps, random numbers and other information to prevent replay attacks and data tampering.
During a data transmission process, the terminal connection module 210 can segment the transmitted data, and each segment of data will be encrypted and integrity checked. The terminal connection module can use the HMAC-SHA256 algorithm to check each piece of data, generate a data integrity identifier, and attach the data integrity identifier to the data packet. After receiving the data packet, the data verification server can perform the same check operation to ensure that the received data has not been tampered with.
In addition, the terminal connection module 210 also implements a flow control mechanism to dynamically adjust the data transmission rate according to network conditions to avoid network congestion caused by sudden traffic. When an increase in network latency or packet loss rate is detected, the terminal connection module can automatically reduce the data transmission rate to ensure that data can be reliably transmitted to the server.
In a use case, the user first launches and logs in to the APP in step S502A, and then the APP can proceed with step S502B to request the data verification server to allow the user to log in. The server verification module of the data verification server can access the database in step S502C to determine whether the user is a registered user. Then, in step S502D, the server authorization module of the data verification server selectively obtains one or more pieces of aggregated data from the database based on a verification value and transmits the obtained aggregated data through the communication network (step S503A to step S503D). In
If it is determined that the credit card binding is successful in step S624, or if it is determined that the credit card information already exists or has been bound to the user registration information in step S622, then step S625 is performed to start requesting the data verification terminal to perform identity verification. The data verification terminal performs the identity verification in steps S616 and S617 to determine that the user is a valid user and transmit a verification result to the data verification server. In step S626, the data verification server determines whether the verification is passed and then stores the data to the database. If the verification is successful, the third-party bank is authorized in step S633. On the contrary, if the verification fails, the authorization to the third-party bank is rejected in step S634. In any case, the data verification terminal can display the transaction result in step S618.
If it is determined that the aggregation data for authorization is successful bound in step S654, or if it is determined that the aggregation data for authorization already exists or has been bound to the user registration information in step S652, then step S655 is performed to start requesting the data verification terminal to perform identity verification. The data verification terminal performs the identity verification in steps S646 and S647 to determine that the user is a valid user and transmit a verification result to the data verification server. In step S656, the data verification server determines whether the verification is passed and then stores the data to the database. If the verification is successful, the third-party bank is authorized for personal data in step S663. On the contrary, if the verification fails, the authorization for personal data to the third party is rejected in step S664. In any case, the data verification terminal can display the transaction result in step S648.
In summary, one of the concepts of the present disclosure can be referenced in
The data verification system provided by the present disclosure achieves a high-security, high-reliability, and high-performance data verification process through the combination of multiple advanced technologies. With hashing algorithm and TOTP technology to encrypt biometric data, the confidentiality and integrity of the data during transmission can be ensured. At the same time, with the collaboration between the server and the terminal, fast and accurate identity verification is achieved, thus providing users with safe and reliable services.
The system of the present disclosure is not only applicable to fields requiring high security, such as finance and e-commerce, but can also be applied to emerging fields like smart cities and the Internet of Things, thus showing broad application prospects. With the continuous development of technology, the system of the present disclosure can be further optimized and improved to provide a better user experience and higher security.
Although the present disclosure has been disclosed by way of above embodiments, the embodiments are not intended to limit the present disclosure, and those skilled in the art will appreciate that changes and modifications may be made therein as long as those changes and modifications do not deviate from the spirit and the scope of the present disclosure. Therefore, the scope of the present disclosure should be construed according to the definitions in the appended claims.
The present disclosure claims the benefit of and priority to U.S. Provisional patent application Ser. No. 63/534,646, filed on Aug. 25, 2023, entitled “DIGITAL IDENTITY MANAGEMENT_SECUREID FOR PERSONAL VERIFICATION AND INTEGRATION,” the content of which is hereby incorporated herein fully by reference into the present disclosure for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 63534646 | Aug 2023 | US |