Cross-medical domain identity authentication method based on alliance chain

Through the cross-medical domain identity authentication method based on alliance chain, the cross-regional medical data interoperability and PKI single point failure problems are solved, trust between hospitals and sharing of medical big data, reducing duplicate examinations, and improving diagnostic accuracy and data access efficiency.

CN119071040APending Publication Date: 2024-12-03YUNNAN UNIVERSITY OF FINANCE AND ECONOMICS

Patent Information

Application Number
CN202411105109.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-13
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In cross-regional and cross-institutional medical scenarios, interoperability of patient medical record information leads to repeated examinations, and the traditional PKI system has a single point of failure risk, making it difficult to achieve trust between hospitals and sharing of medical big data.

Method used

Adopt cross-medical domain identity authentication method based on alliance chain, combined with decentralized features, design lightweight block structure, index query mechanism and certificate revocation module to realize effective sharing and efficient query of cross-medical domain certificates, and reduce storage and query Overhead.

Benefits of technology

It solves the single point of failure problem in the PKI system, promotes the trust of different hospitals and the sharing of medical big data, reduces repeated examinations of patients, and improves the accuracy of doctors' diagnosis and data access efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071040A_ABST
    Figure CN119071040A_ABST
Patent Text Reader

Abstract

The invention provides a cross-medical domain identity authentication method based on an alliance chain aiming at the problem of medical big data island. According to the method, an identity authentication model (CMDIA) is adopted, the decentralization characteristic of an alliance chain is utilized, the common single-point fault problem in a public key infrastructure (PKI) system is effectively avoided, and trust establishment among different medical domains is promoted. According to the method, a more lightweight block structure is designed, a cross-medical domain authentication certificate is designed, the query efficiency of data on a chain is improved, the cross-mechanism authentication experience of a user is improved, and an efficient index query mechanism based on the block height is designed. Besides, the authentication protocol covers intra-domain registration, intra-domain authentication and cross-domain authentication, so that doctors can access patient data of other medical domains, and privacy of doctor information is protected. The CMDIA model is excellent in calculation overhead, query efficiency, response time and throughput, and an efficient and safe solution is provided for sharing of medical big data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a cross-domain data identity authentication method, and specifically to a cross-medical domain identity authentication method based on an alliance chain. Background Art

[0002] In modern society, the use of many online medical service tools such as medical digitization, telemedicine, electronic medical record systems, and online registration platforms has improved patients' medical experience and improved the medical efficiency of hospitals. However, with the explosive growth of medical big data, the problem of "medical big data islands" has become increasingly apparent. In particular, in cross-regional and cross-institutional medical scenarios, the interoperability of patient medical record information has become a major problem. When patients are transferred between different hospitals, they are often required to repeat the examinations they have already done before, resulting in a huge waste of medical resources. Doctors can only access the medical data of their own hospital and cannot access the data of other hospitals across medical domains. Solving the problem of interoperability of patient information between hospitals and promoting the sharing of medical big data can not only reduce patients' repeated examinations, but also allow doctors to access more past case information of patients, which helps to improve the accuracy of doctors' diagnoses. It can also promote medical research, better conduct public health monitoring and control, and promote the education and training of medical students.

[0003] Cross-domain authentication technology in identity authentication is expected to be a solution to the above problems. If a user wants to access certain resources, the user needs to be authenticated to confirm whether the user is qualified to access the resources. This is identity authentication. Currently, most identity authentication technologies use public key infrastructure (PKI) technology, which issues certificates to user entities through CA and provides identity authentication services. However, this design has security risks, the most serious of which is the inevitable single point failure of the centralized system. The traditional PKI system has a tree structure, and the root of the tree is the root CA of each trust domain. Once the root CA is attacked and fails, the entire trust domain will be seriously affected, so the PKI system is prone to single point failure problems.

[0004] Cross-domain authentication is a technology in identity authentication that can break information silos. This technology allows users to access resources in other trust domains, providing users with one-time login and convenient services across the entire network, referred to as single sign-on. A trust domain is an organization, such as a company, a hospital, etc. In this technology, a hospital is called a medical domain. However, CAs in different trust domains naturally lack trust relationships, which hinders cross-domain authentication.

[0005] Blockchain technology has the characteristics of decentralization, data traceability, and tamper-proof, and can establish trust in an untrusted environment. Blockchain can be divided into public chain, private chain, and alliance chain. The alliance chain is a blockchain composed of multiple organizations. Similar to the cross-domain authentication scenario, there are multiple nodes in the alliance chain that store distributed ledgers. Each node must be authorized to join the alliance chain, which solves the trust problem of CAs in different trust domains in the alliance chain. Compared with the public chain, the alliance chain has faster transaction speeds, better protection of user privacy, decentralization, and non-tamperability. While solving the risk of single point failure in the PKI system, it can promote mutual trust among different hospitals, which also provides a prerequisite for sharing medical big data between hospitals. Summary of the invention

[0006] In order to solve the problem of difficulty in sharing medical big data, the present invention proposes that the purpose of the present invention is to provide a cross-medical domain identity authentication method based on alliance chain, and establish a (Cross-medical domain identity authentication model based on alliance chain) model, which is recorded as CMDIA model. The decentralized characteristics of the alliance chain are utilized to solve the problems of CA single point failure in cross-domain authentication and CA difficulty in mutual trust in different trust domains. The cross-medical domain identity authentication model (CMDIA) based on the alliance chain combines the alliance chain with the cross-domain authentication technology and is used in the scenario of sharing medical big data, so that doctors in one hospital can access the medical data of other hospitals across medical domains. Since the alliance chain has the characteristics of decentralization and non-tamperability, it can promote mutual trust among different hospitals while solving the risk of single point failure in the PKI system, which also provides a premise for sharing medical big data between hospitals. In this model, we designed a cross-medical domain certificate adapted to the model for cross-medical domain identity authentication. We have improved the block to make the block more lightweight, which can reduce the overhead of storing the block. In order to reduce the query time overhead of the alliance chain, an index query mechanism is designed. In this model, a fast and efficient certificate revocation mechanism is designed to revoke expired certificates.

[0007] To achieve the above object, the present invention provides the following technical solution including the following contents:

[0008] A cross-medical domain identity authentication method based on alliance chain consists of the following parts:

[0009] Cross-medical domain identity authentication model based on alliance chain CMDIA model, alliance chain, cross-medical domain authentication certificate, certificate revocation module, index query mechanism module, cross-medical domain authentication protocol based on alliance chain;

[0010] The CMDIA model includes multiple medical domains, and each medical domain includes a certificate authority CA, an authentication server AS, and a doctor DO. As a user in each medical domain, the doctor DO can register and authenticate within each medical domain. After completing the authentication within the medical domain, the medical big data within the medical domain can be accessed. Only after the authentication within the medical domain can cross-medical domain authentication be performed. After the cross-medical domain authentication is successful, the medical big data in other medical domains can be accessed. Therefore, it can reduce unnecessary repeated examinations for patients after referral to different hospitals.

[0011] The alliance chain is composed of multiple block structures, and the Raft consensus algorithm is used to make the nodes in the alliance chain reach data consistency. The block height is added to the block header of the block structure;

[0012] The cross-medical domain authentication certificate includes the block height;

[0013] The certificate revocation module includes a certificate revocation table, which records the block height and the hash value stored in the block corresponding to the block height;

[0014] The index query mechanism module first finds the block with the corresponding block height, and then searches for the corresponding hash value in the block;

[0015] The cross-medical domain authentication protocol based on the alliance chain includes: a medical domain registration protocol, a medical domain authentication protocol and a cross-medical domain authentication protocol;

[0016] The protocol works as follows:

[0017] Step-1: Doctor DO submits his information to the authentication server AS. AS first verifies DO's information. If the verification is successful, AS generates a public-private key pair for DO and sends the public-private key pair to DO.

[0018] Step-2: AS sends a certificate application message to the certificate authority CA, which includes DO's information and DO's public key; CA generates a cross-medical domain certificate for DO; CA signs the certificate with its own private key, then takes the hash value of the certificate and stores it on the alliance chain, and sends the hash value of the certificate to AS and the certificate to DO, so that DO completes the registration;

[0019] Step-3: DO sends an authentication request to AS. AS sends a random number N1 to DO. DO uses its own private key to sign Sign-DO(N1), takes a value N2 that is the same as N1, and sends Sign-DO(N1), N2, and the certificate to AS. AS first checks whether the certificate is valid. If the certificate has expired, it returns authentication failure and does not proceed to the following steps. AS calculates the certificate hash value and queries the certificate revocation list. If the certificate has been revoked, it returns authentication failure. AS uses the CA's public key to verify the signature of the certificate. If the verification fails, it returns authentication failure. If the verification passes, it goes to Step-4.

[0020] Step-4: Verify whether N2 is equal to N1. If N2 is not equal to N1, return authentication failure. Use the public key on the certificate to verify Sign-DO (N1). If the verification passes, proceed to Step-5. If the verification fails, return authentication failure.

[0021] Step-5: AS takes the block height from the certificate and sends the block height and certificate hash value to CA. CA queries the hash value on the chain based on the index query mechanism. If the same hash value is found, the query result is returned to AS. AS returns the authentication success or failure message to DO based on the query result. After the DO is successfully authenticated, it can access the medical data in this medical domain.

[0022] Step-6: When DO accesses data from other medical domains across domains, DO must first be authenticated within the domain before it can be authenticated across medical domains. B Send authentication request, AS B Send the random number M1 to DO, DO uses its own private key to sign M1 to get Sign-DO(M1), takes a value M2 equal to M1, and then sends Sign-DO(M1), M2 and its own certificate to AS B , A.S. B Check whether the certificate is within the validity period; if it is within the validity period, query the certificate revocation list. If the certificate has not been revoked, proceed to Step-7;

[0023] Step-7:AS B Use CA's public key to verify the signature of the certificate. If the verification is successful, verify whether M2 is equal to M1. If they are equal, use DO's public key to verify the signature of the random number M1. If the verification is successful, send the block height and hash value of the certificate to CA. B Perform an on-chain query. If the hash value of the certificate can be found in the alliance chain, the authentication is successful, thus completing the cross-medical domain identity authentication.

[0024] Preferably, the CA joins the alliance chain after being authorized, and as a node in the alliance chain, participates in packaging and consensus blocks and stores the alliance chain.

[0025] Compared with the prior art, the present invention has the following beneficial effects:

[0026] 1. A CMDIA model is proposed. The alliance chain technology is combined with the cross-domain authentication technology to realize the sharing of medical big data. A lightweight block structure, a cross-domain authentication certificate based on the improved X.509v3 version of the public key certificate, an efficient certificate revocation mechanism, and an index query mechanism based on the block height are designed.

[0027] 2. Design a complete set of protocols to implement the cross-medical domain identity authentication process. Including the complete process of intra-domain registration, intra-domain authentication, and cross-medical domain authentication. It can well solve the doctor's cross-medical domain authentication needs to achieve the purpose of accessing medical data in other medical domains.

[0028] 3. The proposed CMDIA model is superior to ordinary queries in query speed, response time and throughput, and can realize efficient on-chain query. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 CHDIA model diagram

[0030] Figure 2 To improve the blockchain structure diagram

[0031] Figure 3 Cross-medical domain certification DETAILED DESCRIPTION

[0032] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0033] CMDIA Model

[0034] In the CMDIA model, each medical domain is equipped with a certificate authority CA, an authentication server AS, and a doctor DO. The CA of each medical domain joins the alliance chain after being authorized, and as a node in the alliance chain, participates in packaging and consensus blocks and stores the alliance chain. After the CA generates a certificate for the user, it stores the hash value of the certificate in the alliance chain for subsequent in-domain identity authentication and cross-domain authentication. The authentication server AS is used to authenticate doctors in this medical domain and to perform cross-domain authentication for doctors in other medical domains. The overall model is shown in the figure below. Figure 1 shown.

[0035] In this invention, the block structure in the alliance chain is redesigned to make the block more lightweight. Figure 2 As shown, the left side is the ordinary block structure, and the right side is the improved block structure. The block contains two parts: the block header and the block body. In the block structure on the left, the block header mainly includes the version number, the hash value of the previous block, the timestamp, the random number, the target hash value, and the Merkle root. Among them, the random number and the target hash value are related to the PoW consensus algorithm, and the consensus algorithm used in the present invention is Raft. Since the index query mechanism is used in the present invention, it is necessary to query in conjunction with the block height when querying the blockchain, so the block height is increased in the block header of the newly designed block structure. The improved block is more lightweight, and the memory occupied can be reduced when the block is stored on the CA of each medical domain, thereby improving the blockchain data storage rate. In our model, the plaintext of the certificate is not directly stored in the block, but the hash value is stored in the block after the certificate is hashed, so that the information of the certificate can be protected from being leaked.

[0036] Raft consensus algorithm

[0037] How to make the distributed nodes in the blockchain reach a consensus on the block data is an important aspect in designing a cross-domain authentication solution based on the blockchain. In the present invention, the Raft consensus algorithm suitable for the alliance chain is selected to make the nodes in the alliance chain reach a consensus on the data.

[0038] In the Raft consensus algorithm, CAs in different medical domains are divided into three roles: leader, follower, and candidate. The leader CA assembles data within a period of time into blocks and publishes them to the network for consensus by CAs as the masses. Only when it is necessary to elect a leader will the identity of CAs in each medical domain become a candidate. If the mass CA does not receive a message from the CA within a period of time and its own random election time times out, it will automatically become a candidate and request other CAs to vote for itself. The one who receives more than half of the votes will become the leader and be responsible for assembling data into blocks and publishing them to the alliance chain network.

[0039] Cross-medical domain certification

[0040] We designed a cross-medical domain authentication certificate based on the X.509v3 version of the public key certificate, such as Figure 3As shown. This certificate can be used for identity authentication in this medical domain, and can also be used for cross-medical domain identity authentication. In the entries in the certificate, the serial number is the number given to each certificate by the issuer. When the CA in each medical domain issues a certificate to a doctor in this medical domain, it will sign the certificate. The certificate signing algorithm is the algorithm used by the CA to sign the certificate. After the CA signs the certificate, it indicates that the certificate is issued by the signing CA, because the signature is non-repudiation, and because the CA serving as the certificate issuing authority is set up by this hospital, it is completely trustworthy, which can ensure the authenticity of the certificate. We also added the block height to the certificate to record the height of the block where this certificate is stored in the alliance chain, which facilitates index queries when querying certificates, can greatly improve query efficiency, and reduce CA query overhead.

[0041] Certificate Revocation Module

[0042] Table 1 Certificate Revocation List

[0043]

[0044] In each medical domain, in addition to issuing certificates to doctors, it is also necessary to revoke expired certificates. For example, if a doctor leaves the medical domain, the doctor's certificate must be revoked. In our model, the hash value of the certificate is stored in the block. Because the data on the alliance chain is tamper-proof and cannot be changed once it is on the chain, certificate revocation cannot be queried by deleting the data on the chain, so we designed a convenient certificate revocation solution.

[0045] In each medical domain's AS, a certificate revocation list is maintained. The structure of the certificate revocation list is shown in Table 1. The certificate revocation list includes the block height and the hash value stored in the block corresponding to the block height. When a doctor's certificate is to be revoked, the hash value of the revoked certificate is marked on the row corresponding to the block height in the certificate, thus achieving the purpose of certificate revocation. The certificate revocation list stores a hash value stored in a block in one row. When a certificate in each medical domain is revoked, the CA in this medical domain will broadcast the certificate revocation message to the CAs in other medical domains to ensure the consistency of the certificate revocation lists in all medical domains.

[0046] Index query mechanism

[0047] Because the blockchain is a one-way linked list structure, and the alliance chain is also a one-way linked list structure, data can only be queried sequentially on the alliance, that is, one block is compared and queried one by one. If there is no data we are queried, the next block is queried. This query speed is very slow, so we designed an index query mechanism. Before querying, check whether the certificate is within the validity period. If it is within the validity period, first find the value of the block height in the certificate, and then query the row corresponding to the block height in the certificate revocation table to see if the certificate has been revoked. If it has not been revoked, query on the alliance chain based on the block height and hash value. When querying on the chain, first find the block with the corresponding block height, and then find the corresponding hash value in the block. This can avoid searching one block at a time and improve query efficiency.

[0048] Cross-medical domain authentication protocol based on alliance chain

[0049] In the present invention, a cross-medical domain identity authentication protocol is designed based on the CMDIA model, block structure, cross-medical domain authentication certificate, certificate revocation scheme, and index query mechanism in the previous section. It includes two parts: the registration protocol within the medical domain, the authentication protocol within the medical domain, and the cross-medical domain authentication protocol. First, the symbols used in the cross-medical domain authentication protocol are defined in Table 2.

[0050] Table 2 Symbol definitions in the cross-medical domain authentication protocol

[0051]

[0052] Medical Domain Registration Agreement

[0053] Every doctor in a medical domain needs to register in this medical domain. Taking hospital A as an example, doctor DO A1 To the authentication server AS of this medical domain A Submit your information, AS A First check DO A1 If the information is verified, AS A For DO A1 Generate a public-private key pair and send it to DO A1 .AS A To the CA in this medical domain A Send a certificate request message, which includes DO A1 Information and DO A1 The public key of the CA A For DO A1 Generate a cross-medical domain certificate, which can be used not only within the current medical domain, but also for cross-medical domain identity authentication. A The certificate is signed with its own private key to indicate that the certificate is a CA AThe CA can also issue the certificate to prove its authenticity. A Take the hash value of the certificate, store it on the chain, and send the hash value of the certificate to AS A Finally, send the certificate to DO A1 . A1 The registration in this medical domain is completed. The registration in the medical domain can be described by the following algorithm:

[0054] Table 3. Algorithm description of the registration process in the medical domain

[0055]

[0056] Medical Domain Authentication Protocol

[0057] When DO A1 If you want to obtain resources within this medical domain, you need to first perform domain identity authentication and pass the authentication before you can access the resources. A1 Send authentication request to AS A , A.S. A Send random number N1 to DO A1 , DO A1 Use your own private key to sign and get Sign-DO A1 (N1), DO A1 Take a value N2 equal to N1 and set Sign-DO A1 (N1), N2 and the certificate are sent to AS A .AS A First check whether the certificate is valid. If the certificate has expired, the authentication fails and the following steps are not performed. A Calculate the certificate hash value and query the certificate revocation list. If the certificate has been revoked, the authentication failure is returned. A Using CA A The public key on the certificate is used to verify the signature of the certificate. If the verification fails, the authentication failure is returned. If the verification passes, N2 is compared with N1 to see if they are equal. If they are equal, the public key on the certificate is used to verify the signature of the certificate. A1 (N1) Verify the signature. If the verification fails, the authentication fails. A Take the block height from the certificate and send the block height and certificate hash value to the CA A , C.A. A The hash value on the chain is queried according to the index query mechanism. If the same hash value is found, it is returned to the AS. A Query results, AS A Give DO according to the query results A1 Returns authentication success or failure message. A1After successful authentication, the medical data in this medical domain can be accessed. The authentication process in the medical domain is shown in Table 4 according to the algorithm flow.

[0058] Table 4 Description of authentication algorithms in the medical domain

[0059]

[0060] Cross-medical domain authentication protocol

[0061] If multiple medical domains form a medical domain alliance that can share medical big data, and the CA in each medical domain A Together they form a consortium chain, and nodes in the consortium can only join with permission, so the CAs that make up the consortium chain A Trust each other. When DO A1 To access the medical data of hospital B across medical domains, DO A1 You must first complete the intra-domain authentication before you can perform cross-domain authentication. A1 To AS B Send authentication request, AS B Send random number M1 to DO A1 ,DO A1 Use your own private key to sign M1 to get Sign-DO A1 (M1), then take a value M2 equal to M1, and sign-DO A1 (M1), M2 and their own certificates are sent to AS B , A.S. B Check whether the certificate is within the validity period. If it is within the validity period, query the certificate revocation list. If the certificate has not been revoked, perform the following verification. B Compare M2 and M1 to see if they are equal. If they are equal, use CA A The public key of the certificate is used to verify the signature. If the verification passes, DO A1 The public key verifies the signature of the random number M1. If the verification is successful, the block height of the certificate and the hash value of the certificate are sent to the CA. B Perform an on-chain query. If the hash value of the certificate can be found in the alliance chain, the authentication is successful. The algorithm description of cross-medical domain identity authentication is shown in Table 5.

[0062] Table 5 Description of cross-medical domain authentication algorithm

[0063]

[0064]

Claims

1. A cross-medical domain identity authentication method based on alliance chain consists of the following parts: Cross-medical domain identity authentication model based on alliance chain CMDIA model, alliance chain, cross-medical domain authentication certificate, certificate revocation module, index query mechanism module, cross-medical domain authentication protocol based on alliance chain; The CMDIA model includes multiple medical domains, each of which includes a certificate authority CA, an authentication server AS, and a doctor DO; The alliance chain is composed of multiple block structures, and the Raft consensus algorithm is used to make the nodes in the alliance chain reach data consistency. The block height is added to the block header of the block structure; The cross-medical domain authentication certificate includes the block height; The certificate revocation module includes a certificate revocation table, which records the block height and the hash value stored in the block corresponding to the block height; The index query mechanism module first finds the block with the corresponding block height, and then searches for the corresponding hash value in the block; The cross-medical domain authentication protocol based on the alliance chain includes: a medical domain registration protocol, a medical domain authentication protocol and a cross-medical domain authentication protocol; The protocol works as follows: Step-1: Doctor DO submits his information to the authentication server AS. AS first verifies DO's information. If the verification is successful, AS generates a public-private key pair for DO and sends the public-private key pair to DO. Step-2: AS sends a certificate application message to the certificate authority CA, which includes DO's information and DO's public key; CA generates a cross-medical domain certificate for DO; CA signs the certificate with its own private key, then takes the hash value of the certificate and stores it on the alliance chain, and sends the hash value of the certificate to AS and the certificate to DO, so that DO completes the registration; Step-3: DO sends an authentication request to AS. AS sends a random number N1 to DO. DO uses its own private key to sign Sign-DO(N1), takes a value N2 that is the same as N1, and sends Sign-DO(N1), N2, and the certificate to AS. AS first checks whether the certificate is valid. If the certificate has expired, it returns authentication failure and does not proceed to the following steps. AS calculates the certificate hash value and queries the certificate revocation list. If the certificate has been revoked, it returns authentication failure. AS uses the CA's public key to verify the signature of the certificate. If the verification fails, it returns authentication failure. If the verification passes, it goes to Step-4. Step-4: Verify whether N2 is equal to N1. If N2 is not equal to N1, return authentication failure. Use the public key on the certificate to verify Sign-DO(N1). If the verification passes, go to Step-5. If the verification fails, return authentication failure. Step-5: AS takes the block height from the certificate and sends the block height and certificate hash value to CA. CA queries the hash value on the chain based on the index query mechanism. If the same hash value is found, the query result is returned to AS. AS returns the authentication success or failure message to DO based on the query result. After the DO is successfully authenticated, it can access the medical data in this medical domain. Step-6: When DO accesses data from other medical domains across domains, DO must first be authenticated within the domain before it can be authenticated across medical domains. B Send authentication request, AS B Send the random number M1 to DO, DO uses its own private key to sign M1 to get Sign-DO(M1), takes a value M2 equal to M1, and then sends Sign-DO(M1), M2 and its own certificate to AS B , A.S. B Check whether the certificate is within the validity period; If it is within the validity period, query the certificate revocation list. If the certificate has not been revoked, proceed to Step-7; Step-7:AS B Use CA's public key to verify the signature of the certificate. If the verification is successful, verify whether M2 is equal to M1. If they are equal, use DO's public key to verify the signature of the random number M1. If the verification is successful, send the block height and hash value of the certificate to CA. B Perform an on-chain query. If the hash value of the certificate can be found in the alliance chain, the authentication is successful, thus completing the cross-medical domain identity authentication.

2. According to claim 1, a cross-medical domain identity authentication method based on alliance chain is characterized in that: The CA joins the alliance chain after being authorized, and as a node in the alliance chain, participates in packaging and consensus blocks and stores the alliance chain.

Citation Information

Patent Citations

  • Decentralized cross-trust-domain authentication method and system

    CN110061851A

  • Internet-of-Vehicles hierarchical authentication method based on blockchain technology

    CN111935674A

  • Telemedicine cross-domain authentication method based on an alliance chain

    CN112883406A

  • Multi-CA cross-domain authentication method based on block chain in dispersed autonomous network

    CN113343213A

Cited By

  • Cross-domain data sharing method, system and device based on block chain and storage medium

    CN119652672A

  • Blockchain-based Cross-domain Data Sharing Method, System, Device and Storage Medium

    CN119652672B