Authentication system, authentication method, and program

Abstract

This authentication system comprises a certificate authority, a central control system, a group including a drone serving as a parent device and a drone serving as a child device, a management system, and an external system. The central control system includes a first authentication information transmission unit for transmitting first authentication information received from the certificate authority to the parent device; the parent device includes an authentication unit for executing authentication with the child device belonging to the same group and a second authentication information transmission unit for transmitting second authentication information, including a first token with an expiration time and the first authentication information, to the authenticated child device; the management system includes an authentication unit for executing authentication with the external system and a third authentication information transmission unit for transmitting third authentication information, including a second token and the first authentication information received from the certificate authority, to the authenticated external system; and the child device and the external system include an authentication unit for executing authentication on the basis of the second authentication information and the third authentication information.

Description

[Technical Field]

[0001] The present invention relates to an authentication system, an authentication method, and a program for authenticating an unmanned aerial vehicle. [Background technology]

[0002] In services using unmanned aerial vehicles (vehicles or transport machines without people on board), it is being considered that unmanned aerial vehicles could form groups to provide services, and it is expected that there will be a need to securely manage a huge number of unmanned aerial vehicles in the future.

[0003] When managing drones, a highly flexible management method is required, such as a group of drones sharing their sub-units among themselves depending on the situation.

[0004] As a method for realizing authentication of IoT devices and unmanned aerial vehicles, a system has been disclosed in which a central system distributes digital certificates and private keys to IoT devices and unmanned aerial vehicles (Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] Prodrone Co., Ltd., "Demonstration experiment begins to strengthen drone communication security ~ GMO GlobalSign's security technology makes the sky secure ~" [online], May 14, 2021, Prodrone Co., Ltd., [Retrieved June 20, 2022], Internet <URL: https: / / www.prodrone.com / jp / release / 7589 / > Summary of the Invention [Problem to be solved by the invention]

[0006] Figure 1 shows an example of the configuration of a service provision system using unmanned aircraft that may be realized in the future. As shown in the figure, this example configuration includes a central control system 92 and N groups 93 (93-1, ..., 93-n, ..., 93-N, where N is an integer equal to or greater than 1), each group 93 including a parent device 931 and a child device 932. A parent device 931 belonging to the nth group is represented as parent device 931-n.

[0007] For convenience, in the figure, the number of slave devices 932 in each group is M (M is an integer equal to or greater than 1), but the number of slave devices 932 may differ for each group. A slave device 932 that belongs to the nth group and is the mth slave device within the group is represented as slave device 932-nm. This notation method will also be followed in the embodiments described below.

[0008] In order for drones to communicate securely with each other or with other systems, it is necessary to distribute authentication information that can identify each drone, but when the values ​​of N and M in Figure 1 are large, that is, when there are a huge number of drones, it is difficult to centrally manage the authentication information and permissions of all drones.In addition, when groups are recombined, authentication information and permissions must be appropriately controlled, but when there are a huge number of groups, central management is difficult.

[0009] Therefore, an object of the present invention is to provide an authentication system that can centrally manage the authentication information and authorizations of unmanned aerial vehicles and groups of unmanned aerial vehicles, even if there are a huge number of unmanned aerial vehicles or groups of unmanned aerial vehicles to be managed. [Means for solving the problem]

[0010] The authentication system of the present invention includes an authentication authority, a central control system, a group including a parent unmanned aerial vehicle and a child unmanned aerial vehicle, a management system, and an external system.

[0011] The central control system includes a first authentication information transmitting unit that transmits the first authentication information received from the authentication authority to the parent device.

[0012] The parent device includes an authentication unit that performs authentication with child devices that belong to the same group, and a second authentication information transmission unit that transmits second authentication information including a first token with an expiration date and first authentication information to the authenticated child device.

[0013] The management system includes an authentication unit that performs authentication with the external system, and a third authentication information transmission unit that transmits third authentication information including the second token and the first authentication information received from the authentication authority to the authenticated external system.

[0014] The slave device and the external system each include an authentication unit that performs authentication based on the second authentication information and the third authentication information. [Effects of the Invention]

[0015] According to the authentication system of the present invention, even if there are a huge number of unmanned aerial vehicles or groups of unmanned aerial vehicles to be managed, their authentication information and authorizations can be managed centrally. [Brief explanation of the drawings]

[0016] [Figure 1] A diagram showing an example of the configuration of a service provision system using unmanned aircraft that may be realized in the future. [Figure 2] FIG. 1 is a block diagram showing the functional configuration of an authentication system according to a first embodiment. [Figure 3] FIG. 2 is a block diagram showing the functional configuration of a certificate authority according to the first embodiment. [Figure 4] FIG. 2 is a block diagram showing the functional configuration of the central control system according to the first embodiment. [Figure 5] FIG. 2 is a block diagram showing the functional configuration of the parent device according to the first embodiment. [Figure 6] FIG. 2 is a block diagram showing the functional configuration of the slave device according to the first embodiment. [Figure 7] FIG. 1 is a block diagram showing the functional configuration of a management system according to a first embodiment. [Figure 8] FIG. 2 is a block diagram showing the functional configuration of an external system according to the first embodiment. [Figure 9] FIG. 2 is a diagram showing an outline of the operation of the authentication system according to the first embodiment. [Figure 10]FIG. 3 is a sequence diagram showing the operation of the authentication system according to the first embodiment. [Figure 11] FIG. 10 is a block diagram showing the functional configuration of an authentication system according to a second embodiment. [Figure 12] FIG. 10 is a block diagram showing the functional configuration of a certificate authority according to a second embodiment. [Figure 13] FIG. 10 is a block diagram showing the functional configuration of a central control system according to a second embodiment. [Figure 14] FIG. 10 is a block diagram showing the functional configuration of a parent device according to a second embodiment. [Figure 15] FIG. 10 is a block diagram showing the functional configuration of a slave unit according to a second embodiment. [Figure 16] FIG. 10 is a block diagram showing the functional configuration of a management system according to a second embodiment. [Figure 17] FIG. 10 is a block diagram showing the functional configuration of an external system according to a second embodiment. [Figure 18] FIG. 10 is a sequence diagram showing the operation of the authentication system according to the second embodiment. [Figure 19] FIG. 10 is a block diagram showing the functional configuration of an authentication system according to a third embodiment. [Figure 20] FIG. 2 is a diagram showing an example of the functional configuration of a computer. DETAILED DESCRIPTION OF THE INVENTION

[0017] Hereinafter, embodiments of the present invention will be described in detail. Components having the same functions are given the same numbers, and duplicated explanations will be omitted. [Example]

[0018] The configuration of the authentication system 1 of the first embodiment will be described below with reference to Fig. 2. As shown in the figure, the authentication system 1 of the present embodiment includes an authentication authority 11, a central control system 12, a parent device 131, a child device 132, a management system 14, and an external system 15. The parent device 131, the child device 132, and the external system 15 are placed in a secure environment such as a TEE or SE, and each block is shown enclosed in square brackets to indicate that they are placed in a secure environment.

[0019] The system includes N groups 13 (groups 13-1, ..., 13-n, ..., 13-N, where N is an integer equal to or greater than 1) each including one parent device 131 and M child devices 132. A plurality of parent devices 131 may belong to one group. The number of child devices 132 may differ for each group.

[0020] A parent device 131 belonging to the nth group is represented as a parent device 131-n, and a child device 132 belonging to the nth group and corresponding to the mth device in the group is represented as a child device 132-nm. When expressed as a parent device 131 and a child device 132 without adding a sub-number, this refers to any parent device or child device.

[0021] The functional configuration of the certification authority 11 will be described below with reference to Fig. 3. The certification authority 11 includes a first authentication information issuance request receiving unit 111, a first authentication information transmitting unit 112, a first authentication information issuance request receiving unit 113, and a first authentication information transmitting unit 134.

[0022] The functional configuration of the central control system 12 will be described below with reference to Fig. 4. The central control system 12 includes a first authentication information issuance request transmitting unit 121, a first authentication information receiving unit 122, and a first authentication information transmitting unit 123. When the central control system 12 is configured with a plurality of devices, each of the components (121 to 123) may be a separate device. Alternatively, the central control system 12 may be configured with a device having two of the functions of the components and a device having one of the functions of the components.

[0023] 5, the functional configuration of parent device 131 will be described. Parent device 131 includes first authentication information receiving unit 1311, authentication unit 1312, and second authentication information transmitting unit 1313.

[0024] 6, the functional configuration of the child device 132 will be described. The child device 132 includes an authentication unit 1321, a second authentication information receiving unit 1322, a communication request transmitting unit 1323, an authentication unit 1324, and a service providing unit 1325.

[0025] The functional configuration of the management system 14 will be described below with reference to Fig. 7. The management system 14 includes a first authentication information issuance request transmitting unit 141, a first authentication information receiving unit 142, an authentication unit 143, and a third authentication information transmitting unit 144. When the management system 14 is configured with multiple devices, each of the components (141 to 144) may be a separate device. Alternatively, the management system 14 may be configured with a device having the functions of two or more of the components and a device that functions as the other components.

[0026] The functional configuration of the external system 15 will be described below with reference to Fig. 8. The external system 15 includes an authentication unit 151, a third authentication information receiving unit 152, a communication request receiving unit 153, an authentication unit 154, and a service receiving unit 155. When the external system 15 is configured with a plurality of devices, each of the components (151 to 155) may be a separate device. Also, the external system 15 may be configured with a device having the functions of two or more of the components and a device functioning as the other components.

[0027] 9, the authentication system 1 of this embodiment is characterized in that the authority management is hierarchically structured, and the central control system 12 manages only the authentication information (first authentication information 5, in the same figure) of the parent device 131. Any authentication information can be used as the first authentication information, but for example, when the system is configured using an ID-based encryption method, the first authentication information is equal to the secret key (see Example 2 for details).

[0028] The parent device 131 is equipped with a secure environment such as a secure element (SE) or a trusted execution environment (TEE), and manages and distributes authentication information (second authentication information 6, in the same figure) of the child device 132.

[0029] Only authentication information (fourth authentication information 7, in the same figure) that allows parent device 131 and parent device 132 to mutually confirm that they are legitimate terminals is distributed to child device 132 in advance. Examples of the fourth authentication information 7 include a pre-shared key and image recognition using physical characteristics. For example, as shown in the same figure, if child device 132-1-M that belonged to group 13-1 is reassigned to group 13-n, parent device 131-n of group 13-n distributes the fourth authentication information 7 to the newly assigned child device 132-1-M in advance, enabling them to mutually confirm that they are legitimate terminals.

[0030] Also, the management system 14 distributes in advance authentication information (fifth authentication information A, FIG. 1) used for authentication with the external system 15.

[0031] The operation of each device in the authentication system 1 of this embodiment will be described below for each component based on the sequence of FIG.

[0032] <Central Control System 12 - First Authentication Information Issuance Request Transmitter 121> First, the first authentication information issuance request transmitting unit 121 of the central control system 12 transmits a first authentication information issuance request to the certificate authority 11 (S121).

[0033] <Certification Authority 11-First Authentication Information Issuance Request Receiving Unit 111> The first authentication information issuance request receiving unit 111 of the certificate authority 11 receives the first authentication information issuance request from the central control system 12 (S111).

[0034] <Certification Authority 11 - First Authentication Information Transmission Unit 112> The first authentication information transmitting unit 112 of the certificate authority 11 issues the first authentication information and transmits it to the central control system 12 (S112).

[0035] <Central Control System 12 - First Authentication Information Receiving Unit 122> The first authentication information receiving unit 122 of the central control system 12 receives the first authentication information from the authentication authority 11 (S122).

[0036] <Central Control System 12 - First Authentication Information Transmitting Unit 123> The first authentication information transmitting unit 123 of the central control system 12 transmits the first authentication information received from the authentication station 11 to the parent device 131 (S123).

[0037] <Base Device 131-First Authentication Information Receiving Unit 1311> The first authentication information transmitting unit 1311 of the master device 131 receives the first authentication information from the central control system 12 (S1311).

[0038] <Base unit 131 - Authentication unit 1312> The authentication unit 1312 of the parent device 131 performs authentication with the child device 132 that belongs to the same group (S1312). The authentication uses the fourth authentication information 7 (FIG. 9) described above. It is preferable that the parent device 131 performs authentication with the child device 132 using near field communication (Bluetooth (registered trademark), NFC, etc.).

[0039] This system has a feature not found in conventional authentication systems in that the parent device 131, which is an unmanned aircraft, functions as an intermediate certification authority. As a result, the unmanned intermediate certification authority itself can move (navigate, drive, fly) and establish proximity communication with the child device 132. This reduces the risk of impersonation or operational errors, and enables secure communication to be established in a way not found in conventional authentication systems.

[0040] <Remote Device 132 - Authentication Unit 1321> The authentication unit 1321 of the child device 132 performs authentication with the parent device 131 that belongs to the same group (S1321). The authentication uses the fourth authentication information 7 (FIG. 9) described above. It is preferable that the child device 132 performs authentication with the parent device 131 using near-field communication.

[0041] <Base Device 131-Second Authentication Information Transmission Unit 1313> The second authentication information transmission unit 1313 of the parent device 131 transmits the second authentication information including the first token with an expiration date and the first authentication information to the child device 132 that has been authenticated in steps S1312 and S1321 (S1313). It is preferable that the second authentication information transmission unit 1313 of the parent device 131 transmits the second authentication information to the child device 132 using near-field communication.

[0042] The first token is preferably a one-time token that is issued by the parent device 131 to the child device 132. Authentication and authorization information and an expiration date are written in the one-time token so that it can be confirmed that the external system 15 is a legitimate party. For example, if the system is configured using an ID-based encryption method, the first token may be set to the ID of the child device 132.

[0043] <Second Authentication Information Receiving Unit 1322 of Child Device 132> The second authentication information receiving unit 1322 of the child device 132 that has been authenticated in steps S1312 and S1321 receives the second authentication information from the parent device 131 (S1322). It is preferable that the second authentication information receiving unit 1322 receives the second authentication information using near-field communication.

[0044] <Management System 14 - First Authentication Information Issuance Request Transmitting Unit 141> The first authentication information issuance request transmitting unit 141 of the management system 14 transmits a first authentication information issuance request to the certificate authority 11 (S141).

[0045] <Certification Authority 11 - First Authentication Information Issuance Request Receiving Unit 113> The first authentication information issuance request receiving unit 113 of the certificate authority 11 receives the first authentication information issuance request from the management system 14 (S113).

[0046] <Certification Authority 11 - First Authentication Information Transmission Unit 114> The first authentication information transmitting unit 114 of the certificate authority 11 issues the first authentication information and transmits it to the management system 14 (S114).

[0047] <Management System 14 - First Authentication Information Receiving Unit 142> The first authentication information receiving unit 142 of the management system 14 receives the first authentication information from the certification authority 11 (S142).

[0048] <External System 15 - Authentication Unit 151> The authentication unit 151 of the external system 15 executes authentication with the management system 14 (S151). For the authentication, the above-mentioned fifth authentication information A (FIG. 9) is used.

[0049] <Management System 14 - Authentication Unit 143> The authentication unit 143 of the management system 14 executes authentication with the external system 15 (S143). The above-mentioned fifth authentication information A (FIG. 9) is used for the authentication.

[0050] <Management System 14 - Third Authentication Information Transmission Unit 144> The third authentication information transmitting unit 144 of the management system 14 transmits the third authentication information including the second token and the first authentication information received from the certification authority 11 to the authenticated external system 15 (S144). For example, when the system is configured using an ID-based encryption method, the second token may be set to the ID of the external system 15.

[0051] <External System 15 - Third Authentication Information Receiving Unit 152> The third authentication information receiving unit 152 of the external system 15 receives the third authentication information from the management system 14 (S152).

[0052] <Slave 132 - Communication request transmission unit 1323> The communication request transmitting unit 1323 of the child device 132 transmits a communication request to the external system 15 (S1323).

[0053] <External System 15 - Communication Request Receiving Unit 153> The communication request receiving unit 153 of the external system 15 receives the communication request from the slave device 132 (S153).

[0054] <External System 15 - Authentication Unit 154> The authentication unit 154 of the external system 15 performs authentication with the slave device 132 that is the sender of the communication request based on the second authentication information and the third authentication information (S154). For example, when the system is configured using an ID-based encryption method, authentication can be performed using the ID of the slave device 132, the ID of the external system 15, and a private key, using the method described in Reference Patent Document 1.

[0055] (Reference Patent Document 1: JP 2021-019223 A) <Remote Device 132 - Authentication Unit 1324> The authentication unit 1324 of the slave device 132 performs authentication with the external system 15, which is the destination of the communication request, based on the second authentication information and the third authentication information (S1324). As in step S154, when the system is configured using the ID-based encryption method, authentication can be performed using the method described in Reference Patent Document 1.

[0056] <Handset 132-Service Provider 1325> The service providing unit 1325 of the authenticated slave device 132 provides the service to the authenticated external system (S1325). A typical example of the service is a logistics service. A specific example of the external system 15 is a luggage storage system.

[0057] <External System 15 - Service Receiving Unit 155> The service receiving unit 155 of the authenticated external system 15 receives the service from the authenticated slave unit 132 (S155). In the case of a logistics service, this operation corresponds to receiving a package. [Example]

[0058] The functional configuration of an authentication system 2 according to a second embodiment, which is the authentication system 1 according to the first embodiment configured using the ID-based encryption method, will be described below with reference to Fig. 11. As shown in the figure, the authentication system 1 according to the second embodiment includes an authentication authority 21, a central control system 22, a parent device 231, a child device 232, a management system 24, and an external system 25.

[0059] In this embodiment, the unmanned aerial vehicles (parent device 231, child device 232) are drones, the management system 24 is a smart locker management system, and the external system 25 is a smart locker. The first authentication information is a private key, the first token is the ID of the child device, and the second token is the ID of the external system, and the child device 232 and the external system 25 perform authentication using an ID-based encryption method based on the ID of the child device 232, the ID of the external system 25, and the private key.

[0060] 12 to 17 show the functional configuration of each device and system. The names of the components of each device and system are the same as those in the first embodiment, but some of the reference numerals have been changed.

[0061] More specifically, the certificate authority 21 includes a first authentication information issuance request receiving unit 211, a first authentication information transmitting unit 212, a first authentication information issuance request receiving unit 213, and a first authentication information transmitting unit 234; the central control system 22 includes a first authentication information issuance request transmitting unit 221, a first authentication information receiving unit 222, and a first authentication information transmitting unit 223; the master device 231 includes a first authentication information receiving unit 2311, an authentication unit 2312, and a second authentication information transmitting unit 2313; , an authentication unit 2321, a second authentication information receiving unit 2322, a communication request sending unit 2323, an authentication unit 2324, and a service providing unit 2325, the management system 24 includes a first authentication information issuance request sending unit 241, a first authentication information receiving unit 242, an authentication unit 243, and a third authentication information sending unit 244, and the external system 25 includes an authentication unit 251, a third authentication information receiving unit 252, a communication request receiving unit 253, an authentication unit 254, and a service receiving unit 255.

[0062] The master device 231, slave device 232, and external system 25 are placed in a secure environment such as a TEE or SE, and each block is enclosed in square brackets to indicate that they are placed in a secure environment. In this embodiment, an intermediate key issuing center (intermediate KGC) under the control of the certificate authority 21, which is the root key issuing center (KGC), is placed in the secure environment of the master device 231 and in the management system 24.

[0063] The operation of each device in the authentication system 2 of this embodiment will be described below based on the sequence of FIG.

[0064] <Steps S221, S211, S212, S222, S223, S2311> In steps S121, S111, S112, S122, S123, and S1311 of the first embodiment, the operations in which the first authentication information is replaced with the private key are executed by the components of the same name.

[0065] <Steps S2312, S2321> The same operations as steps S1312 and S1321 in the first embodiment are executed by the components with the same names.

[0066] <Steps S2313, S2322> In steps S1313 and S1322 of the first embodiment, the operations are executed by the configuration elements of the same name, with the first token replaced with the distributor information, the ID (public key) of the slave device 232 incorporating the authority expiration date, and the first authentication information replaced with the private key.

[0067] <Steps S241, S213, S214, S242> In steps S141, S113, S114, and S142 of the first embodiment, the operations in which the first authentication information is replaced with the private key are executed by the components of the same name.

[0068] <Steps S251, S243> The same operations as steps S151 and S143 in the first embodiment are executed by the components with the same names.

[0069] <Steps S244 and S252> In steps S144 and S152 of the first embodiment, the operations in which the second token is replaced with the ID of the external system 25 (smart locker) and the first authentication information is replaced with the private key are executed by the components with the same names.

[0070] <Steps S2323, S253> The same operations as steps S1323 and S153 in the first embodiment are executed by the same components.

[0071] <Steps S2324, S254> In steps S2324 and S254, authentication can be performed by the method described in Patent Document 1 using the ID of the slave device 232, the ID of the external system 25 (smart locker), and a private key.

[0072] <Steps S2325, S255> The same operations as steps S1325 and S155 in the first embodiment are executed by the same constituent elements. In this embodiment, the service involves delivery of packages by drone formation, so these steps correspond to handing over and receiving of the delivery.

[0073] According to the authentication systems 1 and 2 of the first and second embodiments, even if there are a huge number of drones or drone groups to be managed, the cost of managing each drone can be reduced, and the authentication information and authorizations can be managed centrally. In addition, the assignment of drone groups can be changed at any time. [Example]

[0074] 19, the unmanned aerial vehicles (parent and child aerial vehicles) that appeared in the first and second embodiments may not be autonomously moving unmanned aerial vehicles, but may be replaced with fixedly installed IoT devices 331 and 332. As shown in the figure, the authentication system 3 of the third embodiment is configured by replacing the unmanned aerial vehicles (parent and child aerial vehicles) in the first embodiment with IoT devices (parent and child aerial vehicles 331 and 332).

[0075] <Modification> The authentication systems 1 to 3 of the first to third embodiments are not limited to hierarchical ID-based encryption, and may be configured to provide other authentication means, including hierarchical ID-based encryption with a revocation function. For example, a public key infrastructure may be utilized, and an intermediate CA may be placed in the parent device, or a unique authentication method may be used in which the parent device can issue authentication information.

[0076] <Additional Notes> The device of the present invention may, for example, be a single hardware entity having an input unit to which a keyboard or the like can be connected, an output unit to which an LCD display or the like can be connected, a communication unit to which a communication device (e.g., a communication cable) capable of communicating with an external device can be connected, a CPU (which may also include a central processing unit, cache memory, registers, etc.), memories such as RAM and ROM, an external storage device such as a hard disk, and buses connecting these input unit, output unit, communication unit, CPU, RAM, ROM, and external storage device so that data can be exchanged between them. If necessary, the hardware entity may also be provided with a device (drive) capable of reading and writing to a recording medium such as a CD-ROM. A physical entity equipped with such hardware resources includes a general-purpose computer.

[0077] The external storage device of the hardware entity stores the programs required to realize the above-mentioned functions and the data required for processing these programs (the programs may be stored in a ROM, which is a read-only storage device, for example, instead of an external storage device). Data obtained by processing these programs is stored in RAM, the external storage device, etc. as appropriate.

[0078] In a hardware entity, each program stored in an external storage device (or ROM, etc.) and the data required to process each program are loaded into memory as needed, and interpreted, executed, and processed by the CPU as appropriate, resulting in the CPU realizing a predetermined function (each component represented as a unit, means, etc., above).

[0079] The present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the spirit of the present invention. Furthermore, the processes described in the above embodiments may not only be executed in chronological order according to the order described, but may also be executed in parallel or individually depending on the processing capacity of the device that executes the processes or as needed.

[0080] As described above, when the processing functions of the hardware entities (apparatuses of the present invention) described in the above embodiments are realized by a computer, the processing contents of the functions that the hardware entities should have are described by a program. Then, by executing this program on a computer, the processing functions of the hardware entities are realized on the computer.

[0081] The various processes described above can be implemented by loading a program that executes each step of the above method into the recording unit 10020 of the computer shown in Figure 20 and operating the control unit 10010, input unit 10030, output unit 10040, etc.

[0082] The program describing the processing contents can be recorded on a computer-readable recording medium. Examples of computer-readable recording media include magnetic recording devices, optical disks, magneto-optical recording media, and semiconductor memories. Specifically, examples of magnetic recording devices include hard disk drives, flexible disks, and magnetic tapes; optical disks include DVDs (Digital Versatile Discs), DVD-RAMs (Random Access Memory), CD-ROMs (Compact Disc Read Only Memory), and CD-Rs (Recordable) / RWs (Rewritable); magneto-optical recording media include MOs (Magneto-Optical discs), and semiconductor memories include EEP-ROMs (Electrically Erasable and Programmable-Read Only Memory).

[0083] The program may be distributed, for example, by selling, transferring, lending, etc. a portable recording medium such as a DVD or CD-ROM on which the program is recorded. Furthermore, the program may be stored in a storage device of a server computer, and then transferred from the server computer to another computer via a network, thereby distributing the program.

[0084] A computer that executes such a program may first temporarily store the program recorded on a portable recording medium or transferred from a server computer in its own storage device. Then, when executing a process, the computer reads the program stored on its own recording medium and executes the process in accordance with the read program. Alternatively, the computer may read the program directly from a portable recording medium and execute the process in accordance with the program. Furthermore, the computer may execute the process in accordance with the received program each time a program is transferred from a server computer to the computer. Alternatively, the server computer may not transfer the program to the computer, but may execute the process through a so-called ASP (Application Service Provider) service, which realizes the processing function by issuing an execution instruction and obtaining the results. In this embodiment, the program includes information used for processing by a computer that is equivalent to a program (such as data that is not a direct instruction to the computer but has properties that define computer processing).

[0085] In addition, in this embodiment, a hardware entity is configured by executing a predetermined program on a computer, but at least a part of the processing contents may be realized by hardware.

Claims

1. An authentication system including a certification authority, a central control system, a group including a parent unmanned aerial vehicle and a child unmanned aerial vehicle, a management system, and an external system, The central control system a first authentication information transmission unit that transmits first authentication information received from the certificate authority to the parent device; The parent device is an authentication unit that performs authentication with the child devices that belong to the same group; a second authentication information transmitting unit that transmits a first token with an expiration date and second authentication information including the first authentication information to the authenticated child device; The management system includes: an authentication unit that performs authentication with the external system; a third authentication information transmitting unit configured to transmit third authentication information including a second token and the first authentication information received from the certificate authority to the authenticated external system; The slave device and the external system an authentication unit that performs authentication based on the second authentication information and the third authentication information; Authentication system.

2. 2. The authentication system of claim 1, The authentication unit of the parent device Execute authentication with the child device using proximity communication Authentication system.

3. 2. The authentication system of claim 1, The second authentication information transmission unit of the parent device transmitting the second authentication information to the child device using near field communication; Authentication system.

4. 4. The authentication system according to claim 2 or 3, the unmanned aerial vehicle is a drone, The external system is a smart locker Authentication system.

5. 4. The authentication system according to claim 1, the first authentication information is a private key; the first token is an ID of the slave device, the second token is an ID of the external system; The slave device and the external system Authentication is performed by ID-based encryption based on the ID of the slave device, the ID of the external system, and the private key. Authentication system.

6. An authentication method executed by a certificate authority, a central control system, a parent unmanned aerial vehicle, a child unmanned aerial vehicle, a management system, and an external system, The central control system transmitting the first authentication information received from the certificate authority to the parent device; The parent device is performing authentication with the child device belonging to the same group; transmitting a first token with an expiration date and second authentication information including the first authentication information to the authenticated child device; The management system includes: performing authentication with the external system; sending third authentication information to the authenticated external system, the third authentication information including the second token and the first authentication information received from the certificate authority; The slave device and the external system performing a step of performing authentication based on the second authentication information and the third authentication information; Authentication method.

7. A program that causes a computer to function as the central control system of claim 1.

8. A program that causes an unmanned aerial vehicle to function as the parent device or child device according to claim 1.

Images