Information exchange method for vertiport operation

Abstract

The present invention relates to an information exchange method for vertiport operation, the method comprising the steps in which: an operator transmits a reservation request message to a vertiport; the vertiport transmits a reservation approval message or a reservation rejection message to the operator; and when the operator receives the reservation approval message, the operator transmits an arrival and departure notification message to the vertiport. According to the present invention, the information exchange method for vertiport operation enables information exchange based on a preset information exchange order and data format for vertiport operation.

Description

Information exchange methods for vertiport operation

[0001] The present invention relates to a method for exchanging information for operating a vertiport, and more specifically, to a method for exchanging information for operating a vertiport that can exchange information through a pre-set information exchange sequence and data format for operating a vertiport.

[0002] As urbanization progresses globally, urban problems are being triggered, such as a sharp decline in mobility efficiency for urban residents and intensified environmental pollution, while social costs like logistics transportation expenses are skyrocketing. In this context, Urban Air Mobility (UAM) is being proposed as an alternative for future transportation.

[0003] Urban Air Mobility refers to a technology that enables movement within urban areas without runways by utilizing electric-powered vertical take-off and landing (eVTOL) aircraft. Once this technology is commercialized, it will overcome the problems of increasing travel time and worsening traffic congestion, while simultaneously shifting the paradigm of human transportation that has traditionally been limited to ground travel. Accordingly, governments around the world are encouraging the development of urban air mobility and actively promoting related projects. The South Korean government is also proceeding with demonstration and pilot projects in stages, including the refinement of relevant laws and regulations.

[0004] Meanwhile, such urban air mobility generally performs takeoffs and landings on vertiports. A vertiport is a compound word of 'vertical' and 'airport,' referring to an urban aircraft terminal where urban air mobility can take off, land, charge, and perform maintenance.

[0005] However, regarding the aforementioned vertiports, while the selection of construction candidate sites and support for approach control during takeoff and landing are currently being actively discussed, there is a lack of discussion regarding standardized information exchange sequences and data formats for vertiport operations, such as when receiving reservation requests for vertiport resources from airlines.

[0006] The objective of the present invention is to solve the aforementioned conventional problems by providing an information exchange method for vertiport operation that can exchange information through a pre-set information exchange sequence and data format for vertiport operation.

[0007] According to one embodiment of the present invention, the method includes the steps of: a carrier transmitting a reservation request message to a vertiport; the vertiport transmitting a reservation approval message or a reservation rejection message to the carrier; and, if the carrier receives the reservation approval message, the carrier transmitting an arrival / departure report message to the vertiport.

[0008] According to one embodiment of the present invention, the method further includes the step of the operator transmitting a final reservation status message to the vertiport.

[0009] According to one embodiment of the present invention, the method further includes the step of the operator transmitting an operation issue notification message to the vertiport.

[0010] According to one embodiment of the present invention, the method further includes the steps of: the operator transmitting a reservation change request message to the vertiport; the vertiport transmitting a reservation change approval message or a reservation change rejection message to the operator; and the operator transmitting a reservation change status message to the vertiport.

[0011] According to one embodiment of the present invention, the vertiport further includes the step of sending a reservation change notification message to the operator.

[0012] According to one embodiment of the present invention, the method further includes the steps of the operator transmitting a reservation cancellation request message to the vertiport and the operator transmitting a reservation cancellation status message to the vertiport.

[0013] According to one embodiment of the present invention, the vertiport further includes the step of sending a reservation cancellation notification message to the operator.

[0014] According to one embodiment of the present invention, the method further includes the step of the operator transmitting a flight plan approval request message to a traffic control system, and the traffic control system transmitting a flight plan approval message to the operator.

[0015] According to the present invention, since information for the operation of a vertiport can be smoothly exchanged through a pre-set information exchange sequence and data format, efficient operation and stability of urban air mobility can be secured, and thereby, the successful commercialization and service expansion of urban air mobility can be achieved.

[0016] Meanwhile, the effects of the present invention are not limited to those mentioned above, and various effects may be included within the scope obvious to a person skilled in the art from the contents described below.

[0017] FIG. 1 is a flowchart of an information exchange method for operating a vertiport according to an embodiment of the present invention, and

[0018] FIG. 2 is an information exchange flowchart of an information exchange method for operating a vertiport according to an embodiment of the present invention, and

[0019] FIG. 3 is an information exchange flowchart for a reservation inquiry sequence of an information exchange method for operating a vertiport according to an embodiment of the present invention, and

[0020] FIG. 4 illustrates information included in a reservation request message of an information exchange method for operating a vertiport according to an embodiment of the present invention, and

[0021] FIG. 5 illustrates information included in a system response message of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0022] FIG. 6 illustrates information included in a reservation approval message of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0023] FIG. 7 illustrates information included in a reservation rejection message of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0024] FIG. 8 illustrates information included in a final reservation status message of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0025] FIG. 9 illustrates information included in an entry / exit declaration message of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0026] FIG. 10 is an information exchange flowchart for an operation issue notification sequence of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0027] FIG. 11 illustrates information included in an operation issue notification message of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0028] FIG. 12 is a flowchart of a case where a reservation is changed in an information exchange method for operating a vertiport according to an embodiment of the present invention, and

[0029] FIG. 13 is an information exchange flowchart for a reservation change sequence of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0030] FIG. 14 illustrates information included in a reservation change request message of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0031] FIG. 15 illustrates information included in a reservation change approval message of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0032] FIG. 16 illustrates information included in a reservation change refusal message of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0033] FIG. 17 illustrates information included in a reservation change status message of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0034] FIG. 18 illustrates information included in a reservation change notification message of an information exchange method for operating a vertiport according to an embodiment of the present invention, and

[0035] FIG. 19 is a flowchart of the case where a reservation is canceled in an information exchange method for operating a vertiport according to an embodiment of the present invention, and

[0036] FIG. 20 is an information exchange flowchart for a reservation cancellation sequence of an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0037] FIG. 21 illustrates information included in a reservation cancellation request message of an information exchange method for operating a vertiport according to an embodiment of the present invention, and

[0038] FIG. 22 illustrates information included in a reservation cancellation status message of an information exchange method for operating a vertiport according to an embodiment of the present invention, and

[0039] FIG. 23 illustrates information included in a reservation cancellation notification message of an information exchange method for operating a vertiport according to an embodiment of the present invention, and

[0040] FIGS. 24 and 25 illustrate information of an enumerated type for an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0041] FIG. 26 illustrates an example in which a vertiport is equipped with one FATO and two cycle fields in an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0042] FIG. 27 illustrates an example of an inner guidance path in a method for exchanging information for vertiport operation according to an embodiment of the present invention, where the vertiport is equipped with one FATO and two cycle fields.

[0043] FIG. 28 illustrates an example of an outer guidance path in a method for exchanging information for vertiport operation according to an embodiment of the present invention, where the vertiport is equipped with one FATO and two cycle fields.

[0044] FIG. 29 illustrates an example in which a vertiport is equipped with two FATOs and four cycle fields in an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0045] FIG. 30 illustrates an example of an inner guidance path in a case where a vertiport is equipped with two FATOs and four cycle fields in an information exchange method for vertiport operation according to an embodiment of the present invention, and

[0046] FIG. 31 illustrates an example of an outer guidance path in a method for exchanging information for operating a vertiport according to an embodiment of the present invention, in which the vertiport is equipped with two FATOs and four cycle fields.

[0047] Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that in assigning reference numerals to the components of each drawing, the same components are given the same reference numeral whenever possible, even if they are shown in different drawings.

[0048] In addition, when describing embodiments of the present invention, if it is determined that a detailed description of related known configurations or functions would hinder understanding of the embodiments of the present invention, such detailed description is omitted.

[0049] In addition, terms such as first, second, A, B, (a), (b), etc., may be used when describing the components of the embodiments of the present invention. These terms are used merely to distinguish the components from other components, and the essence, order, or sequence of the components is not limited by such terms.

[0050] Additionally, in describing embodiments of the present invention, each "part," "module," or "step" may be implemented through a processor and memory. The term "processor" should be broadly interpreted to include general-purpose processors, central processing units (CPUs), microprocessors, digital signal processors (DSPs), controllers, microcontrollers, and state machines, etc. In some environments, the term "processor" may refer to an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. The term "processor" may also refer to a combination of processing devices, such as, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or any other combination of such configurations.

[0051] Additionally, memory should be broadly interpreted to include any electronic component capable of storing electronic information. Memory may also refer to various types of processor-readable media, such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), programmable read-only memory (PROM), eraseable-programmable read-only memory (EPROM), electrically eraseable PROM (EEPROM), flash memory, magnetic or optical data storage devices, registers, etc. If a processor can read information from memory or write information to memory, memory is said to be in an electronic communication state with the processor, and each "part," "module," or "stage" may be implemented through a program or application based on the processor and memory in an electronic communication state.

[0052] In addition, the communication network may be a wired or wireless communication network and may utilize at least one of LAN (local area network), WLAN (wireless LAN), Wibro (wireless broadband), WiMAX (world interoperability for microwave access), HSDPA (high speed downlink packet access), and various other communication standards. Furthermore, the communication network may be a mobile communication network, and it may be a synchronous mobile communication network or an asynchronous mobile communication network. As an example of the asynchronous mobile communication network, a WCDMA (Wideband Code Division Multiple Access) network may be cited. In this case, although not shown in the drawings, the mobile communication network may include, for example, an RNC (Radio Network Controller). Meanwhile, although the WCDMA network was cited as an example, it may be a next-generation communication network such as a 3GLTE network, 4G network, or 5G network, as well as other low-power communication networks such as Wi-Fi, Bluetooth, and Zigbee, and wired / wireless IP networks.

[0053]

[0054] From now on, with reference to the attached drawings, an information exchange method (S100) for operating a vertiport according to one embodiment of the present invention will be described in detail.

[0055] In the present invention, the aircraft is a flying vehicle capable of being used as a means of urban air mobility (UAM), and may include vertical take-off and landing aircraft (VTOL) and electric powered VTOL (eVTOL), as well as drones, unmanned air vehicles (UAVs), remotely piloted vehicles, fixed-wing aircraft, rotary-wing aircraft, personal aircraft, helicopters, etc. that operate by control or autonomous / semi-autonomous flight in a manned or unmanned state.

[0056] Furthermore, in the present invention, a vertiport may refer to a landing and takeoff location configured for use by the aforementioned UAM aircraft, and may include a departure vertiport and a arrival vertiport. Preferably, such a vertiport may be a location that satisfies specific facility conditions required by the aviation authorities of the relevant region; in this case, the vertiport may be a facility in which a Touchdown and Lift-Off Area (TLOF) and / or a Final Approach and Take-Off Area (FATO) are defined. However, for the application of the present invention, the detailed structure of the vertiport is irrelevant, and it is sufficient if it is recognized as a space capable of enabling landing and takeoff while simultaneously providing services such as charging and maintenance.

[0057] Furthermore, in the present invention, the operator may refer to the operator server, and the vertiport may refer to the vertiport operation server. In this case, the vertiport operation server may be a server provided and operated at each of the origin vertiport and the destination vertiport, and may also refer to a single control server that operates and / or manages a plurality of vertiports including the origin vertiport and the destination vertiport.

[0058] In the present invention, the term "operator server and / or vertiport operating server" may refer to any information processing device used by a suitable individual or group for the purpose of operation and / or management as described above, and may be configured in various forms, for example, including a mainframe, a server, a personal computer, a portable computer (including so-called laptop computers and notebook computers), and a portable communication device (including a mobile terminal, a portable terminal, a smartphone, and a PDA (personal digital assistant)). Alternatively, the operator server and / or vertiport operating server may be configured by a combination of two or more information processing devices connected by mutual wired or wireless communication. For example, the operator server and / or vertiport operating server may be composed of a single server and a portable terminal connected to the server to operate the server. Furthermore, the operator server and / or vertiport operating server may be configured in a form in which a part of its configuration is virtualized and / or distributed, such as in a cloud service or a blockchain network. Of course, the above-described embodiments do not limit or restrict preferred methods of implementing the operator server and / or vertiport operation server in the present invention.

[0059] In addition, the message transmission method within the information exchange method (S100) for operating a vertiport according to the present invention can be classified into two methods: a synchronous message (Request-Response) exchange method and an asynchronous message (Public-Subscribe) exchange method.

[0060] The synchronous message (Request-Response) exchange method based on REST APIs is a system where a client sends a request to a server and the server immediately returns a response. This request-response method (pattern) is primarily used for tasks requiring immediate responses, such as real-time data retrieval or modification. Examples include checking vertiport reservation status and receiving notifications regarding flight operations, such as delays, cancellations, or diversions. The key characteristic of synchronous messaging is that the system waits for a response after making a request, and RESTful APIs using the HTTP protocol are a prime example.

[0061] The Pub / Sub-based asynchronous message (Publish-Subscribe) exchange method involves a publisher publishing a message when a specific event occurs, and a subscriber asynchronously receiving and processing that message. This asynchronous communication method is suitable for event-based processing or periodic data delivery. Examples include processing reservation results, such as reservation approval or rejection, and periodic status updates, such as reservation change notifications. A key feature of asynchronous messages is that when a publisher publishes a message, it does not wait for an immediate response but processes it asynchronously when the subscriber is ready. Additionally, these messages can be managed and delivered in the middle through a message broker (such as RabbitMQ or Apache Kafka).

[0062] The two message exchange methods described above can be used in appropriate combination to meet various system requirements; for example, a REST API-based synchronous message exchange method can be used when real-time request-response is required, and a Publish / Subscribe-based asynchronous message exchange method can be used for asynchronous event processing or periodic tasks.

[0063] In addition, in Figure 4 of the present invention, among Type, string means data type information, boolean means true / false type information, and Instant means information according to the ISO8601 (TUC) format universal standard time notation. In addition, Enum of Type or Format means information of an enumerated type.

[0064]

[0065] FIG. 1 is a flowchart of an information exchange method for operating a vertiport according to an embodiment of the present invention, and FIG. 2 is an information exchange flowchart of an information exchange method for operating a vertiport according to an embodiment of the present invention.

[0066] As illustrated in FIGS. 1 and 2, an information exchange method (S100) for vertiport operation according to an embodiment of the present invention comprises the steps of: an operator transmitting a reservation inquiry message to a departure vertiport and a destination vertiport, and the departure vertiport and the destination vertiport transmitting a reservation status message to the operator (S110); the operator transmitting a reservation request message to the departure vertiport and the destination vertiport (S120); the departure vertiport and the destination vertiport transmitting a reservation approval message or a reservation rejection message to the operator (S130); the operator transmitting a final reservation status message to the departure vertiport and the destination vertiport (S140); the operator transmitting a flight plan approval request message to the traffic control system from the departure and vertiports, and the traffic control system transmitting a flight plan approval message to the operator (S150); and, when the operator receives the reservation approval message, the operator transmitting an arrival / departure report message to the departure vertiport and the destination vertiport. The method may include a step (S160) and a step (S170) in which the operator sends an operation issue notification message to the departure vertiport and the arrival vertiport.

[0067]

[0068] FIG. 3 is an information exchange flowchart for a reservation inquiry sequence of an information exchange method for operating a vertiport according to an embodiment of the present invention.

[0069] As illustrated in FIG. 3, step S110 is a step in which the operator sends a daily schedule reservation inquiry message to the departure vertiport and the arrival vertiport, and the departure vertiport and the arrival vertiport send a daily schedule reservation status message to the operator, wherein the inquiry for the flight number, GUFI (Globally Unique Flight Identifier) ​​and / or date may be performed, and may be performed via SWIM message, but is not limited thereto.

[0070] Here, SWIM (System Wide Information Management) is a system developed to enhance the efficiency and safety of air traffic management systems. It is an information sharing framework that supports the real-time exchange and sharing of various information related to Air Traffic Management (ATM). Since Urban Air Mobility (UAM), which is considered similar to existing aviation systems, can adhere to the Air Traffic Management (ATM) framework, the SWIM information sharing system can also be utilized in UAM.

[0071] Specifically, SWIM messages enhance interoperability between different systems by standardizing the format and content of data; representative standardized data formats include AIXM (Aeronautical Information Exchange Model), FIXM (Flight Information Exchange Model), and / or IWXXM (ICAO Weather Information Exchange Model). Meanwhile, when defining unique SWIM messages for Urban Air Mobility (UAM), standardized data sharing formats for vertiports—which are resources unique to UAM—such as VIXM (Vertiport Information) may be added. Furthermore, the aforementioned SWIM messages are not limited to Step S110; they can be standardized for any information generated at vertiports, as well as for subsequent steps.

[0072] These SWIM messages may contain various types of information, and major message types may include aeronautical information, flight information, weather information, and / or operational information.

[0073]

[0074] FIG. 4 illustrates information included in a reservation request message of an information exchange method for vertiport operation according to an embodiment of the present invention, FIG. 5 illustrates information included in a system response message of an information exchange method for vertiport operation according to an embodiment of the present invention, and FIG. 24 and FIG. 25 illustrate information of an enumerated type of an information exchange method for vertiport operation according to an embodiment of the present invention.

[0075] Step S120 is the step in which the operator sends a reservation request message to the departure vertiport and the arrival vertiport, and the departure vertiport and the arrival vertiport send a system response message to the operator.

[0076] In step S120, the operator first sends a reservation request message to the departure vertiport and the arrival vertiport, respectively. As shown in FIG. 4, the reservation request message may include reservation request information (vpReserveReq) which is header information and / or body information.

[0077] In the present invention, the message format may consist of header information and / or body information.

[0078] Here, header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider publishing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0079] At this time, as illustrated in FIGS. 24 and 25, information regarding message type is information of an enumerated type, and may include a reservation request message (vpReserveReq), a system response message (vpSystemRes), a reservation approval message (vpReserveAppr), a reservation rejection message (vpReserveDeny), a general declaration message, a reservation change request message (vpReserveChangeReq), a reservation change approval message (vpReserveChangeAppr), a reservation change rejection message (vpReserveChangeDeny), a reservation change notification message (vpReserveChangeNotif), a reservation cancellation request message (vpReserveCancelReq), a reservation cancellation notification message (vpReserveCancelNotif) and / or an operational issue notification message (operationalIssueNotif), and at least one of the enumerated message types may be selected.

[0080] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0081] The body information, vpReserveReq, is information required for a vertiport reservation request and may include carrier code information (uaoCode), departure vertiport code information (departureVpCode), arrival vertiport code information (arrivalVpCode), aircraft information (aircraftInfo), flight information (flightInfo), arrival schedule information (scheduledInBlockTime), departure schedule information (scheduledOffBlockTime), and / or resource information (resource), and the arrival schedule information (scheduledInBlockTime) and departure schedule information (scheduledOffBlockTime) may be expressed in units of year, month, day, hour, minute, and second.

[0082] Here, aircraftInfo refers to information about an aircraft taking off or landing at a departure vertiport or a destination vertiport, and may include aircraftRegNumber information, which is the aircraft's unique identification number, aircraftType information, and / or flightNumber information.

[0083] Meanwhile, at each vertiport, connecting flights are identified through the aircraft registration number information (aircraftRegNumber). For example, if there is no next flight, it is identified as continuing to park, and if the next flight is three days later, it is identified as automatically staying at the vertiport (layover). This is because flight number information, which is assigned variably depending on specific conditions such as flight date and route, changes, whereas aircraft registration number information is a unique identification number and remains immutable.

[0084] Additionally, flightInfo is information about the flight and may include serviceType information and / or flightPurpose information. In this case, as illustrated in FIGS. 24 and 25, serviceType information may include information of an enumerated type, such as passenger, cargo, tourism, charter, emergency, education, examination, and / or other information, and flightPurpose information may include information on personnel transport, marine disaster prevention, agricultural support, aerial advertising, photography / surveying, fire suppression, search and rescue / patient transport, cargo transport, patrol management, flight training, high-altitude parachute jump, towing, counter-terrorism, news flight, leisure flight, navigation facility inspection, equipment inspection (airworthiness), air movement, proficiency maintenance, security operations, security operations, and / or traffic management.

[0085] Additionally, resource information in the reservation request information may include towing information, charging information, deicing information, and / or hanger information.

[0086] The towing information in the reservation request information (vpReserveReq) may include towing information (isTowing), which indicates whether the aircraft requires towing when making a vertiport reservation, and towing type information (towingType).

[0087] The charging information in the reservation request information (vpReserveReq) may include charging status information (isCharging), charging type information (chargingType), and / or charging time information (chargingTime), which indicates whether the aircraft requires charging when making a vertiport reservation. Here, charging time information refers to the time required and may be expressed in hours, minutes, and seconds.

[0088] The hanger information in the reservation request information (vpReserveReq) may include hangar status information (isHanger), hanger type information (hangerType), and / or hanger time information (hangerTime), which indicates whether the aircraft is required to be hung for MRO (Maintenance, Repair and Operation), etc., when making a vertiport reservation.

[0089] The de-icing information (deIcing) in the reservation request information (vpReserveReq) may include de-icing status information (isDeIcing), de-icing type information (deIcingType), and / or de-icing time information (deIcingTime), which is information on whether de-icing work is required for the aircraft when making a vertiport reservation.

[0090] Meanwhile, the multiple pieces of information in the aforementioned reservation request message may have a parallel relationship with one another, rather than being dependent on other information.

[0091] Subsequently, in step S120, the departure vertiport and the arrival vertiport transmit a system response message to the operator, and as illustrated in FIG. 5, the system response message may include system response information (vpSystemRes) which is header information and / or body information.

[0092] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0093] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0094] Additionally, the system response information (vpSystemRes) may include reservation unique ID information (reservationId), status information of the counterpart message (status), and / or reason information regarding the current status (reason); the current status information may include a Logical Acknowledgement Message (LAM) to notify that the received message has been accepted without error, and / or a Logical Rejection Message (LRM) to reject the received message because there is an error.

[0095] Meanwhile, the multiple pieces of information in the aforementioned system response messages may have a parallel relationship with one another, rather than being dependent on other information.

[0096] FIG. 6 illustrates information included in a reservation approval message of an information exchange method for operating a vertiport according to an embodiment of the present invention, and FIG. 7 illustrates information included in a reservation rejection message of an information exchange method for operating a vertiport according to an embodiment of the present invention.

[0097] Step S130 is a step in which the departure vertiport and the arrival vertiport send a reservation approval message or a reservation rejection message to the operator after confirming availability, and as illustrated in FIG. 6, the reservation approval message may include reservation approval information (vpReserveAppr) which is header information and / or body information.

[0098] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0099] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0100] Reservation approval information (vpReserveAppr) is information regarding an approved vertiport reservation and may include reservation unique ID information (reservationId), origin and destination vertiport identification information (depArr), vertiport code information (vpCode), carrier code information (uaoCode), aircraft information (aircraftInfo), arrival schedule information (scheduledInBlockTime), departure schedule information (scheduledOffBlockTime), layover information (isLayover), current status information (status) such as whether the reservation has been approved, and / or resource information.

[0101] Here, the reservation ID information (reservationId) is a message generated in the system response (vpSystemRes), and can be generated at the departure vertiport and the arrival vertiport respectively according to the operator's reservation request message (vpReserveReq), and if the departure vertiport and the arrival vertiport are the same, two different reservation ID information may be generated at the respective vertiport.

[0102] Additionally, aircraftInfo is information about an aircraft taking off or landing at a departure vertiport or a destination vertiport, and may include aircraftRegNumber information, which is the unique identification number of the aircraft, aircraftType information, and / or flightNumber information.

[0103] Additionally, the current status information may include information of an enumerated type regarding approval, denial, and / or notification.

[0104] Additionally, resource information in vpReserveAppr may include towing, charging, deicing, hanger, and / or stand information.

[0105] The towing information in the reservation approval information (vpReserveAppr) may include the towing facility number (tugNumber).

[0106] The charging information in the reservation approval information (vpReserveAppr) may include charging facility number information (chargerNumber), charging start time information (startTime), and / or charging end time information (endTime).

[0107] The de-icing information (deIcing) in the reservation approval information (vpReserveAppr) may include de-icing facility number information (deIcingNumber), de-icing start time information (startTime), and / or de-icing end time information (endTime).

[0108] The hanger information in the reservation approval information (vpReserveAppr) may include hanger number information, hanger start time information (startTime), and / or hanger end time information (endTime).

[0109] The stand information in the reservation approval information (vpReserveAppr) is information about a stand that has been approved for reservation and has become available, and may include stand number information (standNumber), stand occupancy start time information (startTime), and / or stand occupancy end time information (endTime).

[0110] Meanwhile, in the present invention, at least one additional resource may be allocated per flight, and accordingly, additional resource information may also be allocated. For example, as shown in FIG. 6, two or more stand information may be allocated, such as when a flight arrives at the arrival stand numbered S101 and then departs through the departure stand numbered S102.

[0111] Meanwhile, the multiple pieces of information in the aforementioned reservation approval message may have a parallel relationship with one another, rather than being dependent on other information.

[0112] Meanwhile, as illustrated in FIG. 7, the reservation rejection message may include reservation rejection information (reserveDeny) which is header information and / or body information.

[0113] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0114] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0115] Reservation Deny information is information regarding a rejected vertiport reservation and may include reservation ID information, origin and destination information (depArr), vertiport code information (vpCode), carrier code information (uaoCode), aircraft information (aircraftInfo), arrival schedule information (scheduledInBlockTime), departure schedule information (scheduledOffBlockTime), current status information (status), such as whether the reservation was denied, and / or reason information; the reason information may include deny code information and comment information such as detailed reasons.

[0116] Here, aircraftInfo refers to information about an aircraft taking off or landing at a departure vertiport or a destination vertiport, and may include aircraftRegNumber information, which is the aircraft's unique identification number, aircraftType information, and / or flightNumber information.

[0117] Additionally, the current status information may include information of an enumerated type regarding approval, denial, and / or notification.

[0118] Additionally, the denyCode information may include enumerated type information regarding insufficient available parking space, vertiport maintenance, reservation data errors, vertiport snow removal, defrosting, sand removal (vertiport / FATO), vertiport adverse weather conditions (poor visibility, strong winds, typhoons, dust storms, snow, etc.), and / or other information.

[0119] Meanwhile, the multiple pieces of information in the aforementioned reservation rejection message may have a parallel relationship with one another, rather than being dependent on other information.

[0120]

[0121] FIG. 8 illustrates information included in the final reservation status message of an information exchange method for vertiport operation according to an embodiment of the present invention.

[0122] Step S140 is the step in which the operator sends a final reservation status message to the departure vertiport and the arrival vertiport, and the departure vertiport and the arrival vertiport send a system response message to the operator.

[0123] In step S140, the operator first sends a final reservation status message to the departure vertiport and the arrival vertiport, respectively. As illustrated in FIG. 8, the final reservation status message may include final reservation status information (vpReserveStat) which is header information and / or body information.

[0124] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0125] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0126] The final reservation status information (vpReserveStat) is information for verifying the final confirmed reservation status and may include the reservation unique ID information (reservationId), current status information (status) such as the final confirmed reservation status, and / or comment information (comment) regarding the current status.

[0127] Here, the reservation ID information (reservationId) is a message generated in the system response (vpSystemRes), and can be generated at the departure vertiport and the arrival vertiport respectively according to the operator's reservation request message (vpReserveReq), and if the departure vertiport and the arrival vertiport are the same, two different reservation ID information may be generated at the respective vertiport.

[0128] Additionally, the current status information may include information of an enumerated type regarding confirmed, denied, pending, and / or canceled.

[0129] Meanwhile, the multiple pieces of information in the aforementioned final reservation status message may have a parallel relationship with one another, rather than being dependent on other information.

[0130] Subsequently, in step S140, the origin vertiport and the destination vertiport transmit a system response message to the operator, and the system response message may include system response information (vpSystemRes) which is header information and / or body information.

[0131] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0132] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0133] Additionally, the system response information (vpSystemRes) may include reservation unique ID information (reservationId), status information of the counterpart message (status), and / or reason information regarding the current status (reason); the current status information may include a Logical Acknowledgement Message (LAM) to notify that the received message has been accepted without error, and / or a Logical Rejection Message (LRM) to reject the received message because there is an error.

[0134] Meanwhile, the multiple pieces of information in the aforementioned system response message may have a parallel relationship with one another, rather than being dependent on other information.

[0135]

[0136] Step S150 is a step in which the operator transmits a flight plan approval request message to the traffic control system, and the traffic control system transmits a flight plan approval message to the operator; this can be carried out via SWIM messages as in Step S110, but is not limited thereto.

[0137] Step S150 may include, more specifically, a step in which the operator transmits a flight plan approval request message to the traffic control system; a step in which the traffic control system verifies the corridor and airspace; a step in which the traffic control system transmits a reservation confirmation message to the departure vertiport and the arrival vertiport, and the departure vertiport and the arrival vertiport transmit a reservation confirmation message to the traffic control system; a step in which the traffic control system transmits a flight plan approval message to the operator, and transmits a message containing the confirmed Flight Plan (FPL) to the departure vertiport and the arrival vertiport.

[0138]

[0139] FIG. 9 illustrates information included in an entry / exit report message of an information exchange method for vertiport operation according to an embodiment of the present invention.

[0140] Step S160 is a step in which, after the operator receives a reservation approval message, the operator sends an arrival / departure declaration message to the departure vertiport and the arrival vertiport, respectively. As illustrated in FIG. 9, the arrival / departure declaration message may include header information and / or body information, such as a general declaration.

[0141] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0142] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0143] At this time, the operator may transmit arrival and departure declaration messages to each vertiport, and input of separate unique reservation ID information (ReservationID) assigned by the departure or arrival vertiport, respectively, may be required. Additionally, the timing for submitting the arrival and departure declaration messages may be immediately after the operation (immediately after the issuance of the Actual FPL).

[0144] The general declaration information may include the reservation ID, uaoCode, departureVpCode, arrivalVpCode, flightNumber, and / or flightDetails.

[0145] Herein, flightDetails may include numberOfSeats, numberOfPassengers, numberOfInfants, numberOfBaggage, weightOfBaggage, weightOfCargo, pilotInCommand, flightRoutes, and / or other information (remarks), and flightRoutes may include originVp, at least one stopOverVp, and / or destinationVp.

[0146] Meanwhile, the multiple pieces of information in the aforementioned arrival and departure declaration messages may have a parallel relationship with one another, rather than being subordinate to other information.

[0147] Subsequently, in step S160, the origin vertiport and the destination vertiport transmit a system response message to the operator, and the system response message may include system response information (vpSystemRes) which is header information and / or body information.

[0148] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0149] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0150] Additionally, the system response information (vpSystemRes) may include reservation unique ID information (reservationId), status information of the counterpart message (status), and / or reason information regarding the current status (reason); the current status information may include a Logical Acknowledgement Message (LAM) to notify that the received message has been accepted without error, and / or a Logical Rejection Message (LRM) to reject the received message because there is an error.

[0151] Meanwhile, the multiple pieces of information in the aforementioned system response message may have a parallel relationship with one another, rather than being dependent on other information.

[0152]

[0153] FIG. 10 is an information exchange flowchart for an operation issue notification sequence of an information exchange method for vertiport operation according to an embodiment of the present invention, and FIG. 11 illustrates information included in an operation issue notification message of an information exchange method for vertiport operation according to an embodiment of the present invention.

[0154] Step S170 is the step in which the operator sends a flight issue notification message to the departure vertiport and the arrival vertiport, and the departure vertiport and the arrival vertiport send a system response message to the operator. Meanwhile, Step S170 can be performed not only after Step S160 but also at any time if a flight issue occurs after the reservation has been approved in Step S130.

[0155] As illustrated in FIG. 10, in step S170, the operator first sends an operational issue notification message, such as a delay, cancellation, and / or diversion, to the departure vertiport and the arrival vertiport. As illustrated in FIG. 11, the operational issue notification message may include operationalIssueNotif information, which is header information and / or body information.

[0156] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0157] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0158] OperationalIssueNotif is information intended to notify the origin or destination vertiport of operational issues such as delays, cancellations, and / or diversions, and may include reservationId, uaoCode, departureVpCode, arrivalVpCode, flightNumber, originSchedule, and / or operationalIssueNotif, and the originSchedule may include scheduledInBlockTime and scheduledOffBlockTime.

[0159] Here, the Operational Issue Notif may include delay information, cancellation information, and / or diversion information.

[0160] Delay information may include delay status information (isDelayed), reason code information (reasonCode), delay duration information (delayDuration), actual arrival time information (actualInBlockTime) and / or actual departure time information (actualOffBlockTime). At this time, as illustrated in FIGS. 24 and 25, the reason code information includes enumerated type information such as shortage of available parking spaces due to the operator (including early arrival), shortage of GT in the flight schedule compared to the published minimum ground time (GT), check-in delay (counter congestion), other (related to passengers, etc.), other (related to cargo), other (related to ground handling), aircraft maintenance (unplanned maintenance), other (related to aircraft maintenance), airframe damage (in flight), airframe damage (in ground operation), other (related to operational standards and crew), departure vertiport de-icing (aircraft), departure vertiport snow removal, defrosting, sand removal (vertiport / FATO), departure vertiport ground handling (adverse weather), deterioration of visibility at departure vertiport (including cloud cover), strong winds at departure vertiport, typhoon at departure vertiport, yellow dust at departure vertiport, snow at destination vertiport, deterioration of visibility at destination vertiport, and destination vertiport Information may be included regarding strong winds, typhoons at destination vertiports, vertiport facilities (shortage of parking spaces, congestion, etc.), destination vertiport restrictions, departure vertiport restrictions, aircraft connections (arrival delays), flight control (route changes, diversions, aircraft replacements), other (connection-related), connection delays due to vertiport control, connection delays due to aircraft defects (DF, DG), connection delays due to ground handling, connection delays due to maintenance, connection delays due to weather, and / or other (excluding delay codes).

[0161] Cancellation information may include isCancelled information and / or reason code information, and the reason code information in the cancellation information may include the same information as the reason code information in the aforementioned delay information.

[0162] Diversion information may include isDiverted, diversionTypeCode, reasonCode, divertVpCode, and / or causeVpCode. In this case, as illustrated in FIGS. 24 and 25, the diversionTypeCode may include information of an enumerated type regarding diversion, normal operation after diversion to one's own airport, change of destination, stopover due to technical problems, and / or normal operation after diversion to another airport, and the reasonCode in the diversion information may include the same information as the reasonCode in the aforementioned delay information.

[0163] Meanwhile, the multiple pieces of information in the aforementioned flight issue notification message may have a parallel relationship with one another, rather than being dependent on other information.

[0164] After the respective operation issue notification messages are transmitted to the departure vertiport and the arrival vertiport, in step S170, the departure vertiport and the arrival vertiport transmit a system response message to the operator, and the system response message may include system response information (vpSystemRes) which is header information and / or body information.

[0165] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0166] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0167] Additionally, the system response information (vpSystemRes) may include reservation unique ID information (reservationId), status information of the counterpart message (status), and / or reason information regarding the current status (reason); the current status information may include a Logical Acknowledgement Message (LAM) to notify that the received message has been accepted without error, and / or a Logical Rejection Message (LRM) to reject the received message because there is an error.

[0168] Meanwhile, the multiple pieces of information in the aforementioned system response message may have a parallel relationship with one another, rather than being dependent on other information.

[0169]

[0170] FIG. 12 is a flowchart of a case where a reservation is changed in an information exchange method for operating a vertiport according to an embodiment of the present invention, FIG. 13 is an information exchange flowchart of a reservation change sequence in an information exchange method for operating a vertiport according to an embodiment of the present invention, and FIG. 14 illustrates information included in a reservation change request message in an information exchange method for operating a vertiport according to an embodiment of the present invention.

[0171] Meanwhile, as illustrated in FIGS. 12 and 13, the present invention may further include the step (S181) in which, after the departure vertiport and the arrival vertiport transmit a reservation approval message to the operator, the operator transmits a reservation change request message to the departure vertiport and the arrival vertiport, and the departure vertiport and the arrival vertiport transmit a system response message to the operator. Meanwhile, the step S181 may be performed not only before but also after the step S140, and after the reservation change is approved, the steps S140 through S170 described above may be performed again.

[0172] In step S181, the operator first sends a reservation change request message to the departure vertiport and the arrival vertiport. As illustrated in FIG. 14, the reservation change request message may include reservation change request information (vpReserveChangeReq) which is header information and / or body information.

[0173] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0174] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0175] The reservation change request information (vpReserveChangeReq) is information for changing a vertiport reservation and may include reservation unique ID information (reservationId), carrier code information (uaoCode), departure vertiport code information (departureVpCode), arrival vertiport code information (arrivalVpCode), aircraft information (aircraftInfo), flight information (flightInfo), schedule information (schedule) and / or resource information (resource), and the reservation change request information may be transmitted with only the values ​​to be changed and other values ​​treated as NULL.

[0176] Here, aircraftInfo refers to information about an aircraft taking off or landing at a departure vertiport or a destination vertiport, and may include aircraftRegNumber, which is the unique identification number of the aircraft, aircraftType, flightNumber, and / or connectedFlightNumber.

[0177] Additionally, flightInfo is information about the flight and may include serviceType information and / or flightPurpose information. In this case, as illustrated in FIGS. 24 and 25, serviceType information may include information of an enumerated type, such as passenger, cargo, tourism, charter, emergency, education, examination, and / or other information, and flightPurpose information may include information on personnel transport, marine disaster prevention, agricultural support, aerial advertising, photography / surveying, fire suppression, search and rescue / patient transport, cargo transport, patrol management, flight training, high-altitude parachute jump, towing, counter-terrorism, news flight, leisure flight, navigation facility inspection, equipment inspection (airworthiness), air movement, proficiency maintenance, security operations, security operations, and / or traffic management.

[0178] Additionally, the schedule information may include arrival schedule information (scheduledInBlockTime) and / or departure schedule information (scheduledOffBlockTime).

[0179] Additionally, the resource information in the vpReserveChangeReq may include towing, charging, deicing, and / or hanger information.

[0180] The towing information in the reservation change request information (vpReserveChangeReq) may include towing information (isTowing), which indicates whether the aircraft requires towing when making a vertiport reservation, and towing type information (towingType).

[0181] The charging information in the reservation change request (vpReserveChangeReq) may include charging status information (isCharging), charging type information (chargingType), and / or charging time information (chargingTime), which indicates whether the aircraft requires charging when making a vertiport reservation. Here, charging time information refers to the duration and may be expressed in hours, minutes, and seconds.

[0182] The deicing information (deIcing) in the reservation change request information (vpReserveChangeReq) may include deicing status information (isDeIcing), deicing type information (deIcingType), and / or deicing time information (deIcingTime), which is information on whether deicing work is required on the aircraft when making a vertiport reservation.

[0183] The hanger information in the reservation change request information (vpReserveChangeReq) may include hangar status information (isHanger), hanger class information (hangerClass), hanger type information (hangerType), and / or hanger time information (hangerTime), which is information on whether the aircraft is required to be hung for MRO (Maintenance, Repair and Operation), etc., when making a vertiport reservation.

[0184] Meanwhile, the multiple pieces of information in the aforementioned reservation change request message may have a parallel relationship with one another, rather than being dependent on other information.

[0185] Subsequently, in step S181, the origin vertiport and the destination vertiport transmit a system response message to the operator, and the system response message may include system response information (vpSystemRes) which is header information and / or body information.

[0186] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0187] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0188] Additionally, the system response information (vpSystemRes) may include reservation unique ID information (reservationId), status information of the counterpart message (status), and / or reason information regarding the current status (reason); the current status information may include a Logical Acknowledgement Message (LAM) to notify that the received message has been accepted without error, and / or a Logical Rejection Message (LRM) to reject the received message because there is an error.

[0189] Meanwhile, the multiple pieces of information in the aforementioned system response message may have a parallel relationship with one another, rather than being dependent on other information.

[0190] Meanwhile, the information in the reservation change request message at step S181 may be the same or similar to the information in the reservation request message at step S120, and the information in the reservation change approval message and / or reservation change rejection message at step S182 may be the same or similar to the information in the reservation approval message and / or reservation rejection message at step S130.

[0191]

[0192] FIG. 15 illustrates information included in a reservation change approval message of an information exchange method for operating a vertiport according to an embodiment of the present invention, and FIG. 16 illustrates information included in a reservation change rejection message of an information exchange method for operating a vertiport according to an embodiment of the present invention.

[0193] Meanwhile, the present invention may further include step S182 in which the departure vertiport and the arrival vertiport transmit a reservation change approval message or a reservation change rejection message to the operator, and as illustrated in FIG. 15, the reservation change approval message may include reservation change approval information (vpReserveChangeAppr) which is header information and / or body information.

[0194] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0195] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0196] The reservation change approval information (vpReserveChangeAppr) is information regarding an approved vertiport reservation change and may include reservation unique ID information (reservationId), origin and destination vertiport identification information (depArr), vertiport code information (vpCode), carrier code information (uaoCode), aircraft information (aircraftInfo), schedule information (schedule) including arrival schedule information (scheduledInBlockTime) and departure schedule information (scheduledOffBlockTime), layover information (isLayover), current status information (status) such as whether the reservation change has been approved, and / or resource information.

[0197] Here, aircraftInfo refers to information about an aircraft taking off or landing at a departure vertiport or a destination vertiport, and may include aircraftRegNumber, which is the unique identification number of the aircraft, aircraftType, flightNumber, and / or connectedFlightNumber.

[0198] Additionally, the current status information may include information of an enumerated type regarding approval, denial, and / or notification.

[0199] Additionally, the resource information in the reservation change approval information (vpReserveChangeAppr) may include towing information, charging information, deicing information, hanger information, and / or stand information.

[0200] The towing information in the reservation change approval information (vpReserveChangeAppr) may include the tugNumber.

[0201] The charging information in the reservation change approval information (vpReserveChangeAppr) may include charging facility number information (chargerNumber), charging start time information (startTime), and / or charging end time information (endTime).

[0202] The deicing information (deIcing) in the reservation change approval information (vpReserveChangeAppr) may include deicing facility number information (deIcingNumber), deicing start time information (startTime), and / or deicing end time information (endTime).

[0203] The hanger information in the reservation change approval information (vpReserveChangeAppr) may include hanger number information (hangerNumber), hanger start time information (startTime), and / or hanger end time information (endTime).

[0204] The stand information in the reservation change approval information (vpReserveChangeAppr) is information about the stand that has been approved for reservation and has become available, and may include stand number information (standNumber), stand occupancy start time information (startTime), and / or stand occupancy end time information (endTime).

[0205] Meanwhile, in the present invention, at least one additional resource may be allocated per flight, and accordingly, additional resource information may also be allocated. For example, as shown in FIG. 15, two or more stand information may be allocated, such as when a flight arrives at arrival stand number S101 and then departs through departure stand number S102.

[0206] Meanwhile, the multiple pieces of information in the aforementioned reservation change approval message may have a parallel relationship with one another, rather than being dependent on other information.

[0207] Meanwhile, as illustrated in FIG. 16, the reservation change rejection message may include reservation change rejection information (vpReserveChangeDeny), which is header information and / or body information.

[0208] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0209] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0210] vpReserveChangeDeny is information regarding a denied vertiport reservation change, and may include reservation ID information (reservationId), departure and arrival information (depArr), vertiport code information (vpCode), carrier code information (uaoCode), flight number information (flightNumber), current status information (status), such as whether the reservation was denied, and / or reason information (reason). The reason information may include denyReason and comment information, such as detailed reasons.

[0211] Here, the current status information is information of an enumerated type and may include information regarding approval, denial, and / or notification.

[0212] Meanwhile, the multiple pieces of information in the aforementioned reservation change rejection message may have a parallel relationship with one another, rather than being dependent on other information.

[0213]

[0214] FIG. 17 illustrates information included in a reservation change status message of an information exchange method for operating a vertiport according to an embodiment of the present invention.

[0215] Meanwhile, the present invention may further include step S183, in which the operator transmits a reservation change status message to the departure vertiport and the arrival vertiport, and the departure vertiport and the arrival vertiport transmit a system response message to the operator.

[0216] In step S183, the operator first sends a reservation change status message to the departure vertiport and the arrival vertiport, respectively. As illustrated in FIG. 17, the reservation change status message may include reservation change status information (vpReserveChangeStat) which is header information and / or body information.

[0217] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0218] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0219] The reservation change status information (vpReserveChangeStat) is information for verifying the final confirmed reservation change status and may include the reservation unique ID information (reservationId), current status information (status) such as the final confirmed reservation change status, and / or comment information (comment) regarding the current status.

[0220] Here, the current status information is of an enumerated type and may include information regarding confirmed, denied, pending, and / or canceled.

[0221] Meanwhile, the multiple pieces of information in the aforementioned reservation change status message may have a parallel relationship with one another, rather than being dependent on other information.

[0222] Subsequently, in step S183, the origin vertiport and the destination vertiport transmit a system response message to the operator, and the system response message may include system response information (vpSystemRes) which is header information and / or body information.

[0223] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0224] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0225] Additionally, the system response information (vpSystemRes) may include reservation unique ID information (reservationId), status information of the counterpart message (status), and / or reason information regarding the current status (reason); the current status information may include a Logical Acknowledgement Message (LAM) to notify that the received message has been accepted without error, and / or a Logical Rejection Message (LRM) to reject the received message because there is an error.

[0226] Meanwhile, the multiple pieces of information in the aforementioned system response message may have a parallel relationship with one another, rather than being dependent on other information.

[0227]

[0228] FIG. 18 illustrates information included in a reservation change notification message of an information exchange method for operating a vertiport according to an embodiment of the present invention.

[0229] Meanwhile, the present invention may further include step S184 in which a departure vertiport transmits a notification-type reservation change notification message to an operator, and as illustrated in FIG. 18, the reservation change notification message may include reservation change notification information (vpReserveChangeNotif) which is header information and / or body information.

[0230] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0231] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0232] The reservation change notification information (vpReserveChangeNotif) is information intended to notify the operator that a reservation has been changed, and may include reservation unique ID information (reservationId), origin and destination vertiport identification information (depArr), vertiport code information (vpCode), operator code information (uaoCode), aircraft information (aircraftInfo), schedule information (schedule) including arrival schedule information (scheduledInBlockTime) and departure schedule information (scheduledOffBlockTime), layover information (isLayover), current status information (status) such as whether the reservation change has been approved, and / or resource information.

[0233] Here, aircraftInfo refers to information about an aircraft taking off or landing at a departure vertiport or a destination vertiport, and may include aircraftRegNumber, which is the unique identification number of the aircraft, aircraftType, flightNumber, and / or connectedFlightNumber.

[0234] Additionally, the current status information may include information of an enumerated type regarding approval, denial, and / or notification.

[0235] Additionally, the resource information in the vpReserveChangeNotif may include towing, charging, deicing, hanger, and / or stand information.

[0236] The towing information in the reservation change notification (vpReserveChangeNotif) may include the towing facility number (tugNumber).

[0237] The charging information in the reservation change notification (vpReserveChangeNotif) may include charging facility number information (chargerNumber), charging start time information (startTime), and / or charging end time information (endTime).

[0238] The deicing information (deIcing) in the reservation change notification information (vpReserveChangeNotif) may include deicing facility number information (deIcingNumber), deicing start time information (startTime), and / or deicing end time information (endTime).

[0239] The hanger information in the reservation change notification (vpReserveChangeNotif) may include hanger number information, hanger start time information, and / or hanger end time information.

[0240] The stand information in the reservation change notification information (vpReserveChangeNotif) is information about a stand that has been approved for reservation and has become available, and may include stand number information (standNumber), stand occupancy start time information (startTime), and / or stand occupancy end time information (endTime).

[0241] Meanwhile, in the present invention, at least one additional resource may be allocated per flight, and accordingly, additional resource information may also be allocated. For example, as shown in FIG. 18, two or more stand information may be allocated, such as when a flight arrives at arrival stand number S101 and then departs through departure stand number S102.

[0242] Meanwhile, the multiple pieces of information in the aforementioned reservation change notification message may have a parallel relationship with one another, rather than being dependent on other information.

[0243]

[0244] FIG. 19 is a flowchart of a case where a reservation is canceled in an information exchange method for operating a vertiport according to an embodiment of the present invention, FIG. 20 is an information exchange flowchart for a reservation cancellation sequence in an information exchange method for operating a vertiport according to an embodiment of the present invention, and FIG. 21 illustrates information included in a reservation cancellation request message in an information exchange method for operating a vertiport according to an embodiment of the present invention.

[0245] Meanwhile, as illustrated in FIGS. 19 and 20, the present invention may further include the step (S191) in which, after the departure vertiport and the arrival vertiport transmit a reservation approval message to the operator, the operator transmits a reservation cancellation request message to the departure vertiport and the arrival vertiport, and the departure vertiport and the arrival vertiport transmit a system response message to the operator. Meanwhile, the step S191 may be performed not only before but also after the step S140.

[0246] In step S191, the operator first sends a reservation cancellation request message to the departure vertiport and the arrival vertiport. As illustrated in FIG. 21, the reservation cancellation request message may include reservation cancellation request information (vpReserveCancelReq) which is header information and / or body information.

[0247] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0248] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0249] The reservation cancellation request information (vpReserveCancelReq) is information for canceling a vertiport reservation and may include reservation ID information (reservationId), carrier code information (uaoCode), departure vertiport code information (departureVpCode), arrival vertiport code information (arrivalVpCode), aircraft information (aircraftInfo), and / or schedule information (schedule).

[0250] Here, aircraftInfo refers to information about an aircraft taking off or landing at a departure vertiport or a destination vertiport, and may include aircraftRegNumber, which is the unique identification number of the aircraft, aircraftType, flightNumber, and / or connectedFlightNumber.

[0251] Additionally, the schedule information may include arrival schedule information (scheduledInBlockTime) and / or departure schedule information (scheduledOffBlockTime).

[0252] Meanwhile, the multiple pieces of information in the aforementioned reservation cancellation request message may have a parallel relationship with one another, rather than being dependent on other information.

[0253] Subsequently, in step S191, the origin vertiport and the destination vertiport transmit a system response message to the operator, and the system response message may include system response information (vpSystemRes) which is header information and / or body information.

[0254] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0255] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0256] Additionally, the system response information (vpSystemRes) may include reservation unique ID information (reservationId), status information of the counterpart message (status), and / or reason information regarding the current status (reason); the current status information may include a Logical Acknowledgement Message (LAM) to notify that the received message has been accepted without error, and / or a Logical Rejection Message (LRM) to reject the received message because there is an error.

[0257] Meanwhile, the multiple pieces of information in the aforementioned system response message may have a parallel relationship with one another, rather than being dependent on other information.

[0258]

[0259] FIG. 22 illustrates information included in a reservation cancellation status message of an information exchange method for operating a vertiport according to an embodiment of the present invention.

[0260] Meanwhile, the present invention may further include step S192, in which the operator transmits a reservation cancellation status message to the departure vertiport and the arrival vertiport, and the departure vertiport and the arrival vertiport transmit a system response message to the operator.

[0261] In step S192, the operator first sends a reservation cancellation status message to the departure vertiport and the arrival vertiport, respectively. As illustrated in FIG. 22, the reservation cancellation status message may include reservation cancellation status information (vpReserveCancelStat) which is header information and / or body information.

[0262] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0263] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0264] The reservation cancellation status information (vpReserveCancelStat) is information for verifying the final confirmed reservation cancellation status and may include the reservation unique ID information (reservationId), current status information (status) such as the final confirmed reservation cancellation status, and / or comment information (comment) regarding the current status.

[0265] Here, the current status information is of an enumerated type and may include information regarding confirmed, denied, pending, and / or canceled.

[0266] Meanwhile, the multiple pieces of information in the aforementioned reservation cancellation status message may have a parallel relationship with one another, rather than being dependent on other information.

[0267] Subsequently, in step S192, the origin vertiport and the destination vertiport transmit a system response message to the operator, and the system response message may include system response information (vpSystemRes) which is header information and / or body information.

[0268] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0269] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0270] Additionally, the system response information (vpSystemRes) may include reservation unique ID information (reservationId), status information of the counterpart message (status), and / or reason information regarding the current status (reason); the current status information may include a Logical Acknowledgement Message (LAM) to notify that the received message has been accepted without error, and / or a Logical Rejection Message (LRM) to reject the received message because there is an error.

[0271] Meanwhile, the multiple pieces of information in the aforementioned system response message may have a parallel relationship with one another, rather than being dependent on other information.

[0272]

[0273] FIG. 23 illustrates information included in a reservation cancellation notification message of an information exchange method for operating a vertiport according to an embodiment of the present invention.

[0274] Meanwhile, the present invention may further include step S193 in which a departure vertiport transmits a notification-type reservation cancellation notification message to an operator, and as illustrated in FIG. 23, the reservation cancellation notification message may include reservation cancellation notification information (vpReserveChangeNotif) which is header information and / or body information.

[0275] Header information is written commonly in the message and may include message identification information (messageInfo) and / or service provider information (serviceProvider). Additionally, message identification information (messageInfo) is information for identifying the message and may include information regarding the message ID (messageId), message type (messageType), and / or message date (messageDate), and service provider information (serviceProvider) is information about the service provider issuing this message and may include the service provider ID (providerId), service provider name (providerName), service provider description (desc), and / or POC information (pointOfContact).

[0276] Meanwhile, the point-of-contact (POC) information of the service provider may include the following information. The point-of-contact information is information about the person in charge and may include information regarding the person-in-charge name (personInCharge), phone number, and / or email.

[0277] The reservation cancellation notification information (vpReserveCancelNotif) is information intended to notify the operator that a reservation has been canceled, and may include reservation unique ID information (reservationId), origin and destination vertiport identification information (depArr), vertiport code information (vpCode), operator code information (uaoCode), aircraft information (aircraftInfo), schedule information (scheduledInBlockTime) and departure schedule information (scheduledOffBlockTime), and / or current status information (status), such as whether a reservation change has been approved.

[0278] Here, aircraftInfo refers to information about an aircraft taking off or landing at a departure vertiport or a destination vertiport, and may include aircraftRegNumber, which is the unique identification number of the aircraft, aircraftType, flightNumber, and / or connectedFlightNumber.

[0279] Meanwhile, the multiple pieces of information in the aforementioned reservation cancellation notification message may have a parallel relationship with one another, rather than being dependent on other information.

[0280]

[0281] Meanwhile, in the present invention, vertiport static data may be defined. Vertiport static data refers to information about a vertiport used for information exchange with an operator in an information exchange method for vertiport operation.

[0282] More specifically, vertiport static information includes vertiport operator information, vertiport location indicator and name information, vertiport geographical and administrative data, vertiport operational hours information, vertiport safety facility information, vertiport approach and monitoring area information, vertiport support rescue and fire fighting services information, at least one FATO information, at least one stand information, at least one taxiway information, at least one charger information, at least one hangar information, at least one deicing information, at least one communication information, at least one surveillance information, at least one light information, and at least one airside facility It may include information (Airside Facility), at least one obstacle information (Obstacle) and / or move guide information (Moveguide).

[0283] Vertiport Operator information may include Vertiport Code information and / or Vertiport Static Version information.

[0284] Here, the code name of the Vertiport Code information may be vpCode, and the notation may be a 5-digit code including letters and numbers, and the code may include information regarding regional classification, size, characteristics, and / or individual names. For example, the Gimpo Airport Vertiport may be expressed as SE1GA.

[0285] Additionally, the codename of the Vertiport Static Version information may be vpStaticVersion, and may include information about the version of the static information and / or the year of that version, such as YYYY / VP.1.0.

[0286] Vertiport Location Indicator and Name information may include Vertiport Name information and / or Vertiport Location information.

[0287] Here, the code name of the Vertiport Name information (Vertiport Name) can be vpName, and it may include an English Vertiport name, for example, GIMPO HUB Vertiport.

[0288] Additionally, the code name for the Vertiport Location information may be vpLoc, and it may include information about the location region, such as SEOUL, and may also include information about the area code if necessary.

[0289] Vertiport Geographical and Administrative Data may include eVTOL Classification, Maximum Take-Off Weight (MTOW), Vertiport Reference Point (VRP), Vertiport Above Mean Sea Level (AMSL), Magnetic Variation (MAG VAR), Magnetic Ambient and / or True Ambient (MAG True), Surface Slope, Vertiport Owner, Vertiport Operator, Vertiport Address, Vertiport Telephone, Vertiport Telefax, Vertiport Homepage and / or Vertiport Operational Hours.

[0290] Here, the code name of the eVTOL classification information (eVTOL Classification) may be evtolClass, and it may be classified according to the size of the gas, for example, A1 for less than 8m, A2 for 8m or more and less than 15m, B1 for 15m or more and less than 19m, and B2 for 19m or more and less than 24m.

[0291] In addition, the code name for the Maximum Take-Off Weight (MTOW) information may be vpMtow, and may include information in kg units, such as 3,000.

[0292] In addition, the code name of the Vertiport Reference Point (VRP) may be vpVrp, and it may be based on the FATO A center coordinates. In the case of a multi-FATO configuration, the center point between FATOs may be used as the reference point (Ref Point). For example, the Vertiport Reference Point information may include coordinate information such as 373325N 1264751E.

[0293] In addition, the code name of the Vertiport AMSL (Above Mean Sea Level) information may be vpTp, and may include information in ft units such as 100.

[0294] In addition, the code name of the magnetic change information (MAG VAR) may be magVar, and may include information about the measurement result value and the year of measurement, such as 9°(2023), for example.

[0295] In addition, the code name for the magnetic azimuth and / or true azimuth (MAG True) may be vpTrueBearing, and may include information about the magnetic azimuth and / or true azimuth of the FATO, such as 10.

[0296] In addition, the code name for the approach surface slope information (Surface Slope) may be surSlope, and may be expressed as a ratio or percentage, such as 8:1 or 12.5%.

[0297] Additionally, the code name for the Vertiport Owner may be vpOwner, and the code name for the Vertiport Operator may be vpOperator; depending on the case, vpOwner and vpOperator may be indicated with the same or different English names.

[0298] In addition, the code name of the vertiport address information (Vertiport Address) may be vpAddress, and may include information about the actual address of the vertiport business location, such as, for example, 76, Haneul-gil, Gangseo-gu, Seoul, 075XX, Republic of Korea.

[0299] Additionally, the code name of the Vertiport Telephone information may be vpTel, and it may include information about the actual contact of the Vertiport business, such as +82-X-XXXX-XXXX.

[0300] Additionally, the code name of the Vertiport Telefax information may be vpTelefax, and it may include information about the actual fax number of the Vertiport business, such as +82-X-XXXX-XXXX.

[0301] Additionally, the code name of the Vertiport homepage information (Vertiport homepage) may be vpHomepage, and may include information about a homepage address on the World Wide Web, such as www.XXX.co.kr.

[0302] In addition, the code name for Vertiport Operational Hours information may be vpOpHours, and, for example, when using Korean Standard Time, it may be expressed in a format such as MM:SS ~ MM:SS, like 06:00 ~ 18:00 KST.

[0303] Meanwhile, Vertiport Operational Hours information may include Vertiport FATO volume, Vertiport STAND volume, Vertiport CHARGER volume, Vertiport HANGER volume, and / or Vertiport DEICING volume.

[0304] Here, the code name for the vertiport FATO volume information (FATO volume) may be vpFatoVol, and may include information regarding the quantity and / or operating hours of the FATO, such as 1 / HO. Here, H0 represents the time when actual passengers use the facility, such as 06:00 to 18:00.

[0305] In addition, the code name of the vertiport parking space quantity information (STAND volume) may be vpStandVol, and may include information on the quantity of parking spaces and / or operating hours, such as 2 / HO.

[0306] Additionally, the code name for the vertiport charging facility quantity information (CHARGER volume) may be vpChargerVol, and may include information regarding the quantity and / or operating hours of the charging facility, such as 2 / H24. Here, H24 means that the operation of facilities such as charging facilities, hangars and / or de-icing facilities is operated 24 hours a day.

[0307] In addition, the code name of the vertiport hangar volume information (HANGER volume) may be vpHangerVol, and may include information on the quantity and / or operating hours of the hangar, such as 1 / H24.

[0308] In addition, the code name of the vertiport de-icing volume information (DEICING volume) may be vpDeicingVol, and may include information on the quantity and / or operating hours of the de-icing facility (or apron equipped with de-icing facility), such as 1 / H24.

[0309] Vertiport Safety Facility information may include at least one Vertiport Safety Facility, information on whether a Vertiport Navigation Safety Facility is installed (Navaid system), and / or information on whether a Vertiport Lighting Facility is installed (Light System).

[0310] Here, the code name of at least one vertiport safety facility may be vpSafeyFac1...n (where n is an integer), and may include information on the details of each safety facility, such as a windcone, fire fighting, and / or fire pump.

[0311] Additionally, the code name for the information on whether a vertiport navigation safety facility is installed (Navaid system) may be vpNavid, and, for example, the installation status of the vertiport navigation safety facility may be expressed as Yes (Y) or No (N).

[0312] Additionally, the code name for the information on whether a vertiport lighting facility is installed (Light System) may be vpLight, and, for example, the installation status of the vertiport lighting facility may be expressed as Yes (Y) or No (N).

[0313] Vertiport Approach and Monitoring Area information may include Vertiport Flight Rule information, Vertiport Corridor information, and / or Vertiport Zone information.

[0314] Here, the code name for Vertiport Flight Rule information may be vpFR, and it may be expressed as, for example, V or PS, which may stand for VFR (Visual Flight Rules) and PinS (Point in Space), respectively.

[0315] In addition, the code name of the Vertiport Corridor information may be Vpcor, and may be expressed as, for example, 2 / 2, which represents the number of departure procedures / the number of arrival procedures as an integer, and may include information on the quantity of Vertiport takeoff and landing approach routes.

[0316] In addition, the code name of the Vertiport Zone information may be vpZone, and may be expressed as, for example, 3 / 3,000, which means A Circle, radius 3NM centered at SE1GA VRP, 3,000ft.

[0317] Vertiport Support Rescue and Fire Fighting Services information may include at least one supportable nearby facility information (Vpsupport).

[0318] Here, the code name of at least one supported nearby facility information (Vpsupport) may be vpSupport1...n (n is an integer), for example, if the nearby facility is a hospital, it may include information about the hospital and / or the number of beds, such as (Hospital) XXX Hospital : Gangseo-gu, Seoul, 075XX, +82-XXXX-XXXX (Bed : 20), and if the nearby facility is a fire station, it may include information about the fire station, such as (Fire station) XXX Fire station : Gangseo-gu, Seoul, 075XX, +82-XXXX-XXXX.

[0319] FATO information (FATO) may include FATO ID information (FATO ID), FATO Position information (FATO Position), FATO AMSL information, FATO size information (FATO size), FATO Landgear Type information, FATO MTOW information, FATO in and out route information, FATO gradient information, FATO eVTOL Land information, FATO surface classification information (FATOsurtp), TLOF size information (TLOFsize), TLOF loadstatic information (TLOFloadstatic), TLOF loaddynamic information (TLOFloaddynamic), TLOF pack classification information (TLOFpcn) and / or stopbar information.

[0320] Here, the code name of the FATO ID information (FATO ID) can be fatoId, and for example, if multiple FATOs exist, it can be expressed as A, B, C...

[0321] In addition, the code name of the FATO position information (FATO Position) may be fatoPos, and may include information about the latitude and longitude of the FATO center point, such as 373325N 1264751E.

[0322] In addition, the code name of the FATO altitude information (FATO AMSL) may be fatoAmsl, and may include information in ft units, such as 100.

[0323] In addition, the code name of the FATO size information (FATO size) may be fatoSize, and may include information about the width and / or length of the FATO in meters, such as 32 × 32.

[0324] Additionally, the code name of the FATO Landgear Information (FATO Landgear Type) may be fatoLandgear, and the FATO Landgear Information may include Tricycle Wheel (TW) type, Fixed Skid (FS) type and / or All (Al) type.

[0325] In addition, the code name of the FATO Maximum Takeoff Weight (FATO MTOW) information may be fatoMtow, and may include information in kg units, such as 3,000.

[0326] In addition, the code name of the FATO in and out route information may be fatoInOut, and the FATO in and out route information may include information about Designations FATO and / or information about True Bearing, for example, the outbound direction and the inbound direction may be expressed as 14A_140° and 32A_320°, respectively.

[0327] In addition, the code name of the FATO gradient information (FATO Gradient) may be fatoGradient, and if the FATO zone drainage gradient excluding TLOF is 5%, it may be expressed as 5.

[0328] In addition, the code name for FATO eVTOL Land aircraft size information may be fatoLand, and may include information in meters, such as 16.

[0329] In addition, the code name of the FATO surface classification information (FATOsurtp) may be fatoSurTp, and may include information about the FATO surface classification, such as Asphalt, for example.

[0330] In addition, the code name of the TLOF size information (TLOFsize) may be tlofSize, and may include information about the width and / or height of the TLOF, such as 16 × 16.

[0331] In addition, the code name of the TLOF static load information (TLOFloadstatic) may be tlofLoadStatic, and may include information in kg units at 100% static load, such as 3,175.

[0332] In addition, the code name of the TLOF dynamic load information (TLOFloaddynamic) may be tlofLoadDynamic, and may include information in kg units at 150% dynamic load, such as 4,762.

[0333] Additionally, the code name of the TLOF pavement classification information (TLOFpcn) may be tlofPcn, and the TLOF pavement classification information may include strength (expressed numerically, e.g., 72), stiffness (e.g., F (Flexible) or R (Rigid)), degree of pavement firmness (e.g., A (maximum) to D (minimum)), tire pressure at landing (e.g., W: unlimited, X: 1.5 MPA, Y: 1.25 MPA, Z: 0.5 MPA), and / or strength derivation criteria (e.g., T: technical evaluation, U: physical direct experience).

[0334] Additionally, the code name of the stopbar information (StopbarType) may be stopbarType, and may include information regarding the end of the stopbar, such as A (stop sign) and / or B (ILS radio protection sign).

[0335] The apron information (Stand) may include apron ID information (Stand ID), apron position information (Stand Position), apron elevation information (Stand AMSL), apron size information (Stand Size), apron charging facility information (Stand Charging), and / or apron available aircraft size information (eVTOL Classification).

[0336] Here, the code name of the parking space ID information (Stand ID) can be standId, and it can be expressed as a number of the parking space, such as 101.

[0337] In addition, the code name of the stand position information may be standPos, and may include information about the latitude and longitude of the center point of the stand, such as 373325N 1264751E.

[0338] In addition, the code name of the apron elevation information (StandAMSL) may be standAmsl, and may include information in ft units, such as 100.

[0339] In addition, the code name of the stand size information may be standSize, and may include information on the width and / or length of the FATO in meters, such as 22.5 × 22.5, and may include information on the 1.5D and / or actual size of the stand.

[0340] Additionally, the code name for the parking space charging facility information (Standcharging) may be standChg, and, for example, whether a parking space charging facility is available may be expressed as Yes (Y) or No (N).

[0341] In addition, the code name of the parking space available aircraft size information (eVTOL Classification) may be standEvtolClass, and may be classified according to aircraft size, for example, A1 for less than 8m, A2 for 8m or more and less than 15m, B1 for 15m or more and less than 19m, and B2 for 19m or more and less than 24m.

[0342] Taxyway information may include Taxyway ID information, Taxyway nodelink route information, Taxyway availability information, and / or Taxyway direction information.

[0343] Here, the code name of the taxiway ID information (Taxiway ID) may be taxiwayId, and for example, if there are multiple taxiways, it can be expressed as T1 (Taxiway1), T2 (Taxiway2), T3 (Taxiway3), T4 (Taxiway4)...

[0344] In addition, the code name of the taxiway nodelink route information (TaxiwayNodelink) may be taxiwayNodelink, and may include information about the taxiway nodelink route, such as FATOA_A_STAND101, FATOA_D_STAND102, STAND101_B_FATOA, STAND102_C_FATOA, etc.

[0345] In addition, the code name for Taxiway Availability information may be taxiwayAva, and may include information on the maximum size of the taxiway-accessible vehicle in meters, such as 16.

[0346] Additionally, the code name for the taxiway direction information (Taxiway Direction) may be taxiwayDir, and may be expressed as, for example, O (One way) and / or B (Both way).

[0347] The charging facility information (Charger) may include charging facility ID information (Charging ID), charging facility location information (Charging Position), charging facility input voltage information (Charging input), charging facility maximum output power information (Charging mgc), charging facility maximum input / output current information (Charging mrc) and / or charging facility maximum output voltage information (Charging mgp).

[0348] Here, the code name of the charging facility ID information (Charging ID) may be chgId, and for example, if there are multiple charging facilities, it may be expressed as C101, C102, C103....

[0349] In addition, the code name of the charging facility location information (Charging Position) may be chgPos, and may include information about the latitude and longitude where the charger is installed, such as 373321N 1264761E, and may include information about the altitude.

[0350] In addition, the code name of the charging input voltage information may be chgIcIp, and may include information about VAC and Phase, such as 380VAC and 3Phase.

[0351] In addition, the code name of the maximum output power information of the charging facility (Charging mgc) may be chgMgc, and may include information in kW units, such as 400kW.

[0352] In addition, the code name of the charging facility maximum input / output current information (Charging mrc) may be chgMrc, and may include information in units of A, such as 500A.

[0353] In addition, the code name of the maximum output voltage information of the charging facility (Charging mgp) may be chgMgp, and may include information in V units, such as DC200 ~ 1,000V.

[0354] Meanwhile, charging facility information may further include charging scheduling information.

[0355] Generally, charging facilities are operated through a contractual power system in which they are contracted with consumers (i.e., a method where the electricity supplier provides power equivalent to the basic charge and charges additionally for any excess). Consequently, the higher the contracted power, the higher the basic charge. This is because there is a contracted capacity that must be supplied stably, even if the full contracted power is not actually used. However, the contracted capacity and the actual average usage capacity inevitably differ; as the peak power value increases, the amount of power required for normal operation rises to the peak level, leading to the problem of unnecessarily high monthly basic charges. Therefore, by utilizing the charging scheduling information of the present invention, unnecessary power consumption can be reduced through optimized contracted capacity settings and peak management.

[0356] Hangar information may include Hangar ID information, Hangar Position information, Hangar Size information, Hangar eVTOLclass information, and / or MROib information.

[0357] Here, the code name of the hangar ID information (Hangar ID) can be hangarId, and for example, if there are multiple hangars, it can be expressed as H101, H102, H103...

[0358] In addition, the code name of the hangar position information (Hangar Position) may be hangarPos, and may include information on the latitude and longitude of the hangar center point, such as 373361N 1264778E, and may include information on the altitude.

[0359] In addition, the code name for the hangar size information (Hangar Size) may be hangarSize, and may include information on the width and / or length of the hangar in meters, such as 24.5 × 24.5.

[0360] In addition, the code name for the hangar eVTOL class information may be hangarAva, and it may be classified according to aircraft size, for example, A1 for less than 8m, A2 for 8m or more and less than 15m, B1 for 15m or more and less than 19m, and B2 for 19m or more and less than 24m.

[0361] In addition, the code name for MRO maintenance level information (MROib) may be mroIb, and it can be classified according to the highest level of MRO maintenance possible; for example, it can be classified as L for the Light level, M for the Middle level, and H for the Heavy level.

[0362] Deicing information may include Deicing ID, Deicing Position, Deicing Size, Deicing eVTOL class, and / or Deicing Liquid.

[0363] Here, the code name of the deicing facility ID information (Deicing ID) may be deicingId, and for example, if there are multiple deicing facilities, it may be expressed as D101, D102, D103...

[0364] In addition, the code name of the deicing position information may be deicingPos, and may include information on the latitude and longitude of the center point of the deicing position, such as 373361N 1264778E, and may include information on the altitude.

[0365] In addition, the code name of the deicing size information (Deicing Size) may be deicingSize, and may include information on the width and / or length of the deicing facility in meters, such as 24.5 × 24.5.

[0366] In addition, the code name of the deicing eVTOL class information may be deicingAva, and it may be classified according to the size of the aircraft, for example, A1 for less than 8m, A2 for 8m or more and less than 15m, B1 for 15m or more and less than 19m, and B2 for 19m or more and less than 24m.

[0367] In addition, the code name of the deicing liquid information (Deicing Liquid) may be deicingLi, and depending on the solution used, it may be classified into HW (Heated Water), SAE I, II, III and / or IV.

[0368] Communication facility information may include Communication ID information, Communication Type information, Communication Position information, Communication Use information, Primary Communication Freq information, Secondary Communication Freq information, Emergency Communication Freq information, Communication Operation information, and / or Callsign information.

[0369] Here, the code name of the communication facility ID information (Communication ID) may be comId, and for example, if there are multiple communication facilities, it may be expressed as COM1, COM2, COM3....

[0370] In addition, the code name of the communication facility type information (Communication Type) may be comType, and may include type information of the communication facility such as VHF (Very High Frequency).

[0371] In addition, the code name of the communication position information may be comPos, and may include information about the latitude and longitude of the antenna center point, such as 373361N 1264778E.

[0372] In addition, the code name for the communication facility use information (Communication Use) may be comUse, and may include information about the use of the communication facility (voice), such as VOICE Com.

[0373] In addition, the code name of the primary communication frequency information (Communication Freq Primary) may be comFreqP, and may include information about the primary communication frequency in MHz units, such as 118.05 MHz.

[0374] In addition, the code name of the backup communication frequency information (Communication Freq Second) may be comFreqS, and may include information on the backup communication frequency in MHz units, such as 118.20 MHz.

[0375] In addition, the code name of the emergency communication frequency information (Communication Freq Emergency) may be comFreqE, and may include information on the emergency communication frequency in MHz units, such as 121.5 MHz.

[0376] In addition, the code name of the communication facility operation time information (Communication Operation) may be comOperation, and may include information about the operation time of the communication facility, such as HO.

[0377] In addition, the code name of the call sign information (Communication Callsign) may be comCallsign, and the call sign information may include, for example, Gimpo Vertiport.

[0378] Surveillance information may include Surveillance ID, Surveillance Name, Surveillance Type, Surveillance Position, Surveillance Detection Altitude, Surveillance Range, and / or Surveillance Operation information.

[0379] Here, the code name of the surveillance facility ID information (Surveillance ID) may be surId, and for example, if there are multiple communication facilities, it may be expressed as SUR1, SUR2, SUR3....

[0380] In addition, the code name of the surveillance name information (Surveillance Name) may be surName, and may include information about the name of the surveillance facility, such as Visual observation.

[0381] In addition, the code name of the surveillance facility type information (Surveillance Type) may be surType, and may include information about the type of surveillance facility, such as CCTV.

[0382] In addition, the code name of the surveillance position information may be surPos, and may include information on the latitude and longitude of the center point of the surveillance facility, such as 373361N 1264778E.

[0383] In addition, the code name of the Surveillance Detection Altitude information may be surAlt, and may include information about the detectable altitude and / or angle, such as 1,000 / 130°.

[0384] In addition, the code name of the surveillance range information may be surRange, and may include information about the detection range in km units, such as 2 km.

[0385] In addition, the code name for the surveillance operation information (Surveillance Operation) may be surOperation, and may include information about the operation time of the relevant surveillance facility, such as HO.

[0386] The lighting facility information (Light) may include lighting facility ID information (Light ID), lighting facility type information (Light Type), lighting facility location information (Light Position) and / or lighting facility color information (Light Color).

[0387] Here, the code name of the lighting facility ID information (Light ID) may be lId, and may include, for example, VLIGHT1, VLIGHT2, VLIGHT3..., where VLIGHT1 may represent the vertical landing guidance light, and VLIGHT2 and VLIGHT3 may represent the landing minimum altitude alarm lights, respectively.

[0388] Additionally, the code name for the light type information (Light Type) may be lType, and may include, for example, VGLS (Vertical takeoff and landing Guidance Light System), LAALS (Lowest Altitude Alarm Light System) and / or FATO Landing Light.

[0389] In addition, the code name for the light position information may be ltPos, and may include information regarding the latitude and longitude of the center point of the light facility, such as 373361N 1264778E, and in cases where it consists of multiple lights, such as a landing area, the position information may be omitted.

[0390] In addition, the code name of the lighting facility color information (Light Color) may be lColor, and may include information about the color of the corresponding lighting facility, such as Green.

[0391] Airside Facility information may include Airside Facility ID information, Airside Facility Name information, and / or Airside Facility Position information.

[0392] Here, the code name of the Airside Facility ID information may be facId, and for example, if there are multiple airside facilities, it may be expressed as FAC1, FAC2, FAC3...

[0393] Additionally, the code name of the Airside Facility Name information may be facName, and may include information regarding the name of the airside facility, such as Windcone, Towcar1, and / or Firepump.

[0394] In addition, the code name of the Airside Facility Position information may be facPos, and may include information on the latitude and longitude of the center point of the airside facility, such as 373311N 1264718E, and may include information on the altitude.

[0395] Obstacle information may include Obstacle ID, Obstacle Position, Obstacle Elevation, Obstacle Type, Obstacle Light Type, and / or Remarks.

[0396] Here, the codename of the obstacle ID information (Obstacle ID) can be obsId, and can be expressed as, for example, SE1GA001.

[0397] In addition, the code name of the obstacle position information (Obstacle Position) may be obsPos, and may include information about the latitude and longitude of the obstacle center point, such as 373225N 1264421E.

[0398] In addition, the code name for the obstacle height information (Obstacle Elevation) may be obsHgt, and may include information for each of the obstacle's ELEV / HGT, such as 400ft / 390ft.

[0399] Additionally, the code name of the Obstacle Type information (Obstacle Type) may be obsType, and may include information about the type of the corresponding obstacle, such as mountains and / or buildings, for example.

[0400] In addition, the code name of the aviation obstruction light information (Obstacle Light Type) may be obsLigTp, and may include information regarding the corresponding aviation obstruction light, such as LGTD.

[0401] In addition, the code name of the approach direction information (Remarks) may be remarks, and may include information about the approach direction such as 14A APCH (approach) or 34A APCH.

[0402] FIG. 26 illustrates an example in which a vertiport is equipped with one FATO and two cycle fields in an information exchange method for vertiport operation according to an embodiment of the present invention; FIG. 27 illustrates an example of an inner guidance path in which a vertiport is equipped with one FATO and two cycle fields in an information exchange method for vertiport operation according to an embodiment of the present invention; FIG. 28 illustrates an example of an outer guidance path in which a vertiport is equipped with one FATO and two cycle fields in an information exchange method for vertiport operation according to an embodiment of the present invention; FIG. 29 illustrates an example in which a vertiport is equipped with two FATOs and four cycle fields in an information exchange method for vertiport operation according to an embodiment of the present invention; FIG. 30 illustrates an example of an inner guidance path in which a vertiport is equipped with two FATOs and four cycle fields in an information exchange method for vertiport operation according to an embodiment of the present invention; and FIG. 31 illustrates an information exchange method for vertiport operation according to an embodiment of the present invention This illustrates an example of an outer guidance path when the vertiport is equipped with two FATOs and four apron fields.

[0403] Moveguide information may include Arrival Taxi Route information and / or Departure Taxi Route information.

[0404] Here, the code name of the arrival taxi route information may be arrRoute, and information about the route may be provided in text, voice, etc., or an image file of the route may be provided through a link as shown in FIGS. 27 and 28 or FIGS. 30 to 31.

[0405] In addition, the code name of the departure taxi route information may be depRoute, and information about the route may be provided in text, voice, etc., or an image file of the route may be provided through a link as shown in FIGS. 27 and 28 or FIGS. 30 to 31.

[0406] That is, as illustrated in FIG. 26, for example, a vertiport may be equipped with one FATO and two stands. In this case, the routes between the FATO and the stands may include the outer Route A and Route D and the inner Route B and Route C. At this time, the inner Route B and Route C can basically be utilized as illustrated in FIG. 27, and if a large capacity is required due to an increase in gas volume, the outer Route A and Route D can be utilized as illustrated in FIG. 28, but is not limited thereto, and both the outer and inner routes may be used depending on the situation.

[0407] In addition, as shown in FIG. 29, for example, a vertiport may be equipped with two FATOs and four stands. In this case, the inner B and E routes can basically be utilized as shown in FIG. 30, and if a large capacity is required due to gas increase, the outer A and F routes can be utilized as shown in FIG. 31, but is not limited thereto, and both the outer and inner routes can be used depending on the situation.

[0408]

[0409] Although all components constituting the embodiments of the present invention have been described above as being combined or operating in combination, the present invention is not necessarily limited to such embodiments. That is, within the scope of the purpose of the present invention, all components may be selectively combined in one or more ways to operate.

[0410] Furthermore, terms such as "include," "compose," or "have" described above, unless specifically stated otherwise, mean that the relevant component may be inherent; therefore, they should be interpreted as allowing for the inclusion of additional components rather than excluding them. All terms, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the present invention pertains, unless otherwise defined. Commonly used terms, such as those defined in advance, should be interpreted in accordance with their meaning in the context of the relevant technology and should not be interpreted in an ideal or overly formal sense unless explicitly defined in the present invention.

[0411] Furthermore, the above description is merely an illustrative explanation of the technical concept of the present invention, and those skilled in the art to which the present invention pertains will be able to make various modifications and variations within the scope of the essential characteristics of the present invention.

[0412] Accordingly, the embodiments disclosed in this invention are intended to illustrate, not limit, the technical concept of the invention, and the scope of the technical concept of the invention is not limited by these embodiments. The scope of protection of this invention shall be interpreted by the claims below, and all technical concepts within an equivalent scope shall be interpreted as being included within the scope of rights of this invention.

Claims

1. The step in which the operator sends a reservation request message to the vertiport; The step of the vertiport sending a reservation approval message or a reservation rejection message to the operator; and A method for exchanging information for vertiport operation, comprising the step of, when the above-mentioned operator receives the above-mentioned reservation approval message, the above-mentioned operator transmitting an arrival / departure report message to the above-mentioned vertiport.

2. In Claim 1, A method for exchanging information for vertiport operation, further comprising the step of the above-mentioned operator transmitting a final reservation status message to the above-mentioned vertiport.

3. In Claim 1, A method for exchanging information for vertiport operation, further comprising the step of the above-mentioned operator transmitting an operation issue notification message to the above-mentioned vertiport.

4. In Claim 1, The step of the above-mentioned operator sending a reservation change request message to the above-mentioned vertiport; The step of the vertiport sending a reservation change approval message or a reservation change rejection message to the operator; and A method for exchanging information for vertiport operation, further comprising the step of the above-mentioned operator transmitting a reservation change status message to the above-mentioned vertiport.

5. In Claim 4, A method for exchanging information for vertiport operation, further comprising the step of the vertiport sending a reservation change notification message to the operator.

6. In Claim 1, The step of the above-mentioned operator sending a reservation cancellation request message to the above-mentioned vertiport; and A method for exchanging information for vertiport operation, further comprising the step of the above-mentioned operator transmitting a reservation cancellation status message to the above-mentioned vertiport.

7. In Claim 6, A method for exchanging information for vertiport operation, further comprising the step of the vertiport sending a reservation cancellation notification message to the operator.

8. In Claim 1, A method for exchanging information for vertiport operation, further comprising the step of the above-mentioned operator transmitting a flight plan approval request message to a traffic control system, and the above-mentioned traffic control system transmitting a flight plan approval message to the above-mentioned operator.

Images