Vertiport entry / exit direction management method and device

Abstract

A corridor management method comprises the steps of: determining a corridor of urban air mobility (UAM), wherein the corridor includes an arrival vertiport of the UAM; transferring the corridor to the UAM; receiving an event around the arrival vertiport from the arrival vertiport; determining the entry direction of the UAM into the arrival vertiport on the basis of the event; and transferring the determined entry direction to the UAM.

Description

Method and device for managing the direction of entry and exit of a vertiport

[0001] The present disclosure relates to a method and device for managing the entry and exit directions of a vertiport.

[0002] As urban traffic becomes saturated, there is a movement to utilize Urban Air Mobility (UAM). UAM requires an airfield, such as a vertiport, for takeoff and landing. To establish a stable UAM flight path (corridor), a UAM traffic management service provider (PSU) can manage the UAM corridor by considering weather conditions (e.g., precipitation, amount, wind direction, wind strength, etc.), obstacles (e.g., surrounding facilities), and no-fly zones. However, the PSU does not manage the direction in which UAM enters or exits a vertiport by considering dynamic information surrounding the vertiport. The following documents are incorporated herein by reference in their entirety.

[0003] Korean Patent Publication No. 10-2023-0078097

[0004] Korean Patent Publication No. 10-2023-0060864

[0005] Korean Patent Publication No. 10-2022-0160413

[0006] Korean Patent Publication No. 10-2022-0013030

[0007] Korean Patent Publication No. 10-2022-0013030

[0008] Korean Patent Publication No. 10-2024-0015292

[0009] Korean Patent No. 10-2445617

[0010] Korean Patent No. 10-2556077

[0011] Korean Urban Air Mobility (K-UAM) Operation Concept 1.0.pdf

[0012] The present disclosure provides a method and device for managing the entry and exit directions of a UAM into a vertiport by using dynamic events (e.g., information that changes over time) around the vertiport.

[0013] In one aspect of the present disclosure, a method for managing entry and exit directions includes the steps of: determining a corridor of urban air traffic (UAM), wherein the corridor includes an arrival vertiport of a UAM; transmitting the corridor to a UAM; receiving an event around the arrival vertiport from the arrival vertiport; determining an entry direction of the UAM to the arrival vertiport based on the event; and transmitting the determined entry direction to the UAM.

[0014] In one embodiment, the event may include real-time floating population around the arrival vertiport.

[0015] In one embodiment, the event may include at least one of wind strength and wind direction around the arrival vertiport.

[0016] In one embodiment, the event may include a flight obstruction that impedes the flight of the UAM.

[0017] In one embodiment, the event may be collected for each of the divided regions, with the perimeter of the arrival vertiport divided into a plurality of regions.

[0018] In one embodiment, the step of determining the direction of entry into the arrival vertiport may include the step of determining the direction of entry so as to pass over any one of the plurality of regions.

[0019] In one embodiment, the step of transmitting the determined entry direction to the UAM may include the step of transmitting the determined entry direction to the UAM through a UAM operator.

[0020] In one embodiment, the step of conveying the corridor to the UAM may include the step of conveying the corridor to the UAM via a UAM operator.

[0021] In one embodiment, the arrival vertiport may further include a step of determining an arrival landing field among the plurality of landing fields and a step of notifying the UAM of the determined arrival landing field.

[0022] In one embodiment, the arrival vertiport may further include a step of receiving an arrival landing pad among the plurality of landing pads and a step of notifying the UAM of the determined arrival landing pad.

[0023] In one embodiment, the corridor management method may further include the step of transmitting the determined entry direction to the arrival vertiport.

[0024] In one embodiment, the method for managing the entry direction of the UAM may be performed by a UAM traffic management service provider (Provider of Services, PSU).

[0025] In one aspect of the present disclosure, a UAM traffic management service provider includes an information collection unit configured to collect information about a departure vertiport and an arrival vertiport, and terrain, obstacle, and weather information between the departure vertiport and the arrival vertiport; a flight planning unit configured to determine a corridor of a UAM between the departure vertiport and the arrival vertiport based on the information collected by the information collection unit; and a communication device configured to transmit the corridor to the UAM. After determining the corridor between the departure vertiport and the arrival vertiport, the information collection unit is configured to further receive an event around the arrival vertiport from the arrival vertiport, and the flight planning unit is configured to further determine an entry direction of the UAM into the arrival vertiport based on the event.

[0026] In one embodiment, the event may include real-time floating population around the arrival vertiport.

[0027] In one embodiment, the event may include at least one of wind strength and wind direction around the arrival vertiport.

[0028] In one embodiment, the event may include a flight obstruction that impedes the flight of the UAM.

[0029] In one embodiment, the communication device may be configured to notify at least one of the UAM and the arrival vertiport of the entry direction.

[0030] In one aspect of the present disclosure, a UAM traffic management service provider includes an information collection unit configured to collect information about a departure vertiport and an arrival vertiport, terrain, obstacles, and weather information between the departure vertiport and the arrival vertiport, and receive an event around the departure vertiport from the departure vertiport; a flight planning unit configured to determine a corridor of the UAM between the departure vertiport and the arrival vertiport based on the information collected by the information collection unit, and further determine an exit direction of the UAM from the departure vertiport based on the event around the departure vertiport; and a communication device configured to transmit the corridor to the UAM.

[0031] In one aspect of the present disclosure, a method for managing an entry or exit direction of urban air traffic (UAM) into a vertiport includes the steps of: collecting events around the vertiport; providing the events to a UAM traffic management service provider (PSU); receiving an entry or exit direction of the UAM into the vertiport from the UAM traffic management service provider; and controlling a guidance device of the vertiport configured to guide takeoff or landing of the UAM based on the entry or exit direction into the vertiport.

[0032] In one embodiment, the event may include real-time floating population around the vertiport.

[0033] In one embodiment, the event may include at least one of wind strength and wind direction around the vertiport.

[0034] In one embodiment, the event may include a flight obstruction that impedes the flight of the UAM.

[0035] In one embodiment, the event may be collected for each of the divided regions, with the periphery of the vertiport divided into a plurality of regions.

[0036] In one embodiment, the direction of entry or exit into the vertiport may be a direction in which the UAM passes over any one of the plurality of areas.

[0037] In one embodiment, the vertiport may further include a step of determining a landing field at which the UAM will land among the plurality of landing fields, and a step of controlling the guidance device based on the determined landing field at which the UAM will land.

[0038] A vertiport according to one aspect of the present disclosure is configured to perform the above method.

[0039] In one aspect of the present disclosure, a method for managing a direction of entry or exit of a UAM into a vertiport includes the steps of collecting events around the vertiport; determining a direction of entry or exit into the vertiport based on the events; and controlling a guidance device of the vertiport, the guidance device being configured to guide takeoff or landing of the UAM based on the determined direction of entry or exit into the vertiport.

[0040] In one embodiment, the event may include real-time floating population around the vertiport.

[0041] In one embodiment, the event may include at least one of wind strength and wind direction around the vertiport.

[0042] In one embodiment, the event may include a flight obstruction that impedes the flight of the UAM.

[0043] In one embodiment, the event may be collected for each of the divided regions, with the periphery of the vertiport divided into a plurality of regions.

[0044] In one embodiment, the direction of entry or exit into the vertiport may be a direction in which the UAM passes over any one of the plurality of areas.

[0045] In one embodiment, the vertiport may further include a step of determining a landing field at which the UAM will land among the plurality of landing fields, and a step of controlling the guidance device based on the determined landing field at which the UAM will land.

[0046] In one aspect of the present disclosure, a vertiport includes a sensor configured to collect events around the vertiport; at least one takeoff and landing pad configured to allow urban air traffic (UAM) vehicles to take off and land; and a guidance device configured to guide takeoff and landing of the UAM. The vertiport includes a control device configured to determine an entry or exit direction of the UAM into the vertiport based on the event, and to control the guidance device based on the entry or exit direction.

[0047] In one embodiment, the sensor may include a camera configured to detect at least one of a real-time floating population around the vertiport and a flight obstacle that impedes the flight of the UAM.

[0048] In one embodiment, the sensor may include a sensor that detects at least one of wind strength and wind direction around the vertiport.

[0049] In one embodiment, the guidance device may include a guidance device configured to notify the direction of entry or exit.

[0050] In one embodiment, the area around the vertiport may be divided into a plurality of regions, and the sensors may be installed corresponding to each of the plurality of regions.

[0051] In one aspect of the present disclosure, a vertiport includes: a sensor configured to collect events around the vertiport; at least one takeoff and landing pad configured to allow urban air traffic (UAM) vehicles to take off and land; a guidance device configured to guide takeoff and landing of the UAM; a communication device configured to provide the event to a UAM traffic management service provider and receive an entry or exit direction of the UAM from the UAM traffic management service provider; and a control device configured to control the guidance device based on the entry or exit direction.

[0052] In one aspect of the present disclosure, a UAM operation system includes a UAM traffic management service provider (PSU) that determines a corridor of urban air traffic (UAM); a vertiport including at least one takeoff and landing pad configured to allow UAM to take off and land and a guidance device configured to guide the UAM to take off and land; and a UAM operator that receives the corridor and operates UAM. The vertiport collects events around the vertiport and transmits the events to the UAM traffic management service provider, and the UAM traffic management service provider determines an entry direction into the vertiport based on the events and transmits the determined entry direction to the vertiport, and the vertiport is configured to control the guidance device based on the determined entry direction.

[0053] In one embodiment, the event may include real-time floating population around the vertiport.

[0054] In one embodiment, the event may include at least one of wind strength and wind direction around the vertiport.

[0055] In one embodiment, the event may include a flight obstruction that impedes the flight of the UAM.

[0056] In one embodiment, the event may be collected for each of the divided regions, with the periphery of the vertiport divided into a plurality of regions.

[0057] In one aspect of the present disclosure, a method for operating a UAM includes the steps of: receiving a flight plan including an arrival vertiport and a corridor from a UAM traffic management service provider; operating a UAM according to the flight plan; receiving an entry direction to the arrival vertiport; and entering in the entry direction and landing at the arrival vertiport.

[0058] In one embodiment, the step of receiving an entry direction to the arrival vertiport may include a step of receiving the entry direction from the UAM traffic management service provider.

[0059] In one embodiment, the step of receiving an entry direction to the arrival vertiport may include the step of receiving the entry direction from the arrival vertiport.

[0060] In one embodiment, the arrival vertiport includes a plurality of takeoff and landing pads, and the operation method of the UAM may include a step of being guided to a takeoff and landing pad at which the UAM will land among the plurality of takeoff and landing pads.

[0061] The present disclosure enables safer flight of UAM by managing the direction of entry and exit of UAM into and out of a vertiport using dynamic events around the vertiport.

[0062] Additionally, the present disclosure enables risk management for unexpected accidents when a UAM takes off from or lands on a vertiport.

[0063] Additionally, the present disclosure can provide an efficient corridor when a UAM takes off from or lands on a vertiport.

[0064] FIG. 1 is a conceptual block diagram of a UAM operation system according to one embodiment of the present disclosure.

[0065] FIG. 2 is a conceptual diagram of UAM operation according to one embodiment of the present disclosure.

[0066] FIGS. 3A to 3C are exemplary diagrams illustrating the operation of a vertiport according to one embodiment of the present disclosure.

[0067] FIG. 4 is a schematic diagram of a vertiport according to one embodiment of the present disclosure.

[0068] FIG. 5 is an exemplary diagram showing a change in the direction of entry and exit of a UAM into a vertiport according to one embodiment of the present disclosure.

[0069] FIG. 6 is a flowchart for determining a vertiport entry direction according to one embodiment of the present disclosure.

[0070] FIG. 7 is a block diagram of a device that may be commonly included in a vertiport (operator), a UAM traffic management service provider, or a UAM operator, according to one embodiment of the present disclosure.

[0071] Below, with reference to the attached drawings, embodiments of the present disclosure are described in detail so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein.

[0072] And in order to clearly explain the present disclosure in the drawings, parts unrelated to the explanation are omitted, and similar parts are given similar drawing reference numerals throughout the specification.

[0073] Throughout the specification, whenever a part is said to "include" a component, this does not mean that it excludes other components, but rather that it may include other components, unless otherwise stated.

[0074] It should be understood that the technology described in this disclosure is not intended to be limited to a particular embodiment, but rather encompasses various modifications, equivalents, and / or alternatives of the embodiments of this disclosure.

[0075] The expression "configured to" as used herein may be used interchangeably with, for example, "suitable for", "having the capacity to", "designed to", "adapted to", "made to", or "capable of", depending on the context. The term "configured to" may not necessarily mean only something "specifically designed to" in terms of hardware. Instead, in some contexts, the expression "a device configured to" may mean that the device is "capable of" in conjunction with other devices or components.

[0076] The prior art documents described in this disclosure are incorporated herein by reference in their entirety, and it will be understood that the contents of the prior art documents can be applied by a person having ordinary skill in the art to the parts briefly described in this disclosure.

[0077] FIG. 1 is a conceptual block diagram of a UAM operation system (1000) according to one embodiment of the present disclosure. Referring to FIG. 1, the UAM operation system (1000) includes a UAM traffic management service provider (100, PSU), a vertiport operator (200), an operation support information provider (300), a UAM operator (400), and a UAM fleet (500).

[0078] In one embodiment, the PSU (100) exchanges necessary information with a vertiport operator (200), an operation support information provider (300), a UAM operator (400), a UAM fleet (500), other stakeholders (not shown), and an air traffic controller (not shown). The PSU (100) can share operation safety information with the vertiport operator (200), an operation support information provider (300), a UAM operator (400), a UAM fleet (500), other stakeholders, and an air traffic controller, and manage traffic flow. The PSU (100) can approve flight plans of UAMs (501, 502, 503) and manage corridors of UAMs (501, 502, 503). For example, the PSU (100) can transmit corridor information to UAMs (501, 502, 503). The PSU (100) can confirm the safety of a newly submitted flight plan by a UAM operator (400) through a comprehensive analysis of other flight plans and operational support information that have already been approved, and approve the same, or adjust the flight plan through cooperation with the UAM operator (400). The PSU (100) can perform real-time traffic management services by synthesizing UAM surveillance information, real-time operation information of UAMs (501, 502, 503), and other national airspace system user information, and can share information with stakeholders when necessary. Other stakeholders can access UAM operation information (UAM aircraft identification information, movement trajectory, etc.) for public interest purposes. This information is provided by the PSU (100). Other stakeholders in charge of public affairs can notify the PSU (100) of this operation restriction when it is necessary to temporarily restrict UAM operation in the airspace over a specific area to ensure public safety, such as due to fire suppression or large-scale outdoor events.

[0079] In one embodiment, the vertiport operator (200) can provide information such as vertiport availability, UAM aircraft operation status, real-time capacity changes, and vertiport area surveillance status to the UAM PSU (100) and UAM operator (400). This information can be used for the UAM operator (400) to establish a flight plan, the PSU (100) to approve a flight plan, manage takeoffs and landings, and provide separation services. The PSU (100) can provide more efficient traffic management services by applying the real-time capacity change information of the vertiport to demand-capacity management. The vertiport operator (200) can receive flight plans or real-time flight information (such as expected arrival times) from the PSU (100) and UAM operator (400) in real time and utilize them for efficient vertiport operation. The vertiport operator (200) can communicate directly with the captain within the vertiport area (including the takeoff and landing process) to ensure safe and efficient UAM operation.

[0080] In one embodiment, the navigation support information provider (300) may collect navigation support information such as terrain, obstacles, and weather and transmit the navigation support information to the PSU (100). In addition, the navigation support information provider (300) may collect navigation support information such as terrain, obstacles, and weather and transmit the information directly to the UAM operator (400) and / or UAMs (501, 502, 503).

[0081] In one embodiment, the UAM operator (400) obtains operational information (corridor availability, departure / arrival airfield availability) and operational safety information (weather, restricted airspace information, etc.) from the PSU (100), the operational support information provider (300), and the vertiport operator (200) and applies them to the flight plan formulation. The UAM operator (400) can provide the PSU (100) with flight plans and real-time operational management information, and receive approved flight plans, operational safety information, and traffic management service information.

[0082] FIG. 2 is a conceptual diagram of UAM operation according to one embodiment of the present disclosure. Referring to FIG. 2, a UAM (501) moves along a corridor (600) from a first vertiport (212) of a first building (210) to a second vertiport (222) of a second building (220). The corridor (600) may be determined by the PSU (100). The determined corridor (600) may be communicated to the UAM (501) via the UAM operator (400) or directly from the PSU (100) to the UAM (501). For illustrative purposes only, the second building (220) is designated as the destination of the UAM (501).

[0083] In one embodiment, the PSU (100) can receive events around each building from each of the first building (210) and the second building (220). In one embodiment, the events can include changes around the buildings. For example, the events can include changes in the number of people around the building, changes in the number of vehicles, changes in the exterior walls of the building (e.g., building cleaning, sunlight reflection, etc.), changes in the takeoff and landing area, wind strength and direction around the building, precipitation conditions around the building, low-altitude flying obstacles (construction facilities, power lines, cranes, flocks of birds, etc.), etc. The events can be limited to the divided areas by segmenting the area around the building. This will be described in detail later. To detect the events, the first and second buildings (210, 220) can each be equipped with sensors (not shown) configured to detect events around their respective buildings (e.g., 222-228 of FIG. 3A and 222'-228' of FIG. 3B). In another embodiment, the event may be an operational opinion of the UAM (501) determined based on changes in the surroundings of the building. For example, the event may include an opinion regarding a change in the direction of entry or exit of the UAM (501) or a change in the takeoff or landing field.

[0084] In one embodiment, the PSU (100) may change the direction of entry / exit to the vertiport of the UAM (501) and / or change the landing field for landing based on the received event. The PSU (100) may transmit the changed direction of entry / exit to the vertiport (not shown) and / or the changed landing field to the vertiport operator (200), the UAM operator (400), and / or the UAM (501). The UAM operator (400) may transmit the received changed direction of entry / exit to the vertiport and / or the landing field to the UAM (501). The UAM (501) may continue its operation based on the changed direction of entry / exit to the vertiport and / or the landing field received from the PSU (100).

[0085] In another embodiment, the first and second buildings (210, 220) may transmit events to the UAM operator (400). The UAM operator (400) may change the direction of entry and exit to the vertiport of the UAM (501) and / or change the landing field for takeoff and landing based on the received events. The UAM operator (400) may transmit the changed direction of entry and exit to the vertiport (not shown) and / or the changed landing field to the UAM (501). The UAM (501) may continue its operation based on the changed direction of entry and exit to the vertiport and / or the landing field received from the UAM operator (400).

[0086] In another embodiment, the first and second buildings (210, 220) may transmit events to the UAM (501). Based on the received events, the UAM (501) may change the direction of entry and exit to the vertiport of the UAM (501) and / or change the landing pad for landing.

[0087] Figures 3a to 3c are exemplary diagrams illustrating the operation of a vertiport according to one embodiment of the disclosure. Referring to Figures 3a and 3b, takeoff and landing pads (V1 to V6, V1' to V4') are installed on the roof of a building (220, 220'), and the building has a rectangular shape when viewed from above. It will be understood that the number and arrangement of the takeoff and landing pads (V1 to V6, V1' to V4') and the shape of the building when viewed from above are exemplary and can be modified in various ways in practice.

[0088] Referring to FIG. 3A, six landing pads (V1 to V6) are installed on the roof of a rectangular building (220). Cameras (222, 224, 226, 228) for detecting events around the building (220) may be installed on the building (220). The cameras (222, 224, 226, 228) may be installed to detect areas facing the sides of the building (220). For example, as illustrated in FIG. 3A, cameras (222, 224, 226, 228) may be installed on each side of the building (220). It will be appreciated that the number and locations of the cameras (222, 224, 226, 228) may be adjusted as needed. It will also be appreciated that the cameras (222, 224, 226, 228) can be installed at appropriate locations to detect events around the building (220), such as the entrance of the building (220), the rooftop of the building (220), etc. In addition, it will be appreciated that instead of the cameras (222, 224, 226, 228), sensors configured to detect events around the building (220) can be installed in the building (220). The cameras (222, 224, 226, 228) can include an AI camera or a 3D depth camera that can analyze images of corresponding areas (230, 240, 250, 260) to determine the number of people, the number of cars, changes in the exterior walls of the building, etc. within the corresponding areas (230, 240, 250, 260). In addition, the sensors can include sensors that determine the wind strength and wind direction around the building, and the precipitation conditions around the building.

[0089] In one embodiment, as illustrated in FIG. 3A, the vertiport operator (200) can collect events occurring in areas (262, 264, 266, 268) corresponding to corners of a building (220) and areas (230, 240, 250, 260) corresponding to faces of the building (220) through a camera (or sensor).

[0090] In one embodiment, an event may include changes in the surroundings of a building. For example, the event may include changes in the number of people around the building, changes in the number of vehicles, changes in the exterior of the building (e.g., building cleaning, sunlight reflection, etc.), changes in the takeoff / landing area, wind strength and direction around the building, precipitation conditions around the building, low-altitude flight obstacles (construction facilities, power lines, cranes, flocks of birds, etc.), etc. A change in the takeoff / landing area means, for example, that the takeoff / landing area of ​​the UAM (501) was initially V1 and has been changed to another takeoff / landing area. The reasons for the takeoff / landing area may vary. For example, the reasons for the change in the takeoff / landing area may include situations where the UAM (501) cannot take off / land on the takeoff / landing area, such as a malfunction or the presence of another object (obstacle).

[0091] It will be appreciated that the areas (230 to 260, 262 to 268) where events are collected, as illustrated in FIG. 3A, are exemplary and may be modified. For example, as illustrated in FIG. 3B, a building (220') may have four landing pads (V1' to V4'), and the area may be divided into areas (230', 240', 250', 260') that include the corners of the building (220'). Additionally, cameras or sensors (222' to 228') may also be installed around the corners of the building (210').

[0092] Additionally, the area where events are collected may vary depending on the shape of the building. FIG. 3C is another exemplary diagram illustrating the operation of a vertiport according to one embodiment of the present disclosure. Referring to FIG. 3C, a case in which the shape of a building (220'') is triangular is illustrated. In this case, the vertiport operator (200) can collect events in areas (230'', 240'', 250'') corresponding to each side of the building (220'') through cameras and / or sensors.

[0093] FIG. 7 is a block diagram of a device that may be commonly included in a UAM traffic management service provider (100), a vertiport operator (200, 600), or a UAM operator (400) according to one embodiment of the present disclosure. The UAM traffic management service provider (100), a vertiport operator (200, 600), or a UAM operator (400) may include a communication device (710), a storage device (720), a control device (730), and an interface (740).

[0094] In one embodiment, the communication device (710) is configured to allow the UAM traffic management service provider (100), the vertiport operator (200, 600), or the UAM operator (400) to communicate with an external device and receive information. The communication method of the communication device (710) may utilize a network built according to GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), HSDPA (High Speed ​​Downlink Packet Access), HSUPA (High Speed ​​Uplink Packet Access), LTE (Long Term Evolution), LTE-A (Long Term Evolution-Advanced), etc.), WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity), Wi-Fi (Wireless Fidelity) Direct, DLNA (Digital Living Network Alliance), WiBro (Wireless Broadband), WiMAX (World Interoperability for Microwave Access), 5G wireless communication network, etc., but is not limited thereto and may include all transmission method standards to be developed in the future. It can include anything that can send and receive data via wired or wireless means.

[0095] Storage (720) includes computer-readable storage media, such as data storage devices, that can be accessed by the computing device and provide persistent storage of data and executable instructions (e.g., software applications, programs, functions, etc.). Examples of storage (720) include volatile and nonvolatile memory, fixed and removable media devices, and any suitable memory device or electronic data repository that maintains data for access by the computing device. Database (120) may include various embodiments of random access memory (RAM), read-only memory (ROM), flash memory, and other types of storage media in various memory device configurations. Storage (720) is configured to store executable software instructions (e.g., computer-executable instructions) that are executable with the processor, or the same software application, which may be implemented as a module.

[0096] The control device (730) is configured to control the operation of a UAM traffic management service provider (100), a vertiport operator (200, 600), or a UAM operator (400). The control device (730) can perform the method provided in the present disclosure when commands stored in the storage device (720) are executed.

[0097] The interface (740) may be configured to receive input from an administrator of a UAM traffic management service provider (100), a vertiport operator (200, 600), or a UAM operator (400).

[0098] FIG. 4 is a schematic diagram of a vertiport (600) according to one embodiment of the present disclosure. Referring to FIG. 4, the vertiport (600) includes landing pads (V1 to V4) and a guidance device (610). As described above, it will be appreciated that the vertiport (600) may further include a control device, a storage device, and a communication device for the operation of the vertiport (600).

[0099] The guidance device (610) may be configured to guide the UAM to take off / land on the takeoff and landing fields (V1 to V4). In one embodiment, the guidance device (610) may be configured to support visual flight and / or instrument flight. Visual flight is a method in which the pilot operates the UAM by checking the entry and exit directions with his / her own eyes. For example, the guidance device (610) for visual flight may include a lamp or the like that can provide visual information to the pilot. Unlike visual flight, instrument flight is a method in which the pilot operates the UAM by referring to instruments inside the UAM. For example, in instrument flight, the guidance device (610) may include an instrument landing system (ILS). The UAM may receive information from the guidance device (610) and provide information for instrument flight to the pilot.

[0100] In one embodiment, the guidance device (610) may include an antenna, a radar, a lamp, etc. The guidance device (610) may be configured to notify the UAM which UAM should take off / land from / to which of the takeoff / landing fields (V1 to V4). The guidance device (610) may be configured to notify the UAM which direction to enter or exit the vertiport.

[0101] In one embodiment, the guidance device (610) may include a first guidance device (602) pointing to each of the takeoff and landing fields (V1 to V4) and a second guidance device (604) installed in a building where the vertiport (600) is installed. The first guidance device (602) may be configured to notify the UAM of which of the takeoff and landing fields (V1 to V4) the UAM will take off from or land on. For example, the first guidance device (602) may be installed in each of the takeoff and landing fields (V1 to V4). The second guidance device (604) may be configured to notify the UAM of which direction to enter or exit the vertiport (600). For example, as illustrated in FIG. 4, the second guidance devices (604) may be installed on each side of the vertiport (600) and configured to notify the UAM of the direction to enter the vertiport (600). Alternatively, the second guidance device (604) may be configured to correspond to the event-collected area and notify the UAM of the airspace over any one of the event-collected areas. The second guidance device (604) may provide the UAM with the information necessary to operate via instrument flight in the direction of entry into the vertiport (600).

[0102] Events around the building where Vertiport collects

[0103] In one embodiment, events around a building collected by a vertiport may include information difficult for a PSU to collect. These events could impact the takeoff and landing of UAMs, and are information that only the vertiport (or the building on which the vertiport is installed) can collect.

[0104] In one embodiment, events collected by a vertiport around a building may include real-time traffic flow around the building. A vertiport can collect traffic flow around a building in real time. A vertiport can divide the building's perimeter into areas, for example, facing the building's face, and collect traffic flow in each area in real time. Traffic flow around a building can be collected through sensors installed on the building where the vertiport is installed.

[0105] In one embodiment, the events collected by the vertiport around a building may be wind information, including wind direction and / or wind strength. Typically, the PSU may consider meteorological information, including weather and wind information, when establishing corridors between vertiports. However, this meteorological information is limited to the information between vertiports, making it difficult to accurately reflect the wind information around the building where the vertiport is installed. Because wind information generated between buildings in urban areas may differ from the information between vertiports, the vertiport needs to collect information such as wind direction and strength around the building.

[0106] In one embodiment, events collected by a vertiport around a building may include flying obstacles. The vertiport can collect flying obstacles in real time, including structures around the building (e.g., construction equipment such as power lines and cranes), and unusual features such as flocks of birds. These flying obstacles are easy for the vertiport to collect, but difficult for the PSU to collect.

[0107] Setting the entry or exit direction according to the events collected by Vertiport

[0108] FIG. 5 is an exemplary diagram illustrating a change in the direction of entry and exit of a UAM into a vertiport according to one embodiment of the present disclosure. FIG. 6 is a flowchart illustrating a method for determining the direction of entry into a vertiport according to one embodiment of the present disclosure.

[0109] Referring to FIGS. 1, 2, and 6, at block S605, the PSU (100) determines a corridor for the UAM. The PSU (100) can determine the corridor for the UAM through a comprehensive analysis of flight plans of other UAMs that have already been approved and operational support information (e.g., weather information, vertiport availability, etc.). At block S610, the UAM (501) can receive the determined corridor from the PSU (100). At block S615, the UAM (501) can navigate from the vertiport (212) to the vertiport (222) along the determined corridor (e.g., 600 of FIG. 2). In one embodiment, the determined corridor may or may not include a landing field for landing at the vertiport (222). If the determined corridor does not include a landing pad for landing, the UAM may be notified of the landing pad from the vertiport (222) before arriving at the vertiport (222).

[0110] Referring to FIG. 5, it is assumed that the UAM (FIG. 2, 501) arrives at the landing pad (V4) of the vertiport (600) along corridor 1. Corridor 1 may or may not include an entry direction to the arrival vertiport (600).

[0111] In one embodiment, as described above, in block S620, the vertiport (600) (or vertiport operator, building) can collect events around the vertiport (600). The vertiport (600) can collect events for each area (area a to area b).

[0112] In block S625, the direction of entry into the vertiport (600) can be determined based on the events collected by the vertiport (600). The entity determining the direction of entry into the vertiport (600) can be at least one of the PSU (100), the vertiport (600), the UAM operator (400), and the UAM (501). That is, in one embodiment, the PSU (100) can receive the events collected by the vertiport (600) from the vertiport (600) and determine the direction of entry into the vertiport (600) based on the events. In one embodiment, the vertiport (600) can determine the direction of entry into the vertiport (600) based on the events collected by the vertiport (600). In one embodiment, the UAM (501) or UAM operator (400) may receive events collected by the vertiport (600) from the vertiport (600) and determine an entry direction to the vertiport (600) based on the events.

[0113] To this end, it will be understood that the PSU (100), the vertiport (600), the UAM operator (400) and the UAM (501) vertiport (600) may further include a control device (730), a storage device (720) and a communication device (710) as illustrated in FIG. 7. The storage devices of the PSU (100), the vertiport (600), the UAM operator (400) and the UAM (501) vertiport (600) store pre-selected criteria for determining an entry direction, and the control device may determine an entry direction to the vertiport (600) based on the pre-selected criteria and collected / received events.

[0114] In one embodiment, an event occurring in area a may determine that landing on the airfield (V4) via area a is difficult. For example, at least one control unit among the PSU (100), the vertiport (600), the UAM operator (400), and the UAM (501) may determine that the number of people in area a is greater than a pre-selected standard, the wind direction and / or strength does not meet the pre-selected standard, or the operation of the UAM is unsafe due to an obstacle in area a.

[0115] The subject of the judgment may be at least one of the PSU (100), the vertiport (600), the UAM operator (400), and the UAM (501). For example, at least one control device among the PSU (100), the vertiport (600), the UAM operator (400), and the UAM (501) may determine to enter the vertiport (600) via area b based on an event that occurred in another area, areas b, c, and d. For example, at least one control device among the PSU (100), the vertiport (600), the UAM operator (400), and the UAM (501) may determine to enter the vertiport (600) via area b by considering at least one of the population, wind direction, wind strength, and obstacles of areas b, c, and d.

[0116] For example, areas where the number of people is greater than a pre-selected criterion, where the wind direction and / or strength does not meet the pre-selected criterion, or where there are obstacles may be excluded from the UAM's entry direction.

[0117] At this time, there may be no change in the landing pad (V4). That is, the direction of entry into the vertiport (600) may be changed and determined in block S625. Generally, a change in the corridor does not necessarily lead to a change in the direction of entry into the vertiport (600). However, a change in the direction of entry into the vertiport (600) will necessarily entail a change in the corridor.

[0118] In one embodiment, it may be determined that landing at the landing pad (V4) via area a is difficult due to an event occurring in area a. The determination may be made by at least one of the PSU (100), the vertiport (600), the UAM operator (400), and the UAM (501). Based on an event occurring in other areas, areas b, c, and d, it may be determined to enter the vertiport (600) via area d. At this time, the landing pad (V4) may be maintained, or the landing pad may be changed (V4->V3) as illustrated in FIG. 5 . In one embodiment, the change of the landing pad may depend on a change in the approach direction. As illustrated in FIG. 5 , when the approach direction is changed, the landing pad may be changed (V4->V3) because the landing pad (V3) is closer to the changed approach direction than the landing pad (V4). However, a change in the takeoff and landing area may not be dependent on a change in the approach direction. That is, it will be understood that a change in the approach direction may not result in a change in the takeoff and landing area.

[0119] In one embodiment, when any one of the PSU (100), the UAM operator (400), and the UAM (501) changes or determines the approach direction, the changed or determined approach direction is transmitted to the vertiport (600). In one embodiment, when any one of the PSU (100), the UAM operator (400), and the UAM (501) changes or determines the takeoff or landing field, the changed or determined takeoff or landing field is transmitted to the vertiport (600).

[0120] Although the areas (262, 264, 266, 268) corresponding to the corners shown in FIG. 3a are not shown in FIG. 5, it will be understood that events in the areas (262, 264, 266, 268) corresponding to the corners can be collected and the direction of entry into the vertiport (600) can be determined based on this.

[0121] The entry direction into the vertiport (600) determined in block S630 is transmitted to the UAM (501). In one embodiment, the entry direction into the vertiport (600) determined may be transmitted to the UAM (501) via the PSU (100). The entry direction into the vertiport (600) determined may be transmitted to the UAM (501) via the vertiport (600). The entry direction into the vertiport (600) determined may also be transmitted to the UAM (501) via the UAM operator (400).

[0122] In block S635, the vertiport (600) can control at least one of the guidance devices (602, 604 of FIG. 4, 602a, 602b, 602c, 602d, 604a, 604d of FIG. 5) depending on the determined entry direction into the vertiport (600).

[0123] In one embodiment, when the entry direction changes from corridor 1 to corridor 2, the vertiport (600) can control at least one of the guidance device (602a) and the guidance device (602b) to guide the UAM (501) to the entry direction into the vertiport (600). For example, when the guidance device (602b) includes a lamp, the vertiport (600) can control the guidance device (602b) to blink or light up. In one embodiment, when the entry direction changes from corridor 1 to corridor 3, the vertiport (600) can control at least one of the guidance devices (602a, 604a, 602d, 604d) to guide the UAM (501) to the entry direction into the vertiport (600). For example, if the induction device (602d, 604d) includes a lamp, the vertiport (600) can control the induction device (602d, 604d) to blink or light up.

[0124] In one embodiment, the vertiport (600) may control at least one of the guidance device (602a) and the guidance device (602b) to provide the UAM (501) with information for instrument flight of the UAM (501). The UAM (501) may be configured to transmit the instrument information to the pilot of the UAM (501) based on the received information.

[0125] In block S640, UAM (501) flies based on the determined entry direction and enters the vertiport (600).

[0126] Although the above description is based on landing, it will be understood that changing the departure direction during takeoff of the UAM based on events around the vertiport is also included in the scope of the present disclosure. For example, the departure direction from the vertiport (600) can be determined based on events collected by the vertiport (600). The entity determining the departure direction from the vertiport (600) may be at least one of the PSU (100), the vertiport (600), the UAM operator (400), and the UAM (501). That is, in one embodiment, the PSU (100) can receive the events collected by the vertiport (600) from the vertiport (600) and determine the departure direction from the vertiport (600) based on the events. In one embodiment, the vertiport (600) can determine the departure direction from the vertiport (600) based on events collected by the vertiport (600). In one embodiment, the UAM (501) or UAM operator (400) may receive events collected by the vertiport (600) from the vertiport (600) and determine the direction of departure from the vertiport (600) based thereon.

[0127] In one embodiment, the direction of entry may influence the corridor setting. Referring again to Figure 5, one of corridors 1 to 3 may be set based on which area is determined to be traversed.

[0128] In this disclosure, a corridor may refer to a rough path between buildings (vertiports). That is, it may only include the path between a departure vertiport and an arrival vertiport, and the corridor may not include the direction in which a UAM enters a vertiport or the direction from which it exits from the vertiport. In this disclosure, the departure direction may refer to the direction in which a UAM departs from a building (vertiport) and enters a designated corridor. In this disclosure, the entry direction may refer to the direction in which a UAM arriving at an arrival vertiport along a corridor enters a building (vertiport) to enter a landing pad.

[0129] In one embodiment, as described above, the UAM traffic management service provider (100) may include a communication device (710), a storage device (720), a control device (730), and an interface (740). When the commands stored in the storage device (720) are executed, the control device (730) may perform the functions of an information collection unit configured to collect information necessary for the flight of the UAM, and a flight planning unit configured to establish a flight plan based on the information. The information collection unit may collect corridor information of the UAM for the vertiport operator (200). The information collection unit may receive information on vertiport availability, UAM aircraft operation status, real-time capacity changes, and vertiport area surveillance status from the vertiport operator (200). The information collection unit may collect operation information on at least one of terrain, obstacles, and weather from the operation support information provider (300). The information collection unit can receive events around the building from the vertiport operator (200) regarding at least one of changes in the number of people around the vertiport, changes in the number of cars, changes in the exterior wall of the building where the vertiport is placed, changes in the takeoff and landing area of ​​the vertiport, wind strength around the building, wind direction, precipitation conditions, and low-altitude flight obstacles. The flight plan establishment unit can establish a UAM flight plan based on any one of the above information and events.

[0130] In one embodiment, the information collection unit may receive a departure vertiport and an arrival vertiport. The information collection unit may receive terrain, obstacles, weather (which may include wind direction and strength), etc., between the departure vertiport and the arrival vertiport. The information collection unit may receive population distribution and real-time number of people between the departure vertiport and the arrival vertiport. The flight planning unit may determine a UAM corridor between the departure vertiport and the arrival vertiport based on the information received by the information collection unit and notify the UAM operator. After determining the UAM corridor, while the UAM is operating, the information collection unit may receive an event around the building from the arrival vertiport regarding at least one of a change in the takeoff and landing field within the arrival vertiport, wind strength and direction around the arrival vertiport, precipitation conditions, and low-altitude flight obstacles. The flight planning unit may determine an entry direction of the UAM into the arrival vertiport based on the event around the building and notify the UAM operator.

[0131] The method according to the present disclosure can be implemented as a processor-readable code on a processor-readable recording medium provided in a server, system, equipment, computer, integrated control device, etc. used by a subject. The processor-readable recording medium includes all types of recording devices that store data readable by the processor. Examples of the processor-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc., and also includes those implemented in the form of a carrier wave, such as transmission via the Internet. In addition, the processor-readable recording medium can be distributed across network-connected computer systems, so that the processor-readable code can be stored and executed in a distributed manner.

[0132] The devices and methods described above may be implemented using hardware components, software components, and / or a combination of hardware components and software components. For example, the devices and components described in the embodiments may be implemented using one or more general-purpose computers or special-purpose computers, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing instructions and responding to them. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. Furthermore, the processing device may access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing device is sometimes described as being used singly; however, those skilled in the art will appreciate that the processing device may include multiple processing elements and / or multiple types of processing elements. For example, the processing device may include multiple processors, or one processor and one controller. Additionally, other processing configurations, such as parallel processors, are also possible.

[0133] Software may include a computer program, code, instructions, or a combination of one or more of these, and may configure a processing device to perform a desired operation or, independently or collectively, command the processing device. The software and / or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual equipment, computer storage medium or device, or transmitted signal wave, for interpretation by the processing device or for providing instructions or data to the processing device. The software may also be distributed over networked computer systems and stored or executed in a distributed manner. The software and data may be stored on one or more computer-readable recording media.

[0134] The described embodiments of the present disclosure can also be implemented in distributed computing environments, where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0135] Although the embodiments described above have been described with limited drawings, those skilled in the art will appreciate that various technical modifications and variations can be applied based on the above. For example, appropriate results can still be achieved even if the described techniques are performed in a different order than described, and / or components of the described systems, structures, devices, circuits, etc. are combined or combined in a different manner than described, or are replaced or substituted with other components or equivalents.

[0136] Therefore, other implementations, other embodiments, and equivalents to the claims also fall within the scope of the claims set forth below.

Claims

1. A method for managing the entry and exit directions of urban air traffic (UAM) into the vertiport. A step of collecting events around the above-mentioned vertiport; A step of providing the above event to a UAM traffic management service provider (Provider of Services, PSU); A step of receiving an entry or exit direction of the UAM to the vertiport from the UAM traffic management service provider; A step of controlling a guidance device of the vertiport, which is configured to guide takeoff and landing of the UAM based on the direction of entry or exit to the vertiport, method.

2. In paragraph 1, The above event includes a real-time floating population around the vertiport.

3. In paragraph 1, A method wherein the above event comprises at least one of wind strength and wind direction around the vertiport.

4. In paragraph 1, The method wherein the above event includes a flight obstacle that interferes with the flight of the UAM.

5. In paragraph 1, The above event is a method in which the surroundings of the vertiport are divided into a plurality of areas and collected for each of the divided areas.

6. In paragraph 5, A method wherein the direction of entry or exit into the above-mentioned vertiport is a direction in which the UAM passes over any one of the plurality of areas.

7. In paragraph 1, The above-mentioned vertiport includes multiple takeoff and landing pads, A step of determining a landing pad on which the UAM will land among the plurality of landing pads; and A method further comprising a step of controlling the guidance device based on the landing field where the determined UAM will land.

8. A buttiport configured to perform the methods of clauses 1 to 7.

9. As a method for managing the direction of entry or exit of UAM into the vertiport, A step of collecting events around the above-mentioned vertiport; A step of determining the direction of entry or exit to the vertiport based on the above event; and A step of controlling a guidance device of the vertiport, which is configured to guide takeoff and landing of the UAM based on the direction of entry or exit to the determined vertiport, method.

10. In paragraph 9, The above event includes a real-time floating population around the vertiport.

11. In paragraph 9, A method wherein the above event comprises at least one of wind strength and wind direction around the vertiport.

12. In paragraph 9, The method wherein the above event includes a flight obstacle that interferes with the flight of the UAM.

13. In paragraph 9, The above event is a method in which the surroundings of the vertiport are divided into a plurality of areas and collected for each of the divided areas.

14. In paragraph 13, A method wherein the direction of entry or exit into the above-mentioned vertiport is a direction passing through the airspace of any one of the above-mentioned multiple areas.

15. In paragraph 9, The above-mentioned vertiport includes multiple takeoff and landing pads, A step of determining a landing pad on which the UAM will land among the plurality of landing pads; and A method further comprising a step of controlling the guidance device based on the landing pad where the UAM will land.

16. A buttiport configured to perform the methods of clauses 9 to 15.

17. As a vertiport, A sensor configured to collect events around the above-mentioned vertiport; At least one airfield configured to allow urban air traffic (UAM) to take off and land; and Includes a guidance device configured to guide takeoff and landing of the above UAM, A control device configured to determine the entry or exit direction of the UAM into the vertiport based on the event and to control the guidance device based on the entry or exit direction, Vertiport.

18. In paragraph 17, A vertiport, wherein the sensor comprises a camera configured to detect at least one of a real-time floating population around the vertiport and a flight obstacle that impedes the flight of the UAM.

19. In paragraph 17, A vertiport, wherein the sensor comprises a sensor that detects at least one of the wind strength and the wind direction around the vertiport.

20. In paragraph 17, A vertiport, wherein the above-mentioned guidance device comprises a guidance device configured to notify the direction of entry.

21. In paragraph 17, A vertiport in which the area surrounding the above-mentioned vertiport is divided into a plurality of areas, and the sensors are installed corresponding to each of the plurality of areas.

22. As a vertiport, A sensor configured to collect events around the above-mentioned vertiport; At least one airfield configured to allow urban air mobility (UAM) to take off and land; A guidance device configured to guide takeoff and landing of the above UAM; A communication device that provides the above event to a UAM traffic management service provider and receives the entry or exit direction of the UAM from the UAM traffic management service provider, and Including a control device configured to control the guidance device based on the entry or exit direction. Vertiport.

Images