JP2020135670A - Operation management system, operation management method, and program - Google Patents

Abstract

To solve the problem of difficulty in flexibly respond to variations in requests from a user.SOLUTION: An operation management system comprises: an identification unit that identifies a utilization plan containing a scheduled getting-off position where a user using a second moving body that moves in accordance with a prescribed operation plan plans to get-off from the second moving body; a first detection unit that detects occurrence of an event that causes a change to the utilization plan in a period during which at least the user is using the second moving body; an estimation unit that estimates a probability of change indicating a degree of possibility that a position where the user gets off from the second moving body is changed to a middle stop position where the second moving body stops before it reaches the scheduled getting-off position on the basis of a situation of occurrence of an event detected by the first detection unit; and an operation determination unit that determines an operation of the first moving body with respect to the middle stop position on the basis of the probability of change estimated by the estimation unit.SELECTED DRAWING: Figure 1

Description

The present invention relates to an operation management system, an operation management method and a program.

A taxi dispatch system that dispatches a taxi in response to a request from a taxi user is known (see, for example, Patent Documents 1 and 2).
[Prior art literature]
[Patent Document]
[Patent Document 1] Japanese Patent Application Laid-Open No. 62-000155 [Patent Document 2] Japanese Patent Application Laid-Open No. 01-267800

For example, a user of public transportation may want to get off the public transportation and head for the destination while securing a private space while getting on the public transportation. As an example, if the accompanying child does not stop crying or is not feeling well, the public transport user may want to switch from the public transport to another means of transportation such as a taxi, rental car or share car. There is. If the above transfer is realized smoothly, the convenience of the user will be significantly improved. On the other hand, if the child stops crying or recovers in physical condition before the above-mentioned user gets off the train, the above-mentioned transfer becomes unnecessary. The conventional vehicle allocation system cannot flexibly respond to such fluctuations in user demands.

In the first aspect of the present invention, an operation management system is provided. The above-mentioned operation management system manages the operation of the first moving body that can move according to the user's request, for example. In the above operation management system, for example, a user who uses a second moving body that moves according to a predetermined operation plan identifies a usage plan including a planned disembarkation position where the user plans to get off the second moving body. It has a part. The operation management system includes, for example, a first detection unit that detects the occurrence of an event that causes a change in the usage plan, at least during the period when the user is using the second moving body. In the above operation management system, for example, based on the occurrence status of the event detected by the first detection unit, the position where the user gets off the second moving body stops until the second moving body reaches the scheduled getting-off position. It is provided with an estimation unit that estimates a change probability indicating the degree of possibility of being changed to a stop position. The above-mentioned operation management system includes, for example, an operation determination unit that determines the operation of the first moving body with respect to the intermediate stop position based on the change probability estimated by the estimation unit.

In the above operation management system, the estimation unit is changed so that the larger the number or frequency of detection of the event by the first detection unit during the period when the user is using the second moving object, the greater the change probability. You may estimate the probability. The above-mentioned operation management system may include a second detection unit that detects the current position of the user at least while the user is using the second moving body. In the above operation management system, the estimation unit may estimate the change probability so that the shorter the distance from the user's current position detected by the second detection unit to the planned disembarkation position, the smaller the change probability.

In the above operation management system, the intermediate stop position may have a first intermediate stop position. In the above operation management system, the intermediate stop position may have a second intermediate stop position in which the second moving body stops before reaching the first intermediate stop position. In the above operation management system, in the estimation unit, (i) the first detection unit detects the event and the second moving body is the second in the period until the second moving body reaches the second intermediate stop position. 2 The change probability when the first detection unit detects an event during the period from reaching the halfway stop position to reaching the first halfway stop position is (ii) the second halfway through the second moving body. During the period until the stop position is reached, the first detection unit does not detect the event, and after the second moving body reaches the second stop position, until the first stop position is reached. The change probability may be estimated so as to be larger than the change probability when the first detection unit detects the event during the period.

In the above-mentioned operation management system, the operation determination unit may execute the vehicle allocation process of the first moving body when the change probability satisfies a predetermined condition. In the above operation management system, the vehicle allocation process may include a procedure for reserving the use of the first moving body by the user. In the above operation management system, the vehicle allocation process may include a procedure of sending a message to the user's communication terminal asking whether or not the user wants to use the first mobile body after the reservation is made. .. In the above operation management system, the vehicle allocation process may include a procedure for transmitting a message for inquiring whether or not the user desires to use the first mobile device to the user's communication terminal. In the above operation management system, the vehicle allocation process may include a procedure for receiving information from the user's communication terminal indicating that the user desires to use the first mobile body. In the above operation management system, the vehicle allocation process may include a procedure of reserving the use of the first moving body by the user after receiving the information indicating that the user desires to use the first moving body. In the above operation management system, the vehicle allocation process assigns a reservation to at least one of one or more first moving bodies, and outputs an instruction for moving the first moving body to which the reservation is assigned to an intermediate stop position. May include steps to do.

In the second aspect of the present invention, an operation management method is provided. The above-mentioned operation management method is, for example, a method of managing the operation of a first moving body that can be moved according to a user's request. In the above operation management method, for example, a user who uses a second moving body that moves according to a predetermined operation plan specifies a usage plan including a planned disembarkation position that is scheduled to get off from the second moving body. Has stages. The above-mentioned operation management method has, for example, a first detection step of detecting the occurrence of an event that causes a change in the usage plan, at least during the period when the user is using the second moving body. In the above operation management method, for example, based on the occurrence status of the event detected in the first detection stage, the position where the user gets off the second moving body stops until the second moving body reaches the planned getting-off position. It has an estimation stage for estimating the change probability indicating the degree of possibility of being changed to the stop position. The above-mentioned operation management method has, for example, an operation determination stage for determining the operation of the first moving body with respect to the intermediate stop position based on the change probability estimated in the estimation stage.

In a third aspect of the invention, a program is provided. A non-transitory computer-readable medium containing the above program may be provided. The above-mentioned program may be a program for making a computer function as the above-mentioned operation management system. The above program may be a program for causing a computer to execute the above operation management method.

The outline of the above invention does not list all the necessary features of the present invention. Subcombinations of these feature groups can also be inventions.

An example of the system configuration of the vehicle allocation support system 100 is shown schematically. An example of the use of the vehicle allocation support system 100 is schematically shown. An example of the internal configuration of the transportation management server 112 is shown schematically. An example of the internal configuration of the vehicle allocation management server 114 is schematically shown. An example of the data table 500 is shown schematically. An example of the internal configuration of the user management server 116 is shown schematically. An example of the internal configuration of the behavior management unit 640 is shown schematically. An example of the internal configuration of the vehicle allocation request unit 650 is shown schematically. An example of the data table 900 is shown schematically. An example of the data table 1000 is shown schematically. An example of the screen 1100 is shown schematically. An example of the screen 1200 is shown schematically. An example of information processing in the vehicle allocation request unit 650 is shown schematically. An example of information processing in the vehicle allocation request unit 650 is shown schematically. An example of information processing in the vehicle allocation request unit 650 is shown schematically. An example of the internal configuration of the communication terminal 120 is shown schematically. An example of the system configuration of the computer 3000 is shown schematically.

Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the inventions claimed in the claims. Also, not all combinations of features described in the embodiments are essential to the means of solving the invention. In the drawings, the same or similar parts may be given the same reference number to omit duplicate explanations.

[Overview of vehicle dispatch support system 100]
The outline of the vehicle allocation support system 100 will be described with reference to FIGS. 1 and 2. FIG. 1 schematically shows an example inside the vehicle allocation support system 100. FIG. 2 schematically shows an example of the use of the vehicle allocation support system 100.

As shown in FIG. 1, in the present embodiment, the vehicle allocation support system 100 includes a transportation management server 112, a vehicle allocation management server 114, and a user management server 116. The transportation management server 112, the vehicle allocation management server 114, and the user management server 116 may send and receive information to and from each other via an arbitrary communication network (for example, the communication network 10).

As shown in FIG. 2, according to the present embodiment, the details of the vehicle allocation support system 100 are described by taking as an example a case where the user 20 who is on the train 102 changes from the train 102 to the automobile 104 and moves to the destination. Explained.

In the present embodiment, the vehicle allocation support system 100 manages the operation of the automobile 104. The vehicle allocation support system 100 may manage the operation of the vehicle 104 by executing the vehicle allocation process of the vehicle 104.

Specifically, the vehicle allocation support system 100 manages reservations for at least one use of one or more vehicles 104. Further, the vehicle allocation support system 100 manages the movement of one or more automobiles 104 based on the contents of the above reservation. As a result, the vehicle allocation support system can manage the operation of the vehicle 104.

In the present embodiment, the user 20 gets on the train 102 at the station SA, which is the nearest station to the departure place. At this point, the user 20 plans to use the train 102 to move from the station SA to the station SD, which is the nearest station to the destination, via the station SB and the station SC.

Here, for example, when the train 102 is moving in the section between the station SA and the station SB, when an event (sometimes referred to as a disembarkation triggering event) occurs in which the user 20 thinks about getting off the train. The user 20 can (i) get off at the station SB or the station SC and move to the destination by using the car 104 from the station where the stop is made, or (ii) after arriving at the station SD, the car from the station SD. There is a possibility of using 104 to move to the destination. The disembarkation trigger events include (i) a change in the state of the user 20, (ii) a change in the state of the companion 22 of the user 20, and (iii) a state of the train 102 on which the user 20 is boarded. (For example, an increase in boarding density, an incident, an accident, a breakdown, etc.) has occurred.

The change in the state of the user 20 may be a change in the physical condition of the user 20. Examples of changes in physical condition include fever, chills, headache, and abdominal pain. The change in physical condition may be a recurring cough, sneeze, runny nose, and at least one of tears. The change in physical condition may be an increase to the extent that it feels uncomfortable. The change in the state of the companion 22 may be a change in the physical condition or mood of the companion 22. The change in physical condition may be as described above. Examples of changes in mood include crying and not stopping crying. Examples of changes in the state of the train 102 include (i) an increase in boarding density, (i) an incident, an accident, or a failure.

The disembarkation trigger event may be that a particular event satisfies a particular condition. Specific conditions include a condition that the frequency or number of occurrences of the above-mentioned specific event is higher than a predetermined value, and that the frequency or number of occurrences of the above-mentioned specific event is smaller than a predetermined value. Conditions and the like are exemplified.

Therefore, according to the present embodiment, the vehicle allocation support system 100 monitors the user 20 or the train 102 to detect the occurrence of a disembarkation triggering event. For example, the vehicle allocation support system 100 detects the occurrence of a disembarkation trigger event based on the information acquired from the communication terminal 120 used by the user 20.

When the occurrence of the disembarkation triggering event is detected, the vehicle dispatch support system 100 determines whether or not the vehicle 104 needs to be dispatched and whether or not the vehicle can be dispatched. When it is determined that the need for vehicle allocation is relatively high, the vehicle allocation support system 100, for example, provides information indicating the determination result regarding the availability of vehicle allocation at each of the station SB, station SC, and station SD, and a disembarkation trigger event occurs. It is transmitted to the communication terminal 120 of the user 20. As a result, the user 20 can easily determine whether or not to disembark the train 102 in consideration of the time until the train 102 arrives at each station and whether or not the automobile 104 can be dispatched at each station. ..

Further, in the present embodiment, the vehicle allocation support system 100 starts executing the vehicle allocation process before the user 20 gets off the train 102 on the way. As a result, the time and effort for the user 20 to request the dispatch of the automobile 104 at the stopover station is greatly reduced.

The vehicle allocation process includes, for example, a procedure for transmitting a message to the communication terminal 120 of the user 20 for inquiring whether or not the user 20 desires to use the automobile 104. The vehicle allocation process includes, for example, a procedure for receiving information (sometimes referred to as a vehicle allocation instruction) indicating that the user 20 desires to use the automobile 104 from the communication terminal 120 of the user 20. The vehicle allocation process includes, for example, a procedure for reserving the use of the automobile 104 by the user 20. The vehicle allocation process includes, for example, a procedure of assigning a reservation to at least one of one or more automobiles 104 and outputting an instruction for moving the automobile 104 to which the reservation is assigned to a specific stop station. The vehicle allocation support system 100 does not have to execute a part of the above procedure, and the order of the above procedure may be arbitrarily changed.

According to one embodiment, the vehicle allocation support system 100 reserves the use of the vehicle 104 by the user 20 before receiving the vehicle allocation instruction from the communication terminal 120 of the user 20. After that, if the vehicle dispatch support system 100 cannot acquire the information indicating the intention of the user 20 by the predetermined deadline, the vehicle dispatch support system 100 cancels the above reservation, for example.

According to the above embodiment, the vehicle allocation reservation process is executed prior to the vehicle allocation instruction from the user 20. Therefore, when the user 20 actually requests the vehicle allocation, the user 20 can smoothly reserve the vehicle allocation. Further, if the user 20 does not respond to any inquiry from the vehicle allocation support system 100, the above reservation is automatically canceled, so that the time and effort for the user 20 to reserve the vehicle allocation is greatly reduced. According to the above embodiment, the vehicle allocation support system 100 can flexibly respond to fluctuations in the demands of the user 20.

According to another embodiment, the vehicle allocation support system 100 reserves the use of the vehicle 104 by the user 20 after receiving the vehicle allocation instruction from the communication terminal 120 of the user 20. When the vehicle dispatch support system 100 receives information from the communication terminal 120 of the user 20 indicating that the user 20 requests the cancellation of the reservation, the vehicle dispatch support system 100 may cancel the above reservation. According to the above embodiment, the vehicle allocation support system 100 can flexibly respond to fluctuations in the demands of the user 20.

In the above two embodiments, the method of canceling the reservation is not particularly limited. As another example of the method of canceling the reservation, the vehicle allocation support system 100 may cancel the reservation according to the following procedure. In the present embodiment, the vehicle allocation support system 100 can detect that the user 20 has got off the train 102. For example, the vehicle allocation support system 100 detects getting off the user 20 based on the information acquired from the communication terminal 120 used by the user 20. If the disembarkation of the user 20 is not detected at the station designated by the above reservation, the vehicle allocation support system 100 cancels the above reservation. On the other hand, when the disembarkation of the user 20 is detected at the station designated by the above reservation, the vehicle allocation support system 100 does not cancel the above reservation. According to the above embodiment, even if the user 20 does not perform an operation for canceling the reservation, the reservation is automatically canceled, so that the time and effort for the user 20 to reserve the vehicle allocation is greatly reduced.

[Overview of each part of the vehicle allocation support system 100]
In the present embodiment, the communication network 10 may be a wired communication transmission line, a wireless communication transmission line, or a combination of a wireless communication transmission line and a wired communication transmission line. .. The communication network 10 may include a wireless packet communication network, the Internet, a P2P network, a dedicated line, a VPN, a power line communication line, and the like. The communication network 10 may include (i) a mobile communication network such as a mobile phone line network, (ii) wireless MAN (for example, WiMAX®), wireless LAN (for example, WiFi®). ), Bluetooth®, Zigbee®, NFC (Near Field Communication) and other wireless data communication networks may be included.

In the present embodiment, the train 102 moves according to the operation plan. The operation plan defines a plurality of stations where the train 102 stops and a scheduled time when the train 102 stops at each station. The location of the station is predetermined and, in principle, cannot be changed according to the request of the user 20. In the operation plan of the train 102, it is preferable that one or a plurality of stop stations are provided between the departure station and the terminal station. The train 102 may be an unmanned driving vehicle, an autonomous driving vehicle, or a manned driving vehicle.

In the present embodiment, the automobile 104 is configured to be movable according to the request of the user 20. The boarding position and the stopping position of the automobile 104 can be changed according to the request of the user 20. For example, the automobile 104 starts from a point according to the request of the user 20 and transports a person or an object to a point according to the request of the user 20. The automobile 104 may be an unmanned driving vehicle, an autonomous driving vehicle, or a manned driving vehicle.

In the present embodiment, the details of the train 102 and the automobile 104 will be described by taking as an example the case where the user 20 transfers from the train 102 to the automobile 104. However, the train 102 and the automobile 104 are not limited to this embodiment. Any moving body can be used as the train 102 and the automobile 104.

Examples of moving bodies include vehicles, ships, and flying bodies. Examples of vehicles include automobiles, motorcycles, and trains. Examples of automobiles include engine vehicles, electric vehicles, fuel cell vehicles, hybrid vehicles, and work machines. Examples of the motorcycle include (i) a motorcycle, (ii) a three-wheeled motorcycle, and (iii) a standing two-wheeled vehicle or a three-wheeled vehicle having a power unit. Examples of ships include ships, hovercraft, surface bikes, submarines, submarines, and underwater scooters. Examples of the flying object include an airplane, an airship or a balloon, a balloon, a helicopter, and a drone.

Examples of moving objects that move according to the operation plan include fixed-route buses, long-distance buses, shared cars, railroad cars, and passenger planes. The moving body that moves according to the request of the user 20 may be a moving body reserved by the user 20 or a moving body reserved by a relatively small number of users. Examples of the moving body that moves according to the request of the user 20 include a taxi, a rental car, a share car, a vehicle used for ride sharing, and a private jet.

In the present embodiment, the transportation management server 112 manages one or more trains 102. The transportation management server 112 manages, for example, the operation status of one or more trains 102. The transportation management server 112 may acquire information on the operation status of each train by communicating with the information processing devices mounted on each of the one or more trains 102 via the communication network 10.

Information on the operation status of the train 102 includes the operation plan of the train 102, the current position of the train 102, the operation status of the equipment mounted on the train 102, the presence or absence of an abnormality on the equipment mounted on the train 102, and the operation of the train 102. The presence or absence of abnormality is exemplified. Examples of abnormalities related to operation include delays, accidents, and construction work on routes related to train 102.

In the present embodiment, the vehicle allocation management server 114 manages one or more automobiles 104. The vehicle allocation management server 114 manages, for example, at least one of the current position and the operating status of each of one or more automobiles 104. The vehicle allocation management server 114 acquires information on at least one of the current position and the operating status of each vehicle by communicating with the information processing devices mounted on each of the one or more automobiles 104 via the communication network 10. Good.

Information on the operating status of the automobile 104 includes the usage status of the automobile 104, the destination of the automobile 104, the reservation status of the automobile 104, the presence or absence of an abnormality in the equipment mounted on the automobile 104, and the presence or absence of an abnormality in the running of the automobile 104. Illustrated. Examples of abnormalities related to the running of the automobile 104 include traffic jams, construction works, accidents, and the like on surrounding roads.

The vehicle allocation management server 114 may execute at least a part of the vehicle allocation process for at least one of the one or more automobiles 104. For example, the vehicle allocation management server 114 assigns a reservation to at least one of one or more automobiles 104 among a plurality of procedures included in the vehicle allocation process, and moves the reserved automobile 104 to a specific stop station. Perform the procedure to output the instruction to make it.

In this embodiment, the user management server 116 manages one or more users 20. The user management server 116 manages, for example, the actions of one or more users 20. The user management server 116 may manage each action plan (sometimes referred to as a schedule) of one or more users 20. The user management server 116 may manage at least one of each current position and movement history of one or more users 20. The user management server 116 may manage at least one of the presence / absence of the disembarkation triggering event and the history of the disembarkation triggering event for each of the one or more users 20. The user management server 116 may acquire various information about each user by communicating with the communication terminal 120 used by each of the one or more users 20 via the communication network 10.

The user management server 116 may execute at least a part of the vehicle allocation process for at least one of the one or more automobiles 104. The user management server 116 executes a procedure of transmitting a message for inquiring whether or not the user 20 wants to use the automobile 104 to the communication terminal 120 of the user 20 among the plurality of procedures included in the vehicle allocation process. You can. The user management server 116 may execute a procedure of receiving information indicating that the user 20 wants to use the automobile 104 from the communication terminal 120 of the user 20 among the plurality of procedures included in the vehicle allocation process. The user management server 116 may execute the procedure of reserving the use of the automobile 104 by the user 20 among the plurality of procedures included in the vehicle allocation process.

In the present embodiment, the communication terminal 120 transmits and receives various information to and from the user management server 116 via the communication network 10. The communication terminal 120 has an input device and an output device, and may be used as a user interface of the vehicle allocation support system 100. The communication terminal 120 has a self-position estimation device, an acceleration sensor, a gyro sensor, a temperature sensor, a camera, a microphone, and the like, and may collect various information about the environment in which the user 20 is placed. For example, the communication terminal 120 collects voice information of the surrounding environment of the user 20.

The communication terminal 120 may collect vital information of the user 20 from the wearable terminal 122 attached to the user 20. The communication terminal 120 may collect vital information of the companion 22 from the wearable terminal 122 attached to the companion 22 of the user 20. Examples of vital information include respiratory state, pulse, heartbeat, blood pressure, blood oxygen concentration, body temperature, sweating state, internal organs state, gastrointestinal state, speech state, excitement state, and arousal state.

In one embodiment, the communication terminal 120 transmits the collected information to the user management server 116. In another embodiment, the communication terminal 120 may analyze the collected information to detect a disembarkation trigger event. The communication terminal 120 may transmit information indicating that the disembarkation trigger event has been detected to the user management server 116. The communication terminal 120 may analyze the collected information to detect the disembarkation of the user 20. The communication terminal 120 may transmit information indicating that the disembarkation of the user 20 has been detected to the user management server 116.

In the present embodiment, the communication terminal 120 may be any information processing device used by the user 20, and the details thereof are not particularly limited. Examples of the communication terminal 120 include a personal computer and a mobile terminal. Examples of the mobile terminal include a mobile phone, a smartphone, a PDA, a tablet, a notebook computer or a laptop computer, a wearable computer, and the like.

The wearable terminal 122 may be an information processing device worn on the body of the user 20 or the companion 22, and the details thereof are not particularly limited. The wearable terminal 122 is attached to, for example, the face or head, chest, abdomen, wrist or ankle, or fingers or toes of the user 20. The wearable terminal 122 may be a wearable type vital sensor. Even if a single user 20 or a companion 22 is equipped with a plurality of wearable terminals 122, and the communication terminal 120 of the user 20 collects information about the user 20 or the companion 22 via the plurality of wearable terminals 122. Good.

The vehicle allocation support system 100 may be an example of an operation management system. The user management server 116 may be an example of an operation management system. The train 102 may be an example of a second moving body. The automobile 104 may be an example of the first moving body. The disembarkation trigger event may be an example of an event that triggers a change in the usage plan. The station where the train 102 stops may be an example of a planned stop position, a stop position, a first stop position, or a second stop position. The station SD may be an example of a planned disembarkation position. The station SB and the station SC may be an example of a stop position on the way. The station SB may be an example of the second stop position. The station SC may be an example of the first stop position. The dispatch of the automobile 104 may be an example of the use of the first moving body.

In the present embodiment, an example of the vehicle allocation support system 100 will be described by taking as an example a case where the vehicle allocation support system 100 includes a transportation management server 112, a vehicle allocation management server 114, and a user management server 116. However, the vehicle allocation support system 100 is not limited to this embodiment. In another embodiment, the functions of at least two servers, the transportation management server 112, the vehicle allocation management server 114, and the user management server 116, may be realized by a single server. At least a part of the function of the transportation management server 112, at least a part of the function of the vehicle allocation management server 114, and at least a part of the function of the user management server 116 may be realized by a single server.

[Specific configuration of each part of the vehicle allocation support system 100]
Each part of the vehicle allocation support system 100 may be realized by hardware, may be realized by software, or may be realized by hardware and software. At least a part of each part of the vehicle allocation support system 100 may be realized by a single server or may be realized by a plurality of servers. At least a part of each part of the vehicle allocation support system 100 may be realized on a virtual server or a cloud system. At least a part of each part of the vehicle allocation support system 100 may be realized by a personal computer or a mobile terminal. Examples of the mobile terminal include a mobile phone, a smartphone, a PDA, a tablet, a notebook computer or a laptop computer, a wearable computer, and the like. Each part of the vehicle allocation support system 100 may store information by using a distributed ledger technology such as a blockchain or a distributed network.

When at least a part of the components constituting the vehicle allocation support system 100 is realized by software, the components realized by the software define the operation related to the components in an information processing device having a general configuration. It may be realized by starting the program. The information processing device having the above general configuration includes (i) a data processing device having a processor such as a CPU and GPU, a ROM, a RAM, and a communication interface, and (ii) a keyboard, a pointing device, a touch panel, a camera, and a voice input. Input devices such as devices, gesture input devices, various sensors, GPS receivers, output devices such as (iii) display devices, audio output devices, vibration devices, and storage devices such as (iv) memory, HDD, SSD (external). It may include a storage device).

In the information processing apparatus having the above general configuration, the data processing apparatus or the storage apparatus may store the program. The above program is executed by the processor to cause the above information processing apparatus to execute the operation specified by the program. The above program may be stored on a non-temporary computer-readable recording medium. The above program may be stored in a computer-readable medium such as a CD-ROM, a DVD-ROM, a memory, or a hard disk, or may be stored in a storage device connected to a network.

The above program may be a program for operating the computer as a vehicle allocation support system 100 or a part thereof. The above program may include a module that defines the operation of each part of the vehicle allocation support system 100. These programs or modules work on a data processing device, an input device, an output device, a storage device, etc. to make the computer function as each part of the vehicle allocation support system 100, or to make the computer perform an information processing method in each part of the vehicle allocation support system 100. Let it run. The above program may be installed on a computer constituting at least a part of the vehicle allocation support system 100 from a computer-readable medium or a storage device connected to a network. By executing the above program, the computer may function as at least a part of each part of the vehicle allocation support system 100. The information processing described in the above program is a specific example in which the software related to the program and various hardware resources of the vehicle allocation support system 100 or a part thereof cooperate with each other by reading the program into a computer. It functions as a means. Then, the above-mentioned specific means realizes the calculation or processing of information according to the purpose of use of the computer in the present embodiment, thereby constructing the vehicle allocation support system 100 according to the purpose of use.

The above program may be a program for causing the computer to function as the user management server 116. The above program may be a program for causing the computer to execute the information processing method in the user management server 116.

The above information processing method may be an operation management method for managing reservations for a first moving body that can be moved according to a user's request. In the above operation management method, for example, a user who uses a second moving body that moves according to a predetermined operation plan specifies a usage plan including a planned disembarkation position that is scheduled to get off from the second moving body. Has stages. The operation management method described above includes, for example, (i) a first detection step of detecting the occurrence of an event that causes a change in the usage plan, at least during the period when the user is using the second moving body, and (ii). ) It has at least one of the second detection steps of detecting the user's current position, at least while the user is using the second moving object. The above operation management method is, for example, (i) the occurrence status of the event detected in the first detection stage, and (ii) the distance from the current position of the user detected in the second detection stage to the planned disembarkation position. Based on at least one, the change probability indicating the degree of possibility that the position where the user gets off the second moving body is changed to the halfway stop position where the second moving body stops before reaching the planned disembarkation position is estimated. Has an estimation stage to do. The above-mentioned operation management method has, for example, an operation determination stage for determining the operation of the first moving body with respect to the intermediate stop position based on the change probability estimated in the estimation stage.

FIG. 3 schematically shows an example of the internal configuration of the transportation management server 112. In the present embodiment, the transportation management server 112 includes an operation plan management unit 320, an operation status management unit 340, and a storage unit 360. In the present embodiment, the storage unit 360 has an operation plan storage unit 362 and an operation status storage unit 364.

In the present embodiment, the operation plan management unit 320 manages each operation plan of one or more trains 102. The operation plan management unit 320 creates an operation plan for each of the one or more trains 102, and stores information indicating the created operation plan in the operation plan storage unit 362. The operation plan management unit 320 changes at least one operation plan of one or more trains 102, and stores information indicating the changed operation plan in the operation plan storage unit 362. The operation plan management unit 320 may respond to inquiries about the operation plan of a specific train 102 from an external information processing device.

In the present embodiment, the operation status management unit 340 manages the operation status of one or more trains 102. The operation status management unit 340 communicates with each of the one or more trains 102 via the communication network 10 and acquires information on the operation status of each train. The operation status management unit 340 stores information on the operation status of each train in the operation status storage unit 364. The operation status management unit 340 may respond to inquiries regarding the operation status of a specific train 102 from an external information processing device.

The storage unit 360 stores various types of information necessary for information processing in at least one of the operation plan management unit 320 and the operation status management unit 340. The storage unit 360 stores various information output from at least one of the operation plan management unit 320 and the operation status management unit 340.

In the present embodiment, the operation plan storage unit 362 stores information indicating each operation plan of one or more trains 102. As described above, the operation plan of each train defines a plurality of stations where the train stops and the scheduled time when the train stops at each station. The operation plan storage unit 362 includes identification information of each train, identification information of each stop station of the train, information indicating the estimated arrival time at each stop station, and information indicating the estimated departure time from each stop station. May be stored in association with each other. The operation plan storage unit 362 includes identification information of each train, information indicating the time, identification information of the stop station where the train arrives or departs at the time, and whether the train departs from the station or at the station. It may be stored in association with information indicating whether or not it will arrive.

In the present embodiment, the operation status storage unit 364 stores information indicating the operation status of one or more trains 102. The operation plan storage unit 362 may store the identification information of each train and the information indicating the operation status of each train in association with each other.

FIG. 4 schematically shows an example of the internal configuration of the vehicle allocation management server 114. In the present embodiment, the vehicle allocation management server 114 includes a request processing unit 420, a vehicle allocation unit 440, and a vehicle status storage unit 460. In the present embodiment, the request processing unit 420 has an extraction request processing unit 422 and a vehicle allocation request processing unit 424.

In the present embodiment, the request processing unit 420 receives various requests from an external information processing device. The request processing unit 420 processes the above request and transmits information indicating the result of the above processing to the information processing apparatus that has transmitted the request.

In the present embodiment, the extraction request processing unit 422 determines, for example, from the user management server 116 whether or not there is an automobile 104 that meets a specific condition, or extracts the number or identification information of the automobile 104 that meets the specific condition. Get a request to do something like that. The above-mentioned specific condition may be a condition that the transportation service for a specific number of people can be provided at a specific time and the distance from the specific position is within a predetermined numerical range. The extraction request processing unit 422 extracts the automobile 104 that meets the above conditions with reference to the vehicle status storage unit 460. The extraction request processing unit 422 responds to the above request based on the extracted information.

In the present embodiment, the vehicle allocation request processing unit 424 acquires, for example, a request for reserving vehicle allocation from the user management server 116. The request for reserving a vehicle allocation may include identification information of the user 20, information indicating the required number of vehicles 104, information indicating a place and time to which the vehicle 104 is directed, and the like. The vehicle allocation request processing unit 424 determines whether or not the above reservation can be accepted with reference to the vehicle status storage unit 460.

When the vehicle allocation request processing unit 424 can accept the above reservation, the vehicle allocation request processing unit 424 transmits information indicating the details of the reservation to the vehicle allocation unit 440. Further, the vehicle allocation request processing unit 424 transmits the information indicating that the reservation has been accepted and the identification information of the reservation to the user management server 116. On the other hand, when the vehicle allocation request processing unit 424 cannot accept the above reservation, the vehicle allocation request processing unit 424 transmits information indicating that the reservation is not accepted to the user management server 116.

The vehicle dispatch request processing unit 424 may acquire a request for canceling the reservation from, for example, the user management server 116. The request to cancel the reservation may include the identification information of the reservation. The vehicle dispatch request processing unit 424 executes, for example, a process for canceling the reservation identified by the above reservation identification information. In addition, the vehicle allocation request processing unit 424 transmits information indicating that the reservation has been canceled to the user management server 116.

The vehicle dispatch request processing unit 424 may execute a process for determining whether or not a charge is incurred due to the cancellation of the reservation, and a process for settling the charge incurred due to the cancellation of the reservation. When a charge is incurred due to the cancellation of the reservation, the vehicle allocation request processing unit 424 may send a message regarding the charge to the user management server 116.

In the present embodiment, when the vehicle allocation request processing unit 424 accepts the reservation, the vehicle allocation unit 440 allocates the reservation to at least one of the one or more automobiles 104 according to the information shown in the above reservation. The vehicle dispatching unit 440 outputs an instruction for moving the automobile 104 to which the reservation is assigned to the position indicated by the reservation. For example, the vehicle dispatching unit 440 transmits the above instruction to the information processing device mounted on the automobile 104 to which the reservation is assigned. The vehicle dispatching unit 440 may transmit the above instruction to the communication terminal used by the driver of the automobile 104 to which the reservation is assigned.

In the present embodiment, the vehicle status storage unit 460 stores at least one of information indicating the current position of each of one or more automobiles 104 and information indicating the operating status. The vehicle status storage unit 460 stores, for example, the identification information of each vehicle, at least one of the information indicating the current position of each vehicle and the information indicating the operating status of each vehicle in association with each other.

FIG. 5 schematically shows an example of the data table 500. The data table 500 may be an example of information stored in the vehicle status storage unit 460. In the present embodiment, the data table 500 stores the vehicle ID 522 of each vehicle, the current position 524 of each vehicle, and the operating status 526 of each vehicle in association with each other.

The current position 524 of each vehicle may be indicated by the position coordinates of the position, or may be indicated by the identification information of the facility existing at the position. The position coordinates may include latitude information and longitude information, and may include latitude information, longitude information and altitude information. The facility identification information may be the name of the facility.

The operating status 526 of each vehicle may include, for example, information regarding the usage status of each vehicle, the destination of each vehicle, and the reservation status of each vehicle. The usage status of each vehicle is "available" indicating that the vehicle is in a state where it can provide transportation services, "in use" indicating that the vehicle is providing transportation services, and the vehicle. Examples include "reserving" indicating that the vehicle is reserved, and "unavailable" indicating that the vehicle is in a state where it cannot provide transportation services for some reason.

The information regarding the reservation status of each vehicle is information indicating the degree of possibility (sometimes referred to as reservation probability) of an event in which the transportation service by the automobile 104 is actually provided without canceling the reservation. May include. The reservation probability can be an index indicating the degree of possibility that the user 20 reserves the dispatch of the automobile 104 at least while the user 20 is using the train 102. The reservation probability is that the station where the user 20 gets off is another station (for example, station SB or) where the train 102 stops from the originally planned stop station (for example, station SD) until the train 102 reaches the planned stop station. It can be an index showing the degree of possibility of being changed to station SC.).

The vehicle allocation management server 114 may be an example of a part of the operation determination unit. The vehicle allocation unit 440 may be an example of a part of the operation determination unit. The reservation probability may be an example of the change probability.

FIG. 6 schematically shows an example of the internal configuration of the user management server 116. In the present embodiment, the user management server 116 includes a request reception unit 620, a screen generation unit 630, an action management unit 640, a vehicle allocation request unit 650, and a storage unit 660. In the present embodiment, the storage unit 660 has a user setting storage unit 662, a schedule storage unit 664, a route storage unit 666, and a user status storage unit 668.

In the present embodiment, the request reception unit 620 receives various requests from the communication terminal 120. The request reception unit 620 transfers the request from the communication terminal 120 to, for example, the behavior management unit 640 or the vehicle allocation request unit 650.

The above request requests, for example, the use of a service for managing a schedule. The above request may request the use of a service to search for a route from the origin to the destination. The above request may request the registration of the travel route of the user 20. The above request may request the use of a service for booking a ride. In the service for reserving a vehicle allocation, for example, functions such as reservation for vehicle allocation, execution of vehicle allocation, and cancellation of reservation are realized. These services may be provided by the user management server 116, and at least a part of these services may be provided by an information processing device different from the user management server 116. At least a part of the above services may be provided by an information processing device external to the vehicle allocation support system 100.

In the present embodiment, the screen generation unit 630 generates various screens that serve as a user interface of the vehicle allocation support system 100. As the above screens, the input screen and confirmation screen in the service for managing the schedule, the input screen and confirmation screen in the service for searching the route to move from the departure place to the destination, and the movement route of the user 20 are registered. A screen for confirming a registered movement route, an input screen and a confirmation screen for a service for reserving vehicle allocation, a screen for registering settings specific to the user 20, and the like are exemplified.

In the present embodiment, the behavior management unit 640 manages each behavior of one or more users 20. Specifically, the behavior management unit 640 specifies the usage plan of the train 102 by each user.

The usage plan of the train 102 by each user includes, for example, information indicating a station where the user plans to get off the train 102. The use plan of the train 102 by each user may prescribe the identification information of the train 102 used by the user and the information indicating the station where the user plans to get off the train 102.

The behavior management unit 640 may, for example, transmit information indicating a usage plan of the train 102 by the specific user 20 to the vehicle allocation request unit 650 in response to a request from the vehicle allocation request unit 650. Details of the behavior management unit 640 will be described later.

In the present embodiment, the vehicle allocation request unit 650 determines whether or not to reserve the vehicle allocation of the automobile 104 according to the situation of the user 20. Specifically, whether or not the vehicle allocation request unit 650 reserves the allocation of the vehicle 104 based on the presence / absence of the disembarkation triggering event, the occurrence pattern of the disembarkation triggering event, and at least one of the current positions of the user 20. To decide. The vehicle allocation request unit 650 may decide whether or not to reserve the vehicle allocation of the automobile 104 based on the instruction from the user 20.

When it is decided to reserve the dispatch of the automobile 104, the vehicle allocation request unit 650 executes the vehicle allocation reservation process. Specifically, the vehicle allocation request unit 650 transmits a request for reserving the vehicle allocation to the vehicle allocation management server 114.

In the present embodiment, the vehicle allocation requesting unit 650 determines whether or not to cancel the reservation regarding the vehicle allocation of the automobile 104 according to the situation of the user 20. Specifically, the vehicle allocation request unit 650 determines whether or not to cancel the reservation based on the presence / absence of the disembarkation triggering event, the occurrence pattern of the disembarkation triggering event, and at least one of the current positions of the user 20. .. The vehicle dispatch request unit 650 may decide whether or not to cancel the reservation based on the instruction from the user 20.

If it is decided to cancel the reservation, the vehicle allocation request unit 650 executes the reservation cancellation process. Specifically, the vehicle allocation request unit 650 transmits a request for canceling the reservation to the vehicle allocation management server 114. Details of the vehicle dispatch request unit 650 will be described later.

The storage unit 660 stores various information necessary for information processing in each unit of the user management server 116. The storage unit 660 stores various information output from each unit of the user management server 116.

The user setting storage unit 662 stores information indicating settings specific to the user for each of the one or more users 20. The above settings include home address, work address, holiday address, route selection policy, fee settlement method, currency or electronic value account information, credit card number, reservation The policy regarding the cancellation of the ticket, the setting regarding the detection of the disembarkation trigger event, etc. are exemplified.

The schedule storage unit 664 stores information indicating the schedule of one or more users 20 for each of the users 20. The schedule may include information indicating the title of the event in which the user participates, the duration or time of the event, and the location of the event.

The route storage unit 666 stores information indicating the movement route of the user for each of the one or more users 20. The travel route of the user 20 may include a section in which the user 20 travels by using the train 102. The section in which the user 20 travels by using the train 102 may be composed of one or a plurality of traveling sections. Each traveling section may be a section in which the train 102 travels from one stop station to the next stop station. The travel route may include information indicating the station where the user 20 plans to board the train 102 and the station where the user 20 plans to get off the train 102.

The user status storage unit 668 stores information indicating the situation in which the user is placed for each of the one or more users 20. For example, the user status storage unit 668 stores information indicating the current position of the user for each of one or more users 20. The user status storage unit 668 may store information indicating the movement history of the user for each of one or more users 20.

The user status storage unit 668 may store information about a disembarkation trigger event related to the user for each of the one or more users 20. Examples of information on the disembarkation trigger event include the presence or absence of a disembarkation triggering event on the current travel route, the type of disembarkation triggering event that occurred on the current travel route, and the occurrence pattern of the disembarkation triggering event. Will be done. The user status storage unit 668 may store information about a disembarkation trigger event on a past travel route for each of one or more users 20.

The behavior management unit 640 may be an example of a specific unit. The vehicle allocation request unit 650 may be an example of a first detection unit, a second detection unit, and an estimation unit. Each of the planned disembarkation stations of each user may be an example of the planned disembarkation position.

FIG. 7 schematically shows an example of the internal configuration of the behavior management unit 640. In the present embodiment, the behavior management unit 640 includes a schedule management unit 742, a route search unit 744, and a route registration unit 746.

In the present embodiment, the schedule management unit 742 provides each user with a service for managing the schedule of the user. The schedule management unit 742 acquires a request from the request reception unit 620 indicating that the user 20 wants to use the service for managing the schedule. The schedule management unit 742 acquires information about the schedule of the user 20 via, for example, an input screen or a confirmation screen generated by the screen generation unit 630. As a result, the schedule management unit 742 can specify the usage plan of the train 102 by the user 20.

For example, the schedule management unit 742 determines whether or not the departure place is the home of the user 20 from the input event holding time. When it is determined that the departure place is the home of the user 20, the schedule management unit 742 searches for a route from the home of the user 20 to the venue of the event, and holds the event from the nearest station of the home. It is possible to identify the travel route to the nearest station of the place. When a plurality of candidates are extracted as the movement route of the user 20, the schedule management unit 742 may specify the movement route of the user 20 based on the route selection policy stored in the user setting storage unit 662. The schedule management unit 742 may store information indicating the usage plan of the specified train 102 in the user status storage unit 668.

In the present embodiment, the route search unit 744 provides a service for searching for a route moving from a departure place to a destination. The route search unit 744 acquires a request from the request reception unit 620 indicating that the user 20 wants to use the service for searching the route. The route search unit 744 acquires information on the departure point and the destination of the user 20 via, for example, the input screen or the confirmation screen generated by the screen generation unit 630. As a result, the route search unit 744 can specify the usage plan of the train 102 by the user 20. When a plurality of candidates are extracted as the travel route of the user 20, the route search unit 744 may specify the travel route of the user 20 based on the route selection policy stored in the user setting storage unit 662. The route search unit 744 may store information indicating the usage plan of the specified train 102 in the user status storage unit 668.

In the present embodiment, the route registration unit 746 acquires a request from the request reception unit 620 indicating that the user 20 wants to register the travel route. The route registration unit 746 acquires information about the travel route of the user 20 via, for example, an input screen or a confirmation screen generated by the screen generation unit 630. As a result, the route registration unit 746 can specify the usage plan of the train 102 by the user 20. The route registration unit 746 may store information indicating the usage plan of the specified train 102 in the user status storage unit 668.

The schedule management unit 742 may be an example of a specific unit. The route search unit 744 may be an example of a specific unit. The route registration unit 746 may be an example of a specific unit.

FIG. 8 schematically shows an example of the internal configuration of the vehicle allocation request unit 650. In the present embodiment, the vehicle allocation request unit 650 includes an event detection unit 822, a user position estimation unit 824, and a reservation probability estimation unit 826. In the present embodiment, the vehicle allocation request unit 650 includes a request generation unit 832, a deadline determination unit 834, and an instruction confirmation unit 836.

In the present embodiment, the event detection unit 822 detects the occurrence of a predetermined type of event. The event detection unit 822 may detect the occurrence of a predetermined type of event at least while the user 20 is using the train 102. Examples of the above-mentioned event include (i) a disembarkation triggering event, (ii) the user 20 disembarking from the train 102, and the like.

In one embodiment, the event detection unit 822 acquires vital information of the user 20 or the companion 22 from the communication terminal 120 of the user 20. The event detection unit 822 analyzes the above vital information and detects the occurrence of a disembarkation trigger event. Thereby, for example, the occurrence of a disembarkation-inducing event such as poor physical condition of the user 20 or the companion 22 and whether or not the child who is the companion 22 is crying can be detected.

In another embodiment, the event detection unit 822 acquires ambient voice information from the communication terminal 120 of the user 20. The event detection unit 822 analyzes the above voice information and detects the occurrence of a disembarkation trigger event. Thereby, for example, the occurrence of a disembarkation-inducing event such as whether or not other passengers are uncomfortable and whether or not the child who is the companion 22 is crying can be detected.

In another embodiment, the event detection unit 822 acquires ambient voice information from the communication terminal 120 of the user 20. The event detection unit 822 analyzes the above voice information and detects that the user 20 has disembarked from the train 102.

In still another embodiment, the event detection unit 822 acquires output data of at least one of the acceleration sensor and the gyro sensor from the communication terminal 120 of the user 20. The event detection unit 822 analyzes the above output data and detects that the user 20 has disembarked from the train 102.

If a disembarkation trigger event is detected, the user 20's plan to use the train 102 may be changed. In this case, the user management server 116 may receive a vehicle allocation instruction from the communication terminal 120 of the user 20. Therefore, when a disembarkation triggering event is detected, the event detection unit 822 transmits, for example, information indicating that the disembarkation triggering event has been detected to the reservation probability estimation unit 826.

Further, when it is detected that the user 20 gets off the train 102 at the station where the automobile 104 is dispatched, the possibility that the user 20 actually uses the automobile 104 increases. On the other hand, if it is not detected that the user 20 has disembarked from the train 102 at the station where the car 104 is dispatched, the possibility that the user 20 actually uses the car 104 is reduced. In this case, the user management server 116 needs to cancel the reservation of the automobile 104. Therefore, when it is detected that the user 20 has disembarked from the train 102, the event detection unit 822 transmits, for example, information indicating that the user 20 has disembarked from the train 102 to the request generation unit 832.

In this embodiment, the user position estimation unit 824 detects the current position of the user 20. The user position estimation unit 824 may detect the current position of the user 20 at least while the user 20 is using the train 102.

In one embodiment, the user position estimation unit 824 may specify the movement route of the user 20 by referring to the information stored in the route storage unit 666. The user position estimation unit 824 may detect the current position of the user 20 based on the current time and the movement route of the user 20.

In another embodiment, the user position estimation unit 824 may inquire of the operation status management unit 340 of the transportation management server 112 about the current operation status of the train 102 on which the user 20 is riding. The user position estimation unit 824 may detect the current position of the user 20 based on the current time, the movement route of the user 20, and the current operating status of the train 102 on which the user 20 is riding.

In the present embodiment, the reservation probability estimation unit 826 estimates the reservation probability indicating the degree of possibility that the user 20 reserves the dispatch of the automobile 104 at least while the user 20 is using the train 102. For example, when the user management server 116 executes the vehicle allocation reservation process prior to the vehicle allocation instruction from the user 20, the user management server 116 receives the formal vehicle allocation instruction from the user 20 within a predetermined period. If not, the above reservation will be cancelled. In consideration of such a case, as described above, the reservation probability may indicate the degree of possibility of an event in which the transportation service by the automobile 104 is actually provided without canceling the reservation.

The reservation probability may be an index indicating the degree of possibility that the user 20's usage plan of the train 102 is changed at least during the period when the user 20 is using the train 102. The reservation probability is distributed between the station where the user 20 boarded the train 102 and the station where the user 20 originally planned to get off the train 102 (sometimes referred to as a scheduled disembarkation station). It may be an index indicating the degree of possibility that the user 20 gets off the train 102 (sometimes referred to as a disembarkation probability) at at least one of the one or more other stations. The disembarkation probability is that the disembarkation station of the user 20 stops from the originally planned disembarkation station (for example, station SD) until the train 102 reaches the planned disembarkation station (for example, station SB or station SB). It can be an index showing the degree of possibility of being changed to a station SC (sometimes referred to as a stop on the way).

The reservation probability estimation unit 826 is based on, for example, (i) the occurrence status of the disembarkation trigger event related to the user 20 detected by the event detection unit 822, and (ii) the current position of the user 20 detected by the user position estimation unit 824. The above disembarkation probability is estimated based on at least one of the distances to the planned disembarkation station. The reservation probability estimation unit 826 may regard the estimated disembarkation probability as the reservation probability.

The reservation probability estimation unit 826 may estimate the reservation probability for at least one of the one or more stations arranged between the current position of the user 20 and the scheduled stop station. The reservation probability estimation unit 826 may estimate the reservation probability for all stations arranged between the current position of the user 20 and the scheduled disembarkation station. The reservation probability estimation unit 826 may use the disembarkation probability at each station as the reservation probability at each station.

[Procedure for estimating the disembarkation probability based on the occurrence of disembarkation trigger events]
In one embodiment, the reservation probability estimation unit 826 increases the disembarkation probability as the number or frequency of the event detection unit 822 detecting the disembarkation triggering event during the period when the user 20 is using the train 102. , Estimate the disembarkation probability. The frequency may be the number of times in a unit period having a particular length. The frequency may be the number of times between stops.

The length of the unit period is not particularly limited. The length of the unit period may be determined based on the statistics of the time required between the stations. Examples of statistics include maximum value, minimum value, average value, and most frequent value. The length of the unit period may be less than the minimum required time between stations. The length of the unit period may be less than or equal to half of the minimum value of the required time between stations, and may be less than half of the minimum value. The length of the unit period may be 30 seconds, 1 minute, 2 minutes, 3 minutes, 5 minutes, or 10 minutes. It may be 15 minutes, 30 minutes, 1 hour, 2 hours, or 3 hours.

For example, the reservation probability estimation unit 826 uses the cumulative value of the number of times the disembarkation triggering event is detected while the user 20 is using the train 102 as an explanatory variable, and determines the disembarkation probability at the stop station after the next stop station. Estimate the disembarkation probability at each stop using a table, function, or estimation model as the objective variable. The reservation probability estimation unit 826 uses the cumulative value of the number of times the disembarkation trigger event is detected while the user 20 is using the train 102 and the time required to reach the stop station where the disembarkation probability is calculated as explanatory variables. , The disembarkation probability at each stop station may be estimated by using a table, a function or an estimation model having the disembarkation probability at the stop stations after the next stop station as the objective variable.

For example, the reservation probability estimation unit 826 uses the number of times a disembarkation trigger event is detected after the train 102 departs from the immediately preceding stop station as an explanatory variable, and the disembarkation probability at a stop station after the next stop as an objective variable. Estimate the probability of getting off at each stop using a table, function or estimation model. The reservation probability estimation unit 826 uses the number of times the disembarkation trigger event is detected after the train 102 departs from the immediately preceding stop station and the time required to reach the stop station where the disembarkation probability is calculated as explanatory variables, and sets the next stop. The disembarkation probability at each stop station may be estimated by using a table, a function, or an estimation model in which the disembarkation probability at a stop station after the station is used as an objective variable.

For example, the reservation probability estimation unit 826 uses the history of the frequency at which a disembarkation triggering event is detected during the period when the user 20 is using the train 102 as an explanatory variable, and aims at the disembarkation probability at a stop station after the next stop station. Estimate the probability of getting off at each stop using a table, function, or estimation model as variables. The reservation probability estimation unit 826 uses the history of the frequency at which the disembarkation trigger event is detected during the period when the user 20 is using the train 102 and the time required to reach the stop station where the disembarkation probability is calculated as explanatory variables. The disembarkation probability at each stop station may be estimated by using a table, a function, or an estimation model whose objective variable is the disembarkation probability at the stop stations after the next stop station.

For example, the reservation probability estimation unit 826 uses the cumulative value of the length of the period during which the frequency of detecting the disembarkation trigger event exceeds the reference value during the period when the user 20 is using the train 102 as an explanatory variable, and uses the following as an explanatory variable. The disembarkation probability at each stop station is estimated by using a table, function, or estimation model whose objective variable is the disembarkation probability at the stop stations after the stop station. The reservation probability estimation unit 826 calculates the cumulative value of the period during which the frequency of detecting the disembarkation trigger event exceeds the reference value during the period when the user 20 is using the train 102, and the stop for which the disembarkation probability is calculated. You may estimate the probability of getting off at each stop using a table, function, or estimation model that uses the time required to reach the station as the explanatory variable and the probability of getting off at the stations after the next stop as the objective variable. .. The length of the period during which the frequency of detection of the disembarkation trigger event exceeds the reference value is, for example, the product of the number of unit periods in which the frequency of detection of the disembarkation trigger event exceeds the reference value and the length of the unit period. It is calculated.

For example, the reservation probability estimation unit 826 uses the length of the period during which the frequency at which the disembarkation triggering event is detected exceeds the reference value after the train 102 departs from the immediately preceding stop station as an explanatory variable, and after the next stop station. The disembarkation probability at each stop station is estimated by using a table, function, or estimation model whose objective variable is the disembarkation probability at the stop station. The reservation probability estimation unit 826 determines the length of the period during which the frequency at which the disembarkation trigger event is detected exceeds the reference value after the train 102 departs from the immediately preceding stop station, and the time required to reach the stop station where the disembarkation probability is calculated. The disembarkation probability at each stop station may be estimated by using a table, a function, or an estimation model in which the above is an explanatory variable and the disembarkation probability at a stop station after the next stop station is an objective variable.

[Probability of getting off based on the current position of user 20]
In other embodiments, the user 20 may have different ideas about getting off the train, depending on the remaining time or distance to the destination. Therefore, in the present embodiment, the reservation probability estimation unit 826 estimates the disembarkation probability based on the distance from the current position of the user 20 detected by the user position estimation unit 824 to the planned disembarkation station. For example, the reservation probability estimation unit 826 estimates the disembarkation probability so that the shorter the distance from the current position of the user 20 detected by the user position estimation unit 824 to the planned disembarkation station, the smaller the disembarkation probability. The above distance may be a straight line distance or a distance along the route of the train 102.

[Another example of the procedure for estimating the probability of getting off]
In still another embodiment, when the disembarkation triggering event occurs for the first time during the period when the user 20 is using the train 102, and when the disembarkation triggering event has occurred in the past, the disembarkation of the user 20 is determined. The idea may be different. Therefore, in the present embodiment, the reservation probability estimation unit 826 estimates the disembarkation probability based on the detection history of the disembarkation triggering event.

For example, consider a case where a station SX and a station SY are arranged between a station SS on which the user 20 boarded the train 102 and a scheduled disembarkation station SG. The distance between the station SY and the station SS shall be smaller than the distance between the station SX and the station SS. In this case, the reservation probability estimation unit 826 (i) the event detection unit 822 detects the disembarkation trigger event while the train 102 is operating between the station SS and the station SY, and the train 102 is the station. The disembarkation probability when the event detection unit 822 detects a disembarkation-inducing event during the period of operation between SY and station SX is (ii) the period during which train 102 is operating between station SS and station SY. In addition, the disembarkation probability when the event detection unit 822 does not detect the disembarkation triggering event and the event detection unit 822 detects the disembarkation triggering event during the period when the train 102 is operating between the station SY and the station SX. Estimate the disembarkation probability so that it becomes larger than.

In the present embodiment, the request generation unit 832 determines whether or not to execute the vehicle allocation process of the automobile 104 based on the reservation probability estimated by the reservation probability estimation unit 826. Specifically, the request generation unit 832 determines whether or not to reserve the use of the automobile 104 based on the reservation probability estimated by the reservation probability estimation unit 826. The request generation unit 832 may decide to reserve the use of the automobile 104 when the above reservation probability satisfies a predetermined condition. Examples of the predetermined conditions include a condition that the reservation probability is larger than a predetermined value, a condition that the reservation probability falls within a predetermined numerical range, and the like.

The request generation unit 832 may total the reservation probabilities of one or more users 20 at the stop station for each stop station of the train 102. The request generation unit 832 may decide whether or not to reserve the use of the automobile 104 based on the aggregated value of the reservation probability described above. For example, when there are eight users 20 who may use the automobile 104 at the station SB and the total value of the reservation probabilities of the eight users 20 at the station SB is 325%, the request generation unit 832 has 3 Decide to reserve the use of one or four cars 104.

When it is decided to reserve the use of the automobile 104, the request generation unit 832 executes the reservation process of the automobile 104. In the specific period, the request generation unit 832 generates a request for reserving the vehicle allocation and transmits the request to the vehicle allocation management server 114. The request generation unit 832 may generate a request including, for example, the identification information of the user 20, the identification information of the station where the user 20 uses the automobile 104, and the information indicating the time when the user 20 arrives at the station. ..

In the present embodiment, the request generation unit 832 determines whether or not to cancel the above reservation. In one embodiment, after the reservation process is executed, the request generation unit 832 uses (i) from the communication terminal 120 of the user 20 to the automobile 104 while the user 20 is using the train 102. If the information indicating that the user wants to use the vehicle is not received, or (ii) the information indicating that the user 20 does not want to use the automobile 104 is received from the communication terminal 120 of the user 20. Decide to cancel the reservation.

In another embodiment, the request generation unit 832 may decide whether or not to cancel the reservation based on the reservation probability estimated by the reservation probability estimation unit 826. The request generation unit 832 may decide to cancel the reservation when the above reservation probability satisfies a predetermined condition. Examples of the predetermined conditions include a condition that the reservation probability is smaller than a predetermined value, a condition that the reservation probability does not fall within the predetermined numerical range, and the like. The threshold or numerical range in the condition for canceling a reservation may be the same as or different from the threshold or numerical range in the condition for reservation.

When it is decided to cancel the above reservation, the request generation unit 832 executes the reservation cancellation process. In the specific period, the request generation unit 832 generates a request for canceling the reservation and transmits the request to the vehicle allocation management server 114. The request generation unit 832 may generate, for example, a request including identification information of a reservation to be canceled.

In the present embodiment, the deadline determination unit 834 determines a deadline (sometimes referred to as a reservation deadline) in which the user management server 116 can accept a reservation request for allocating the automobile 104 to a specific station. To do. In one embodiment, the deadline determination unit 834 determines the reservation deadline so that the period between the estimated time of arrival of the train 102 at a specific station and the reservation deadline is a predetermined value. In another embodiment, the deadline determination unit 834 makes a reservation so that the larger the reservation probability of the user 20 at a specific station, the shorter the estimated time of arrival of the train 102 at the specific station and the reservation deadline. Determine the deadline. In another embodiment, the deadline determination unit 834 determines that the estimated time of arrival of the train 102 at a specific station and the reservation deadline are the larger the aggregated value of the estimated probability of reservation of one or more users 20 at a specific station. Determine the reservation deadline so that the period of

The deadline determination unit 834 determines a deadline (sometimes referred to as a cancellation deadline) in which the user management server 116 can accept a cancellation request for canceling a reservation for dispatching a car 104 to a specific station. You may. In one embodiment, the deadline determination unit 834 determines the cancellation deadline so that the period between the estimated time of arrival of the train 102 at a specific station and the cancellation deadline is a predetermined value. In another embodiment, the deadline determination unit 834 cancels so that the larger the reservation probability of the user 20 at a specific station, the shorter the period between the estimated time of arrival of the train 102 at the specific station and the cancellation deadline. Determine the deadline. In another embodiment, the deadline determination unit 834 determines that the larger the aggregated value of the estimated probability of reservation of one or more users 20 at a specific station, the more the estimated time of arrival of the train 102 at the specific station and the cancellation deadline. Determine the cancellation deadline so that the period of

In the present embodiment, the instruction confirmation unit 836 confirms the instruction of the user 20 regarding whether or not to reserve the use of the automobile 104 at a specific station. In one embodiment, the instruction confirmation unit 836 controls the screen generation unit 630 to generate a screen (sometimes referred to as a reservation confirmation screen) for confirming the necessity of reservation. The instruction confirmation unit 836 transmits the data of the reservation confirmation screen to the communication terminal 120 of the user 20. In another embodiment, the instruction confirmation unit 836 may transmit a command for outputting the reservation confirmation screen to the communication terminal 120 of the user 20. The instruction confirmation unit 836 may confirm the instruction of the user 20 regarding the reservation for the use of the automobile 104 by receiving the information indicating that the user 20 requests the above reservation from the communication terminal 120.

When the instruction confirmation unit 836 receives information from the communication terminal 120 indicating that the user 20 requests the above reservation, the instruction confirmation unit 836 makes a reservation for the use of the automobile 104 at a specific station by the user 20. Information indicating that the request is being made may be transmitted to the request generation unit 832. On the other hand, if the instruction confirmation unit 836 cannot receive the information indicating that the user 20 requests the above reservation even after a predetermined time has elapsed after the reservation confirmation screen is transmitted, the instruction confirmation unit 836 is the instruction confirmation unit. The 836 may transmit information to the request generation unit 832 indicating that the user 20 has not requested the reservation for the use of the automobile 104 at a specific station.

The instruction confirmation unit 836 may confirm the instruction of the user 20 regarding whether or not to cancel the reservation regarding the use of the automobile 104 at a specific station. The instruction confirmation unit 836 controls, for example, the screen generation unit 630 to generate a screen (sometimes referred to as a cancellation confirmation screen) for confirming the necessity of canceling the reservation. The instruction confirmation unit 836 transmits the data of the cancellation confirmation screen to the communication terminal 120 of the user 20. The instruction confirmation unit 836 confirms the instruction of the user 20 regarding the cancellation of the reservation by receiving the information indicating that the user 20 requests the cancellation of the reservation from the communication terminal 120.

When the instruction confirmation unit 836 receives information from the communication terminal 120 indicating that the user 20 requests the cancellation of the above reservation, the instruction confirmation unit 836 requests the user 20 to cancel the reservation for a specific station. Information indicating that this is done may be transmitted to the request generation unit 832. On the other hand, the instruction confirmation unit 836 gives an instruction when the user 20 cannot receive the information indicating that the reservation is requested to be canceled even after a predetermined time has elapsed after the cancellation confirmation screen is transmitted. The confirmation unit 836 may transmit information to the request generation unit 832 indicating that the user 20 has not requested the cancellation of the reservation for a specific station.

The event detection unit 822 may be an example of the first detection unit. The user position estimation unit 824 may be an example of a specific unit and a second detection unit. The reservation probability estimation unit 826 may be an example of the estimation unit. The reservation confirmation screen may be an example of a message for inquiring whether or not the user wishes to use the first mobile body.

The scheduled stop station may be an example of the planned stop position. Each of the station where the user 20 boarded the train 102 and one or more other stations arranged between the scheduled disembarkation station may be an example of the intermediate stop position. The station SG may be an example of a planned disembarkation position. Station SX and station SY may be examples of stopover positions. The station SX may be an example of the first stop position. The station SY may be an example of the second stop position. The period during which the train 102 operates between the station SS and the station SY may be an example of the period until the second moving body reaches the second intermediate stop position. The period during which the train 102 operates between the station SY and the station SX is an example of the period after the second moving body reaches the second stop position and until it reaches the first stop position. You can.

FIG. 9 schematically shows an example of the data table 900. The data table 900 shows the output result of the process of estimating the reservation probability of a specific user. In the present embodiment, the data table 900 stores the user ID 922, the event detection frequency 924, and the reservation probability 926 in association with each other. In the present embodiment, the event detection frequency 924 records the number of times a disembarkation trigger event is detected in each section on the movement route of the train 102. In the present embodiment, the reservation probability 926 records an estimated value of the reservation probability at each station on the movement route of the train 102.

FIG. 10 schematically shows an example of the data table 1000. The data table 1000 shows the output result of the process of totaling the estimated value of the reservation probability at a specific station. In the present embodiment, the data table 1000 stores the station name 1022 and the reservation probability 1024 for each station in association with each other. In the present embodiment, the reservation probability 1024 for each station includes the identification information of one or more users 20 who may use the automobile 104 at the specific station, and the estimated value of the reservation probability of the user. The associated information is recorded. In the reservation probability 1024 for each station, the aggregated value of the estimated value of the reservation probability may be recorded.

FIG. 11 schematically shows an example of the screen 1100. The screen 1100 may be an example of a reservation confirmation screen. In the present embodiment, the screen 1100 includes a data table 1120, a plurality of reservation buttons 1142, and a plurality of cancel buttons 1144. In the present embodiment, the data table 1120 shows that (i) the station name 1122 of the station where the train 102 stops on the travel route of the user 20, and (ii) the reserved automobile 104 arrives after the user 20 arrives at the station. Waiting time 1124, (iii) estimated time of arrival of train 102 to the station 1126, (iv) estimated time of arrival to destination 1128 when using car 104 from the station, and (v) The reservation deadline 1132 and (vi) cancellation order acceptance deadline 1134 are stored in association with each other.

In this embodiment, each of the plurality of reservation buttons 1142 and the plurality of cancel buttons 1144 correspond to each row (sometimes referred to as a record) of the data table 1120. When the user 20 clicks the reservation button 1142 on the screen of the communication terminal 120, the reservation process for the record corresponding to the clicked reservation button 1142 is executed, and the reservation instruction is output. The reservation instruction may be an instruction from the user 20 and may be information indicating that the user 20 desires to reserve the automobile 104.

Similarly, when the user 20 clicks the cancel button 1144 on the screen of the communication terminal 120, the cancel process for the record corresponding to the clicked cancel button 1144 is executed, and the cancel instruction is output. The cancellation instruction may be an instruction from the user 20 and may be information indicating that the user 20 desires to cancel the reservation of the automobile 104.

In the present embodiment, the screen 1100 is a screen for the user 20 to request a reservation for using the automobile 104. Therefore, according to the present embodiment, on the screen 1100, the cancel button 1144 is invalidated so that the cancel process is not executed even if the cancel button 1144 is clicked. It is also designed so that the cancel button 1144 can be seen to be disabled on the screen. Specifically, at least one of the shapes, patterns and colors of the cancel button 1144 is determined to indicate the disabled button.

The reservation instruction may be an example of a vehicle allocation instruction. The cancellation instruction may be an example of information indicating that the user 20 does not want to use the automobile 104.

FIG. 12 schematically shows an example of the screen 1200. The screen 1200 may be an example of a cancellation confirmation screen. The screen 1200 differs from the screen 1100 in that at least one of the shapes, patterns, and colors of the reserved record differs from at least one of the shapes, patterns, and colors of the other records. Further, the screen 1200 is different from the screen 1100 in that the reservation button 1142 corresponding to the reserved record is disabled and the cancel button 1144 corresponding to the reserved record is enabled. With respect to features other than the above differences, the screen 1200 may have the same configuration as the screen 1100.

An example of an embodiment of information processing in the vehicle allocation support system 100 is schematically shown with reference to FIGS. 13, 14 and 15. FIG. 13 schematically shows an example of information processing in the vehicle allocation support system 100. FIG. 14 is a drawing for explaining a part of information processing in FIG. 13 in detail. FIG. 15 schematically shows an example of another embodiment of information processing in the vehicle allocation support system 100. According to the present embodiment, the details of the information processing in the vehicle allocation support system 100 will be described by taking as an example the case where the disembarkation probability of the user 20 is used as the reservation probability of the user 20. However, it should be noted that the information processing in the vehicle allocation support system 100 is not limited to this embodiment.

FIG. 13 schematically shows an example of information processing in the user management server 116 or the vehicle allocation request unit 650, for example. According to the present embodiment, first, in step 1322 (step may be abbreviated as S), the user management server 116 determines the necessity of reservation processing related to the allocation of the automobile 104.

For example, the user management server 116 calculates the disembarkation probability of the user 20 at an arbitrary timing. When the calculated disembarkation probability satisfies a predetermined condition, the user management server 116 may determine that the above reservation process is necessary. If the disembarkation probability does not satisfy a predetermined condition, the user management server 116 may determine that the reservation process is unnecessary. Details of the above determination process will be described later with reference to FIG.

When it is determined that the above reservation process is unnecessary (No in S1324), for example, the process of S1322 is repeated. The process of S1322 may be executed periodically.

On the other hand, when it is determined that the above reservation process is necessary (Yes in S1324), the user management server 116 executes the reservation process. Specifically, in S1332, the request generation unit 832 of the vehicle allocation request unit 650 generates a request for reserving the use of the automobile 104, and transmits the request to the vehicle allocation management server 114.

More specifically, for example, first, the reservation probability estimation unit 826 calculates the reservation probability for all the stops on the movement route of the user 20. Next, when the reservation probability of the next stop station is larger than a predetermined threshold value and the reservation deadline has not passed, the request generation unit 832 uses the vehicle 104 by the user 20 at the next stop station. A request for reserving the use of is transmitted to the vehicle allocation management server 114. Upon receiving the above request, the vehicle allocation management server 114 executes a process for allocating the vehicle 104 to the next stop station of the train 102 on which the user 20 is riding.

In the present embodiment, the request generation unit 832 transmits a request for allocating the automobile 104 to the next stop station to the vehicle allocation management server 114. However, the reservation method or the vehicle allocation method of the automobile 104 is not limited to this embodiment. In another embodiment, the request generation unit 832 reserves the use of the automobile 104 at the planned stop station and one or more intermediate stop stations for all stations whose reservation probability is larger than a predetermined threshold value. The request for this may be transmitted to the vehicle allocation management server 114. Upon receiving the above request, the vehicle allocation management server 114 executes a process for allocating the automobile 104 to all the stations designated by the request.

According to the reservation process according to the present embodiment, next, in S1334, the instruction confirmation unit 836 of the vehicle allocation request unit 650 generates a reservation confirmation screen using the estimation result of the reservation probability estimation unit 826 of the vehicle allocation request unit 650. Then, the reservation confirmation screen is transmitted to the communication terminal 120 of the user 20. After transmitting the reservation confirmation screen, the instruction confirmation unit 836 may wait for the reservation instruction from the communication terminal 120 of the user 20. As a result, the instruction confirmation unit 836 can acquire the instruction from the user 20 via the communication terminal 120 of the user 20.

In S1340, when the instruction confirmation unit 836 receives the reservation instruction from the communication terminal 120 of the user 20 before the reservation deadline has passed (Yes in S1340), the instruction confirmation unit 836 has the remaining period until the cancellation deadline. Waits until is less than a predetermined value. Next, in S1352, when the remaining period until the cancellation deadline becomes smaller than the predetermined value, the instruction confirmation unit 836 transmits a message indicating that the cancellation deadline is approaching to the communication terminal 120 of the user 20. .. The above message may include the URI of the cancellation confirmation screen. The instruction confirmation unit 836 may send a cancellation confirmation screen on which a message indicating that the cancellation deadline is approaching is approaching to the communication terminal 120 of the user 20.

Next, in S1354, when the instruction confirmation unit 836 receives the cancellation instruction from the communication terminal 120 of the user 20 before the cancellation deadline has passed (Yes in S1354), the instruction confirmation unit 836 cancels the user 20. The instruction is transmitted to the request generation unit 832. In S1370, the request generation unit 832 transmits a request for canceling the reservation to the vehicle allocation management server 114. On the other hand, in S1354, if the instruction confirmation unit 836 does not receive the cancellation instruction from the communication terminal 120 of the user 20 before the cancellation deadline has passed (No in S1354), the vehicle allocation request unit 650 ends the process. To do.

On the other hand, in S1340, when the instruction confirmation unit 836 does not receive the reservation instruction from the communication terminal 120 of the user 20 before the reservation deadline has passed (No of S1340), the instruction confirmation unit 836 has the reservation deadline. Wait until the remaining period until becomes smaller than the predetermined value. Next, in S1362, when the remaining period until the reservation deadline becomes smaller than the predetermined value, the instruction confirmation unit 836 transmits a message indicating that the reservation deadline is approaching to the communication terminal 120 of the user 20. .. The above message may include the URI of the reservation confirmation screen. The instruction confirmation unit 836 may send a reservation confirmation screen on which a message indicating that the reservation deadline is approaching is approaching to the communication terminal 120 of the user 20.

Next, in S1364, when the instruction confirmation unit 836 does not receive the reservation instruction from the communication terminal 120 of the user 20 before the reservation deadline has passed (No of S1364), the instruction confirmation unit 836 has the reservation deadline. Information indicating that the reservation instruction of the user 20 has not been obtained by this time is transmitted to the request generation unit 832. In S1370, the request generation unit 832 transmits a request for canceling the reservation to the vehicle allocation management server 114. On the other hand, in S1364, when the instruction confirmation unit 836 receives the reservation instruction from the communication terminal 120 of the user 20 before the reservation deadline has passed (Yes in S1364), the vehicle allocation request unit 650 ends the process.

FIG. 14 schematically shows an example of information processing in the determination process of S1322. According to the present embodiment, first, in S1422, for example, the user position estimation unit 824 of the vehicle allocation request unit 650 determines whether or not the user 20 is on the train 102. In one embodiment, the user position estimation unit 824 determines whether or not the user 20 is on the train 102 based on the movement history of the user 20. In another embodiment, the user position estimation unit 824 determines whether or not the user 20 is on the train 102 based on the current time and the travel route of the user 20.

When it is determined that the user 20 is not on the train (No in S1422), for example, the process of S1422 is repeated. The process of S1422 may be executed periodically.

On the other hand, when it is determined that the user 20 is on the train (Yes in S1422), in S1424, the user position estimation unit 824 specifies the usage plan of the train 102 by the user 20. For example, the user position estimation unit 824 refers to the information stored in the route storage unit 666, and the user position estimation unit 824 acquires information indicating the usage plan of the user 20. As a result, the user position estimation unit 824 can specify the movement route of the user 20. The user position estimation unit 824 may specify at least the planned stop station of the user 20 and the intermediate stop station of the train 102 on which the user 20 is boarding. The user position estimation unit 824 may specify the scheduled arrival time of the train 102 at each of the scheduled stop station of the user 20 and the above-mentioned intermediate stop station.

As described above, the event detection unit 822 analyzes the information from the communication terminal 120 and monitors the occurrence of the disembarkation trigger event. Therefore, next, in S1432, it is determined whether or not the event detection unit 822 has detected the disembarkation triggering event.

When the event detection unit 822 does not detect the disembarkation trigger event (No in S1432), according to one embodiment, the processes of S1422, S1424, and S1432 are repeated. The processes of S1422, S1424 and S1432 may be executed periodically. According to another embodiment, the process of S1432 is repeated. The process of S1432 may be executed periodically.

On the other hand, when the event detection unit 822 detects the disembarkation triggering event (in the case of S1432Yes), it is determined whether or not the reservation processing regarding the vehicle allocation of the automobile 104 described in relation to FIG. 13 is necessary. Specifically, first, in S1434, the user position estimation unit 824 detects the current position of the user 20. The user position estimation unit 824 may specify the traveling section in which the user 20 exists among the traveling sections of the train 102 based on the current position of the user 20. The user position estimation unit 824 may output information indicating a traveling section in which the user 20 exists to the reservation probability estimation unit 826.

Next, in S1436 and S1438, the reservation probability estimation unit 826 calculates the disembarkation probability of the user 20 at each station as the reservation probability at each of the one or more intermediate stops. First, in S1436, among the planned disembarkation stations of the user 20 specified in S1424 and the one or more intermediate stop stations, the station for which the disembarkation probability is calculated is determined.

Specifically, the reservation probability estimation unit 826 determines that the disembarkation probability is not calculated for the stations that the train 102 has already passed among the stations that have stopped in the middle of one or more. As a result, the probability of getting off is calculated for stations where the train 102 has not passed. The reservation probability estimation unit 826 may decide not to calculate the disembarkation probability for the planned disembarkation station. You may decide to calculate the disembarkation probability for the planned disembarkation station. Further, when the next stop station of the train 102 is the scheduled stop station, the reservation probability estimation unit 826 may decide not to calculate the stop probability for all stations.

Next, the reservation probability estimation unit 826 determines the number of times the disembarkation triggering event is detected for each traveling section of the train 102. In one embodiment, the reservation probability estimation unit 826 aggregates the number of times a disembarkation trigger event is detected for each traveling section of the train 102. The reservation probability estimation unit 826 stores the aggregation result in the data table 900. In another embodiment, the reservation probability estimation unit 826 refers to the data table 900 and acquires information indicating the number of times the disembarkation triggering event is detected for each traveling section of the train 102.

Next, in S1438, the reservation probability estimation unit 826 estimates the disembarkation probability of the user 20 at each station for each of the one or more stations for which the disembarkation probability is calculated. The reservation probability estimation unit 826 may estimate the disembarkation probability of the user 20 at each station based on the number of detections of the disembarkation triggering event for each traveling section of the train 102. The probability of getting off the user 20 at each station is calculated by, for example, the following procedure.

In one embodiment, the disembarkation probability P (X) of the user 20 at the station X is determined by the following mathematical formula (1). P (X) may be 0 or more and 1 or less.
[Formula 1]
P (X) = p ₁ (X) + p ₂ (X) -p ₃ (X)

In Equation 1, p ₁ (X) is a probability determined based on at least one of one or more disembarkation triggering events detected between the boarding station of user 20 and station X. p ₁ (X) may be a probability determined based on the cumulative value N of the number of detections of the disembarkation triggering event detected between the boarding station of the user 20 and the station X. Further, p ₂ (X) and p ₃ (X) are probabilities determined based on the situation of the user 20. As shown in the formula (1), p ₂ (X) may be an adjustment term for increasing the disembarkation probability P (X), and p ₃ (X) decreases the disembarkation probability P (X). It may be an adjustment term for.

p ₁ (X) is a numerical value of 0 or more and 1 or less, and is determined based on, for example, the current situation of the user 20. For example, p ₁ (X) is determined so that the larger the cumulative value N is, the larger p ₁ (X) is. As described above, the reservation probability estimation unit 826 uses, for example, a table, a function, or an estimation model in which the above cumulative value N is used as an explanatory variable and the disembarkation probability at a stop station after the next stop is used as an objective variable. , Estimate the probability of getting off at each stop. The above function is expressed as p ₁ (X) = a × N, for example, using an arbitrary constant a.

p ₂ (X) is a numerical value of 0 or more and 1 or less, and is determined based on, for example, factors related to past events. Factors related to past events were detected in (i) the traveling section with station X as the arrival station (that is, the traveling section from the stop station immediately before station X to station X). Matters concerning the disembarkation trigger event, (ii) The traveling section before the traveling section with station X as the arrival station (that is, the traveling section from the boarding station of user 20 to the stop station immediately before station X) Matters related to the disembarkation triggering event detected in the above are exemplified.

Matters concerning the disembarkation trigger event include (i) the number of times the disembarkation triggering event is detected, the cumulative value of the number of detections, the degree or fluctuation pattern of the number of detections, and (ii) the type of disembarkation triggering event detected. In addition, at least one of the transition patterns of the type and the number of traveling sections in which the (iii) disembarkation triggering event is detected is exemplified. As described above, p 2 _(X) may be calculated using the appropriate table, function or estimation model.

For example, in the embodiment in which p ₂ (X) is determined based on the number M of the traveling sections in which the disembarkation triggering event is detected, among the traveling sections before the traveling section with the station X as the arrival station, p. ₂ (X) may be expressed as p ₂ (X) = b × M using an arbitrary constant b. Incidentally, if the off eliciting events in the travel segment before the travel section to arrival station of the station X is not detected, p 2 _(X) may be 0.

p ₃ (X) is a number greater than or equal to 0 and less than or equal to 1, and is determined, for example, based on factors relating to future events. Factors related to future events include (i) the distance between the current position of the user 20 and the next stop, (ii) the scheduled time until the train 102 arrives at the next stop, and (iii) the user 20. The distance between the current position and the planned stop station, (iv) the number of stop stations existing between the current position of the user 20 and the planned stop station, and (v) until the train 102 arrives at the planned stop station. The scheduled time and the like are exemplified. As described above, p 3 _(X) may be calculated using the appropriate table, function or estimation model.

For example, p 3 _(X) is, the distance L ₁ between the current position and the planned detraining station of the user _20, or, based on the number L ₂ of the middle stopping station that exists between the current position and the planned detraining station of the user 20 In the embodiment determined by p ₃ (X), p ₃ (X) = c ₁ ÷ L ₁ or p ₃ (X) = c ₂ ÷ using any constant c ₁ or c _2. It may be represented as L ₂ . It should be noted that, if the next stop is expected to get off at the station, p 3 _(X) may not be calculated.

In another embodiment, the probability of getting off the user 20 at the station X is determined by P (X) by the following mathematical formula (2).
[Formula 2]
P (X) = p ₁ (X) x k ₂ (X) x k ₃ (X)

In Equation 2, p ₁ (X) is a probability determined based on at least one of one or more disembarkation triggering events detected between the boarding station of user 20 and station X. p ₁ (X) may be a probability determined based on the cumulative value N of the number of detections of the disembarkation triggering event detected between the boarding station of the user 20 and the station X. Further, k ₂ (X) and k ₃ (X) are proportional coefficients determined based on the situation of the user 20. k ₂ (X) may be a proportional coefficient for increasing the disembarkation probability P (X), and k ₃ (X) may be a proportional coefficient for decreasing the disembarkation probability P (X).

p ₁ (X) is a numerical value of 0 or more and 1 or less, and is determined based on, for example, the current situation of the user 20. The details of p ₁ (X) are as described above, and the description thereof will be omitted.

k ₂ (X) is a number greater than or equal to 1, and is determined, for example, based on factors relating to past events. k ₂ (X) may be calculated by the same method as p ₂ (X).

k ₃ (X) is a number greater than or equal to 0 and less than 1, and is determined, for example, based on factors relating to future events. k ₃ (X) may be calculated by the same method as p ₃ (X).

Next, in S1440, the reservation probability estimation unit 826 determines whether or not the disembarkation probability of the user 20 at each of the one or more stations for which the disembarkation probability is calculated satisfies a predetermined condition. judge. Examples of the predetermined conditions regarding the disembarkation probability include a condition that the disembarkation probability is equal to or higher than a predetermined value and a condition that the disembarkation probability is larger than a predetermined value.

For all stations for which the disembarkation probability is calculated, when the disembarkation probability at the station does not satisfy a predetermined condition (No in S1440), in one embodiment, S1422, S1424, S1432, S1434, S1436 And S1438 are repeated. The above processing may be executed periodically. In other embodiments, the processes of S1432, S1434, S1436 and S1438 may be repeated. The above processing may be executed periodically.

When the disembarkation probability at at least one station for which the disembarkation probability is calculated satisfies a predetermined condition (in the case of Yes in S1440), the reservation probability estimation unit 826 in S1442 , Determines to perform a reservation process for vehicle allocation at at least one of the above stations. The reservation probability estimation unit 826 generates a request for information for identifying at least one station whose disembarkation probability satisfies a predetermined condition and information indicating that a reservation process for vehicle allocation at the station is executed. Output to unit 832. As a result, the information processing in S1322 is completed.

As described above, FIG. 15 schematically shows an example of information processing in the user management server 116 or the vehicle allocation request unit 650. According to this embodiment, first, S1322, S1324 and S1334 are executed.

Next, in S1340, when the instruction confirmation unit 836 receives the reservation instruction from the communication terminal 120 of the user 20 before the reservation deadline has passed (Yes in S1340), the instruction confirmation unit 836 receives the reservation instruction from the user 20. The reservation instruction of is transmitted to the request generation unit 832. Further, in S1550, the request generation unit 832 transmits a request for reserving the use of the automobile 104 to the vehicle allocation management server 114 according to the reservation instruction from the user 20.

Next, in S1352, when the remaining period until the cancellation deadline becomes smaller than the predetermined value, the instruction confirmation unit 836 transmits a message indicating that the cancellation deadline is approaching to the communication terminal 120 of the user 20. .. The above message may include the URI of the cancellation confirmation screen. The instruction confirmation unit 836 may send a cancellation confirmation screen on which a message indicating that the cancellation deadline is approaching is approaching to the communication terminal 120 of the user 20.

Next, in S1354, when the instruction confirmation unit 836 receives the cancellation instruction from the communication terminal 120 of the user 20 before the cancellation deadline has passed (Yes in S1354), the instruction confirmation unit 836 cancels the user 20. The instruction is transmitted to the request generation unit 832. In S1370, the request generation unit 832 transmits a request for canceling the reservation to the vehicle allocation management server 114. On the other hand, in S1354, if the instruction confirmation unit 836 does not receive the cancellation instruction from the communication terminal 120 of the user 20 before the cancellation deadline has passed (No in S1354), the vehicle allocation request unit 650 ends the process. To do.

On the other hand, in S1340, when the instruction confirmation unit 836 does not receive the reservation instruction from the communication terminal 120 of the user 20 before the reservation deadline has passed (No of S1340), the instruction confirmation unit 836 has the reservation deadline. Wait until the remaining period until becomes smaller than the predetermined value. Next, in S1362, when the remaining period until the reservation deadline becomes smaller than the predetermined value, the instruction confirmation unit 836 transmits a message indicating that the reservation deadline is approaching to the communication terminal 120 of the user 20. .. The above message may include the URI of the reservation confirmation screen. The instruction confirmation unit 836 may send a reservation confirmation screen on which a message indicating that the reservation deadline is approaching is approaching to the communication terminal 120 of the user 20.

Next, in S1364, when the instruction confirmation unit 836 receives the reservation instruction from the communication terminal 120 of the user 20 (Yes in S1364) before the reservation deadline has passed, the processing after S1550 is executed. On the other hand, in S1364, if the instruction confirmation unit 836 does not receive the reservation instruction from the communication terminal 120 of the user 20 before the reservation deadline has passed (No in S1364), the vehicle allocation request unit 650 ends the process. To do.

FIG. 16 schematically shows an example of the internal configuration of the communication terminal 120. In the present embodiment, the communication terminal 120 includes an input unit 1620, an output unit 1640, an input / output control unit 1660, and a communication unit 1680. In the present embodiment, the input unit 1620 includes a user input reception unit 1622, a vital information acquisition unit 1624, and a voice information acquisition unit 1626.

In the present embodiment, the input unit 1620 receives various inputs to the communication terminal 120. Examples of the input unit 1620 include various input devices such as a keyboard, a touch panel, a pointing device, a camera, a microphone, various sensors, and a GPS receiver.

In the present embodiment, the user input receiving unit 1622 accepts the user's input. Examples of the user input receiving unit 1622 include a keyboard, a touch panel, and a pointing device. In the present embodiment, the vital information acquisition unit 1624 acquires vital information of the user 20 or the companion 22 from the wearable terminal 122. In the present embodiment, the voice information acquisition unit 1626 acquires voice information.

In this embodiment, the output unit 1640 outputs various information. Examples of the output unit 1640 include various output devices such as a display device, a speaker, and a vibration device.

In the present embodiment, the input / output control unit 1660 controls the input unit 1620 and the output unit 1640. In the present embodiment, the communication unit 1680 sends and receives information to and from an external information processing device. For example, the communication unit 1680 sends and receives information to and from the user management server 116. The communication unit 1680 may send and receive information to and from the wearable terminal 122.

FIG. 17 shows an example of a computer 3000 in which a plurality of aspects of the present invention may be embodied in whole or in part. The vehicle dispatch support system 100 or a part thereof may be realized by the computer 3000. For example, each of the transportation management server 112, the vehicle allocation management server 114, and the user management server 116 is realized by the computer 3000.

The program installed on the computer 3000 causes the computer 3000 to function as an operation associated with the device according to an embodiment of the present invention or as one or more "parts" of the device, or the operation or the one or more "parts". A unit can be run and / or a computer 3000 can be run a process according to an embodiment of the invention or a stage of the process. Such a program may be executed by the CPU 3012 to cause the computer 3000 to perform a specific operation associated with some or all of the blocks of the flowcharts and block diagrams described herein.

The computer 3000 according to this embodiment includes a CPU 3012, a RAM 3014, a graphic controller 3016, and a display device 3018, which are interconnected by a host controller 3010. The computer 3000 also includes an input / output unit such as a communication interface 3022, a hard disk drive 3024, a DVD-ROM drive 3026, and an IC card drive, which are connected to the host controller 3010 via the input / output controller 3020. The computer also includes legacy I / O units such as the ROM 3030 and keyboard 3042, which are connected to the I / O controller 3020 via an I / O chip 3040.

The CPU 3012 operates according to the programs stored in the ROM 3030 and the RAM 3014, thereby controlling each unit. The graphic controller 3016 acquires the image data generated by the CPU 3012 in a frame buffer or the like provided in the RAM 3014 or itself so that the image data is displayed on the display device 3018.

The communication interface 3022 communicates with other electronic devices via the network. The hard disk drive 3024 stores programs and data used by the CPU 3012 in the computer 3000. The DVD-ROM drive 3026 reads the program or data from the DVD-ROM 3001 and provides the program or data to the hard disk drive 3024 via the RAM 3014. The IC card drive reads the program and data from the IC card and / or writes the program and data to the IC card.

The ROM 3030 stores in it a boot program or the like executed by the computer 3000 at the time of activation, and / or a program depending on the hardware of the computer 3000. The input / output chip 3040 may also connect various input / output units to the input / output controller 3020 via a parallel port, a serial port, a keyboard port, a mouse port, and the like.

The program is provided by a computer-readable storage medium such as a DVD-ROM 3001 or an IC card. The program is read from a computer-readable storage medium, installed on a hard disk drive 3024, RAM 3014, or ROM 3030, which is also an example of a computer-readable storage medium, and executed by the CPU 3012. The information processing described in these programs is read by the computer 3000 and provides a link between the program and the various types of hardware resources described above. The device or method may be configured to implement the operation or processing of information in accordance with the use of computer 3000.

For example, when communication is executed between the computer 3000 and an external device, the CPU 3012 executes a communication program loaded in the RAM 3014, and performs communication processing on the communication interface 3022 based on the processing described in the communication program. You may order. Under the control of the CPU 3012, the communication interface 3022 reads and reads the transmission data stored in the transmission buffer area provided in the recording medium such as the RAM 3014, the hard disk drive 3024, the DVD-ROM 3001, or the IC card. The data is transmitted to the network, or the received data received from the network is written to the reception buffer area or the like provided on the recording medium.

Further, the CPU 3012 makes the RAM 3014 read all or necessary parts of a file or database stored in an external recording medium such as a hard disk drive 3024, a DVD-ROM drive 3026 (DVD-ROM3001), or an IC card. Various types of processing may be performed on the data on the RAM 3014. The CPU 3012 may then write back the processed data to an external recording medium.

Various types of information such as various types of programs, data, tables, and databases may be stored on recording media and processed. The CPU 3012 describes various types of operations, information processing, conditional judgment, conditional branching, unconditional branching, and information retrieval described in various parts of the present disclosure with respect to the data read from the RAM 3014, and is specified by the instruction sequence of the program. Various types of processing may be performed, including / replacement, etc., and the results are written back to RAM 3014. Further, the CPU 3012 may search for information in a file, a database, or the like in the recording medium. For example, when a plurality of entries each having an attribute value of the first attribute associated with the attribute value of the second attribute are stored in the recording medium, the CPU 3012 is the first of the plurality of entries. The attribute value of the attribute of is searched for the entry that matches the specified condition, the attribute value of the second attribute stored in the entry is read, and the first attribute satisfying the predetermined condition is selected. You may get the attribute value of the associated second attribute.

The program or software module described above may be stored on or in a computer-readable storage medium on or near the computer 3000. In addition, a recording medium such as a hard disk or RAM provided in a dedicated communication network or a server system connected to the Internet can be used as a computer-readable storage medium, whereby the above program can be transmitted via the network. Provided to computer 3000.

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be apparent to those skilled in the art that various changes or improvements can be made to the above embodiments. Further, to the extent that there is no technical contradiction, the matters described for the specific embodiment can be applied to other embodiments. Further, each component may have the same characteristics as other components having the same name but different reference numerals. It is clear from the description of the claims that the form with such modifications or improvements may be included in the technical scope of the present invention.

The order of execution of each process such as operation, procedure, step, and step in the device, system, program, and method shown in the claims, specification, and drawings is particularly "before" and "prior to". It should be noted that it can be realized in any order unless the output of the previous process is used in the subsequent process. Even if the scope of claims, the specification, and the operation flow in the drawings are explained using "first," "next," etc. for convenience, it means that it is essential to carry out in this order. It's not a thing.

10 communication network, 20 users, 22 companions, 100 vehicle allocation support system, 102 trains, 104 automobiles, 112 transportation management server, 114 vehicle allocation management server, 116 user management server, 120 communication terminals, 122 wearable terminals, 320 operation plan management 340 Operation status management unit, 360 storage unit, 362 Operation plan storage unit, 364 Operation status storage unit, 420 Request processing unit, 422 Extraction request processing unit, 424 Vehicle allocation request processing unit, 440 Vehicle allocation unit, 460 Vehicle status storage unit , 500 data table, 522 vehicle ID, 524 current position, 526 operation status, 620 request reception unit, 630 screen generation unit, 640 behavior management unit, 650 vehicle allocation request unit, 660 storage unit, 662 user setting storage unit, 664 schedule storage Unit, 666 route storage unit, 668 user status storage unit, 742 schedule management unit, 744 route search unit, 746 route registration unit, 822 event detection unit, 824 user position estimation unit, 826 reservation probability estimation unit, 832 request generation unit, 834 Deadline determination unit, 836 instruction confirmation unit, 900 data table, 922 user ID, 924 event detection frequency, 926 reservation probability, 1000 data table, 1022 station name, 1024 reservation probability, 1100 screen, 1120 data table, 1122 station name, 1124 hours 1,126 Scheduled arrival time, 1128 Scheduled arrival time, 1132 Reception deadline, 1134 Reception deadline, 1142 Reservation button, 1144 Cancel button, 1200 screen, 1620 input unit, 1622 User input reception unit, 1624 Vital information acquisition unit, 1626 Voice information acquisition Unit, 1640 output unit, 1660 input / output control unit, 1680 communication unit, 3000 computer, 3001 DVD-ROM, 3010 host controller, 3012 CPU, 3014 RAM, 3016 graphic controller, 3018 display device, 3020 input / output controller, 3022 communication interface , 3024 hard disk drive, 3026 DVD-ROM drive, 3030 ROM, 3040 I / O chip, 3042 key board

Claims (10)

It is an operation management system that manages the operation of the first moving body that can move according to the user's request.
A specific unit that specifies a usage plan including a planned disembarkation position where the user who uses the second moving body that moves according to a predetermined operation plan plans to get off from the second moving body, and
A first detection unit that detects the occurrence of an event that causes a change in the usage plan, at least during the period when the user is using the second moving body.
Based on the occurrence status of the event detected by the first detection unit, the position where the user gets off the second moving body is a stop position in the middle of stopping until the second moving body reaches the scheduled disembarkation position. An estimation unit that estimates the probability of change, which indicates the degree of possibility of change to
An operation determination unit that determines the operation of the first moving body with respect to the intermediate stop position based on the change probability estimated by the estimation unit.
An operation management system equipped with. The estimation unit is modified so that the larger the number or frequency of detection of the event by the first detection unit during the period when the user is using the second moving body, the greater the change probability. Estimate the probability,
The operation management system according to claim 1. A second detection unit that detects the current position of the user at least during the period when the user is using the second moving body is provided.
The estimation unit estimates the change probability so that the shorter the distance from the user's current position detected by the second detection unit to the planned disembarkation position, the smaller the change probability.
The operation management system according to claim 1 or 2. The stop position is
The first stop position and
A second intermediate stop position at which the second moving body stops before reaching the first intermediate stop position, and
Have,
In the estimation unit, (i) the first detection unit detects the event during the period until the second moving body reaches the second intermediate stop position, and the second moving body is the first. 2 The change probability when the first detection unit detects the event in the period after reaching the halfway stop position and until reaching the first halfway stop position is (ii) the second movement. After the first detection unit does not detect the event and the second moving body reaches the second stop position during the period until the body reaches the second stop position. The change probability is estimated so as to be larger than the change probability when the first detection unit detects the event in the period until the first stop position is reached.
The operation management system according to any one of claims 1 to 3. When the change probability satisfies a predetermined condition, the operation determination unit executes the vehicle allocation process of the first moving body.
The operation management system according to any one of claims 1 to 4. The vehicle allocation process
A procedure for reserving the use of the first moving body by the user and
After the reservation is made, a procedure for sending a message to the communication terminal of the user asking whether or not the user wants to use the first mobile body, and
including,
The operation management system according to claim 5. The vehicle allocation process
A procedure for sending a message to the user's communication terminal asking whether or not the user wants to use the first mobile body, and
A procedure for receiving information indicating that the user desires to use the first mobile body from the user's communication terminal, and
After receiving the information indicating that the user wants to use the first moving body, the procedure for reserving the use of the first moving body by the user and the procedure.
including,
The operation management system according to claim 5. The vehicle allocation process is a procedure of assigning the reservation to at least one of the one or more first moving bodies and outputting an instruction for moving the first moving body to which the reservation is assigned to the intermediate stop position. The operation management system according to claim 6 or 7, further comprising. A program for causing a computer to function as the operation management system according to any one of claims 1 to 8. It is an operation management method that manages the operation of the first moving body that can move according to the user's request.
A specific step of specifying a usage plan including a planned disembarkation position where the user who uses the second moving body that moves according to a predetermined operation plan plans to get off from the second moving body, and
At least during the period when the user is using the second moving body, a first detection step of detecting the occurrence of an event that causes a change in the usage plan, and
Based on the occurrence status of the event detected in the first detection stage, the position where the user gets off the second moving body stops halfway until the second moving body reaches the scheduled disembarkation position. An estimation stage that estimates the probability of change, which indicates the degree of possibility of being changed to a position,
An operation determination step of determining the operation of the first moving body with respect to the intermediate stop position based on the change probability estimated in the estimation stage, and
Operation management method.