Flight service system

Abstract

To provide a flight service system capable of meeting many needs in a single flight in a flight service using an aircraft.SOLUTION: In the flight service system, a management system 100 holds information on an observation request in an observation request database 200 requested from a client other than a user of a flight service. The observation request includes an observation point designated by a requester. A flight route of an object aircraft 10 on which a user U boards is generated to pass through the observation point.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present disclosure relates to a technology for providing flight services using aircraft. [Background technology]

[0002] Patent Document 1 discloses a system that provides various information, such as weather information, to aircraft in real time. The various information is provided in the form of three-dimensional mesh data so that the aircraft can avoid obstacles such as bad weather. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2001-110000 A Summary of the Invention [Problem to be solved by the invention]

[0004] Consider flight services that use aircraft. If an aircraft can be used for other purposes while carrying users (passengers) of the flight service, it can meet many needs in one flight, making it more efficient. There is room for improvement in flight services that use aircraft. [Means for solving the problem]

[0005] One aspect of the present disclosure relates to a flight service system that provides flight services using aircraft. The flight service system one or more processors; one or more storage devices for storing information on observation requests made by requesters other than flight service users; Equipped with. An observation request includes an observation point specified by the requester. The one or more processors generate a flight route for the target aircraft in which the user is boarding, passing through the observation point. Effect of the Invention

[0006] According to the present disclosure, a flight route of a target aircraft on which a user boards is generated so as to pass through observation points designated by a requester other than the user. The target aircraft is able to perform observations at the observation points while flying along the flight route with the user on board. That is, one flight of the target aircraft can not only transport users of the flight service but also respond to observation requests made by requesters. Many needs can be met in one flight, which is efficient. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a conceptual diagram for explaining an overview of a flight service system. [Diagram 2] FIG. 2 is a conceptual diagram for explaining an observation request database. [Diagram 3] FIG. 1 is a conceptual diagram to explain observation cooperation using aircraft flights. [Figure 4] FIG. 13 is a conceptual diagram for explaining division of an observation target space. [Diagram 5] FIG. 2 is a block diagram showing an example of the configuration of a management system. [Figure 6] 4 is a flow chart illustrating an example process associated with a flight service reservation. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0009] 1. Flight Service System Overview Consider a flight service using an aircraft. For example, an electric vertical take-off and landing aircraft (eVTOL) is used as the aircraft. In the following description, a flight service using an eVTOL is considered as an example. However, this embodiment is not limited to eVTOL. When generalizing, "eVTOL" in the following description is replaced with "aircraft".

[0010] 1 is a conceptual diagram for explaining an overview of a flight service system 1 according to the present embodiment. The flight service system 1 provides a flight service using an eVTOL 10.

[0011] The eVTOL10 is a small and lightweight VTOL driven by an electric motor. More specifically, the eVTOL10 includes a rotor, a power unit, and a control unit. The power unit includes an electric motor that rotates the rotor, a battery that supplies power to the electric motor, and the like. The battery is, for example, a storage battery such as an all-solid-state battery. Alternatively, the battery may be a fuel cell. The control unit controls the flight of the eVTOL10 by controlling the power unit. Such an eVTOL10 has features such as space saving, low cost, and low noise compared to general aircraft. In addition, the eVTOL10 can stop in the air and rotate on the spot. Therefore, the eVTOL10 can create a new experience that cannot be experienced on a normal passenger aircraft.

[0012] The takeoff and landing field 20 is a place where the eVTOL 10 takes off or lands. The takeoff and landing field 20 may include a charging facility, a battery exchange facility, a maintenance facility, and the like. Examples of the takeoff and landing field 20 include an airport, an airfield, a heliport, a rooftop of a building, an eVTOL hangar, and the like. As another example, the takeoff and landing field 20 may be an automobile dealership. By using the dealership as the takeoff and landing field 20, it is possible to seamlessly connect ground mobility services using automobiles and flight services using the eVTOL 10. In addition, it is possible to provide both mobility services at one stop.

[0013] In FIG. 1, airfield 20-1 is the departure point, and airfield 20-2 is the destination. A user U of a flight service boards an eVTOL 10 at airfield 20-1. The eVTOL 10 carrying the user U takes off from airfield 20-1, flies toward airfield 20-2, and lands at airfield 20-2. The user U disembarks from the eVTOL 10 that has landed at airfield 20-2.

[0014] The user terminal 30 is a terminal used by a user U. Examples of the user terminal 30 include a smartphone, a tablet, and a PC.

[0015] The management system 100 manages the entire flight service. For example, the management system 100 manages the eVTOL 10, the airstrip 20, accepts flight reservations from the user U, and determines an itinerary (flight route and flight schedule) for the user U. The management system 100 can communicate with the eVTOL 10, terminals installed at the airstrip 20, and the user terminal 30. Typically, the management system 100 performs wireless communication. The management system 100 may be composed of a single management server, or may be composed of multiple management servers that perform distributed processing.

[0016] As described above, the eVTOL 10 can stop in the air and rotate on the spot. Therefore, the eVTOL 10 can create a new experience that cannot be experienced with a normal passenger aircraft. For example, the eVTOL 10 may stop at a spot where a beautiful view can be seen during the flight from the airstrip 20-1 (departure point) to the airstrip 20-2 (destination point). A user U aboard the eVTOL 10 can enjoy the beautiful view from the spot at a preferred angle.

[0017] 2. Observation cooperation If the eVTOL10 could be used for other purposes while carrying a user U (passenger), it would be possible to meet multiple needs in a single flight, making it more efficient.

[0018] For example, meteorological information in the sky (temperature, humidity, wind speed, wind direction, etc.) can be used for various purposes such as academic research, weather information services, and flight route determination. Therefore, there is a need to observe and collect meteorological information for a specific area in the sky. If the eVTOL 10, while carrying the user U, could pass through the specific area and observe the meteorological information for the specific area, it would kill two birds with one stone. In other words, in one flight of the eVTOL 10, it would be possible not only to transport the user U of the flight service, but also to observe and collect useful meteorological information.

[0019] From the above perspective, the flight service system 1 according to this embodiment is configured not only to provide flight services to the user U, but also to cooperate with observations requested by a requester X other than the user U. For this purpose, an "observation request database 200" is prepared.

[0020] 2 is a conceptual diagram for explaining the observation request database 200. The management system 100 holds the observation request database 200. The observation request database 200 is a database that accumulates observation requests made by various requesters X.

[0021] An observation request indicates the observation content desired by a requester X. More specifically, an observation request includes at least an "observation target" and an "observation point (observation location)" specified (desired) by the requester X. The observation target is typically a physical quantity, and examples include temperature, humidity, air pressure, wind speed, wind direction, cloud cover, rainfall, etc. An observation point is defined by latitude, longitude, and altitude. At least one of latitude, longitude, and altitude may be given within a certain range. In other words, an observation point may be any of a specific position (pinpoint), a specific line, a specific range, and a specific space. An observation request may further include an "observation time zone" specified (desired) by the requester X.

[0022] The requester X is other than the user U. Examples of the requester X include a research institute, a private company, a weather forecasting company, an airline, and the like. The requester X may be an organization that provides the flight service according to the present embodiment. This is because weather information in the sky is useful when determining whether or not the eVTOL 10 can be operated and when determining the flight route. The requester X can register a desired observation request in the management system 100. For example, information on the desired observation request is input to the terminal of the requester X. The terminal of the requester X transmits the input information on the observation request to the management system 100. The management system 100 accumulates the observation requests received from various requesters X in the observation request database 200.

[0023] Figure 3 is a conceptual diagram for explaining observation cooperation using the flight of the eVTOL 10. The eVTOL 10 is equipped with a sensor 15 that can observe an observation target.

[0024] First, the user U operates the user terminal 30 to specify a departure point (takeoff and landing field 20-1) and a destination point (takeoff and landing field 20-2). The management system 100 acquires information on the departure point and destination point specified by the user U. The management system 100 sets an "observation target space" between the departure point and the destination. The observation target space is, for example, a space that can be reached within a certain time from a normal flight route FR0 between the departure point and the destination. As another example, the observation target space may be a space within a certain distance from a normal flight route FR0 between the departure point and the destination. The management system 100 refers to the observation request database 200 to extract at least one observation point PX included in the observation target space. In addition, the management system 100 selects an eVTOL 10 equipped with a sensor 15 capable of observing an observation target at the extracted observation point PX as a target eVTOL to be boarded by the user U. Then, the management system 100 generates a flight route FRX for the target eVTOL to pass through the observation point PX.

[0025] The management system 100 may further take into account the observation time slot specified by the requester X. Specifically, the management system 100 grasps the desired flight period between the desired departure time and desired arrival time specified by the user U. The management system 100 then refers to the observation request database 200 to extract observation requests whose observation time slots are included in or close to the desired flight period. The management system 100 then generates a flight route FRX for the target eVTOL so that the flight route FRX passes through the observation point PX specified in the extracted observation request.

[0026] Thus, according to this embodiment, a flight route FRX of the target eVTOL on which the user U is aboard is generated so as to pass through the observation point PX specified by the requester X. The target eVTOL is able to perform observations at the observation point PX while flying along the flight route FRX with the user U on board. That is, one flight of the target eVTOL can not only transport the user U of the flight service, but also respond to observation requests made by the requester X. Many needs can be met in one flight, which is efficient.

[0027] The flight route FRX passing through the observation point PX is likely to be longer than the normal flight route FR0. As a result, the flight time in the case of the flight route FRX is likely to be longer than the flight time in the case of the normal flight route FR0. Therefore, the management system 100 may allow the user U to select whether or not to accept the flight route FRX before finalizing the flight route FRX. Specifically, the management system 100 generates itinerary information (observation cooperation itinerary information) including the flight route FRX passing through the observation point PX and the flight schedule in that case. The flight schedule includes the departure time, the arrival time, and the required flight time. Then, the management system 100 transmits the itinerary information to the user terminal 30 of the user U, and the user terminal 30 presents the received itinerary information to the user U. That is, the management system 100 presents the itinerary information to the user U via the user terminal 30. The user U considers the contents of the presented itinerary information and inputs whether or not to accept it. The information input by the user U is sent from the user terminal 30 to the management system 100. If the itinerary information is approved by the user U, the management system 100 confirms the itinerary information.

[0028] The management system 100 may present both the "observation cooperation itinerary information" for the flight route FRX and the "normal itinerary information" for the normal flight route FR0 to the user U via the user terminal 30. The user U may compare the two itinerary information and select one of the two itinerary information.

[0029] When the user U accepts the observation cooperation itinerary information, the management system 100 may give a reward to the user U. That is, the management system 100 may give the user U an incentive to accept the observation cooperation itinerary information. For example, the management system 100 may present reward information to the user U together with the observation cooperation itinerary information. The reward information may include, for example, information that a flight fare will be discounted if the user U accepts the observation cooperation itinerary information. As another example, the reward information may include information that a reward such as points or a coupon will be given. By presenting the reward information to the user U, the user U is more likely to accept the observation cooperation itinerary information. As a result, the possibility of responding to the observation request made by the requester X is also increased. That is, it is possible to increase the satisfaction of the requester X while suppressing the dissatisfaction of the user U.

[0030] The management system 100 may recommend a recommended point near the observation point PX to the user U. The recommended point is, for example, a spot where a good view can be seen. A database in which various recommended points are accumulated is prepared in advance. The management system 100 can grasp the recommended points near the observation point PX by referring to the recommended point database. The management system 100 generates a flight route FRX of the target eVTOL so as to pass through the observation point PX and its nearby recommended points. Such recommended points can also be an incentive for the user U to accept the observation cooperation itinerary information. Therefore, the reward information presented to the user U is generated so as to include information on the recommended points. This increases the possibility that the user U will accept the observation cooperation itinerary information.

[0031] Next, with reference to FIG. 4, the division of the "observation target space" will be considered. As described above, the observation target space is a predetermined space between the departure point and destination of the target eVTOL on which the user U boards. The observation target space is, for example, a space that can be reached within a certain time from the normal flight route FR0 between the departure point and the destination. As another example, the observation target space may be a space within a certain distance from the normal flight route FR0 between the departure point and the destination. When a large number of observation requests are accumulated in the observation request database, the observation target space may include multiple observation points PX. In FIG. 4, the direction S means the height direction or the horizontal direction. In the example shown in FIG. 4, the multiple observation points PX included in the observation target space are distributed over a wide range in the direction S.

[0032] In the example (A) in FIG. 4, a flight route FRX is generated so as to pass through all of the observation points PX included in the observation target space. Such a roundabout flight route FRX is inefficient and undesirable from the viewpoint of energy consumption. For example, there is a flight section in the reverse direction returning to the departure point in addition to the forward direction toward the destination. This means that energy is wasted. In addition, the flight route FRX becomes excessively long, and the required flight time becomes excessively long, resulting in a decrease in the satisfaction level of the user U.

[0033] In order to generate a more efficient flight route FRX, as shown in the example (B) in FIG. 4, the management system 100 may divide the observation target space into a plurality of unit spaces SU. For example, the observation target space is divided into a plurality of unit spaces SU in the direction S. The plurality of unit spaces SU may have equal sizes. Next, the management system 100 selects one of the plurality of unit spaces SU. Then, the management system 100 generates a flight route FRX for the target eVTOL so that the flight route FRX passes through one or more observation points PX included in the selected one unit space SU. This generates an efficient flight route FRX, and the target eVTOL can efficiently go around the observation points PX. As a result, unnecessary energy consumption is suppressed. In addition, the valuable time of the user U during the flight is also suppressed from being wasted.

[0034] The observation target space may be divided in the height direction or in the horizontal direction. Alternatively, the observation target space may be divided in both the height direction and the horizontal direction. From the viewpoint of energy, changing the altitude of the eVTOL 10 requires more energy. In order to minimize the amount of movement of the eVTOL 10 in the height direction, the observation target space may be divided into a plurality of unit spaces at least in the height direction. Since the amount of movement of the eVTOL 10 in the height direction is suppressed, energy consumption is further suppressed.

[0035] When multiple eVTOLs 10 are operated, multiple unit spaces SU may be shared by the multiple eVTOLs 10. In other words, different unit spaces SU may be assigned to different eVTOLs 10. This makes it possible to efficiently achieve observation in multiple unit spaces SU.

[0036] In the above, a case where the aircraft used for the flight service is an eVTOL10 has been described. The same effect as above can be obtained even when an aircraft other than the eVTOL10 is used. However, the eVTOL10 can stop (hover) at the same position for a while. Therefore, when the eVTOL10 is used, it is possible to observe the time change of the observation target (physical quantity) at the same observation point PX. In that sense, the use of the eVTOL10 is preferable.

[0037] 2. Management system configuration example 5 is a block diagram showing an example of the configuration of the management system 100. The management system 100 includes one or more processors 101 (hereinafter simply referred to as processors 101), one or more storage devices 102 (hereinafter simply referred to as storage devices 102), and a communication interface 103.

[0038] The processor 101 executes various processes. For example, the processor 101 manages the eVTOL 10, manages the airfield 20, accepts flight reservations from the user U, and determines an itinerary (flight route and flight schedule) for the user U. Examples of the processor 101 include a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and the like.

[0039] The storage device 102 stores various types of information. Examples of the storage device 102 include a volatile memory, a non-volatile memory, a hard disk drive (HDD), and a solid state drive (SSD).

[0040] The communication interface 103 is communicatively connected to each eVTOL 10, a terminal installed at each takeoff and landing field 20, each user terminal 30, etc. The processor 101 communicates with each eVTOL 10, a terminal installed at each takeoff and landing field 20, each user terminal 30, etc. via the communication interface 103.

[0041] The management program PROG is a computer program executed by the processor 101. The functions of the management system 100 may be realized by cooperation between the processor 101, which executes the management program PROG, and the storage device 102. The management program PROG is stored in the storage device 102. Alternatively, the management program PROG may be recorded in a computer-readable recording medium.

[0042] The storage device 102 stores eVTOL management information 110, airfield information 120, user information 130, itinerary information 140, reward information 150, observation request database 200, etc.

[0043] The eVTOL management information 110 is information for managing each eVTOL 10. For example, the eVTOL management information 110 includes the aircraft ID, location information, performance information, status information, schedule information, etc. of each eVTOL 10. The location information is measured by a Global Navigation Satellite System (GNSS) or an altimeter mounted on the eVTOL 10, and is transmitted from the eVTOL 10 to the management system 100. The performance information includes a cruising distance, a maximum flight speed, a battery performance, information of the sensor 15 for observing the observation target, etc. The status information includes an operating state (waiting, flying), a flight speed, etc., and is transmitted from the eVTOL 10 to the management system 100. The schedule information indicates the flight schedule and flight route of the eVTOL 10.

[0044] The airstrip information 120 is information related to each airstrip 20. For example, the airstrip information 120 includes the ID, location information, facility information, schedule information, etc. of each airstrip 20. The location information (latitude, longitude) of each airstrip 20 is known information. The facility information indicates the presence or absence of charging facilities, the presence or absence of maintenance facilities, etc. The schedule information indicates which eVTOL 10 is present (available) at each airstrip 20 and when.

[0045] The user information 130 is information related to a user U of a flight service. For example, the user information 130 includes the user ID, registration information, reservation information, usage history information, and the like of each user U.

[0046] The itinerary information 140 is information related to the itinerary of the flight booked by the user U. For example, the itinerary information 140 includes an itinerary ID, a user ID of the user U, an aircraft ID of the eVTOL 10 to be used, a departure point (first takeoff and landing pad 20-1), a destination point (second takeoff and landing pad 20-2), a flight route, a flight schedule (departure time, arrival time, required flight time), a flight fare, and the like.

[0047] The reward information 150 provides an incentive to the user U to accept the itinerary information 140 (observation cooperation itinerary information) including the flight route FRX. For example, the reward information 150 offers a discount on flight fares or a coupon. As another example, the reward information 150 may include information on recommended points near the observation point PX.

[0048] The observation request database 200 is as described above (see FIG. 2). The observation request database 200 is a database that accumulates observation requests made by various requesters X.

[0049] 3. Processing example 6 is a flowchart showing an example of a process related to a flight service reservation. A user U who wishes to use a flight service starts up a flight service application on the user terminal 30.

[0050] In step S110, the processor 101 accepts a flight service request from the user U. For example, the flight service request includes a desired date of use, a desired departure time, a desired arrival time, a departure point (airport 20-1), a destination point (airport 20-2), and the like. The flight service request corresponds to search information for the user U to search for a flight service. More specifically, the user U inputs a flight service request using the user terminal 30. The user terminal 30 transmits the input flight service request to the management system 100. The processor 101 of the management system 100 receives the flight service request via the communication interface 103. The processor 101 stores the received flight service request in the storage device 102.

[0051] In step S120, the processor 101 executes an "itinerary creation process" that creates one or more itineraries from a departure point (airport 20-1) to a destination point (airport 20-2) in response to the flight service request. For example, the processor 101 selects an eVTOL 10 that is available at the departure point at the desired departure time on the desired use date as a target eVTOL based on the eVTOL management information 110 and the airport information 120. The processor 101 also acquires location information of the departure point and the destination point based on the airport information 120. Then, the processor 101 determines one or more flight routes from the departure point to the destination point.

[0052] In step S120, the processor 101 may generate a flight route FRX that passes through the observation point PX. Specifically, the processor 101 sets an observation target space between the departure point and the destination. The processor 101 refers to the observation request database 200 to extract at least one observation point PX included in the observation target space. The processor 101 also refers to the eVTOL management information 110 to select an eVTOL 10 equipped with a sensor 15 that can observe an observation target at the observation point PX as a target eVTOL. Then, the processor 101 generates a flight route FRX for the target eVTOL so as to pass through the observation point PX.

[0053] The processor 101 may further take into account the observation time slot specified by the requester X. Specifically, the processor 101 grasps the desired flight period between the desired departure time and the desired arrival time specified by the user U. The processor 101 then refers to the observation request database 200 to extract observation requests whose observation time slots are included in or close to the desired flight period. The processor 101 then generates a flight route FRX for the target eVTOL to pass through the observation point PX specified in the extracted observation request.

[0054] The processor 101 may divide the observation target space into a plurality of unit spaces SU (see FIG. 4). In this case, the processor 101 selects one of the plurality of unit spaces SU. Then, the processor 101 generates a flight route FRX for the target eVTOL to pass through one or more observation points PX included in the selected one unit space SU.

[0055] The processor 101 may generate both a normal flight route FR0 that does not pass through the observation point PX, and a flight route FRX that passes through the observation point PX.

[0056] In step S130, the processor 101 presents the itinerary information 140 to the user U. The itinerary information 140 includes a departure point, a destination, a flight route, a flight schedule (departure time, arrival time, required flight time), information on the target eVTOL, and the like. The processor 101 transmits the itinerary information 140 to the user terminal 30 of the user U via the communication interface 103. The user terminal 30 presents the itinerary information 140 to the user U.

[0057] The observation cooperation itinerary information is itinerary information 140 in the case of a flight route FRX that passes through an observation point PX. When the flight route FRX is generated, the processor 101 presents the observation cooperation itinerary information to the user U. In this case, the processor 101 may present the user U with reward information 150 together with the observation cooperation itinerary information.

[0058] The normal itinerary information is the itinerary information 140 for a normal flight route FR0 that does not pass through the observation point PX. The processor 101 may present the user U with both the observation cooperation itinerary information and the normal itinerary information.

[0059] In step S140, the user U considers whether to accept the presented itinerary information 140. If multiple itinerary information 140 are presented, the user U may select one from the multiple itinerary information 140. For example, the user U makes a decision or selection by referring to the required flight time and the usage fee. If the user U does not accept the presented itinerary information 140, the user U may change the flight service request. In that case, the process returns to step S110.

[0060] When accepting the presented itinerary information 140, the user U instructs the user to confirm the reservation using the user terminal 30. The user terminal 30 transmits a reservation confirmation request to the management system 100. The processor 101 of the management system 100 receives the reservation confirmation request via the communication interface 103. In response to the reservation confirmation request, the processor 101 confirms the itinerary information 140 regarding the user U. Then, the processor 101 updates the eVTOL management information 110, the airfield information 120, and the user information 130 based on the confirmed reservation contents. [Explanation of symbols]

[0061] 1... flight service system, 10... eVTOL, 20... takeoff and landing field, user terminal 30, 100... management system, 200... observation request database

Claims

1. A flight service system for providing flight services using aircraft, one or more processors; one or more storage devices for storing information on observation requests made by requesters other than users of the flight service; Equipped with the observation request includes an observation point specified by the requester; The one or more processors are configured to generate a flight route for a target aircraft in which the user is boarding, the flight route passing through the observation point. Flight service system.

2. 2. The flight service system of claim 1, The one or more processors further include: When an observation target space between the departure point and the destination point of the target aircraft includes a plurality of observation points, the observation target space is divided into a plurality of unit spaces; selecting one of the plurality of unit spaces; The flight route of the target aircraft is generated so as to pass through one or more observation points included in the selected one unit space. It was configured as Flight service system.

3. 3. A flight service system according to claim 2, comprising: The one or more processors are configured to divide the observation target space into the plurality of unit spaces at least in a height direction. Flight service system.

4. 2. The flight service system of claim 1, The one or more processors further include: presenting to the user itinerary information including the generated flight route and flight schedule, and reward information that provides the user with an incentive to accept the itinerary information; Confirming the itinerary information if the itinerary information is accepted by the user. It was configured as Flight service system.

5. A flight service system according to any one of claims 1 to 4, comprising: The aircraft is an electric vertical take-off and landing aircraft. Flight service system.

Images