Distributed DID identity authentication parking system based on block chain
By using a blockchain-based distributed DID identity authentication parking system, which utilizes cameras and IoT edge computing modules for anonymous identity verification and selective information sharing, the system addresses the problem of insufficient user privacy protection in existing technologies and achieves efficient parking transaction security and privacy protection.
Patent Information
- Application Number
- CN202411097470.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-12
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2044-08-12
AI Technical Summary
Existing blockchain parking systems struggle to effectively protect user privacy data, and there is a risk of privacy leaks after data is uploaded to the blockchain. They also fail to achieve anonymous identity verification and selective information sharing.
The system adopts a blockchain-based distributed DID identity authentication parking system. It acquires license plate information through cameras, uses IoT edge computing modules and blockchain platform modules for anonymous identity verification and selective information sharing, and combines trusted oracle off-chain data acquisition services to enable users to autonomously control data exchange and storage.
It enables anonymous user authentication and selective information sharing, protects user privacy, reduces the abuse of personal information, improves the security of personal privacy, and ensures the credibility and immutability of parking transactions.
Smart Images

Figure CN119051925A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of blockchain, and in particular to a distributed DID identity authentication parking system based on blockchain. Background Art
[0002] With the rapid development of economy and society, the number of motor vehicles has increased rapidly. In the future, the number of motor vehicles in my country will continue to increase, and along with it will come the problem of difficulty in parking and the problem of privacy protection when parking.
[0003] At present, most of the cases and methods of applying blockchain to parking are to launch parking platforms based on blockchain, aiming to provide safer, more transparent and efficient parking services. These platforms use the immutability and smart contract functions of blockchain to realize functions such as parking lot management, payment and data recording. Blockchain technology is also used to provide new possibilities for parking lot sharing and leasing. Through smart contracts and decentralized platforms, car owners can share or lease their parking spaces to others, achieving more flexible and efficient parking resource utilization. Most applications only use blockchain as a distributed ledger, using its immutability to leave data traces and record the data required by parking merchants. However, in parking lot applications, users' privacy data needs to be protected. It is difficult for the current public chain to achieve complete protection of personal privacy data, because the data will be permanently stored on the public network after being uploaded to the chain, which may lead to the risk of privacy leakage. And even if blockchain is used, most user data is directly stored in the merchant server, and the parking business does not require so much personal information, which may cause the risk of personal information leakage. Summary of the invention
[0004] The purpose of the present invention is to overcome the shortcomings of the prior art and provide a distributed DID identity authentication parking system based on blockchain. The distributed DID parking system based on blockchain can realize anonymous identity authentication and selective information sharing. Users can use parking services without disclosing their personal identities, thereby protecting the privacy of users.
[0005] The object of the present invention is to achieve the following technical solution: a distributed DID identity authentication parking system based on blockchain, comprising: Camera, used to take photos of parked vehicles and obtain license plate information; The IoT edge computing module is used to obtain license plate information from the camera, save and update the license plate information, and provide license plate data for the blockchain platform module; Blockchain platform module, used to provide distributed DID services and trusted oracle off-chain data acquisition services; The issuer business module is used to provide a voucher template ID for the merchant and provide a voucher or selectively disclose a voucher for the user device according to information sent by the user device or the merchant business module; The user device is used to send a credential creation request and a selective credential creation request to the issuer business module, receive the credential or selective disclosure credential returned by the issuer business module for storage, and display the credential to the merchant; The merchant business module is used to send a voucher template creation request to the issuer business module, receive the voucher template ID returned by the issuer business module, and verify the voucher displayed by the user module to perform merchant business.
[0006] Furthermore, the IoT edge computing module includes: The license plate acquisition submodule is used to obtain the license plate information of the vehicle that needs to park from the camera, save it in the resource file of the API submodule, and record the license plate information and time information at the same time; the time information includes the parking time and the exit time; The API submodule, as a web server, is used to provide an API for the blockchain platform module to read license plate data.
[0007] Furthermore, the blockchain platform module includes a distributed DID service submodule and a trusted oracle off-chain data acquisition service submodule.
[0008] Further, the distributed DID service submodule includes: a DID generation functional unit, a credential template creation functional unit, a credential generation functional unit, a credential selective disclosure functional unit, and a credential verification functional unit; The DID generation functional unit is used to generate a decentralized DID number defined based on the W3C DID specification for a user, wherein the user includes a user device, a merchant business module, and an issuer business module; The voucher template creation functional unit is used to generate the corresponding template format and voucher template ID after receiving the attributes required by the voucher, and save these two pieces of information in the blockchain; The credential generation functional unit is used to first confirm whether the template ID and issuer DID are correct through the smart contract according to the template ID, the issuer's DID, and the attribute values required for the credential, and then generate the hash value of the attribute value and the corresponding signature; generate the credential using the attribute value, template ID, attribute hash value and signature; then generate the hash value of the entire credential, sign the hash value to generate a certificate, and store the certificate on the blockchain for subsequent verification; The credential selective disclosure function unit is used to parse whether the template ID and the publisher's DID in the credential are correct, and then encrypt the attribute value according to the disclosure rules, and then generate the hash value of the attribute value, and use the attribute value, template ID, attribute hash value and signature to generate the credential, and then generate the hash value of the entire credential, and sign the hash value to generate a certificate, and then store the certificate on the blockchain for subsequent verification; The credential verification functional unit is used to parse and verify the existence of the issuer DID and template ID in the credential, then verify whether the signature value is correct, and then determine whether the attribute value format is correct based on the template ID. Then, the overall hash value calculated for the credential is compared with the hash value on the chain to determine whether there is any change, and finally return a TRUE / FALSE result.
[0009] Furthermore, the trusted oracle off-chain data acquisition service submodule includes: The core functional unit of the trusted oracle is used to trigger monitoring events, read the license plate data of the API provided by the edge computing module, and write the results back to the chain; The trusted oracle client functional unit is used to call the trusted oracle core functional contract and call back the license plate matching function; The smart contract license plate matching functional unit is used to verify the credentials, parse the license plate information from the credentials, read and parse the corresponding license plate data from the API through the trusted oracle contract, and return a TRUE / FALSE result after comparison.
[0010] Furthermore, the issuer business module includes: The voucher template creation submodule is used to receive the attributes required for the voucher sent by the merchant business module, call the blockchain voucher template creation function unit, and return the voucher template id to the merchant business module; The credential creation submodule is used to receive the template ID, attribute value and issuer's DID sent by the user device, call the blockchain credential generation function unit, and return the credential to the user device; The selective credential creation submodule is used to receive the credentials and disclosure rules of the user device, call the blockchain credential selective disclosure function unit, and return the selective disclosure credential to the user device.
[0011] Furthermore, the user equipment includes: The credential request submodule is used to send a credential creation request and a selective credential creation request to the issuer business module, wherein the credential creation request includes the credential template ID number and the issuer's DID number, and the attribute value required for the credential; the selective credential creation request includes the credential and disclosure rules of the user device; A credential saving submodule is used to receive the credential returned by the issuer business module or the selective disclosure credential and save it in a custom location of the user device; The display credential submodule is used to send credentials or selectively disclose credentials to the merchant business module for the merchant to verify identity information.
[0012] Furthermore, the merchant business module includes: The registration submodule is used to provide a registration interface for the user device to log in to the merchant business platform for registration; The voucher template creation request submodule is used to send a voucher template creation request to the issuer business module. The request contains the attributes required for the voucher and receives the voucher template ID returned by the issuer business module for storage. The credential verification submodule is used to receive credentials sent by users or selectively disclose credentials, call the blockchain smart contract license plate matching function unit, and return true / false for merchants to customize submodules to perform business functions; The merchant's custom submodule is used to perform the merchant's own business after receiving the result of the verification credential submodule, such as displaying the payment code and operating the gate lift control operation at the exit after successful verification.
[0013] A distributed DID identity authentication parking method based on blockchain, comprising the following steps: S1. Blockchain node deployment: The blockchain platform module and blockchain nodes constitute the blockchain; the underlying blockchain contracts include but are not limited to the smart contracts for distributed DID services and the smart contracts for credential verification; The issuer business module deploys a blockchain node and uses the SDK in its server to connect to the underlying blockchain to obtain the smart contract address of the distributed DID service for subsequent use, and calls the distributed DID service submodule to generate a DID number; The merchant business module deploys a blockchain node and uses the SDK in its server to connect to the underlying blockchain to obtain the credential verification smart contract address for subsequent verification; S2. Merchant Registration: The merchant business module sends a voucher template creation request to the issuer business module. The request contains the attributes required for the voucher. The necessary attribute is the license plate number. Other attributes can be name, age and other information. The storage type of these attributes is String type. After the issuer business module receives the attributes required for the voucher sent by the merchant, it calls the voucher template creation function unit to generate the corresponding template format and the corresponding voucher template ID, and saves these two information in the blockchain. Then, the voucher template ID is returned to the merchant business module, and the issuer's DID number is sent to the merchant business module at the same time. The voucher template ID is 2000017, which means the 2000017th template ID. Subsequent new ones will be superimposed in sequence. The merchant business module receives the voucher template ID number and the issuer's DID number and saves them for providing the user with a registration voucher; S3. User registration: The user logs in to the merchant business platform through the user device and initiates a registration request on the merchant business platform registration interface. The merchant sends the voucher template ID number and the issuer's DID number to the user and links the user device to the issuer's business module. The user submits a voucher creation request to the issuer business platform through the user device. The request contains the voucher template ID number and the issuer's DID number, as well as the attribute values required for the voucher. The required attribute is the license plate number, and other attributes can be name, age and other information. After receiving the user's request, the issuer business module calls the credential generation function unit, which confirms whether the template ID and the issuer's DID are correct, then generates a hash value of the attribute value and generates a corresponding signature; generates a credential using the attribute value, template ID, attribute hash value and signature; then generates a hash value of the entire credential, signs the hash value to generate a certificate, and stores the certificate on the blockchain for subsequent verification; Save the credentials on the user's device; After the user receives the credential, the following steps are also included: The user device sends the credentials and disclosure rules of the user device to the issuer business module through the user device, and the disclosure rules include selecting the attribute values that need to be disclosed or hidden; the issuer business module calls the credential selective disclosure function unit to parse whether the template ID and the publisher's DID in the credential are correct, and then encrypts the attribute value according to the disclosure rules, and then generates a hash value of the attribute value, and uses the attribute value, template ID, attribute hash value and signature to generate the credential, and then generates the hash value of the entire credential, and signs the hash value to generate a certificate, and stores the certificate on the blockchain for subsequent verification; The selective disclosure credentials are then stored in the user's device; S4. User parking: The car owner drives the vehicle into the merchant parking lot. The camera recognizes the license plate information of the parked vehicle and transmits it to the edge computing module. The edge computing module records the license plate data, including the license plate information and parking time, and uploads it to the blockchain through the trusted oracle core functional unit. When the car owner drives the vehicle out of the parking lot, the camera at the exit of the parking lot recognizes the license plate information of the parked vehicle and transmits it to the edge computing module. The edge computing module records the license plate data, including the license plate information and the exit time, and uploads it to the blockchain through the trusted oracle core functional unit. At the same time, the user scans the code through the user device to link the merchant business module and sends the certificate or selective disclosure certificate to the merchant business module. After receiving the credential or selective disclosure credential, the merchant business module calls the credential verification function unit to parse and verify the existence of the issuer DID and template ID in the credential, then verifies whether the signature value is correct, and then determines whether the attribute value format is correct based on the template ID, and then compares the overall hash value calculated for the credential with the hash value on the chain to determine whether there is any change; then calls the smart contract license plate matching function unit to verify the credential, parses the license plate information from the credential, and the trusted oracle contract reads and parses the corresponding license plate data from the API and compares them. If the credential verification function unit and the smart contract license plate matching function unit are both successfully verified, a TRUE result is returned, otherwise a FALSE result is returned; When the merchant business module receives a TRUE result, it determines the parking entry time and exit time from the blockchain, then calculates the parking fee based on the preset parking unit price and displays the payment code to the user; when it receives a FALSE result, it reminds the user that the verification is incorrect.
[0014] The merchant has set up a barrier at the exit of the parking lot. After receiving a TRUE result and the user has paid, the barrier is lifted to allow the user to pass.
[0015] The beneficial effects of the present invention are: using distributed DID applications in parking systems, after users create digital identity credentials, they can completely control the exchange and storage of data by themselves, and can generate selective disclosure credentials to cover up unnecessary personal information during parking. For example, in this parking system, only the license plate is necessary information. Even if the merchant requires other identity information, the user can choose to provide it, which reduces the abuse of personal information. In addition, the license plate data off the chain is uploaded to the chain using a trusted oracle, and the closed loop of the identity authentication business is completed in the blockchain, which not only realizes the credibility and non-tamperability of the business, but also allows the user's identity information to circulate in fewer links, improving the security of personal privacy. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Figure 1 It is a schematic diagram of the principle of the present invention; Figure 2 Issuing distributed identity flow chart for issuers; Figure 3 Register a distributed identity authentication flow chart for a user. DETAILED DESCRIPTION
[0017] The technical solution of the present invention is further described in detail below in conjunction with the accompanying drawings, but the protection scope of the present invention is not limited to the following.
[0018] The system architecture diagram of the technical solution of the present invention is as follows Figure 1As shown in the figure, the main participants of the whole system are parking users, parking merchants and third-party issuers, and the blockchain module operates independently of the three parties. The system can be applied to regionally managed parking lots, such as school parking lots and comprehensive commercial parking lots. In addition to secure identity authentication, IoT devices such as cameras, recognition modules and wireless communications installed in the parking lot can collect the driver's license plate and parking time, etc. The real-world data obtained is connected to the blockchain through a trusted oracle, and the license plate information in the distributed DID is matched with the real license plate information directly in the smart contract, completing the closed loop of the parking process on the blockchain, reducing dependence on third parties, and thus reducing the possibility of privacy leakage.
[0019] First, the technical solution used in the blockchain part of the present invention is described. The present invention uses the FISCO BCOS chain as the bottom layer of the blockchain module. Its consensus mechanism adopts PBFT, with low transaction confirmation latency, high throughput, and final consistency. The two major functions of the blockchain module are distributed DID service and trusted oracle off-chain data acquisition service.
[0020] The distributed DID service includes DID generation function, credential template creation function, credential generation function, credential selective disclosure function, and credential verification function. The DID generation function provides decentralized IDs based on the W3C DID specification definition for all users. The credential template creation function declares the attributes required for the identity credential, and its declaration format is: attribute name, attribute data type, and attribute description. For example, the license plate attribute required in this parking system has a declaration format of attribute name: license plate, attribute type: String, attribute description: user's license plate number. The credential template creation contract creates different credential templates and stores the template format on the chain according to different attribute requirements, and finally outputs the template ID number for subsequent generation of identity credentials. After the credential generation function fills in the information of the corresponding attributes according to the template, the issuer of the credential enters its DID, and finally generates the credential through the smart contract. The credential as a whole will use the Keccak256 hash algorithm to generate a string of hash values and store them on the blockchain for subsequent verification. The selective disclosure function of credentials allows users to choose the attributes that need to be exposed. For example, in conventional parking systems, users are generally required to enter their license plate, name, gender, age and other personal information, but in actual parking business, only the license plate number is required, so users can create disclosure rules by themselves and choose whether to disclose personal information such as name, gender and age. If they choose not to disclose, the corresponding attribute value will be encrypted using AES. The credential verification function will analyze whether the format of the incoming credential matches its corresponding template, and determine whether its content has been tampered with based on the overall generated hash value, and finally return a verification result.
[0021] Another function of the blockchain module is to obtain license plate services from off-chain data of a trusted oracle. Because blockchain is a deterministic, closed system environment, smart contracts must produce consistent results no matter when and where they are run. Smart contracts cannot have network calls, otherwise the results will be uncertain. Therefore, the present invention uses a trusted oracle as a bridge between the off-chain and on-chain. The camera with a built-in license plate recognition function recognizes the license plate number and transmits it to the edge computing service platform. In the embodiment of the application, the edge computing service platform builds an API for the trusted oracle core contract to read current data, and designs a smart parking contract. This contract inherits the trusted oracle client contract. The client can read the license plate data from the core contract and match it with the license plate data in the identity credential sent. The parking business is completed and the transaction is archived directly in the blockchain. In this process, there is no need for parking merchants to participate. The characteristics of the blockchain are used to achieve the credibility and immutability of parking transactions. At the same time, the trusted oracle will encrypt the request, collect data signatures and verify the signatures on the chain to ensure the credibility of the off-chain data.
[0022] In the embodiment of the application, the issuer business module is similar to an authoritative issuing agency, which is used to create identity credential templates and issue credentials. Figure 2 As shown, the issuer uses the CreateID function provided by the blockchain smart contract to generate a DID stored on the chain. The issuer obtains the required identity information attributes from the parking merchant. The basic attributes set by the present invention are: name, age, gender and license plate. Among them, the license plate is a necessary attribute for the parking business, and other identity attributes can be added and deleted according to the needs of different parking merchants. After obtaining the identity information attributes required by the parking merchant, the identity credential template contract is called, and the contract uses a standard data-logic separation architecture. For an identity credential template contract, the most critical part is its jsonSchema part, which is used to store the Claim format content recorded in jsonSchema format, that is, the identity information attributes required by the parking merchant. Different templates are distinguished by the contract ID. This structural design ensures the separation of data and logic, and provides a standardized way to manage and identify different contracts. The issuer sends the generated template ID to the parking merchant for its users to register identity credentials. Among them, the identity credentials required by different parking merchants have the necessary license plate information to ensure the basic parking business, so the identity credential templates of different merchants can communicate with each other.
[0023] In the embodiments of the application, Figure 3As shown in the figure, the user will register the identity certificate of the corresponding merchant in the issuer business module. After the user fills in the required information, the issuer business module will send the identity certificate file to the user's device in an encrypted manner, and will add the issuer's DID signature to the sent certificate. The issuer business module itself does not save the identity certificate, and the generated identity certificate is kept by the user. When generating an identity certificate, a hash value signature of the entire certificate will be generated and cannot be modified. This hash value will be stored on the chain for subsequent verification of the certificate. At the same time, the user also needs to register DID and endorse the generated certificate with his own signature. Different signatures will be stored in the form of Linked-Event. In the blockchain development language Solidity, each block has a corresponding Event storage area for storing block-related events and finally storing them in the Event log. Therefore, the DID signature updates added at different times can be stored in the Event of the current block when updating, and the current block height is used as an index to record each update event. When reading, reverse search is convenient according to the index. After receiving the identity certificate, the user saves it in the device's safe place. At this time, the user can choose to use the certificate directly for parking, or choose to create a selective disclosure identity certificate in the issuer business module. The user can selectively disclose identity information except the license plate number. The user can only create a selective disclosure identity certificate once. The user will create the disclosure rules by himself. The issuer business module encrypts the corresponding identity information according to the disclosure rules and generates a new identity certificate for the user to save. The user can use the original certificate or the selective disclosure certificate for parking according to his own needs.
[0024] In the embodiment of the application, the merchant will have as little contact with the user's identity information as possible. The merchant first calls the credential verification interface of the blockchain platform module. Because the credential is based on the public key storage and digital signature of the DID to prevent the credential from being tampered with, the module will first query whether there is a corresponding template ID number, and then check whether the format of the identity credential and its corresponding template ID number matches. Finally, the credential content is verified by the signature and credential hash value. Whether it has been tampered with. If the identity credential is successfully verified, the blockchain will call the trusted oracle to obtain the license plate data captured and recognized by the real camera, and match it with the license plate information in the identity credential, return the matching result to the merchant, and save this matching process as a transaction in the blockchain as a record. The merchant performs parking fees and lifting barrier services based on the returned results. In this process, the merchant will only obtain the user's license plate data and the identity information that the user is willing to expose, which greatly protects personal privacy.
[0025] A distributed DID identity authentication parking method based on blockchain, comprising the following steps: S1. Blockchain node deployment: The blockchain platform module and blockchain nodes constitute the blockchain; the underlying blockchain contracts include but are not limited to the smart contracts for distributed DID services and the smart contracts for credential verification; The issuer business module deploys a blockchain node and uses the SDK in its server to connect to the underlying blockchain to obtain the smart contract address of the distributed DID service for subsequent use, and calls the distributed DID service submodule to generate a DID number; The merchant business module deploys a blockchain node and uses the SDK in its server to connect to the underlying blockchain to obtain the credential verification smart contract address for subsequent verification; S2. Merchant Registration: The merchant business module sends a voucher template creation request to the issuer business module. The request contains the attributes required for the voucher. The necessary attribute is the license plate number. Other attributes can be name, age and other information. The storage type of these attributes is String type. After the issuer business module receives the attributes required for the voucher sent by the merchant, it calls the voucher template creation function unit to generate the corresponding template format and the corresponding voucher template ID, and saves these two information in the blockchain. Then, the voucher template ID is returned to the merchant business module, and the issuer's DID number is sent to the merchant business module at the same time. The voucher template ID is 2000017, which means the 2000017th template ID. Subsequent new ones will be superimposed in sequence. The merchant business module receives the voucher template ID number and the issuer's DID number and saves them for providing the user with a registration voucher; S3. User registration: The user logs in to the merchant business platform through the user device and initiates a registration request on the merchant business platform registration interface. The merchant sends the voucher template ID number and the issuer's DID number to the user and links the user device to the issuer's business module. The user submits a voucher creation request to the issuer business platform through the user device. The request contains the voucher template ID number and the issuer's DID number, as well as the attribute values required for the voucher. The required attribute is the license plate number, and other attributes can be name, age and other information. After receiving the user's request, the issuer business module calls the credential generation function unit, which confirms whether the template ID and the issuer's DID are correct, then generates a hash value of the attribute value and generates a corresponding signature; generates a credential using the attribute value, template ID, attribute hash value and signature; then generates a hash value of the entire credential, signs the hash value to generate a certificate, and stores the certificate on the blockchain for subsequent verification; Save the credentials on the user's device; After the user receives the credential, the following steps are also included: The user device sends the credentials and disclosure rules of the user device to the issuer business module through the user device, and the disclosure rules include selecting the attribute values that need to be disclosed or hidden; the issuer business module calls the credential selective disclosure function unit to parse whether the template ID and the publisher's DID in the credential are correct, and then encrypts the attribute value according to the disclosure rules, and then generates a hash value of the attribute value, and uses the attribute value, template ID, attribute hash value and signature to generate the credential, and then generates the hash value of the entire credential, and signs the hash value to generate a certificate, and stores the certificate on the blockchain for subsequent verification; The selective disclosure credentials are then stored in the user's device; S4. User parking: The car owner drives the vehicle into the merchant parking lot. The camera recognizes the license plate information of the parked vehicle and transmits it to the edge computing module. The edge computing module records the license plate data, including the license plate information and parking time, and uploads it to the blockchain through the trusted oracle core functional unit. When the car owner drives the vehicle out of the parking lot, the camera at the exit of the parking lot recognizes the license plate information of the parked vehicle and transmits it to the edge computing module. The edge computing module records the license plate data, including the license plate information and the exit time, and uploads it to the blockchain through the trusted oracle core functional unit. At the same time, the user scans the code through the user device to link the merchant business module and sends the certificate or selective disclosure certificate to the merchant business module. After receiving the credential or selective disclosure credential, the merchant business module calls the credential verification function unit to parse and verify the existence of the issuer DID and template ID in the credential, then verifies whether the signature value is correct, and then determines whether the attribute value format is correct based on the template ID, and then compares the overall hash value calculated for the credential with the hash value on the chain to determine whether there is any change; then calls the smart contract license plate matching function unit to verify the credential, parses the license plate information from the credential, and the trusted oracle contract reads and parses the corresponding license plate data from the API and compares them. If the credential verification function unit and the smart contract license plate matching function unit are both successfully verified, a TRUE result is returned, otherwise a FALSE result is returned; When the merchant business module receives a TRUE result, it determines the parking entry time and exit time from the blockchain, then calculates the parking fee based on the preset parking unit price and displays the payment code to the user; when it receives a FALSE result, it reminds the user that the verification is incorrect.
[0026] The merchant has set up a barrier at the exit of the parking lot. After receiving a TRUE result and the user has paid, the barrier is lifted to allow the user to pass.
[0027] The technical solution of the present invention is described below in conjunction with specific implementation cases: Assume that the entire system is arranged in a comprehensive commercial entity. The first step is to arrange the blockchain module. The blockchain nodes are arranged in the issuer module and the parking merchant business module respectively. After the arrangement is completed, the smart contract deployed in the blockchain can be accessed. The two major functions of the blockchain module are distributed DID service and trusted oracle chain data acquisition service. Among them, the distributed DID service includes DID generation function, credential template creation function, credential generation function, credential selective disclosure function, and credential verification function. Another function is the trusted oracle chain data acquisition license plate service. The main functions used by the issuer module are DID generation function, credential template creation function, credential generation function, and credential selective disclosure function. The functions used by parking merchants are credential verification function and trusted oracle chain data acquisition license plate service.
[0028] The issuer uses the CreateID function of the blockchain smart contract to generate a decentralized identity (DID) stored on the blockchain. In order to meet the needs of parking merchants, the issuer obtains the required identity information attributes. In the implementation case, the comprehensive commercial parking merchant sets the basic attributes including name, age, gender and license plate. The license plate is a necessary attribute for parking business. Once the identity information attributes required by the parking merchant are obtained, the issuer will call the identity credential template contract and send the generated template ID to the parking merchant for its users to register the identity credential. Since the identity credentials required by different parking merchants all contain the necessary license plate information, the basic parking business can be guaranteed, so the identity credential templates between different merchants can be used interchangeably. This design ensures the interoperability of identity credentials and provides flexibility and convenience for different parking merchants. If this comprehensive commercial parking merchant also operates other parking lots, the credentials generated using this credential template can also be used. Even if it is an identity credential from another operator, as long as the credential contains license plate information, the business can still be carried out.
[0029] After parking, users need to register distributed DID and identity credentials. Users will register the identity credentials of the commercial parking merchant in the issuer's business module. After the user fills in the required information, the issuer's business module will send the identity credential file to the user's device in an encrypted manner and add the issuer's DID signature to the credential. The issuer's business module does not save the identity credentials itself, but the generated identity credentials are kept by the user. After receiving the identity credentials, the user saves them in the secure storage space of the device. At this time, the user can choose to use the credentials directly for parking, or choose to create a selectively disclosed identity credential in the issuer's business module. For selectively disclosed credentials, users can selectively disclose identity information other than the license plate number. Users can only create a selectively disclosed identity credential once and formulate disclosure rules according to their own needs. The issuer's business module encrypts the corresponding identity information according to the disclosure rules and generates a new identity credential for the user to save. Users can choose to use native credentials or selectively disclosed credentials for parking services according to their own needs. This flexible identity credential mechanism enables users to make choices based on specific circumstances and privacy needs, and ensures that users' personal information is protected. When the user needs to exit the parking lot, he scans the QR code arranged by the parking merchant at the exit, opens the business system arranged by the merchant, and sends the identity credentials in his device to the merchant for the merchant to settle the parking business.
[0030] In the specific implementation, in order to meet the needs of the parking merchants in the integrated commercial complex, they need to deploy the smart parking edge service platform and cameras equipped with license plate recognition functions at the entrances and exits of the parking lot. Once the camera recognizes the license plate number, the information will be transmitted to the edge computing service platform. To achieve this goal, the edge computing service platform builds an API for the trusted oracle core contract to read real-time data. In addition, a smart parking contract is designed, which inherits the functions of the trusted oracle client contract. Through the client, the license plate data can be read from the core contract and matched with the license plate data in the received identity certificate. With these technologies, parking services can be completed and transactions can be archived directly on the blockchain without the participation of parking merchants. The characteristics of the blockchain ensure the credibility and immutability of parking transactions. Throughout the process, the trusted oracle will encrypt the request, collect data signatures and on-chain signature verification, thereby ensuring the credibility of the off-chain data. This solution that integrates the smart parking edge service platform, cameras, edge computing service platform, and trusted oracles provides an efficient, secure, and reliable parking business management system for integrated commercial parking merchants. Merchants post QR codes at the exit for users to log in to the parking business interface. The parking business interface requires users to send their credentials. After receiving the user's credentials, the merchant first verifies the identity credentials by calling the credential verification interface of the blockchain platform module. These credentials are stored based on the public key of the DID and use digital signatures to prevent the credentials from being tampered with. During the verification process, the module first queries whether the corresponding template ID number exists and checks whether the format of the identity credential matches that of the template ID number. Next, the signature and hash value of the credential are verified to ensure that the credential content has not been tampered with. Once the identity credential is successfully verified, the blockchain system calls a trusted oracle to obtain the license plate data captured and recognized by the actual camera. By comparing the recognized license plate information with the license plate information in the identity credential, the blockchain system returns the matching result to the merchant. At the same time, this matching process will be recorded and saved on the blockchain as a record of a transaction. The merchant performs related business operations such as parking fees and lifting barriers based on the returned results. This process ensures that the merchant verifies the identity credential and uses a trusted oracle to obtain real-time camera recognition data to ensure the accuracy of the license plate information. At the same time, all transaction records are permanently stored on the blockchain, providing traceability and trustworthiness. This blockchain-based credential verification and parking business process provides merchants with safe, efficient and reliable services.
[0031] The above is a preferred embodiment of the present invention. It should be understood that the present invention is not limited to the form disclosed herein, and should not be regarded as excluding other embodiments, but can be used in other combinations, modifications and environments, and can be modified within the scope of the concept described herein through the above teachings or the technology or knowledge of the relevant field. The changes and modifications made by those skilled in the art do not depart from the spirit and scope of the present invention, and should be within the scope of protection of the claims attached to the present invention.
Claims
1. A distributed DID identity authentication parking system based on blockchain, Features: include: Camera, used to take photos of parked vehicles and obtain license plate information; The IoT edge computing module is used to obtain license plate information from the camera, save and update the license plate information, and provide license plate data for the blockchain platform module; Blockchain platform module, used to provide distributed DID services and trusted oracle off-chain data acquisition services; The issuer business module is used to provide a voucher template ID for the merchant and provide a voucher or selectively disclose a voucher for the user device according to information sent by the user device or the merchant business module; The user device is used to send a credential creation request and a selective credential creation request to the issuer business module, receive the credential or selective disclosure credential returned by the issuer business module for storage, and display the credential to the merchant; The merchant business module is used to send a voucher template creation request to the issuer business module, receive the voucher template ID returned by the issuer business module, and verify the voucher displayed by the user module to perform merchant business.
2. According to claim 1, a distributed DID identity authentication parking system based on blockchain, Features: The IoT edge computing module includes: The license plate acquisition submodule is used to obtain the license plate information of the vehicle that needs to park from the camera, save it in the resource file of the API submodule, and record the license plate information and time information at the same time; the time information includes the parking time and the exit time; The API submodule, as a web server, is used to provide an API for the blockchain platform module to read license plate data.
3. According to claim 1, a distributed DID identity authentication parking system based on blockchain, Features: The blockchain platform module includes a distributed DID service submodule and a trusted oracle off-chain data acquisition service submodule.
4. According to claim 3, a distributed DID identity authentication parking system based on blockchain, Features: The distributed DID service submodule includes: a DID generation functional unit, a credential template creation functional unit, a credential generation functional unit, a credential selective disclosure functional unit, and a credential verification functional unit; The DID generation functional unit is used to generate a decentralized DID number for a user, wherein the user includes a user device, a merchant business module, and an issuer business module; The voucher template creation functional unit is used to generate the corresponding template format and voucher template ID after receiving the attributes required by the voucher, and save these two pieces of information in the blockchain; The credential generation functional unit is used to first confirm whether the template ID and issuer DID are correct through the smart contract according to the template ID, the issuer's DID, and the attribute values required for the credential, and then generate the hash value of the attribute value and the corresponding signature; generate the credential using the attribute value, template ID, attribute hash value and signature; then generate the hash value of the entire credential, sign the hash value to generate a certificate, and store the certificate on the blockchain for subsequent verification; The credential selective disclosure function unit is used to parse whether the template ID and the publisher's DID in the credential are correct, and then encrypt the attribute value according to the disclosure rules, and then generate the hash value of the attribute value, and use the attribute value, template ID, attribute hash value and signature to generate the credential, and then generate the hash value of the entire credential, and sign the hash value to generate a certificate, and then store the certificate on the blockchain for subsequent verification; The credential verification functional unit is used to parse and verify the existence of the issuer DID and template ID in the credential, then verify whether the signature value is correct, and then determine whether the attribute value format is correct based on the template ID. Then, the overall hash value calculated for the credential is compared with the hash value on the chain to determine whether there is any change, and finally return a TRUE / FALSE result.
5. According to claim 3, a distributed DID identity authentication parking system based on blockchain, Features: The trusted oracle off-chain data acquisition service submodule includes: The core functional unit of the trusted oracle is used to trigger monitoring events, read the license plate data of the API provided by the edge computing module, and write the results back to the chain; The trusted oracle client functional unit is used to call the trusted oracle core functional contract and call back the license plate matching function; The smart contract license plate matching functional unit is used to verify the credentials, parse the license plate information from the credentials, read and parse the corresponding license plate data from the API through the trusted oracle contract, and return a TRUE / FALSE result after comparison.
6. A distributed DID identity authentication parking system based on blockchain according to claim 1, Features: The issuer business module includes: The voucher template creation submodule is used to receive the attributes required for the voucher sent by the merchant business module, call the blockchain voucher template creation function unit, and return the voucher template id to the merchant business module; The credential creation submodule is used to receive the template ID, attribute value and issuer's DID sent by the user device, call the blockchain credential generation function unit, and return the credential to the user device; The selective credential creation submodule is used to receive the credentials and disclosure rules of the user device, call the blockchain credential selective disclosure function unit, and return the selective disclosure credential to the user device.
7. According to claim 1, a distributed DID identity authentication parking system based on blockchain, Features: The user equipment comprises: The credential request submodule is used to send a credential creation request and a selective credential creation request to the issuer business module, wherein the credential creation request includes the credential template ID number and the issuer's DID number, and the attribute value required for the credential; the selective credential creation request includes the credential and disclosure rules of the user device; A credential saving submodule is used to receive the credential returned by the issuer business module or the selective disclosure credential and save it in a custom location of the user device; The display credential submodule is used to send credentials or selectively disclose credentials to the merchant business module for the merchant to verify identity information.
8. According to claim 1, a distributed DID identity authentication parking system based on blockchain, Features: The merchant business module includes: The registration submodule is used to provide a registration interface for the user device to log in to the merchant business platform for registration; The voucher template creation request submodule is used to send a voucher template creation request to the issuer business module. The request contains the attributes required for the voucher and receives the voucher template ID returned by the issuer business module for storage. The credential verification submodule is used to receive credentials sent by users or selectively disclose credentials, call the blockchain smart contract license plate matching function unit, and return true / false for merchants to customize submodules to perform business functions; The merchant's custom submodule is used to perform the merchant's own business after receiving the result of the verification credential submodule, such as displaying the payment code and operating the gate lift control operation at the exit after successful verification.
9. A distributed DID identity authentication parking method based on blockchain, based on the system described in any one of claims 1 to 8, Features: The following steps are involved: S1. Blockchain node deployment: The blockchain platform module and blockchain nodes constitute the blockchain; The issuer business module deploys a blockchain node and uses the SDK in its server to connect to the underlying blockchain to obtain the smart contract address of the distributed DID service for subsequent use, and calls the distributed DID service submodule to generate a DID number; The merchant business module deploys a blockchain node and uses the SDK in its server to connect to the underlying blockchain to obtain the credential verification smart contract address for subsequent verification; S2. Merchant Registration: The merchant business module sends a voucher template creation request to the issuer business module. The request contains the attributes required for the voucher. After receiving the attributes required for the voucher sent by the merchant, the issuer business module calls the voucher template creation function unit to generate the corresponding template format and the corresponding voucher template ID, and saves these two pieces of information in the blockchain. Then, the voucher template ID is returned to the merchant business module, and the issuer's DID number is sent to the merchant business module at the same time; The merchant business module receives the voucher template ID number and the issuer's DID number and saves them for providing the user with a registration voucher; S3. User registration: The user logs in to the merchant business platform through the user device and initiates a registration request on the merchant business platform registration interface. The merchant sends the voucher template ID number and the issuer's DID number to the user and links the user device to the issuer's business module. The user submits a credential creation request to the issuer's business platform through the user device. The request contains the credential template ID number and the issuer's DID number, as well as the attribute values required for the credential; After receiving the user's request, the issuer business module calls the credential generation function unit, which confirms whether the template ID and the issuer's DID are correct, then generates a hash value of the attribute value and generates a corresponding signature; generates a credential using the attribute value, template ID, attribute hash value and signature; then generates a hash value of the entire credential, signs the hash value to generate a certificate, and stores the certificate on the blockchain for subsequent verification; Save the credentials on the user's device; After the user receives the credential, the following steps are also included: The user device sends the credentials and disclosure rules of the user device to the issuer business module through the user device, and the disclosure rules include selecting the attribute values that need to be disclosed or hidden; the issuer business module calls the credential selective disclosure function unit to parse whether the template ID and the publisher's DID in the credential are correct, and then encrypts the attribute value according to the disclosure rules, and then generates a hash value of the attribute value, and uses the attribute value, template ID, attribute hash value and signature to generate the credential, and then generates the hash value of the entire credential, and signs the hash value to generate a certificate, and stores the certificate on the blockchain for subsequent verification; The selective disclosure credentials are then stored in the user's device; S4. User parking: The car owner drives the vehicle into the merchant parking lot. The camera recognizes the license plate information of the parked vehicle and transmits it to the edge computing module. The edge computing module records the license plate data, including the license plate information and parking time, and uploads it to the blockchain through the trusted oracle core functional unit. When the car owner drives the vehicle out of the parking lot, the camera at the exit of the parking lot recognizes the license plate information of the parked vehicle and transmits it to the edge computing module. The edge computing module records the license plate data, including the license plate information and the exit time, and uploads it to the blockchain through the trusted oracle core functional unit. At the same time, the user scans the code through the user device to link the merchant business module and sends the certificate or selective disclosure certificate to the merchant business module. After receiving the credential or selective disclosure credential, the merchant business module calls the credential verification function unit to parse and verify the existence of the issuer DID and template ID in the credential, then verifies whether the signature value is correct, and then determines whether the attribute value format is correct based on the template ID, and then compares the overall hash value calculated for the credential with the hash value on the chain to determine whether there is any change; then calls the smart contract license plate matching function unit to verify the credential, parses the license plate information from the credential, and the trusted oracle contract reads and parses the corresponding license plate data from the API and compares them. If the credential verification function unit and the smart contract license plate matching function unit are both successfully verified, a TRUE result is returned, otherwise a FALSE result is returned; The merchant business module, upon receiving the TRUE result, determines the parking entry time and exit time from the blockchain, then calculates the parking fee based on the preset parking unit price, and displays the payment code to the user; Upon receiving a FALSE result, the user is alerted that the validation was incorrect.
10. According to the distributed DID identity authentication parking method based on blockchain as described in claim 9, Features: The merchant has set up a barrier at the exit of the parking lot. After receiving a TRUE result and the user has paid, the barrier is lifted to allow the user to pass.
Citation Information
Patent Citations
Identity authentication method based on block chain
CN110798483A
Block chain zero-knowledge proving anonymous certificate verification method and system based on DID identity
CN113037493A
Trusted distributed identity authentication method and system, storage medium and application
CN113098838A
Variable electrode for electropolishing inside pipes
KR1020230125735A
