WO2021049155A1 - Système de gestion de fonctionnement, procédé de gestion de fonctionnement et programme de gestion de fonctionnement - Google Patents

Système de gestion de fonctionnement, procédé de gestion de fonctionnement et programme de gestion de fonctionnement Download PDF

Info

Publication number
WO2021049155A1
WO2021049155A1 PCT/JP2020/027142 JP2020027142W WO2021049155A1 WO 2021049155 A1 WO2021049155 A1 WO 2021049155A1 JP 2020027142 W JP2020027142 W JP 2020027142W WO 2021049155 A1 WO2021049155 A1 WO 2021049155A1
Authority
WO
WIPO (PCT)
Prior art keywords
flight
transaction
operation management
specific
reservation
Prior art date
Application number
PCT/JP2020/027142
Other languages
English (en)
Japanese (ja)
Inventor
古川　潤
Original Assignee
本田技研工業株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 本田技研工業株式会社 filed Critical 本田技研工業株式会社
Publication of WO2021049155A1 publication Critical patent/WO2021049155A1/fr

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B64—AIRCRAFT; AVIATION; COSMONAUTICS
    • B64C—AEROPLANES; HELICOPTERS
    • B64C39/00—Aircraft not otherwise provided for
    • B64C39/02—Aircraft not otherwise provided for characterised by special use
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B64—AIRCRAFT; AVIATION; COSMONAUTICS
    • B64F—GROUND OR AIRCRAFT-CARRIER-DECK INSTALLATIONS SPECIALLY ADAPTED FOR USE IN CONNECTION WITH AIRCRAFT; DESIGNING, MANUFACTURING, ASSEMBLING, CLEANING, MAINTAINING OR REPAIRING AIRCRAFT, NOT OTHERWISE PROVIDED FOR; HANDLING, TRANSPORTING, TESTING OR INSPECTING AIRCRAFT COMPONENTS, NOT OTHERWISE PROVIDED FOR
    • B64F1/00—Ground or aircraft-carrier-deck installations
    • B64F1/36—Other airport installations
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
    • G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
    • G05D1/10—Simultaneous control of position or course in three dimensions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/02—Reservations, e.g. for tickets, services or events
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]

Definitions

  • the present invention relates to an operation management system for an air vehicle, an operation management method, and an operation management program.
  • Patent Document 1 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the flight reservation reception unit 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the operation management ledger 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.
  • 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.
  • 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.
  • peer-to-peer Peer to Peer
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the operation management ledger Bc is composed of a blockchain
  • FIG. 3 shows an example including four blocks 31, 32, 33, and 34. Blocks are added every time a predetermined time elapses.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the flight reservation reception unit 11 proceeds with the process in S30 and transmits the reservation application rejection information to the flight object 50.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • step S102 the minor sets the initial value of nonce.
  • 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.
  • 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.
  • step S104 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.
  • step S120 the miner proceeds from step S120 to step S107 and ends the process of adding the new block.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • step S145 the takeoff and landing management unit 14 transmits the takeoff / rejection information notifying that the takeoff is not possible to the aircraft 50.
  • the aircraft 50 waits at the takeoff / landing site, waits for the usage request route to become available, or searches for another flight route.
  • 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.
  • 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).
  • 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.
  • step S177 transmits the landing permission information notifying the landing permission to the desired landing site to the aircraft 50.
  • the aircraft 50 can land at the desired airfield.
  • step S175 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the flying objects 50 to 53 and the user terminal 70 may be included in the minor.
  • 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).
  • 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.
  • the operation management system of the present invention is configured by a plurality of systems or devices having each configuration 11 to 14.
  • 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.
  • 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.
  • 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.
  • 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.
  • the operation management ledger 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.
  • 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.
  • 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.
  • (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.
  • 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
  • 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.
  • the flight transaction of the target aircraft is added to the operation management ledger.
  • the operation management ledger 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.
  • 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.
  • 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. ..
  • the configuration of the operation management system of the first item can be realized.

Landscapes

  • Engineering & Computer Science (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Tourism & Hospitality (AREA)
  • Theoretical Computer Science (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Development Economics (AREA)
  • Mechanical Engineering (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Automation & Control Theory (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention gère strictement le nombre d'aéronefs qui volent sur une trajectoire de vol prédéterminée dans le même créneau temporel.　Un système de gestion d'opération (1) comprend : une unité de détermination de permission de vol (12) qui, en référençant un registre de gestion d'opération de type distribué Bc dans lequel des transactions de vol sont enregistrées en série chronologique, détermine s'il faut autoriser le vol d'un aéronef sujet sur une trajectoire de vol spécifique et dans un créneau temporel spécifique désigné par une transaction de réservation ; et une unité d'addition de transaction (13) qui, si l'unité de détermination de permission de vol (12) permet le vol de l'aéronef sujet à l'aide de la trajectoire de vol spécifique et du créneau temporel spécifique, exécute un processus d'ajout de transaction pour ajouter la transaction de réservation au registre de gestion de fonctionnement Bc en tant que transaction de vol.
PCT/JP2020/027142 2019-09-13 2020-07-10 Système de gestion de fonctionnement, procédé de gestion de fonctionnement et programme de gestion de fonctionnement WO2021049155A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2019166992 2019-09-13
JP2019-166992 2019-09-13

Publications (1)

Publication Number Publication Date
WO2021049155A1 true WO2021049155A1 (fr) 2021-03-18

Family

ID=74866114

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/027142 WO2021049155A1 (fr) 2019-09-13 2020-07-10 Système de gestion de fonctionnement, procédé de gestion de fonctionnement et programme de gestion de fonctionnement

Country Status (1)

Country Link
WO (1) WO2021049155A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023063423A1 (fr) * 2021-10-14 2023-04-20 和男 吉原 Système de véhicule aérien

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005500611A (ja) * 2001-08-17 2005-01-06 エクスペディア インコーポレイテッド １以上の商品目録項目の予約リクエストを管理するシステムおよび方法
US20100191458A1 (en) * 2009-01-23 2010-07-29 Daniel Baker System and method for optimized flight planning
US20180270244A1 (en) * 2017-03-20 2018-09-20 International Business Machines Corporation Unmanned aerial vehicle data management
JP2019028713A (ja) * 2017-07-31 2019-02-21 株式会社Ａｅｒｉａｌ Ｌａｂ Ｉｎｄｕｓｔｒｉｅｓ 匿名化システム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005500611A (ja) * 2001-08-17 2005-01-06 エクスペディア インコーポレイテッド １以上の商品目録項目の予約リクエストを管理するシステムおよび方法
US20100191458A1 (en) * 2009-01-23 2010-07-29 Daniel Baker System and method for optimized flight planning
US20180270244A1 (en) * 2017-03-20 2018-09-20 International Business Machines Corporation Unmanned aerial vehicle data management
JP2019028713A (ja) * 2017-07-31 2019-02-21 株式会社Ａｅｒｉａｌ Ｌａｂ Ｉｎｄｕｓｔｒｉｅｓ 匿名化システム

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023063423A1 (fr) * 2021-10-14 2023-04-20 和男 吉原 Système de véhicule aérien

Similar Documents

Publication Publication Date Title
US11637746B2 (en) Object identification for groups of IoT devices
KR102174665B1 (ko) 디바이스의 보안 프로비저닝 및 관리
US20180218454A1 (en) Managing participation in a monitored system using blockchain technology
CN111143378B (zh) 处理数据的方法及实现该方法的装置
US12020013B2 (en) Software updates distribution to vehicles via V2V communication and verification by a community of vehicles
US5968177A (en) Method and apparatus for processing administration of a secured community
CN101669128B (zh) 级联认证系统
EP2942921B1 (fr) Système et procédé de filtrage de certificats numériques
US11151512B2 (en) Interlocking blockchains for aircraft part history and current aircraft configuration
US11729175B2 (en) Blockchain folding
US20190141048A1 (en) Blockchain identification system
US9967102B2 (en) Managing transfer of device ownership
US11625385B2 (en) Method and apparatus for managing data based on blockchain
WO2021049155A1 (fr) Système de gestion de fonctionnement, procédé de gestion de fonctionnement et programme de gestion de fonctionnement
JP5865386B2 (ja) バックエンド制約委譲モデル
US20230089487A1 (en) Communication network, communication network node, user equipment, method
CN110807189B (zh) 一种区块链访问控制中的权限分割方法
WO2022091183A1 (fr) Système d'authentification/autorisation, dispositif, procédé d'authentification/autorisation, et programme
JP2021530169A (ja) 拡張可能な証明書管理システムアーキテクチャ
US20230237469A1 (en) Utilities linked to digital non-fungible assets
Venable et al. SUPPLY CHAIN DEVICE PROVENANCE
CN102438014A (zh) 后端受限委托模型

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20862786

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20862786

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP