WO2025120863A1 - Information processing device and information processing method - Google Patents

Abstract

An information processing device (2) is provided with a controller (22) that executes: processing (S6) for identifying a user (U1) who uses a vehicle dispatch service; processing (S6) for determining whether or not the identified user (U1) is an approvee user requiring approval by an approver user (U2), who is a user other than the user identified for the use of the vehicle dispatch service; and when the identified user (U1) is an approvee user, processing (S1-3, S7) for presenting the approvee user (U1) with usage place candidates approved by the approver user (U2) from among usage place candidates, which are candidates determined in advance to be usage places of the vehicle dispatch service.

Description

Information processing device and information processing method

The present invention relates to an information processing device and an information processing method.

The following Patent Document 1 describes a vehicle monitoring system that allows guardians to check the riding status of the person they are monitoring in real time.

JP 2022-069033 A

The above-mentioned Patent Document 1 does not disclose how to set a location where the person being watched over uses the vehicle transportation service. Therefore, there is a risk that the person being watched over will use the vehicle transportation service in an inappropriate location.
The present invention aims to restrict an approved user, who requires approval from an approver user to use a vehicle dispatch service, from using the vehicle dispatch service in a location not intended by the approver user.

An information processing device according to one embodiment of the present invention includes a controller that executes the following processes: identifying a user who uses a ride-hailing service; determining whether the identified user is an approved user who requires approval for use of the ride-hailing service from an approver user who is a user other than the identified user; and, if the identified user is an approved user, presenting to the approved user potential usage locations approved by the approver user from among potential usage location locations that are predetermined candidates for usage locations of the ride-hailing service.

According to the present invention, an approved user who requires approval from an approver user to use a vehicle dispatch service can be restricted from using the vehicle dispatch service in a location not intended by the approver user.
The objects and advantages of the invention will be realized and attained by means of the elements and combinations recited in the appended claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed.

1 is a schematic configuration diagram of an example of a vehicle dispatch service providing system according to an embodiment; FIG. 2 is a sequence diagram of an example of processing in the vehicle dispatch service providing system of FIG. 1 . 3A and 3B are diagrams showing an example of a GUI of an approver terminal in the first embodiment, and FIG. 3C is a diagram showing an example of a GUI of an approved party terminal. 4 is a flowchart of an example of an information processing method according to the first embodiment. 13A and 13B are diagrams showing an example of a GUI of an approver terminal in the second embodiment, and 13C is a diagram showing an example of a GUI of a proxy approver terminal. 13 is a flowchart of an example of an information processing method according to a second embodiment. 13A to 13C are diagrams showing an example of a GUI of an approver terminal in the third embodiment. 13 is a flowchart illustrating an example of an information processing method according to a third embodiment. 13A to 13C are diagrams showing an example of a GUI of an approver terminal in the fourth embodiment. 13 is a flowchart of an example of an information processing method according to the fourth embodiment.

First Embodiment
(composition)
1 is a schematic configuration diagram of an example of a vehicle dispatch service providing system according to an embodiment. The vehicle dispatch service providing system 1 is a system that provides a vehicle dispatch service (passenger transportation service) that moves users by operating a vehicle 3. In this specification, the vehicle 3 provided for the vehicle dispatch service by the vehicle dispatch service providing system 1 is referred to as a "service vehicle", and the vehicle dispatch service provided by the vehicle dispatch service providing system 1 is simply referred to as a "vehicle dispatch service". The vehicle dispatch service providing system 1 includes a server device 2, a service vehicle 3, an approved person terminal 4, and an approver terminal 5.

The terminal for the person to be approved 4 and the terminal for the person to be approved 5 are terminal devices operated by the users U1 and U2 who use the vehicle dispatch service. The terminal for the person to be approved 4 and the terminal for the person to be approved 5 have dedicated application software (hereinafter sometimes referred to as "vehicle dispatch software") installed therein for using the vehicle dispatch service.
Here, user U1 is a user who requires approval from user U2 to use the vehicle dispatch service. In the following description, user U1 may be referred to as "approved user U1" and user U2 may be referred to as "approver user U2". For example, approved user U1 may be a protected person such as a minor (e.g., a child) under a certain age or a person receiving care such as an elderly person. For example, approver user U2 may be a guardian including the parents of a minor of approved user U1 or a caregiver who cares for an elderly person. In the following description, users of the vehicle dispatch service, including user U1 and user U2, may be collectively referred to as "user U".

The approved person terminal 4 is, for example, a portable information terminal that the approved person user U1 can carry with him or a small computer that is easily portable. If the approved person user U1 does not own such a terminal device, it may be a terminal device (for example, a tablet terminal or a small computer) located in a facility (for example, a public facility) used by the approved person user U1. The approved person user U1 reserves a car dispatch service using car dispatch software executed on the approved person terminal 4.

The approved party terminal 4 includes a communication device 40 , a human machine interface (HMI) 41 , and a controller 42 .
The communication device 40 provides a communication function between the approval recipient terminal 4 and the server device 2. The HMI 41 is an interface device that transmits and receives information between the approval recipient terminal 4 and the approval recipient user U1. The HMI 41 includes a display device that can be seen by the approval recipient user U1, and a speaker and a buzzer that output auditory information. The HMI 41 also includes operators (e.g., buttons, switches, levers, dials, keyboards, touch panels, etc.) and a voice input device that accepts operational inputs to the approval recipient terminal 4 by the approval recipient user U1.

The controller 42 is an electronic control unit (ECU) that controls the operation of the recipient terminal 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 a register, cache memory, ROM (Read Only Memory), or RAM (Random Access Memory). The functions of the recipient terminal 4 described below are realized, for example, by the processor 43 executing a computer program stored in the storage device 44.

The approver terminal 5 is, for example, a portable information terminal that the approver user U2 can carry with him or a small computer that is easy to carry. The approver user U2 uses the vehicle dispatch software executed on the approver terminal 5 to reserve a vehicle dispatch service. The approver user U2 also uses the vehicle dispatch software executed on the approver terminal 5 to approve the location where the approved user U1 can use the vehicle dispatch service.

In the following explanation, the location where the approved user U1 uses the car dispatch service is the boarding and disembarking point where the approved user U1 boards and disembarks the service vehicle 3, but the location where the car dispatch service is used in this invention is not limited to the boarding and disembarking point. The location where the car dispatch service is used in this invention includes the travel route (linear space) where the approved user U1 travels in the service vehicle 3, and the travel area (linear space) where the approved user U1 travels in the service vehicle 3.

The approver terminal 5 includes a positioning device 50 , a communication device 51 , an HMI 52 , and a controller 53 .
The positioning device 50 measures the current location of the approver terminal 5 (i.e., the current location of the approver user U2). The positioning device 50 may include, for example, a Global Navigation System (GNSS) receiver. The GNSS receiver may be, for example, a Global Positioning System (GPS) receiver or the like.
The communication device 51 provides a communication function between the approver terminal 5 and the server device 2. The HMI 52 is an interface device that transmits and receives information between the approver terminal 5 and the approver user U2. The HMI 52 includes a display device that can be seen by the approver user U2, and a speaker and a buzzer that output auditory information. The HMI 52 also includes an operator and a voice input device that accepts operational input to the approver terminal 5 by the approver user U2.

The controller 53 is an ECU that controls the operation of the approver terminal 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 non-transitory tangible storage media such as a register, cache memory, ROM, or RAM. The functions of the approver terminal 5 described below are realized, for example, by the processor 54 executing a computer program stored in the storage device 55.

The server device 2 is an information processing device that receives reservation information from the approved party terminal 4 and the approver terminal 5, and arranges a service vehicle 3 to be provided for use by the user U in accordance with the reservation information. The server device 2 is an example of the "information processing device" described in the claims. The server device 2 includes a communication device 20, a database 21, and a controller 22.
The communication device 20 provides a communication function between the server device 2 and the service vehicle 3, the approved person's terminal 4, and the approver's terminal 5.
Various information used for providing the vehicle dispatch service is stored in the database 21. For example, the database 21 stores information about the user U of the vehicle dispatch service, a map database of the business area in which the vehicle dispatch service providing system 1 provides the vehicle dispatch service, information about the boarding and disembarking points where the user U can board and disembark the service vehicle 3, and information about events held in the business area.

The controller 22 includes a processor 23 and peripheral components such as a storage device 24. The processor 23 may be, for example, a CPU or an MPU. The storage device 24 may include a register, a cache memory, or a non-transitory tangible storage medium such as a ROM or RAM. The functions of the server device 2 described below are realized by, for example, the processor 23 executing a computer program stored in the storage device 24.

The service vehicle 3 is a vehicle (a so-called demand-based transportation vehicle) that operates in response to a request from the user U, and may be, for example, a shared taxi or a robot taxi. For example, the service vehicle 3 may be an autonomous vehicle that is automatically driven by the controller 36 according to route information transmitted from the server device 2 without the involvement of a driver. When the service vehicle 3 receives a driving plan from the server device 2, it drives to the boarding location so as to arrive at the boarding date and time included in the driving plan. When the user U gets on the service vehicle 3 at the boarding location, it drives to the disembarking location included in the driving plan.
In the following description, a case will be described in which the service vehicle 3 is an autonomous vehicle, but the present invention is not limited thereto, and the service vehicle 3 may be a manually driven vehicle driven by a driver (human). In this case, the service vehicle 3 may present the route information transmitted from the server device 2 to the driver, thereby assisting the driver in driving the service vehicle 3 according to the route information.

The service vehicle 3 includes a sensor 30 , a positioning device 31 , a map database (map DB) 32 , a communication device 33 , 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 state) obtained from the service vehicle 3. For example, the object sensor may include a distance measuring device such as a laser range finder (LRF), a radar, or a LiDAR (Light Detection and Ranging) laser radar. The object sensor outputs surrounding environment information, which is information on the detected surrounding environment of the service vehicle 3, to the controller 36. For example, the vehicle sensor may include a vehicle speed sensor, a wheel speed sensor, a three-axis acceleration sensor, a steering angle sensor, a gyro sensor, and a yaw rate sensor. The vehicle sensor outputs vehicle state information related to the vehicle state of the service vehicle 3 to the controller 36.

The positioning device 31 measures the current position and attitude of the service vehicle 3. The positioning device 31 may be equipped with a GNSS receiver, for example. The GNSS receiver may be, for example, a GPS receiver. The positioning device 31 outputs current position information of the measured current position to the controller 36. The map DB 32 stores map information. The map information may include map data for navigation and high-precision map data suitable as a map for autonomous driving. The communication device 33 provides a communication function between the service vehicle 3 and the server device 2.

The controller 36 is an electronic control unit that controls the service vehicle 3. For example, the controller 36 controls the autonomous driving 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 a non-transitory tangible storage medium such as a register, a cache memory, a ROM, or a RAM. 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 executes autonomous driving control to drive the service vehicle 3 according to the driving plan based on the surrounding environment information and vehicle state information from the sensor 30, the positioning result of the positioning device 31, and the map information of the map DB 32. For example, the controller 36 calculates a target driving trajectory for driving 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. For example, the controller 36 generates a route space map that represents the route around the service vehicle 3 and the presence or absence of objects, and a risk map that quantifies the risk of the driving field, and generates a target driving trajectory for driving the service vehicle 3 based on the motion characteristics of the service vehicle 3, the vehicle state information, the route space map, and the risk map. The controller 36 drives the actuator 37 so that the service vehicle 3 drives along the generated target driving trajectory. The actuator 37 operates the steering device, drive device, and brake device of the service vehicle 3 in response to a control signal from the controller 36 to generate the vehicle behavior of the service vehicle 3, thereby automatically driving the service vehicle 3. The actuator 37 includes a steering actuator, an accelerator opening actuator, and a brake control actuator.

2 is a sequence diagram of an example of processing in the vehicle dispatch service providing system 1. In step S1, the approver user U2 performs an operation on the approver terminal 5 to approve candidate boarding and alighting locations (hereinafter sometimes referred to as "candidate boarding and alighting locations") that can be used by the approved user U1 among the boarding and alighting locations of the vehicle dispatch service. The approver terminal 5 accepts a selection input of the candidate boarding and alighting locations approved by the approver user U2. In the following description, the candidate boarding and alighting locations approved by the approver user U2 as the candidate boarding and alighting locations that can be used by the approved user U1 may be referred to as "approved candidate boarding and alighting locations."
In step S2, the approver terminal 5 transmits to the server device 2 a registration request signal requesting that the approved candidate boarding/alighting points be registered in the database 21.

In step S3, the server device 2 newly registers (adds) the approved candidate boarding/alighting point designated in the registration request signal from the approver terminal 5 as a boarding/alighting point available to the approved user U1 in the database 21. For example, the server device 2 may store in the database 21 the identification information of the approved candidate boarding/alighting point in association with the identification information of the approved user U1.
In step S4, the approval-subject terminal 4 accepts a login operation by the approval-subject user U1. In step S5, the approval-subject terminal 4 transmits user information of the approval-subject user U1 to the server device 2. The user information may include identification information of the approval-subject user U1.

In step S6, the server device 2 authenticates the approval-recipient user U1 based on the user information. At this time, the server device 2 determines whether the approval-recipient user U1 is an approval-recipient who requires approval from another user for using the vehicle dispatch service based on the user registration information of the approval-recipient user U1 registered in the database 21. For example, the database 21 may store information indicating whether the approval-recipient user U1 is an approval-recipient in association with the identification information of the approval-recipient user U1.
In step S7, the server device 2 transmits candidate boarding and alighting location information regarding boarding and alighting locations of the vehicle dispatch service to the approved person's terminal 4. When the approved person user U1 is the approved person, the server device 2 transmits candidate boarding and alighting location information to the approved person's terminal 4, the candidate boarding and alighting location information including only approved candidate boarding and alighting locations that have been approved in advance by the approver user U2 as boarding and alighting locations that the approved person user U1 can use and that have been registered in the database 21.

In step S8, the terminal 4 for the person to be approved generates reservation information including information on the boarding place, boarding date and time, and disembarking place based on the input operation of the user U1 for the person to be approved. At this time, the user U1 for the person to be approved selects a boarding place from the approved boarding place candidates. In step S9, the terminal 4 for the person to be approved transmits the reservation information to the server device 2.
In step S10, the server device 2 arranges for a service vehicle 3 to be used by the approved user U1 based on the reservation information. The server device 2 also generates driving plan information for the service vehicle 3 to transport the approved user U1 from the boarding location to the disembarking location. For example, the driving plan information may include information on the boarding location and the disembarking location. For example, the driving plan information may also include a driving route from the current location of the service vehicle 3 to the boarding location and a driving route from the boarding location to the disembarking location.
In step S11, the server device 2 transmits the driving plan information to the service vehicle 3. In step S12, the controller 42 of the service vehicle 3 drives the service vehicle 3 in accordance with the driving plan information received from the server device 2, and transports the approved user U1 from the boarding location to the disembarking location.

Next, a process will be described in which the approver user U2 approves a candidate boarding/alighting point available to the approved user U1. Figures 3(a) and 3(b) are diagrams showing an example of a GUI (Graphical User Interface) of the approver terminal 5 in the first embodiment, and Figure 3(c) is a diagram showing an example of a GUI of the approved user terminal 4. Figure 4 is a flowchart showing an example of an information processing method in the first embodiment.
In order for the approver user U2 to register the candidate boarding and alighting points available to the approved user U1, the approver user U2 who approves the use of the ride-hailing service by the approved user U1 must first be registered in the database 21. If the approver user U2 has already been registered (step S20: N), the process proceeds to step S22. If the approver user U2 needs to be registered (step S20: Y), the process proceeds to step S21.

In step S21, a registration process for the approver user U2 is performed. For example, the registration of the approver user U2 may be realized by registering the approver user U1 as an approver on the approver terminal 5 of the approver user U2.
3A is a diagram showing an example of an approval recipient registration screen in the approver terminal 5. The approval recipient registration screen 60 includes an approval recipient selection field 60a, an ID input field 60b, and a decision button 60c.
The approver terminal 5 displays in the approval candidate selection field 60a the list of candidates for approval received from the server device 2. For example, the approver terminal 5 may transmit the identification information input by the approver user U2 in the ID input field 60b to the server device 2, and the server device 2 may use the identification information to search for candidates for approval and transmit the list of candidates for approval to the approver terminal 5.

When the approver terminal 5 receives an operation of selecting an approved user candidate included in the approved user candidate list in the approval selection field 60a and a pressing operation of the decision button 60c, it transmits identification information of the selected approved user candidate to the server device 2. When the server device 2 stores the identification information of the approved user candidate as identification information of the approved user U1 of the approver user U2 in the database 21 in association with the identification information of the approver user U2, the registration of the approved user U1 is completed. For example, the server device 2 may store the user registration information of the approver user U2 in the database 21 including the identification information of the approved user U1.
In addition, the process of storing the approved user U1 in the database 21 as the approved person of the approver user U2 (or the process of storing the approver user U2 in the database 21 as the approver of the approved user U1) may be performed by the operator of the vehicle dispatch service (hereinafter, sometimes simply referred to as the ``operator'').

Refer to Fig. 4. When the approver user U2 starts the operation of registering a candidate boarding/alighting point on the approver terminal 5, the server device 2 judges in step S22 whether the approver user U2 is the approver of the approved user U1. If the approver user U2 is not the approver of the approved user U1 (step S22: N), the process ends. If the approver user U2 is the approver of the approved user U1 (step S22: Y), the process proceeds to step S23.
In step S23, the server device 2 acquires the current location information of the approver user U2. For example, the approver terminal 5 may transmit the location information of the approver user U2 detected by the positioning device 50 to the server device 2. The approver terminal 5 may also transmit the location information (e.g., address) input by the approver user U2 to the approver terminal 5 to the server device 2.
In step S24, the server device 2 searches for candidate boarding and alighting points around the current location of the approver user U2. The server device 2 transmits information on the candidate boarding and alighting points obtained by the search to the approver terminal 5.

In step S25, the approver terminal 5 accepts an operation in which the approver user U2 selects and approves one of the candidate boarding and alighting locations searched and acquired by the server device 2 as a candidate boarding and alighting location available to the approved user U1. Fig. 3(b) is a diagram showing an example of a candidate boarding and alighting location registration screen on the approver terminal 5 where the approval operation for the candidate boarding and alighting locations is performed.
The candidate boarding/alighting location registration screen 61 includes a map display field 61a, a candidate boarding/alighting location selection field 61b, a registration name input field 61c, an expiration date input field 61d, and a confirmation button 61e.
The map display field 61a displays map information of the area around the current location of the approver user U2 and the current location 61f of the approver user U2. The candidate boarding/alighting point selection field 61b displays a list of candidate boarding/alighting points searched and acquired by the server device 2. The approver terminal 5 accepts an input operation by the approver user U2 to select one of the candidate boarding/alighting points included in the list displayed in the candidate boarding/alighting point selection field 61b.

In the registration name input field 61c, the approver user U2 inputs an alternative name for the candidate boarding/alighting point selected in the candidate boarding/alighting point selection field 61b. In the following description, the alternative name for the candidate boarding/alighting point set by the approver user U2 may be referred to as a “registered name.”
The official names of the boarding and disembarking points of the ride-hailing service may be set in advance in the database 21 by the operator. In addition to the official names, the operator may also set sub-names (e.g., abbreviations or alternative names written in hiragana) that are easy for young people to read in the database 21. The approver user U2 can input a registration name different from these official names and sub-names in the registration name input field 61c. The approver terminal 5 accepts the input operation of the registration name by the approver user U2.

The expiration date input field 61d is used to input a time condition for displaying the selected candidate boarding/alighting points on the approved person's terminal 4. For example, the expiration date for displaying the candidate boarding/alighting points on the approved person's terminal 4 is input in the expiration date input field 61d. The approver terminal 5 accepts the input operation of the expiration date by the approver user U2. For example, the expiration date input field 61d can be used to select and input a temporary period (until December 22, 2023 in the example of FIG. 3(b)) or a permanent period (unlimited in the example of FIG. 3(b)). The temporary period may be set by a default value by the approver terminal 5 or may be input by the approver user U2.
When the approver user U2 selects the candidate boarding/alighting location to be approved, inputs the registration name and expiration date, and presses the decision button 61e, the approver terminal 5 sends a registration request signal to the server device 2, which includes information on the selected candidate boarding/alighting location, the registration name, and the expiration date.
In addition, although not shown, this screen may be provided with a comment field in which the approver user U2 can write a comment when approving the candidate boarding/alighting point, allowing the user to input a message to the person to be approved U1.

4, in step S26, the server device 2 registers the candidate boarding/alighting points included in the registration request signal as approved candidate boarding/alighting points in the database 21. In addition, the server device 2 stores the registered name and the expiration date in the database 21 in association with the approved candidate boarding/alighting points.
When the approved user U1 reserves a car dispatch service, the server device 2 transmits the approved boarding and alighting candidate locations to the approved user terminal 4 in step S27. At this time, the server device 2 may transmit only the approved boarding and alighting candidate locations that satisfy the time condition to be displayed on the approved user terminal 4 to the approved user terminal 4. When creating reservation information for the car dispatch service (S8 in FIG. 2), the approved user terminal 4 displays the approved boarding and alighting candidate locations as boarding and alighting candidate locations that the approved user U1 can use, and presents them to the approved user U1. FIG. 3(c) is an example of a boarding and alighting candidate selection screen displayed for selecting a boarding and alighting location when creating reservation information for the car dispatch service on the approved user terminal 4. The boarding and alighting candidate selection screen 62 includes approved boarding and alighting candidate selection fields 62a and 62b and a decision button 62c.

A list of approved candidate boarding/disembarking locations is displayed in the approved candidate boarding/disembarking locations selection fields 62a and 62b. The registered name set by the approver user U2 may be used as the name of the approved candidate boarding/disembarking location displayed in the approved candidate boarding/disembarking locations selection fields 62a and 62b. When the approved user terminal 4 receives an operation of selecting an approved candidate boarding/disembarking location included in the approved candidate boarding/disembarking locations list in the approved candidate boarding/disembarking locations selection fields 62a and 62b and a pressing operation of the decision button 62c, the approved user terminal 4 creates reservation information including the selected approved candidate boarding/disembarking location as a boarding/disembarking location.
The boarding/alighting place selection screen 62 may distinguish between approved boarding/alighting place candidates for which a time condition for displaying on the approved person's terminal 4 is set (e.g., candidates displayed in the approved boarding/alighting place candidate selection field 62a) and approved boarding/alighting place candidates for which a time condition for displaying on the approved person's terminal 4 is not set (e.g., candidates displayed in the approved boarding/alighting place candidate selection field 62b). In addition, if there is an approved boarding/alighting place candidate that has been newly registered during the period from when the boarding/alighting place selection screen 62 was last displayed on the approved person's terminal 4 until it is displayed this time, an update mark 62d may be added to the newly registered approved boarding/alighting place candidate and displayed.
Furthermore, when the server device 2 receives reservation information including the approved candidate boarding/alighting point as a boarding/alighting point (i.e., when the candidate boarding/alighting point approved by the approver user U2 is selected as the candidate boarding/alighting point to be used by the approved user U1), the server device 2 may transmit a selection result signal informing the approved candidate boarding/alighting point selected by the approved user U1 to the approver terminal 5. The approver terminal 5 may notify the approver user U2 of the approved candidate boarding/alighting point selected by the approved user U1.

Second Embodiment
In the second embodiment, the candidate boarding and alighting points available to the approved user U1 are determined based on the location information of the proxy approver user. The proxy approver user is an example of a "related user" described in the claims. For example, the proxy approver user may be a relative of the approved user U1, or a guardian or adult guardian of an acquaintance of the approved user U1.
5(a) and 5(b) are diagrams showing an example of a GUI of the approver terminal 5, and Fig. 5(c) is a diagram showing an example of a GUI of the proxy approver terminal used by a proxy approver user. The configuration of the proxy approver terminal may be the same as the configuration of the approver terminal 5. Fig. 6 is a flowchart showing an example of an information processing method according to the second embodiment.

In step S30, a process for registering a proxy approver user is performed. Fig. 5A is a diagram showing an example of a proxy approver registration screen in the approver terminal 5. The proxy approver registration screen 63 includes an approved person selection field 63a, a proxy approver selection field 63b, an ID input field 63c, and a decision button 63d.
The approver terminal 5 displays in the approval target user selection field 63a the list of candidates for the approved user received from the server device 2. For example, the server device 2 may transmit to the approver terminal 5 as the list of candidates for the approved user a list including users registered in the database 21 as approved users of the approver user U2.
Furthermore, the approver terminal 5 displays the list of proxy approver user candidates received from the server device 2 in the proxy approver selection field 63b. For example, the approver terminal 5 may transmit the identification information input by the approver user U2 in the ID input field 63c to the server device 2, and the server device 2 may use the identification information to search for proxy approver user candidates and transmit the list of proxy approver user candidates to the approver terminal 5. The server device 2 may generate the list of proxy approver user candidates based on history information of users previously designated as proxy approver users.

When the approver terminal 5 receives an operation of selecting an approved user U1 included in the approved user candidate list in the approved user selection field 63a, an operation of selecting a proxy approver user included in the proxy approver user candidate list in the proxy approver selection field 63b, and an operation of pressing the decision button 60d, it transmits identification information of the selected approved user U1 and the proxy approver user to the server device 2. When the server device 2 stores the received identification information of the proxy approver user as identification information of the proxy approver user of the approved user U1 in the database 21 in association with the identification information of the approved user U1, registration of the proxy approver user is completed. For example, the server device 2 may store the user registration information of the approved user U1 in the database 21 including the identification information of the proxy approver user.

Please refer to Fig. 4. When the proxy approver starts the operation of registering the boarding and alighting point candidates for the approved user U1 on the proxy approver terminal, in step S31, the server device 2 judges whether the proxy approver user is the proxy approver of the approved user U1. If the proxy approver user is not the proxy approver of the approved user U1 (step S31: N), the process ends. If the proxy approver user is the proxy approver of the approved user U1 (step S31: Y), the process proceeds to step S32.
In step S32, the server device 2 acquires the current location information of the proxy approver user. For example, the proxy approver terminal may transmit the location information of the proxy approver user detected by a positioning device to the server device 2. The proxy approver terminal may also transmit the location information (e.g., address) that the proxy approver user inputs to the proxy approver terminal to the server device 2.

In step S33, the server device 2 searches for candidate boarding and alighting points around the current location of the proxy approver user. The server device 2 transmits information on the candidate boarding and alighting points acquired by the search to the proxy approver terminal.
In step S34, the proxy approver terminal accepts an operation in which the proxy approver user selects one of the candidate boarding and alighting points searched and acquired by the server device 2 as a candidate boarding and alighting point available to the approved user U1. The operation of selecting a candidate boarding and alighting point on the proxy approver terminal is the same as the operation described with reference to FIG. 3(b).
In step S35, the proxy approver terminal 5 transmits a registration application signal including information on the selected candidate boarding and alighting locations to the server device 2. The server device 2 transmits the received registration application signal and location information of the proxy approver user to the approver terminal 5.

In step S36, the approver terminal 5 accepts an operation of the approver user U2 approving the candidate boarding/alighting points selected by the proxy approver user as a candidate boarding/alighting point available for the approved user U1. FIG. 5B is a diagram showing an example of a candidate boarding/alighting point registration screen on the approver terminal 5 where the approval operation of the candidate boarding/alighting points is performed.
The candidate boarding/alighting location registration screen 64 includes a map display field 64a, a candidate boarding/alighting location display field 64b, a registration name input field 64c, an expiration date display field 64d, a comment input field 64e, an approve button 64f, and a reject button 64g.
The map display field 64a displays map information of the area surrounding the current location of the proxy approver user and the current location 64h of the proxy approver user.

The candidate boarding/alighting locations display field 64b displays the candidate boarding/alighting locations selected by the proxy approver user.
The registered name of the boarding/alighting point candidate selected by the proxy approver user is input by the approver user U2 in the registered name input field 64c. The approver terminal 5 accepts the input operation of the registered name by the approver user U2.
The expiration date display field 64d displays the expiration date of the candidate boarding/alighting locations set by the proxy approver user.
The approver user U2 can input a comment to the proxy approver user in the comment input field 64e. The approver terminal 5 accepts an input operation of a comment by the approver user U2.
When the approver terminal 5 receives the pressing operation of the reject button 64g by the approver user U2 (step S36: N), the process proceeds to step S37. When the approver terminal 5 receives the pressing operation of the approve button 64f (step S36: Y), the process proceeds to step S38.

In step S37, the approver terminal 5 transmits a rejection notification signal including the comment information entered in the comment input field 64e to the proxy approver terminal via the server device 2. The proxy approver terminal presents the notification that the registration of the boarding/alighting point candidate has been rejected and the comment information to the proxy approver user, and then the process ends.
In step S38, the approver terminal 5 transmits an approval notification signal including the registered name information and the comment information to the server device 2. The server device 2 registers the candidate boarding/alighting points included in the registration application signal received from the proxy approver terminal as approved candidate boarding/alighting points in the database 21. The server device 2 also stores the registered name and the expiration date in the database 21 in association with the approved candidate boarding/alighting points.

In step S39, the server device 2 transmits the approval notification signal received from the approver terminal 5 to the proxy approver terminal. The proxy approver terminal presents the proxy approver user with a notification that the registration of the candidate boarding and alighting points has been approved and comment information.
5C is a diagram showing an example of an application result notification screen 65 for notifying the user that the registration of the candidate boarding/alighting point has been approved on the proxy approver terminal. The application result notification screen 65 includes a map display field 65a, an approved candidate boarding/alighting point display field 65b, a registered name display field 65c, a validity period display field 65d, a comment display field 65e, and a close button 65f.

The map display field 65a displays map information around the current location of the proxy approver user and the current location 65g of the proxy approver user. The approved candidate boarding/alighting point display field 65b, the registered name display field 65c, and the expiration date display field 65d display the official name, registered name, and expiration date of the approved candidate boarding/alighting point applied for by the proxy approver user and approved by the approver user U2. The comment display field 65e displays the comment information input in the comment input field 64e of the approver terminal 5.
Please refer to Fig. 4. In step S40, the server device 2 transmits the approved candidate boarding/alighting locations to the terminal 4 for the person to be approved. At this time, the server device 2 may transmit to the terminal 4 for the person to be approved only the approved candidate boarding/alighting locations that satisfy the time condition to be displayed on the terminal 4 for the person to be approved. When creating reservation information for the vehicle dispatch service, the terminal 4 for the person to be approved displays the approved candidate boarding/alighting locations as the candidate boarding/alighting locations that the user U1 for the person to be approved can use, and presents them to the user U1 for the person to be approved.

Third Embodiment
In the third embodiment, approved boarding and alighting location candidates are registered based on event information related to events held in a business area where the approved user U1 uses a vehicle dispatch service.
7(a) to 7(c) are diagrams showing an example of a GUI of the approver terminal 5, and FIG. 8 is a flowchart showing an example of an information processing method according to the third embodiment.
In step S50, the approver terminal 5 accepts a selection operation by the approver user U2 to select the approved user U1. Fig. 7(a) is a diagram showing an example of an approved user selection screen 66 on the approver terminal 5 on which the approval user U1 is selected. The approved user selection screen 66 includes an approved user selection field 66a and a decision button 66b.
The approver terminal 5 displays the list of candidates for the approved user in the approval candidate selection field 60a received from the server device 2. When the approver terminal 5 receives an operation of selecting the approved user U1 included in the list of the approved user candidates in the approval candidate selection field 63a and an operation of pressing the decision button 66b, it transmits the identification information of the approved user U1 to the server device 2.

See Fig. 8. In step S51, the server device 2 acquires from the database 21 event information related to events held within the business area in which the approval-recipient user U1 uses the vehicle dispatch service. For example, the server device 2 may acquire event information of events that match the age and hobbies of the approval-recipient user U1. The server device 2 may also acquire event information from a terminal device operated by the event organizer, or from schedule information of the approver user U2. The server device 2 transmits a list of the acquired event information to the approver terminal 5.
In step S52, the approver terminal 5 accepts an operation by the approver user U2 to select one of the events received from the server device 2. Fig. 7(b) is a diagram showing an example of an event selection screen 67 on the approver terminal 5. The event selection screen 67 includes an event selection field 67a and a decision button 67b.

The approver terminal 5 displays in the event selection field 67a the list of event information received from the server device 2. When the approver terminal 5 accepts an operation of selecting an event included in the list of event information in the event selection field 67a and an operation of pressing the decision button 67b, the approver terminal 5 transmits the selected event information to the server device 2.
Note that step S50 may be executed after steps S51 and S52. In this case, the server device 2 may transmit to the approver terminal 5 a list of candidates for the approved users who match the attributes of the event selected in step S52, among the approved users stored in association with the approver user U2.
In step S53, the server device 2 searches for candidate boarding and alighting locations around the location of the event selected by the approver user U2. The server device 2 transmits information on the candidate boarding and alighting locations obtained by the search to the approver terminal 5.

In step S54, the approver terminal 5 accepts an operation by the approver user U2 to select the candidate boarding and alighting locations around the event location received from the server device 2 as candidate boarding and alighting locations available to the approved user U1. Fig. 7(c) is a diagram showing an example of a candidate boarding and alighting location registration screen on which a boarding and alighting location selection operation is performed on the approver terminal 5. The candidate boarding and alighting location registration screen 68 includes a map display field 68a, a candidate boarding and alighting location display field 68b, an allowed time display field 68c, and a decision button 68d.
The map display field 68a displays map information of the area around the event location and the event location 68e. The candidate boarding/alighting location display field 68b displays the names of the candidate boarding/alighting locations received from the server device 2. When there are multiple candidate boarding/alighting locations around the event location, the candidate boarding/alighting location registration screen 68 may include an input field where the approver terminal 5 receives an input operation to select a candidate boarding/alighting location. The permitted time display field 68c displays the permitted time during which the candidate boarding/alighting locations received from the server device 2 are permitted to be displayed as a time condition for displaying the candidate boarding/alighting locations on the approved person terminal 4.

For example, the permitted time may be a default value determined by the approver terminal 5 or the server device 2. For example, the start time and end time of the permitted time may be set as default values to a time a predetermined time before the start time of the event and a time a predetermined time after the end time. In addition, the candidate boarding and alighting location registration screen 68 may include an input field in which the approver terminal 5 accepts input of the permitted time.
When the approver terminal 5 accepts the pressing operation of the decision button 68d, it transmits to the server device 2 a registration request signal requesting that the candidate boarding and alighting locations around the event venue received by the server device 2 be registered as approved candidate boarding and alighting locations available to the approved user U1. In step S55, the server device 2 sets the permitted time displayed in the permitted time display field 68c as the permitted time for displaying the candidate boarding and alighting locations on the approved user terminal 4.

In step S56, the server device 2 registers the candidate boarding/alighting locations included in the registration request signal as approved candidate boarding/alighting locations in the database 21. Also, the server device 2 stores the permitted time in the database 21 in association with the approved candidate boarding/alighting locations.
In step S57, the server device 2 transmits the approved candidate boarding and alighting locations to the terminal 4 for the person to be approved. At this time, the server device 2 may transmit to the terminal 4 for the person to be approved only the approved candidate boarding and alighting locations that satisfy the time condition to be displayed on the terminal 4 for the person to be approved. When creating reservation information for the vehicle dispatch service, the terminal 4 for the person to be approved displays the approved candidate boarding and alighting locations as possible boarding and alighting locations for the person to be approved user U1, and presents them to the person to be approved user U1.

Fourth Embodiment
In the fourth embodiment, the approved user U1 registers the approved candidate boarding/alighting points based on the past history information of the boarding/alighting points and the attributes of the boarding/alighting points. In addition, the approver user U2 sets the permission time during which the approved candidate boarding/alighting points are permitted to be displayed on the approved user terminal 4.
9(a) to 9(c) are diagrams showing an example of a GUI of the approver terminal 5, and FIG. 10 is a flowchart showing an example of an information processing method according to the fourth embodiment.
In step S60, the approver terminal 5 accepts a selection operation by the approver user U2 to select the approveee user U1. The process of step S60 is similar to the process of step S50 in FIG.

In step S61, the approver terminal 5 accepts an operation by the approver user U2 to select and approve a candidate boarding/alighting point that can be used by the approved user U1. Fig. 9(a) is a diagram showing an example of a candidate boarding/alighting point registration screen on the approver terminal 5. The candidate boarding/alighting point registration screen 69 includes a keyword input field 69a, a candidate boarding/alighting point selection field 69b, and a decision button 69c.
The approver terminal 5 displays a list of candidate boarding and alighting points that the server device 2 has searched and acquired in the candidate boarding and alighting point selection field 69b. For example, the approver terminal 5 may transmit to the server device 2 a keyword that the approver user U2 has input in the keyword input field 69a. Furthermore, the database 21 may register keywords in association with information on each boarding and alighting point. The server device 2 may search the database 21 for candidate boarding and alighting points using the keyword, and transmit the list of candidate boarding and alighting points to the approver terminal 5. Furthermore, the server device 2 may generate a list of candidate boarding and alighting points based on past history information of the approved user U1's use of the boarding and alighting points, and transmit the list to the approver terminal 5.

9B is a diagram showing another example of a candidate boarding/alighting place registration screen on which an approval operation for a candidate boarding/alighting place is performed on the approver terminal 5. The candidate boarding/alighting place registration screen 70 includes an attribute information input field 70a, a candidate boarding/alighting place selection field 70b, and a decision button 70c.
The approver terminal 5 may transmit the attribute information of the boarding/alighting point input by the approver user U2 in the attribute information input field 70a to the server device 2. For example, as the attribute information of the boarding/alighting point, whether or not a terminal device that can be used as the approved person terminal 4 is provided at the boarding/alighting point may be input in the attribute information input field 70a. The server device 2 may search the database 21 for candidate boarding/alighting points using the attribute information and transmit a list of the candidate boarding/alighting points to the approver terminal 5.
The approver terminal 5 accepts an input operation by the approver user U2 to select one of the candidate boarding/alighting points included in the list displayed in the candidate boarding/alighting point selection field 69b, 70b. When the approver user U2 accepts the selection operation of the candidate boarding/alighting point and the pressing operation of the decision button 69c, 70c, the process proceeds to step S62.

In step S62, the approver terminal 5 accepts an operation by the approver user U2 to set an allowed time during which display of the boarding/alighting candidate selected in step S61 is allowed as a time condition for displaying the boarding/alighting candidate on the approved person terminal 4. Fig. 9(c) is a diagram showing an example of an allowed time setting screen 71 on which an allowed time setting operation is performed on the approver terminal 5. The allowed time setting screen 71 may include a period setting field 71a, a repetition condition setting field 71b, a time setting field 71c, and a decision button 71d.
The period setting field 71a is used to input the start and end dates of the period for which the permitted time is set. The repetition condition setting field 71b is used to set a repetition condition for repeatedly setting the permitted time between the start and end dates specified in the period setting field 71a. For example, the repetition condition setting field 71b may be used to set the day of the week for which the permitted time is set every week. The time setting field 71c is used to set the start and end times for which the permitted time is set out of the 24 hours in a day.

The permission time setting screen 71 may include a supplementary information input field in which the approver terminal 5 accepts an operation of the approver user U2 inputting supplementary information regarding the permission time. For example, the supplementary information may be information such as a reason why the approver user U2 set the permission time.
When the approver terminal 5 accepts the input operations of the permitted time entered in the period setting field 71a, the repetition condition setting field 71b, and the time setting field 71c, the input operation of the supplementary information, and the pressing of the decision button 71d, it transmits a registration request signal to the server device 2, which includes the candidate boarding and alighting locations selected in step S61, the permitted time information set in step S62, and the supplementary information.

In step S63, the server device 2 registers the candidate boarding/alighting locations included in the registration request signal in the database 21 as approved candidate boarding/alighting locations. In addition, the server device 2 stores the approved candidate boarding/alighting locations in the database 21 in association with the approved candidate boarding/alighting locations. In step S64, the server device 2 transmits the approved candidate boarding/alighting locations to the terminal 4 for the person to be approved. At this time, the server device 2 may transmit to the terminal 4 for the person to be approved only the approved candidate boarding/alighting locations that satisfy the time conditions to be displayed on the terminal 4 for the person to be approved. In addition, the server device 2 transmits information on the permitted time and the supplementary information to the terminal 4 for the person to be approved.
The terminal 4 for the person to be approved displays the approved candidate boarding and alighting places as possible boarding and alighting places for the approved user U1 when creating reservation information for the vehicle dispatch service, and presents them to the approved user U1. The terminal 4 for the person to be approved displays the permitted time set for the approved candidate boarding and alighting places and its supplementary information, and presents them to the approved user U1.

The type, mode, or setting method of the permitted time set for an approved candidate boarding/alighting location may be switched depending on the attributes of the approved candidate boarding/alighting location. For example, in the case of the first and second embodiments, when the candidate boarding/alighting location is for the approved user U1 to travel to the location of the approver user U2 or the proxy approver user, the approver user U2 or the proxy approver user may set only the end point of the permitted time. In this case, the permitted time may be set to start from the current time and end at the end point. Also, for example, in the case of a candidate boarding/alighting location for participating in an event or for participating in a specific activity (for example, attending a cram school) as in the third embodiment, the approver user U2 may set both the start and end points of the permitted time.

(Effects of the embodiment)
(1) The information processing device includes a controller that executes a process of identifying a user who uses a vehicle dispatch service, a process of determining whether the identified user is an approved user who requires approval from an approver user who is a user other than the identified user for using the vehicle dispatch service, and a process of presenting to the approved user, if the identified user is an approved user, a candidate use location approved by the approver user from among candidate use location locations that are predetermined candidates for use locations of the vehicle dispatch service. This restricts an approved user who requires approval from the approver user for using the vehicle dispatch service from using the vehicle dispatch service in a location not intended by the approver user.

(2) The controller may execute a process of acquiring location information of the approver user or a related user related to the approver user, and a process of setting a potential use location to be presented to the approved user based on the acquired location information, thereby facilitating approval of the potential use location for the approved user to travel to the location of the approver user or the related user.
(3) The controller may execute a process of acquiring event information about an event held in an area where the approved user uses the vehicle dispatch service, and a process of setting candidate locations to be presented to the approved user based on the event information, which makes it easier to approve the candidate locations for the approved user to participate in the event.

(4) The approver user may be able to set a time condition for presenting the candidate location of use to the approver user. This makes it possible to restrict the approver user from using the vehicle dispatch service at a time that the approver user does not intend.
(5) The controller may execute a process of presenting the time condition and supplemental information related to the time condition to the approved user, thereby enabling the approved user to recognize that the time condition has been set.
(6) The approver user may be able to set a temporary or permanent period as a period for which potential locations are presented to the approved user. This allows the use of the vehicle dispatch service to be approved for an appropriate period according to, for example, the reason for using the vehicle dispatch service.

(7) The approver user may set a different name for the candidate location of use presented to the approved user from the name preset in the dispatch system that provides the dispatch service. This makes it easier for minor approved users to understand the candidate location of use.
(8) The controller may execute a process of generating a list of potential use locations based on past history information of the use of the potential use locations by the approved user, a process of presenting the list of potential use locations to the approver user, and a process of accepting a result of the approver user selecting one of the potential use locations included in the list. This allows the approver user to approve the potential use locations by using the past history information.

(9) The controller may execute a process of generating a list of related user candidates based on past history information of a user designated by the approver user as a related user, a process of presenting the list of related user candidates to the approver user, and a process of accepting a result of the approver user selecting one of the related user candidates included in the list as a related user. This allows the approver user to designate a related user by using the past history information.
(10) The controller may execute a process of generating a list of potential use locations based on attributes of the potential use locations, a process of presenting the list of potential use locations to an approver user, and a process of accepting a result of the approver user selecting one of the potential use locations included in the list, thereby enabling the approver user to approve the potential use locations based on the attributes of the potential use locations.

(11) The information processing device may include a database in which an approver user and an approved user are stored in association with each other. This allows an appropriate approver user to approve the candidate boarding and alighting points used by the approved user.
(12) The controller may execute a process of notifying the approver user of a candidate use location selected by the approver user as a use location where the approved user uses the vehicle dispatch service, from among the candidate use location locations approved by the approver user. This allows the approver user to know that the approved user has used the candidate use location.

All examples and conditional terms described herein are intended for educational purposes to assist the reader in understanding the present invention and the concepts provided by the inventor for the advancement of technology, and should be construed without limitation to the above specifically described examples and conditions, and the configuration of the examples in this specification with respect to showing the advantages and disadvantages of the present invention. Although the embodiments of the present invention have been described in detail, it should be understood that various changes, substitutions and modifications can be made thereto without departing from the spirit and scope of the present invention.

1...Vehicle dispatch service system, 2...Server device, 3...Service vehicle, 4...Terminal for approved party, 5...Terminal for approver, 20, 33, 40, 51...Communication device, 21...Database, 22, 36, 42, 53...Controller, 23, 38, 43, 54...Processor, 24, 39, 44, 55...Storage device, 30...Sensor, 31...Positioning device, 32...Map database (map DB), 37...Actuator, 41, 52...Human machine interface, 50...Positioning device

Claims (13)

A process of identifying a user who uses a ride-hailing service;
A process of determining whether the identified user is an approved user who requires approval from an approver user other than the identified user for use of the vehicle dispatch service;
When the identified user is the approved user, a process of presenting to the approved user a use location candidate approved by the approver user from among use location candidates that are predetermined candidates as use locations of the vehicle dispatch service;
23. An information processing apparatus comprising: a controller for executing the above-mentioned steps; The controller:
acquiring location information of the approver user or a related user related to the approver user;
A process of setting the use location candidates to be presented to the approved user based on the acquired location information;
The information processing apparatus according to claim 1, wherein the information processing apparatus executes the following: The controller:
A process of acquiring event information regarding events held in an area where the approved user uses the vehicle dispatch service;
A process of setting the use location candidates to be presented to the approved user based on the event information;
2. The information processing apparatus according to claim 1, wherein the information processing apparatus executes the steps of: The information processing device according to claim 1, characterized in that the time conditions for presenting the potential use locations to the approved user can be set by the approver user. The information processing device according to claim 4, characterized in that the controller executes a process of presenting the time condition and supplementary information related to the time condition to the approved user. The information processing device according to claim 1, characterized in that the approver user can set a temporary or permanent period as the period for which the potential use locations are presented to the approver user. The information processing device according to claim 1, characterized in that the approver user can set an alternative name for the candidate location of use presented to the approver user that is different from a name preset in the dispatch system that provides the dispatch service. The controller:
A process of generating a list of the use location candidates based on past history information of the approved user using the use location candidates;
A process of presenting a list of the use location candidates to the approver user;
A process of accepting a result of the approver user selecting one of the use location candidates included in the list;
2. The information processing apparatus according to claim 1, wherein the information processing apparatus executes the steps of: The controller:
generating a list of candidates for the related users based on past history information of users designated by the approver user as the related users;
presenting a list of the related user candidates to the approver user;
a process of receiving a result of the approver user selecting one of the related user candidates included in the list as the related user;
3. The information processing apparatus according to claim 2, wherein the information processing apparatus executes the steps of: The controller:
generating a list of the potential use locations based on attributes of the potential use locations;
A process of presenting a list of the use location candidates to the approver user;
A process of accepting a result of the approver user selecting one of the use location candidates included in the list;
2. The information processing apparatus according to claim 1, wherein the information processing apparatus executes the steps of: The information processing device according to claim 1, further comprising a database in which the approver user and the approveee user are stored in association with each other. The information processing device according to claim 1, characterized in that the controller executes a process of notifying the approver user of the candidate use location that the approved user has selected as the use location where the vehicle dispatch service will be used, from among the candidate use location locations approved by the approver user. A process of identifying a user who uses a ride-hailing service;
A process of determining whether the identified user is an approved user who requires approval from an approver user other than the identified user for use of the vehicle dispatch service;
When the identified user is the approved user, a process of presenting to the approved user a use location candidate approved by the approver user from among use location candidates that are predetermined candidates as use locations of the vehicle dispatch service;
The information processing method according to claim 1, further comprising:

Images