WO2022196850A1

WO2022196850A1 - Method and system for issuing and certifying digital vaccination certificate

Info

Publication number: WO2022196850A1
Application number: PCT/KR2021/003519
Authority: WO
Inventors: 최철원
Original assignee: 블록체인랩스 주식회사
Priority date: 2021-03-15
Filing date: 2021-03-22
Publication date: 2022-09-22
Also published as: KR20220128812A; KR102478963B1

Abstract

In an authentication method comprising a blockchain network including a public distributed ledger, a first electronic device associated with a first user, and a second electronic device associated with a second user, the blockchain network may store a first user identifier associated with the first user and a first institution identifier corresponding to at least one trusted institution, and the first electronic device may include a first vaccination certificate issued by the at least one trusted institution and including a first digital institution signature of the trusted institution, the first user identifier, and information associated with vaccination of the first user. Various other embodiments understood through the specification are also possible.

Description

Method and system for issuing and certifying vaccination digital certificate

Embodiments disclosed in this document relate to technology for issuing and distributing digital certificates.

When a virus spreads around the world, an epidemic caused by this virus will lead to a global pandemic. A vaccine is developed to address the pandemic, and vaccination begins once the vaccine is complete. At this time, the vaccinated person and the non-vaccinated person are divided, and in order to distinguish between the vaccinated person and the non-vaccinated person, an authentication means capable of authenticating the vaccination person is required.

The distinction between vaccinated and non-vaccinated becomes essential, especially for highly contagious diseases. Due to its strong contagious nature, immunization may be required, for example, in order to have access to places where a large number of people may come into contact. In general, a certificate may be issued to certify that you are the vaccinated person. The certificate may contain information about the name of the recipient, vaccine information, medical institution, and the like. If the certificate is a paper certificate, it is difficult to verify the authenticity of the certificate itself, and the risk of personal information leakage is high.

In addition, the current electronic certificate is issued only by a specific trusted authority. The electronic certificate issuance procedure includes an identity authentication procedure and a payment procedure, which is not convenient for the user because the issuance procedure is difficult. Even if the issuance is completed through a complicated issuance procedure, it is difficult to reuse because it is distributed in the form of printed paper (submitted to an institution, etc.)

Various embodiments disclosed in this document are intended to provide a method and system that simplifies the issuance and distribution of certificates, and allows users to conveniently authenticate whether or not they have been vaccinated. In addition, we want to ensure that there is no risk of personal information leakage during the authentication process, and that authentication can be easily performed between individuals. As a one-time certificate issuance, we want to make it possible to certify all over the world.

A method according to an embodiment disclosed in this document includes a blockchain network including a public distributed ledger, a first electronic device associated with a first user, and a second electronic device associated with a second user, the blockchain network stores a first user identifier associated with the first user, a first organization identifier corresponding to at least one trusted authority, and the first electronic device is issued by the at least one trusted authority, and a first inoculation certificate comprising a first authority digital signature, the first user identifier, and information associated with the vaccination of the first user. The method may include generating, by the first electronic device, a second inoculation certificate, wherein the second inoculation certificate includes information related to vaccination, whether vaccination is performed, the digital signature of the first institution, and the first inoculation certificate. Transmitting, by the first electronic device, the second inoculation certificate to the second electronic device, which is stored in the electronic device and includes a first digital signature generated based on the first identifier associated with the first user; verifying, by the second electronic device, the first institution digital signature included in the second inoculation certificate based on the first institution identifier stored in the blockchain network, the second electronic device being included in the second inoculation certificate verifying the first digital signature based on a first user identifier stored in the blockchain network, and based on the verification result for the first institution digital signature and the verification result for the first digital signature, 2 The method may include obtaining, by the electronic device, information on whether or not the vaccination has been performed.

According to the embodiments disclosed in this document, authentication of whether to vaccinate with minimal exposure of personal information can be made. In addition, high-reliability authentication can be achieved between individuals without using a national agency or a trusted agency as an intermediary. In addition, various effects directly or indirectly identified through this document may be provided.

1 is a schematic diagram of a system for issuing a vaccination digital certificate and verifying whether or not vaccination is performed according to an embodiment.

2 is a block diagram of an identity authentication server and a vaccination management server according to an embodiment.

3 is a block diagram of a medical institution electronic device and a personal electronic device according to an exemplary embodiment.

4 is a signal flow diagram illustrating a method for an identity authentication server to issue an identity certificate to a personal electronic device according to an embodiment.

5 is a signal flow diagram illustrating a method for a vaccination management server to issue a vaccination institution certificate to an electronic device of a medical institution according to an embodiment.

6 is a signal flow diagram for a method of registering a practitioner of vaccination in the vaccination management server according to an embodiment.

7 is a signal flow diagram for a method of issuing an inoculation certificate according to an embodiment.

8 is a signal flow diagram for a method of authenticating whether vaccination is performed according to an embodiment.

In connection with the description of the drawings, the same or similar reference numerals may be used for the same or similar components.

Hereinafter, various embodiments of the present invention will be described with reference to the accompanying drawings. However, this is not intended to limit the present invention to specific embodiments, and it should be understood that various modifications, equivalents, and/or alternatives of the embodiments of the present invention are included.

1 is a schematic diagram of a system 10 (hereinafter referred to as system 10) for issuing a vaccination digital certificate and verifying whether or not inoculation is performed according to an embodiment. The issuance and certification process of the vaccination digital certificate performed on the system 10 will be described as follows.

A vaccination certificate (hereinafter, inoculation certificate) that certifies whether or not a vaccine is available may be issued in the form of a digital certificate. Vaccination Certificate The digital certificate may be a data set including data related to vaccination. The data may include personal sensitive information related to vaccination.

The vaccination management institution may be an institution or organization that manages matters related to vaccination of vaccines. Vaccination management institutions can monitor the sequence of importing, distributing, and inoculating vaccines, and store and manage records thereof. Vaccination management agency can be understood as a trust agency as an agency operated by the state.

The identity authentication institution may be an institution or an organization that manages identity information about individuals and medical institutions. An identity certification authority may manage identity information about an individual that can identify a specific individual. The identity certification authority may issue a certificate (hereinafter, an identity certificate) for at least one item of identity information. The identity authentication institution may manage basic information (identity information) about a medical institution that can identify a specific medical institution. The identity authentication institution may issue a certificate (hereinafter, referred to as a medical institution certificate) for at least one item of basic information of a medical institution. The identity authentication institution may perform authentication of medical institutions necessary for vaccination and identity authentication of inoculators. An identity certification authority is an organization operated by the state and can be understood as a trusted authority.

Vaccination may be performed by a medical institution that is accredited to administer the vaccine. The vaccination management institution may select a medical institution that can perform vaccination among medical institutions or manage a list of pre-selected medical institutions. The vaccination management institution may check basic identity information about the vaccination institution and issue a certificate of the vaccination institution.

For the issuance of an inoculation certificate, an identity authentication institution, a vaccination management institution, and a medical institution may cooperate with each other. Vaccination digital certificate (hereinafter, inoculation certificate) may be issued by a vaccination management institution. The identity authentication institution may provide identity authentication to the vaccination management institution with basic information of a medical institution for issuing an inoculation certificate.

In various embodiments, the identity authentication authority and the vaccination management authority may be integrated. For example, a vaccination management institution can directly store basic identity information about an individual or a medical institution and issue an identity certificate.

Referring to FIG. 1 , the system 10 includes an identity authentication server 100 , a vaccination management server 200 , a medical institution electronic device 300 , a personal electronic device 400 , and a third-party electronic device 500 . can do. The identity authentication server 100 and the vaccination management server 200 may include a plurality of authentication servers, but the system 10 configured with one authentication server is disclosed below.

The identity authentication server 100 is a server device operated by an identity authentication authority. The vaccination management server 200 is a server device operated by a vaccination management institution. The medical institution electronic device 300 is an electronic device (eg, PC, tablet, server device) possessed by a medical institution performing vaccination. The personal electronic device 400 is a personal electronic device (eg, a smartphone, tablet, personal PC) to be vaccinated. The third-party electronic device 500 is an electronic device (eg, a PC, a tablet, a server device) owned by another person or a company that checks whether a specific individual is vaccinated. The structure and operation of the server device and the electronic device will be described later with reference to FIGS. 2 and 3 .

The identity authentication server 100 may issue an identity certificate for an individual and transmit the generated identity certificate to the personal electronic device 400 . The identity authentication server 100 may issue a medical institution certificate for a medical institution, and transmit the issued certificate to the medical institution electronic device 300 . The personal electronic device 400 may store the received identity certificate. The medical institution electronic device 300 may store the received medical institution certificate.

In various embodiments, the medical institution certificate may be understood as a confirmation certificate that enables identification of a specific medical institution. The medical institution certificate may be a verification certificate for the medical institution itself or an identity certificate for a medical institution representative.

The vaccination management server 200 may issue a certificate of a white vaccination institution for a specific medical institution, and may transmit the issued certificate to the electronic device 300 of the medical institution. The medical institution electronic device 300 may store the received vaccination institution certificate.

When the vaccination management server 200 issues the vaccination institution certificate, the vaccination management server 200 may receive the medical institution certificate from the identity authentication server 100 or the medical institution electronic device 300 . The vaccination management server 200 may issue the vaccination institution certificate after identifying whether it is a specific medical institution authorized to inoculate based on the medical institution certificate.

The medical institution electronic device 300 may identify vaccine information. The vaccine information may include information about a vaccine to be administered to the inoculator. Vaccine information may include, for example, the name of the vaccine, manufacturer, clinical information, identification information, and distribution information. For example, the electronic device 300 of a medical institution may receive the vaccine information by recognizing a code (eg, barcode, QR code) attached to the vaccine. Alternatively, the medical institution electronic device 300 may receive a direct input for vaccine information from a medical person.

The medical institution electronic device 300 may identify an individual who is an inoculator. For example, the medical institution electronic device 300 may receive an identity certificate stored in the personal electronic device 300 and identify an individual who is the owner of the personal electronic device 300 based on the received identity certificate. After the vaccination is completed, the electronic device 300 of the medical institution may transmit the identified vaccine information, the identified personal information, and the inoculation information to the vaccination management server 200 . The inoculation information may include information necessary to report the fact of inoculation, such as inoculation time, inoculation location, and inoculation status.

The vaccination management server 200 may issue an inoculation certificate based on the received vaccine information, personal information, and inoculation information. The vaccination management server 200 may transmit the issued vaccination certificate to the personal electronic device 400 .

The personal electronic device 300 may store an inoculation certificate. The personal electronic device 300 may transmit all or part of at least some information included in the inoculation certificate to an electronic device of an individual who is the owner of another subject requesting vaccination authentication or to an electronic device 500 of a third party.

The certificate disclosed herein may be digitally signed by an issuer. A digital signature is a method that can serve as a means of proving the identity of the issuer. For example, the issuer can digitally sign the certificate using an identifier for the corresponding to its digital identity. The certificate recipient can verify the identity of who is the issuer of the certificate through the digital signature. Each subject included in the system 10 (identity authentication server 100, vaccination management server 200, medical institution electronic device 300, personal electronic device 400) may have a respective identifier, and An identifier can be used to issue a digitally signed certificate.

In various embodiments, the digital signature may consist of various algorithms. A key generation algorithm, A signing algorithm, and A signature verifying algorithm may be used. In one example, the RSA algorithm may be utilized.

The identity authentication server 100 may digitally sign an identity certificate and a medical institution certificate with its own identifier. The vaccination management server 200 may digitally sign the vaccination certificate with its identifier. Recipients who have received the identity certificate or inoculation certificate can verify the issuer through a digital signature and trust the contents of the certificate.

For example, in the case of a key generation algorithm, the identity authentication server 100 or the vaccination management server 200 may sign the certificate with its own private key. The certificate recipient may decrypt the inoculation certificate with the public key owned by the identity authentication server 100 or the vaccination management server 200 .

The certificate disclosed in this document may be designed to be verifiable by a third party. That is, the certificate issued and distributed on the system 10 may be verified by all, not by a specific trusted organization (eg, an identity authentication institution, a vaccination management institution).

For example, in the case of a key generation algorithm, the public key is not stored in a specific centralized authority, but in a centralized P2P network such as a federated identity management system of multiple trusted authorities or a distributed ledger. have. In this way, the certificate can be verified by using the value of the public key stored in a place where anyone can access it.

For example, the recipient who receives the inoculation certificate digitally signed by the vaccination management server 200 does not authenticate the inoculation certificate through the vaccination management organization, but through the digital signature of the public vaccination management organization, the inoculation It can be directly confirmed that the certificate was issued by the vaccination management agency, and the contents of the vaccination certificate can be trusted.

In various embodiments, the personal electronic device 400 may generate a certificate by processing a part of the contents of the inoculation certificate. The personal electronic device 400 may transmit the processed certificate to the third-party electronic device 500 . The purpose of processing is to protect privacy by not transmitting all the contents included in the inoculation certificate to a third party, and only include essential contents. For example, if only the fact of the inoculation needs to be proved, the certificate containing only the 'vaccination status' excludes information such as 'what vaccine was received' and 'what medical institution received the vaccine from' may be transmitted to the electronic device 500 .

In one embodiment, the system 10 may be operated based on the blockchain network 600 . The blockchain network 600 of the system 10 may include at least one blockchain network among known public blockchains. A key value for the digital signature of each of the

subjects

100 , 200 , 300 , 400 may be stored in the blockchain network 600 . For example, the identifier of each of the

subjects

100 , 200 , 300 , 400 may be an account or an address value of the blockchain network 600 .

By utilizing the blockchain network 600, the system 10 can function as a global system. Since the certificate issuance and verification can be made based on the blockchain network 600, which is a global platform, the inoculation certificate can be issued and verified without being restricted by the trust institutions of each country or other authentication systems for each country. Hereinafter, the system 10 based on the blockchain network 600 will be described as an example. However, the present invention is not limited thereto, and other open and reliable networks may be employed.

In an embodiment, the identity authentication server 100, the vaccination management server 200, the medical institution electronic device 300, and the personal electronic device 400 communicate with the block chain network 600, and the block chain network ( 600), at least one application that allows access to an account on the above may be stored. The at least one application may include a wallet application of the blockchain network 600 .

In an embodiment, the certificate issued and distributed by the system 10 may have a specification of a verifiable credential (VC) designed according to the W3C standard protocol. Each of the

entities

100 , 200 , 300 , and 400 of the system 100 may be an issuer of a VC.

For example, the processed certificate may have a specification of a verifiable presentation (VP) designed according to the W3C standard protocol. The VP may be composed of some claims among claims included in one VC, and may be composed of a plurality of VCs. Also, the VP may include VCs signed by different issuers.

Entities

100 , 200 , 300 , 400 of system 10 may create or issue a VP containing only the necessary information from one or more VCs.

Digital signatures or digital identifiers used under the blockchain network 600 may be understood as decentralized identifiers (DID) according to the W3C standard protocol. .

In various embodiments, the VC may include an identifier of an issuer and a destructor of the issuer. For example, when the VC for the owner of the personal electronic device 400 is issued by the identity authentication server 100 , the VC is the identifier information (the first identifier) of the identity authentication server 100 and the personal electronic device 400 . of identifier information (second identifier). This may include a meaning that the VC was issued by the first identifier and was issued to the second identifier.

Also, the personal electronic device 400 may generate a VP by signing the VC with its second identifier. Accordingly, the VP may include information that the owner of the second identifier currently owns the VC issued to the second identifier by the first identifier. Accordingly, a third party that has received the VP including some information of the VC can confirm that it has received the authentication information from the rightful owner of the VC, and can trust the authentication information. For example, a third party receiving the VP can confirm that the VP created by the rightful owner of the VC has been transmitted by checking whether the second identifier of the person who created the VP matches the second identifier included in the VC, The information stored in the VP can be trusted.

Hereinafter, the system 10 based on the blockchain network 600 will be described as an example. However, the present invention is not limited thereto, and other open and reliable networks may be employed. For verification through the blockchain network 600 , in one embodiment, the blockchain network 600 may store

ID registries

610 and 620 . Identifiers (eg, DIDs) of subjects of the system 10 may be stored in the

ID registries

610 and 620 . Public keys of VC issuers may be stored in . For example, the

ID registries

610 and 620 may store DIDs of the identity authentication server 100 , the vaccination management server 200 , the medical institution electronic device 300 , and the personal electronic device 400 .

Each of the

subjects

100, 200, 300, and 400 of the system 10 accesses the DID

registry

610, 620 of the blockchain network 600 for mutual verification of certificates, and stores the IDs stored in the registry. You may have permission to read.

In an embodiment, the blockchain network 600 may include a first ID registry 610 and a second ID registry 620 . The first ID registry 610 may be understood as a storage space managed by the identity authentication server 100 and the vaccination management server 200 . Data stored in the first ID registry 610 may be input, modified, or deleted by the trusted

organizations

100 and 200 . Accordingly, the medical institution electronic device 300 and the personal electronic device 400 can view data stored in the first ID registry 610 , but cannot modify or delete data stored in the first ID registry 610 , New data cannot be added to the ID registry 610 . On the other hand, data stored in the second ID registry 620 may be input, modified, or deleted by the

respective subjects

100 , 200 , 300 , and 400 . Therefore, the information provided by the trusted

institutions

100 and 200 can be stored in the block chain network 600, and the subject who reads it can trust the information.

2 is a block diagram of the identity authentication server 100 and the vaccination management server 200 according to an embodiment. In various embodiments, the identity authentication server 100 and the vaccination management server 200 may be integrated. Although the identity authentication server 100 and the vaccination management server 200 are illustrated as one server device, for example, they may be composed of a plurality of server devices.

In an embodiment, the identity authentication server 100 may include a processor 110 , a memory 120 , and a communication circuit 130 . The processor 110 may control the overall operation of the identity authentication server 100 . The identity authentication server 100 may transmit/receive data to and from

other subjects

200 , 300 , and 400 of the system 10 through the communication circuit 130 .

In an embodiment, the memory 120 may include a personal identity DB 122 including identity information on individuals to whom an identity certificate is to be issued. The personal identity DB 122 may include the types of data shown in Table 1. An identity certificate for an individual may be issued based on the personal identity DB 122 .

1One	디지털 신원 식별자(예: DID)Digital identity identifiers (such as DIDs)
22	이름name
33	생년월일date of birth
44	전화번호Phone number
55	개인식별번호 (예: 주민번호)Personal identification number (e.g. social security number)
66	국적nationality
77	푸시토큰push token

The memory 120 may include a medical institution DB 124 for medical institutions to which a medical institution certificate is to be issued. The medical institution DB 124 may include the types of data shown in Table 2. A medical institution certificate for a medical institution may be issued based on the medical institution DB 124 .

1One	의료기관 식별번호(예: 기관 등록번호)IDMedical institution identification number (eg, institution registration number) ID
22	의료기관 명Medical institution name
33	의료기관 주소Medical institution address
44	대표자 이름Representative Name
55	대표자 전화번호Representative phone number
66	의료기관 디지털 신원 식별자(예: DID)Medical institution digital identity identifier (e.g. DID)

In an embodiment, the processor 110 may include an identity certificate issuing module issuing module 112 and a medical institution certificate issuing module issuing module 114 . The processor 110 may execute the instructions stored in the memory 120 to drive the identity certificate issuing module issuing module 112 and the medical institution certificate issuing module issuing module 114 . Operations performed by the identity certificate issuing module issuing module 112 and the medical institution certificate issuing module issuing module 114 may be understood as operations performed by the processor 110 . Other operations described as being performed by the identity authentication server 100 may be understood as operations performed by the processor 110 . The identity certificate issuing module issuing module 112 is a personal identity DB stored in the memory 120 . (122) can be used to issue an identity certificate. For example, an identity certificate including at least a portion of data included in the personal identity DB 122 may be generated. The generated identity certificate may be digitally signed with the digital identity identifier of the identity authentication server 100 . The identity certificate may include an identifier of an individual to whom the identity certificate is issued.

The medical institution certificate issuing module issuing module 114 may issue a medical institution certificate using the medical institution DB 124 stored in the memory 120 . For example, a medical institution certificate including at least a portion of data included in the medical institution DB 124 may be generated. It is possible to digitally sign the generated medical institution certificate with the digital identity identifier of the identity authentication server 100 . The medical institution certificate may include an identifier of a medical institution to which the certificate is issued.

In an embodiment, the identity authentication server 100 may include a wallet for the identity authentication server 100 to communicate with the blockchain network 600 . The wallet may include an account of the identity authentication server 100 on the blockchain network 600 . For example, the identity authentication server 100 may store the private key in the memory 120 . When the identity authentication server 100 issues a certificate, it may be signed with its own private key.

In various embodiments, the wallet may include a DID agent. The DID agent may be issued a DID on the blockchain network 600, inquire the DID, and change the DID. The identity certificate issuing module 112 may store the DID of the individual who issued the certificate and the fact of issuing the certificate in the first registry 610 . The medical institution certificate issuance module 114 may store the DID of the subject who issued the certificate and the fact that the certificate is issued in the first registry 610 .

In an embodiment, the vaccination management server 200 may include a processor 210 , a memory 220 , and a communication circuit 230 . The processor 210 may control the overall operation of the vaccination management server 200 . The vaccination management server 200 may transmit/receive data to and from

other subjects

100 , 300 , 400 of the system 10 through the communication circuit 230 .

In an embodiment, the memory 220 may include a vaccine DB 222 including information on vaccines. Vaccine DB 222 may include the types of data shown in Table 3. Information on vaccines to be described later may include at least one data included in Table 3. An inoculation certificate may be issued based on the vaccine DB 222 . Also, the vaccine DB 222 may be periodically updated according to new information. As the vaccine DB 222 is updated, an action necessary for the medical institution electronic device 300 or the personal electronic device 400 storing the inoculation certificate may be performed. The action may include, for example, a notification operation and an inoculation certificate renewal operation.

1One	백신 이름vaccine name
22	제조사manufacturing company
33	백신 유형Vaccine type
44	투여 방법, 접종 횟수Method of administration, number of inoculations
55	임상 정보(알러지, 부작용)Clinical information (allergy, side effects)
66	사후 관찰 정보Post-observation information
77	유통 정보(시리얼 번호, 수입일, 유통 방법, 의료기관 배송일)Distribution information (serial number, date of import, distribution method, delivery date to medical institutions)

In an embodiment, the memory 220 may include a vaccination institution DB 2124 including information on a vaccination institution having the authority to perform vaccination. The vaccination institution DB 2124 is shown in Table 4 It may include the type of data shown in . There may be multiple vaccination practitioners for a single medical institution. Based on the vaccination agency DB 224, the vaccination management server 200 may determine whether to issue an inoculation certificate.

1One	의료기관 ID 식별번호(예: 기관 등록번호) Medical institution ID identification number (e.g. institution registration number)
22	백신접종 실무자 이름Vaccination practitioner name
33	백신접종 실무자 전화번호Vaccination practitioner phone number
44	백신접종 실무자 식별자디지털 신원(예: DID)Vaccination practitioner identifier digital identity (e.g. DID)
55	허가 상태permission status
66	의료기관 식별자디지털 신원(예: DID)Healthcare IdentifierDigital Identity (e.g. DID)

In an embodiment, the memory 220 may include a vaccination history DB 2126 including information on the performed vaccination. The vaccination history DB 2126 may include the types of data shown in Table 5.

1One	접종자의 식별자 IDIdentifier ID of the inoculant
22	백신 종류Vaccine type
33	백신 시리얼 번호 Vaccine serial number
44	백신접종 의료기관 IDVaccination Medical Institution ID
55	백신접종 수행자인 개인의 디지털 식별자 ID접종 시간, 장소, 횟수 등 접종 정보Digital identifier of the individual who performed the vaccination. Information on vaccination such as time, place, and number of vaccinations.
66	접종 시간, 장소, 횟수 등 접종 정보Inoculation information such as inoculation time, place, frequency, etc.

In an embodiment, the processor 210 may include an inoculation certificate issuing module issuing module 212 and a vaccination post management module 214 . The processor 210 may execute the instructions stored in the memory 220 to drive the vaccination certificate issuing module issuing module 212 and the vaccination post management module 214 . Operations performed by the vaccination certificate issuing module issuing module 212 and the vaccination post management module 214 may be understood as operations performed by the processor 2110 . Other operations described as being performed by the vaccination management server 2100 may be understood as operations performed by the processor 210 . The vaccination certificate issuing module issuing module 212 is a vaccine DB stored in the memory 220 . 222 , the vaccination institution DB 2224 , and the inoculation history DB 226 may be used to issue an inoculation certificate. For example, an inoculation certificate including at least a portion of the data included in the vaccine DB 222 , the vaccination institution DB 2224 , and the inoculation history DB 226 may be generated. The generated inoculation certificate may be digitally signed with the digital identity identifier of the vaccination management server 200 .

The vaccination follow-up management module 214 is a medical institution electronic device 300 and/or personal electronic device based on the vaccine DB 222 , the vaccination institution DB 2224 , and the inoculation history DB 226 stored in the memory 220 . Follow-up care may be provided for the device 400 . For example, when new clinical information is added to the vaccine DB 222 , the vaccination follow-up management module 214 may transmit the additional information to the medical institution electronic device 300 and/or the personal electronic device 400 . .

In an embodiment, the vaccination management server 200 may include a wallet for communication between the vaccination management server 200 and the blockchain network 600 . The wallet may include an account of the vaccination management server 200 on the blockchain network 600 . For example, the vaccination management server 200 may store the private key in the memory 220 . When the vaccination management server 200 issues a certificate, it can be signed with its own private key.

In various embodiments, the wallet may include a DID agent. The DID agent may be issued a DID on the blockchain network 600, inquire the DID, and change the DID. The inoculation certificate issuance module 212 may store the individual DID, the medical institution's DID, and the certificate issuance fact included in the inoculation certificate in the first registry 610 .

3 is a block diagram of a medical institution electronic device 300 and a personal electronic device 400 according to an exemplary embodiment.

In an embodiment, the medical institution electronic device 300 may include a processor 310 , a memory 320 , a communication circuit 330 , a camera 340 , and a display 350 . The processor 310 may control overall operations of the electronic device 300 of a medical institution. The medical institution electronic device 300 may transmit/receive data to and from

other subjects

100 , 200 , and 400 of the system 10 through the communication circuit 330 .

In an embodiment, the memory 320 may store the first application 322 . The medical institution electronic device 300 may execute the first application 322 and output an execution screen of the first application 322 through the display 350 .

The first application 322 may be understood as an application for receiving an authentication service provided on the system 10 . The first application 322 may include functions necessary to use the authentication service, such as a function for requesting issuance of a medical institution certificate and an inoculation certificate, a function for recognizing information on vaccines, and a function for recognizing an inoculator. The first application 322 may store an identifier (eg, DID) of a medical institution. It may be understood as an application for driving an identity authentication function and a vaccination report function of a medical institution that are performed.

In an embodiment, the memory 320 may store the medical institution certificate 324 , the vaccination institution certificate 326 , and the vaccination practitioner list 328 . The medical institution certificate 324 may be issued by the identity authentication server 100 . The vaccination agency certificate 326 may be issued by the vaccination management server 300 . The vaccination practitioner list 328 may be understood as a list of practitioners who may perform vaccination among medical personnel working in a medical institution.

In various embodiments, the memory 322 of the electronic device 300 of the medical institution may include a secure element SE (not shown). The medical institution certificate 324 and the vaccination institution certificate 326 may be stored in the secure element. For example, the secure element may be restricted in direct communication with the

external devices

100 , 200 , and 400 . The first application 322 may relay data transmission/reception between the secure element and the

external devices

100 , 200 , and 400 . In another example, the

external devices

100 , 200 , and 400 may communicate with the secure element through short-range wireless communication through the communication circuit 330 . The identifier of the medical institution electronic device 300 may be stored in the secure element.

In various embodiments, the electronic device 300 of a medical institution may photograph a vaccine to be inoculated through the camera 340 or may photograph a person inoculated. For example, the electronic device 300 of a medical institution may identify an individual vaccine and/or inoculation recipient through the camera 340 .

In an embodiment, the personal electronic device 400 may include a processor 410 , a memory 420 , a communication circuit 430 , a camera 440 , and a display 450 . The processor 410 may control overall operations of the personal electronic device 400 . The personal electronic device 400 may transmit/receive data to and from

other subjects

100 , 200 , and 300 of the system 10 through the communication circuit 430 .

In an embodiment, the memory 420 may store the second application 422 . The personal electronic device 400 may execute the second application 422 and output an execution screen of the second application 422 through the display 450 .

The second application 422 may be understood as an application for driving an identity authentication function and a vaccination authentication function provided to an individual on the system 10 .

In one embodiment, the memory 420 may store the identity certificate 424 and the inoculation certificate 426 . The identity certificate 424 may be issued by the identity authentication server 100 . The vaccination certificate 426 may be issued by the vaccination management server 300 .

The identity certificate 424 and the inoculation certificate 426 are stored in the personal electronic device 400 , and are not stored in the identity authentication server 100 , the vaccination management server 200 , and the medical institution electronic device 300 . Once the certificate is issued, the owner of the personal electronic device 400 can directly prove his/her identity or vaccination status by using the certificate stored in his/her electronic device 400 directly without communication with other trusted organizations. have. Also, by issuing the processed certificate, the personal electronic device 400 may generate a certificate including only necessary information and share it with a third party. In this way, individual sovereignty over data can be strengthened.

In various embodiments, the memory 422 of the electronic device 400 of the medical institution may include a secure element SE (not shown). The identity certificate 424 and the inoculation certificate 426 may be stored in the secure element. For example, the secure element may be restricted in direct communication with the

external devices

100 , 200 , and 300 . The second application 422 may relay data transmission/reception between the secure element and the

external devices

100 , 200 , and 300 . In another example, the

external devices

100 , 200 , and 300 may communicate with the secure element through short-range wireless communication through the communication circuit 430 .

In an embodiment, the personal electronic device 300 may share a stored certificate or a processed certificate with a third party through the communication circuit 330 .

The second application 422 may be understood as an application for receiving an authentication service provided on the system 10 . The second application 422 may include functions necessary to use the authentication service, such as a function to request issuance of an identity certificate and an inoculation certificate, and a function to share a certificate stored in the personal electronic device 400 . The second application 422 may store an individual identifier (eg, DID).

In an embodiment, the first application 322 and the second application 422 may include a wallet for communicating with the blockchain network 600 . The wallet may include accounts on the blockchain network 600 . For example, the medical institution electronic device 300 and the personal electronic device 400 may store respective private keys in the

memories

320 and 420 . When the medical institution electronic device 300 and the personal electronic device 400 issue a certificate, signing may be performed with their own private key.

In various embodiments, the first application 322 and the second application 422 may include a DID agent. The first application 322 and the second application 422 may receive a DID on the block chain network 600, inquire the DID, and change the DID.

Hereinafter, a case in which the certificate issued on the system 10 is a verifiable credential (hereinafter, VC) according to the W3C standard will be described as an example. In addition, the case of a verifiable presentation (hereinafter referred to as VP) designed according to the W3C standard protocol will be described as an example of the certificate generated by processing from the VC.

4 is a signal flow diagram illustrating a method for the identity authentication server 100 to issue an identity certificate to the personal electronic device 400 according to an embodiment.

The personal electronic device 400 may request the identity authentication server 100 to issue an identity authentication VC (the above-mentioned identity certificate) ( 4010 ). The personal electronic device 400 may drive the second application 422 and transmit the request to the identity authentication server 100 through the second application 422 . In operation 4010, the personal electronic device 300 may transmit its own DID (hereinafter, personal DID). The identity authentication server 100 may confirm the received DID through the personal identity DB 122 block chain network 600 . The identity authentication server 100 may transmit an identity verification request to the personal electronic device 300 ( 4020 ). Before issuing the identity authentication VC, the identity confirmation request may be performed to identify whether the owner of the personal electronic device 300 is a specific individual to whom the identity authentication VC is issued.

The identity authentication server 100 may acquire personal information ( 4030 ). For example, the identity authentication server 100 may acquire the personal information of the owner of the personal electronic device 300 from a third service that provides the identity authentication service. The personal information may include name, gender, date of birth, mobile phone number, nationality, and personal identification number (eg, data in Table 1). The identity authentication server 100 may compare the acquired personal information with data stored in the personal identity DB 122 and check whether the two match. Through this, the identity authentication server 100 can check whether the identity authentication VC issuance request is made by a legitimate user. It can be stored.

The identity authentication server 100 may issue an identity authentication VC (4040). Identity Authentication VC The identity authentication server 100 may include the personal DID and personal information received from the personal electronic device 400. One VC may be issued. The identity authentication VC may be digitally signed as an identifier for a digital identity as an identifier of the identity authentication server 100 . The identifier may be, for example, a secret key (DID) of an account of the blockchain network 600 of the identity authentication server 100 .

The identity authentication server 100 and the personal electronic device 400 may form a communication channel for mutual data transmission ( 4050 ). The identity authentication server 100 may transmit the identity authentication VC to the personal electronic device 400 through the communication channel. The personal electronic device 400 may store the received identity authentication VC in the memory 420 . The identity authentication VC may be referred to as the identity certificate 424 of FIG. 3 .

In one example, the communication channel may be an inter-DID encrypted secret communication channel. For example, the communication channel may be a DIDComm communication channel. Hereinafter, a communication channel formed to distribute VCs may be understood as an encrypted secret communication channel between DIDs. The identity authentication VC may be delivered to the second application 422 of the personal electronic device 400 possessing the DID, which is the issuance target of the VC, through the DIDComm communication channel. For example, the identity authentication server 100 may use a web socket connected to the second application 422 . Alternatively, the identity authentication server 100 may use the message queue after sending a push notification to the second application 422 when the websocket does not exist.

The identity authentication server 100 may update the personal identity DB 122 for the user who has issued the identity authentication VC to the personal identity DB 122 and store personal information (4070). For example, the identity authentication server 100 may store the DID obtained in step 4010 and the personal information obtained in step 4030 in the personal identity DB 122 in the personal identity DB 122 . Accordingly, the DID and the personal information may be mapped to each other and stored. In addition, it is possible to record whether the identity authentication VC is issued in the personal identity DB 122 .

The identity authentication server 100 may receive and store the push notification token from the second application 422 of the personal electronic device 400 ( 4080 ). The identity authentication server 100 may send a push notification to the personal electronic device 400 through the push notification token and the second application 422 .

The push notification token stored in the personal electronic device 400 may update the identity authentication server 100 with updates whenever the second application 422 is driven ( 4090 ).

In various embodiments, the identity authentication server 100 may record the identity authentication VC issuance fact for the user DID in the first registry 610 of the blockchain network 600 . Therefore, the fact that the identity authentication VC issued by the identity authentication authority for the corresponding DID can be verified.

The method of issuing an identity certificate of FIG. 4 may be similarly applied to a method of issuing a medical institution certificate to the medical institution electronic device 300 .

The medical institution electronic device 300 may request a medical institution authentication VC (the aforementioned medical institution certificate) issuance request (eg, operation 4010 ). The medical institution electronic device 300 may drive the first application 322 and transmit the request to the identity authentication server 100 through the first application 322 . In this case, the medical institution electronic device 300 may transmit basic information about the medical institution and the DID of the medical institution stored in the first application 322 to the identity authentication server 100 .

The identity authentication server 100 may compare information stored in the medical institution DB 124 based on the received basic information. Through this, the identity authentication server 100 can check whether the medical institution authentication VC issuance request is made by a legitimate user. When the information stored in the medical institution DB 124 and the received basic information match, the identity authentication server 100 may issue a medical institution authentication VC including the identifier DID of the medical institution and the identifier of the identity authentication institution.

The identity authentication server 100 and the medical institution electronic device 300 may form a communication channel for mutual data transmission (eg, operation 4050). The identity authentication server 100 may transmit the medical institution authentication VC to the medical institution electronic device 300 through the communication channel. The medical institution electronic device 200 may store the received medical institution authentication VC in the memory 320 . The medical institution authentication VC may be referred to as the medical institution certificate 324 of FIG. 3 . The identity authentication server 100 may map and store basic information about the medical institution that issued the medical institution authentication VC and the medical institution DID to the medical institution DB 124 (eg, operation 4070). You can record whether or not it is issued.

In various embodiments, the identity authentication server 100 may record the fact that the medical institution authentication VC is issued for the medical institution DID in the first registry 610 of the blockchain network 600 . Therefore, the fact that the medical institution authentication VC issued the DID by the identity authentication institution can be verified.

Operations 4080 to 4090 of FIG. 4 may be equally performed through the identity authentication server 100 and the first application 322 of the electronic device 300 of the medical institution. Through this, the identity authentication server 100 may transmit a push notification to the medical institution electronic device 300 through the first application 322 .

5 is a signal flow diagram illustrating a method by which the vaccination management server 200 issues a vaccination institution certificate to the electronic device 300 of a medical institution according to an embodiment. A vaccination institution may be understood as a medical institution licensed to perform vaccination. The list of vaccination institutions may be designated in advance and stored in the vaccination institution (DB) 224 of the vaccination management server 200 . The vaccination institution can prove that it is a medical institution that can vaccinate with the certificate of the vaccination institution.

The medical institution electronic device 300 may transmit a vaccination institution authentication VC issuance request including the medical institution authentication VC (eg, the medical institution certificate 324 of FIG. 3 ) to the vaccination management server 200 ( 5010 ). The request may include a medical institution authentication VC (eg, the medical institution certificate 324 of FIG. 3 ). In various embodiments, the medical institution electronic device 300 may sign the medical institution authentication VC with the medical institution DID and transmit the digitally signed medical institution authentication VC to the vaccination management server 200 . The vaccination management server 200 may check whether the medical institution authentication VC is transmitted from a person having a legitimate authority to own the VC by checking whether the digital signature matches the medical institution DID stored in the medical institution authentication VC. If another medical institution makes an unreasonable issuance of a vaccination institution authentication VC with the medical institution authentication VC, since the medical institution authentication VC received in operation 5010 does not include a signature by the medical institution DID stored in the VC, vaccination management The server 200 may reject the VC issuance request.

The medical institution electronic device 300 may receive a medical institution authentication VC by the method described above with reference to FIG. 4 before applying for the vaccination institution authentication VC. The medical institution electronic device 300 may perform identity authentication by submitting the medical institution authentication VC to the vaccination management server 200 . For example, a representative (individual) of a medical institution may download the first application 322 to the electronic device 300 of the medical institution and then generate the medical institution's own DID. The DID generated locally by the representative through the first application 322 of the electronic device 300 of the medical institution may be stored and registered in the second registry 620 of the blockchain network 600 . In various embodiments, the medical institution DID may be replaced with a DID of an individual representative of the medical institution. In this case, the medical institution electronic device 300 transmits the generated DID to the identity authentication server 100, and the identity authentication VC for the individual representative may be treated as a medical institution authentication VC.

The vaccination management server 200 may verify the received medical institution authentication VC (5020). The vaccination management server 200 may verify the digital signature of the identity authentication server 100 of the medical institution authentication VC. For example, the vaccination management server 200 may check whether the DID that signed the medical institution authentication VC is the DID of the trusted institution registered in the first registry 610 of the blockchain network 600 . It is possible to check the DID owner initiated through the blockchain network 600 through the blockchain network 600 .

The vaccination management server 200 may compare the information of the vaccination institution DB 224 with the information of the medical institution authentication VC (5020). When the vaccination management server 200 has information matching the medical institution authentication VC in the vaccination institution DB 224 , it can confirm that the medical institution that has applied for the VC is a medical institution that has been previously authenticated as a vaccination institution. The vaccination management server 200 may issue a vaccination institution VC (5030). Vaccination institution VC may include an identifier of a vaccination management institution and an identifier of a medical institution.

The vaccination management server 200 and the medical institution electronic device 300 may form a communication channel for mutual data transmission (5040). The vaccination management server 200 may transmit the vaccination institution VC to the electronic device 300 of the medical institution through the communication channel. The medical institution electronic device 300 may store the received vaccination institution VC in the memory 320 . The vaccination institution VC may be referred to as the vaccination institution certificate 326 of FIG. 3 .

In one example, the communication channel of operation 5040 may be an encrypted communication channel. For example, the communication channel may be a DIDComm communication channel. The vaccination institution VC may be transmitted to the first application 322 of the medical institution electronic device 300 possessing the DID, which is the issuance target of the VC, through the DIDComm communication channel. For example, the vaccination management server 200 may use a web socket connected to the first application 322 . Alternatively, the vaccination management server 200 may use the message queue after sending a push notification to the first application 322 when the websocket does not exist.

The vaccination management server 200 may store the VC issuance history in the vaccination institution DB (5060). In various embodiments, the vaccination management server 200 may record the fact that the vaccination institution authentication VC is issued for the medical institution DID in the first registry 610 of the blockchain network 600 . Therefore, it can be verified that the DID was issued by the vaccination agency certification VC by the vaccination management agency.

The vaccination management server 200 may receive and store the push notification token from the first application 322 of the electronic device 300 of the medical institution ( 5070 ). The vaccination management server 200 may send a push notification to the medical institution electronic device 300 through the push notification token and the first application 322 .

The push notification token stored in the electronic device 300 of the medical institution may update the update information to the vaccination institution server 200 whenever the first application 322 is driven ( 4090 ).

In various embodiments, the medical institution authentication VC may be replaced with the identity authentication VC of the individual representative of the medical institution. Information on the individual representative may be stored in the vaccination agency DB 224 of the vaccination management server 200 (eg, Table 2). Individual representatives can submit the identity authentication VC issued by their DID and receive a vaccination agency VC.

6 is a signal flow diagram for a method of registering a practitioner of vaccination in the vaccination management server 200 according to an embodiment. The medical institution electronic device 300 may manage a list of practitioners to be vaccinated among medical personnel of the corresponding medical institution. The medical institution electronic device 300 may store information about the practitioners in the vaccination practitioner list 328 . When a change occurs in the practitioner, the medical institution electronic device 300 may immediately update the changed information in the vaccination practitioner list 328 .

The medical institution electronic device 300 may transmit the vaccination practitioner list to the vaccination management server 200 (6010). The vaccination management server 200 may update the vaccination institution DB 224 . The list of vaccination practitioners may be stored in a mapping with a medical institution.

A medical practitioner who is a vaccination practitioner may download the first application 322 to an electronic device 300-1 (hereinafter, referred to as medical practitioner electronic device 300-1) possessed by the person and may generate a DID. The medical personnel electronic device 300 - 1 may register the locally generated DID in the blockchain network 600 . The medical personnel electronic device 300 - 1 may receive an identity authentication VC for the medical personnel from the identity authentication server 100 . In order to receive the authentication service of the system 10 , a first application 322 may be installed in the medical personnel electronic device 300 - 1 . The medical personnel electronic device 300 - 1 may have the same block diagram as the medical institution electronic device 300 of FIG. 3 .

The medical personnel electronic device 300 - 1 may transmit the identity authentication VC to the vaccination management server 200 ( 6030 ). The vaccination management server 200 may verify the digital signature of the identity authentication server 100 of the identity authentication VC. The vaccination management server 200 may compare the information of the practitioner in the vaccination institution DB 224 and the information of the identity authentication VC. When there is information matching the identity authentication VC in the vaccination institution DB 224, the vaccination management server 200 may confirm that the medical person who applied for the VC is a medical person who has been previously authenticated as a vaccination practitioner (6040). The vaccination management server 200 may issue a vaccination institution VC to a specific medical person (6050). In this case, the vaccination institution VC may include the DID of the medical institution and the DID of the medical personnel.

The vaccination management server 200 and the medical personnel electronic device 300-1 may form a communication channel for data communication with each other (6060). The vaccination management server 200 may transmit the vaccination institution VC to the healthcare provider electronic device 300-1 through the communication channel. The healthcare provider electronic device 300 - 1 may store the received vaccination institution VC in a memory (eg, the memory 320 of FIG. 3 ). The vaccination institution VC may be referred to as the vaccination institution certificate 326 of FIG. 3 .

The vaccination management server 200 may store the VC issuance history in the vaccination institution DB 224 (6080). In various embodiments, the vaccination management server 200 may record the fact that the vaccination institution VC is issued for the healthcare provider DID in the first registry 610 of the blockchain network 600 . Therefore, the fact that the Vaccination Agency VC issued the DID by the Vaccination Management Agency can be verified.

According to various embodiments, when a specific vaccination practitioner is deleted from the vaccination practitioner list, the electronic device 300 of the medical institution may transmit a vaccination practitioner deletion update request to the vaccination management server 200 . The vaccination management server 200 may delete the practitioner from the vaccination institution DB 224 and cause the deleted practitioner's DID to be deleted from the first registry 610 of the block chain network 600 (6080) . Vaccination agency VC issued for the deleted practitioner's DID will be unavailable. Therefore, it becomes impossible to issue an inoculation certificate through the electronic device 300-1 for medical personnel.

In various embodiments, the medical institution electronic device 300 and the medical personnel electronic device 300 - 1 may be subjects that can request issuance of an inoculation certificate after vaccination. Although an example in which the medical institution electronic device 300 performs a request for issuing an inoculation certificate is illustrated through FIG. 7 , the same procedure may be applied to the medical care provider electronic device 300-1.

The medical institution electronic device 300 may identify a vaccine to be used ( 7010 ). For example, the electronic device 300 of a medical institution may drive the first application 322 and identify a vaccine to be inoculated. Here, the vaccine to be identified may be a vaccine to be directly vaccinated to the vaccinated person. The medical institution electronic device 300 may acquire information about a vaccine to be used, for example, information such as a vaccine type, a serial number, and distribution information of the corresponding vaccine (eg, data in Table 3). The identification procedure may be performed by manual input or by barcode/QR code recognition.

The medical institution electronic device 300 may receive the identity authentication VC from the personal electronic device 400 possessed by the inoculator ( 7020 ). The identity authentication VC may include a digital signature of the individual's DID. The medical institution electronic device 300 may identify the inoculator through the digital signature and identity authentication VC.

When the inoculation is completed, the medical institution electronic device 300 may transmit the inoculation information, the identity authentication VC of the inoculator, and the vaccination institution authentication VC of the medical institution to the vaccination management server 200, and may request issuance of the inoculation authentication VC (7030). ). In this case, the vaccine identification information, the identity authentication VC, and the vaccination institution authentication VC may be digitally signed with the user DID of the medical institution electronic device 300 . In operation 7030, the electronic device 300 of the medical institution may collect and transmit information on a vaccine inoculated to a vaccination management institution and information on an individual inoculation.

The inoculation information may include medical information that needs to be recorded in relation to inoculation, such as identified vaccine information, inoculation time, and inoculation location.

The vaccination management server 200 may verify the received information. The vaccination management server 200 may verify the received digital signatures of the received vaccination institution VC and the electronic device 300 of the medical institution ( 7040 ). That is, whether it is a digital signature by the vaccination institution can be verified.

In various embodiments, the vaccination management server 200 may compare the received vaccine information with the vaccine DB 222 to confirm whether the correct vaccine information distributed to the corresponding medical institution is input. The vaccination management server 200 may check whether the received identity authentication VC is valid. When it is determined that the corresponding information needs to be supplemented, the vaccination management server 200 may transmit a supplementation request to the electronic device 300 of the medical institution.

When the verification of the received information is completed, the vaccination management server 200 may issue an inoculation authentication VC (7050). The vaccination management server 200 may transmit the issued vaccination authentication VC to the personal electronic device 400 . The personal electronic device 400 may store the inoculation authentication VC. The inoculation certification VC may be referred to as an inoculation certificate 426 .

The user of the personal electronic device 400 may check detailed information about the inoculated vaccine through the second application 422 . The inoculation certificate 426 may include a vaccine type, an inoculation date, an inoculation time, information on a medical institution that performed the vaccination, and information on a medical person who performed the vaccination.

The vaccination management server 200 may store the vaccination history in the vaccination history DB 226 .

An individual who has completed the inoculation holds the inoculation certificate 426 in the personal electronic device 400 . Through the second application 422 of the personal electronic device 400 , it is possible to authenticate whether a subject has been vaccinated or not with respect to a subject that requests authentication of whether or not to vaccinate.

Referring to FIG. 8 , an example of authenticating whether or not vaccination is performed between individual A and individual B is illustrated. However, certification of whether or not vaccination is performed can be performed by any third party, such as a company or service. Any subject possessing the electronic device 400 in which the second application 422 providing the inoculation authentication function is installed may perform the authentication.

A request for authentication of whether to vaccinate or not may occur between the electronic device A 400a and the electronic device B 400b ( 8010 ). For example, the electronic device A 400a and the electronic device B 400b may execute the second application 422 and output a screen requesting authentication. The electronic device A 400a and the electronic device B 400b may generate an authentication request by scanning each other's screens. As another example, when the electronic device A 400a and the electronic device B 400b are located close to each other by a predetermined distance or more, an authentication request may occur.

When an authentication request is generated, the electronic device A 400a and the electronic device B 400b may establish an encrypted communication channel ( 8020 ).

Since the inoculation certificate 426 includes various information related to inoculation, the electronic device A 400a may issue a processed inoculation certificate including only some information included in the inoculation certificate 426 . The processed inoculation certificate may be referred to as VP as described above.

For example, the electronic device A 400a may issue a VP including only information on whether or not vaccination has been performed ( 8030 ). The electronic device A 400a may transmit the VP for whether or not to vaccinate to the electronic device B 400b. Since the VP is digitally signed by the vaccination management agency, Person B can trust it. As described above, exposure of personal information can be minimized by using a zero-knowledge proof that only authenticates information on whether or not vaccination is performed.

In various embodiments, the electronic device A 400a may issue a VP including only whether or not vaccination is performed among the identity authentication VC and the inoculation authentication VC. The electronic device A 400a may transmit a corresponding VP to a subject requesting both identity information and whether to vaccinate.

Since the system 10 based on the blockchain network 600 is an open system, anyone using the same DID agent can use the authentication service provided by the system 10 . In addition, certification can be freely performed in the private sector without a national agency or a specific trusted agency as an intermediary.

The electronic device according to various embodiments disclosed in this document may be a device of various types. The electronic device may include, for example, a portable communication device (eg, a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance device. The electronic device according to the embodiment of the present document is not limited to the above-described devices.

The various embodiments of this document and terms used therein are not intended to limit the technical features described in this document to specific embodiments, but it should be understood to include various modifications, equivalents, or substitutions of the embodiments. In connection with the description of the drawings, like reference numerals may be used for similar or related components. The singular form of the noun corresponding to the item may include one or more of the item, unless the relevant context clearly dictates otherwise. As used herein, "A or B", "at least one of A and B", "at least one of A or B," "A, B or C," "at least one of A, B and C," and "A , B, or C" each may include all possible combinations of items listed together in the corresponding one of the phrases. Terms such as "first", "second", or "first" or "second" may simply be used to distinguish an element from other elements in question, and may refer elements to other aspects (e.g., importance or order) is not limited. It is said that one (eg, first) component is “coupled” or “connected” to another (eg, second) component, with or without the terms “functionally” or “communicatively”. When referenced, it means that one component can be connected to the other component directly (eg by wire), wirelessly, or through a third component.

As used herein, the term “module” may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as, for example, logic, logic block, component, or circuit. A module may be an integrally formed part or a minimum unit or a part of the part that performs one or more functions. For example, according to an embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of the present document are stored in a storage medium (eg, internal memory (#36) or external memory (#38)) readable by a machine (eg, electronic device #01). It may be implemented as software (eg, program #40) including one or more instructions. For example, a processor (eg, processor #20) of a device (eg, electronic device #01) may call at least one command among one or more commands stored from a storage medium and execute it. This makes it possible for the device to be operated to perform at least one function according to the called at least one command. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain a signal (eg, electromagnetic wave), and this term is used in cases where data is semi-permanently stored in the storage medium and It does not distinguish between temporary storage cases.

According to one embodiment, the method according to various embodiments disclosed in this document may be provided as included in a computer program product. Computer program products may be traded between sellers and buyers as commodities. The computer program product is distributed in the form of a machine-readable storage medium (eg compact disc read only memory (CD-ROM)), or via an application store (eg Play Store ^TM ) or on two user devices ( It can be distributed (eg downloaded or uploaded) directly, online between smartphones (eg: smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily generated in a machine-readable storage medium such as a memory of a server of a manufacturer, a server of an application store, or a memory of a relay server.

According to various embodiments, each component (eg, a module or a program) of the above-described components may include a singular or a plurality of entities. According to various embodiments, one or more components or operations among the above-described corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (eg, a module or a program) may be integrated into one component. In this case, the integrated component may perform one or more functions of each component of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component are executed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations are executed in a different order, or omitted. , or one or more other operations may be added.

Claims

An authentication method comprising a blockchain network including a public distributed ledger, a first electronic device associated with a first user, and a second electronic device associated with a second user, the authentication method comprising:

The blockchain network stores a first user identifier associated with the first user, a first organization identifier corresponding to at least one trusted organization, and

The first electronic device includes a first inoculation certificate issued by the at least one trusted organization, the first inoculation certificate including a first digital signature of the trusted organization, the first user identifier, and information related to vaccination of the first user box;

The method is

and generating, by the first electronic device, a second inoculation certificate, wherein the second inoculation certificate is stored in the first electronic device including whether or not vaccination is performed, the digital signature of the first institution, and the information related to the vaccination. and comprising a first digital signature generated based on a first identifier associated with the first user;

transmitting, by the first electronic device, the second inoculation certificate to the second electronic device;

verifying, by the second electronic device, the first institution digital signature included in the second inoculation certificate based on the first institution identifier stored in the blockchain network;

verifying, by the second electronic device, a first digital signature included in the second inoculation certificate based on a first user identifier stored in the blockchain network; and

and obtaining, by the second electronic device, information on whether or not the vaccination has been performed, based on a verification result of the first institution digital signature and a verification result of the first digital signature.
The method according to claim 1,

The step of generating the second inoculation certificate by the first electronic device includes:

receiving a selection input for at least some data of the first inoculation certificate; and

Stored in the first electronic device, the step of performing a digital signature on the second inoculation certificate based on the first identifier; Containing, the authentication method.
The method according to claim 1,

The step of verifying the digital signature of the first institution included in the second inoculation certificate,

Comprising the step of the second electronic device comparing the identifier derived from the first institution digital signature included in the second inoculation certificate with the first institution identifier stored in the blockchain network,

The step of verifying the second user digital signature included in the second inoculation certificate,

and comparing, by the second electronic device, the first identifier derived from the first digital signature included in the second inoculation certificate with a first user identifier stored in the blockchain network.
The method according to claim 1,

a trusted institution server associated with the at least one trusted institution, and a medical institution electronic device associated with a medical institution, wherein the block chain network stores a first medical institution identifier associated with the medical institution;

The method is

transmitting, by the first electronic device, a first identity certificate to the medical institution electronic device, wherein the first identity certificate is issued by at least one trusted organization, the first institution digital signature, identity information associated with the first user; and the first digital signature generated based on the first identifier;

verifying, by the medical institution electronic device, the first digital signature based on a first user identifier stored in the blockchain network;

obtaining, by the electronic device of the medical institution, information on a vaccine to be inoculated to a first user based on a result of verifying the first digital signature;

transmitting an inoculation certificate issuance request including a second digital signature generated based on the first identity certificate, the vaccine information, and a second identifier stored in the electronic device of the medical institution to the trusted institution server;

in response to the inoculation certificate issuance request, verifying, by the trusted institution server, the second digital signature based on the first medical institution identifier stored in the blockchain network;

Generating the first inoculation certificate including at least some of the information included in the first identity certificate, at least some of the vaccine information, and the first institution digital signature based on the verification result for the second digital signature step; and

The authentication method further comprising the step of transmitting, by the trusted authority server, the first inoculation certificate to the first electronic device.
5. The method according to claim 4,

transmitting, by the medical institution electronic device, a request for issuing a vaccination institution certificate to the trusted institution server, wherein the request for issuing a vaccination institution certificate includes the second digital signature generated based on the second identifier and a medical institution certificate, , the medical institution certificate is issued by the at least one trusted institution, and includes the first institution digital signature and basic information associated with the medical institution;

In response to the vaccination institution certificate issuance request, the trusted institution server verifies the first institution digital signature included in the vaccination institution certificate issuance request based on the first institution identifier stored in the blockchain network; ;

in response to the vaccination institution certificate issuance request, verifying, by the trusted institution server, the second digital signature based on the first medical institution identifier stored in the blockchain network;

generating, by the trusted authority server, a vaccination authority certificate based on a result of the verification, wherein the vaccination authority certificate includes the first authority digital signature and the first medical facility identifier; and

The method further comprising the step of uploading, by the trusted institution server, the first medical institution identifier to the block chain network, and transmitting the vaccination institution certificate to the medical institution electronic device.
5. The method according to claim 4,

The blockchain network is

a first registry storing the first user identifier and the first organization identifier;

The first registry is configured to be modifiable only by the trusted authority server.
The method according to claim 1,

Transmitting the second inoculation certificate,

outputting, by the first electronic device, a code corresponding to the second inoculation certificate through a display; and

Recognizing, by the second electronic device, the code through a camera;