Reservation acceptance system and reservation acceptance method

Abstract

The present disclosure relates to a reservation acceptance system and a reservation acceptance method. The system includes one or more processors, and the one or more processors are configured to: obtain request information from a user who proposes a reservation for using a mobile body, the request information including the expected date and time, the departure place and the destination; derive a reservation result indicating whether the reservation is established for the request information; based on the request information, derive the reservation result indicating establishment, retention or non-establishment for the request information once or multiple times; when deriving the reservation result for the first time, derive at least one of the reservation results including the reservation result indicating the establishment for the request information and the reservation result indicating the retention; for the request information indicating the reservation result, derive the reservation result indicating the establishment or the non-establishment before a predetermined period; and notify the user of the reservation result that has been exported.

Description

Technical Field

[0001] The invention relates to a reservation acceptance system and a reservation acceptance method. Background Art

[0002] WO 2019 / 106745 discloses a demand-responsive transport operation system, which operates demand-responsive transport, wherein vehicles are operated in response to user requests. The demand-responsive transport operation system receives a trip request including an expected departure time and an expected arrival time as well as a departure place and a destination from a passenger, and creates a scheduling plan for a demand-responsive transport vehicle based on the trip requests aggregated at the specified time. Summary of the invention

[0003] In the technology disclosed in WO 2019 / 106745, since the vehicle dispatch is planned after the trip requests of multiple users are accepted until the specified time, the specified time has not arrived at the time when the user requests the trip, so that the user cannot obtain the result of the trip request. On the other hand, in the case of planning the vehicle dispatch at the time when each user makes a trip request, the trip request accepted later is more likely to be rejected, and the number of established trip requests may be greatly reduced.

[0004] The present invention provides a technique for suppressing a decrease in the number of established requests while improving ease of use for users.

[0005] According to the first scheme of the present invention, the reservation acceptance system includes one or more processors, and the one or more processors are configured to: obtain request information from a user who proposes a reservation for using a mobile body, the request information including the expected date and time, the departure place and the destination; export a reservation result indicating whether the reservation is established with respect to the request information; based on the request information, export the reservation result indicating establishment, retention or failure with respect to the request information once or multiple times; when exporting the reservation result for the first time, export at least one of the reservation results including the reservation result indicating establishment with respect to the request information and the reservation result indicating retention; with respect to the request information whose reservation result indicates retention, export the reservation result indicating establishment or failure before a predetermined deadline; and notify the user of the reservation result that has been exported.

[0006] The reservation acceptance method according to the second scheme of the present invention is executed by one or more processors. The reservation acceptance method includes: obtaining request information including a desired date and time, a departure place and a destination, the request information being requested by a user who proposes a reservation for using a mobile body; based on the request information and a derivation function, deriving a reservation result indicating whether the reservation is established for the request information; and notifying the user of the derived reservation result, wherein deriving the reservation result includes: deriving the reservation result indicating establishment, retention or non-establishment for the request information once or multiple times, when deriving the reservation result for the first time, deriving at least one of the reservation results including the reservation result indicating the establishment for the request information and the reservation result indicating the retention, and deriving the reservation result indicating the establishment or the non-establishment before a predetermined deadline for the request information indicating the reservation.

[0007] The present invention can provide a technique for suppressing a decrease in the number of established requests while improving ease of use for users. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described below with reference to the accompanying drawings, wherein like reference numerals represent like elements, and wherein:

[0009] Figure 1 is a diagram showing an overview of a reservation acceptance system according to an embodiment;

[0010] Figure 2 is a diagram showing a functional configuration of a reservation acceptance system according to an embodiment;

[0011] Figure 3A is a diagram showing request information sent from a user terminal device;

[0012] Figure 3B is a diagram showing vehicle information transmitted from a vehicle management device; and

[0013] Figure 4 This is a flowchart of a reservation result notification process performed by the reservation acceptance device. DETAILED DESCRIPTION

[0014] Figure 11 is a diagram showing an overview of a reservation acceptance system 1 according to an embodiment. The reservation acceptance system 1 includes a reservation acceptance device 10, a user terminal device 12, a vehicle management device 14, and a vehicle 16. The reservation acceptance system 1 accepts reservations from users for operation by on-demand transportation. In on-demand transportation, the reservation acceptance device 10 accepts a request from a user to reserve the use of one of the vehicles 16, and in response to the request, operates the vehicle 16 to transport the user and the user's luggage. Figure 1 The bus vehicle 16 shown enables users to share a ride. Note that although the vehicle 16 Figure 1 1 is shown as a moving body, but the vehicle 16 is not limited to this mode and may be a moving body such as a ship or an airplane, for example.

[0015] The user terminal device 12 is capable of communicating with the reservation accepting device 10. The user uses the user terminal device 12 to request the reservation accepting device 10 to operate the vehicle 16. The user terminal device 12 may be a mobile terminal device held by each user, and stores an application for requesting the operation of the vehicle 16. The user terminal device 12 executes the application, sends request information to the reservation accepting device 10, and receives a reservation result from the reservation accepting device 10, the reservation result indicating that the request has been established, reserved, or not established.

[0016] The user's request information is accepted until a predetermined acceptance deadline (e.g., one day before the operation date or a predetermined time before the operation time). In demand-responsive transportation, it is expected to operate in response to request information from all users, but these requests may not be established, depending on the content of the user's request information, because the number of vehicles 16 that can operate is limited. Whether the user's request will be established or not is ultimately determined by the reservation acceptance device 10. The reservation acceptance device 10 creates an operation plan corresponding to the established request and sends the operation plan to the vehicle management device 14.

[0017] An arrangement in which the reservation acceptance device 10 determines whether a request can be established at the moment of accepting a request from a user will result in a first-come, first-served basis system in which requests accepted later are more likely to be rejected and the number of established requests is greatly reduced. On the other hand, in an arrangement in which the reservation acceptance device 10 retains all requests from users until the acceptance deadline and determines whether the request is established at the acceptance deadline, the user cannot immediately tell whether the reservation has been established, which is inconvenient.

[0018] The reservation acceptance device 10 according to the present embodiment can reply to the request made by the user with the reservation result in at least two stages (i.e., the time of accepting the request and the time of reaching the acceptance deadline). For example, immediately after accepting the request from the user, the reservation acceptance device 10 notifies the user of the reservation result indicating establishment, reservation reservation or failure in response to the request, and when the request is retained, the reservation acceptance device 10 notifies the user of the reservation result indicating establishment or failure before the predetermined acceptance deadline. By notifying the reservation result in multiple stages as described above, it is possible to improve the usability and user experience.

[0019] The vehicle management device 14 manages the operation of the vehicle 16. The vehicle management device 14 can communicate with the reservation acceptance device 10 and the on-board device of the vehicle 16, receive vehicle information including the location information of the vehicle 16 from the vehicle 16, and send the vehicle information to the reservation acceptance device 10. In addition, the vehicle management device 14 receives the operation plan from the reservation acceptance device 10 and manages the vehicle 16 so that the vehicle 16 travels according to the operation plan. The vehicle 16 may be capable of automatic driving.

[0020] Figure 2 1 is a diagram showing a functional configuration of a reservation acceptance system 1 according to an embodiment. Figure 2 In the present invention, the various elements described as functional blocks that perform various processes may be composed of circuit blocks, memories, and other integrated circuits in terms of hardware, and may be implemented in terms of software by programs loaded into the memory, etc. Therefore, it will be understood by those skilled in the art that these functional blocks may be implemented in various forms by hardware only, software only, or a combination thereof, and are not limited to any particular arrangement.

[0021] The reservation acceptance device 10 includes a communication unit 20, an acquisition unit 22, a derivation processing unit 24, a request storage unit 26, and a notification control unit 28. The communication unit 20 can communicate with the user terminal device 12 and the vehicle management device 14, and transmit and receive information.

[0022] The acquisition unit 22 acquires the request information from the user terminal device 12 via the communication unit 20, and acquires the vehicle information from the vehicle management device 14. Figure 3A and Figure 3B Describes the request information and vehicle information.

[0023] Figure 3A shows the request information sent from the user terminal device 12, Figure 3B 1 shows the vehicle information sent from the vehicle management device 14. Figure 3A As shown, the request information includes a user identification (ID), departure information, destination information, desired date and time information, and deadline information.

[0024] The departure place information and the destination information may be position information of a pre-set pickup / drop-off location, or may be position information indicated by longitude and latitude. That is, the vehicle 16 for transportation in response to demand may move between pre-set pickup / drop-off locations, or may move to any location desired by the user. The desired date and time information may specify any one of a departure time, a departure time period, an arrival time, and an arrival time period.

[0025] The deadline information indicates a deadline that the user expects for responding to the request, and indicates a deadline for receiving a reservation result indicating whether the request is established or not. The user can receive a reservation result indicating whether the request has been established before the deadline in the deadline information set by the user. In addition, when the user does not set the request response deadline, the standard request response deadline will be automatically set. Note that the request information may include the number of passengers, and a single request may be made to request to take multiple passengers.

[0026] like Figure 3B As shown, the vehicle information includes a vehicle ID, location information, seat information, and operation schedule information. The location information of the vehicle is sent from the onboard device of the vehicle 16 to the vehicle management device 14. In the seat information of the vehicle 16, the seat ID of the seat that can be occupied is saved in association with the user ID of the user who has reserved the seat ID. That is, the seat information includes information about the user's reservation for each seat. Therefore, the acquisition unit 22 is able to acquire information about the remaining seats that are not fully reserved. The operation schedule information is information about the operation schedule of the vehicle 16 that has been determined by the reservation acceptance device 10, etc.

[0027] Now the description will return to Figure 2 The export processing unit 24 exports a reservation result indicating whether the reservation has been established for the acquired request information. This “no” includes a reserved state and an unestablished state. The export processing unit 24 includes a model storage unit 30 and an export unit 32.

[0028] The model storage unit 30 stores a derivation function F1 for deriving a reservation result, which is generated based on past request information. When receiving a request information input from a certain user, the derivation function F1 outputs the possibility of the request information being satisfied through a score of, for example, 0% to 100%.

[0029] The export function F1 is generated based on the request information of the past, and when the request information of a certain user is similar to most of the request information established in the past, the possibility of establishment is high. The export function F1 is a learning model using, for example, a decision tree, a random forest, a logistic regression, a support vector machine, a k-nearest neighbor algorithm, a support vector regression, a deep neural network (DNN), a long short-term memory (LSTM), or a neural network technology, and is generated by machine learning using the request information of the past as teaching data. Therefore, an empirical judgment that has been learned from the request information of the past can be made. In addition, the export function F1 can be rule-based, and a result can be derived that when there is a large amount of other request information that allows the user to be transported on the same driving route as the driving route included in the request information of a certain user, the possibility of establishment is high, or a result can be derived that when there is a predetermined number of other request information that allows the user to be transported on the same driving route as the driving route included in the request information of a certain user, the request is established. In addition, the export function F1 can be a combination of a learning model and a rule-based arrangement. For example, the export function F1 can be generated by combining a learning model with a rule that enables the request of a user with few appointments to be established.

[0030] In terms of learning the derived function F1, the goal may be to maximize the number of established requests, but the goal is not limited to maximizing the number of established requests. For example, the goal may be to maximize the total riding distance of the user, the usage fee, the profit of the commercial operator, etc., or the goal may be a combination thereof.

[0031] In order to enable the export function F1 to determine the possibility of establishment based on weather, day of the week and traffic conditions, in addition to the request information, weather information, day of the week information, traffic information, etc. that have been associated with the request information can be input into the machine learning of the export function F1 as past experience.

[0032] The derivation function F1 can derive a score indicating the possibility of establishment for the request information acquired by the acquisition unit 22, and the score can be divided into three categories: establishment, retention and failure. Alternatively, the derivation function can classify the request information into four categories: establishment, high possibility retention, low possibility retention and failure.

[0033] In the derivation function F1, the reservation result is derived by inputting not only the request information of a certain user but also the request information and vehicle information of another user. The use of the vehicle information enables the derivation of the reservation result based on the number of remaining seats where the user can sit. The derivation function F1 can be trained and updated at predetermined intervals based on the accumulated request information and its reservation results.

[0034] The export unit 32 exports the reservation result based on the acquired request information and the export function F1. The export unit 32 inputs the request information of a certain user into the export function F1, and when the score derived by the export function F1 is not less than a predetermined threshold, the export reservation result will be established.

[0035] It is sufficient to set a predetermined threshold value according to the time from the expected date and time of a certain request information to the current date and time, and the predetermined threshold value can be set, for example, so that the shorter the time from the expected date and time of a certain request information to the current date and time, the lower the threshold value. In addition, the predetermined threshold value can be set to be lower when the time from the expected date and time of a certain request information to the current date and time is shorter than when the time is longer. For example, the deriving unit 32 can set the predetermined threshold value to 95% one week before the expected date and time, and set the predetermined threshold value to 70% two days before the expected date and time. That is, when the probability of being established one week before the expected date and time is more than 95%, the deriving unit 32 derives the request will be established, and when the probability of being established two days before the expected date and time is more than 70%, the deriving unit 32 derives the request will be established. Therefore, the predetermined threshold value can be set to decrease as the expected date and time approaches. Therefore, the predetermined threshold value can be set so that the request is more likely to be established as the running time approaches. Note that the predetermined threshold value can be a pre-set fixed value.

[0036] In addition, the predetermined threshold value may be set based on the profile information of the user. For example, the deriving unit 32 may set the predetermined threshold value to be lower than the reference value for the request information of the user whose requests are frequently not fulfilled.

[0037] The export unit 32 may export the reservation result multiple times for the request information acquired by the acquisition unit 22. The export unit 32 exports the reservation result of reservation that is retained or not established when the request information is not established for the first time, and exports the reservation result of establishment or not established for the reserved request information from the second time and thereafter until the predetermined period. In addition, when the request information is not established for the first time, the export unit 32 may only export the reservation result of reservation. That is, at least the reservation result indicating establishment or reservation is exported for the request information for the first time, and the reservation result of establishment or not established is exported before the predetermined period.

[0038] Therefore, when making a reservation request, the user can at least know the establishment or reservation of the reservation at the first time (the moment when the request is accepted), so the reservation result can be recognized at an early stage. In addition, the reservation result is determined based on a model generated based on past request information, and thus an appropriate reservation result can be derived. On the other hand, the reservation acceptance device 10 can temporarily retain the user's request information so that a determination can be made after waiting for other request information, and the number of shared ride passengers can be increased to increase the number of established requests.

[0039] The export unit 32 exports the reservation result of being completed or not completed before the date indicated in the deadline information. Therefore, the user can freely set the deadline for indicating completion or not completed and change the reservation status. Therefore, the usability can be improved for users who want to know the result in advance, users who want to share a ride in a vehicle even if they have to wait until the acceptance deadline, etc.

[0040] When the deadline for accepting the request is reached, the export unit 32 exports the establishment or non-establishment from the reserved request information, exports the final reservation result, and eliminates the reserved request information. When the acceptance deadline is reached and the final reservation result is exported, the export unit 32 can use the export function F1 with additional rules. For example, when exporting the final reservation result, such a rule can be added, in which, among the reserved request information, request information with a common departure place and a common destination is preferentially established.

[0041] When the predetermined re-evaluation condition is met, the export unit 32 can derive the reservation result from the reserved request information based on the export function F1. That is, when the re-evaluation condition is met, the reserved request information is re-evaluated, and it is determined whether the request information is established or reserved. The re-evaluation condition includes at least one of the conditions that, for example, another request has been established, the vehicle management device 14 has added the operation of a new vehicle, and the re-evaluation time has been reached. When another request is established, the export unit 32 re-evaluates whether there is any reserved request information that can be shared in the vehicle corresponding to the other request information. In addition, when the operation of a new vehicle is added, the export unit 32 re-evaluates whether there is any reserved request information for riding the vehicle. In addition, the export unit 32 re-evaluates the reserved request information at the re-evaluation time (for example, 1 o'clock every afternoon). For example, when the predetermined threshold becomes lower as the operating time approaches, the possibility of establishment increases each time the re-evaluation time is reached. Therefore, when the re-evaluation condition is met, even before the acceptance deadline is reached, the export unit 32 again derives the reservation result for the reserved request information. This can increase the possibility that the request will be established before the acceptance deadline.

[0042] The request storage unit 26 stores the reserved request information and the established request information. Therefore, the export unit 32 can re-export the reservation result for the reserved request information. In addition, the export unit 32 can export whether the newly acquired request information enables the user to participate in the shared ride in the vehicle corresponding to the established request information.

[0043] The notification control unit 28 controls notification of the reservation result derived by the deriving unit 32 to the user, and transmits the reservation result to the user terminal device 12 via the communication unit 20. The user terminal device 12 outputs the reservation result received from the reservation acceptance device 10. In addition, the notification control unit 28 transmits the established request information as an operation plan to the vehicle management device 14. The vehicle management device 14 overwrites the established request information as the operation information and updates the vehicle information.

[0044] The deriving unit 32 derives the possibility of the appointment being established by the deriving function F1, and when the appointment result is reserved, the notification control unit 28 sends information indicating the possibility of establishment to the user terminal device 12, and the user terminal device 12 notifies the user of the information indicating the possibility of establishment. The information indicating the possibility of establishment notified to the user by the user terminal device 12 can be a percentage display or a step display. For example, the user terminal device 12 displays the possibility of establishment in three stages of "high", "medium" and "low", and displays the characters, colors, sounds, vibrations and / or patterns corresponding to each of the three stages. Therefore, when the request information is reserved, the user can know the possibility of establishment.

[0045] When the user's request information is retained, the notification control unit 28 can notify the user to shift the request information to a time period with a high possibility of establishment. The time period with increased possibility of establishment is derived by the deriving unit 32 based on the deriving function F1 generated based on past request information.

[0046] The model saving unit 30 can save a derivation function F2 different from the derivation function F1, and the derivation unit 32 can use the derivation function F2 to derive the reservation result. The other derivation function F2 derives the prediction result for the request predicted to be generated in the future based on the past request information. In the prediction result of the request, the predicted number of requests to be accepted is set for the set date and time, destination and departure point. For example, the derivation function F2 is generated by learning based on the number of requests that were established and the number of requests that were not established in the past, the date and time of requests in the past, environmental information from the past, etc. Environmental information includes the weather on the expected date and time of the request, and whether there are large-scale activities near the destination and departure point. Therefore, the demand for requests can be predicted, and the time period and route where requests will be concentrated in the future can be derived.

[0047] The export unit 32 exports the reservation result of establishment or non-establishment based on the prediction result of the request derived by the export function F2 and the request information actually obtained. For example, even if the user applies for a request at an early stage, when the export unit 32 predicts that the request for another route will be concentrated in the time period of the request, the export unit 32 will most likely determine that the request is not established. Note that, for example, the export unit 32 can export the reservation result for the purpose of maximizing the number of established requests, but can also export the reservation result for other purposes, such as maximizing the total driving distance.

[0048] In addition, the export unit 32 can repeatedly perform the process of exporting the result of reservation that is established or not established based on the prediction result of the request exported by the export function F2 and the request information actually obtained, while changing the parameters of the export function F2 multiple times to calculate the possibility of reservation establishment, and exporting that the request will be established when the possibility of reservation establishment is not less than a predetermined value. For example, the export unit 32 repeats the process of exporting the result of reservation that is established or not established based on the prediction result of the request exported by the export function F2 and the request information actually obtained ten times, while changing the parameters, and when the request is established more than eight times out of ten times, the export unit 32 derives that the request will be established. In addition, the export unit 32 can determine that the request will be retained based on the value of the exported possibility of reservation establishment. The export unit 32 can use the export function F1 and the export function F2 to export the reservation result of the request. For example, the export unit 32 can use the prediction result of the request exported by the export function F2 as one of the input data of the export function F1.

[0049] Figure 4 2 is a flowchart of the notification process of the reservation result performed by the reservation receiving device 10. The acquisition unit 22 acquires the request information from the user terminal device 12 via the communication unit 20 (S10), and acquires the vehicle information from the vehicle management device 14 (S12).

[0050] The deriving unit 32 inputs the request information and the vehicle information acquired by the acquiring unit 22 into the deriving function F1 to derive a score, and evaluates the request information (S14). When the initial score of the request information derived by the deriving function F1 is a high score not lower than a predetermined threshold value (Yes in S16), the deriving unit 32 determines that the request is established, and the notification control unit 28 notifies the user terminal device 12 that sent the request information of information indicating that the request has been established (S18). Therefore, the notification on the establishment of the request can be performed before the acceptance deadline.

[0051] When the initial score of the request information derived by the derivation function F1 is not a high score not lower than the predetermined threshold value (No in S16), the derivation unit 32 determines that the request information is retained, and the notification control unit 28 notifies the user terminal device 12 that sent the request information of information indicating that the request has been retained (S20). The derivation unit 32 determines whether the re-evaluation condition is satisfied (S22).

[0052] When the re-evaluation condition is met (Yes in S22), the export unit 32 can export the reservation result from the retained request information based on the export function F1 and perform re-evaluation (S24). When the retained request information being re-evaluated is a high score not lower than the predetermined threshold (Yes in S26), the export unit 32 determines that the request is established, and the notification control unit 28 notifies the user terminal device 12 that sent the request information of the information indicating that the request has been established (S28). Therefore, the notification about the establishment of the request can be performed before the acceptance deadline. Note that the predetermined threshold for determining the score in S26 can be lower than the predetermined threshold for determining the score in S16. When the re-evaluated retained request information does not have a high score not lower than the predetermined threshold (No in S26), it is repeatedly determined whether the retained request information meets the re-evaluation condition until the acceptance deadline is reached (S22).

[0053] When the re-evaluation condition is not satisfied (No in S22), the deriving unit 32 determines whether the retained request information satisfies the evaluation period (acceptance period) (S30). The evaluation period is a period for completing the re-evaluation and corresponds to the acceptance period. When the retained request information does not satisfy the evaluation period (No in S30), the determination as to whether the re-evaluation condition is satisfied is repeated until the acceptance period is satisfied (S22).

[0054] When the retained request information satisfies the evaluation period (No in S30), the export unit 32 exports the final reservation result from the retained request information and creates an operation plan (S32). Note that after creating the operation plan, the export unit 32 may determine that the request of the user who can share the ride in the vehicle according to the operation plan is established. When the request information retained in the final reservation result satisfies the establishment condition (Yes in S34), the notification control unit 28 notifies the user terminal device 12 that sent the request information of information indicating that the request has been established (S36). When the export unit 32 determines that the final reservation result is established, the establishment condition is satisfied.

[0055] When the request information retained in the final reservation result does not satisfy the establishment condition (No in S34), the notification control unit 28 notifies the user terminal device 12 that sent the request information of information indicating that the request has not been established (S38). As described above, when the retained request information reaches the acceptance deadline, a conclusion is drawn as to whether the request is established or not.

[0056] It should be noted that the embodiments are merely exemplary, and those skilled in the art will appreciate that various modifications may be made to the combination of components, and these modifications are also within the scope of the present invention.

Claims

1. A reservation acceptance system, characterized in that The system includes one or more processors and a storage medium, wherein the one or more processors are configured to: acquiring request information from a user who makes a reservation for using a moving body, the request information including a desired date and time, a departure place, and a destination; Exporting a reservation result indicating whether the reservation is established for the request information; Based on the request information, deriving the reservation result indicating establishment, retention or non-establishment according to the request information once or multiple times; When exporting the reservation result for the first time, exporting at least one of the reservation results indicating the established reservation result and the reservation result indicating the reserved reservation result for the request information; For the request information indicating the reservation result, deriving the reservation result indicating the establishment or the non-establishment before a predetermined time limit; and Notifying the user of the exported reservation result; The storage medium is configured as: Saving an export function for exporting the reservation result; storing the derivation function generated by learning based on past request information, the derivation function being used to derive, based on the request information, a score indicating the possibility of establishment of the reservation for the request information; The one or more processors are configured to: deriving the score indicating the possibility of establishment of the reservation for the request information by the derivation function, and When the derived score is not less than a predetermined threshold, the derived appointment will be established; And the predetermined threshold is set according to the time from the moment when the request information has been acquired to the expected date and time.

2. The reservation acceptance system according to claim 1, characterized in that: The one or more processors are configured to: deriving information indicating the possibility of establishment of the reservation for the request information; and When the reservation result indicates the reservation, information indicating the possibility of establishment of the reservation is notified to the user.

3. The reservation acceptance system according to claim 1, characterized in that: The request information obtained by the one or more processors includes deadline information; and The one or more processors are configured to derive the reservation result indicating the establishment or the non-establishment before a date indicated in the deadline information.

4. The reservation acceptance system according to claim 1, characterized in that: The one or more processors are configured to, when a predetermined re-evaluation condition is satisfied before the predetermined deadline, derive the reservation result again for the request information indicating the reservation result being retained.

5. The reservation acceptance system according to any one of claims 1 to 4, characterized in that: The one or more processors are configured to: deriving predicted results for requests predicted to occur in the future; and Based on the prediction result for the request and the request information that have been derived, the reservation result indicating the establishment or the non-establishment is derived.

6. A reservation acceptance method, which is executed by a reservation acceptance system, wherein the reservation acceptance method is characterized by comprising: acquiring request information including a desired date and time, a departure place, and a destination, the request information being requested by a user who makes a reservation for using a moving body; Based on the request information and the export function, export a reservation result indicating whether the reservation is established for the request information; as well as Notifying the user of the exported reservation result, wherein Exporting the reservation result includes: deriving the reservation result indicating establishment, retention or non-establishment of the request information once or multiple times, When exporting the reservation result for the first time, exporting at least one of the reservation result indicating the establishment and the reservation result indicating the reservation is reserved for the request information, for the request information in which the reservation result indicates the reservation, deriving the reservation result indicating the establishment or the non-establishment before a predetermined time limit, Saving an export function for exporting the reservation result; storing the derivation function generated by learning based on past request information, the derivation function being used to derive, based on the request information, a score indicating the possibility of establishment of the reservation for the request information; deriving the score indicating the possibility of establishment of the reservation for the request information by the derivation function, and When the derived score is not less than a predetermined threshold, deriving that the reservation will be established; and The predetermined threshold is set according to the time from the time when the request information has been acquired to the expected date and time.

Images