Information processing device and information processing method

Abstract

An information processing device (2) is provided with a controller that performs: a process (S3) for identifying a user (U1) who uses a vehicle dispatch service; a process (S3) for determining whether or not the identified user (U1) is a to-be-approved user, who requires approval from a approver user (U2) who is a user other than the identified user, for use of the vehicle dispatch service; and a process for, if the identified user (U1) is the to-be-approved user, presenting, to the approver user (U2), a notification prompting the approver user (U2) to confirm whether or not to approve, as a candidate for a use location that can be used by the to-be-approved user (U1), a use location candidate that has been selected by the to-be-approved user (U1) from among use location candidates that are candidates predetermined as use locations for 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 enable an approved user, who requires approval from an approver user to use the vehicle dispatch service, to select the location where the vehicle dispatch service will be used, and to restrict the approver user from using the vehicle dispatch service in a location unintended 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 a notification to the approver user that allows the approver user to choose whether to approve a candidate usage location selected by the approved user from among candidate usage location locations that are predetermined candidates for locations where the ride-hailing service can be used as a candidate usage location that the approved user can use.

[0006] According to the present invention, an approved user who requires approval from an approver user to use a ride-hailing service can select the location where the ride-hailing service is used, and the approver user can be restricted from using the ride-hailing service in an unintended location. 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 (f) are diagrams of an example of a GUI of a terminal for a person to be approved according to the first embodiment, and (b) to (e) are diagrams of an example of a GUI of a terminal for a person to be approved according to the first embodiment. FIG. 1 is a flowchart of an example of an information processing method according to the first embodiment. (a) is a diagram of an example of a GUI of a terminal for a person to be approved according to the second embodiment, and (b) is a diagram of an example of a GUI of a terminal for an approver according to the third embodiment. FIG. 2 is a flowchart of an example of an information processing method according to the third 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 approval recipient 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 approval recipient 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 minor (e.g., a child) under a certain age or an elderly person. For example, approver user U2 may be the parent or adult guardian of approved user U1. In the following description, users of the vehicle dispatch service, including user U1 and user 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] FIG. 2 is a sequence diagram of an example of processing in the vehicle-dispatch service providing system 1. In step S1, the terminal 4 for the person to be approved accepts a login operation by the user U1 to be approved. In step S2, the terminal 4 for the person to be approved transmits user information of the user U1 to the server device 2. The user information may include identification information of the user U1 to be approved. In step S3, the server device 2 authenticates the user U1 to be approved based on the user information. At this time, the server device 2 determines whether the user U1 to be approved is a person who requires approval from another user for using the vehicle-dispatch service based on the user registration information of the user U1 registered in the database 21. For example, the database 21 may store information indicating whether the user U1 to be approved is a person to be approved, in association with the identification information of the user U1 to be approved.

[0025] In step S4, the approval-required user U1 performs an operation on the approval-required terminal 4 to request the approver user U2 to approve the addition of candidate boarding and alighting locations that the approval-required user U1 can use among the boarding and alighting locations of the ride-hailing service (hereinafter, sometimes referred to as "candidate boarding and alighting locations"). At this time, the approval-required terminal 4 accepts the selection input of the candidate boarding and alighting locations by the approval-required user U1. In step S5, the approval-required terminal 4 transmits an approval request signal to the server device 2 requesting approval of the selected candidate boarding and alighting locations. In step S6, the server device 2 transmits the approval request signal received from the approval-required terminal 4 to the approver terminal 5.

[0026] In step S7, the approver terminal 5 accepts an operation to approve or disapprove the addition of the candidate boarding or alighting location requested by the approval request signal. In the following description, a candidate boarding or alighting location approved by the approver user U2 as a candidate boarding or alighting location available to the approved user U1 may be referred to as an "approved candidate boarding or alighting location." In step S8, the approver terminal 5 transmits an approval / disapproval notification signal to the server device 2, notifying the approver user U2 of the approval or disapproval of the candidate boarding or alighting location. In step S9, if the approved user terminal 4 is a terminal device personally owned by the approved user U1, the server device 2 transmits an approval / disapproval notification signal to the approved user terminal 4. If the approver user U2 approves the addition of the candidate boarding or alighting location, the server device 2 newly registers (adds) the approved candidate boarding or alighting location in the database 21 as a candidate boarding or alighting location available to the approved user U1 in step S10. 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. If the approver user U2 does not approve the addition of the candidate boarding / alighting location, the server device 2 does not register the candidate boarding / alighting location for which the approved user U1 has requested approval. Meanwhile, in step S11, the approved user terminal 4, which has received the approval / disapproval notification signal, notifies (presents) the approved user U1 of the result of the approver user U2's approval or disapproval of the candidate boarding / alighting location. Furthermore, the meaning of "present" includes the meaning of being able to present based on a user operation.

[0027] When the approval-subject user U1 arranges for a service vehicle 3, in step S12, the approval-subject terminal 4 acquires candidate boarding and alighting location information regarding boarding and alighting locations for the vehicle dispatch service from the server device 2. If the approval-subject user U1 is the person being approved, the server device 2 transmits candidate boarding and alighting location information to the approval-subject 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-subject user U1 and registered in the database 21. In step S13, the approval-subject terminal 4 generates reservation information including information on the boarding location, boarding date and time, and alighting location based on the input operation of the approval-subject user U1. At this time, the approval-subject user U1 selects a boarding and alighting location from the approved candidate boarding and alighting locations. In step S14, the approval-subject terminal 4 transmits the reservation information to the server device 2.

[0028] In step S15, 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. Also, 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 S16, the server device 2 transmits the driving plan information to the service vehicle 3. In step S17, 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 to transport the approved user U1 from the boarding location to the disembarking location.

[0029] Next, a process for adding a candidate boarding and alighting location available to the approval-recipient user U1 will be described. FIGS. 3(a) and 3(f) are diagrams illustrating an example of a GUI (Graphical User Interface) of the approval-recipient terminal 4 in the first embodiment, and FIGS. 3(b) to 3(e) are diagrams illustrating an example of a GUI of the approver terminal 5. FIG. 4 is a flowchart illustrating an example of an information processing method in the first embodiment. In step S20, the approval-recipient terminal 4 accepts an operation by the approval-recipient user U1 to select a candidate boarding and alighting location that the approval-recipient user U1 wishes to use from among the boarding and alighting locations of the ride-hailing service. FIG. 3(a) is a diagram illustrating an example of a candidate boarding and alighting location selection screen on the approval-recipient terminal 4, on which the candidate boarding and alighting location selection operation is performed. The candidate boarding and alighting location selection screen 60 includes a candidate boarding and alighting location selection field 60a, a keyword input field 60b, a supplemental information input field 60c, and a confirm button 60d.

[0030] The terminal 4 for the person to be approved displays a list of candidate boarding and alighting locations acquired from the server device 2 in the candidate boarding and alighting location selection field 60a. For example, the terminal 4 for the person to be approved may transmit to the server device 2 a keyword entered by the user U1 to be approved in the keyword input field 60b. Keywords may also be registered in the database 21 in association 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 terminal 4 for the person to be approved. For example, the server device 2 may generate a list of candidate boarding and alighting locations based on historical information of the past use of the boarding and alighting locations by the user U1 to be approved. For example, the server device 2 may generate a list of candidate boarding and alighting locations based on attributes of the boarding and alighting locations. For example, attribute information of the boarding and alighting locations may include information on whether the boarding and alighting location is a boarding and alighting location where a terminal device that can be used as the terminal 4 for the person to be approved is installed.

[0031] The official names of each boarding and alighting location of the ride-hailing service are preset in the database 21 by the operator of the ride-hailing service (hereinafter, sometimes simply referred to as 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 server device 2 may transmit the sub-names of the candidate boarding and alighting locations to the approval recipient terminal 4 as the names of the candidate boarding and alighting locations to be displayed on the approval recipient terminal 4 (i.e., the names to be presented to the approval recipient user U1). That is, the sub-names of the candidate boarding and alighting locations may be displayed in the candidate boarding and alighting location selection field 60a. The approval recipient terminal 4 may accept an operation by the approval recipient user U1 to input supplemental information regarding the selection of the candidate boarding and alighting location in the supplemental information input field 60c. The supplemental information may be the reason why the approval recipient user U1 selected the candidate boarding and alighting location. See FIG. 4. When the approved user U1 selects a candidate boarding / alighting location and presses the decision button 60d, in step S21 the approved user terminal 4 sends an approval request signal to the server device 2, which includes the selected candidate boarding / alighting location and supplementary information.

[0032] In step S22, the server device 2 transmits the approval request signal received from the approval-recipient terminal 4 to the approver terminal 5 of the approver user U2 of the approval-recipient user U1. This notifies the approver user U2 of the approval-recipient user U1's request for approval of the candidate boarding / alighting location selected by the approval-recipient user U1, prompting the approver user U2 to confirm whether or not to approve the candidate boarding / alighting location as a candidate boarding / alighting location available to the approval-recipient user U1. The server device 2 identifies the approver user U2 of the approval-recipient user U1 by referring to the database 21. The database 21 stores the identification information of the approver user U2 and the identification information of the approval-recipient user U1 in association with each other. For example, the database 21 may store the user registration information of the approval-recipient user U1 including the identification information of the approver user U2, and may store the user registration information of the approver user U2 including the identification information of the approval-recipient user U1. The operation of registering the association between the approval-recipient user U1 and the approver user U2 in the database 21 may be performed by the approver user U2 or by the administrator.

[0033] The approver terminal 5, which has received the approval request signal, notifies the approver user U2 that the approver user U1 has requested approval of the candidate boarding and alighting locations. For example, the approver terminal 5 may display a pop-up message 61a on the GUI home screen 61, as shown in FIG. 3(b), to promptly notify the approver user U2 of the approval request from the approver user U1. See FIG. 4. In step S23, the approver terminal 5 displays the approval request for the candidate boarding and alighting locations from the approver user U1 on the GUI screen. FIG. 3(c) is a diagram of an example of a candidate boarding and alighting location approval screen 62 on the approver terminal 5, on which the approval request for the candidate boarding and alighting locations is displayed. The candidate boarding and alighting location approval screen 62 includes a map display field 62a, a candidate boarding and alighting location display field 62b, a supplemental information display field 62c, a registered name input field 61d, a validity period input field 61e, a disapproval button 62f, and an approval button 62g.

[0034] The map display field 62a displays map information about the area surrounding the candidate boarding / alighting location for which the approved user U1 has requested approval, as well as the location 62h of the candidate boarding / alighting location. The candidate boarding / alighting location display field 62b displays the name of the candidate boarding / alighting location. The supplemental information display field 62c displays the supplemental information entered by the approved user U1 in the supplemental information input field 60c of the candidate boarding / alighting location selection screen 60 of FIG. 3(a). The registered name input field 61c is used to input an alternative name set by the approver user U2 for the candidate boarding / alighting location when the approver user U2 approves the candidate boarding / alighting location. In the following description, the alternative name for the candidate boarding / alighting location set by the approver user U2 may be referred to as the "registered name." The approver user U2 can input a registered name different from the official name or secondary name of the boarding / alighting location described above in the registered name input field 62d.

[0035] The validity period input field 62e is used to input a time condition for displaying the candidate boarding / alighting location on the approved person's terminal 4 when the approver user U2 approves the candidate boarding / alighting location. For example, the validity period input field 62e is used to input a validity period for displaying the candidate boarding / alighting location on the approved person's terminal 4. For example, the validity period input field 62e can select and input a temporary period (until December 22, 2023 in the example of FIG. 3(c)) or a permanent period (unlimited in the example of FIG. 3(c)). The temporary period may be set by a default value on the approver terminal 5 or may be input by the approver user U2. Note that the method for setting the validity period is not limited to the example of FIG. 3(c), and various types and modes of validity periods may be set (i.e., the validity period may be set by various setting methods).

[0036] FIG. 3( d ) shows another example of the validity period input field 62 e. In this example, the approver user U2 may select and set a validity period as a repeating time period ("Repeated Schedule" in the example of FIG. 3( d )), a validity period starting from the current time and ending at the end time ("3 hours from now" in the example of FIG. 3( d )), or a permanent period. FIG. 3( e ) shows an example of a validity period setting screen for setting a validity period as a repeating time period. The validity period setting screen 63 may include a period setting field 63 a, a repetition condition setting field 63 b, a time setting field 63 c, and a close button 63 d. The period setting field 63 a is used to input the start date and end date of the period for which the validity period is set. The repetition condition setting field 63 b is used to set a repetition condition for repeatedly setting the validity period between the start date and end date specified in the period setting field 63 a. For example, the repetition condition setting field 63 b may be used to set the day of the week for which the validity period is set every week. The time setting field 63c is used to set the start time and end time of the validity period within 24 hours of one day. When the close button 63d is pressed, the display on the approver terminal 5 returns to the candidate boarding and alighting location approval screen 62.

[0037] Furthermore, the type, mode, or setting method of the validity period set for a candidate boarding or alighting location may be switched depending on the attributes of the 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 the location of a proxy approver user (described later), the approver user U2 may set only the end point of the validity period. In this case, the validity period may be set to start from the current time and end at the end point. For example, in the case of a candidate boarding or alighting location for the approved user U1 to participate in an event or to participate in a specific activity (e.g., attending a cram school), as in the third embodiment described later, the approver user U2 may set both the start and end points of the validity period.

[0038] See FIG. 4. In step S24, the approver terminal 5 accepts input of a registered name in the registered name input field 62d. It also accepts input of a validity period in the validity period input field 62e. In step S25, the approver terminal 5 accepts an operation by the approver user U2 to approve the candidate boarding / alighting location (i.e., pressing the approve button 62g) or not approve it (i.e., pressing the disapproval button 62f). Upon accepting the approval operation, the approver terminal 5 transmits an approval / disapproval notification signal to the server device 2 in step S26, indicating that the candidate boarding / alighting location has been approved. In this case, the approval / disapproval notification signal includes information on the registered name and the validity period. Upon accepting the disapproval operation, the approver terminal 5 transmits an approval / disapproval notification signal to the server device 2, indicating that the candidate boarding / alighting location has not been approved.

[0039] When the server device 2 receives an approval / disapproval notification signal indicating that the candidate boarding / alighting location has been approved, the server device 2 registers the candidate boarding / alighting location specified in the approval request signal received from the terminal 4 for the person to be approved as an approved candidate boarding / alighting location in the database 21. The server device 2 also stores the registered name and validity period in the database 21 in association with the approved candidate boarding / alighting location. When the server device 2 receives an approval / disapproval notification signal indicating that the candidate boarding / alighting location is not approved, the server device 2 does not register the approved candidate boarding / alighting location in the database 21. Furthermore, if the terminal 4 for the person to be approved is a terminal device personally owned by the user U1 to be approved, the server device 2 transmits the approval / disapproval notification signal received from the terminal 5 for the approver to the terminal 4 for the person to be approved. The terminal 4 for the person to be approved, upon receiving the approval / disapproval notification signal, notifies (presents) the user U1 of the result of approval or disapproval of the candidate boarding / alighting location by the approver user U2.

[0040] When the approved user U1 makes a reservation for a ride-hailing service, the server device 2 transmits the approved candidate locations to the approved user terminal 4 in step S27. At this time, the server device 2 may transmit only approved candidate 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 (S13 in FIG. 2), the approved user terminal 4 displays the approved candidate locations as candidate locations available to the approved user U1 and presents them to the approved user U1. FIG. 3(f) is an example of a location selection screen displayed for selecting a location when creating reservation information for a ride-hailing service on the approved user terminal 4. The location selection screen 64 includes approved candidate location selection fields 64a and 64b and a decision button 64c.

[0041] A list of approved candidate boarding and alighting locations is displayed in the approved candidate boarding and alighting location selection fields 64a and 64b. The names of the approved candidate boarding and alighting locations displayed in the approved candidate boarding and alighting location selection fields 64a and 64b 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 64a and 64b and a press of the decision button 64c, 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 64 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 64a) 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 64b). Furthermore, if there are any newly registered approved candidate boarding and alighting locations between the last time the boarding and alighting location selection screen 64 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 64d 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.

[0042] (Variations) (1) In the above embodiment, the approver user U2, who is set as the approver for the approved user U1, decides whether to approve the candidate boarding and alighting locations selected by the approved user U1. However, a proxy approver user designated by the approver user U2 may also decide whether to approve the candidate boarding and alighting locations selected by the approved user U1. For example, the proxy approver user may be a relative of the approved user U1, or the guardian or adult guardian of an acquaintance of the approved user U1. In this case, for example, the approver terminal 5 may accept an operation by the approver user U2 to designate a user other than the approved user U1 or the approver user U2 as the proxy approver user for the approved user U1. The approver terminal 5 transmits identification information of the proxy approver user to the server device 2.

[0043] 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. 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. When the server device 2 receives an approval request signal requesting approval of the candidate boarding and alighting locations from the approved user terminal 4, it transmits the approval request signal to the proxy approver terminal used by the proxy approver, as in the case of the approver terminal 5. The configuration of the proxy approver terminal may be the same as the configuration of the approver terminal 5. The approval operation and non-approval operation at the proxy approver terminal are the same as the operations described with reference to Figures 3(c) to 3(e).

[0044] (2) The terminal 4 for the person to be approved may simultaneously accept the selection of multiple candidate boarding and alighting locations by the approved user U1. For example, the terminal 4 for the person to be approved may accept an operation to simultaneously select multiple candidate boarding and alighting locations from the list of candidate boarding and alighting locations displayed in the candidate boarding and alighting location selection field 60a on the candidate boarding and alighting location selection screen 60 of FIG. 3(a). In this case, the terminal 4 for the person to be approved may individually transmit an approval request signal for each of the multiple selected candidate boarding and alighting locations. In this case, the terminal 5 for the approver may individually display the pop-up message 61a of FIG. 3(b) for each of the multiple candidate boarding and alighting locations. Furthermore, the terminal 5 for the approver may individually display the candidate boarding and alighting location approval screen 62 of FIG. 3(c) for each of the multiple candidate boarding and alighting locations. In other words, the terminal 5 for the approver may individually accept an approval operation or a disapproval operation for each of the multiple candidate boarding and alighting locations.

[0045] (3) The database 21 may register candidate boarding and alighting locations that require the approval of the approver user U2 when used by the approved user U1, and candidate boarding and alighting locations that do not require the approval of the approver user U2. For example, for all or some of the boarding and alighting locations of the ride-hailing service, whether the candidate boarding and alighting location requires the approval of the approver user U2 or does not require the approval of the approver user U2 may be registered. For example, the approver terminal 5 may accept an operation by the approver user U2 to set candidate boarding and alighting locations that require the approval of the approver user U2 and candidate boarding and alighting locations that do not require the approval of the approver user U2, and transmit a registration request signal to the server device 2 requesting registration of these settings. Based on the registration request signal received from the approver terminal 5, the server device 2 may register candidate boarding and alighting locations that require the approval of the approver user U2 and candidate boarding and alighting locations that do not require the approval of the approver user U2 in the database 21.

[0046] When the server device 2 receives an approval request signal requesting approval of a candidate boarding or alighting location from the approved user terminal 4, the server device 2 may determine whether the candidate boarding or alighting location specified in the approval request signal is a candidate boarding or alighting location that requires approval from the approver user U2 or a candidate boarding or alighting location that does not require approval from the approver user U2. If the candidate boarding or alighting location specified in the approval request signal is a candidate boarding or alighting location that requires approval from the approver user U2, the server device 2 transmits the approval request signal to the approver terminal 5. In this case, the pop-up message 61a in FIG. 3(b) and the candidate boarding or alighting location approval screen 62 in FIG. 3(c) are displayed on the approver terminal 5. On the other hand, if the candidate boarding or alighting location specified in the approval request signal is a candidate boarding or alighting location that does not require approval from the approver user U2, the server device 2 does not transmit the approval request signal to the approver terminal 5. In this case, the pop-up message 61a and the candidate boarding or alighting location approval screen 62 are not displayed on the approver terminal 5.

[0047] 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 approver user U2 or the proxy approver user. The proxy approver user is an example of a "related user" as defined in the claims. FIG. 5(a) is a diagram illustrating an example of a GUI for the approved user terminal 4, and FIG. 5(b) is a diagram illustrating an example of a GUI for the approver terminal 5. When the approved user U1 selects a candidate boarding and alighting location to use in step S20 of FIG. 4, the approved user terminal 4 accepts the approval user U1's selection operation to select either the approver user U2 or the proxy approver user. FIG. 5(a) is a diagram illustrating an example of a candidate boarding and alighting location selection screen on the approved user terminal 4 on which the approver user U2 or the proxy approver user performs a selection operation. The candidate boarding and alighting location selection screen 65 includes a candidate boarding and alighting location selection field 65a and a decision button 65b.

[0048] The terminal 4 for the person to be approved displays a list of the approver user U2 and the proxy approver users acquired from the server device 2 in the candidate boarding and alighting location selection field 60a. The server device 2 may generate a list of candidate proxy approver users based on historical information of users previously designated as proxy approver users. When the terminal 4 for the person to be approved U1 accepts a selection operation to select either the approver user U2 or the proxy approver user included in the list and a pressing operation of the decision button 65b, the terminal 4 for the person to be approved transmits an approval request signal including identification information of the selected approver user U2 or proxy approver user (hereinafter sometimes referred to as the "selected user") to the server device 2 (step S21).

[0049] Upon receiving the approval request signal from the approval recipient terminal 4, the server device 2 acquires the current location information of the selected user in step S22. For example, the approver terminal 5 or the proxy approver terminal may transmit the location information of the selected user detected by the positioning device 50 to the server device 2. The approver terminal 5 or the proxy approver terminal may also transmit the location information (e.g., address) entered by the selected user to the server device 2. The server device 2 searches for candidate boarding and alighting locations near the selected user's current location and sets them as candidate boarding and alighting locations for which the approval recipient user U1 requests approval. The server device 2 transmits an approval request signal to the approver terminal 5, including information about the candidate boarding and alighting locations (identification information and official name) and the selected user's (identification information and location information). The approver terminal 5 displays a pop-up message 61a ( FIG. 3( b) ) notifying the approver user U2 that the approval recipient user U1 has requested approval of the candidate boarding and alighting locations.

[0050] In step S23, the approver terminal 5 displays a request for approval of the candidate boarding and alighting locations. Fig. 5(b) is a diagram showing an example of a candidate boarding and alighting location approval screen 62 on which the request for approval of the candidate boarding and alighting locations is displayed on the approver terminal 5. In the example of Fig. 5(b), map information of the area surrounding the current location of the approver user U2 ("MaMa") selected by the approvee user U1 in step S20 and the current location 62h are displayed. The subsequent processing in steps S24 to S27 is the same as in the first embodiment.

[0051] Third Embodiment In the third embodiment, candidate boarding and disembarking locations available to the approval-subject user U1 are determined based on event information about events held in the business area where the approval-subject user U1 uses the ride-hailing service. FIG. 6 is a diagram illustrating an example of a GUI of the approval-subject user terminal 4, and FIG. 7 is a flowchart illustrating an example of an information processing method according to the third embodiment. In step S30, the server device 2 acquires event information about events held in the business area where the approval-subject user U1 uses the ride-hailing service from the database 21. For example, the server device 2 may acquire event information about events that match the age and hobbies of the approval-subject 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 approval-subject user terminal 4.

[0052] In step S31, the terminal 4 for the person to be approved accepts an operation by the user U1 to select one of the events received from the server device 2. Fig. 6 is a diagram showing an example of an event selection screen 66 on the terminal 4 for the person to be approved. The event selection screen 66 includes an event selection field 66a and a confirm button 66b. The terminal 4 for the person to be approved displays a list of event information received from the server device 2 in the event selection field 66a. Upon accepting an operation to select an event included in the list of event information in the event selection field 66a and an operation to press the confirm button 66b, the terminal 5 for the approver transmits an approval request signal including the selected event information to the server device 2 in step S32.

[0053] In step S33, when the server device 2 receives the approval request signal from the approval-recipient terminal 4, it searches for candidate boarding and alighting locations near the location of the event selected by the approval-recipient user U1 and sets them as candidate boarding and alighting locations for which the approval-recipient user U1 is requesting approval. The server device 2 transmits an approval request signal including information about the candidate boarding and alighting locations (identification information and official name) to the approver terminal 5. The approver terminal 5 displays a pop-up message 61a (FIG. 3(b)) notifying the approver user U2 that the approval-recipient user U1 has requested approval of the candidate boarding and alighting locations. The subsequent processing of steps S34 to S38 is the same as the processing of steps S23 to S27 in the first embodiment.

[0054] (Effects of the Embodiments) (1) The information processing device 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 from an approver user other than the identified user for use of the ride-hailing service; and, if the identified user is an approved user, presenting a notification to the approver user prompting the approver user to confirm whether to approve a candidate use location selected by the approved user from among candidate use location locations that are predetermined candidates for use of the ride-hailing service as a candidate use location that the approved user can use. This enables an approved user who requires approval from the approver user for use of the ride-hailing service to select a location for use of the ride-hailing service and restricts the approver user from using the ride-hailing service in places unintended by the approver user.

[0055] (2) The controller may execute a process to present the approver user with map information of the candidate use location selected by the approvee user or supplementary information regarding the selection of the candidate use location by the approvee user. This makes it easier for the approver user to determine whether to approve the candidate use location. (3) The approver user may be able to set candidate use locations that require the approver user's approval when used by the approvee user and candidate use locations that do not require the approver user's approval. When the approvee user selects a candidate use location that requires the approver user's approval, the controller may execute a process to present the approver user with a notification prompting the approver user to confirm whether or not to approve. This can eliminate unnecessary approval operations by the approver user.

[0056] (4) The controller may execute the following processes: accepting a selection result from an approval recipient user who selects either the approver user or a related user related to the approver user; acquiring location information of the approver user or the related user; and determining a potential use location selected by the approval recipient user based on the selection result and the location information. This facilitates the approval recipient user to request approval of a potential use location for traveling to the location of the approver user or the related user.

[0057] (5) The controller may perform a process of acquiring event information regarding events held in an area where the approved user uses the ride-hailing service, and a process of determining a candidate use location selected by the approved user based on the event information. This makes it easier for the approved user to request approval of a candidate use location for participating in the event. (6) The controller may perform a process of presenting the candidate use location approved by the approver user to the approved user. The time conditions for presenting the candidate use location to the approved user may be set by the approver user or a related user related to the approver user. This makes it possible to restrict the approved user from using the ride-hailing service at times unintended by the approver user.

[0058] (7) The controller may perform a process of presenting the candidate use locations approved by the approver user to the approved user. The period for which the candidate use locations are presented to the approved user may be set by the approver user or a related user associated with the approver user as a temporary or permanent period. This allows the use of the ride-hailing service to be approved for an appropriate period depending on, for example, the reason for using the ride-hailing service. (8) The name of the candidate use locations presented to the approved user may be set by the approver user or a related user associated with the approver user to an alternative name that is different from the name pre-set in the ride-hailing system that provides the ride-hailing service. This makes it easier for minor approved users to understand the candidate use locations.

[0059] (9) The information processing device may include a database storing an association between an approver user and an approved user. This allows the appropriate approver user to approve the candidate boarding and disembarking locations used by the approved user. (10) The controller may execute a process of presenting a notification to the approver user for each of multiple candidate use locations selected by the approved user, prompting the approver user to confirm whether or not to approve the location. This makes it easier for the approved user to request approval of multiple candidate use locations. (11) The controller may execute a process of accepting a designation result of a proxy approver user designated by the approver user, and a process of presenting a notification to the proxy approver user prompting the proxy approver user to confirm whether or not to approve the candidate use location selected by the approved user from among the candidate use location locations that are predetermined candidates for use locations of the ride-hailing service as a candidate use location that the approved user can use. This allows the approver user to delegate approval of the candidate use location by the approved user to the proxy approver user.

[0060] 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.

[0061] 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 process for identifying a user who uses a carpooling service, a process for determining whether the identified user is an approvee user who requires approval from an approver user who is another user other than the identified user for using the carpooling service, and when the identified user is the approvee user, a process of presenting a notice to the approver user for selecting whether to approve the place candidate selected by the approvee user as a place candidate that the approvee user can use among the place candidates that are predetermined as the use places of the carpooling service. An information processing apparatus characterized by comprising a controller that executes the above processes.

2. The information processing apparatus according to claim 1, wherein the controller executes a process of presenting map information of the place candidate selected by the approvee user or supplementary information regarding the selection of the place candidate by the approvee user to the approver user.

3. The place candidates that require approval from the approver user when the approvee user uses them and the place candidates that do not require approval from the approver user can be set by the approver user. The controller executes a process of presenting a notice for selecting whether to approve to the approver user when the approvee user selects a place candidate that requires approval from the approver user. The information processing apparatus according to claim 1.

4. The controller executes a process of receiving a selection result of the approvee user for selecting either the approver user or a related user related to the approver user, a process of acquiring position information of the approver user or the related user, and a process of determining a place candidate selected by the approvee user based on the selection result and the position information. The information processing apparatus according to claim 1.

5. 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 determining a place candidate selected by the approvee user based on the event information. The information processing apparatus according to claim 1.

6. The controller performs a process of presenting the utilization location candidates approved by the approver user to the approved user, and the time condition for presenting the utilization location candidates to the approved user can be set by the approver user or a related user related to the approver user. The information processing apparatus according to claim 1, characterized in that.

7. The controller performs a process of presenting the utilization location candidates approved by the approver user to the approved user, and as the period for presenting the utilization location candidates to the approved user, a temporary period or a permanent period can be set by the approver user or a related user related to the approver user. The information processing apparatus according to claim 1, characterized in that.

8. As the name of the utilization location candidates presented to the approved user, an alias different from the name preset in the vehicle dispatching system that provides the vehicle dispatching service can be set by the approver user or a related user related to the approver user. The information processing apparatus according to claim 1, characterized in that.

9. The information processing apparatus according to claim 1, characterized in that it includes a database in which the approver user and the approved user are associated and stored.

10. The controller executes a process of presenting a notification for selecting whether to approve each of the plurality of utilization location candidates selected by the approved user to the approver user. The information processing apparatus according to claim 1, characterized in that.

11. The controller performs a process of receiving the designation result of the proxy approver user designated by the approver user, and among the utilization location candidates that are candidates predetermined as the utilization locations of the vehicle dispatching service, a notification for selecting whether to approve the utilization location candidate selected by the approved user as a utilization location candidate that the approved user can use is presented to the proxy approver user. The information processing apparatus according to claim 1, characterized in that it executes the process.

12. A process for identifying a user who uses a carpooling service, a process for 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 when the identified user is the approvee user, a process for presenting a notice to the approver user to select whether to approve the use location candidate selected by the approvee user as a use location candidate that the approvee user can use among the use location candidates that are predetermined candidates for the use location of the carpooling service. An information processing method characterized by causing a controller to execute the above processes.

Images