Reservation management device, reservation management method, and computer program

Abstract

To provide a reservation management device or the like capable of preventing a specific user from monopolizing the reservation of a takeoff / landing place in the reservation of the takeoff / landing place of a personal aircraft.SOLUTION: Receiving, from a user, an occupation request including an occupation time period and a desired occupation amount for a landing area; acquiring a usage amount of the user within a predetermined period; determining whether a sum of the usage amount and the desired occupation amount exceeds a predetermined upper limit; The reservation management device includes request processing means for setting the user as a new occupation candidate when the desired occupation amount is higher than the desired occupation amount presented by the occupation candidate in the occupation time zone, and reservation means for determining the user set as the occupation candidate as an occupant in the occupation time zone at a predetermined acceptance end time and making a reservation.SELECTED DRAWING: Figure 25

Description

[Technical Field]

[0001] The present disclosure relates to a reservation management device, a reservation management method, and a computer program. [Background technology]

[0002] In recent years, with the increasing popularity of personal aircraft, there is a demand for a system that can appropriately manage reservations for landing and takeoff sites for personal aircraft.

[0003] For example, Patent Document 1 describes a technology for managing reservations for takeoff and landing sites for unmanned aerial vehicles that deliver luggage. The server described in Patent Document 1 accepts from a user a designated time and location at which the user wishes to deliver luggage by the unmanned aerial vehicle. The server identifies parking lots that are available for reservation during a specific time slot determined based on the designated time and that are located within a specific distance from the designated location. The server then reserves the specified time slot in the identified parking lot as a takeoff and landing site for the unmanned aerial vehicle. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2022-057888 Summary of the Invention [Problem to be solved by the invention]

[0005] The technology described in Patent Document 1 accepts a specified time and location from a user, but the time slot and takeoff and landing field to be reserved are identified by a server. Users have a need to directly specify a specific time slot and a specific takeoff and landing field for a reservation. When building a system to meet this need, there is a possibility that multiple users will wish to reserve the same time slot at the same takeoff and landing field. When such a conflict arises, it is preferable for the system to treat each user's request fairly and to be able to allocate the space so that a specific user does not monopolize the reservations for the takeoff and landing field.

[0006] An object of the present disclosure is to provide a reservation management device, a reservation management method, and a computer program that can prevent a specific user from monopolizing reservations for an airfield for personal aircraft. [Means for solving the problem]

[0007] A reservation management device according to one aspect of the present disclosure includes an input receiving means for receiving an occupancy request from a user, the request including the occupancy time slot of the takeoff and landing field and the desired occupancy amount; an acquisition means for acquiring the amount of usage by the user within a specified period; a determination means for determining whether the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit; a request processing means for setting the user as a new occupancy candidate if it is determined that the upper limit is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time slot; and a reservation means for determining the user who has been set as the occupancy candidate as the occupant of the occupancy time slot at a predetermined acceptance closing time and making a reservation.

[0008] In one aspect of the reservation management method of the present disclosure, a computer receives an occupancy request from a user, the request including the occupancy time slot of an airfield and the desired occupancy amount, obtains the amount of usage by the user within a specified period, determines whether the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit, and if it determines that the upper limit is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time slot, sets the user as a new occupancy candidate, and at a predetermined closing time for reservations, determines the user who has been set as the occupancy candidate to be the occupant of the occupancy time slot, and makes a reservation.

[0009] A computer program according to one embodiment of the present disclosure causes a computer to perform the following processes: receiving an occupancy request from a user, the request including an occupancy time slot for an airfield and a desired occupancy amount; obtaining the amount of usage by the user within a specified period of time; determining whether the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit; setting the user as a new occupancy candidate if it is determined that the upper limit is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time slot; and determining the user who has been set as the occupancy candidate as the occupant of the occupancy time slot at a predetermined closing time for reservations and making a reservation. [Effects of the Invention]

[0010] According to the present disclosure, it is possible to provide a reservation management device, a reservation management method, and a computer program that can prevent a specific user from monopolizing reservations for a landing and takeoff field for a personal aircraft. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a conceptual diagram illustrating a reservation management system according to the present disclosure. [Figure 2] 1 is a block diagram illustrating an example of a configuration of a reservation management device according to the present disclosure. [Figure 3] FIG. 10 is a diagram illustrating an example of a machine information input screen according to the present disclosure. [Figure 4] FIG. 10 is a diagram illustrating an example of an occupancy request screen according to the present disclosure. [Figure 5] FIG. 10 is a diagram showing an example of a reservation status confirmation screen in the present embodiment. [Figure 6] FIG. 10 is a diagram illustrating an example of occupancy request log information in the present disclosure. [Figure 7] FIG. 2 is a diagram illustrating an example of aircraft model list information in the present disclosure. [Figure 8] FIG. 10 is a diagram illustrating an example of airfield information in the present disclosure. [Figure 9] FIG. 10 is a diagram illustrating an example of reservation log information in the present disclosure. [Figure 10] FIG. 10 is a diagram illustrating an example of a notification of occupancy request rejection in the present disclosure. [Figure 11] FIG. 10 illustrates an example of a notification of occupancy request acceptance in the present disclosure. [Figure 12] FIG. 10 is a diagram illustrating an example of a reservation confirmation notification in the present disclosure. [Figure 13] 10 is a flowchart illustrating an example of an operation of the reservation management device according to the present disclosure. [Figure 14] 10 is a flowchart illustrating an example of an operation of the reservation management device according to the present disclosure. [Figure 15] 10 is a flowchart illustrating an example of an operation of the reservation management device according to the present disclosure. [Figure 16] 1 is a block diagram illustrating an example of a configuration of a reservation management device according to the present disclosure. [Figure 17] 10 is a flowchart illustrating an example of an operation of the reservation management device according to the present disclosure. [Figure 18] 1 is a block diagram illustrating an example of a configuration of a reservation management device according to the present disclosure. [Figure 19] FIG. 10 is a diagram illustrating an example of a reservation availability notification in the present disclosure. [Figure 20] 10 is a flowchart illustrating an example of an operation of the reservation management device according to the present disclosure. [Figure 21] 1 is a block diagram illustrating an example of a configuration of a reservation management device according to the present disclosure. [Figure 22] FIG. 10 is a diagram illustrating an example of an occupied time period change screen according to the present disclosure. [Figure 23] FIG. 10 is a diagram illustrating an example of a reservation cancellation request in the present disclosure. [Figure 24] 10 is a flowchart illustrating an example of an operation of the reservation management device according to the present disclosure. [Figure 25] 1 is a block diagram illustrating an example of a configuration of a reservation management device according to the present disclosure. [Figure 26] FIG. 10 is a diagram illustrating an example of the operation of the reservation management device according to the present disclosure. [Figure 27] FIG. 2 is a block diagram showing an example of a hardware configuration for executing control and processing in each embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] Embodiments of the present disclosure will be described in detail below with reference to the drawings. The embodiments described below are limited in a manner that is technically preferable for implementing the present disclosure, but the scope of the invention is not limited to the following. In all drawings used to describe the following embodiments, the same reference numerals are used for similar components unless otherwise specified. In the following embodiments, repeated explanations of similar configurations and operations may be omitted. The UI (User Interface) shown in the drawings is an example and may be replaced with another UI. A personal aircraft in the present disclosure is an aircraft operated by an individual. For example, a personal aircraft may be an autonomous flying object such as a flying car, a small aircraft, or a drone.

[0013] (First embodiment) First, a reservation management system according to a first embodiment will be described with reference to the drawings. The reservation management system according to this embodiment accepts an occupancy request from a user who wishes to reserve a landing field for a personal aircraft, and makes the reservation if certain conditions are met.

[0014] Fig. 1 is a conceptual diagram for explaining a reservation management system according to the present disclosure. As shown in Fig. 1, the reservation management system 1 includes a reservation management device 10 and multiple terminal devices (80-1, 80-2, ... 80-n) (n is a natural number). In the following description, when it is not necessary to distinguish between the multiple reservation management devices, they will be referred to as terminal devices 80.

[0015] The reservation management device 10 is communicably connected to each of a plurality of terminal devices 80. The reservation management device 10 and the terminal devices 80 are realized by information processing devices such as a desktop terminal device, a notebook terminal device, or a portable terminal device.

[0016] The terminal device 80 is a terminal device operated by a user. The terminal device 80 includes an input unit and a display unit, not shown. The terminal device 80 transmits an occupancy request input by the user via the input unit to the reservation management device 10. The occupancy request is a request to occupy an airfield for a personal aircraft. For example, the occupancy request includes a desired occupancy time, which is the desired date and time for occupancy of the airfield, and a desired occupancy amount, which is the amount of money desired for occupancy.

[0017] The reservation management device 10 is a device for making reservations for takeoff and landing pads for personal aircraft. When the reservation management device 10 receives an occupancy request from the terminal device 80, it determines whether or not certain conditions related to the reservation are met. Details of the certain conditions will be described later. If the certain conditions are met, the reservation management device 10 accepts the occupancy request and makes the reservation. If the certain conditions are not met, the reservation management device 10 rejects the occupancy request. The reservation management device 10 notifies the terminal device 80 that the reservation has been made or that the occupancy request has been rejected.

[0018] (composition) 2 is a block diagram showing an example of the configuration of a reservation management device 10 according to the present disclosure. As shown in FIG. 2, the reservation management device 10 according to the present disclosure includes an input receiving unit 11, an identifying unit 12, an acquiring unit 13, a determining unit 14, a request processing unit 15, a reservation unit 16, a notifying unit 17, and a storage unit 18.

[0019] The input accepting unit 11 accepts input from the terminal device 80. For example, the input accepting unit 11 accepts input of user identification information, input of aircraft information of the personal aircraft, and input of an occupancy request. The input accepting unit 11 accepts information entered via an input interface such as a web browser displayed on the display unit of the terminal device 80.

[0020] The user's identification information is information for uniquely identifying a user. For example, the user's identification information includes personal information such as name, user ID (Identification) in the reservation management device 10, email address, telephone number, date of birth, address, etc., and biometric information such as fingerprints and iris patterns. The input accepting unit 11 displays an input interface such as a web browser that requests input of the user's identification information on the display unit of the terminal device 80. A user operating the terminal device 80 inputs the user's identification information via the input interface. The input accepting unit 11 accepts the identification information input to the terminal device 80 and uses it in the user identification process described below.

[0021] The personal aircraft aircraft information is information about the personal aircraft for which a user wishes to reserve an airfield. For example, the aircraft information includes the aircraft model of the personal aircraft, the number of passengers expected to board, and the type of power source. The aircraft information is used to select an airfield that can be used by the user's personal aircraft. Details of the process by which the reservation management device 10 selects an airfield for the user using the aircraft information will be described later.

[0022] FIG. 3 is a diagram showing an example of an aircraft information input screen in the present disclosure. For example, the input accepting unit 11 displays an aircraft information input screen W1 as shown in FIG. 3 on the display unit of the terminal device 80 to request input of aircraft information for a personal aircraft. The aircraft information input screen W1 includes an aircraft model input field E1, an input field for the number of passengers planned to board, and a power source type input field E3. The user inputs the aircraft model, the number of passengers planned to board, and the power source type of their personal aircraft into the aircraft model input field E1, the input field for the number of passengers planned to board, and the power source type input field E3, respectively, via the input unit of the terminal device 80. The input accepting unit 11 accepts the aircraft information input to the terminal device 80 and uses it in the takeoff and landing site selection process described below.

[0023] The occupancy request is information transmitted via the terminal device 80 when a user wishes to reserve a specific airfield for a specific time period. The occupancy request includes the time period for occupancy and the desired occupancy price. In addition to the information described above, the occupancy request may also include identification information of the airfield desired for occupancy.

[0024] The occupancy time slot is the time slot during which the user wishes to reserve the airstrip (i.e., occupy the airstrip). The desired occupancy amount is the amount the user wishes to pay for occupancy of the airstrip. In the present disclosure, the desired occupancy amount is not limited to a monetary amount, but may be expressed, for example, in points. Points are a numerical value that is used as payment for a service purchased in advance by the user. Points are not limited to points purchased by the user, but may also be points awarded to the user by the reservation management system 1, for example. Details of point awarding will be described in the fourth embodiment. Hereinafter, the desired occupancy amount will be described as points, but this is an example for the purpose of explanation, and it is not intended to limit the desired occupancy amount to points.

[0025] FIG. 4 is a diagram illustrating an example of an occupancy request screen in the present disclosure. For example, the input receiving unit 11 displays an occupancy request screen W2 as shown in FIG. 4 on the display unit of the terminal device 80 to request input of an occupancy request. The occupancy request screen W2 includes a field E4 for selecting the desired takeoff and landing field for occupancy, a field E5 for inputting a time period for occupancy, a field E6 for inputting a desired amount to be paid, and a field E7 for confirming the amount to be used. The field E4 is a UI component for selecting an arbitrary takeoff and landing field from the takeoff and landing fields available for the user's personal aircraft selected by the identification unit 12. The user inputs the identification information of the takeoff and landing field to be reserved, the desired time period for occupancy, and the desired amount for occupancy into each of these input fields. The input receiving unit 11 receives this information input to the terminal device 80 and uses it for the occupancy determination process, which will be described later.

[0026] The occupancy request screen W2 may include a user usage amount confirmation field E7. The usage amount confirmation field E7 includes the user's usage amount for a specified period and an upper limit. The usage amount is the total amount paid by the user for occupancy of the airstrip during a specified period in the past. The specified period is a period determined in advance by an administrator of the reservation management system 1, for example, a fixed period such as the past week or the past day. The upper limit is the maximum amount that the user can pay for occupancy of the airstrip during the specified period. The upper limit may be set for each user, or a value common to all users may be set.

[0027] The reservation status confirmation screen visually displays the status of occupancy requests from multiple users. By including the reservation status confirmation screen in the occupancy request screen W2, users can understand the time slots that do not overlap with other users' reservations and the time slots that cannot be reserved.

[0028] FIG. 5 is a diagram showing an example of a reservation status confirmation screen W3 in this embodiment. For example, the reservation status confirmation screen W3 is configured in a Gantt chart format. On the reservation status confirmation screen W3, the vertical axis represents the identification information of the airstrip, and the horizontal axis represents the occupancy date and time. The schedule bars B1 and B2 arranged on the reservation status confirmation screen W3 represent the time periods for which occupancy requests have been made by each user. On the reservation status confirmation screen W3, when the mouse is placed over the schedule bar B1 or B2, detailed reservation status information M1 pops up. The reservation status confirmation screen W3 may highlight airstrips available for use by the user's personal aircraft. Area E9 in FIG. 5 displays airstrips available for use by the user's personal aircraft. In area E9, airstrips available for use by the user's personal aircraft are sorted to the top and highlighted by being filled in.

[0029] In the example of FIG. 5, the display methods of schedule bar B1 and schedule bar B2 are different. In the example of FIG. 5, the display method of the schedule bar changes depending on whether the reservation is confirmed or not. In the following explanation, information indicating whether the reservation is confirmed or not is also referred to as the reservation status. For example, a time slot for which a reservation is not confirmed is represented by a bar filled in white, as in schedule bar B1, and a time slot for which a reservation is confirmed is represented by a bar filled in with a hatched pattern, as in schedule bar B2. In the example of FIG. 5, the display color is changed to change the display method, but this is just one example. For example, the bar height (vertical width) of schedule bars B1 and B2 may be different, or the reservation status may be displayed as a pop-up when the mouse is hovered over the schedule bar.

[0030] On the reservation status confirmation screen W3, if there are conflicting occupancy requests, the display method of the schedule bar for the conflicting time slot may be changed. In the example of FIG. 5, an example display when there are conflicting occupancy requests is shown in area E8. As shown in area E8, if there are conflicting occupancy requests, the conflict may be expressed by a schedule bar B3 in which the display color of the schedule bar for the conflicting time slot is changed. In addition, the desired occupancy price for the occupancy request may be displayed near the schedule bar B3. In the example of area E8, all of the conflicting occupancy requests are expressed by schedule bars, but it is also possible to display only the schedule bar of the current occupancy candidate. An occupancy candidate is a user who meets the specified conditions for reservation in that time slot and has proposed the highest desired occupancy price. Details of occupancy candidates will be described later.

[0031] An occupancy request input via the occupancy request screen is stored in the storage unit 18 as occupancy request log information. FIG. 6 is a diagram illustrating an example of occupancy request log information in the present disclosure. In the example illustrated in FIG. 6, the occupancy request log information includes a reception time, a desired occupancy time, user identification information, takeoff and landing field identification information, a desired occupancy price, whether the occupancy request is accepted, a reservation status, and an acceptance end time. The reception time is the time when the occupancy request is accepted from the terminal device 80. When the occupancy request is accepted from the terminal device 80, the acceptance end time field is NULL. The value of the acceptance end time field is added after processing by the request processing unit 15. The value of the reservation status field is updated each time processing by the reservation unit 16 is performed. The acceptance end time is the time when acceptance of occupancy requests from users is ended. The acceptance end time is predetermined and stored in the storage unit 18. The acceptance end time may be determined for each occupancy time period, or a common acceptance end time may be determined for all occupancy time periods.

[0032] The identification unit 12 uniquely identifies a user using the user information input via the input receiving unit 11. Since the user can be identified using known technology, a description thereof will be omitted.

[0033] The identification unit 12 also uses the aircraft information input via the input reception unit 11, the aircraft model list information, and the airfield information stored in the memory unit 18 to select an airfield available for the user's personal aircraft. As described above, the aircraft information of the personal aircraft is information about the personal aircraft for which the user wishes to reserve an airfield. For example, the aircraft information includes the aircraft model of the personal aircraft, the number of passengers planned to board, and the power source type. The selection result of the identification unit 12 is acquired by the input reception unit 11 and reflected on the occupancy request screen W2 and the reservation status confirmation screen W3. The airfield selection field E4 on the occupancy request screen W2 may be configured to allow only the airfields selected by the identification unit 12 to be selected. Furthermore, the reservation status confirmation screen W3 may be configured to allow only the reservation status of the airfield selected by the identification unit 12 to be confirmed. Alternatively, the display method of the airfield selected by the identification unit 12 may be changed on the reservation status confirmation screen W3. In the example of FIG. 5, as shown in area E9, the reservation statuses of "airport B" and "airport C," which are airports selected by the identification unit 12, are highlighted.

[0034] The identification unit 12 searches the aircraft model list information stored in the memory unit 18 using the aircraft model of the personal information, and identifies information necessary for selecting an available takeoff and landing site. FIG. 7 is a diagram showing an example of the aircraft model list information in the present disclosure. In the example of FIG. 7, the aircraft model list information has a table structure. For example, the aircraft model list information is composed of items such as aircraft model, aircraft length, wingspan, height, runway length requirement, and maximum takeoff weight. The aircraft model list information may further include items such as engine model and total output (horsepower). The runway length requirement is the minimum runway length required for a personal aircraft to safely take off and land. The maximum takeoff weight is the maximum weight of a personal aircraft permitted when the personal aircraft takes off. The maximum weight is the total weight of the personal aircraft, which is the empty weight plus the operating weight. The identification unit 12 searches the aircraft model list information using the aircraft model included in the aircraft information input via the input reception unit 11, and identifies an entry corresponding to the aircraft model. The identifying unit 12 acquires information included in the identified entry.

[0035] The identification unit 12 searches for airfield information using the input aircraft information and the information identified by the identification unit 12, thereby selecting an airfield that can be used by the user's personal aircraft. The airfield information is a dataset including information about the airfield of the personal aircraft. The information about the airfield specifically includes the size and facilities of the airfield. FIG. 8 is a diagram showing an example of airfield information in the present disclosure. In the example of FIG. 8, the airfield information has a table structure. For example, the airfield information includes items such as airfield identification information, area, aircraft size, whether or not a charger is installed, and runway length. The airfield information may further include items such as a maximum takeoff weight allowance. The maximum takeoff weight allowance is the maximum weight of a personal aircraft that can be safely accommodated at the airfield. The identification unit 12 refers to FIG. 8 and selects an airfield that can be used by the user's personal aircraft from multiple airfields. Specifically, the identification unit 12 determines that a personal aircraft can be used if its size (aircraft length, wingspan) fits within the area of ​​the airfield, the required runway length is equal to or less than the runway length of the airfield, and the maximum takeoff weight is equal to or less than the allowable value of the airfield. Furthermore, if the power source type of the user's personal aircraft is "rechargeable," the identification unit 12 selects an airfield with a charger installed. If the power source type is "fuel-powered," the identification unit 12 considers any airfield to be a selection target, regardless of whether a charger is installed.

[0036] The acquisition unit 13 acquires the usage amount of the user identified by the identification unit 12. As described above, the usage amount is the total amount paid by the user for occupancy of the airfield during a predetermined period in the past. The acquisition unit 13 calculates the usage amount during the predetermined period using the reservation log information stored in the memory unit 18.

[0037] FIG. 9 is a diagram illustrating an example of reservation log information in the present disclosure. For example, reservation log information is created for each user. The reservation log information includes items such as the reservation date and time, identification information of the reserved takeoff and landing pad, and the payment amount paid for the takeoff and landing pad reservation. Referring to FIG. 9, the procedure by which the acquisition unit 13 acquires the user's usage amount will be described. First, the acquisition unit 13 references the storage unit 18 and reads out the reservation log information of the user identified by the identification unit 12. Next, the acquisition unit 13 extracts records of reservation dates and times within a predetermined period from the reservation log information. Next, the acquisition unit 13 calculates the user's usage amount for the predetermined period by adding up the payment amounts of the extracted records.

[0038] The acquisition unit 13 may further acquire the number of occupancy requests made by the user for the occupancy time period. The acquisition unit 13 acquires the number of occupancy requests made by the user for the same occupancy time period at the same airfield, using the occupancy request log information stored in the storage unit 18.

[0039] The determination unit 14 determines whether the sum of the usage amount acquired by the acquisition unit 13 and the desired occupancy amount accepted by the input acceptance unit 11 exceeds a predetermined upper limit. The determination unit 14 determines whether the sum exceeds the predetermined upper limit by comparing the sum with the upper limit stored in the memory unit 18. As described above, the upper limit is the maximum amount that a user can pay for occupancy of an airfield in a specified period of time. The upper limit may be determined for each user, or a common amount may be determined for all users.

[0040] The determination unit 14 may further determine whether the number of occupancy requests made by the user exceeds a predetermined upper limit. The determination unit 14 determines whether the number of occupancy requests made by the user exceeds the predetermined upper limit by comparing the number of occupancy requests acquired by the acquisition unit 13 with the upper limit stored in the storage unit 18. The upper limit is the maximum allowable number of occupancy requests that a user can make for the same occupancy time period.

[0041] The request processing unit 15 uses the judgment result of the judgment unit 14 to decide whether to accept the exclusive use request. If the judgment unit 14 determines that the upper limit amount is not exceeded and that the desired exclusive use amount is higher than the other exclusive use candidates, the request processing unit 15 accepts the exclusive use request and determines the user as the new exclusive use candidate. In this case, the exclusive use request of the user who was set as the exclusive use candidate immediately before the new user is rejected. Note that if there are no exclusive use candidates for the exclusive use time period, the request processing unit 15 does not determine whether the desired exclusive use amount is higher than the other exclusive use candidates. If the judgment unit 14 determines that the upper limit amount is exceeded or the desired exclusive use amount is lower than the other exclusive use candidates, the request processing unit 15 rejects the exclusive use request. When the request processing unit 15 decides to accept or reject the exclusive use request, it adds a value to the “Accept / Deny” field in the entry corresponding to the exclusive use request in the exclusive use request log information.

[0042] An occupancy candidate is a user who, among multiple users wishing to reserve an airfield, has the possibility of having his / her occupancy request accepted. More specifically, an occupancy candidate is a user who has made an occupancy request and whose occupancy request has been accepted and whose reservation status is undetermined. In the example shown in FIG. 6, user "BBBB" is a candidate for occupancy at "Airfield A" for the desired occupancy time "November 24, 2024, 10:00-11:30."

[0043] In addition to the above conditions, if the judgment unit 14 judges that the upper limit number of times has not been exceeded, the request processing unit 15 may set the user corresponding to the judged occupancy request as a new occupancy candidate.

[0044] When a predetermined acceptance end time arrives, the reservation unit 16 determines the occupancy candidate set by the request processing unit 15 as the occupant and makes a reservation. Specifically, when the acceptance end time arrives, the reservation unit 16 changes the reservation status of the occupancy candidate in the occupancy request log information from "undecided" to "confirmed." The processing of the reservation unit 16 will be further explained using the example of occupancy request log information shown in FIG. 6. An occupant is a user who has made an occupancy request, and whose occupancy request has been accepted and whose reservation status is confirmed. In the example shown in FIG. 6, user "AAAA" is a candidate for occupancy at "Airport C" for the desired occupancy time "November 24, 2024, 9:00-10:00." For example, when the reservation acceptance deadline reaches "November 3, 2024, 12:00," the reservation unit 16 changes the reservation status of user "BBBB," who is a candidate for occupancy at "Airport A" for the desired occupancy time "November 24, 2024, 10:00-11:30," from "Undecided" to "Confirmed." Furthermore, when the reservation status is changed from "Undecided" to "Confirmed," the reservation unit 16 adds an entry corresponding to the confirmed occupancy request to the reservation log information. For example, when the reservation for the above-mentioned user "BBBB" is confirmed, the reservation unit 16 adds an entry to the reservation log information corresponding to user "BBBB," in which the reservation date and time is "November 24, 2024, 10:00-11:30," the airport identification information is "Airport A," and the payment amount is "15 points." The reservation date and time is the desired occupancy time for which the reservation status is "Confirmed." The payment amount is the desired occupancy amount for which the reservation status is "Confirmed."

[0045] The notification unit 17 transmits a notification of the rejection of the exclusive use request to the user who rejected the exclusive use request. FIG. 10 is a diagram illustrating an example of a notification of the rejection of an exclusive use request according to the present disclosure. The exclusive use request rejection notification W4 includes information indicating that the exclusive use request has been rejected and the reason for the rejection of the exclusive use request. In the example shown in FIG. 10, "there is an exclusive use candidate who offers a higher desired exclusive use amount in the desired time period" is selected as the reason for rejection. The exclusive use request rejection notification W4 may also include a UI widget E10 for requesting an exclusive use request again. When the user selects the UI widget E10, the screen transitions to the exclusive use request screen W2, which allows the user to make an exclusive use request again.

[0046] The notification unit 17 also transmits a notification of exclusive use request acceptance to the user who accepted the exclusive use request. Fig. 11 is a diagram showing an example of an exclusive use request acceptance notification in the present disclosure. The exclusive use request acceptance notification W5 includes information indicating that the exclusive use request has been accepted and detailed information about the accepted exclusive use request. The exclusive use request acceptance notification W5 may also include a UI widget E11 for canceling the accepted exclusive use request.

[0047] Furthermore, the notification unit 17 transmits a reservation completion notification to the user whose reservation has been confirmed. FIG. 12 is a diagram illustrating an example of a reservation confirmation notification in the present disclosure. The reservation confirmation notification W6 includes information indicating that the reservation has been confirmed and detailed information about the reservation contents. In the example shown in FIG. 12, the detailed information about the reservation contents includes the occupancy time period, identification information of the takeoff and landing field, and the desired occupancy price. The reservation confirmation notification W6 may also include a UI widget E12 for canceling the reservation and a UI widget E13 for requesting a change in the reservation time. Details of the processing when a request to cancel a reservation or change the reservation time is received will be described later in the third and fourth embodiments.

[0048] The storage unit 18 stores information required for processing by the reservation management device 10. The storage unit 18 stores aircraft model list information, airfield information, occupancy request log information, reservation log information, upper limit fare, and acceptance end time. The storage unit 18 may store information other than the above-mentioned information, such as information temporarily required for processing by the reservation management device 10.

[0049] (operation) Next, the operation of the reservation management device 10 in this embodiment will be described with reference to Figures 13, 14, and 15. Figures 13, 14, and 15 are flowcharts for explaining an example of the operation of the reservation management device in the present disclosure.

[0050] [Occupancy request processing] First, the process of determining whether or not to accept a user's occupancy request will be described with reference to FIGS.

[0051] First, the input accepting unit 11 accepts input of user information (step S101). The input accepting unit 11 requests the input of user information by displaying an input interface such as a web browser that requests the input of user identification information on the display unit of the terminal device 80. The identifying unit 12 uniquely identifies the user using the input user information.

[0052] Next, the input accepting unit 11 accepts input of aircraft information of the personal aircraft (step S102). The input accepting unit 11 requests the input of aircraft information by displaying an input interface such as a web browser that requests the input of aircraft information on the display unit of the terminal device 80. The order of the processing of step S101 and step S102 may be reversed.

[0053] Next, the identification unit 12 performs an airfield selection process, which is a process of selecting an airfield that can be reserved by the user's personal aircraft (step S103). The airfield selection process will be described with reference to FIG.

[0054] First, the identification unit 12 acquires the machine information accepted by the input acceptance unit 11 (step S1031).

[0055] Next, the identification unit 12 refers to the aircraft model list information stored in the storage unit 18, and acquires the aircraft size, required runway length, and maximum takeoff weight corresponding to the aircraft model included in the aircraft information (step S1032).

[0056] Next, the identification unit 12 scans all records of the airfield information stored in the memory unit 18 (step S1033). Specifically, the identification unit 12 sequentially checks entries that satisfy the following conditions. The first condition is that the aircraft size (aircraft length, wingspan) is equal to or less than the area of ​​the airfield. The second condition is that the required runway length is equal to or less than the runway length of the airfield. The third condition is that the maximum takeoff weight is equal to or less than the maximum takeoff weight allowable value for the airfield. The fourth condition is that the presence or absence of a charger installed is "present." The fourth condition is imposed only when the charging type is "rechargeable." Note that the first to fourth conditions are merely examples, and other conditions may be added, or any of the conditions may be deleted.

[0057] If there is an entry that satisfies all of the first to fourth conditions (Yes in step S1034), the identification unit 12 selects the airfield corresponding to that entry as an "available airfield." If there are multiple entries that satisfy all of the first to fourth conditions, the identification unit 12 may select all airfields that satisfy the conditions as "available airfields," or may select any one of the airfields. If there is no entry that satisfies all of the first to fourth conditions (No in step S1034), the identification unit 12 returns to the processing of step S101 in FIG. 13. After completing the processing of step S1035, the identification unit 12 ends the airfield selection processing shown in FIG. 14.

[0058] Returning to the explanation of the processing in the flowchart of Fig. 13, after completing the processing of step S103 in Fig. 13, the input receiving unit 11 receives input of an occupancy request from the user (step S104). The input receiving unit 11 requests input of an occupancy request by displaying an input interface such as a web browser on the display unit of the terminal device 80, which requests input of an occupancy request. The occupancy request includes an occupancy time period, a desired occupancy amount, and identification information of the takeoff and landing field desired to be occupied. When requesting input of identification information of the takeoff and landing field, the input receiving unit 11 may be configured to select only the takeoff and landing fields selected in step S103.

[0059] Next, the acquisition unit 13 acquires the usage amount of the user identified in step S101 (step S105). The acquisition unit 13 uses the reservation log information stored in the storage unit 18 to calculate the usage amount of the user for a predetermined period.

[0060] Next, the determination unit 14 determines whether or not the total value of the usage amount acquired in step S105 and the desired occupancy amount acquired in step S104 exceeds a predetermined upper limit (step S106).

[0061] If it is determined that the upper limit is exceeded (Yes in step S106), the request processing unit 15 determines whether the user's desired occupancy amount exceeds the desired occupancy amount of another occupancy candidate (step S107). If there is no occupancy candidate for the desired occupancy time, the process of step S107 is not performed, and the process proceeds to step S108.

[0062] If the determination unit 14 determines that the upper limit amount is not exceeded and that the desired occupancy amount is higher than the other occupancy candidates (Yes in step S107), the request processing unit 15 rejects the occupancy request of the occupancy candidate. Furthermore, the notification unit 17 notifies the occupancy candidate that the occupancy request has been rejected (step S108). Then, the request processing unit 15 accepts the user's occupancy request and determines the user as a new occupancy candidate. Furthermore, the notification unit notifies the user that the user's occupancy request has been accepted (step S109).

[0063] If the determination unit 14 determines that the upper limit is exceeded (No in step S106), or if the desired occupancy amount is lower than that of other occupancy candidates (No in step S107), the request processing unit 15 rejects the occupancy request. In addition, the notification unit notifies the user that the occupancy request has been rejected (step S110).

[0064] When the reservation management device 10 completes the process of step S109 or the process of step S110, it ends the series of occupancy request processes described above.

[0065] [Reservation Processing] Next, the process by which the reservation management device 10 makes a reservation will be described with reference to FIG.

[0066] First, the reservation unit 16 checks whether a predetermined acceptance end time has arrived (step S111). The reservation unit 16 repeats the process of step S111 until the acceptance end time arrives (No in step S111).

[0067] When the end time for accepting reservations arrives, the reservation unit 16 determines the occupancy candidate set by the request processing unit 15 as the occupant and makes a reservation (step S112).

[0068] Next, the notification unit 17 notifies the user that the reservation has been confirmed (step S113). After completing the process of step S113, the reservation management device 10 ends the series of processes described above.

[0069] As described above, the reservation management device of this embodiment includes an input receiving unit, an acquisition unit, a determination unit, a request processing unit, and a reservation unit. The input receiving unit receives an occupancy request from a user, including the occupancy time slot of the takeoff and landing field and the desired occupancy amount. The acquisition unit acquires the amount of usage by the user within a specified period. The determination unit determines whether the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit. If it is determined that the upper limit is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time slot, the request processing unit sets the user as a new occupancy candidate. The reservation unit determines the user set as an occupancy candidate as the occupant of the occupancy time slot at the predetermined acceptance closing time and makes a reservation.

[0070] With the above configuration, the reservation management device of this embodiment can prevent a specific user from monopolizing a landing field reservation for a personal aircraft. This is because a reservation can be made only if the sum of the usage fee and the desired occupancy fee does not exceed the upper limit. In a system in which a user can directly specify a specific time period and a specific landing field for a reservation, multiple users may wish to reserve the same landing field for the same time period. In such a situation, if the occupant is determined without considering factors other than the payment amount, as in an auction, a financially advantageous user may monopolize the landing field reservation. The reservation management device of this embodiment sets an upper limit for the amount that can be used in a specified period, and a reservation cannot be made if the upper limit is exceeded. In other words, it is possible to prevent a user who pays the highest desired occupancy fee from monopolizing the landing field reservation. This ensures fairness among users. Furthermore, the reservation management device of this embodiment does not simply determine the occupant on a first-come, first-served basis, but rather determines the occupant to the user who submits the highest desired occupancy fee by the closing time of reservations. This maximizes the revenue of the landing field while preventing a specific user from monopolizing the landing field reservation.

[0071] In one aspect of this embodiment, a reservation management device sets an upper limit on the number of occupancy requests a user can make for an exclusive time slot at an airfield. Furthermore, in one aspect of this embodiment, an acquisition unit acquires the number of occupancy requests made by the user for the exclusive time slot. The determination unit further determines whether the number of occupancy requests exceeds the upper limit. If the request processing unit determines that the number of occupancy requests does not exceed the upper limit, it sets the user as a new occupancy candidate. This makes it possible to limit the number of occupancy requests for the same exclusive time slot, which is expected to have the effect of preventing abuse of occupancy requests.

[0072] A reservation management device according to one aspect of this embodiment further includes a specification unit that selects, from a plurality of airfields, an airfield that can be used by the user's personal aircraft. In the reservation management device according to one aspect of this embodiment, the input acceptance unit further accepts input of aircraft information, including the aircraft model of the personal aircraft. The specification unit compares the airfield information, including information on the area of ​​each of the plurality of airfields, with information on the size of the personal aircraft specified from the aircraft model, and selects an airfield that can accommodate the personal aircraft within the area of ​​the airfield as an available airfield. The input acceptance unit accepts a request to occupy the selected airfield. The reservation management device according to the location aspect of this embodiment, with the above configuration, can automatically select an airfield that can be used by the user's personal aircraft, thereby improving convenience for users when making reservations. Furthermore, the above configuration eliminates the risk that a user will mistakenly select an airfield that cannot be used by personal aircraft, thereby improving the safety of airfield operations.

[0073] In a reservation management device according to one aspect of the present disclosure, the aircraft information further includes the power source type of the personal aircraft. In a reservation management device according to a location aspect of the present disclosure, if the power source type of the personal aircraft is rechargeable, the identification unit selects an airfield with charging facilities as an available airfield. With the above configuration, the reservation management device according to one aspect of the present embodiment eliminates the need for users who own rechargeable personal aircraft to manually select an airfield with charging facilities, thereby improving user convenience when making reservations. Furthermore, with the above configuration, there is no risk that a user will mistakenly reserve an airfield that does not allow charging for the personal aircraft, thereby preventing problems such as emergency landings due to dead batteries.

[0074] (Second embodiment) Next, the reservation management system of this embodiment will be described with reference to the drawings. In the following description, parts similar to those of the first embodiment will be given the same reference numerals, and descriptions will be omitted as appropriate. The reservation management device of this embodiment differs from the reservation management device of the first embodiment in that, when the immediate purchase condition is met, an immediate reservation is made without comparing the desired occupancy price.

[0075] (composition) 16 is a block diagram showing an example of the configuration of a reservation management device according to the present disclosure. As shown in FIG. 16, the reservation management device 20 includes an input receiving unit 11, an identifying unit 12, an acquiring unit 23, a determining unit 14, a request processing unit 25, a reservation unit 26, a notifying unit 17, and a storage unit 28.

[0076] The acquisition unit 23 acquires the number of reservations made by the user in a predetermined period from the storage unit 28, using the user information identified by the identification unit 12. The number of reservations made by the user is calculated using reservation log information stored in the storage unit 28.

[0077] If the determination unit 14 determines that the upper limit amount is not exceeded and the immediate decision condition is satisfied, the request processing unit 25 determines the user who made the occupancy request as the occupant. While the request processing unit 15 of the first embodiment performed the process of setting occupancy candidates, the request processing unit 25 does not perform the process of setting occupancy candidates, but instead determines the occupant.

[0078] For example, the immediate decision condition is that the number of reservations made by a user within a specified period is less than the number of guaranteed reservations. The number of guaranteed reservations is the upper limit of the number of times a user can make a priority reservation for an airfield within a specified period. If the number of reservations made within a specified period is less than the number of guaranteed reservations, the user's occupancy request will be immediately reserved. The number of guaranteed reservations is determined for each user and stored in the memory unit 28.

[0079] Alternatively, the immediate purchase condition is that the desired occupancy price is equal to a predetermined immediate purchase price. The immediate purchase price is determined for each occupancy time period and stored in the storage unit 28.

[0080] When the request processing unit determines an occupant, the reservation unit 26 makes a reservation regardless of the end time of acceptance. In other words, when the user's occupancy request satisfies the judgment condition of the judgment unit and the immediate decision condition, the reservation is made immediately.

[0081] In addition to the information described in the first embodiment, the storage unit 28 further stores the number of guaranteed reservations for each user and the buyout price for each occupied time slot.

[0082] (operation) Next, the operation of the reservation management device 20 in this embodiment will be described with reference to Fig. 17. Fig. 17 is a flowchart showing an example of the operation of the reservation management device in the present disclosure.

[0083] First, the input receiving unit 11 receives input of user information (step S201). Next, the input receiving unit 11 receives input of aircraft information of the personal aircraft (step S202). Next, the identification unit 12 performs an airfield selection process, which is a process of selecting an airfield that can be reserved by the user's personal aircraft (step S203). Next, the input receiving unit 11 receives input of an occupancy request from the user (step S204). The processes of steps S201 to S204 are the same as the processes of steps S101 to S104 in the first embodiment, and therefore detailed description thereof will be omitted.

[0084] Next, the acquisition unit 23 acquires the amount of use of the user identified in step S201 and the number of reservations made by the user during the predetermined period (step S105). The acquisition unit 23 calculates the amount of use of the user and the number of reservations made during the predetermined period using the reservation log information stored in the storage unit 28.

[0085] Next, the determination unit 14 determines whether the total of the usage amount acquired in step S205 and the desired occupancy amount acquired in step S204 exceeds a predetermined upper limit (step S206).

[0086] If it is determined that the upper limit is exceeded (Yes in step S206), the request processor 25 determines whether the user's occupancy request satisfies the immediate decision condition (step S207). The immediate decision condition is that the number of reservations made by the user in a predetermined period is less than the guaranteed number of reservations, or the desired occupancy amount is equal to a predetermined immediate decision amount.

[0087] When the request processing unit 25 determines that the immediate decision condition is met (Yes in step S207), it determines the user who made the occupancy request as the occupant (step S208). Then, the reservation unit 26 makes a reservation, and the notification unit 17 notifies the user that the reservation has been confirmed (step S209). When the reservation management device finishes the process of step S209, it ends the series of processes described above.

[0088] On the other hand, if it is determined that the total of the usage amount and the desired occupancy amount exceeds the predetermined upper limit (No in step S206), or if it is determined that the immediate decision condition is not met (No in step S207), the process proceeds to step S107 shown in Figure 13.

[0089] The reservation management device of this embodiment is configured as described above. In addition to the effects obtained from the reservation management device of the first embodiment, the reservation management device of this embodiment provides the following effects.

[0090] In a reservation management device according to one aspect of this embodiment, the number of guaranteed reservations within a predetermined period is determined for each user. The acquisition unit acquires the number of guaranteed reservations for the user who has made an occupancy request. If the request processing unit determines that the upper limit amount has not been exceeded and the number of reservations made by the user within the predetermined period is less than the guaranteed number of reservations, it determines the user as the occupant instead of setting an occupancy candidate. If the request processing unit determines the occupant, the reservation unit makes a reservation regardless of the end time of reservations. According to the reservation management device according to one aspect of this embodiment, reservations can be made immediately up to the guaranteed number of reservations within a predetermined period, thereby preventing a specific user from monopolizing reservations for the airfield. This also ensures fairness among users.

[0091] In a reservation management device according to one aspect of this embodiment, a buy now amount is set for each exclusive time slot. If the request processing unit determines that the upper limit amount is not exceeded and the desired occupancy amount is equal to the buy now amount, the request processing unit determines the user as the occupant instead of setting an exclusive candidate. If the request processing unit determines the occupant, the reservation unit makes the reservation regardless of the reservation end time. According to the reservation management device according to one aspect of this embodiment, reservations in which the desired occupancy amount is equal to the buy now amount can be made immediately. For example, if there is an exclusive time slot that a user definitely wants to reserve, the reservation could not be made reliably with the reservation management device of the first embodiment. According to the reservation management device according to one aspect of this embodiment, a reservation can be made reliably by submitting an buy now amount, thereby improving user convenience.

[0092] (Third embodiment) Next, the reservation management system of this embodiment will be described with reference to the drawings. In the following description, the same parts as those of the first and second embodiments will be given the same reference numerals, and the description will be omitted as appropriate. In this embodiment, the process when a cancellation request is received from the user who is the occupant after a reservation has been confirmed by the process described in the first or second embodiment will be described.

[0093] (composition) 18 is a block diagram showing an example of the configuration of a reservation management device according to the present disclosure. As shown in FIG. 18, the reservation management device 30 includes an input receiving unit 31, an identifying unit 32, an acquiring unit 13, a determining unit 14, a request processing unit 15, a reservation unit 36, a notifying unit 37, and a storage unit 18.

[0094] The input receiving unit 31 further receives a request to cancel a reservation. For example, the input receiving unit 31 receives a request to cancel a reservation when the user presses the UI widget E12 in the reservation confirmation notification W6 shown in FIG.

[0095] The identification unit 32 uses the reservation log information stored in the memory unit 18 to identify users who have personal aircraft that can use the airstrip for which a cancellation request has been made. For example, the identification unit 32 refers to the reservation log information for each user shown in Fig. 9 to identify users who have a reservation history for the airstrip for which a cancellation request has been made. Alternatively, the identification unit 32 may refer to the airstrip information shown in Fig. 8 to identify airstrips that have an area and runway length equal to or greater than that of the airstrip for which a cancellation request has been made and that have the same availability of charging facilities, and identify users who have a reservation history for the identified airstrip.

[0096] The notification unit 37 notifies the user identified by the identification unit 32 that the canceled occupied time slot is now available for reservation. FIG. 19 is a diagram showing an example of a reservation availability notification in the present disclosure. For example, the notification unit 37 notifies the user that the canceled occupied time slot is now available for reservation by displaying a reservation availability notification W7 shown in FIG. 19 on the display unit of the terminal device 80. The reservation availability notification W7 may include a UI component E13 for requesting a reservation for the notified occupied time slot.

[0097] The input receiving unit 31 further receives a reservation request from the user who has received the notification. For example, the input receiving unit 31 receives a reservation request when the UI widget E14 is pressed in the reservation available notification W7 shown in FIG.

[0098] The reservation unit 36 ​​confirms the user's reservation when the input reception unit 31 receives a reservation request. The reservation unit 36 ​​refers to the reservation log information in the storage unit 18, and deletes the entry corresponding to the canceled reservation. The reservation unit 36 ​​also adds an entry corresponding to the newly confirmed reservation.

[0099] (operation) Next, the operation of the reservation management device 30 in this embodiment will be described with reference to Fig. 20. Fig. 20 is a flowchart showing an example of the operation of the reservation management device in the present disclosure. The processing shown in Fig. 20 is processing after a reservation is confirmed. In other words, the processing shown in Fig. 20 is processing after the processing of steps S101 to S113 in the first embodiment or the processing of steps S201 to S209 in the second embodiment has ended.

[0100] First, the input receiving unit 31 receives a reservation cancellation request from an occupant (step S31).

[0101] Next, the identification unit 32 identifies users who have personal aircraft that can use the airstrip for which the cancellation request has been made (step S32). For example, the identification unit 32 refers to the reservation log information for each user shown in Fig. 9 to identify users who have a reservation history for the airstrip for which the cancellation request has been made.

[0102] Next, the notification unit 37 notifies the user identified by the identification unit 32 that the canceled occupied time slot is now available for reservation (step S33).

[0103] Next, the input receiving unit 31 receives an input of a reservation request for the canceled occupied time slot from the user who received the notification in step S33 (step S34).

[0104] Next, when the reservation unit 36 ​​receives the reservation request in step S34, it confirms the user's reservation (step S35).

[0105] Next, the notification unit 37 notifies the user that the reservation has been confirmed (step S36).

[0106] The reservation management device of this embodiment is configured as described above. In addition to the effects obtained from the reservation management devices of the first and second embodiments, the reservation management device of this embodiment provides the following effects.

[0107] In a reservation management device according to one aspect of this embodiment, the input acceptance unit further accepts a request to cancel a reservation. The identification unit uses the reservation log information to identify a user who owns a personal aircraft that can use the airfield for which a cancellation request has been made. When the input of the cancellation request is accepted, the notification unit notifies the identified user that a reservation for the exclusive time slot is available. The input acceptance unit further accepts a reservation request from the notified user. When a reservation request is accepted, the reservation unit confirms the user's reservation. With the above configuration, the reservation management device according to one aspect of this embodiment can improve the utilization rate of the airfield and make effective use of the airfield by opening the reservation to other users in the event of a sudden cancellation just before the desired exclusive time.

[0108] (Fourth embodiment) Next, the reservation management system of this embodiment will be described with reference to the drawings. In the following description, the same parts as those of the first, second, and third embodiments will be assigned the same reference numerals, and the description will be omitted as appropriate. In this embodiment, the process will be described when a request to change the occupied time slot is received from the occupant user after the reservation has been confirmed by the process described in the first or second embodiment.

[0109] (composition) 21 is a block diagram showing an example of the configuration of a reservation management device according to the present disclosure. As shown in FIG. 21, the reservation management device 40 includes an input receiving unit 41, a request unit 42, a reward granting unit 43, an identifying unit 12, an acquiring unit 13, a determining unit 14, a request processing unit 15, a reservation unit 46, a notifying unit 17, and a storage unit 18.

[0110] The input receiving unit 41 further receives a request from the occupant to change the occupied time slot. For example, when the user presses UI widget E13 in the reservation confirmation notification W6 shown in FIG. 12, the input receiving unit 41 displays an input interface such as that shown in FIG. 22 on the display unit of the terminal device 80. FIG. 22 is a diagram showing an example of an occupied time slot change screen according to the present disclosure. The occupied time slot change screen W8 includes information indicating the current reservation details and information about the time slot to which the user wishes to change. The user inputs the occupied time slot to which the user wishes to change via UI widget E15. When the user presses UI widget E16, the input receiving unit 41 receives a request to change the occupied time slot.

[0111] The request unit 42 requests the other user to cancel the reservation if the desired change time period conflicts with the reserved time period of another user's reservation. FIG. 23 is a diagram illustrating an example of a reservation cancellation request in the present disclosure. The reservation cancellation request W9 includes information indicating that the reserved time period requested by the other user to change conflicts with the reserved time period of the user receiving the request, information requesting cancellation, information about the reservation that is the subject of the cancellation request, and information about the reward to be obtained if the reservation is canceled. In the example illustrated in FIG. 23, the reward is shown as being selectable by the user, but it may also be a uniquely determined reward. In the example illustrated in FIG. 23, an example of the reward is a refund of an amount greater than the initial payment amount (refund of 1.5 times the reserved amount). Another example of the reward is a full refund of the initial payment amount plus the granting of an additional guaranteed reservation number (full refund of the reserved amount and one additional guaranteed reservation number). The reward illustrated in FIG. 23 is an example, and the reward content may be freely set by the administrator of the reservation management device 40. If the refund is more than the initial payment, the increased amount shall be borne by the user who made the cancellation request. When the user presses UI widget E17, the input receiving unit 41 receives that the request has been accepted.

[0112] The reward granting unit 43 provides preferential treatment to users who accept the request. Specifically, the reward granting unit 43 grants the reward selected by the user via the reservation cancellation request W9. For example, if a reward of 1.5 times the occupancy amount is selected, the reward granting unit 43 bills the user who requested a change to the occupancy time slot for the increased amount (i.e., 0.5 times the occupancy amount). When the user who requested the change pays the increased amount, the reward granting unit 43 refunds 1.5 times the occupancy amount to the user who accepted the cancellation request. Alternatively, if a full refund of the initial payment amount and an additional number of guaranteed reservations are selected as the reward, the reward granting unit 43 refunds the full amount and increases the user's number of guaranteed reservations stored in the storage unit 18 by a specified value.

[0113] If the user who made the cancellation request accepts the request, the reservation unit 46 changes the reservation. Specifically, the reservation unit 46 refers to the reservation log information stored in the storage unit 18 and changes the reservation date and time of the entry corresponding to the change request to the desired occupied time period.

[0114] (operation) Next, the operation of the reservation management device 40 in this embodiment will be described with reference to Fig. 24. Fig. 24 is a flowchart showing an example of the operation of the reservation management device in the present disclosure. The processing shown in Fig. 24 is processing after a reservation is confirmed. In other words, the processing shown in Fig. 24 is processing after the processing of steps S101 to S113 in the first embodiment or the processing of steps S201 to S209 in the second embodiment has ended.

[0115] First, the input receiving unit 41 receives a request to change the occupied time period from the occupant (step S41). The change request includes the desired change time period.

[0116] Next, the request unit 42 determines whether the desired time slot to be changed conflicts with an occupied time slot for a reservation made by another user (step S42). The request unit 42 scans all records of the reservation log information stored in the storage unit 18 to determine whether there is a conflicting reservation. If it is determined that there is no conflicting reservation (No in step S42), the process proceeds to step S46.

[0117] If it is determined that there is a conflicting reservation (Yes in step S42), the request unit 42 requests the user who has the conflicting reservation to cancel the occupancy request (step S43). If the requested user does not accept the request (No in step S44), the process ends.

[0118] If the user who received the request accepts the request (Yes in step S44), the reward granting unit 43 gives preferential treatment to the user who accepted the request (step S45).

[0119] Next, the reservation unit 46 changes the reservation time of the user who made the change request to the desired time slot (step S46). After completing the process of step S46, the reservation management device 40 ends the series of processes described above.

[0120] The reservation management device of this embodiment is configured as described above. In addition to the effects obtained from the reservation management devices of the first and second embodiments, the reservation management device of this embodiment provides the following effects.

[0121] A reservation management device according to an aspect of this embodiment further includes a request unit and a reward granting unit. The input receiving unit further receives a request from the occupant to change the occupied time slot. The change request includes a desired time slot to be changed. If the desired time slot conflicts with the occupied time slot reserved by another user, the other user is requested to cancel the reservation. The reward granting unit provides preferential treatment to users who accept the request. With the above configuration, the reservation management device according to an aspect of this embodiment can compensate to a certain extent for the disadvantage suffered by a user by accepting a cancellation request through preferential treatment, thereby ensuring fairness among users. Furthermore, the reservation management device according to an aspect of this embodiment can also accommodate cases where a reservation time needs to be changed suddenly due to weather or other reasons, thereby improving user convenience.

[0122] (Fifth embodiment) In this embodiment, a reservation management device 50 will be described, which has a simplified configuration of the reservation management devices in the first, second, third, and fourth embodiments. In the following explanation, explanations of parts that are the same as those in the first to fourth embodiments will be omitted as appropriate.

[0123] (composition) Next, the configuration of the reservation management device in this embodiment will be described with reference to the drawings. Fig. 25 is a block diagram showing an example of the configuration of the reservation management device in the present disclosure. The reservation management device 50 includes an input receiving unit 51, an acquisition unit 53, a determination unit 54, a request processing unit 55, and a reservation unit 56.

[0124] The input receiving unit 51 receives an occupancy request from a user, including the occupancy time slot of the takeoff and landing field and the desired occupancy amount. The acquisition unit 53 acquires the amount of usage by the user within a specified period. The determination unit 54 determines whether the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit. If it is determined that the upper limit is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time slot, the request processing unit 55 sets the user as a new occupancy candidate. The reservation unit 56 determines the user set as an occupancy candidate as the occupant of the occupancy time slot at the predetermined acceptance closing time and makes a reservation.

[0125] (operation) Next, an example of the operation of the reservation management device in this embodiment will be described with reference to Fig. 26. Fig. 26 is a diagram showing an example of the operation of the reservation management device in the present disclosure.

[0126] First, the input receiving unit 51 receives an occupancy request from a user, including a time period for occupying the airfield and a desired occupancy fee (step S11).

[0127] Next, the acquisition unit 53 acquires the amount of money used by the user within a predetermined period (step S12).

[0128] Next, the determination unit 54 determines whether the total of the usage amount and the desired occupancy amount exceeds a predetermined upper limit (step S13).

[0129] Next, if it is determined that the upper limit amount is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time period, the request processing unit 55 sets the user as a new occupancy candidate (step S14).

[0130] Next, the reservation unit 56 determines the user who has been set as an occupancy candidate at the predetermined acceptance closing time as the occupant of the occupancy time slot and makes a reservation (step S15).

[0131] In the reservation management device of this embodiment, reservations are made only if the sum of the usage amount and the desired occupancy amount does not exceed the upper limit. This prevents specific users with economic advantages from monopolizing airfield reservations. In other words, the reservation management device of this embodiment can prevent specific users from monopolizing airfield reservations for personal aircraft.

[0132] (Hardware configuration) The functions of each of the components in each of the embodiments of the present disclosure described above can be realized not only as hardware but also as a computer device or firmware under program control.

[0133] 27 is a diagram showing an example of a hardware configuration in which the reservation management device according to the present disclosure is realized by a computer device 90 including a processor. The reservation management device according to each embodiment is realized by the computer device 90. As shown in FIG. 27, the computer device 90 includes a processor 91, memory 92, a storage device 93 such as a hard disk for storing programs, an input / output interface 94 for connecting input devices and output devices, and a communication interface 95 for connecting to a network.

[0134] The processor 91 loads a program (instructions) stored in a storage device 93 or the like into the memory 92. For example, the program is a software program for executing the control and processing in the present disclosure. The processor 91 executes the program loaded into the memory 92. The processor 91 executes the program to execute the control and processing in the present disclosure.

[0135] The storage device 93 may be, for example, an optical disk, a flexible disk, a magneto-optical disk, an external hard disk, or a semiconductor memory. Some storage media in the storage device are non-volatile storage devices, and the programs are recorded therein. The programs may also be downloaded from an external computer (not shown) connected to a communication network.

[0136] The input device connected to the input / output interface 94 is realized by, for example, a mouse or a keyboard, and is used for input operations. Similarly, the output device connected to the input / output interface 94 is realized by, for example, a display, and is used for displaying and checking output results.

[0137] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0138] Some or all of the above embodiments can also be described as follows:

[0139] (Appendix 1) an input receiving means for receiving from a user an occupancy request including a time period for occupying the takeoff and landing field and a desired occupancy fee; an acquisition means for acquiring the amount of usage by the user within a predetermined period; a determination means for determining whether or not the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit; a request processing means for setting the user as a new occupancy candidate when it is determined that the upper limit amount is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time period; a reservation means for determining the user who has been set as the occupancy candidate as the occupant of the occupancy time slot at a predetermined end time of acceptance, and making a reservation; A reservation management device comprising: (Appendix 2) A guaranteed number of reservations within a predetermined period is determined for each user, The acquisition means acquires the guaranteed number of reservations of the user who has made the occupancy request, When it is determined that the upper limit amount is not exceeded and the number of reservations made by the user in a predetermined period is less than the guaranteed number of reservations, the request processing means determines the user as an occupant instead of setting the occupancy candidate, 2. The reservation management device according to claim 1, wherein the reservation means makes the reservation regardless of the end time of acceptance when the request processing means has determined the occupant. (Appendix 3) The buy-now amount is determined for each of the aforementioned occupancy time periods, When it is determined that the upper limit price is not exceeded and the desired occupancy price is equal to the immediate purchase price, the request processing means determines the user as the occupant instead of setting the occupancy candidate; 2. The reservation management device according to claim 1, wherein the reservation means makes the reservation regardless of the end time of acceptance when the request processing means has determined the occupant. (Appendix 4) an upper limit of the number of occupancy requests that the user can make for the occupancy time period of the airfield is determined; The acquisition means further acquires the number of occupancy requests made by the user for the occupancy time period; The determining means further determines whether the number of occupancy requests exceeds the upper limit number of times; 4. The reservation management device according to any one of appendices 1 to 3, wherein the request processing means further sets the user as a new occupancy candidate when it is determined that the upper limit number of times has not been exceeded. (Appendix 5) a specifying means for selecting an airfield available for the user's personal aircraft from the plurality of airfields; the input receiving means further receives input of aircraft information including the aircraft model of the personal aircraft; the specifying means compares airfield information including information on the area of ​​each of the plurality of airfields with information on the size of the personal aircraft specified from the aircraft type, and selects an airfield whose area the personal aircraft can fit into as the available airfield; 5. The reservation management device according to claim 1, wherein the input receiving means receives the occupancy request for the selected takeoff and landing field. (Appendix 6) The aircraft information further includes a power source type of the personal aircraft; The reservation management device described in Appendix 5, wherein the identification means selects an airfield with charging facilities as the available airfield if the power source type of the personal aircraft is rechargeable. (Appendix 7) notification means for notifying the user; and a specifying means for selecting an airfield available for use by the user's personal aircraft from the plurality of airfields; The input receiving means further receives a request to cancel the reservation, The identification means uses reservation log information to identify a user who has a personal aircraft that can use the airfield for which the cancellation request has been made; When the input of the cancellation request is accepted, the notification means notifies the identified user that the occupied time slot is available for reservation; The input receiving means further receives a reservation request from the user who has received the notification, 7. The reservation management device according to any one of claims 1 to 6, wherein, when the reservation request is received, the reservation means confirms the reservation of the user. (Appendix 8) a requesting means for requesting cancellation of the reservation; The system further comprises a reward granting means for granting preferential treatment to the user who accepts the request, the input receiving means further receives a request from the occupant to change the occupied time period; The change request includes a desired time period to be changed, 7. The reservation management device according to claim 1, wherein the request means makes the request to the user when the desired time slot to be changed conflicts with the occupied time slot in a reservation made by another user. (Appendix 9) The computer Accept an occupancy request from a user, including a time period for occupying the airfield and a desired occupancy price; Acquire the amount of usage by the user within a predetermined period of time; determining whether the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit; If it is determined that the upper limit amount is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time period, the user is set as a new occupancy candidate; A reservation management method in which the user who has been set as the occupancy candidate is determined to be the occupant of the occupancy time slot at a predetermined end time of acceptance, and a reservation is made. (Appendix 10) On the computer, A process of receiving an occupancy request from a user, the request including a time period for occupying the airfield and a desired occupancy price; A process of acquiring the amount of usage by the user within a predetermined period; a process of determining whether or not the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit; a process of setting the user as a new occupancy candidate when it is determined that the upper limit amount is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time period; and determining the user who has been set as the occupancy candidate as the occupant of the occupancy time slot at a predetermined end time of acceptance, and making a reservation.

[0140] In addition, in the above appendices, some or all of the configurations described in appendices 2 to 8 that are dependent on appendices 1 may also be dependent on appendices 9 and 10 in the same dependent relationship as appendices 2 to 8. Furthermore, not limited to appendices 1, 9, and 10, some or all of the configurations described as appendices may be made dependent on various hardware, software, various recording means for recording software, or systems, within the scope of each of the above-mentioned embodiments. [Explanation of symbols]

[0141] 10, 20, 30, 40, 50 Reservation Management Device 11, 21, 31, 41, 51 Input reception section 12, 32 Specific part 13, 23, 53 Acquisition part 14, 54 Judgment section 15, 25, 55 Request processing section 16, 26, 36, 46, 56 Reserved Section 17, 37 Notification Department 18, 28 Memory section 42 Request Department 43 Reward Division 80 Terminal Equipment 90 Computer Equipment 91 processors 92 memory 93 Storage device 94 Input / Output Interface 95 Communication Interface

Claims

1. an input receiving means for receiving from a user an occupancy request including a time period for occupying the takeoff and landing field and a desired occupancy fee; an acquisition means for acquiring the amount of usage by the user within a predetermined period; a determination means for determining whether or not the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit; a request processing means for setting the user as a new occupancy candidate when it is determined that the upper limit amount is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time period; a reservation means for determining the user who has been set as the occupancy candidate as the occupant of the occupancy time slot at a predetermined end time of acceptance, and making a reservation; A reservation management device comprising:

2. A guaranteed number of reservations within a predetermined period is determined for each user, The acquisition means acquires the guaranteed number of reservations of the user who has made the occupancy request, When it is determined that the upper limit amount is not exceeded and the number of reservations made by the user in a predetermined period is less than the guaranteed number of reservations, the request processing means determines the user as an occupant instead of setting the occupancy candidate, 2. The reservation management device according to claim 1, wherein said reservation means makes said reservation regardless of said acceptance closing time when said request processing means has determined said occupant.

3. The buy-now amount is determined for each of the aforementioned occupancy time periods, When it is determined that the upper limit price is not exceeded and the desired occupancy price is equal to the immediate purchase price, the request processing means determines the user as the occupant instead of setting the occupancy candidate; 2. The reservation management device according to claim 1, wherein said reservation means makes said reservation regardless of said acceptance closing time when said request processing means has determined said occupant.

4. an upper limit of the number of occupancy requests that the user can make for the occupancy time period of the airfield is determined; The acquisition means further acquires the number of occupancy requests made by the user for the occupancy time period; The determining means further determines whether the number of occupancy requests exceeds the upper limit number of times; 2. The reservation management device according to claim 1, wherein said request processing means further sets said user as a new occupancy candidate when it is determined that said upper limit number of times has not been exceeded.

5. a specifying means for selecting an airfield available for the user's personal aircraft from the plurality of airfields; the input receiving means further receives input of aircraft information including the aircraft model of the personal aircraft; the specifying means compares airfield information including information on the area of ​​each of the plurality of airfields with information on the size of the personal aircraft specified from the aircraft type, and selects an airfield whose area the personal aircraft can fit into as the available airfield; 2. The reservation management device according to claim 1, wherein said input receiving means receives said request for occupancy of said selected takeoff and landing field.

6. The aircraft information further includes a power source type of the personal aircraft; 6. The reservation management device according to claim 5, wherein the specifying means selects an airfield having a charging facility as the available airfield when the power source type of the personal aircraft is a rechargeable type.

7. notification means for notifying the user; and a specifying means for selecting an airfield available for use by the user's personal aircraft from the plurality of airfields; The input receiving means further receives a request to cancel the reservation, The identification means uses reservation log information to identify a user who has a personal aircraft that can use the airfield for which the cancellation request has been made; When the input of the cancellation request is accepted, the notification means notifies the identified user that the occupied time slot is available for reservation; The input receiving means further receives a reservation request from the user who has received the notification, 2. The reservation management device according to claim 1, wherein, when the reservation request is received, the reservation means confirms the reservation of the user.

8. a requesting means for requesting cancellation of the reservation; The system further comprises a reward granting means for granting preferential treatment to the user who accepts the request, the input receiving means further receives a request from the occupant to change the occupied time period; The change request includes a desired time period to be changed, 2. The reservation management device according to claim 1, wherein the requesting unit makes the request to the user when the desired time slot to be changed conflicts with the occupied time slot in a reservation made by another user.

9. The computer Accept an occupancy request from a user, including a time period for occupying the airfield and a desired occupancy price; Acquire the amount of usage by the user within a predetermined period of time; determining whether the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit; If it is determined that the upper limit amount is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time period, the user is set as a new occupancy candidate; A reservation management method in which the user who has been set as the occupancy candidate is determined to be the occupant of the occupancy time slot at a predetermined end time of acceptance, and a reservation is made.

10. On the computer, A process of receiving an occupancy request from a user, the request including a time period for occupying the airfield and a desired occupancy price; A process of acquiring the amount of usage by the user within a predetermined period; a process of determining whether or not the sum of the usage amount and the desired occupancy amount exceeds a predetermined upper limit; a process of setting the user as a new occupancy candidate when it is determined that the upper limit amount is not exceeded and the desired occupancy amount is higher than the desired occupancy amount presented by the occupancy candidate for the occupancy time period; and determining the user who has been set as the occupancy candidate as the occupant of the occupancy time slot at a predetermined end time of acceptance, and making a reservation.

Images