WO2021049155A1 - Operation management system, operation management method, and operation management program - Google Patents

Abstract

The present invention strictly manages the number of aircraft that fly on a predetermined flight path in the same time slot.　An operation management system 1 comprises: a flight permission determination unit 12 that, by referencing a distributed-type operation management ledger Bc in which flight transactions are recorded in time series, determines whether to permit the flight of a subject aircraft on a specific flight path and in a specific time slot designated by a reservation transaction; and a transaction addition unit 13 that, if the flight permission determination unit 12 permits the flight of the subject aircraft using the specific flight path and the specific time slot, executes a transaction addition process for adding the reservation transaction to the operation management ledger Bc as a flight transaction.

Description

Operation management system, operation management method, and operation management program

The present invention relates to an operation management system for an air vehicle, an operation management method, and an operation management program.

Conventionally, an authentication system has been proposed that authenticates the IDs of an air vehicle and a user to provide secure communication between the air vehicle and the user and forces the user to operate the flight of the air vehicle in accordance with flight regulations (for example). , Patent Document 1). Further, a system for managing various transaction data transmitted from an air vehicle by a blockchain has been proposed (see, for example, Patent Document 2).

U.S. Pat. No. 9412278B1 U.S. Patent Application Publication No. 2018/0270244A1

In the airspace where multiple aircraft come and go, in addition to the functions of the conventional system described above, the upper limit of the number of aircraft flying in the same time zone on the predetermined flight path in order to prevent approaching between the aircraft. Need to be set. In addition, it is necessary to prevent a plurality of flying objects from flying beyond the upper limit thus limited.
The present invention has been made in view of this background, and is used for an operation management system, an operation management method, and an operation management that can strictly control the number of flying objects flying on a predetermined flight route in the same time zone. The purpose is to provide a program.

This specification includes all the contents of the Japanese patent application / Japanese Patent Application No. 2019-166992 filed on September 13, 2019.
As the first aspect for achieving the above object, a reservation transaction is received, which is transmitted from the flight object terminal corresponding to the target flight object and specifies the specific flight route and the specific time zone in which the target flight object is scheduled to fly. The reservation transaction is made by referring to the flight reservation reception unit and the distributed operation management ledger that records the flight record or flight reservation of the flight object for each time zone for the specific flight route in chronological order. The specific flight path and the specific flight route specified by the flight permission determination unit for determining whether or not to permit the flight of the target aircraft in the specific flight path and the specific time zone, and the flight permission determination unit. An operation management system including a transaction addition unit that executes a transaction addition process for adding the reserved transaction as the flight transaction to the operation management ledger when the flight of the target aircraft is permitted in a time zone. Can be mentioned.

Further, in the operation management system, the operation management ledger is configured by a block chain, and the transaction addition unit performs consensus building processing between a plurality of ledger reference terminals that refer to the operation management ledger as the transaction addition process. A process of adding a new block including the flight transaction corresponding to the reserved transaction to the blockchain may be executed.

Further, in the operation management system, the flight permission determination unit uses the reservation transaction depending on whether or not the capacity of the specific flight path set based on at least the number of flying objects flying on the specific flight path is exceeded. It may be configured to determine whether or not to permit the flight of the target flight object in the designated specific flight path and the specific time zone.

Further, in the operation management system, the target flight recorded in the operation management ledger is recorded in the operation management ledger for the takeoff from the first takeoff and landing site and the landing on the second takeoff and landing site when the target aircraft flies on the specific flight route. It may be configured to include a takeoff and landing management unit that manages the body based on the flight transaction.

Further, in the operation management system, the takeoff / landing management unit receives takeoff / landing request information for requesting takeoff from the first takeoff / landing site or landing at the second takeoff / landing site when the target aircraft flies on the specific flight path. Upon receipt, authentication processing is performed using the private key associated with the target aircraft and the public key created using the private key, and the transmitting subject of the takeoff / landing request information is the target aircraft. It may be configured to verify that there is.

Further, in the operation management system, when the flight reservation reception unit receives the reservation transaction, it uses a private key associated with the target aircraft and a public key created by using the private key. The authentication process may be performed to verify that the sender of the reserved transaction is the target aircraft.

Next, as a second aspect for achieving the above object, the operation management method executed by the operation management system of the flight object, which is transmitted from the flight object terminal corresponding to the target flight object, is the target flight object. A flight reservation reception step for receiving a reservation transaction that specifies a specific flight route and a specific time zone for which the flight is scheduled, and a flight record or a flight reservation for each time zone for the specific flight route. , With reference to the decentralized operation management ledger recorded in time series, it is determined whether or not to permit the flight of the target aircraft in the specific flight route and the specific time zone specified by the reservation transaction. When the flight permission determination step and the flight permission determination step permit the flight of the target aircraft in the specific flight route and the specific time zone, the reserved transaction is set as the flight transaction in the operation management ledger. An operation management method including a transaction addition step for executing a transaction addition process for addition can be mentioned.

Next, as a third aspect for achieving the above object, the computer is transmitted from the flight object terminal corresponding to the target flight object to set a specific flight path and a specific time zone in which the target flight object is scheduled to fly. Refer to the flight reservation reception unit that receives the specified reservation transaction and the distributed operation management ledger that records the flight record or flight reservation of the flight object for each time zone for the specific flight route in chronological order. Then, the flight permission determination unit for determining whether or not to permit the flight of the target aircraft in the specific flight path and the specific time zone specified by the reservation transaction, and the flight permission determination unit A transaction addition unit that executes a transaction addition process for adding the reserved transaction as the flight transaction to the operation management ledger when the flight of the target aircraft is permitted in the specific flight route and the specific time zone. , An operation management program for functioning as.

According to the above operation management system, when a reservation transaction is accepted by the flight reservation reception unit, the flight permission determination unit refers to the distributed operation management ledger and refers to the specific route and specific time specified by the reservation transaction. It is determined whether or not to allow the target aircraft to fly in the belt. Then, when the flight of the target aircraft is permitted, the flight transaction of the target aircraft is added to the operation management ledger. In this case, since the operation management ledger is decentralized, it is difficult to falsify the flight transactions recorded in the operation management ledger. Therefore, it is possible to strictly control the number of flying objects flying in the same time zone on the predetermined flight path.

FIG. 1 is an explanatory diagram of the configuration of the operation management system. FIG. 2 is an explanatory diagram of the transaction pool. FIG. 3 is an explanatory diagram of an operation management ledger composed of a blockchain. FIG. 4 is an explanatory diagram of a flight route map and a route management table of the flying object. FIG. 5 is a flowchart of flight reservation application and reception processing. FIG. 6 is a flowchart of transaction addition processing according to the reservation application. FIG. 7 is a flowchart of the process of adding a new block to the operation management ledger. FIG. 8 is a flowchart of a takeoff application and processing according to the application. FIG. 9 is a flowchart of a landing application and processing according to the application.

[1. Operation management system configuration]
With reference to FIG. 1, the configuration of the operation management system 1 of the present embodiment and the operation management mode of the route of the aircraft by the operation management system 1 will be described. The operation management system 1 is a computer system composed of a CPU (Central Processing Unit) 10, a memory 20, a communication unit 40, and the like.

The operation management system 1 is a building in which a flight body 50 to 53, a user terminal 70 used by a user U of any of the flight bodies, and an airfield 301 are installed by a communication unit 40 via a communication network 500. A server that communicates with the management device 302 arranged at 300, the management device 302 of the building 310 where the takeoff and landing site 311 is installed, the management device 312 of the building 310 where the takeoff and landing site 321 is installed, and the public key server 510. It is a system. Here, the communication unit (not shown) provided in the flight objects 50 to 53 and the user terminal 70 correspond to the flight object terminals corresponding to the target aircraft objects of the present invention.

The operation management system 1, the aircraft 50 to 53, the user terminal 70, the management devices 302, 312, 322, and the public key server 510 communicate with each other by peer-to-peer (Peer to Peer). In FIG. 1, an eVOL (electric Vertical Takeoff and Landing aircraft, for example, a drone) having four rotor blades is illustrated as the flying objects 50 to 53. The aircraft bodies 50 to 53 fly along the flight path set between the takeoff and landing sites 301, 311 and 321 to carry luggage and the like.

By executing the control program 21 of the operation management system 1 stored in the memory 20, the CPU 10 of the operation management system 1 executes the flight reservation reception unit 11, the flight permission determination unit 12, the transaction addition unit 13, and the takeoff and landing management unit. Functions as 14. The operation management system 1 may read the control program 21 from a recording medium (optical disk, flash memory, etc.) on which the control program 21 is recorded, or may download it from an external server.

The process executed by the flight reservation reception unit 11 corresponds to the flight reservation reception step in the operation management method of the present invention. The process executed by the flight permission determination unit 12 corresponds to the flight permission determination step in the operation management method of the present invention. The process executed by the transaction addition unit 13 corresponds to the transaction addition step in the operation management method of the present invention.

In the memory 20, in addition to the control program 21, a transaction pool 22 that temporarily stores flight transactions indicating flight records or flight reservations of flight paths and flight time zones of flight objects such as aircraft 50 to 53, and a transaction pool 22 The operation management ledger Bc, which stores the time-series history of flight transactions so far, is saved. As will be described later, the operation management ledger Bc is composed of a blockchain.

The flight reservation reception unit 11 receives a reservation transaction that specifies a specific flight route and a specific time zone transmitted from the flight objects 50 to 53 or the user terminal 70, and accepts the flight reservation application. The flight permission determination unit 12 generates a flight route management table from the flight transaction history of the operation management ledger Bc, and determines whether or not to permit the flight reservation by referring to the flight route management table.

When permitting a flight reservation, the transaction addition unit 13 executes a transaction addition process for adding a flight transaction corresponding to the reserved transaction to the blockchain of the operation management ledger Bc. The takeoff / landing management unit 14 receives the takeoff application or landing application of the aircraft 50 to 53 or the aircraft 50 to 53 transmitted from the user terminal 70, and determines whether to permit takeoff or landing.

In the present embodiment, the operation management ledger Bc is distributed and managed by the operation management system 1 and the management devices 302, 312, 322, and consensus building processing (consensus processing) by the operation management system 1 and the management devices 302, 312, 322. Will add a new block to the blockchain of the operation management ledger Bc. The operation management system 1 and the management devices 302, 312, 322 correspond to the ledger reference terminal of the present invention.

Further, the operation management ledger Bc is transmitted from the operation management system 1 to the flight objects 50 to 53 and the user terminal 70, and the flight objects 50 to 53 and the user terminal 70 are the flight transactions recorded in the operation management ledger Bc. From the history of, it is possible to generate a flight route management table for the reservation target date and check the availability of the flight route.

The public key server stores the public key associated with the aircraft 50-53. The public key is created using the original private key, and the ciphertext encrypted with the private key can be decrypted with the public key. Therefore, for example, when an encrypted reservation application with an ID of the aircraft 50 is received and the reservation application can be decrypted with the public key of the aircraft 50, the sender of the reservation application is the aircraft 50. It can be verified that there is. In this way, the authentication process using the combination of the private key and the public key as the electronic signature can be performed.

[2. Transaction pool and operation management ledger configuration]
The configuration of the transaction pool 22 and the operation management ledger Bc will be described with reference to FIGS. 2 to 3. As shown in FIG. 2, the flight transaction 22a, the flight transaction 22b, the flight transaction 22c, ..., Which the application is approved by the flight reservation reception unit 11, are sequentially stored in the transaction pool 22. In each flight transaction 22a, 22b, 22c, ..., The reserved flight route and time zone, and the public key corresponding to the ID (airframe ID) of the aircraft are recorded.

As shown in FIG. 3, the operation management ledger Bc is composed of a blockchain, and FIG. 3 shows an example including four blocks 31, 32, 33, and 34. Blocks are added every time a predetermined time elapses. In the second and subsequent blocks 32, 33, 34, the hash value of the data of the previous workbook, the history data of the flight transaction stored in the transaction pool 22 during the predetermined time, and the hash value satisfying the predetermined rule. Is included with the nonce determined to be calculated.

For example, when the block 34 is added, the hash value 34a of the total data of the hash value 33a recorded in the previous block 33, the flight transaction history data 33b, and the nonce 33c is calculated. Further, the hash value is calculated by changing the nonce 34c so that the hash value 34a, the history data 34b of the current flight transaction transferred from the transaction pool 22, and the hash value of the total data of the nonce 34c satisfy a predetermined rule. The process of doing is repeated. Then, when the nonce 34c from which the hash value satisfying the predetermined rule is obtained is determined, the block 34 recording the determined nonce 34c is added to the operation management ledger Bc.

[3. Flight route and flight route management table]
With reference to FIG. 4, a flight path through which the flight objects 50 to 53 and the like fly, and a flight path management table for managing the capacity of the flight object flying on each flight path will be described.

The flight path FIG. 100 of FIG. 4 shows the flight path R12 between P1 and P2, the flight path R13 between P1 and P3, and the flight path R14 between P1 and P4, which are set for the five takeoff and landing sites P1 to P5. The flight path R23 between P2 and P3, the flight path R34 between P3 and P4, and the flight path R45 between P4 and P5 are shown. In the flight path diagram 100, the numbers in the squares shown in each flight path indicate the relative distances of each flight path, and the larger the number, the longer the distance.

The flight route management table 110 shows the availability of each flight route on a specific day generated from the transition data recorded in the operation management ledger Bc every 30 minutes. The remaining capacity indicates the flight space left in each flight path, and the specifications (size, weight) of the flight objects (size, weight) for the flight objects flying in each flight path and all the flight objects scheduled to fly. , Number of rotating wings, etc.), flight status (flight speed, amount of loaded luggage, weather, etc.) are recognized and calculated. The specifications and flight status of each flying object are recognized by communication with each flying object or a flight management device (not shown) that manages the flight of each flying object.

The larger the remaining capacity, the more space there is in the flight route, and when the remaining capacity becomes "0", flight reservation becomes impossible. For example, in the flight route management table 110 of FIG. 4, since the remaining capacity of the flight route from P1 to P2 in the time zone from 9:30 to 10:00 is "0", the flight reservation in this time zone is set. Becomes impossible.

[4. Flight reservation reception process]
The flight reservation acceptance process executed between the flight object 50 and the operation management system 1 will be described with reference to the flowcharts shown in FIGS. 5 to 6. Here, the flying object 50 will be described, but the same processing is executed for other flying objects such as the flying objects 51 to 53.

In step S1 of FIG. 5, the flight object 50 refers to the operation management ledger Bc and generates a flight route management table for the reservation target date. In the following step S2, the aircraft 50 determines the flight route and time zone for making a flight reservation by checking the remaining capacity of each flight route for each time zone with reference to the flight route management table. In the next step S3, a reservation transaction including the flight route and time zone to be reserved and the aircraft ID of the aircraft 50 is transmitted to the operation management system 1.

The flight reservation reception unit 11 of the operation management system 1 receives the reservation transaction from the aircraft 50 in step S10 of FIG. 5, and calculates the hash value of the data of the reservation transaction in the subsequent step SS11. In the next step S12, the flight reservation reception unit 11 transmits the hash value to the flight object 50.

The aircraft 50 receives the hash value from the operation management system 1 in step S4, and encrypts the hash value with the private key of the aircraft 50 in the subsequent step S5. Then, in step S5, the aircraft 50 transmits the ciphertext of the hash value to the operation management system 1.

The flight reservation reception unit 11 of the operation management system 1 receives the ciphertext from the aircraft 50 in step S13, and attempts to decrypt the ciphertext with the public key of the aircraft 50 in the following step S14. Then, when the flight reservation reception unit 11 was able to decrypt the ciphertext in the next step S15, it was verified that the sender of the reservation transaction was the flight body 50, so the flight reservation reception unit 11 proceeded with the process in step S16 to make a reservation. The application receipt information is transmitted to the aircraft 50, and the process proceeds to step S17 of FIG.

On the other hand, when the ciphertext could not be decrypted, it is possible that an aircraft other than the aircraft 50 sent a reservation transaction by impersonating the aircraft 50 using the aircraft ID of the aircraft 50. Therefore, the flight reservation reception unit 11 proceeds with the process in S30 and transmits the reservation application rejection information to the flight object 50.

In step S17 of FIG. 6, the flight permission determination unit 12 of the operation management system 1 creates a flight route management table for the reservation target date from the operation management ledger Bc. In the following step S18, the flight permission determination unit 12 confirms the remaining capacity (vacancy status) of the flight route and the time zone according to the reservation application with reference to the flight route management table. Then, in the next step S19, the flight permission determination unit 12 proceeds to step S20 when there is a vacancy in the flight route and time zone according to the reservation application, and proceeds to step S40 when there is no vacancy.

In step S40, the flight permission determination unit 12 transmits the non-reservable information notifying that the reservation is not possible to the flight object 50. Further, in step S20, the flight permission determination unit 12 adds and stores the flight transaction corresponding to the reservation application to the transaction pool 22.

In the following step S21, the flight permission determination unit 12 determines whether or not it is time to add a new block (for example, it is set at predetermined time intervals). Then, when it is time to add a new block, the process proceeds to step S22. In step S22, the transaction addition unit 13 of the operation management system 1 transmits the flight transactions stored in the transaction pool 22 to the management devices 302, 312, 322, which are minors, and requests a consensus process. On the other hand, when it is not the timing to add a new block, the flight permission determination unit 12 proceeds to step S50, and in this case, the flight reservation reception process by the flight reservation reception unit 11 is continued.

[5. New block addition process]
According to the flowchart shown in FIG. 7, the consensus process of adding a new block executed by the operation management system 1, the management device 302, the management device 312, and the management device 322, which are minors of the blockchain, will be described. The operation management system 1, the management device 302, the management device 312, and the management device 322 each execute the processing according to the flowchart shown in FIG.

In step S100, the miner verifies the hash value of each block constituting the operation management ledger Bc, and confirms whether or not the operation management ledger Bc has been tampered with. In the following step S101, the miner proceeds to step S110 when the operation management ledger Bc has been tampered with, and proceeds to step S102 when the operation management ledger Bc has not been tampered with. In step S110, the miner transmits tampering information indicating that the tampering has occurred to the operation management system 1, and in this case, the addition of the new block is suspended.

In step S102, the minor sets the initial value of nonce. In the following step S103, the miner calculates the hash value of the hash value of the most recent block and the total data of the transaction and the nonce stored in the transaction pool 22 as described above with reference to FIG.

In the following step S104, the miner determines whether or not a hash value satisfying a predetermined rule has been calculated in step S103. Then, when the hash value satisfying the predetermined rule is calculated, the miner proceeds to step S105 and adds a new block to the blockchain of the operation management ledger Bc. In the next step S106, the miner transmits the operation management ledger Bc to which the new block is added to the other miners.

On the other hand, when the hash value satisfying the predetermined rule is not calculated, the miner proceeds from step S104 to step S120 and determines whether or not the operation management ledger Bc to which the new block is added is received from another miner. To do. Then, when the miner has not received the operation management ledger Bc to which the new block is added, the process proceeds to step S121 to change the nonce, and the hash value is calculated again in step S103.

On the other hand, when the operation management ledger Bc to which the new block is added is received, the miner proceeds from step S120 to step S107 and ends the process of adding the new block. In this way, each miner executes the consensus process according to steps S103 to S106, S120, and S121, and the miner who calculates the hash that satisfies the predetermined rule earliest executes the process of adding a new block to the operation management ledger. And other miners follow this. Therefore, a malicious third party cannot independently change the transaction recorded in the operation management ledger or add the flight transaction to the operation management ledger, thereby preventing falsification of the operation management ledger Bc. Can be done.

[6. Takeoff response processing]
The takeoff response processing of the aircraft executed by the takeoff / landing management unit 14 of the operation management system 1 will be described with reference to the flowchart shown in FIG. Here, the case where the flying object 50 requests takeoff will be described, but the same processing is executed for other flying objects.

In step S130 of FIG. 8, the aircraft 50 has takeoff request information requesting takeoff from the parked takeoff / landing site (corresponding to the first takeoff / landing site of the present invention) (corresponding to the takeoff / landing request information of the present invention). Is transmitted to the operation management system 1. The takeoff / landing management unit 14 receives the takeoff request information from the aircraft 50 in step S140, and calculates the hash value of the takeoff request information in the subsequent step S141. In the following step S142, the takeoff and landing management unit 14 transmits the hash value to the aircraft body 50.

The aircraft 50 receives the hash value from the operation management system 1 in step S131, and encrypts the hash value with the private key of the aircraft 50 in the subsequent step S131. In the following step S133, the aircraft 50 transmits the ciphertext of the hash value to the operation management system 1. The takeoff and landing management unit 14 receives the ciphertext from the aircraft 50 in step S143, and attempts to decrypt the ciphertext using the public key of the aircraft 50 in the next step S144.

In the following step S145, the takeoff and landing management unit 14 determines whether or not the hash value has been decrypted. Then, when the hash value is decoded, the takeoff and landing management unit 14 proceeds with the process in step S146 (verification of the flight object 50 is OK). In step S146, the takeoff and landing management unit 14 determines the flight reservation status recognized from the flight route management table created from the operation management ledger Bc for the flight route requested to be used by the flight body 50, and the flight reservation status with each flight body. It is determined whether or not there is a vacancy in the usage request route based on the status of the currently flying aircraft recognized by communication or the like.

Then, when there is a vacancy in the usage request route, the takeoff / landing management unit 14 proceeds with the process in step S147, and transmits the takeoff permission information notifying the takeoff permission to the aircraft 50. The aircraft 50 that has received the takeoff clearance information can take off from the takeoff landing site.

On the other hand, when the hash value is not decoded in step S145 (verification of the flying object 50 is NG, there is a possibility of spoofing to the flying object 50), and when it is determined in step S146 that there is no space in the usage request route. The takeoff and landing management unit 14 proceeds to step S150. In step S150, the takeoff / landing management unit 14 transmits the takeoff / rejection information notifying that the takeoff is not possible to the aircraft 50. Upon receiving the takeoff / rejection information, the aircraft 50 waits at the takeoff / landing site, waits for the usage request route to become available, or searches for another flight route.

[7. Landing response processing]
According to the flowchart shown in FIG. 9, the landing response processing of the aircraft executed by the takeoff and landing management unit 14 of the operation management system 1 will be described. Here, the case where the flying object 50 requests landing will be described, but the same processing is executed for other flying objects.

In step S160 of FIG. 9, the aircraft body 50 receives landing request information (corresponding to the takeoff / landing request information of the present invention) requesting landing at a specific takeoff / landing site (corresponding to the second takeoff / landing field of the present invention). It is transmitted to the operation management system 1. The takeoff and landing management unit 14 receives the landing request information from the aircraft 50 in step S170, and calculates the hash value of the landing request information in the subsequent step S171. In the following step S172, the takeoff and landing management unit 14 transmits the hash value to the aircraft body 50.

The aircraft 50 receives the hash value from the operation management system 1 in step S161, and encrypts the hash value with the private key of the aircraft 50 in the subsequent step S162. In the following step S163, the aircraft 50 transmits the ciphertext of the hash value to the operation management system 1. The takeoff and landing management unit 14 receives the ciphertext from the aircraft 50 in step S173, and attempts to decrypt the ciphertext using the public key of the aircraft 50 in the following step S174.

In the following step S175, the takeoff and landing management unit 14 determines whether or not the hash value has been decrypted. Then, when the hash value is decoded, the takeoff and landing management unit 14 proceeds to step S176 (verification of the flight object 50 is OK). In step S176, the takeoff and landing management unit 14 receives the desired takeoff and landing site usage information from the desired takeoff and landing site management device (for example, the management device 302 when the desired takeoff and landing site is the takeoff and landing site 301), and receives the desired takeoff and landing site usage information. Determine if there is space in.

Then, when the desired landing site is vacant, the takeoff and landing management unit 14 proceeds to step S177 and transmits the landing permission information notifying the landing permission to the desired landing site to the aircraft 50. Upon receiving the landing permission information, the aircraft 50 can land at the desired airfield.

On the other hand, when the hash value is not decoded in step S175 (verification of the flying object 50 is NG, there is a possibility of spoofing to the flying object 50), or when it is determined in step S176 that there is no space in the desired airfield. The takeoff and landing management unit 14 proceeds to step S180. In step S180, the takeoff and landing management unit 14 transmits the landing rejection information notifying that the landing is not possible to the aircraft 50. Upon receiving the landing rejection information, the aircraft 50 takes measures such as waiting near the desired landing site and waiting for the desired landing site to become available, or searching for another landing site.

[8. Other embodiments]
In the above embodiment, the takeoff and landing management unit 14 is provided, and when landing and taking off of the aircraft, verification is performed to prevent spoofing of the aircraft by using the private key and the public key associated with the aircraft. , The air vehicle may be verified for only one of landing and takeoff. Alternatively, the takeoff and landing management unit 14 may be omitted.

In the above embodiment, the takeoff / landing management unit 14 is provided, and regarding the landing and takeoff of the air vehicle, it is determined whether or not to allow the takeoff and landing by referring to the flight route management table generated from the operation management ledger. For only one of the landing and landing, it may be decided whether or not to permit by referring to the flight route management table.

In the above embodiment, the decentralized operation management ledger is configured by the blockchain, but another configuration in which the operation management ledger is distributed and managed by a plurality of entities may be adopted.

In the above embodiment, the availability of the flight path is determined by using the remaining capacity of the flight path, but at least the number of flying objects flying on the flight path may be used to determine the availability.

In the above embodiment, the operation management system 1, the management device 302, the management device 312, and the management device 322 are set as blockchain miners, but the selection of the miners is not limited to this. For example, the flying objects 50 to 53 and the user terminal 70 may be included in the minor.

In the above embodiment, the flight reservation reception unit 11, the flight permission determination unit 12, the transaction addition unit 13, and the takeoff and landing management unit 14 are configured by one system (operation management system 1 in FIG. 1). As another configuration, for example, the takeoff and landing management unit 14 may be provided in the management device 302 of the takeoff and landing site 301 in a distributed manner in a plurality of systems. In this case, the operation management system of the present invention is configured by a plurality of systems or devices having each configuration 11 to 14.

In the above embodiment, the flight transaction is recorded in each block of the blockchain, but the flight transaction and the flight route management table may be recorded. According to this, it is possible to eliminate the process of creating the flight route management table in the flight bodies 50 to 53 or the operation management system 1.

Note that FIG. 1 is a schematic view showing the functional configuration of the operation management system 1 divided according to the main processing contents in order to facilitate the understanding of the present invention. It may be configured according to the classification of. Further, the processing of each component may be executed by one hardware unit or may be executed by a plurality of hardware units. Further, the processing of each component shown in FIG. 1 may be executed by one program or may be executed by a plurality of programs.

[9. Configuration supported by the above embodiment]
The above embodiment is a specific example of the following configuration.

(Section 1) A flight reservation reception unit that receives a reservation transaction that specifies a specific flight route and a specific time zone in which the target aircraft is scheduled to fly, which is transmitted from the flight object terminal corresponding to the target aircraft. The specific flight specified by the reserved transaction with reference to a distributed operation management ledger that records the flight record or flight reservation of the flight object for each time zone for the specific flight route in chronological order. The flight permission determination unit that determines whether or not to permit the flight of the target aircraft in the route and the specific time zone, and the flight permission determination unit determine the target flight in the specific flight route and the specific time zone. An operation management system including a transaction addition unit that executes a transaction addition process for adding the reserved transaction as the flight transaction to the operation management ledger when the flight of a body is permitted.
According to the operation management system of paragraph 1, when a reservation transaction is accepted by the flight reservation reception unit, the flight permission judgment unit refers to the decentralized operation management ledger and refers to the specific route specified by the reservation transaction. And whether or not to allow the flight of the target aircraft in a specific time zone is determined. Then, when the flight of the target aircraft is permitted, the flight transaction of the target aircraft is added to the operation management ledger. In this case, since the operation management ledger is decentralized, it is difficult to falsify the flight transactions recorded in the operation management ledger. Therefore, it is possible to strictly control the number of flying objects flying in the same time zone on the predetermined flight path.

(Clause 2) The operation management ledger is composed of a blockchain, and the transaction addition unit performs the reservation transaction as the transaction addition process by consensus building processing between a plurality of ledger reference terminals that refer to the operation management ledger. The operation management system according to paragraph 1, which executes a process of adding a new block including the flight transaction corresponding to the above to the blockchain.
According to the operation management system of the second paragraph, by configuring the operation monitoring ledger by the blockchain, it is possible to manage the operation management ledger without setting a specific management unit.

(Section 3) The flight permission determination unit is designated by the reservation transaction depending on whether or not the capacity of the specific flight path set based on at least the number of flying objects flying on the specific flight path is exceeded. The operation management system according to paragraph 1 or 2, which determines whether or not to permit the flight of the target flight object in the specific flight route and the specific time zone.
According to the operation management system of the third item, it is possible to determine whether or not to reserve a specific flight route based on the number of flying objects flying on the flight route.

(Clause 4) The takeoff from the first takeoff and landing site and the landing on the second takeoff and landing site when the target aircraft flies on the specific flight path are recorded in the operation management ledger. The operation management system according to any one of paragraphs 1 to 3, further comprising a takeoff and landing management unit that manages based on flight transactions.
According to the operation management system of paragraph 4, based on the flight transaction recorded in the operation management ledger, it is possible to determine whether or not takeoff and landing are possible due to the flight on a specific flight route.

(Section 5) When the takeoff / landing management unit receives takeoff / landing request information requesting takeoff from the first takeoff / landing site or landing at the second takeoff / landing site when the target aircraft flies on the specific flight path. In addition, an authentication process is performed using the private key associated with the target aircraft and the public key created by using the private key, and the subject of the takeoff / landing request information is the target aircraft. The operation management system described in Section 4 to be verified.
According to the operation management system in Section 5, the target aircraft uses the private key and public key associated with the target aircraft to verify that the subject of the takeoff / landing request information is the target aircraft. It is possible to judge whether or not takeoff or landing is possible.

(Section 6) When the flight reservation reception unit receives the reservation transaction, the authentication process using the private key associated with the target aircraft and the public key created by using the private key. The operation management system according to any one of paragraphs 1 to 4, wherein the transmission subject of the reserved transaction is verified to be the target aircraft.
According to the operation management system in Section 6, the target aircraft uses the private key and public key associated with the target aircraft to verify that the subject of the takeoff and landing request information is the target aircraft. It is possible to determine whether or not to allow flight in a specific flight route and a specific time zone.

(Section 7) An operation management method executed by an operation management system of an air vehicle, which is transmitted from an air vehicle terminal corresponding to the target air vehicle and is specified as a specific flight route to which the target air vehicle is scheduled to fly. A decentralized operation in which a flight reservation reception step for receiving a reservation transaction specifying a time zone and a flight record of a flight record or a flight reservation for each time zone for the specific flight route are recorded in chronological order. With reference to the management ledger, a flight permission determination step for determining whether or not to permit the flight of the target aircraft in the specific flight route and the specific time zone specified by the reservation transaction, and the flight permission determination By the step, when the flight of the target aircraft in the specific flight route and the specific time zone is permitted, a transaction addition process for adding the reserved transaction as the flight transaction to the operation management ledger is executed. An operation management method that includes a transaction addition step.
According to the operation management method of paragraph 7, when the reservation transaction is accepted by the flight reservation acceptance step, the flight permission determination step refers to the decentralized operation management ledger and the specific route specified by the reservation transaction. And whether or not to allow the flight of the target aircraft in a specific time zone is determined. Then, when the flight of the target aircraft is permitted, the flight transaction of the target aircraft is added to the operation management ledger. In this case, since the operation management ledger is decentralized, it is difficult to falsify the flight transactions recorded in the operation management ledger. Therefore, it is possible to strictly control the number of flying objects flying in the same time zone on the predetermined flight path.

(Section 8) Flight reservation reception that receives a reservation transaction that specifies a specific flight route and a specific time zone that the target aircraft plans to fly, which is transmitted from the flight object terminal corresponding to the target aircraft. Designated by the reservation transaction with reference to the decentralized operation management ledger that records the flight record or flight reservation of the flight object for each time zone for the specific flight route in chronological order. The flight permission determination unit that determines whether or not to permit the flight of the target aircraft in the specific flight path and the specific time zone, and the flight permission determination unit determine the specific flight route and the specific time zone. An operation management program for functioning as a transaction addition unit that executes a transaction addition process for adding the reserved transaction as the flight transaction to the operation management ledger when the flight of the target aircraft is permitted. ..
By causing the computer to execute the operation management program of the eighth item, the configuration of the operation management system of the first item can be realized.

Since flight transactions are managed by the decentralized operation management ledger and it is difficult to tamper with the flight transactions recorded in the operation management ledger, the number of aircraft flying on the default flight route at the same time is strictly controlled. Applicable to applications.

1 ... Operation management system, 10 ... CPU, 11 ... Flight reservation reception unit, 12 ... Flight permission judgment unit, 13 ... Transaction addition unit, 14 ... Takeoff and landing management department, 20 ... Memory, 21 ... Control program, 22 ... Transaction pool , 50-53 ... flying object, 70 ... user terminal, 100 ... flight route map, 110 ... flight route management table, 301, 311, 321 ... takeoff and landing site, 302, 312, 322 ... (takeoff and landing site) management device, Bc ... Flight management ledger, Rq ... Reservation application information, U ... User.

Claims (8)

1. A flight reservation reception unit that receives a reservation transaction that specifies a specific flight route and a specific time zone that the target aircraft plans to fly, which is transmitted from the flight object terminal corresponding to the target aircraft.
   The specific flight specified by the reservation transaction with reference to a distributed operation management ledger that records the flight record or flight reservation of the flight object for each time zone for the specific flight route in chronological order. A flight permission determination unit that determines whether or not to permit the flight of the target aircraft in the route and the specific time zone, and
   Addition of a transaction for adding the reserved transaction as the flight transaction to the operation management ledger when the flight permission determination unit permits the flight of the target aircraft in the specific flight route and the specific time zone. Transaction addition part that executes processing and
   Operation management system equipped with.
2. The operation management ledger is composed of a block chain, and the transaction addition unit performs the flight corresponding to the reservation transaction by consensus building processing between a plurality of ledger reference terminals that refer to the operation management ledger as the transaction addition process. The operation management system according to claim 1, wherein a process of adding a new block including a transaction to the blockchain is executed.
3. The flight permission determination unit determines the specific flight path and the specific flight path specified by the reservation transaction depending on whether or not the capacity of the specific flight path set based on at least the number of flying objects flying on the specific flight path is exceeded. The operation management system according to claim 1 or 2, which determines whether or not to permit the flight of the target aircraft in the specific time zone.
4. The takeoff from the first airfield and the landing at the second airfield when the target aircraft flies over the specific flight path are based on the flight transaction of the target air vehicle recorded in the operation management ledger. The operation management system according to any one of claims 1 to 3, further comprising a takeoff and landing management unit for management.
5. When the target aircraft receives takeoff / landing request information requesting takeoff from the first takeoff / landing site or landing at the second takeoff / landing site when the target aircraft flies on the specific flight path, the takeoff / landing management unit receives the target flight. Claim 4 that performs authentication processing using the private key associated with the body and the public key created by using the private key to verify that the sender of the takeoff / landing request information is the target aircraft. Operation management system described in.
6. When the flight reservation reception unit receives the reservation transaction, the flight reservation reception unit performs an authentication process using the private key associated with the target aircraft and the public key created by using the private key, and performs the authentication process. The operation management system according to any one of claims 1 to 4, which verifies that the transmitting entity of the reserved transaction is the target aircraft.
7. It is an operation management method executed by the operation management system of the aircraft.
   A flight reservation reception step that receives a reservation transaction that specifies a specific flight route and a specific time zone that the target aircraft plans to fly, which is transmitted from the flight object terminal corresponding to the target aircraft.
   The specific flight specified by the reservation transaction with reference to a distributed operation management ledger that records the flight record or flight reservation of the flight object for each time zone for the specific flight route in chronological order. A flight permission determination step for determining whether or not to permit the flight of the target aircraft in the route and the specific time zone, and
   Addition of a transaction for adding the reserved transaction as the flight transaction to the operation management ledger when the flight of the target aircraft is permitted in the specific flight route and the specific time zone by the flight permission determination step. A transaction addition step to execute the process and
   Operation management method equipped with.
8. Computer,
   A flight reservation reception unit that receives a reservation transaction that specifies a specific flight route and a specific time zone that the target aircraft plans to fly, which is transmitted from the flight object terminal corresponding to the target aircraft.
   The specific flight specified by the reservation transaction with reference to a distributed operation management ledger that records the flight record or flight reservation of the flight object for each time zone for the specific flight route in chronological order. A flight permission determination unit that determines whether or not to permit the flight of the target aircraft in the route and the specific time zone, and
   Addition of a transaction for adding the reserved transaction as the flight transaction to the operation management ledger when the flight permission determination unit permits the flight of the target aircraft in the specific flight route and the specific time zone. Transaction addition part that executes processing and
   Operation management program to function as.

Images