Information processing device and information processing method

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

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

[0002] The following Patent Document 1 describes a vehicle monitoring system that allows guardians to check the riding status of a person being monitored in real time.

[0003] Japanese Patent Application Laid-Open No. 2022-069033

[0004] The above-mentioned Patent Document 1 does not disclose how to set the 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 the vehicle transportation service from using the vehicle transportation service in a location not intended by the approver user.

[0005] An information processing device of one embodiment of the present invention includes a controller that performs the following processes: identifying a user who uses a ride-hailing service; 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 ride-hailing service; and, if the identified user is an approved user, presenting to the approved user potential usage locations that have been approved by the approver user from among potential usage locations that are predetermined candidates for locations where the ride-hailing service is used.

[0006] According to the present invention, an approved user who requires approval from an approver user to use a ride-hailing service can be restricted from using the ride-hailing service in a location not intended by the approver user. The objects and advantages of the present invention are realized and achieved by using the elements and combinations thereof set forth in the claims. It should be understood that both the foregoing general description and the following detailed description are merely exemplary and explanatory and are not intended to limit the invention as defined by the claims.

[0007] FIG. 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. (a) and (b) are diagrams of an example of a GUI of an approver terminal according to a first embodiment, and (c) is a diagram of an example of a GUI of an approved party terminal. FIG. 3 is a flowchart of an example of an information processing method according to the first embodiment. (a) and (b) are diagrams of an example of a GUI of an approver terminal according to a second embodiment, and (c) is a diagram of an example of a GUI of a proxy approver terminal. FIG. 4 is a flowchart of an example of an information processing method according to the second embodiment. (a) to (c) are diagrams of an example of a GUI of an approver terminal according to a third embodiment. FIG. 5 is a flowchart of an example of an information processing method according to the third embodiment. (a) to (c) are diagrams of an example of a GUI of an approver terminal according to a fourth embodiment. FIG. 6 is a flowchart of an example of an information processing method according to the fourth embodiment.

[0008] (First embodiment) (Configuration) Fig. 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 transports 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 party terminal 4, and an approver terminal 5.

[0009] The approved user terminal 4 and the approver terminal 5 are terminal devices operated by users U1 and U2 who use the vehicle dispatch service. Dedicated application software for using the vehicle dispatch service (hereinafter sometimes referred to as "vehicle dispatch software") is installed on the approved user terminal 4 and the approver terminal 5. 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 approved user U1's minor, or a caregiver who cares for an elderly person. In the following description, users of the vehicle dispatch service, including users U1 and U2, may be collectively referred to as "user U."

[0010] The approval recipient terminal 4 is, for example, a portable information terminal that can be carried by the approval recipient user U1 or a small, portable computer. If the approval recipient 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 approval recipient user U1. The approval recipient user U1 reserves a vehicle dispatch service using vehicle dispatch software executed on the approval recipient terminal 4.

[0011] The approval recipient terminal 4 includes a communication device 40, a human-machine interface (HMI) 41, and a controller 42. The communication device 40 provides communication functions between the approval recipient terminal 4 and the server device 2. The HMI 41 is an interface device that exchanges 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 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 accept operational inputs to the approval recipient terminal 4 by the approval recipient user U1.

[0012] The controller 42 is an electronic control unit (ECU) that controls the operation of the approval 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 central processing unit (CPU) or a micro-processing unit (MPU). The storage device 44 may include non-transitory tangible storage media such as a register, cache memory, read-only memory (ROM), or random access memory (RAM). The functions of the approval recipient terminal 4 described below are realized, for example, by the processor 43 executing a computer program stored in the storage device 44.

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

[0014] In the following explanation, the location where the approved user U1 uses the vehicle dispatch service is the boarding and disembarking location where the approved user U1 gets on and off the service vehicle 3, but the location where the vehicle dispatch service is used in the present invention is not limited to the boarding and disembarking location. The location where the vehicle dispatch service is used in the present 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.

[0015] 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. The communication device 51 provides communication between the approver terminal 5 and the server device 2. The HMI 52 is an interface device that exchanges information between the approver terminal 5 and the approver user U2. The HMI 52 includes a display device visible to the approver user U2, as well as a speaker and a buzzer that output auditory information. The HMI 52 also includes controls and a voice input device that accept operational inputs to the approver terminal 5 by the approver user U2.

[0016] 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, a cache memory, a ROM, or a 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.

[0017] The server device 2 is an information processing device that receives reservation information from the approval recipient terminal 4 and the approver terminal 5 and arranges for 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 an "information processing device" as defined in the claims. The server device 2 includes a communication device 20, a database 21, and a controller 22. The communication device 20 provides communication functions between the server device 2, the service vehicle 3, the approval recipient terminal 4, and the approver terminal 5. The database 21 stores various information used to provide the vehicle dispatch service. 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 boarding and disembarking locations where the user U can board and disembark the service vehicle 3, and information about events held within the business area.

[0018] 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 the processor 23 executing a computer program stored in the storage device 24, for example.

[0019] The service vehicle 3 is a vehicle that operates in response to a request from the user U (a so-called demand-based transportation vehicle), 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 trip plan from the server device 2, it drives to the boarding location so as to arrive by the boarding date and time included in the trip plan. When the user U boards the service vehicle 3 at the boarding location, it drives to the drop-off location included in the trip 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 to this. The service vehicle 3 may also 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 to assist the driver in driving the service vehicle 3 according to the route information.

[0020] 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 status) obtained from the service vehicle 3. For example, the object sensor may include a distance measuring device such as a laser range finder (LRF), radar, or LiDAR (Light Detection and Ranging) laser radar. The object sensor outputs surrounding environment information, which is information about 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 status information regarding the vehicle status of the service vehicle 3 to the controller 36.

[0021] The positioning device 31 measures the current position and attitude of the service vehicle 3. The positioning device 31 may include, for example, a GNSS receiver. 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.

[0022] 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 non-transitory tangible storage media 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.

[0023] 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 sensors 30, the positioning results of the positioning device 31, and the map information in 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 area, 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 control signals from the controller 36 to generate 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.

[0024] 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 from 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 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 a registration request signal to the server device 2 requesting that the approved candidate boarding and alighting locations be registered in the database 21.

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

[0026] 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 a person who requires approval from another user to use the ride-hailing 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 a person to be approved 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 for the ride-hailing service to the approval-recipient terminal 4. If the approval-recipient user U1 is a person to be approved, the server device 2 transmits candidate boarding and alighting location information to the approval-recipient terminal 4, including only approved candidate boarding and alighting locations that have been previously approved by the approver user U2 as boarding and alighting locations available to the approval-recipient user U1 and registered in the database 21.

[0027] In step S8, the terminal 4 for the person to be approved generates reservation information including information on the boarding location, boarding date and time, and disembarking location based on the input operation of the user U1 to be approved. At this time, the user U1 to be approved selects a boarding location from the approved candidate boarding and disembarking locations. 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 user U1 to be approved based on the reservation information. The server device 2 also generates driving plan information for the service vehicle 3 to transport the user U1 to be approved 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. Furthermore, for example, the driving plan information may 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.

[0028] Next, the process when the approver user U2 approves a candidate boarding and alighting location available to the approval-recipient user U1 will be described. FIGS. 3A and 3B are diagrams showing an example of a GUI (Graphical User Interface) of the approver terminal 5 in the first embodiment, and FIG. 3C is a diagram showing an example of a GUI of the approval-recipient terminal 4. FIG. 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 a candidate boarding and alighting location available to the approval-recipient user U1, the approver user U2 who approves the approval-recipient user U1's use of the ride-hailing service 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.

[0029] In step S21, a registration process for the approver user U2 is performed. For example, the registration of the approver user U2 may be achieved by registering the approved user U1 as an approved user on the approver terminal 5 of the approver user U2. FIG. 3A is a diagram showing an example of an approval recipient registration screen on 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 a list of candidate approved users received from the server device 2 in the approval recipient selection field 60a. For example, the approver terminal 5 may transmit identification information entered 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 candidate approved users and transmit the list of candidate approved users to the approver terminal 5.

[0030] When the approver terminal 5 receives an operation to select an approval candidate user included in the approval candidate user candidate list in the approval candidate selection field 60a and an operation to press the decision button 60c, it transmits identification information of the selected approval candidate user to the server device 2. The server device 2 stores the identification information of the approval candidate user as the identification information of the approver user U1 of the approver user U2 in the database 21 in association with the identification information of the approver user U2, thereby completing the registration of the approval candidate user U1. 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 approval candidate user U1. The process of storing the approval candidate user U1 in the database 21 as the approver of the approver user U2 (or the process of storing the approver user U2 in the database 21 as the approver of the approval candidate user U1) may be performed by the operator of the vehicle dispatch service (hereinafter, sometimes simply referred to as the "operator").

[0031] See FIG. 4. When the approver user U2 starts registering a potential boarding or alighting location on the approver terminal 5, the server device 2 determines 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) entered by the approver user U2 into the approver terminal 5 to the server device 2. In step S24, the server device 2 searches for potential boarding or alighting locations near the current location of the approver user U2. The server device 2 transmits the information on the candidate boarding and alighting locations obtained by the search to the approver terminal 5.

[0032] In step S25, the approver terminal 5 accepts an operation by the approver user U2 to select and approve 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. 3B is a diagram showing an example of a candidate boarding and alighting location registration screen on the approver terminal 5, on which the approval operation for the candidate boarding and alighting locations is performed. The candidate boarding and alighting location registration screen 61 includes a map display field 61a, a candidate boarding and alighting location selection field 61b, a registration name input field 61c, an expiration date input field 61d, and a decision button 61e. The map display field 61a displays map information about the area around the current location of the approver user U2 and the current location 61f of the approver user U2. The candidate boarding and alighting location selection field 61b displays a list of the candidate boarding and alighting locations 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 and alighting locations included in the list displayed in the candidate boarding and alighting location selection field 61b.

[0033] In the registered name input field 61c, the approver user U2 inputs an alternative name for the candidate boarding / alighting location selected in the candidate boarding / alighting location selection field 61b. In the following description, the alternative name for the candidate boarding / alighting location set by the approver user U2 may be referred to as a "registered name." The official names of each boarding / alighting location 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 registered name that is different from these official names or sub-names in the registered name input field 61c. The approver terminal 5 accepts the input operation of the registered name by the approver user U2.

[0034] The expiration date input field 61d is used to input a time condition for displaying the selected candidate boarding / alighting location on the approval recipient terminal 4. For example, the expiration date for displaying the candidate boarding / alighting location on the approval recipient terminal 4 is input in the expiration date input field 61d. The approver terminal 5 accepts an input operation of the expiration date by the approver user U2. For example, the expiration date input field 61d allows the approver user U2 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. Upon accepting the operation of selecting the candidate boarding / alighting location to be approved by the approver user U2, the operation of inputting the registration name and expiration date, and the operation of pressing the OK button 61e, the approver terminal 5 transmits a registration request signal including information on the selected candidate boarding / alighting location, the registration name, and the expiration date to the server device 2. Although not shown, this screen may also be provided with a comment field in which the approver user U2 can enter a comment when approving the candidate boarding / alighting location, allowing the approver user U2 to input a message to the person to be approved U1.

[0035] See FIG. 4. In step S26, the server device 2 registers the candidate boarding and alighting locations included in the registration request signal as approved candidate boarding and alighting locations in the database 21. The server device 2 also associates the registered name and expiration date with the approved candidate boarding and alighting locations and stores them in the database 21. When the approved user U1 makes a reservation for a ride-hailing service, the server device 2 transmits the approved candidate boarding and alighting locations to the approved user terminal 4 in step S27. At this time, the server device 2 may transmit only approved candidate boarding and alighting locations that satisfy the time conditions for display on the approved user terminal 4 to the approved user terminal 4. When creating reservation information for a ride-hailing service (S8 in FIG. 2), the approved user terminal 4 displays the approved candidate boarding and alighting locations as candidate boarding and alighting locations available to the approved user U1 and presents them to the approved user U1. FIG. 3(c) shows an example of a boarding and alighting location selection screen displayed for selecting a boarding and alighting location when creating reservation information for a ride-hailing service on the approved user terminal 4. The boarding / alighting location selection screen 62 includes approved boarding / alighting location candidate selection fields 62a and 62b and a confirm button 62c.

[0036] A list of approved candidate boarding and alighting locations is displayed in the approved candidate boarding and alighting location selection fields 62a and 62b. The names of the approved candidate boarding and alighting locations displayed in the approved candidate boarding and alighting location selection fields 62a and 62b may be registered names set by the approver user U2. When the approved user terminal 4 receives an operation to select an approved candidate boarding and alighting location included in the approved candidate boarding and alighting location list in the approved candidate boarding and alighting location selection fields 62a and 62b and a press of the decision button 62c, the approved user terminal 4 creates reservation information that includes the selected approved candidate boarding and alighting location as a boarding and alighting location. The boarding and alighting location selection screen 62 may distinguish between approved candidate boarding and alighting locations for which a time condition is set for display on the approved user terminal 4 (e.g., candidates displayed in the approved candidate boarding and alighting location selection field 62a) and approved candidate boarding and alighting locations for which a time condition is not set (e.g., candidates displayed in the approved candidate boarding and alighting location selection field 62b). Furthermore, if there are any newly registered approved candidate boarding and alighting locations between the last time the boarding and alighting location selection screen 62 is displayed on the approval recipient terminal 4 and the current time, the newly registered approved candidate boarding and alighting location may be displayed with an update mark 62d added. Furthermore, when the server device 2 receives reservation information including the approved candidate boarding and alighting location as a boarding and alighting location (i.e., when the candidate boarding and alighting location approved by the approver user U2 is selected as the candidate boarding and alighting location to be used by the approval recipient user U1), the server device 2 may transmit a selection result signal to the approver terminal 5 informing the approver user U2 of the approved candidate boarding and alighting location selected by the approval recipient user U1. The approver terminal 5 may notify the approver user U2 of the approved candidate boarding and alighting location selected by the approval recipient user U1.

[0037] Second Embodiment In the second embodiment, candidate boarding and alighting locations 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" as described in the claims. For example, the proxy approver user may be a relative of the approved user U1, or the parent or adult guardian of an acquaintance of the approved user U1. Figures 5(a) and 5(b) are diagrams of an example GUI of the approver terminal 5, and Figure 5(c) is a diagram of an example GUI of the proxy approver terminal used by the proxy approver user. The configuration of the proxy approver terminal may be the same as the configuration of the approver terminal 5. Figure 6 is a flowchart of an example information processing method of the second embodiment.

[0038] In step S30, a proxy approver user registration process is performed. FIG. 5A is a diagram showing an example of a proxy approver registration screen on the approver terminal 5. The proxy approver registration screen 63 includes an approver selection field 63a, a proxy approver selection field 63b, an ID input field 63c, and a confirm button 63d. The approver terminal 5 displays a list of candidate approver users received from the server device 2 in the candidate approver selection field 63a. For example, the server device 2 may transmit a list of candidate approver users including users registered in the database 21 as approver users of the approver user U2 to the approver terminal 5 as the list of candidate approver users. The approver terminal 5 also displays the list of candidate proxy approver users received from the server device 2 in the proxy approver selection field 63b. For example, the approver terminal 5 may transmit the identification information entered 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 candidate proxy approver users and transmit the list of candidate proxy approver users to the approver terminal 5. The server device 2 may generate a list of candidate proxy approver users based on history information of users previously designated as proxy approver users.

[0039] When the approver terminal 5 receives an operation to select the approved user U1 included in the list of candidate approver users in the approval recipient selection field 63a, an operation to select a proxy approver user included in the list of candidate proxy approver users in the proxy approver selection field 63b, and an operation to press the decision button 60d, it transmits the 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 the 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, the 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.

[0040] See FIG. 4. When the proxy approver starts the operation of registering candidate boarding and alighting locations for the approved user U1 on the proxy approver terminal, in step S31, the server device 2 determines 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 location information of the proxy approver user detected by a positioning device to the server device 2. The proxy approver terminal may also transmit location information (e.g., address) entered by the proxy approver user into the proxy approver terminal to the server device 2.

[0041] In step S33, the server device 2 searches for candidate boarding and alighting locations near the current location of the proxy approver user. The server device 2 transmits information about the candidate boarding and alighting locations obtained by the search to the proxy approver terminal. In step S34, the proxy approver terminal accepts an operation by the proxy approver user to select one of the candidate boarding and alighting locations searched and obtained by the server device 2 as a candidate boarding and alighting location available to the approved user U1. The operation of selecting a candidate boarding and alighting location 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 transmits a registration request signal including information about the selected candidate boarding and alighting location to the server device 2. The server device 2 transmits the received registration request signal and the location information of the proxy approver user to the approver terminal 5.

[0042] In step S36, the approver terminal 5 accepts an operation by the approver user U2 to approve the candidate boarding and alighting locations selected by the proxy approver user as candidate boarding and alighting locations available for use by the approved user U1. Figure 5(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 and alighting location registration screen 64 includes a map display field 64a, a candidate boarding and 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 around the proxy approver user's current location and the proxy approver user's current location 64h.

[0043] The candidate boarding and alighting location display field 64b displays the candidate boarding and alighting locations selected by the proxy approver user. The registered name input field 64c is entered by the approver user U2 as the registered name of the candidate boarding and alighting location selected by the proxy approver user. 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 and alighting location set by the proxy approver user. The comment input field 64e allows the approver user U2 to input a comment for the proxy approver user. The approver terminal 5 accepts the input operation of the comment by the approver user U2. When the approver terminal 5 accepts the operation of pressing the reject button 64g by the approver user U2 (step S36: N), the process proceeds to step S37. When the approver terminal 5 accepts the operation of pressing the approve button 64f (step S36: Y), the process proceeds to step S38.

[0044] 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 proxy approver user with a notification that the registration of the candidate boarding / alighting location has been rejected and the comment information, and then the processing 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 location included in the registration application signal received from the proxy approver terminal as an approved candidate boarding / alighting location in the database 21. The server device 2 also stores the registered name and expiration date in association with the approved candidate boarding / alighting location in the database 21.

[0045] 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 location has been approved, along with comment information. Figure 5(c) is a diagram of an example of an application result notification screen displayed on the proxy approver terminal to notify the user that the registration of the candidate boarding and alighting location has been approved. The application result notification screen 65 includes a map display field 65a, an approved candidate boarding and alighting location display field 65b, a registered name display field 65c, an expiration date display field 65d, a comment display field 65e, and a close button 65f.

[0046] The map display field 65a displays map information around the proxy approver user's current location and the proxy approver user's current location 65g. The approved candidate boarding and alighting location 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 and alighting location applied by the proxy approver user and approved by the approver user U2, respectively. The comment display field 65e displays comment information entered in the comment input field 64e of the approver terminal 5. See FIG. 4. In step S40, the server device 2 transmits the approved candidate boarding and alighting locations to the approvee terminal 4. At this time, the server device 2 may transmit only approved candidate boarding and alighting locations that satisfy the time conditions for display on the approvee terminal 4 to the approvee terminal 4. When creating reservation information for a ride-hailing service, the approvee terminal 4 displays the approved candidate boarding and alighting locations as possible candidates for the approvee user U1 and presents them to the approvee user U1.

[0047] Third Embodiment In the third embodiment, approved candidate boarding and disembarking locations are registered based on event information about events held in the business area where the approval-recipient user U1 uses the ride-hailing service. FIGS. 7(a) to 7(c) are diagrams illustrating an example of a GUI of the approver terminal 5, and FIG. 8 is a flowchart illustrating 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 approval-recipient user U1. FIG. 7(a) is a diagram illustrating an example of an approval-recipient selection screen 66 on the approver terminal 5, on which the approval-recipient user U1 is selected. The approval-recipient selection screen 66 includes an approval-recipient selection field 66a and a decision button 66b. The approver terminal 5 displays a list of candidate approval users received from the server device 2 in the approval-recipient selection field 60a. When the approver terminal 5 receives an operation to select the approved user U1 included in the list of candidate approved users in the approved user selection column 63a and an operation to press the decision button 66b, it sends the identification information of the approved user U1 to the server device 2.

[0048] See FIG. 8. In step S51, the server device 2 acquires, from the database 21, event information related to events to be held within the business area in which the approval-required user U1 uses the vehicle dispatch service. For example, the server device 2 may acquire event information related to events that match the age and hobbies of the approval-required user U1. The server device 2 may also acquire event information from a terminal device operated by the event organizer or from the 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, on which the event selection operation is performed. The event selection screen 67 includes an event selection field 67a and a confirmation button 67b.

[0049] The approver terminal 5 displays the list of event information received from the server device 2 in the event selection field 67a. When the approver terminal 5 receives an operation to select an event included in the list of event information in the event selection field 67a and an operation to press the decision button 67b, it 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 candidate approved users who match the attributes of the event selected in step S52, from among the approved users stored in association with the approver user U2. In step S53, the server device 2 searches for candidate boarding and disembarking locations near the location of the event selected by the approver user U2. The server device 2 transmits information on the candidate boarding and disembarking locations obtained by the search to the approver terminal 5.

[0050] In step S54, the approver terminal 5 accepts an operation by the approver user U2 to select from 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. 7C is a diagram showing an example of a candidate boarding and alighting location registration screen on the approver terminal 5, on which the boarding and alighting location selection operation is performed. 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 confirm button 68d. The map display field 68a displays map information around the event location and the event location 68e. The candidate boarding and alighting location display field 68b displays the names of the candidate boarding and alighting locations received from the server device 2. If there are multiple candidate boarding and alighting locations around the event location, the candidate boarding and alighting location registration screen 68 may include an input field through which the approver terminal 5 accepts an input operation to select a candidate boarding and alighting location. The permitted time display field 68c displays the permitted time for which display of the candidate boarding and alighting locations received from the server device 2 is permitted as a time condition for displaying the candidate boarding and alighting locations on the approved user terminal 4.

[0051] 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 event start time and a time a predetermined time after the event end time. Furthermore, 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. Upon accepting the press of the decision button 68d, the approver terminal 5 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. Furthermore, 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.

[0052] In step S56, the server device 2 registers the candidate boarding and alighting locations included in the registration request signal as approved candidate boarding and alighting locations in the database 21. The server device 2 also associates the permitted time with the approved candidate boarding and alighting locations and stores it in the database 21. 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 only approved candidate boarding and alighting locations that satisfy the time conditions to be displayed on the terminal 4 for the person to be approved to the terminal 4 for approval. When creating reservation information for a ride-hailing service, the terminal 4 for the person to be approved displays the approved candidate boarding and alighting locations as candidate boarding and alighting locations that the approved user U1 can use, and presents them to the user U1.

[0053] (Fourth Embodiment) In the fourth embodiment, the approved candidate boarding and alighting locations are registered by the approved user U1 based on the past history information of the boarding and alighting locations and the attributes of the locations. The approver user U2 also sets the permitted time for which the approved candidate boarding and alighting locations are permitted to be displayed on the approved user terminal 4. Figures 9(a) to 9(c) are diagrams showing an example of the GUI of the approver terminal 5, and Figure 10 is a flowchart showing an example of the information processing method of the fourth embodiment. In step S60, the approver terminal 5 accepts a selection operation by the approver user U2 to select the approved user U1. The processing of step S60 is similar to the processing of step S50 in Figure 8.

[0054] In step S61, the approver terminal 5 accepts an operation by the approver user U2 to select and approve candidate boarding and alighting locations available to the approved user U1. FIG. 9A is a diagram illustrating an example of a candidate boarding and alighting location registration screen on the approver terminal 5, on which the approval operation for candidate boarding and alighting locations is performed. The candidate boarding and alighting location registration screen 69 includes a keyword input field 69a, a candidate boarding and alighting location selection field 69b, and a decision button 69c. The approver terminal 5 displays a list of candidate boarding and alighting locations searched and acquired by the server device 2 in the candidate boarding and alighting location selection field 69b. For example, the approver terminal 5 may transmit a keyword entered by the approver user U2 in the keyword input field 69a to the server device 2. Furthermore, the database 21 may store keywords associated with information on each boarding and alighting location. The server device 2 may use the keywords to search the database 21 for candidate boarding and alighting locations and transmit the list of candidate boarding and alighting locations to the approver terminal 5. In addition, 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.

[0055] FIG. 9B is a diagram illustrating another example of a candidate boarding and alighting location registration screen on which the approver terminal 5 approves candidate boarding and alighting locations. The candidate boarding and alighting location registration screen 70 includes an attribute information input field 70a, a candidate boarding and alighting location selection field 70b, and a decision button 70c. The approver terminal 5 may transmit the attribute information of the boarding and alighting location entered 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 and alighting location, whether or not a terminal device that can be used as the approved user terminal 4 is installed at the boarding and alighting location may be entered in the attribute information input field 70a. The server device 2 may use the attribute information to search the database 21 for candidate boarding and alighting locations and transmit a list of candidate boarding and alighting locations 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 and alighting locations included in the list displayed in the candidate boarding and alighting location selection fields 69b and 70b. When the selection operation of the candidate boarding / alighting location and the pressing operation of the decision buttons 69c and 70c are accepted, the process proceeds to step S62.

[0056] In step S62, the approver terminal 5 accepts an operation by the approver user U2 to set a permitted time for which the candidate boarding and alighting locations selected in step S61 are permitted to be displayed on the approved user terminal 4 as a time condition for displaying the candidate boarding and alighting locations. FIG. 9C is a diagram illustrating an example of a permitted time setting screen 71 on the approver terminal 5, on which the permitted time setting operation is performed. The permitted time setting screen 71 may include a period setting field 71a, a repetition condition setting field 71b, a time setting field 71c, and a confirm button 71d. The period setting field 71a is used to input the start date and end date 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 date and end date 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 time and end time for which the permitted time is set within the 24 hours of a day.

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

[0058] In step S63, the server device 2 registers the candidate boarding and alighting locations included in the registration request signal in the database 21 as approved candidate boarding and alighting locations. The server device 2 also associates the permitted time and supplementary information with the approved candidate boarding and alighting locations and stores them in the database 21. In step S64, 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 only approved candidate boarding and alighting locations that satisfy the time conditions to be displayed on the terminal 4 for the person to be approved to the terminal 4 for approval. The terminal 4 for the person to be approved displays the approved candidate boarding and alighting locations as possible candidate boarding and alighting locations for the approved user U1 when creating reservation information for the ride-hailing service, and presents them to the terminal 4 for the person to be approved. The terminal 4 for the person to be approved displays the permitted time set for the approved candidate boarding and alighting locations and the supplementary information for the approved user U1.

[0059] The type, mode, or setting method of the permitted time set for an approved candidate boarding or alighting location may be switched depending on the attributes of the approved candidate boarding or alighting location. For example, in the case of a candidate boarding or alighting location for the approved user U1 to travel to the location of the approver user U2 or a proxy approver user, as in the first and second embodiments, the approver user U2 or a 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 or alighting location for participating in an event or a specific activity (e.g., 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.

[0060] (Effects of the Embodiments) (1) The information processing device includes a controller that executes the following processes: identifying a user who uses a vehicle dispatch service; 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; and, if the identified user is an approved user, presenting to the approved user candidate usage locations that have been approved by the approver user from among candidate usage locations that are predetermined candidates for use of the vehicle dispatch service. This restricts an approved user who requires approval from the approver user for use of the vehicle dispatch service from using the vehicle dispatch service in a location not intended by the approver user.

[0061] (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 candidate use locations to be presented to the approved user based on the acquired location information. This facilitates approval of candidate use locations for the approved user to travel to the location of the approver user or a related user. (3) The controller may execute a process of acquiring event information regarding events to be held in an area where the approved user uses a ride-hailing service, and a process of setting candidate use locations to be presented to the approved user based on the event information. This facilitates approval of candidate use locations for the approved user to participate in the event.

[0062] (4) The approver user may be able to set a time condition for presenting potential use locations to the approved user. This can restrict the approved user from using the ride-hailing service at a time unintended by the approver user. (5) The controller may execute a process for presenting the time condition and supplemental information related to the time condition to the approved user. This allows the approved user to recognize that a time condition has been set. (6) The approver user may be able to set a temporary or permanent period as the period for presenting potential use locations to the approved user. This can allow approval of use of the ride-hailing service for an appropriate period depending on, for example, the reason for using the ride-hailing service.

[0063] (7) The approver user may be able to set an alternative name for the candidate use location presented to the approved user that is different from the name preset in the vehicle dispatch system that provides the vehicle dispatch service. This makes it easier for a minor approved user to understand the candidate use location. (8) The controller may execute the following processes: generating a list of candidate use location based on past history information of the approved user's use of the candidate use location; presenting the list of candidate use location to the approver user; and accepting a result of the approver user's selection of one of the candidate use location included in the list. This allows the approver user to approve the candidate use location using past history information.

[0064] (9) The controller may execute the following processes: generating a list of candidate related users based on past history information of users designated by the approver user as related users; presenting the list of candidate related users to the approver user; and accepting a result of the approver user selecting one of the candidate related users included in the list as a related user. This allows the approver user to specify a related user using past history information. (10) The controller may execute the following processes: generating a list of candidate use locations based on attributes of the candidate use locations; presenting the list of candidate use locations to the approver user; and accepting a result of the approver user selecting one of the candidate use locations included in the list. This allows the approver user to approve the candidate use locations based on the attributes of the candidate use locations.

[0065] (11) The information processing device may include a database storing an association between an approver user and an approved user. This allows an appropriate approver user to approve the candidate boarding and disembarking locations used by the approved user. (12) The controller may execute a process to notify the approver user of a candidate use location selected by the approved user as a location where the approved user will use the ride-hailing 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.

[0066] All examples and conditional terms described herein are intended for educational purposes to aid 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 specifically described examples and conditions above, and the configuration of examples herein for illustrating 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 alterations can be made thereto without departing from the spirit and scope of the present invention.

[0067] 1... Vehicle dispatch service providing 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

1. A controller that executes a process of identifying a user who uses a carpooling service, a process of determining whether the identified user is an approvee user who requires approval by an approver user who is another user other than the identified user for using the carpooling service, and a process of presenting, to the approvee user, a candidate location for use that is a candidate predetermined as a location for using the carpooling service and that has been approved by the approver user, in the case where the identified user is the approvee user. An information processing apparatus characterized by comprising the controller.

2. The controller executes a process of acquiring position information of the approver user or a related user related to the approver user, and a process of setting the candidate location for use to be presented to the approvee user based on the acquired position information. The information processing apparatus according to claim 1, characterized by this.

3. The controller executes a process of acquiring event information regarding an event implemented in an area where the approvee user uses the carpooling service, and a process of setting the candidate location for use to be presented to the approvee user based on the event information. The information processing apparatus according to claim 1, characterized by this.

4. The information processing apparatus according to claim 1, characterized in that a time condition for presenting the candidate location for use to the approvee user can be set by the approver user.

5. The controller of the information processing apparatus according to claim 4 executes a process of presenting the time condition and supplementary information regarding the time condition to the approvee user.

6. The information processing apparatus according to claim 1, characterized in that a temporary period or a permanent period can be set by the approver user as a period for presenting the candidate location for use to the approvee user.

7. The information processing apparatus according to claim 1, characterized in that an alias different from a name preset in a carpooling system that provides the carpooling service can be set by the approver user as a name of the candidate location for use presented to the approvee user.

8. The controller generates a list of the candidate usage locations based on the past history information of the approved user using the candidate usage locations, presents the list of the candidate usage locations to the approver user, and accepts the result of the approver user selecting any of the candidate usage locations included in the list. The information processing apparatus according to claim 1, characterized in that it executes the above.

9. The controller generates a list of candidate related users based on the past history information of the users specified by the approver user as the related users, presents the list of the candidate related users to the approver user, and accepts the result of the approver user selecting any of the candidate related users included in the list as the related user. The information processing apparatus according to claim 2, characterized in that it executes the above.

10. The controller generates a list of the candidate usage locations based on the attributes of the candidate usage locations, presents the list of the candidate usage locations to the approver user, and accepts the result of the approver user selecting any of the candidate usage locations included in the list. The information processing apparatus according to claim 1, characterized in that it executes the above.

11. The information processing apparatus according to claim 1, characterized by comprising a database in which the approver user and the approved user are associated and stored.

12. The controller executes a process of notifying the approver user of the candidate usage location selected by the approved user as the usage location for using the car-sharing service among the candidate usage locations approved by the approver user. The information processing apparatus according to claim 1, characterized in that it executes the above.

13. A method for information processing, characterized by causing a controller to execute: a process of identifying a user who uses a vehicle dispatching service; a process of determining whether the identified user is an approvee user who requires approval by an approver user, who is another user other than the identified user, for using the vehicle dispatching service; and a process of presenting, to the approvee user, a candidate location for use, which is a candidate location predetermined as a use location for the vehicle dispatching service and is approved by the approver user, when the identified user is the approvee user.

Images