KR20230120792A - Method and computer program of verifying drone pilot qualifications based on Decentralized Identity - Google Patents

Abstract

Provided is a computer program stored in a computer-readable storage medium including instructions for allowing a processor of a verification node to perform the following steps. According to some embodiments, the steps include the steps of: generating a decentralized identifier (DID) for a verifying entity; in response to an access request obtained from a node to be verified, requesting a verifiable presentation (VP) for an entity to be verified from the node to be verified, the access request including a control request for a drone controlled by a verification node; if the VP is obtained from the node to be verified, verifying the VP using a registry based on a blockchain network; and if the verification of the VP is successful, granting control authority for the drone to the node to be verified. Therefore, provided are a method for verifying drone pilot qualifications with improved reliability and a program for implementing the same.

Description

Method and computer program of verifying drone pilot qualifications based on decentralized identity

The present invention relates to a drone pilot qualification verification method, and more particularly, to a drone pilot qualification verification method with improved reliability using decentralized identity (DID) and a program implementing the same.

Recently, drones are widely used in various fields such as personal hobbies, industrial use, and military use. For example, a delivery company may use a drone to deliver goods, a military official may use a drone to search a military area, and an individual may use a drone to photograph a user using a camera. Since drones for various purposes are developed and used for various purposes, it is unknown who controls the drone in flight and for what purpose it is flying. In addition, there is a risk that the drone is controlled by another person, and in the event of an accident caused by a drone, it is necessary to identify the person who operated the drone.

Accordingly, the Enforcement Decree of the Aviation Safety Act expanded the scope of drone aircraft reporting, and the Enforcement Rule of the Aviation Safety Act subdivided and regulated pilot qualification requirements according to the classification of drones. However, there are still cases where drones are operated by users who are not qualified to operate drones or who do not have the qualifications required to operate the drones. As a result, problems such as the risk of accidents and operation within restricted areas occur frequently. exist.

In order to solve the above problem, Korean Patent Registration No. 2228579 devised a drone user authentication method through biometric authentication. It is only for the purpose, but there is a limit that the drone pilot qualification cannot be verified.

Domestic Patent No. 2228579 (published on March 10, 2021)

The present invention has been made in response to the above background art, and a technical problem to be solved by the present invention is to provide a method for verifying drone pilot qualification with improved reliability and a program implementing the same.

The technical problems of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the following description.

A computer program stored in a computer readable storage medium according to some embodiments of the present invention for achieving the above technical problem is disclosed. The computer program includes instructions for causing a processor of a verification node to perform the following steps:

generating a decentralized identifier (DID) for the verification entity; In response to an access request obtained from a node to be verified, requesting a verifiable presentation (VP) for an entity to be verified to the node to be verified, wherein the access request includes a control request for a drone controlled by the node to be verified. ; verifying the VP through a blockchain network-based registry when the VP is obtained from the node to be verified; and if the verification of the VP is successful, granting control authority for the drone to the node to be verified.

According to an embodiment, the control authority may include power on/off authority of the drone and driving authority of the drone.

According to an embodiment, the VP may include a verifiable credential (VC) including at least one of information about the unmanned aerial vehicle piloting qualification, piloting experience, total piloting time, and recent piloting history of the entity to be verified.

In this case, the driving authority may include the authority for the driving altitude of the drone or the driving speed of the drone, which is determined based on at least one information of the piloting history, total piloting time, and recent piloting history.

According to an embodiment, the VP may include a Verifiable Credential (VC) including information about the piloting qualification of the unmanned aerial vehicle of the entity to be verified and the pilot area of the entity to be verified.

In this case, the driving authority may include authority for the steering permitted area.

According to an embodiment, the steps may further include transmitting a warning notification to the node to be verified when it is determined that the drone is out of the pilot permitted area.

According to an embodiment, the steps may further include activating a Return To Home (RTH) of the drone when the number of times the drone leaves the pilot permitted area reaches a predetermined reference number.

According to an embodiment, the steps may include re-requesting the VP to the node to be verified when a predefined additional verification condition is satisfied; re-verifying the VP through the registry when the VP is acquired; and maintaining the control authority when the re-verification of the VP is successful, and retrieving the control authority and activating a Return To Home (RTH) of the drone when the re-verification of the VP fails.

According to an embodiment, the additional verification condition may be satisfied when a preset time is reached after the previous verification.

According to an embodiment, the additional verification condition may include a condition for the driving state of the drone.

According to an embodiment, the additional verification condition may be satisfied when a hovering duration of the drone reaches a preset time.

According to an embodiment, the additional verification condition may be satisfied when the driving speed of the drone is less than a preset speed.

A computer program stored in a computer readable storage medium according to some embodiments of the present invention is provided. The computer program includes instructions for causing a processor of a node to be verified to perform the following steps:

generating a decentralized ID (DID) for the entity to be verified; requesting issuance of a Verifiable Credential (VC) to an issuing node using the DID; when obtaining the VC for the entity to be verified from the issuing node, providing an access request including a control request of a drone to a verification node, wherein the drone is controlled by the verification node; generating a VP of the entity to be verified including the VC, and providing the created VP to the verification node when a request for a verifiable presentation (VP) of the entity to be verified is received from the verification node; When the verification of the VP is successful, obtaining control authority for the drone from the verification node.

According to an embodiment, the VC may include at least one information of unmanned aerial vehicle qualification information and unmanned aerial vehicle training completion information of the entity to be verified.

According to an embodiment, the control authority may include power on/off authority of the drone and driving authority of the drone.

According to an embodiment, the VC may provide information on at least one of unmanned aerial vehicle qualification information, unmanned aerial vehicle training completion information, piloting career, total piloting time, and recent piloting history of the entity to be verified. can include

In this case, the driving authority may include the authority for the driving altitude of the drone or the driving speed of the drone, which is determined based on at least one information of the piloting history, total piloting time, and recent piloting history.

According to an embodiment, the VC may include unmanned aerial vehicle qualification information, unmanned aerial vehicle training completion information of the entity to be verified, and information on a pilot permitted area of the entity to be verified.

In this case, the driving authority may include authority for the steering permitted area.

Details of other embodiments are included in the detailed description and drawings.

1 is a diagram for explaining a drone pilot qualification verification system using distributed identification according to some embodiments of the present invention.
2 is a diagram for explaining configurations of an issuing node, a to-be-verified node, and a verification node according to some embodiments of the present invention.
3 is a diagram for schematically explaining a linked operation of a drone piloting qualification verification system using distributed identification according to some embodiments of the present invention.
4 is a diagram for illustratively explaining the configuration of a Verifiable Credential (VC) according to some embodiments of the present invention.
5 is a diagram for illustratively explaining the configuration of a Verifiable Presentation (VP) according to some embodiments of the present invention.
6 is a diagram schematically illustrating an associated operation of a system performing re-verification according to some embodiments of the present invention.

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

Recently, drones are widely used in various fields such as personal hobbies, industrial use, and military use. For example, a delivery company may use a drone to deliver goods, a military official may use a drone to search a military area, and an individual may use a drone to photograph a user using a camera. Since drones for various purposes are developed and used for various purposes, it is unknown who controls the drone in flight and for what purpose it is flying. In addition, there is a risk that the drone is controlled by another person, and in the event of an accident caused by a drone, it is necessary to identify the person who operated the drone.

Accordingly, the Enforcement Decree of the Aviation Safety Act expanded the scope of drone aircraft reporting, and the Enforcement Rule of the Aviation Safety Act subdivided and regulated pilot qualification requirements according to the classification of drones. However, there are still cases where drones are operated by users who are not qualified to operate drones or who do not have the qualifications required to operate the drones. As a result, problems such as the risk of accidents and operation within restricted areas occur frequently. exist.

In order to solve the above problem, Korean Patent Registration No. 2228579 devised a drone user authentication method through biometric authentication. It is only for the purpose, but there is a limit that the drone pilot qualification cannot be verified.

Methods, systems and computer programs according to some embodiments of the present invention are described below with reference to FIGS. 1-6.

1 is a diagram for explaining a drone pilot qualification verification system using distributed identification according to some embodiments of the present invention, and FIG. 2 is a configuration of an issuing node, a verified node, and a verification node according to some embodiments of the present invention. It is a drawing for explaining.

Referring to FIG. 1 , the drone piloting qualification verification system using distributed identification (DID) according to an embodiment of the present invention includes an issuing node 100, a verified node 200, a verification node 300, and a registry 400. ) and the communication network 500. For convenience of description, it is assumed that the issuing node 100, the verified node 200, and the verification node 300 are separate entities from the blockchain network-based registry 400. However, in the present invention, all steps performed by nodes included in the blockchain network-based registry 400 may be performed by the issuing node 100, the verified node 200, and/or the verification node 300. can be interpreted as

The issuing node 100, the verified node 200, and the verifying node 300 have a mechanism for communicating with at least one node included in the registry 400 through the communication network 500, and the drone using the DID. It can mean any type of node in the steering qualification verification system. For example, the issuing node 100, the verified node 200, and the verifying node 300 may include microprocessors, mainframe computers, digital processors, portable devices, personal computers (PCs), laptop computers, workstations, and/or It may include any electronic device having network connectivity. In addition, the issuing node 100, the verified node 200, and the verifying node 300 may be implemented by at least one of an agent, an application programming interface (API), and a plug-in. May contain servers. Also, the issuing node 100, the verified node 200, and the verifying node 300 may include an application source and/or a client application.

The issuing node 100, the verified node 200, and the verifying node 300 may be computing devices included in an arbitrary registry 400 capable of performing arbitrary data processing and storage.

According to one embodiment, the issuing node 100 may be a node managed by an external authentication authority (issuer, eg, a government agency, Korea Transportation Safety Authority, etc.) that issues an identity certificate for an entity to be verified. That is, it may be a node associated with an entity that first performed identity and qualification authentication of the entity to be verified. According to an embodiment, the node to be verified 200 may be a node (terminal) managed by a user who wants to control a drone. That is, it may be a computing device managed by an entity to be verified. According to an embodiment, the verification node 300 may be a node (verifier) that is physically or logically connected to a drone to verify the qualifications of an entity to be verified (eg, a pilot).

Issuing node 100 and verifying node 300 may be associated with an issuing entity and a verifying entity seeking access to registry 400 . The node to be verified 200 is authenticated by the issuing node 100, verified by the verification node 300, and records identification information related to the identity of its own entity on the registry 400. can be related

The issuing node 100 may perform identity and qualification authentication for an entity to be verified related to the node to be verified 200 in response to a request of the node to be verified 200 . According to one embodiment, the issuing node 100 may be one or a plurality of nodes.

Each component of the system of FIG. 1 generates a PKI (Public Key Infrastructure)-based key pair (including a private key and a public key), and the private key is stored in the electronic wallet of the corresponding device. After storing, generating a DID document using a public key, and then storing it in a blockchain, a blockchain-based verification system can be used. Basically, a DID document contains information related to the identity subject, how this information can be verified, a set of public keys for the DID, a set of authentication protocols, and a set of service endpoints that can communicate or interact with the entity. can include One of the advantages of DID is that since DIDs are created and managed by individuals themselves, they can be managed so as not to include information that they deem unnecessary or do not want to be exposed. The DID document stored in the blockchain-based registry 400 can be shared with each configurator and related organizations of each configurator described above through a blockchain network.

According to some embodiments of the present invention, the blockchain-based registry 400 may mean a plurality of nodes that operate based on blockchain technology. Here, blockchain technology is a distributed storage technology that uses a storage structure in which blocks are connected in a chain form to store data to be managed in a plurality of nodes included in a blockchain network.

The blockchain-based registry 400 may store transactions transmitted from the issuing node 100, the verified node 200, and/or the verifying node 300 in block form based on a predetermined consensus algorithm. Data stored in block form may be shared by a plurality of nodes included in the registry 400 .

Depending on the type of implementation, the registry 400 may include a public blockchain network in which arbitrary nodes can perform consensus operation or a private blockchain network in which only predetermined nodes can perform consensus operation.

Consensus algorithms performed in the registry 400 according to some embodiments of the present invention include a Proof of Work (PoW) algorithm, a Proof of Stake (PoS) algorithm, a Delegated Proof of Stage (DPoS) algorithm, and a Practical Byzantine Fault Tolerance (PBFT) algorithm. Algorithm, Delegated Byzantine Fault Tolerance (DBFT) Algorithm, Redundant Byzantine Fault Tolerance (RBFT) Algorithm, Sieve Algorithm, Tendermint Algorithm, Paxos Algorithm, Raft Algorithm, PoA (Proof of Authority) Algorithm, and/or PoET (Proof of Elapsed Time) Algorithm can include

In some demonstrative embodiments of the present invention, nodes in registry 400 may operate by a blockchain core package according to a hierarchical structure. According to an embodiment, this hierarchical structure defines the structure of data handled in the registry 400, a data layer that manages data, performs mining that validates blocks and generates blocks, and informs miners in the mining process. Consensus layer in charge of handling paid fees, execution layer that processes and executes smart contracts, common layer that implements and manages P2P network protocols, hash functions, digital signatures, encoding, and common storage, and various applications are created and processed and a managed application layer.

According to an embodiment, the issuing node 100 , the verified node 200 , and/or the verifying node 300 may be nodes included in the registry 400 . In this example, the issuing node 100, the verified node 200, and/or the verifying node 300 perform at least one of a wallet function, a miner function, and a full blockchain data storage function. can be implemented.

According to one embodiment, the issuing node 100 , the verified node 200 , and/or the verifying node 300 may issue a query or transaction to the registry 400 . The query in the present invention can be used to search identification information of a registered receiver on the registry 400 . A transaction in the present invention may be used to update (modify/change/delete/add) data recorded on the registry 400.

According to an embodiment, the issuing node 100, the verified node 200, and/or the verifying node 300 may transmit and receive an application source written in a programming language. For example, the issuing node 100, the verified node 200, and/or the verifying node 300 may generate a client application by compiling an application source. For example, the generated client application may be transferred to the registry 400 and then executed.

According to one embodiment, the communication network 500 may include a Public Switched Telephone Network (PSTN), x Digital Subscriber Line (xDSL), Rate Adaptive DSL (RADSL), Multi Rate DSL (MDSL), and Very High Speed DSL (VDSL). Speed DSL), UADSL (Universal Asymmetric DSL), HDSL (High Bit Rate DSL), and various wired communication systems such as local area networks (LAN) may be used.

In addition, the communication network 500 presented in the present invention includes Code Division Multi Access (CDMA), Time Division Multi Access (TDMA), Frequency Division Multi Access (FDMA), Orthogonal Frequency Division Multi Access (OFDMA), SC-FDMA ( Single Carrier-FDMA) and other systems. The techniques described herein may be used not only in the networks mentioned above, but also in any type of other communication networks.

Referring to FIG. 2, the issuing node 100, the verified node 200, and the verifying node 300 according to an embodiment of the present invention include processors 110, 210, and 310, and memories 120, 220, and 320, respectively. ) and communication units 130, 230 and 330.

The processors 110, 210, and 310 may be composed of one or more cores, and include a central processing unit (CPU), a general purpose graphics processing unit (GPGPU), and a tensor processing unit ( It may include any type of processor for performing identity and qualification authentication by executing instructions stored in memory, such as a tensor processing unit (TPU). A processor may read a computer program stored in memory to perform identity and entitlement authentication in accordance with some embodiments of the present invention. The processor may control overall operations of components of the issuing node 100, the verified node 200, and the verifying node 300 in order to proceed with the identity and qualification authentication process.

The memories 120, 220, and 320 may store programs for operation of the processors 110, 210, and 310, and may temporarily or permanently store input/output data. Memory is a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (eg SD or XD memory, etc.), RAM (Random Access Memory, RAM), SRAM (Static Random Access Memory), ROM (Read-Only Memory, ROM), EEPROM (Electrically Erasable Programmable Read-Only Memory), PROM (Programmable Read-Only Memory), magnetic memory, magnetic disk, optical disk At least one type of storage medium may be included. These memories 120, 220, and 320 may be operated under the control of the processors 110, 210, and 310.

The communication units 130, 230, and 330 may include a wired/wireless Internet module for network access. The communication units 130, 230, and 330 may communicate with at least one of the issuing node 100, the verified node 200, the verification node 300, the registry 400, and nodes included in other blockchain networks. can Wireless Internet technologies include wireless LAN (WLAN) (Wi-Fi), wireless broadband (Wibro), world interoperability for microwave access (Wimax), high speed downlink packet access (HSDPA), and the like. As a wired Internet technology, XDSL (Digital Subscriber Line), FTTH (Fibers to the home), PLC (Power Line Communication), and the like may be used.

The aforementioned components are exemplary and the scope of the present invention is not limited to the aforementioned components. That is, of course, additional components may be included or some of the aforementioned components may be omitted according to implementation aspects of the embodiments of the present invention.

3 is a diagram for schematically explaining the linked operation of a drone pilot qualification verification system using distributed identity verification according to some embodiments of the present invention, and FIG. 4 is a diagram of VC (Verifiable Credential) 5 is a diagram for illustratively explaining a configuration of a Verifiable Presentation (VP) according to some embodiments of the present invention.

Referring to FIG. 3 , the system, method, and program according to some embodiments of the present invention verify the piloting qualification of the entity to be verified (eg, pilot) using the DID, and grant control authority to the drone. .

In step S1000, the issuing node 100, the verified node 200, and the verifying node 300 store distributed identifiers (DID_ISSUER, DID_HOLDER, and DID_VERIFIER) for the issuing entity, the verified entity, and the verifying entity, respectively, in the registry 400. can register. As described above, the issuing entity refers to an authority issuing a certificate (eg, Korea Transportation Safety Authority), the entity to be verified refers to a user who wants to pilot a drone, and the verification entity refers to the certification of the entity to be verified ( It may refer to a drone (or a device associated with a drone) that performs identity verification.

In step S2000, the node to be verified 200 may transmit a VC issuance request (CLAIM) to the issuing node 100. That is, the verified node 200 that delivers the VC issuance request (CLAIM) to the issuing node 100, which is the issuer of the qualification, is the verified subject (entity) or holder that owns and manages the VC. can be

In step S3000, the issuing node 100 may issue a VC for the entity to be verified and transmit the VC to the node to be verified 200 in response to the VC issuance request (CLAIM). At this time, the issuing node 100 checks the details of the VC issuance request (CLAIM), checks whether or not the qualification for the requested item exists, and if the qualification of the entity to be verified is confirmed, issues the VC to verify It can be delivered to node 200.

Referring to FIG. 4, the VC issued by the issuing node 100 and managed by the verified node 200 includes VC metadata (CREDENTIAL METADATA), VC issuance request (CLAIM), and VC proof (PROOF). can do.

In the VC metadata (CREDENTIAL METADATA), metadata such as information about the issuer (Issuer, issuing node 100), expiration (validity) period of qualification, and issuance time may be recorded. In the VC issuance request (CLAIM), information about the claim requested by the holder (Holder, node to be verified 200) may be recorded as it is. For example, the VC issuance request (CLAIM) may include ID information, qualification information, learning information, and the like of the entity to be verified. A signature value (for example, a private key of the issuing node 100) for verifying the VC may be recorded in the VC proof (PROOF).

According to one embodiment, the VC may include information such as unmanned aerial vehicle qualification information and unmanned aerial vehicle training completion information of the entity to be verified, pilot experience, total pilot time, recent pilot history, pilot permitted area, and the like.

Referring back to FIG. 3 , in step S4000 , the node to be verified 200 may transmit a drone access request (RQ_ACCESS) to the verification node 300 . The access request (RQ_ACCESS) may include a control request for a drone.

In step S5000, the verification node 300 may transmit a VP issuance request (RQ_VP) to the node to be verified 200 in response to the access request (RQ_ACCESS). The verification node 300, which is a management entity of the drone, may request, from the node to be verified 200, a VP in which information such as specifications of the corresponding drone is stored and qualification information for controlling the corresponding drone is included.

In step S6000, the node to be verified 200 may generate a VP in response to the VP issuance request (RQ_VP) and transmit it to the verification node 300.

Referring to FIG. 5 , VP may include VP metadata (PRESENTATION METADATA), VC, and VP proof (PROOF).

In the VP metadata (PRESENTATION METADATA), metadata of the VP, such as information about the entity to be verified (Holder, the node to be verified 200), which is the management subject of the VC, and the type of the VP, may be recorded. In the VC, information on the VC issued by the node to be verified 200 from the issuing node 100 may be recorded as it is. According to an embodiment, one VP may include a plurality of VCs. That is, when there are several credentials required for verification, a plurality of VCs may be included in the VP. A signature value for verifying the VP (for example, a private key of the node 200 to be verified) may be recorded in the VP proof (PROOF).

Referring back to FIG. 3 , in step S7000 , the verification node 300 may perform a verification procedure on the VP acquired from the node to be verified 200 . As shown, verification of the VP may be performed using the blockchain-based registry 400 .

In step S8000, if the verification of the VP succeeds (if the qualification conditions are satisfied), the verification node 300 may grant the drone control authority (AUTHORITY_CONTROL) to the verified node 200. Conversely, if verification of the VP fails (if the qualification condition is not satisfied), the verification node 300 may not grant control authority (AUTHORITY_CONTROL) for the drone to the verified node 200. According to an embodiment, the verification node 300 may provide a verification failure message to the verified node 200 .

According to an embodiment, the control authority (AUTHORITY_CONTROL) may include power on/off authority of the drone and driving authority of the drone. That is, only the node to be verified 200 whose identity has been verified may be authorized to supply power to the drone and perform control.

According to an embodiment, if the VP includes the VC including information such as the qualification for piloting the unmanned aerial vehicle of the entity to be verified, the piloting experience, the total piloting time, and the recent piloting history, the value assigned to the node to be verified 200 The piloting authority may include authority for the driving altitude or driving speed of the drone determined based on the VC. For example, a criterion (range) for piloting experience, piloting time, elapsed time from a recent piloting date, etc. is set, and the authority for driving altitude or driving speed that meets the criteria is given to the node to be verified 200, that is, the pilot. This can reduce the risk of pilot accidents.

According to an embodiment, when the VP includes a VC including information on a permitted area for manipulation of an entity to be verified, the manipulation authority granted to the node to be verified 200 includes the authority for a permitted area based on the VC. and if it is determined that it is out of the permitted area, the verification node 300 may transmit a warning notification to the verified node 200 . According to an embodiment, the verification node 300 may activate RTH (Return To Home) of the drone when the number of times the drone leaves the permitted area reaches a predetermined reference number.

According to some embodiments of the present invention, by verifying DID-based drone piloting qualification and granting control authority (AUTHORITY_CONTROL) only to verified users, reliable verification is possible and the risk of accidents due to unqualified piloting can be prevented. there is.

6 is a diagram schematically illustrating an associated operation of a system performing re-verification according to some embodiments of the present invention. Since re-verification is an embodiment after the first verification of the entity to be verified is successful, a description of the process described with reference to FIG. 3 will be omitted.

Referring to FIG. 6 , in step S9100, the verification node 300 may transmit a VP reissue request (RQ_VP) to the node to be verified 200 when a predefined additional verification condition is satisfied.

According to an embodiment, the additional verification condition may be set to be satisfied when a preset time is reached after the previous verification. For example, 10 minutes after the initial verification is performed, the verification node 300 may transmit a VP reissue request (RQ_VP) to the verified node 200 . In addition, when the same time (eg, 10 minutes) has elapsed after re-validation, the VP reissue request (RQ_VP) may be transmitted again. According to an embodiment of the present invention, by periodically performing re-verification, it is possible to improve reliability and stability by preventing another user (operator) from controlling the drone after the initial verification.

According to an embodiment, the additional verification condition may include a condition for the driving state of the drone. For example, when the hovering duration of the drone reaches a predetermined time (eg, 1 minute), the additional verification condition is satisfied, and the verification node 300 is the VP as the verified node 200. A reissue request can be sent. As another example, when the flight speed of the drone is less than a predetermined reference speed, an additional verification condition may be set to be satisfied. According to an embodiment of the present invention, it is possible to secure stability of piloting and perform identity verification by determining whether or not to perform VP re-verification according to the driving state of the drone.

In step S9200, the node to be verified 200 provides the VP to the verification node 300 in response to the VP reissue request (RQ_VP), and in step S9300, the verification node 300 performs a verification operation of the VP using the registry 400. can be performed. Steps S9200 and S9300 are implemented substantially the same as steps S6000 and S7000 described with reference to FIG. 3, respectively, and thus detailed descriptions thereof are omitted.

According to an embodiment, if the re-verification of the VP is successful, the control authority (AUTHORITY_CONTROL) granted to the node to be verified 200 may be maintained, and if the re-verification of the VP is unsuccessful, the control authority (AUTHORITY_CONTROL) may be retrieved. According to one embodiment, in case of failure, the verification node 300 may activate RTH of the drone.

Various embodiments of this document and terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, like reference numbers may be used for like or related elements. The singular form of a noun corresponding to an item may include one item or a plurality of items, unless the relevant context clearly dictates otherwise. In this document, "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, Each of the phrases such as "at least one of B or C" may include any one of the items listed together in the corresponding one of the phrases, or all possible combinations thereof. Terms such as "first" and "second" may simply be used to distinguish a corresponding component from other corresponding components, and do not limit the corresponding components in other respects (eg, importance or order).

The term "module" used in this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be an integrally constructed component or a minimal unit of components or a portion thereof that performs one or more functions. For example, according to one embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of this document include one or more instructions stored in a storage medium readable by a machine (eg, the issuing node 100, the verified node 200, and the verifying node 300). It can be implemented as software that For example, processors (eg, processors 110, 210, 310) of devices (eg, issuing node 100, verified node 200, and verifying node 300) may include one or more instructions stored from a storage medium. At least one of these commands can be invoked and executed. This enables the device to be operated to perform at least one function according to the at least one command invoked. 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-temporary' only means that the storage medium is a tangible device and does not contain a signal (e.g. electromagnetic wave), and this term refers to the case where data is stored semi-permanently in the storage medium. It does not discriminate when it is temporarily stored.

According to one embodiment, the method according to various embodiments disclosed in this document may be included and provided in a computer program product. Computer program products may be traded between sellers and buyers as commodities. A computer program product is distributed in the form of a device-readable storage medium (eg compact disc read only memory (CD-ROM)), or through an application store or between two user devices (eg smartphones). It can be distributed (e.g., downloaded or uploaded) directly or online. In the case of online distribution, at least part of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium such as a manufacturer's server, an application store server, or a relay server's memory.

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

Claims (16)

A computer program stored on a computer readable storage medium, the computer program including instructions for causing a processor of a verification node to perform the following steps:
generating a decentralized identifier (DID) for the verification entity;
In response to an access request obtained from a node to be verified, requesting a verifiable presentation (VP) for an entity to be verified to the node to be verified, wherein the access request includes a control request for a drone controlled by the node to be verified. ;
verifying the VP through a blockchain network-based registry when the VP is obtained from the node to be verified; and
When the verification of the VP is successful, granting control authority for the drone to the verified node.
A computer program stored on a computer-readable storage medium.
The method of claim 1,
The control authority includes power on/off authority of the drone and driving authority of the drone.
A computer program stored on a computer-readable storage medium.
The method of claim 2,
The VP includes a Verifiable Credential (VC) including at least one information of an unmanned aerial vehicle piloting qualification, a piloting career, a total piloting time, and a recent piloting history of the entity to be verified,
The driving authority includes authority for the driving altitude of the drone or the driving speed of the drone determined based on at least one information of the piloting history, total piloting time, and recent piloting history.
A computer program stored on a computer-readable storage medium.
The method of claim 2,
The VP includes a Verifiable Credential (VC) including information about the unmanned aerial vehicle piloting qualification of the entity to be verified and the pilot area of the entity to be verified,
The driving authority includes authority for the steering permitted area,
A computer program stored on a computer-readable storage medium.
The method of claim 4,
These steps are
Further comprising transmitting a warning notification to the verified node when it is determined that the drone is out of the pilot permitted area.
A computer program stored on a computer-readable storage medium.
The method of claim 5,
These steps are
Further comprising activating RTH (Return To Home) of the drone when the number of times the drone leaves the pilot permitted area reaches a preset reference number,
A computer program stored on a computer-readable storage medium.
The method of claim 1,
These steps are
re-requesting the VP to the node to be verified when a predefined additional verification condition is satisfied;
re-verifying the VP through the registry when the VP is obtained; and
Maintaining the control authority if the re-verification of the VP is successful, and recovering the control authority and activating RTH (Return To Home) of the drone if the re-verification of the VP fails,
A computer program stored on a computer-readable storage medium.
The method of claim 7,
The additional verification condition is satisfied when a predetermined time is reached after the previous verification,
A computer program stored on a computer-readable storage medium.
The method of claim 7,
The additional verification condition includes a condition for the driving state of the drone.
A computer program stored on a computer-readable storage medium.
The method of claim 9,
The additional verification condition is satisfied when the hovering duration of the drone reaches a preset time,
A computer program stored on a computer-readable storage medium.
The method of claim 7,
The additional verification condition is satisfied when the driving speed of the drone is less than a preset speed,
A computer program stored on a computer-readable storage medium.
A computer program stored on a computer readable storage medium, the computer program including instructions for causing a processor of a node under test to perform the following steps, the steps:
generating a decentralized ID (DID) for the entity to be verified;
requesting issuance of a Verifiable Credential (VC) to an issuing node using the DID;
when obtaining the VC for the entity to be verified from the issuing node, providing an access request including a control request of a drone to a verification node, wherein the drone is controlled by the verification node;
generating a VP of the entity to be verified including the VC when receiving a request for a verifiable presentation (VP) of the entity to be verified from the verification node, and providing the generated VP to the verification node;
If the verification of the VP is successful, obtaining a control authority for the drone from the verification node.
A computer program stored on a computer-readable storage medium.
The method of claim 12,
The VC includes at least one information of unmanned aerial vehicle qualification information and unmanned aerial vehicle training completion information of the entity to be verified.
A computer program stored on a computer-readable storage medium.
The method of claim 12,
The control authority includes power on/off authority of the drone and driving authority of the drone.
A computer program stored on a computer-readable storage medium.
The method of claim 14,
The VC includes information on at least one of unmanned aerial vehicle qualification information, unmanned aerial vehicle training completion information, pilot career, total pilot time, and recent pilot history of the entity to be verified,
The driving authority includes authority for the driving altitude of the drone or the driving speed of the drone determined based on at least one information of the piloting history, total piloting time, and recent piloting history.
A computer program stored on a computer-readable storage medium.
The method of claim 14,
The VC includes unmanned aerial vehicle qualification information, unmanned aerial vehicle training completion information of the entity to be verified, and information on a pilot permitted area of the entity to be verified,
The driving authority includes authority for the steering permitted area,
A computer program stored on a computer-readable storage medium.