JP7836669B2 - Mobility service provision system, mobility service provision method, mobility service provision device - Google Patents

Description

This invention relates to a mobility service provision system, a mobility service provision method, and a mobility service provision device.

Patent Document 1 describes a notification method that allows a caregiver, upon request from a person being monitored (e.g., an elderly person) using on-demand transportation, to make a reservation for on-demand transportation, and to send notification information to the caregiver regarding the date and time of boarding and alighting, stopping points, names of the passengers, and whether or not the person being monitored boarded the vehicle as reserved.

Japanese Patent Publication No. 2016-212536

The notification method described in Patent Document 1 is not configured to notify the caregiver of information while the person being monitored is in the vehicle. However, depending on the relationship between the caregiver and the person being monitored, there may be a need for the caregiver to be notified of information while the person being monitored is in the vehicle. However, continuously notifying the caregiver of information while the person being monitored is in the vehicle may create time constraints and increase the caregiver's workload.
The present invention aims to reduce the burden on the person making the reservation when notifying the person making the reservation of information while the user is riding in the vehicle that provides the transportation service that transports the user by operating the vehicle.

According to one aspect of the present invention, a mobility service provision system for operating vehicles is provided. The mobility service provision system comprises a vehicle used for mobility services and a control device that receives reservation information, at least including information about the user receiving the mobility service, from an electronic device which is a terminal device operated by a user making a reservation for the mobility service, and arranges a vehicle for the user's use according to the reservation information. The control device includes a user database that stores information about registered users who have been pre-registered to use the mobility service provision system, and information about the relationships between registered users. By referring to the user database, if the reservation user and the user have a predetermined relationship, the control device notifies the electronic device of information regarding the vehicle's operation at a predetermined notification timing.

According to this invention, information regarding the vehicle's operation is notified to the reservation holder at a predetermined notification timing, only when the reservation holder and the user have a predetermined relationship. Therefore, while the user is riding in the vehicle, the burden on the reservation holder is reduced when notifying them of information.

This is a schematic diagram of an example of a mobile service provision system according to an embodiment. Figure 1 is an explanatory diagram illustrating an example of the functional configuration of the first electronic device. Figure 1 is an explanatory diagram illustrating an example of the functional configuration of the control device. Figure 1 is an explanatory diagram illustrating an example of the functional configuration of the second electronic device. This is a sequence diagram illustrating an example of the process when booking a mobility service. This is a sequence diagram illustrating an example of the operation when using a mobility service. This is a sequence diagram illustrating an example of the operation when using a mobility service. This is a sequence diagram illustrating an example of the operation when using a mobility service.

The embodiments of the present invention will be described below with reference to the drawings. In the drawings, identical or similar parts are denoted by the same or similar reference numerals, and redundant descriptions are omitted. Each drawing is schematic and may differ from reality. The embodiments shown below illustrate devices and methods for realizing the technical idea of the present invention; however, the technical idea of the present invention is not limited to the devices and methods exemplified in the embodiments below. The technical idea of the present invention can be modified in various ways within the technical scope described in the claims.

(composition)
Figure 1 is a schematic diagram of an example of a mobility service provision system according to an embodiment. Mobility service provision system 1 is a system that provides mobility services by operating a vehicle 3 to transport users. In this specification, the vehicle 3 used for mobility services by mobility service provision system 1 is referred to as a "service vehicle".
The mobile service provision system 1 comprises at least a control device 2 and a service vehicle 3.
Furthermore, the first electronic device 4 is a terminal device operated by the person who reserves a mobility service through the mobility service provision system 1 (hereinafter referred to as the "reservationer"), and the second electronic device 5 is a terminal device operated by the person who receives a mobility service through the mobility service provision system 1 (hereinafter referred to as the "user"). For example, the first electronic device 4 may be a portable information terminal that the reservationer can carry, a small portable computer, or a computer mounted on a desk. For example, the second electronic device 5 may be, for example, a portable information terminal that the user can carry, or a small portable computer.

When a user makes a reservation for a mobility service, they access the control device 2 using the first electronic device 4. Before making a reservation for a mobility service, the user may pre-install dedicated application software for using the mobility service provision system 1 on the first electronic device 4 and make a reservation using the dedicated application software. In the following explanation, "application software" will be simply referred to as "software." Alternatively, the user may use the browser function of the first electronic device 4 to make a reservation for a mobility service on a website that accepts reservations for mobility services over the internet.
The first electronic device 4 receives input operations from the person making the reservation for the mobility service. Based on the information entered by the person making the reservation, the first electronic device 4 generates reservation information for applying for the mobility service and transmits the reservation information to the control device 2. The reservation information may include, for example, information about the user receiving the mobility service (e.g., user identification information), the boarding location (boarding place) and boarding date and time for boarding the service vehicle 3, and the disembarking location (disembarking place) for disembarking from the service vehicle 3.

The first electronic device 4 comprises a communication device 40, a human-machine interface (HMI) 41, and a controller 42.
The communication device 40 provides a communication function between the first electronic device 4 and an external device. The communication method used by the communication device 40 may be, for example, wireless communication over a public mobile communication network, satellite communication, etc. The first electronic device 4 transmits and receives data with the control device 2 and the second electronic device 5 using the communication device 40.
HMI41 is an interface device that exchanges information between the first electronic device 4 and the user. HMI41 is equipped with a display device visible to the user, as well as a speaker and buzzer that output alarm sounds, notification sounds, and voice information. HMI41 is also equipped with an operator and a voice input device that accepts operation input from the user to the first electronic device 4. The operator may be a button, switch, lever, dial, keyboard, touch panel, etc.

The controller 42 is an electronic control unit (ECU) that controls the operation of the first electronic device 4. The controller 42 includes a processor 43 and peripheral components such as a storage device 44. The processor 43 may be, for example, a CPU (Central Processing Unit) or an MPU (Micro-Processing Unit). The storage device 44 may include non-transitory tangible storage media such as registers, cache memory, and ROM (Read Only Memory) or RAM (Random Access Memory) used as main memory.
The functions of the first electronic device 4, described below, are realized, for example, by the processor 43 executing a computer program stored in the storage device 44.

The control device 2 receives reservation information from the first electronic device 4 and arranges a service vehicle 3 for use by the user according to the reservation information. The control device 2 includes a processor 20, a storage device 21, a communication device 22, a registered user database (registered user DB) 23, a map database (map DB) 24, and a reservation database (reservation DB) 25.
The processor 20 may be, for example, a CPU or an MPU. The storage device 21 may include tangible storage media that are not temporary, such as registers, cache memory, and ROM, RAM, or other memory used as main memory. The functions of the control device 2 described below are realized, for example, by the processor 20 executing a computer program stored in the storage device 21.

The communication device 22 provides a communication function between the control device 2 and an external device. The communication method used by the communication device 22 may be, for example, wired communication or wireless communication via a public mobile communication network, satellite communication, or vehicle-to-infrastructure communication with the service vehicle 3.
The control device 2 transmits and receives data between the service vehicle 3, the first electronic device 4, and the second electronic device 5 via the communication device 22.

The Registered User Database 23 is a database for registering users of the Mobility Service Provision System 1. In the following description, those registered in the Registered User Database 23 will be referred to as "registered users." For example, as users of the Mobility Service Provision System 1, both those who make reservations for mobility services provided by the Mobility Service Provision System 1 and those who receive mobility services are registered in the Registered User Database 23.
Various methods can be adopted for registering reservation holders and users in the registrant DB 23. For example, reservation holders and users may be registered in the registrant DB 23 as persons who can both reserve and use the mobility service (i.e., persons who can use the mobility service provision system 1 as both a reservation holder and a user).
Furthermore, for example, individuals who can only make reservations for mobility services (i.e., those who can only use the mobility service provision system 1 as reservation holders), or individuals who can both make reservations and use mobility services, may be registered in the registrant DB 23 as primary registrants, while individuals who can only use mobility services (i.e., those who can only use the mobility service provision system 1 as users) may be registered as secondary registrants attached to the primary registrants.
Furthermore, for example, individuals who are only able to use mobility services, or individuals who are able to both book and use mobility services, may be registered in the registrant DB23 as primary registrants, while individuals who are only able to book mobility services may be registered as secondary registrants attached to the primary registrants.

Furthermore, if a relationship exists between different registrants registered in the registrant database 23, the relationship between the registrants is registered in the registrant database 23.
As part of such relationships between registrants, one registrant may register in the Registrant DB23 that they are the legal supervisor of another registrant. Examples of legal supervisory roles include registering that one registrant is the parent of another registrant, the guardian of another registrant, or the child of another elderly registrant.
Furthermore, as a relationship between registered users, for example, it may be registered in the user database 23 that one user provides care services to another user.
Furthermore, as a relationship between registered users, it is also possible to register in the Registered User DB23 that a user is contracted to make reservations for mobility services on behalf of other registered users. Additionally, for example, it is possible to register that a registered user is a secretary or butler for another registered user.

Various methods can be used to register the relationships between registered users in the user database 23. For example, when registering the relationships between registered users who are separately registered as being able to both book and use mobility services, link information that associates these registered users with each other and relationship attribute information that indicates the relationship between these registered users may be stored in the user database 23.
Furthermore, when registering the relationship between a secondary registrant registered in association with the primary registrant and the primary registrant, relationship attribute information indicating the relationship between the primary registrant and the secondary registrant may be added to the registration information of the primary registrant or the secondary registrant and stored in the registrant DB23.

Map DB24 stores map information for the area where the mobility service provision system 1 provides mobility services. The map information may be, for example, navigation map data (hereinafter simply referred to as "navigation map").
When the control device 2 receives reservation information from the first electronic device 4, it calculates the travel route from the boarding location to the alighting location included in the reservation information based on the map information stored in the map DB 24. The control device 2 also predicts the alighting date and time when the service vehicle 3 will depart at the boarding date and time included in the reservation information and arrive at the alighting location after traveling along the travel route.
The control device 2 stores the boarding location, boarding date and time, and alighting location included in the reservation information received from the first electronic device 4, along with the travel route and alighting date and time calculated by the control device 2, in the reservation DB 25 as a travel plan for the service vehicle 3 (i.e., a travel plan for the mobility service provided to the user), along with the user's identification information.
Furthermore, the control device 2 transmits a travel plan, including the boarding location, boarding date and time, alighting location, alighting date and time, and travel route, to the service vehicle 3.

Service vehicle 3 is a vehicle that operates in response to user requests (a so-called on-demand transport vehicle), and may be, for example, a shared taxi or a robot taxi. Service vehicle 3 is an autonomous vehicle that is automatically driven by the controller 36 without the involvement of a driver (human), according to a driving plan transmitted from the control device 2.
When service vehicle 3 receives a travel plan from control device 2, it travels to the boarding location so as to arrive by the boarding date and time included in the travel plan. When a user boards service vehicle 3 at the boarding location, it travels to the disembarking location along the route included in the travel plan.
The service vehicle 3 is equipped with a sensor 30, a positioning device 31, a map database (map DB) 32, a communication device 33, an in-vehicle terminal 34, in-vehicle equipment 35, a controller 36, and an actuator 37.
The sensor 30 includes an object sensor that detects objects around the service vehicle 3, and a vehicle sensor that detects various information (vehicle status) obtained from the service vehicle 3.
The object sensor detects the surrounding environment of the service vehicle 3, such as the relative position of objects surrounding the service vehicle 3, the distance between the service vehicle 3 and the objects, and the direction in which the objects are located. The object sensor may include, for example, a camera that photographs the surrounding environment of the service vehicle 3. The object sensor may also include, for example, a distance measuring device such as a laser rangefinder (LRF), radar, or a LiDAR (Light Detection and Ranging) laser radar. The object sensor outputs the surrounding environment information, which is the information of the surrounding environment of the service vehicle 3 that it has detected, to the controller 36.
The vehicle sensors may include, for example, a vehicle speed sensor for detecting the driving speed (vehicle speed) of the service vehicle 3, a wheel speed sensor for detecting the rotational speed of each tire on the service vehicle 3, a three-axis acceleration sensor (G sensor) for detecting the acceleration (including deceleration) of the service vehicle 3 in three axes, a steering angle sensor for detecting the steering angle (including turning angle), a gyro sensor for detecting the angular velocity occurring in the service vehicle 3, and a yaw rate sensor for detecting the yaw rate. Furthermore, the vehicle sensors may include a seat belt sensor for detecting whether a seat belt is fastened or unfastened, and a door sensor for detecting whether a door is opened or closed. The vehicle sensors output vehicle status information to the controller 36.

The positioning device 31 measures the current position and attitude of the service vehicle 3. The positioning device 31 may include, for example, a Global Positioning System (GNSS) receiver. The GNSS receiver may be, for example, a GPS receiver. The positioning device 31 may also include an inertial navigation device. The positioning device 31 outputs the measured current position information to the controller 36.
Map DB32 stores map information. The map information may include map data for navigation (hereinafter simply referred to as "navigation map") and high-precision map data suitable for autonomous driving (hereinafter simply referred to as "high-precision map").
The communication device 33 provides a communication function between the service vehicle 3 and an external device. The communication method used by the communication device 33 may be, for example, wireless communication over a public mobile communication network, satellite communication, vehicle-to-infrastructure communication, etc.
The service vehicle 3 transmits and receives data to and from the control device 2 via the communication device 33.

The in-vehicle terminal 34 is a terminal device used by users riding in the service vehicle 3. The terminal device may be an information terminal device separate from the controller 36, or it may be an HMI that exchanges information between the user and the controller 36. By using the in-vehicle terminal 34, users can access various information services (e.g., internet, news, video, and music distribution services) and obtain coupons. In addition, for example, the in-vehicle terminal 34 can be used for user authentication procedures when starting to use the service vehicle 3. In addition, for example, the in-vehicle terminal 34 can be used by users to change the travel plan of the service vehicle 3.
The in-vehicle equipment 35 includes the window opening and closing device, door locking device, air conditioning system, audio system, etc., of the service vehicle 3.

The controller 36 is an electronic control unit that controls the service vehicle 3. For example, the controller 36 performs autonomous driving control of the service vehicle 3. The controller 36 includes a processor 38 and peripheral components such as a storage device 39. The processor 38 may be, for example, a CPU or an MPU. The storage device 39 may include tangible storage media that are not temporary, such as registers, cache memory, or ROM, RAM, etc., used as main memory. The functions of the controller 36 are realized, for example, by the processor 38 executing a computer program stored in the storage device 39.
The controller 36 performs autonomous driving control to drive the service vehicle 3 according to a driving plan, based on ambient environment information and vehicle status information from the sensor 30, positioning results from the positioning device 31, and map information from the map DB 32. For example, the controller 36 calculates a target driving trajectory for the service vehicle 3 based on the current position and attitude of the service vehicle 3, the driving route included in the driving plan, the map information, and the surrounding environment of the service vehicle 3. In addition, the controller 36 generates, for example, a path space map that represents the paths and presence or absence of objects around the service vehicle 3, and a risk map that quantifies the degree of danger of the driving area, and generates a target driving trajectory based on the motion characteristics of the service vehicle 3, vehicle status information, path space map, and risk map. Then, the controller 36 drives the actuator 37 so that the service vehicle 3 travels along the generated target driving trajectory.
The actuator 37 automatically drives the service vehicle 3 by operating the steering system, drive system, and braking system of the service vehicle 3 in response to control signals from the controller 36, thereby generating vehicle behavior for the service vehicle 3. The actuator 37 comprises a steering actuator, an accelerator opening actuator, and a brake control actuator.

The second electronic device 5 is a terminal device used and operated by the user of the service vehicle 3. For example, the second electronic device 5 may be used for user authentication procedures when starting to use the service vehicle 3, and the user can use it to change the travel plan of the service vehicle 3. When a user uses the mobility service using the second electronic device 5, they must pre-install dedicated software for using the mobility service provision system 1 on the second electronic device 5.
The second electronic device 5 includes a positioning device 50, a communication device 51, an HMI 52, and a controller 53.
The positioning device 50 measures the current position of the second electronic device 5 (i.e., the current position of the user). The positioning device 50 may include, for example, a Global Navigation System (GNSS) receiver. The GNSS receiver may be, for example, a GPS receiver. The positioning device 50 may also include an inertial navigation device. The positioning device 50 outputs the current position information of the second electronic device 5 to the controller 36.

The communication device 51 provides a communication function between the second electronic device 5 and an external device. The communication method used by the communication device 51 may be, for example, wireless communication over a public mobile communication network, satellite communication, etc. The second electronic device 5 transmits and receives data with the control device 2 and the first electronic device 4 using the communication device 51.
HMI 52 is an interface device that exchanges information between the second electronic device 5 and the user. HMI 52 is equipped with a display device visible to the user, as well as a speaker and buzzer that output alarm sounds, notification sounds, and voice information. HMI 52 is also equipped with an operator and a voice input device that accepts operation input from the user to the second electronic device 5. The operator may be a button, switch, lever, dial, keyboard, touch panel, etc.

The controller 53 is an electronic control unit that controls the operation of the second electronic device 5. The controller 53 includes a processor 54 and peripheral components such as a storage device 55. The processor 54 may be, for example, a CPU or an MPU. The storage device 55 may include tangible, non-temporary storage media such as registers, cache memory, and ROM, RAM, etc., which are used as main memory.
The functions of the second electronic device 5, described below, are realized, for example, by the processor 54 executing a computer program stored in the storage device 55.

When providing mobility services in the mobility service provision system 1, the person making the reservation for the mobility service and the user receiving the mobility service may be different, and the relationship between the person making the reservation and the user may be a predetermined relationship set in advance.
The following are examples of situations where the relationship between the reservation holder and the user is a prescribed relationship: for example, the reservation holder is the legal supervisor of the user (for example, the user is a young child and the user's parent makes a reservation for a transportation service on behalf of the child), or the reservation holder is a person who provides care services to the user and makes a reservation for a transportation service on behalf of the user.
In such cases, it may be preferable to notify the person who made the reservation of information regarding the travel of the service vehicle 3 in which the user is riding, in order to confirm whether the user has arrived safely at the drop-off location. For example, if the user receiving the transportation service is a young child, it may be preferable to notify the person who made the reservation that the service vehicle 3 has passed through the points it passes through on its journey to the drop-off location without any problems.

However, if the person who made the reservation is constantly notified of information regarding the operation of service vehicle 3 while they are riding in service vehicle 3, the person who made the reservation will have to constantly be mindful of the notifications, which may create time constraints and increase the burden on the person who made the reservation.
Therefore, in the mobility service provision system 1 of this embodiment, if the person making the reservation and the user are different, and the relationship between the person making the reservation and the user is a predetermined relationship, the system notifies the person making the reservation of information regarding the operation of the service vehicle 3 at a pre-set notification timing.
This allows the reservation holder to receive notifications regarding the service vehicle 3's operation only at pre-set notification times. Therefore, time constraints and other factors are reduced, lessening the burden on the reservation holder.

The details of the mobile service provision system 1 are described below. Figures 2A to 2C are explanatory diagrams illustrating an example of the functional configuration of the first electronic device 4, the control device 2, and the second electronic device 5, respectively.
The first electronic device 4 includes a reservation information transmission unit 60, a reservation information generation unit 61, a notification location setting unit 62, a remaining distance setting unit 63, a remaining time setting unit 64, and a notification receiving unit 65.
The control device 2 includes a reservation setting unit 70, a location information acquisition unit 71, a vehicle dispatch unit 72, a travel plan setting unit 73, a relationship attribute determination unit 74, a travel plan modification unit 75, a notification point passage determination unit 76, a remaining distance determination unit 77, a remaining time determination unit 78, and a delay determination unit 79.
The second electronic device 5 includes a location information acquisition unit 80 and a driving plan change setting unit 81.

The reservation information transmission unit 60 transmits the reservation holder's identification information to the control device 2 when a mobility service is reserved using the first electronic device 4. For example, the reservation information transmission unit 60 may transmit the reservation holder's identification information to the control device 2 for the purpose of authenticating the reservation holder when logging into the control device 2. Alternatively, the reservation information transmission unit 60 may transmit the reservation holder's identification information to the control device 2 at the same time as the reservation information.
When the user operates the HMI 41 and inputs the information necessary to reserve a mobility service (user, boarding location, boarding date and time, and alighting location), the reservation information generation unit 61 generates reservation information. As described above, the reservation information includes user identification information and information on the boarding location, boarding date and time, and alighting location. The reservation information generation unit 61 transmits the generated reservation information to the control device 2.

When the reservation setting unit 70 receives reservation information from the first electronic device 4, it registers the reservation information in the reservation DB 25 and sets up a reservation for the mobility service for the user specified in the reservation information.
If dedicated software for using the mobility service provision system 1 is installed on the second electronic device 5, the reservation setting unit 70 transmits reservation notification information to the second electronic device 5 informing the user that a mobility service has been reserved. For example, the reservation setting unit 70 may transmit the reservation notification information to the second electronic device 5 by push-type data transmission. This allows the dedicated software installed on the second electronic device 5 to receive the reservation notification information promptly.

The location information acquisition unit 80 acquires the current location information of the second electronic device 5 (i.e., the user's current location information) from the positioning device 50. When the location information acquisition unit 80 receives reservation notification information from the control device 2, it transmits the current location information of the second electronic device 5 to the control device 2. For example, the location information acquisition unit 80 may periodically transmit the current location information to the control device 2 until the mobility service is completed (for example, until the user disembarks from the service vehicle 3 at the drop-off location). Alternatively, for example, the current location information may be periodically transmitted to the control device 2 until the user boards the service vehicle 3 at the boarding location.

The location information acquisition unit 71 receives the current location information of the second electronic device 5 transmitted from the second electronic device 5. The location information acquisition unit 71 also receives the current location information of the service vehicle 3 transmitted from the service vehicle 3.
The dispatch unit 72 determines which service vehicle 3 to provide to the user based on the pick-up location included in the reservation information and the current location of the service vehicle 3. For example, the dispatch unit 72 may select a service vehicle 3 that is not currently being used by another user and can arrive at the pick-up location by the pick-up date and time, and that is located closest to the pick-up location. The dispatch unit 72 stores the identification information of the selected service vehicle 3 in the reservation DB 25.

The travel plan setting unit 73 calculates the travel route from the boarding location to the alighting location based on the map information stored in the map DB 24. The travel plan setting unit 73 also predicts the alighting date and time when the service vehicle 3 departs at the boarding date and time, travels along the travel route, and arrives at the alighting location. The travel plan setting unit 73 stores the calculated travel route and alighting date and time in the reservation DB 25. As a result, the boarding location, boarding date and time, alighting location included in the reservation information, along with the alighting date and time and travel route calculated by the travel plan setting unit 73, are stored in the reservation DB 25 as the travel plan for the mobility service provided to the user.
The driving plan setting unit 73 transmits driving plan information related to the driving plan to the service vehicle 3 selected by the dispatch unit 72 (i.e., the service vehicle 3 made available for use by the user) and to the first electronic device 4.
Upon receiving the travel plan information, the first electronic device 4 displays the boarding location, boarding date and time, alighting location, alighting date and time, and travel route on the HMI 41.

When the boarding location, boarding date and time, alighting location, alighting date and time, and travel route are displayed on the HMI 41, the notification point setting unit 62 of the first electronic device 4 allows the reservation holder to input the notification point. The notification point is input by, for example, the reservation holder specifying the location of the notification point within the travel route displayed on the HMI 41 using the touch panel. Alternatively, the notification point can be input by, for example, the reservation holder specifying the location of the notification point within the travel route displayed on the HMI 41 using coordinates or the like.
A notification point is a point along the travel route where the reservation holder wishes to receive notification regarding the travel of service vehicle 3. At the moment service vehicle 3 passes through a notification point, information regarding the travel of service vehicle 3 is notified to the reservation holder via HMI 41. In this case, information regarding the travel of service vehicle 3 includes, for example, information indicating that service vehicle 3 has passed through a notification point.
Furthermore, when a notification location is entered by the reservation holder, the notification location setting unit 62 transmits the notification location information (notification location information) to the control device 2. In addition to the location entered and specified by the reservation holder, other locations such as intersections, pick-up locations, and drop-off locations can be specified as notification locations.

When the HMI 41 displays the boarding location, boarding date and time, alighting location, alighting date and time, and travel route, the remaining distance setting unit 63 of the first electronic device 4 allows the reservation holder to input the notified remaining distance. The notified remaining distance is input by the reservation holder specifying a numerical value ("m", "km"). Alternatively, the notified remaining distance can be input by the reservation holder using the touch panel to specify the location of a point between the boarding location and the alighting location on the travel route displayed on the HMI 41 where the distance to the alighting location is the desired distance.
The notification remaining distance is the distance (remaining distance) from the current location of the service vehicle 3 to the drop-off location, at the point where the reservation holder wishes to receive notifications regarding the service vehicle 3's movement. The notification remaining distance is the distance at which information regarding the service vehicle 3's movement is notified to the reservation holder via the HMI 41 when the distance from the current location of the service vehicle 3 to the drop-off location reaches the notification remaining distance. In this case, the information regarding the service vehicle 3's movement is, for example, information indicating that the distance from the current location of the service vehicle 3 to the drop-off location has reached the notification remaining distance. Furthermore, when the notification remaining distance is entered by the reservation holder, the remaining distance setting unit 63 transmits the notification remaining distance information (notification remaining distance information) to the control device 2.

When the HMI 41 displays the boarding location, boarding date and time, alighting location, alighting date and time, and travel route, the remaining time setting unit 64 of the first electronic device 4 allows the reservation holder to input the notification remaining time. The notification remaining time is input by the reservation holder specifying a numerical value ("minutes", "seconds"). Alternatively, the notification remaining time can be input by the reservation holder specifying the location of a point on the travel route displayed on the HMI 41, between the boarding location and the alighting location, where the time until the alighting date and time is expected to be the desired time, using the touch panel.
The notification remaining time is the time remaining from the current location of the reservation holder until the service vehicle 3 arrives at the drop-off location, at the point where the reservation holder wishes to receive notifications regarding the service vehicle 3's movement. The notification remaining time is also the time at which information regarding the service vehicle 3's movement is notified to the reservation holder via the HMI 41 when the time remaining until the service vehicle 3 arrives at the drop-off location from its current location becomes the notification remaining time. In this case, the information regarding the service vehicle 3's movement is, for example, information indicating that the time remaining until the service vehicle 3 arrives at the drop-off location from its current location has become the notification remaining time. Furthermore, when the notification remaining time is entered by the reservation holder, the remaining time setting unit 64 transmits the notification remaining time information (notification remaining time information) to the control device 2.

The relationship attribute determination unit 74 determines whether the reservation holder and the user are different based on the reservation holder's identification information received from the first electronic device 4 and the user's identification information included in the reservation information. If the reservation holder and the user are different, the relationship attribute determination unit 74 determines the relationship between the reservation holder and the user by comparing the reservation holder's identification information and the user's identification information with the registrant DB 23. For example, the relationship attribute determination unit 74 determines whether the relationship between the reservation holder and the user is a first relationship (i.e., a relationship where the reservation holder is the legal supervisor of the user, or a relationship where the reservation holder provides care services to the user). Alternatively, for example, the relationship attribute determination unit 74 determines whether the relationship between the reservation holder and the user is a second relationship (i.e., a relationship where the reservation holder is commissioned to make reservations for mobility services on behalf of the user).

The travel plan modification unit 75 permits or prohibits changes to the travel plan by the user (i.e., changes to at least one of the following: boarding location, boarding date and time, alighting location, alighting date and time, or travel route, or setting of intermediate stops) depending on the relationship between the reservation holder and the user.
The travel plan modification unit 75, for example, prohibits changes to the travel plan when the relationship between the reservation holder and the user is a first relationship, and permits changes to the travel plan when the relationship between the reservation holder and the user is a second relationship. The travel plan modification unit 75 may also prohibit changes to the travel plan when the relationship between the reservation holder and the user is neither a first relationship nor a second relationship.
The travel plan modification unit 75 stores restriction information, which is information that permits or prohibits users from changing their travel plan, in the reservation database 25.
When the controller 36 of the service vehicle 3 receives restriction information from the control device 2, it displays on the display screen of the in-vehicle terminal 34 that the user is restricted from changing the travel plan. This allows the user to confirm that they are restricted from changing the travel plan.
Furthermore, if the driving plan modification unit 75 determines that it is preferable to change the driving plan based on map information, driving plan information, the current location of the service vehicle 3, etc., it modifies the driving plan set by the driving plan setting unit 73. Note that the changes to the driving plan by the driving plan modification unit 75 include, for example, changes to the route between the pick-up location and the drop-off location due to accidents, traffic congestion, etc.
Then, when the travel plan modification unit 75 modifies the travel plan set by the travel plan setting unit 73, it transmits information about the modified travel plan (server modification information) to the first electronic device 4 and the second electronic device 5. Furthermore, when the travel plan modification unit 75 receives information including the modified travel plan (user modification information) from the second electronic device 5, it modifies the travel plan set by the travel plan setting unit 73 to the travel plan including the user modification information. Changes to the travel plan by the user include, for example, changes to the route between the boarding location and the alighting location at the user's request, or changes to the route due to accidents or traffic congestion. Changes to the travel plan by the user also include, for example, changes to the alighting location due to changes in the user's actions after alighting.
Then, when the travel plan modification unit 75 changes the travel plan set by the travel plan setting unit 73 to a travel plan that includes user change information, it transmits information about the changed travel plan (travel plan user change information) to the first electronic device 4.

When the notification point passage determination unit 76 receives notification point information from the first electronic device 4, it determines whether the service vehicle 3 has passed the notification point based on the notification point information and the current position of the service vehicle 3. If it determines that the service vehicle 3 has passed the notification point, the notification point passage determination unit 76 transmits information that the service vehicle 3 has passed the notification point (notification point passage information) to the first electronic device 4.
Furthermore, if a boarding location or alighting location is set as a notification point, the notification point passage determination unit 76 transmits information to the first electronic device 4 that the service vehicle 3 has arrived at the boarding location or that the service vehicle 3 has arrived at the alighting location. In addition, if an alighting location is set as a notification point, the notification point passage determination unit 76 may be configured to transmit to the first electronic device 4 information that the service vehicle 3 has arrived at the alighting location, as well as information that the user has alighted from the service vehicle 3 upon arrival at the alighting location.

When the remaining distance determination unit 77 receives the notified remaining distance information from the first electronic device 4, it determines, based on the notified remaining distance information and the current position of the service vehicle 3, whether the distance from the current position of the service vehicle 3 to the drop-off location has reached the notified remaining distance. If it determines that the distance from the current position of the service vehicle 3 to the drop-off location has reached the notified remaining distance, the remaining distance determination unit 77 transmits information (notified remaining distance information) indicating that the distance from the current position of the service vehicle 3 to the drop-off location has reached the notified remaining distance to the first electronic device 4.

When the remaining time determination unit 78 receives remaining time information from the first electronic device 4, it determines, based on the remaining time information and the current position of the service vehicle 3, whether the time until the service vehicle 3 arrives at the drop-off location from its current position has reached the notification remaining time. If the remaining time determination unit 78 determines that the time until the service vehicle 3 arrives at the drop-off location from its current position has reached the notification remaining time, it transmits information (notification remaining time information) indicating that the time until the service vehicle 3 arrives at the drop-off location from its current position has reached the notification remaining time to the first electronic device 4.

Based on the travel plan information and the current location of the service vehicle 3, the delay determination unit 79 calculates the estimated arrival time at the boarding location, which is the time when the service vehicle 3 is expected to arrive at the boarding location, if the service vehicle 3 has not yet arrived at the boarding location. In addition, the delay determination unit 79 refers to the boarding date and time and the estimated arrival time at the boarding location to determine whether the estimated arrival time is later than the boarding date and time (i.e., whether it is predicted that the service vehicle 3 will not arrive at the boarding location at the boarding date and time). If the delay determination unit 79 determines that the estimated arrival time is later than the boarding date and time, it determines whether the delay in the estimated arrival time at the boarding location relative to the boarding date and time (in minutes or seconds) exceeds a preset first delay time (for example, 5 minutes). The first delay time is set, for example, by the person who made the reservation or by the control device 2.
If the delay in the estimated arrival time at the boarding location relative to the boarding date and time exceeds the first delay time, the delay determination unit 79 transmits information including the delay in the estimated arrival time at the boarding location relative to the boarding date and time (vehicle boarding location arrival delay time information) to the first electronic device 4.
Furthermore, based on the travel plan information and the current position of the second electronic device 5, the delay determination unit 79 calculates the estimated time of user arrival, which is the time when the second electronic device 5 is expected to arrive at the boarding location, if the second electronic device 5 (user) has not yet arrived at the boarding location. In addition, the delay determination unit 79 refers to the boarding date and time and the estimated time of user arrival to determine whether the estimated time of user arrival is later than the boarding date and time (i.e., whether the user will not arrive at the boarding location at the boarding date and time). If the delay determination unit 79 determines that the estimated time of user arrival is later than the boarding date and time, it determines whether the delay (in minutes or seconds) of the estimated time of user arrival relative to the boarding date and time exceeds the first delay time.
The first delay time, which is compared with the estimated arrival time of the vehicle at the boarding location relative to the boarding date and time, and the first delay time, which is compared with the estimated arrival time of the user relative to the boarding date and time, may be set to the same time or to different times. If the delay in the estimated arrival time of the user relative to the boarding date and time exceeds the first delay time, the delay determination unit 79 transmits information including the delay in the estimated arrival time of the user relative to the boarding date and time (user boarding location arrival delay time information) to the first electronic device 4.
Furthermore, based on the travel plan information and the current positions of the service vehicle 3 and the second electronic device 5, the delay determination unit 79 calculates the estimated arrival time at the drop-off location, which is the time when the service vehicle 3 is expected to arrive at the drop-off location, if the service vehicle 3 has not yet arrived at the drop-off location. In addition, the delay determination unit 79 refers to the drop-off date and time and the estimated arrival time at the drop-off location to determine whether the estimated arrival time is later than the drop-off date and time (i.e., whether it is predicted that the service vehicle 3 will not arrive at the drop-off location at the drop-off date and time). If the delay determination unit 79 determines that the estimated arrival time is later than the drop-off date and time, it determines whether the delay (in minutes or seconds) of the estimated arrival time at the drop-off location relative to the drop-off date and time exceeds a pre-set second delay time (for example, 5 minutes). The second delay time is set, for example, by the person who made the reservation or by the control device 2. If the delay in the estimated arrival time of the vehicle at the drop-off location relative to the drop-off date and time exceeds the second delay time, the delay determination unit 79 transmits information including the delay in the estimated arrival time of the vehicle at the drop-off location relative to the drop-off date and time (vehicle drop-off location arrival delay time information) to the first electronic device 4.

When the notification receiving unit 65 receives notification point passage information from the control device 2, it displays a message on the display device of the HMI 41 of the first electronic device 4 indicating that the service vehicle 3 has passed the notification point. This allows the person who made the reservation to confirm that the service vehicle 3 has passed the notification point, which was set in advance by the person who made the reservation, as information regarding the movement of the service vehicle 3.
Furthermore, when the notification receiving unit 65 receives notification remaining distance information from the control device 2, it displays a message on the display device of the HMI 41 of the first electronic device 4 indicating that the distance from the current position of the service vehicle 3 to the drop-off location has become the notification remaining distance. This allows the person who made the reservation to confirm that the distance from the current position of the service vehicle 3 to the drop-off location has become the notification remaining distance, as information regarding the travel of the service vehicle 3, at the moment the distance from the current position of the service vehicle 3 to the drop-off location reaches the notification remaining distance set by the person who made the reservation.
Furthermore, when the notification receiving unit 65 receives notification remaining time information from the control device 2, it displays a message on the display device of the HMI 41 of the first electronic device 4 indicating that the time until the service vehicle 3 arrives at the drop-off location from its current location has reached the notification remaining time. This allows the person who made the reservation to confirm, as information regarding the operation of the service vehicle 3, that the time until the service vehicle 3 arrives at the drop-off location from its current location has reached the notification remaining time set by the person who made the reservation.
Furthermore, when the notification receiving unit 65 receives information on the vehicle's arrival delay time from the control device 2, it displays a message on the display device of the HMI 41 of the first electronic device 4 indicating that the service vehicle 3 is expected to arrive at the boarding location a delay equal to the delay from the boarding date and time. This allows the person with a reservation to confirm, at the time when it is predicted that the service vehicle 3 will arrive later than the predicted arrival time at the boarding location, by more than the first delay time, that the service vehicle 3 is expected to arrive at the boarding location a delay equal to the delay from the boarding date and time, as information regarding the operation of the service vehicle 3.
Furthermore, when the notification receiving unit 65 receives information on the delay time of the user's arrival at the boarding location from the control device 2, it displays a message on the display device of the HMI 41 of the first electronic device 4 indicating that the second electronic device 5 (user) is expected to arrive at the boarding location a delay of the amount of the delay from the boarding date and time. This allows the person with a reservation to confirm, at the time when it is predicted that the user will arrive later than the predicted arrival time at the boarding location, that the information regarding the operation of the service vehicle 3 indicates that the user is expected to arrive at the boarding location a delay of the amount of the delay from the boarding date and time.
Furthermore, when the notification receiving unit 65 receives information on the delay time of arrival at the vehicle drop-off location from the control device 2, it displays a message on the display device of the HMI 41 of the first electronic device 4 indicating that the service vehicle 3 is expected to arrive at the drop-off location a delay equal to the delay time from the drop-off date and time. This allows the person with the reservation to confirm, as information regarding the operation of the service vehicle 3, that the service vehicle 3 is expected to arrive at the drop-off location a delay equal to the delay time from the drop-off date and time, when it is predicted that the service vehicle 3 will arrive more than the second delay time than the predicted arrival time at the drop-off location.
Furthermore, when the notification receiving unit 65 receives server change information from the control device 2, it displays a message on the display device of the HMI 41 of the first electronic device 4 indicating that the travel plan set by the travel plan setting unit 73 has been changed by the control device 2. In addition, it displays the drop-off location, drop-off date and time, and travel route according to the changed travel plan. This allows the person who made the reservation to confirm that the travel plan set by the travel plan setting unit 73 has been changed by the control device 2 as information regarding the travel of the service vehicle 3 at the time the travel plan is changed by the control device 2.
Furthermore, when the notification receiving unit 65 receives travel plan user change information from the control device 2, it displays a message on the display device of the HMI 41 of the first electronic device 4 indicating that the travel plan set by the travel plan setting unit 73 has been changed by the user. In addition, it displays the drop-off location, drop-off date and time, and travel route according to the changed travel plan. This allows the person who made the reservation to confirm, as information regarding the travel of the service vehicle 3, that the travel plan set by the travel plan setting unit 73 has been changed by the user at the time the travel plan has been changed by the user.

When the second electronic device 5 receives restriction information from the control device 2, it displays the restriction status of changes to the travel plan on the display device of the HMI 52 for the user. This allows the user to confirm that changes to the travel plan are restricted.
To accommodate situations where a user wishes to change their travel plan, it may be possible to allow the user to request approval from the reservation holder for changing the travel plan. In this case, the travel plan change setting unit 81 receives a request operation from the user to request approval for changing the travel plan, for example, via the HMI 52. Upon receiving the request operation from the user, it transmits approval request information to the first electronic device 4. The approval request information may also be transmitted to the first electronic device 4 via the control device 2. Alternatively, the user may request approval for changing the travel plan by operating the in-vehicle terminal 34.

Furthermore, if the reservation holder approves a change to the travel plan, the travel plan setting unit 73 reflects the user's requested change to the travel plan in the service vehicle 3's travel plan. The travel plan setting unit 73 stores the changed travel plan in the reservation DB 25. The travel plan setting unit 73 also transmits the changed travel plan to the service vehicle 3. The controller 36 drives the service vehicle 3 according to the changed travel plan. Changes to the travel plan by the user include, for example, changes to the route between the pick-up location and the drop-off location due to the user's wishes, accidents, traffic congestion, etc., or changes to the drop-off location due to changes in the user's actions after drop-off.
On the other hand, if the first electronic device 4 receives a denial operation from the reservation holder, it does not transmit approval information to the control device 2. As a result, the restriction on changing the travel plan for the user is not lifted. In this case, denial information informing the user that the use of the travel plan change has been denied may be transmitted to the second electronic device 5. The denial information may be transmitted to the second electronic device 5 via the control device 2. When the second electronic device 5 receives the denial information from the first electronic device 4, it may display a notification on the display device of the HMI 52 informing the reservation holder that the use of the travel plan change has been denied.
Furthermore, when the second electronic device 5 receives server change information from the control device 2, it displays a message on the HMI 52's display device indicating that the travel plan set by the travel plan setting unit 73 has been changed by the control device 2. In addition, it displays the disembarking location, disembarking date and time, and travel route according to the changed travel plan. This allows the user to confirm that the travel plan set by the travel plan setting unit 73 has been changed by the control device 2.

(operation)
Figure 3 is a sequence diagram illustrating an example of the operation of the mobility service provision system 1 when booking a mobility service.
In step S1, the first electronic device 4 accepts the operation of the reservation holder to log in to the control device 2. In step S2, the reservation holder information transmission unit 60 transmits the reservation holder's identification information to the control device 2. In step S3, the control device 2 authenticates the reservation holder based on the received identification information.

In step S4, the reservation information generation unit 61 generates reservation information that includes user identification information and information on the boarding location, boarding date and time, and alighting location, based on the input operation of the person making the reservation. In step S5, the reservation information generation unit 61 transmits the reservation information to the control device 2. In step S6, the reservation setting unit 70 of the control device 2 sets the reservation for the mobility service for the user specified in the reservation information.
In other words, a person making a reservation can book a transportation service if the relationship between the person making the reservation and the user is a predetermined relationship set in advance.
In step S7, the reservation setting unit 70 transmits reservation notification information to the second electronic device 5 informing the user that a mobility service has been reserved. In step S8, the location information acquisition unit 80 starts transmitting the current location information of the second electronic device 5.

In step S9, the service vehicle 3 transmits its current location information. In step S10, the dispatch unit 72 determines which service vehicle 3 to provide to the user based on the pick-up location included in the reservation information and the current location of the service vehicle 3. The travel plan setting unit 73 calculates the travel route for the service vehicle 3 from the pick-up location to the drop-off location, and the expected drop-off date and time.
In step S11, the driving plan setting unit 73 transmits the driving plan information for the service vehicle 3 to the service vehicle 3. In step S12, the relationship attribute determination unit 74 determines whether the person who made the reservation and the user are different. If the person who made the reservation and the user are different, the driving plan modification unit 75 performs a relationship determination process to allow or prohibit the user from changing the driving plan, depending on the relationship between the person who made the reservation and the user.

In step S13, the travel plan modification unit 75 transmits restriction information, which is information that restricts the user from changing the travel plan, to the service vehicle 3, the first electronic device 4, and the second electronic device 5. The controller 36 restricts the user from changing the travel plan according to the restriction information. In step S14, the second electronic device 5 displays the travel plan change restriction status to the user on the HMI 52 display device.

Figure 4 is a sequence diagram illustrating an example of the operation when using the mobility service. Note that the operation in Figure 4 begins before the service vehicle 3 and the user have arrived at the boarding location.
In step S20, the delay determination unit 79 calculates the estimated arrival time at the boarding location (estimated arrival time at the vehicle boarding location and estimated arrival time of the user).
In step S21, the delay determination unit 79 determines whether the delay in the estimated arrival time of the vehicle at the boarding location relative to the boarding date and time (arrival delay time) exceeds the first delay time. In addition, it determines whether the delay in the estimated arrival time of the user relative to the boarding date and time (arrival delay time) exceeds the first delay time. If the arrival delay time exceeds the first delay time (step S21: Y), the process proceeds to step S22. If the arrival delay time does not exceed the first delay time (step S21: N), the process proceeds to step S23.
In step S22, the notification receiving unit 65 receives at least one of the vehicle boarding location arrival delay information and the user boarding location arrival delay information from the control device 2. When the notification receiving unit 65 receives the vehicle boarding location arrival delay information, a message is displayed on the HMI 41 display device indicating that the service vehicle 3 is expected to arrive at the boarding location with a delay equal to the boarding date and time. Also, when the notification receiving unit 65 receives the user boarding location arrival delay information, a message is displayed on the HMI 41 display device indicating that the second electronic device 5 (user) is expected to arrive at the boarding location with a delay equal to the boarding date and time.
In step S23, the user boards the service vehicle 3 at the boarding location specified in the reservation information. At that time, the user performs an authentication operation to use the mobility service using the second electronic device 5.
When the authentication operation is performed, in step S24, the second electronic device 5 transmits the user's identification information to the control device 2. In steps S23 and S24, the authentication operation may be performed using the in-vehicle terminal 34 installed in the service vehicle 3 instead of the second electronic device 5.

In step S25, the control device 2 authenticates the user based on the identification information.
In other words, when a user boards the service vehicle 3, the user is authenticated based on the user's information (user identification information).
If user authentication is successful, in step S26 the control device 2 transmits authentication completion notification information to the service vehicle 3.
In step S27, when the controller 36 receives the authentication completion notification information, it starts the service vehicle 3 and begins driving it toward the drop-off location according to the driving plan received from the control device 2.
In step S28, the delay determination unit 79 calculates the estimated arrival time at the disembarking location (estimated arrival time at the vehicle disembarking location).
In step S29, the delay determination unit 79 determines whether the delay in the estimated arrival time at the vehicle disembarkation location relative to the disembarkation date and time (arrival delay time) exceeds the second delay time. If the arrival delay time exceeds the second delay time (step S29: Y), the process proceeds to step S30. If the arrival delay time does not exceed the second delay time (step S29: N), the process proceeds to step S31.
In step S30, the notification receiving unit 65 receives vehicle arrival delay information from the control device 2. When the notification receiving unit 65 receives the vehicle arrival delay information, a message is displayed on the HMI 41 display device indicating that the service vehicle 3 is expected to arrive at the arrival location with a delay equal to the delay from the arrival date and time.
In step S31, the service vehicle 3 arrives at the drop-off location, and in step S32, the user alights from the service vehicle 3. In step S33, the sensor 30 of the service vehicle 3 transmits information that the user has alighted from the service vehicle 3 to the control device 2. This information is generated using, for example, the current location of the service vehicle 3 and vehicle status information detected by the seat belt sensor and door sensor.
In step S34, the control device 2 transmits information to the first electronic device 4 that a user has disembarked from the service vehicle 3 that has arrived at the disembarking location.
In step S35, the notification receiving unit 65 receives information from the control device 2 that the user has disembarked from the service vehicle 3 which has arrived at the disembarking location, as information that the user has completed disembarking. When the notification receiving unit 65 receives information from the service vehicle 3 that the user has disembarked, a message indicating that the user has disembarked at the disembarking location is displayed on the display device of the HMI 41.

Figure 5 is a sequence diagram illustrating an example of the operation when using the mobility service. Note that the operation in Figure 5 begins while the service vehicle 3, in which the user is riding, is in motion.
In step S40, the person making the reservation enters the notification location into the notification location setting unit 62. In step S41, the control device 2 obtains the notification location from the notification location information. In step S42, the control device 2 obtains the current location of the service vehicle 3.
In step S43, the notification point passage determination unit 76 determines whether the service vehicle 3 has passed the notification point based on the notification point and the current position of the service vehicle 3. If the service vehicle 3 has passed the notification point (step S43: Y), the process proceeds to step S44. If the service vehicle 3 has not passed the notification point (step S43: N), the process in step S43 is repeated.
In step S44, the notification receiving unit 65 receives notification point passage information from the control device 2. When the notification receiving unit 65 receives notification point passage information, a message indicating that the service vehicle 3 has passed the notification point is displayed on the display device of the HMI 41 of the first electronic device 4.

Figure 6 is a sequence diagram illustrating an example of the operation when using the mobility service. Note that the operation in Figure 6 begins while the service vehicle 3, in which the user is riding, is in motion.
In step S50, the communication device 22 receives traffic congestion information for the driving route calculated by the driving plan setting unit 73.
If it is determined that it is preferable to change the driving plan, in step S51 the driving plan change unit 75 changes the driving plan set by the driving plan setting unit 73 according to the traffic congestion information received in step S50 and transmits the server change information to the first electronic device 4.
In step S52, the notification receiving unit 65 receives server change information from the control device 2. When the notification receiving unit 65 receives the server change information, a message indicating that the travel plan has been changed by the control device 2 is displayed on the display device of the HMI 41. In addition, the disembarking location, disembarking date and time, and travel route corresponding to the changed travel plan are displayed.
In step S53, the controller 36 causes the service vehicle 3 to travel along the route that was changed in step S51.
If, while the service vehicle 3 is in motion, the user changes the route via the route plan change setting unit 81 in step S54, the route plan change unit 75 receives user change information from the second electronic device 5 in step S55 and changes the route plan changed in step S55 to a route plan that includes the user change information. Furthermore, it transmits the user change information to the first electronic device 4.
In step S56, the notification receiving unit 65 receives user change information from the control device 2. When the notification receiving unit 65 receives user change information, a message indicating that the travel plan has been changed by the user is displayed on the display device of the HMI 41. In addition, the disembarking location, disembarking date and time, and travel route corresponding to the changed travel plan are displayed.
In step S57, the controller 36 causes the service vehicle 3 to travel along the route that was changed in step S55.

(Effects of the embodiment)
(1) The mobility service provision system 1 that operates the vehicle, the mobility service provision method, and the mobility service provision device include a service vehicle 3 used for the mobility service and a control device 2 that receives reservation information, which includes at least information about the user receiving the mobility service, from a first electronic device 4, which is a terminal device operated by a person making a reservation for the mobility service, and arranges for the service vehicle 3 to be used by the user according to the reservation information. The control device 2 includes a registrant DB 23 that stores information about registrants who have been registered in advance to use the mobility service provision system and information about the relationship between registrants, and when the person making the reservation and the user are in a predetermined relationship set in advance, it notifies the person making the reservation (first electronic device 4) of information about the operation of the service vehicle 3 at a predetermined notification timing.
This ensures that information regarding the service vehicle 3's operation is notified to the reservation holder at a predetermined notification timing, only when the reservation holder and the user have a predetermined relationship. Therefore, it is possible to reduce the burden on the reservation holder when notifying them of information while the user is riding in the service vehicle 3.

(2) The notification timing will be at least one of the timing set by the reservation holder and the timing according to the usage status of the mobility service.
As a result, information regarding the operation of the service vehicle 3 is notified to the reservation holder at at least one of the following times: at a time arbitrarily set by the reservation holder or at a time corresponding to the usage status of the mobility service, thereby reducing the burden on the reservation holder.

(3) The timing set by the reservation holder is the timing when the service vehicle 3 passes over the point set by the reservation holder in advance.
This allows the reservation holder to receive notification about the service vehicle's movement when the service vehicle passes a pre-set notification point, thereby reducing the burden on the reservation holder.

(4) The timing set by the reservation holder is at least one of the following: when the remaining time until the estimated arrival time at the drop-off location reaches the time set in advance by the reservation holder, and when the remaining distance until the service vehicle 3 arrives at the drop-off location reaches the distance set in advance by the reservation holder.
This allows the reservation holder to receive information about the service vehicle 3's movements at a time pre-set by the reservation holder, before the service vehicle 3 arrives at the drop-off location, thereby reducing the burden on the reservation holder.

(5) The timing according to the usage status of the mobility service is the timing at which it is predicted that at least one of the user and the service vehicle 3 will arrive later than the predicted arrival time at the boarding location by more than the first delay time, or the timing at which it is predicted that the service vehicle 3 will arrive later than the predicted arrival time at the disembarking location by more than the second delay time.
This allows the person who made the reservation to be notified of information regarding the service vehicle 3's movements before the user or service vehicle 3 arrives at the boarding location, and before the service vehicle 3 arrives at the drop-off location, thereby reducing the burden on the person who made the reservation.

(6) The timing corresponding to the usage status of the mobility service is the timing when the driving plan of the service vehicle 3 is changed by the control device 2 or the user.
This means that when the travel route is changed, the person who made the reservation will be notified of information regarding the travel of service vehicle 3. If the travel route is not changed, no information will be sent, thus reducing the burden on the person who made the reservation.

(7) A reservation for a mobility service can be made if the relationship between the reservation holder and the user is as specified.
This makes it possible to prohibit the provision of transportation services if the relationship between the person making the reservation and the user is deemed inappropriate for the use of transportation services.

(8) When a user boards service vehicle 3, the user is authenticated based on the user's information.
This makes it possible to interrupt the provision of transportation services if the user's information differs from the reservation information, or if the relationship between the reservation holder and the user is not a predetermined one.

1…Mobile service provision system, 2…Control device, 3…Service vehicle, 4…First electronic device, 5…Second electronic device, 20, 38, 43, 54…Processor, 21, 39, 44, 55…Storage device, 22, 33, 40, 51…Communication device, 23…Registered user database, 24, 32…Map database, 25…Reservation database, 30…Sensor, 31, 50…Positioning device, 34…In-vehicle terminal, 35…In-vehicle equipment, 36, 42, 53…Controller, 37…Actuator, 41, 5 2…Human-machine interface, 60…Reservation information transmission unit, 61…Reservation information generation unit, 62…Notification point setting unit, 63…Remaining distance setting unit, 64…Remaining time setting unit, 65…Notification reception unit, 70…Reservation setting unit, 71…Location information acquisition unit, 72…Vehicle dispatch unit, 73…Driving plan setting unit, 74…Relationship attribute determination unit, 75…Driving plan change unit, 76…Notification point passage determination unit, 77…Remaining distance determination unit, 78…Remaining time determination unit, 79…Delay determination unit, 80…Location information acquisition unit, 81…Driving plan change setting unit

Claims (5)

A mobility service provision system that operates vehicles,
Vehicles used for the aforementioned mobility service,
A control device that receives reservation information, which includes at least information of the user receiving the mobility service, from an electronic device that is a terminal device operated by the person making the reservation for the mobility service, and arranges a vehicle for use by the user according to the reservation information,
Equipped with,
The control device is
The system includes a user database that stores registered users who have been pre-registered to use the aforementioned mobile service provision system, and relationship attribute information indicating the relationships between such registered users.
Based on the relationship attribute information stored in the registered user database , it is determined whether the reservation holder and the user have a predetermined relationship, and if the reservation holder and the user have a predetermined relationship , the electronic device is notified of information regarding the vehicle's operation at a predetermined notification timing.
The notification timing is the timing when the vehicle passes a point arbitrarily set in advance by the person who made the reservation.
A mobility service provision system characterized in that the location in question includes any location other than the boarding/alighting point. The mobility service provision system according to claim 1 , characterized in that it is possible to make a reservation for the mobility service when the relationship between the person making the reservation and the user is the predetermined relationship. The mobility service provision system according to claim 1 , characterized in that when the user boards the vehicle, the system authenticates the user based on the user's information. A method of providing mobility services by operating vehicles,
Registered users who have been registered in advance to use the aforementioned mobile service provision method, and relationship attribute information indicating the relationships between such registered users, are stored in advance in the registered user database.
An electronic device, which is a terminal device operated when making a reservation for the aforementioned mobility service, receives an operation from the person making the reservation for the mobility service and transmits reservation information, which includes at least the information of the user receiving the mobility service, to a control device.
The control device,
In accordance with the aforementioned reservation information, a vehicle will be arranged for use by the aforementioned user.
Based on the relationship attribute information stored in the registered user database , it is determined whether the reservation holder and the user have a predetermined relationship, and if the reservation holder and the user have a predetermined relationship , the reservation holder is notified of information regarding the vehicle's operation at a predetermined notification timing.
The notification timing is the timing when the vehicle passes a point arbitrarily set in advance by the person who made the reservation.
A method for providing mobility services, characterized in that the location in question includes any location other than the boarding/alighting point. A mobile service provider device that operates vehicles,
Registered users who have been registered in advance to use the aforementioned mobile service provider, and relationship attribute information indicating the relationship between said registered users, are pre-stored in the registered user database.
An electronic device, which is a terminal device operated when making a reservation for the aforementioned mobility service, receives an operation from the person making the reservation for the mobility service and transmits reservation information, which includes at least the information of the user receiving the mobility service, to a control device.
The process of arranging a vehicle for use by the user in accordance with the aforementioned reservation information,
Based on the relationship attribute information stored in the registered user database , it is determined whether the reservation holder and the user have a predetermined relationship, and if the reservation holder and the user have a predetermined relationship , the reservation holder is notified of information regarding the vehicle's operation at a predetermined notification timing.
Equipped with a computer that runs,
The notification timing is the timing when the vehicle passes a point arbitrarily set in advance by the person who made the reservation.
A mobility service provider characterized in that the said location includes any location other than the boarding/alighting point.