Information processing system, information processing method, and program
The system addresses the inefficiency of manual taxi reservations by using sensing devices to detect and automate dispatches based on user behavior patterns, improving convenience by reducing user effort and streamlining the reservation process.
Patent Information
- Application Number
- JP2025157995
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-09-24
- Publication Date
- 2026-01-06
AI Technical Summary
Existing taxi reservation systems require significant user effort and cumbersome operations, particularly for regular users, due to the need for multiple inputs and confirmations, which can be burdensome.
An information processing system that utilizes sensing devices to detect user behavior patterns and automatically determines and executes taxi dispatches based on registered behavior patterns, reducing the need for manual input and confirmation.
Automated taxi dispatches based on user behavior patterns streamline the reservation process, minimizing user effort and enhancing convenience by allowing seamless taxi usage without repeated manual interactions.
Smart Images

Figure 2026001082000001_ABST
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to an information processing device, an information processing method, a program, and an information processing system. [Background technology]
[0002] Traditionally, the method of reserving a taxi was to call a taxi company in advance and have the taxi take you to a specified location. In recent years, however, services have been provided that allow you to reserve a taxi via the Internet using a smartphone or other device.
[0003] For example, Patent Document 1 below discloses that the user inputs the taxi's departure point, destination, and additional information (such as payment method), and then the user confirms the route from the taxi's departure point to the destination and fare information before making a taxi dispatch request. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Patent Publication No. 2021-51659 Summary of the Invention [Problem to be solved by the invention]
[0005] However, in the above-mentioned Patent Document 1, the user's man-hours required for requesting a vehicle dispatch are large, and the reservation operation is cumbersome. For example, depending on the user's usage pattern, such as when using taxis regularly, the effort required for requesting a vehicle dispatch each time can be a burden.
[0006] Therefore, the present disclosure proposes an information processing device, an information processing method, a program, and an information processing system that can reduce the user's effort in dispatching a taxi. [Means for solving the problem]
[0007] According to the present disclosure, an information processing device is proposed that includes a control unit that determines whether or not a taxi needs to be dispatched based on the sensing results of user behavior and the registered user behavior patterns.
[0008] According to the present disclosure, an information processing method is proposed, which includes a processor determining whether or not a taxi needs to be dispatched based on the sensing results of user behavior and the registered user behavior patterns.
[0009] According to the present disclosure, a program is proposed that causes a computer to function as a control unit that determines whether or not a taxi needs to be dispatched based on the sensing results of user behavior and the registered user behavior patterns.
[0010] According to the present disclosure, an information processing system is proposed that includes one or more sensing devices that sense user behavior, and an information processing device having a control unit that determines whether or not a taxi needs to be dispatched based on the sensing results of the user behavior obtained from the one or more sensing devices and the behavior patterns of registered users. [Brief explanation of the drawings]
[0011] [Figure 1] 1 is a diagram illustrating an overview of an information processing system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of a server according to the present embodiment. [Figure 3] FIG. 10 is a sequence diagram illustrating an example of a process for registering a user's behavior pattern according to the present embodiment. [Figure 4] FIG. 10 is a diagram showing an example of a registration confirmation screen according to the present embodiment. [Figure 5] FIG. 10 is a sequence diagram illustrating an example of a process for registering a user's behavior pattern according to the present embodiment. [Figure 6] FIG. 4 is a sequence diagram illustrating an example of a vehicle reservation process according to the present embodiment. [Figure 7]FIG. 3 is a sequence diagram illustrating the flow of a vehicle reservation process according to a first example of the present embodiment. [Figure 8] FIG. 10 is a sequence diagram illustrating the flow of a vehicle reservation process according to a second example of the present embodiment. [Figure 9] 10 is a flowchart showing the flow of a first operation process according to another embodiment of the present disclosure. [Figure 10] 10 is a flowchart showing the flow of a second operation process according to another embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION
[0012] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functional configurations are designated by the same reference numerals, and redundant description will be omitted.
[0013] The explanation will be given in the following order: 1. Overview of information processing system according to one embodiment of the present disclosure 2.Configuration example 3. Operation processing 3-1. Registration process 3-2. Vehicle reservation processing 3-3. Example of vehicle reservation processing 4. Use of reservation waiting list 5. Supplementary Information
[0014] <<1. Overview of Information Processing System According to One Embodiment of the Present Disclosure>> 1 is a diagram illustrating an overview of an information processing system according to an embodiment of the present disclosure. As shown in FIG. 1, the information processing system according to this embodiment includes one or more sensing devices 30 that sense user behavior, a user terminal 10 that senses user behavior and also receives user operation input and presents information, a server 20, and a taxi dispatch server 40.
[0015] The server 20 is connected to a taxi dispatch server 40 for communication and can request the taxi dispatch server 40 to make a taxi dispatch reservation.
[0016] The taxi dispatch server 40 manages taxi dispatch reservation information and transmits the taxi dispatch reservation information to each taxi company server or each taxi. In response to a taxi dispatch reservation request from the server 20, the taxi dispatch server 40 searches for a taxi that can be dispatched and can reply to the server 20 whether or not the taxi dispatch reservation was successful. The taxi dispatch server 40 is connected to multiple taxi company servers (not shown) and can search for taxis that can be scheduled from multiple taxi companies.
[0017] The user terminal 10 is an example of an information processing terminal used by a user. The user terminal 10 may be a smartphone, a tablet terminal, a PC, or a wearable device (such as a transparent / non-transparent HMD (head mounted display), a smart ring, or a smart watch). The user terminal 10 can communicate with the server 20 and transmit and receive data.
[0018] (Identifying issues) Here, while it is highly convenient to be able to reserve a taxi using a smartphone, etc., the operation is cumbersome due to the large number of input fields and the need to communicate with the server multiple times (the confirmation screen is displayed multiple times). For example, if a user uses a taxi regularly, depending on the user's usage pattern, the hassle of having to go through the process every time can be bothersome and burdensome.
[0019] Therefore, the information processing system according to the present disclosure makes it possible to reduce the effort required of users when dispatching a taxi.
[0020] Specifically, the server 20 determines whether or not a taxi needs to be dispatched based on the sensing data of user behavior (sensing results of user behavior) acquired by the sensing device 30 and the user terminal 10 and the registered behavioral patterns of the user. The behavioral patterns include behavior related to the user's taxi rides. For example, if the user uses taxis regularly, the server 20 registers the user's behavioral patterns when riding a taxi based on the sensing data, and automatically determines that a taxi needs to be dispatched if the user exhibits a similar behavioral pattern, thereby reducing the user's effort in dispatching a taxi. Note that the behavioral patterns to be registered may be learned from the user's actual behavior as described above, or may be arbitrarily set by the user in advance.
[0021] The sensing device 30 includes various sensors worn or carried by the user and various sensors installed in the environment. The sensing device 30 has a communication function and transmits acquired data (sensing data) to the server 20. Examples of the sensing device 30 include surveillance cameras installed outdoors or indoors, authentication terminals installed at building entrances, and various IoT devices around the user (motion sensors at the entrance, alarm clocks, motion sensors in the bedroom, cameras installed in the living room or bathroom sink, smart speakers, etc.). The sensing device 30 is assumed to be various sensors that detect user behavior, and the installation location, installation method, type, number, etc. are not particularly limited. The user behavior is detected as needed by various sensors and transmitted to the server 20. The surveillance camera, authentication terminal, etc. may associate the user's face recognition information or identification information (terminal ID or user ID) received from the user terminal 10 carried by the user with the sensing data and transmit it to the server 20, and the server 20 may recognize the user (personal recognition).
[0022] In this embodiment, the user terminal 10 carried by the user also acquires various types of sensing data and transmits the data as sensing results of user behavior to the server 20. In other words, the user terminal 10 can be said to be an example of a sensing device.
[0023] The outline of the information processing system according to an embodiment of the present disclosure has been described above. Next, a specific configuration of the server 20 included in the information processing system according to the present embodiment will be described with reference to the drawings.
[0024] <<2. Example of Server 20 Configuration>> 2 is a block diagram showing an example of the configuration of the server 20 according to this embodiment. As shown in FIG. 2, the server 20 includes a communication unit 210, a control unit 220, and a storage unit 230.
[0025] (Communication unit 210) The communication unit 210 transmits and receives data to and from external devices via wired or wireless communication. The communication unit 210 is connected to and communicates with the user terminal 10 and the event management terminal 50 using, for example, wired / wireless LAN (Local Area Network), Wi-Fi (registered trademark), Bluetooth (registered trademark), or a mobile communication network (LTE (Long Term Evolution), 4G (fourth generation mobile communication method), 5G (fifth generation mobile communication method)), etc.
[0026] (control unit 220) The control unit 220 functions as an arithmetic processing unit and a control device, and controls the overall operation of the server 20 in accordance with various programs. The control unit 220 is realized by electronic circuits such as a CPU (Central Processing Unit) or a microprocessor. The control unit 220 may also include a ROM (Read Only Memory) that stores the programs to be used, arithmetic parameters, etc., and a RAM (Random Access Memory) that temporarily stores parameters that change as appropriate.
[0027] The control unit 220 according to this embodiment also functions as a behavior history storage processing unit 221, a behavior pattern registration processing unit 222, a vehicle dispatch necessity determination unit 223, and a vehicle dispatch reservation processing unit 224.
[0028] The behavior history storage processing unit 221 stores the user's behavior history in the storage unit 230 based on the sensing results of user behavior acquired from the sensing device 30 or the user terminal 10. The sensing results may be sensing data (raw data) as is, sampled data, or data generated based on the sensing data (processed data). The behavior history storage processing unit 221 particularly stores behavior related to taxi riding as behavior history. Behavior related to taxi riding includes, for example, the user's behavior up to reserving a taxi and the user's behavior up to getting into the taxi. The behavior history storage processing unit 221 stores date and time information, location information, details, etc. of such behavior. The behavior history may also include a taxi riding history (ride date and time, location, destination, etc.). For example, if a taxi reservation application is downloaded to the user terminal 10 and the user makes a reservation or the like using the application, the server 20 may acquire the user's riding history from the application. The behavior history may also include information about the situation when the behavior was performed. Information about the situation includes, for example, weather information, traffic information, etc.
[0029] The behavior pattern registration processing unit 222 performs a process of registering a behavior pattern for determining the need for taxi dispatch in the dispatch necessity determination unit 223. The behavior pattern registration processing unit 222 extracts and registers, for example, a behavior pattern of a user reserving a taxi dispatch or riding in a taxi from the user's behavior history. As an example, if a user performs a certain behavior and then calls a taxi (reserving a taxi dispatch) a predetermined number of times or more, the behavior pattern registration processing unit 222 registers the behavior as a behavior pattern. As a result, if the user performs the same behavior again, the dispatch necessity determination unit 223 may determine that a taxi dispatch is necessary. Furthermore, if the user performs the behavior of riding a taxi from the same location at the same time on the same day of the week a predetermined number of times or more, the behavior pattern registration processing unit 222 may register the day of the week, time, and location as a behavior pattern. At this time, the behavior of the user leading up to the pickup location may also be referenced, and behavior from a certain time prior may be registered as a behavior pattern for determining that a taxi dispatch reservation is necessary so that a taxi has already arrived when the user arrives at the pickup location.
[0030] The dispatch necessity determination unit 223 determines whether a taxi needs to be dispatched based on the sensing results of the user's behavior and the registered user's behavior pattern. Specifically, the dispatch necessity determination unit 223 determines that a taxi needs to be dispatched when the sensing results of the user's behavior match the registered user's behavior pattern. Then, the dispatch reservation processing unit 224 performs processing to execute a taxi dispatch reservation. Specifically, the dispatch reservation processing unit 224 requests a taxi dispatch reservation from the taxi dispatch server 40. In requesting the taxi dispatch reservation, for example, the dispatch reservation processing unit 224 transmits information on the time, boarding location, and destination to the taxi dispatch server 40.
[0031] (Storage unit 230) The storage unit 230 is realized by a ROM (Read Only Memory) that stores programs and calculation parameters used in the processing of the control unit 220, and a RAM (Random Access Memory) that temporarily stores parameters that change as appropriate. In this embodiment, the storage unit 230 stores information about the virtual space.
[0032] The storage unit 230 according to this embodiment stores information about the user's behavior history, behavior patterns, and vehicle reservation.
[0033] Although the configuration of the server 20 has been specifically described above, the configuration of the server 20 according to the present disclosure is not limited to the example shown in Fig. 2. For example, the server 20 may be realized by a plurality of devices.
[0034] <<3. Operation Processing>> Next, the operation and processing of the information processing system according to this embodiment will be specifically described with reference to the drawings. Specifically, the process of registering a user's behavior pattern and the process of booking a vehicle according to the sensing results of the user's behavior will be described in order.
[0035] <3-1. Registration process> First, some specific examples of the process of registering a user's behavior pattern will be described with reference to the drawings.
[0036] (3-1-1. Using a taxi when going out from work) 3 is a sequence diagram illustrating an example of a process for registering a user's behavior pattern according to this embodiment. In FIG. 3, an example is described in which a user who takes a taxi every time he or she leaves the office is registered as a behavior pattern.
[0037] 3, first, when a camera (an example of sensing device 30) installed at the entrance or in the hallway of the conference room detects that a user is leaving the conference room (step S103), it transmits the detection result (sensing result of user behavior) to server 20 (step S106). Server 20 stores the fact that the user has left the conference room (which conference room, the date and time when the user left the conference room, etc.) (step S109).
[0038] Next, when the user terminal 10 detects that the user is getting off in the elevator (step S112), it transmits the detection result to the server 20 (step S115). The user terminal 10 may be provided with, for example, a positioning unit or a motion sensor, and may detect from sensing data that the user is getting off in the elevator. The positioning unit may include an outdoor positioning unit and an indoor positioning unit. The outdoor positioning unit may calculate the user's current location information using a Global Navigation Satellite system (GNSS). The indoor positioning unit may calculate the current location information using Wi-Fi, a beacon, or the like. The server 20 stores the fact that the user is getting off in the elevator (such as the number of floors the user has gotten off, and the date and time the user got on the elevator) (step S118).
[0039] Next, when the user terminal 10 detects that the user has called a taxi (a taxi reservation) using a taxi-dispatch app (an application for making a taxi reservation) (step S121), it transmits the detection result to the server 20 (step S124). The server 20 stores information that the user has called a taxi (such as the boarding time, boarding location, destination, and date and time of the taxi reservation) (step S127). Note that, although the case where a taxi is called using a taxi-dispatch app is described here as an example, the means for calling a taxi is not particularly limited. When the user calls a taxi using a website, telephone, email, SNS (Social Networking Service), or the like, the user terminal 10 detects such behavior and transmits the detection result to the sensing device 30. Information about the user's taxi reservation is not limited to being received from the user terminal 10, but may also be received from, for example, the taxi-dispatch server 40.
[0040] Next, when the company entrance / exit management system (an example of the sensing device 30) detects that the user has left the company (step S130), it transmits the detection result to the server 20 (step S133). The server 20 stores the fact that the user has left the company (such as the date and time when the user left the company) (step S136).
[0041] Next, when the user terminal 10 detects that the taxi has arrived at the destination and the user has gotten off (step S139), it transmits the detection result to the server 20 (step S142). The server 20 stores the fact that the user has arrived at the destination (the destination, the date and time, etc.) (step S145). Here, the server 20 stores the fact that the taxi has arrived at the destination and gotten off, but the server 20 may also acquire and store from the user terminal 10 the fact that the user has gotten on a taxi (the place where the taxi got on, the date and time of the taxi, etc.).
[0042] As described above, the server 20 stores the user's behavior history as needed. The server 20 may store only behavior related to taxi riding. For example, the server 20 may keep only the behavior from a certain time before the taxi ride to getting off (for example, the behavior from 15 minutes before the ride to getting off), and delete the rest.
[0043] Next, the server 20 determines whether the same behavior has occurred a predetermined number of times or more regarding the behavior leading up to calling a taxi (step S148). In the example shown in FIG. 3, a taxi is called after leaving a conference room and going down three floors in an elevator. The server 20 determines whether such behavior has occurred a predetermined number of times or more based on the accumulated behavior history. Note that the "same behavior" here is not limited to location and time, and may also include circumstances. For example, the server 20 may extract from the behavior history an action of taking a taxi from a location near the user's home between five minutes before and five minutes after 8:00 a.m. on a weekday when it is raining, and count the number of times that action has occurred.
[0044] Next, if the same behavior occurs a predetermined number of times or more (step S148 / Yes), the server 20 requests the user to confirm whether or not to register a behavior pattern (step S151).
[0045] Next, the user terminal 10 confirms with the user whether or not to register the behavior pattern (step S154). Here, FIG. 4 shows an example of a registration confirmation screen. For example, as shown in screen 600 on the left side of FIG. 4, the user's behavior before and after the recorded taxi call is displayed, and the user is asked whether or not to register the automatic vehicle dispatch reservation with this content. If there is any behavior that the user wants to edit, the user presses the edit button on screen 600 and makes any edits on screen 610 shown on the right side of FIG. 4. Furthermore, if the user approves the registration, the user presses the yes button on screen 600. Such registration confirmation with the user may be performed, for example, when the user gets out of the taxi. Note that the timing of the registration confirmation with the user is not particularly limited.
[0046] Next, if the registration is approved (step S157 / Yes), the user terminal 10 notifies the server 20 of the approval (step S160). The server 20 registers the behavior pattern (step S163).
[0047] On the other hand, if the registration is not approved (step S157 / No), the user terminal 10 notifies the server 20 that approval was not granted (step S166). In this case, the server 20 does not register any behavioral patterns. The server 20 may store which behaviors were denied approval. The server 20 may also request confirmation of registration again if this occurs a further predetermined number of times. The server 20 may also adjust the "predetermined number of times" used as the confirmation criterion if approval is frequently denied.
[0048] (3-1-2. Using a taxi when leaving home) 5 is a sequence diagram illustrating an example of a process for registering a user's behavior pattern according to this embodiment. In FIG. 5, an example is described in which a user takes a taxi every time he or she leaves home (for example, to go to work), and such behavior is registered as a behavior pattern.
[0049] 5, first, the alarm clock (an example of the sensing device 30) sounds an alarm at a set time (step S203), and upon detecting that the alarm has been stopped (step S206), transmits the detection result (sensing result of the user's behavior) to the server 20 (step S209). The server 20 stores the time when the alarm was stopped (the user's wake-up time) (step S212).
[0050] Next, when the camera (an example of the sensing device 30) installed in the bathroom detects that the user is washing their face (step S215), it transmits the detection result to the server 20 (step S218). The server 20 stores the time when the user washed their face (step S221). Note that while "washing your face" is detected here as an example, this embodiment is not limited to "washing your face" and may also detect getting ready (progress of getting ready to go out), such as changing clothes, having breakfast, brushing teeth, and applying makeup, as appropriate.
[0051] Next, when the camera (an example of the sensing device 30) installed at the entrance detects that the user has gone out (step S224), it transmits the detection result to the server 20 (step S227). The server 20 stores the fact that the user has left the entrance (time of leaving) (step S230).
[0052] Next, when the user terminal 10 detects that the user has called a taxi, for example, using a taxi dispatch app (step S233), it transmits the detection result to the server 20 (step S236). The server 20 stores the fact that the user has called a taxi (boarding time, boarding location, destination, date and time of taxi dispatch reservation, etc.) (step S239). As described above, the means by which the user calls a taxi is not particularly limited.
[0053] Next, when the user terminal 10 detects that the taxi has arrived at the destination and the user has gotten off (step S242), it transmits the detection result to the server 20 (step S245). The server 20 stores the fact that the user has arrived at the destination (the destination, the date and time, etc.) (step S248).
[0054] Next, the server 20 determines whether the same behavior before calling a taxi has occurred a predetermined number of times or more (step S251). In the example shown in Fig. 5, the behavioral patterns extracted from the accumulated behavioral history include what time the user wakes up, what time the user washes their face, and what time the user leaves home to call a taxi.
[0055] Next, if the same behavior occurs a predetermined number of times or more (step S251 / Yes), the server 20 requests the user to confirm whether or not to register a behavior pattern (step S254).
[0056] Next, the user terminal 10 confirms with the user whether or not it is necessary to register a behavior pattern (step S257).
[0057] Next, if the registration is approved (step S260 / Yes), the user terminal 10 notifies the server 20 of the approval (step S263), and the server 20 registers the behavior pattern (step S266).
[0058] On the other hand, if the registration is not approved (step S260 / No), the user terminal 10 notifies the server 20 that the registration has not been approved (step S269).
[0059] A specific example of the registration process has been described above. The server 20 according to this embodiment can accumulate a behavioral history related to taxi riding from the user's usual behavior, and extract and register the user's behavioral pattern leading up to riding a taxi. Note that the registration process according to this embodiment is not limited to the examples shown in FIGS. 3 and 5.
[0060] In the above example, the user's approval is obtained when registering a behavior pattern, but this is not limiting and the server 20 may register without approval. Also, the server 20 may provisionally register a behavior pattern when the same behavior occurs a predetermined number of times or more, and the next time the same behavior occurs, the server 20 may ask the user whether to make a car reservation, and if approval to call is obtained, make a car reservation and register the behavior pattern. Also, if approval to call is obtained, the server 20 may ask "Do you want to call again?" and register the behavior pattern if approval is obtained.
[0061] In the above example, the behavioral patterns are registered based on the user's behavior history, but this embodiment is not limited to this, and the server 20 may register a behavioral pattern arbitrarily set by the user. Also, the server 20 may present default behavioral patterns, and the user may select or arrange them and register them.
[0062] <3-2. Vehicle reservation processing> FIG. 6 is a sequence diagram illustrating an example of a vehicle reservation process according to this embodiment.
[0063] As shown in FIG. 6, first, the vehicle dispatch reservation processing unit 224 of the server 20 acquires sensing data regarding the user's behavior (sensing results of the user's behavior) from each sensing device 30 and the user terminal 10 (step S273), and stores the sensing data (step S276).
[0064] Next, the vehicle reservation processing unit 224 determines whether the sensing result of the user's behavior matches the registered behavior pattern (step S279).
[0065] If they match (step S279 / Yes), the vehicle dispatch reservation processing unit 224 executes the vehicle dispatch reservation (step S282). Specifically, the vehicle dispatch reservation processing unit 224 transmits the boarding location, boarding time, and destination to the taxi dispatch server 40 according to the behavior pattern to make a vehicle dispatch reservation request. This allows the server 20 to dispatch a taxi to the user's usual boarding location.
[0066] An example of the vehicle reservation process according to this embodiment has been described above. The server 20 according to this embodiment automatically reserves a vehicle by comparing the user's usual behavior with pre-registered user behavior patterns leading to taxi rides, thereby eliminating the user's effort in reserving a vehicle and further improving the convenience of using a taxi. The user simply uses a taxi as they normally do, and the system registers their behavior patterns leading to a taxi ride, allowing them to use a taxi without the hassle of making a reservation.
[0067] Note that this embodiment is not limited to the example shown in Fig. 6. For example, the vehicle dispatch reservation processing unit 224 may confirm with the user whether or not it is OK to make a vehicle dispatch reservation before step S282. The user may optionally set whether or not to confirm in advance. The user may also be asked to confirm after the vehicle dispatch reservation has been made. In this case, if the user presses cancel, the server 20 notifies the taxi dispatch server 40 of the cancellation.
[0068] Furthermore, the server 20 may appropriately modify a behavioral pattern that has been registered once based on the user's subsequent behavior history. The server 20 may modify the behavioral pattern automatically or after confirming with the user.
[0069] <3-3. Example of vehicle reservation processing> Next, some specific examples of the vehicle reservation process according to this embodiment will be described with reference to the drawings.
[0070] (3-3-1. First Example) Fig. 7 is a sequence diagram illustrating the flow of a vehicle reservation process according to a first example of this embodiment. In the example shown in Fig. 7, a case will be described in which a user's behavior of usually taking a taxi when going out from home (such as when going to work) is registered as a behavior pattern, and a vehicle reservation is automatically made in accordance with the user's usual behavior. Furthermore, in the example shown in Fig. 7, if the user's behavior deviates from the registered behavior pattern, the server 20 may urge the user or suggest an alternative.
[0071] As shown in FIG. 7, the server 20 sets an alarm on the user's alarm clock at the usual time based on the registered behavior pattern (step S303).
[0072] Next, the alarm clock sounds an alarm at the set time (step S306), and when it detects that the alarm has been stopped (step S309), it transmits the detection result to the server 20 (step S312). The server 20 stores the time when the alarm was stopped (the user's wake-up time) (step S315).
[0073] Next, if the wake-up time is not the usual time (i.e., if there is a deviation from the behavioral pattern) (step S318 / No), the server 20 notifies the user to hurry up (step S321). Specifically, for example, an indoor speaker (an example of the sensing device 30) installed in the user's home may be used to notify the user that the wake-up time was later than usual and to urge the user to hurry up (step S324). The indoor speaker may be a smart speaker that has a communication unit, a control unit, a speaker, and a microphone and can recognize and respond to speech uttered by the user. The speech recognition process may be performed in the cloud.
[0074] Next, when the camera (an example of sensing device 30) installed in the bathroom detects that the user is washing their face (step S327), it transmits the detection result to the server 20 (step S330). The server 20 stores the time when the user washed their face (step S333). Here, "face washing" is detected as an example, but this embodiment is not limited to "face washing" and may appropriately detect getting ready (progress of getting ready to go out), such as changing clothes, having breakfast, brushing teeth, applying makeup, etc.
[0075] Next, if the progress (of getting dressed) is not as usual (i.e., if there is a deviation from the behavioral pattern) (step S336 / No), the server 20 notifies the user to hurry up (step S339). Specifically, for example, the server 20 issues a notification through an indoor speaker saying that the user is taking longer than usual to get dressed and urges the user to hurry up (step S342).
[0076] Next, the server 20 determines whether or not the taxi will arrive in time for the final deadline for calling a regular taxi (step S345). In this embodiment, as an example, a general manned taxi is referred to as a "regular taxi."
[0077] If the time is not available (step S345 / No), the server 20 presents an alternative to the user (step S348). The alternative is, for example, a proposal to use a robot taxi, which has a more flexible deadline for calls than a regular taxi. A robot taxi is assumed to travel, for example, on dedicated lanes or toll lanes, and can arrive at the boarding location or destination faster than a regular taxi (without delays due to road congestion, etc.). Alternatively, a robot taxi is expected to have all map information input, allowing it to travel more accurately than a human driver and arrive at the destination faster. Note that although a robot taxi is used as an example here, the alternative is not limited to this. For example, it could be a special manned taxi that can travel on dedicated lanes or toll lanes, or a taxi with a special experienced driver.
[0078] Next, the indoor speaker asks the user whether to switch to a robot taxi (step S351). If an additional surcharge is required, the user is notified of this. The user may verbally respond to the indoor speaker (smart speaker) whether they agree or not. If the user agrees, the indoor speaker notifies the server 20 of the request for a robot taxi (step S354).
[0079] Then, the server 20 makes a reservation for dispatching a regular taxi or a robot taxi (step S357). Specifically, the server 20 transmits information on the boarding location, boarding time, and destination to the taxi dispatch server 40 in accordance with the registered behavior pattern, and makes a request for dispatching a taxi.
[0080] The server 20 also stores the fact that a vehicle reservation has been made (as a riding history included in the user's behavior history) (step S360).
[0081] The first embodiment has been described above. However, an example in which an alternative plan is not presented is also possible. In this case, the server 20 notifies the user that the arrival time will be later than usual, and then makes a reservation for a regular taxi.
[0082] (3-3-2. Second Example) Fig. 8 is a sequence diagram illustrating the flow of a taxi reservation process according to a second example of this embodiment. In the example shown in Fig. 8, a case is described in which a behavior pattern is registered in which a person normally does not use a taxi when going out from home (such as when going to work), but uses a taxi when an unusual situation occurs, such as when the person oversleeps, when it rains, or when a train is delayed. For this reason, in this example, a normal behavior pattern of not using a taxi and a request to reserve a taxi when an unusual situation occurs are registered.
[0083] 7, the server 20 sets an alarm for the user's alarm clock at the registered time (step S403). The alarm setting for the alarm clock may be set arbitrarily by the user, or may be set based on the user's usual behavior pattern before going out, which the server 20 extracts from the user's usual behavior.
[0084] Next, the alarm clock sounds an alarm at the set time (step S406), and when it detects that the alarm has been stopped (step S409), it transmits the detection result to the server 20 (step S412). The server 20 stores the time when the alarm was stopped (the user's wake-up time) (step S415).
[0085] Next, the server 20 determines whether or not it was the usual wake-up time (step S418).
[0086] Next, if it is the usual wake-up time (step S418 / Yes), the server 20 acquires weather information from an external server (step S421) and checks whether it is raining or snowing or a typhoon (step S424). In any case, the server 20 determines whether an unusual situation (oversleeping or bad weather) has occurred.
[0087] Furthermore, when the camera installed in the bathroom detects that the user is washing their face (step S427) and transmits the detection result to the server 20 (step S430), the server 20 stores the time when the user washed their face (step S433) and further checks whether the user is proceeding (getting dressed) as usual (step S436). Here, the focus is on washing the face as an example of getting dressed, but this embodiment is not limited to this, and changing clothes, having breakfast, brushing teeth, putting on makeup, etc. may also be detected as appropriate.
[0088] In any case, the server 20 determines whether or not an unusual situation (such as oversleeping or bad weather) has occurred. If the user has not overslept, the weather is not bad, and getting ready is proceeding as usual (step S436 / Yes), the server 20 ends the process.
[0089] On the other hand, if the trip is not proceeding as usual (step S436 / No), if the user oversleeps (step S418 / No), or if the weather is bad, such as rain (step S424 / Yes), the server 20 will ask the user whether or not to reserve a taxi (step S439).
[0090] Next, the indoor speaker (an example of the sensing device 30) asks the user whether to call a taxi (step S442), and transmits the user's answer to the server 20 (step S445).
[0091] If the server 20 receives approval to call the taxi, it makes a taxi dispatch reservation (step S448). Specifically, the server 20 transmits information on the boarding location, boarding time, and destination to the taxi dispatch server 40 in accordance with the registered behavior pattern, and makes a taxi dispatch reservation request.
[0092] Furthermore, the server 20 stores the fact that a vehicle reservation has been made (as a riding history included in the user's behavior history) (step S451).
[0093] The above describes the second embodiment. Note that, in step S439, the user is asked whether or not to make a taxi reservation, but this embodiment is not limited to this, and a taxi reservation may be made without asking the user.
[0094] <<4. Using the reservation waiting list>> Next, other embodiments of the present disclosure will be described.
[0095] Conventionally, when a user manually makes a car reservation, the user can only make reservations for a certain period of time in advance and for a certain number of times, and even if the user wants to make multiple car reservations in advance, such as when using a taxi regularly, reservations beyond a certain period of time or for more than a certain number of times must be made at an appropriate time at a later date, which is time-consuming. Also, even if the user wants to make multiple car reservations in advance, including for plans beyond a certain period of time, it is difficult to make reservations beyond a certain period of time or for more than a certain number of times, and the reservations must be made just before the plans, which is time-consuming.
[0096] Therefore, in another embodiment of the present disclosure, by using a vehicle reservation waiting list in the vehicle reservation process by the vehicle reservation processing unit 224, it is possible to reduce the effort required of the user in dispatching a taxi.
[0097] The vehicle reservation waiting list is a list of vehicle reservations that are waiting to be made, generated for each user, and includes information to that effect if a reservation has already been made. The vehicle reservation processing unit 224 generates a vehicle reservation waiting list based on vehicle reservations from users, and makes vehicle reservations up to the number of reservations that can be made from the vehicle reservation waiting list. The number of reservations that can be made may be set, for example, by restrictions on the vehicle dispatch system side (specifically, the taxi dispatch server 40). The restrictions on the number of reservations that can be made may further include, for example, a time limit (up to one week in the future, etc.).
[0098] In another embodiment of the present disclosure, by using a vehicle reservation waiting list, a user can make more vehicle reservation requests to the server 20 than the number of reservations that can be made. This allows the user to make multiple reservations in one reservation, even for future reservations, without worrying about the number or time. Also, in the case of a regular reservation (for example, a vehicle is to be delivered to a specific location every Tuesday morning at 8:00 AM), the server 20 can reduce the user's effort by automatically adding the next reservation to the vehicle reservation waiting list when the vehicle is dispatched after the vehicle reservation is made.
[0099] <4-1. About the waiting list for vehicle reservations> An example of a vehicle reservation waiting list according to another embodiment of the present disclosure is shown in the following Table 1. The vehicle reservation processing unit 224 of the server 20 enters the vehicle reservation information (date, time, location) received from the user terminal 10 into the vehicle reservation waiting list.
[0100] [Table 1]
[0101] As shown in Table 1 above, when the vehicle reservation processing unit 224 of the server 20 executes a request for vehicle reservation to the taxi dispatch server 40, information indicating that the request has been executed is added to the vehicle reservation waiting list. Note that the list of regular reservations described above and the list of optional reservations made by the user as shown in Table 1 above may be generated as separate lists.
[0102] <4-2. Operational Processing> Next, operation processing according to another embodiment of the present disclosure will be specifically described with reference to the drawings.
[0103] (4-2-1. First operation processing example) FIG. 9 is a flowchart showing the flow of a first operation process according to another embodiment of the present disclosure.
[0104] As shown in FIG. 9, first, the server 20 receives vehicle reservation information from the user terminal 10 (step S503).
[0105] Next, the vehicle reservation processing unit 224 of the server 20 determines whether the total number of reservations in the vehicle reservation waiting list and new reservations (new vehicle reservation information) exceeds the default number of available reservations (step S506). The default number of available reservations may be set for each user, or may be a value requested by the taxi dispatch server 40. If the default number of available reservations is, for example, three, the vehicle reservation processing unit 224 determines whether the total number of available reservations, including new reservations, exceeds three.
[0106] Next, if the limit is not exceeded (step S506 / No), the vehicle reservation processing unit 224 adds a new reservation to the vehicle reservation waiting list and executes the new reservation (step S509). Specifically, the vehicle reservation processing unit 224 transmits the contents of the new reservation to the taxi dispatch server 40 and requests a vehicle reservation. In addition, the vehicle reservation processing unit 224 adds information indicating that the new reservation has been executed to the new reservation.
[0107] On the other hand, if it exceeds the deadline (step S506 / Yes), the vehicle reservation processing unit 224 determines whether the reservation date and time of the new reservation is earlier than the reservation date and time of the already executed reservation included in the vehicle reservation waiting list (step S512).
[0108] Next, if the date and time is earlier (step S512 / Yes), the taxi reservation processing unit 224 adds a new reservation to the taxi reservation waiting list, cancels one of the existing reservations (notifies the taxi dispatch server 40 of the cancellation), and then executes the new reservation (step S515). This allows reservations with earlier dates and times to be executed with priority. The canceled reservation remains on the taxi reservation waiting list, so it can be executed again when a reservation slot becomes available. In this way, the server 20 automatically adjusts the execution of each reservation, thereby reducing the user's effort.
[0109] On the other hand, if the date and time is not early (step S512 / No), the vehicle allocation reservation processing unit 224 adds a new reservation to the vehicle allocation reservation waiting list (step S518).
[0110] Next, when the reservation date and time of the already executed reservation has passed, the vehicle reservation processing unit 224 deletes the reservation from the vehicle reservation waiting list (step S521). As a result, it is expected that the number of available reservations will become available.
[0111] Next, if a reservation slot becomes available (step S524 / Yes), the vehicle dispatch reservation processing unit 224 executes the reservation with the nearest date and time that is not yet executed among the reservations on the vehicle dispatch reservation waiting list (step S527).
[0112] (4-2-2. Second operation processing example) Next, a second example of the operation process will be described. For example, the number of available taxi slots may be set for each date, time, and location on the taxi dispatch server 40 side. The number of available taxi slots may be calculated based on, for example, past performance, predicted weather, scheduled events, etc. There are no particular limitations on the method for setting the number of available taxi slots. Here, with reference to FIG. 10, the operation process for taxi reservation that also takes the number of available taxi slots into consideration will be described.
[0113] FIG. 10 is a flowchart showing the flow of the second operation process according to another embodiment of the present disclosure.
[0114] As shown in FIG. 10, first, the server 20 receives vehicle reservation information from the user terminal 10 (step S603).
[0115] Next, the vehicle reservation processing unit 224 of the server 20 determines whether the total number of reservations on the vehicle reservation waiting list and new reservations (new vehicle reservation information) exceeds the predetermined number of available reservations (step S606).
[0116] Next, if the number of vehicles does not exceed the limit (step S606 / No), the vehicle reservation processing unit 224 determines whether there is a vacant vehicle slot available for the reservation conditions (step S609). Specifically, the vehicle reservation processing unit 224 inquires about the reservation conditions (date, time, and location) from the taxi dispatch server 40 and checks whether there is a vacant vehicle slot available for the reservation conditions.
[0117] Next, if there is a vacancy in the available vehicle slots (step S609 / Yes), the vehicle reservation processing unit 224 adds a new reservation to the vehicle reservation waiting list and executes the new reservation (step S612). In addition, the vehicle reservation processing unit 224 adds information indicating that the new reservation has been executed to the new reservation.
[0118] Next, in step S606, if the number of available reservations exceeds the preset number (step S606 / Yes), the vehicle reservation processing unit 224 determines whether the reservation date and time of the new reservation is earlier than the reservation date and time of an already executed reservation included in the vehicle reservation waiting list (step S615).
[0119] Next, if the date and time is earlier (step S615 / Yes), the vehicle allocation reservation processing unit 224 determines whether or not there is a vacant vehicle allocation slot under the reservation conditions (step S618).
[0120] Next, if there is a vacant vehicle slot available (step S618 / Yes), the vehicle reservation processing unit 224 adds a new reservation to the vehicle reservation waiting list, cancels one already-executed reservation, and then executes the new reservation (step S621).
[0121] Next, in step S615, if the date and time is not early (step S615 / No), the vehicle allocation reservation processing unit 224 adds a new reservation to the vehicle allocation reservation waiting list (step S624).
[0122] Next, if the reservation date and time of the already executed reservation has passed, the vehicle reservation processing unit 224 deletes the reservation from the vehicle reservation waiting list (step S627).
[0123] Next, if a reservation slot becomes available (step S630 / Yes), the vehicle allocation reservation processing unit 224 selects the reservation with the nearest date and time that is an unexecuted reservation from the reservations on the vehicle allocation reservation waiting list (step S633).
[0124] Next, the vehicle allocation reservation processing unit 224 determines whether or not there is a vacant vehicle allocation slot under the reservation conditions of the selected reservation (step S636).
[0125] Next, if there is a vacant vehicle slot available for allocation (step S636 / Yes), the vehicle allocation reservation processing unit 224 executes the reservation (step S639).
[0126] If there are no available vehicle slots (step S609 / No, S618 / No, or S636 / No), the vehicle reservation processing unit 224 notifies the user that the reservation cannot be made under the specified reservation conditions due to limitations on the available vehicle slots, and then implements alternative measures, etc. (step S642).
[0127] (Alternative) One alternative is to "wait for cancellations." The vehicle reservation processing unit 224 waits until a vehicle becomes available in the available vehicle slots, and when a vehicle becomes available, it makes a reservation.
[0128] Another alternative is "modification." The vehicle reservation processing unit 224 modifies the reservation conditions to another reservation condition that can be made (preferably a date, time, and location that are close to the user's desired reservation conditions) and proposes this to the user. Table 2 below shows an example of a reservation waiting list when a reservation is made based on the modified proposal. Table 2 below shows a case where, for example, a reservation cannot be made for date and time X3 and location Y, but the reservation is modified to a date and time (date and time X3', location Y') that matches each condition, and the modified reservation is made.
[0129] [Table 2]
[0130] Another alternative is "skip." When a reservation cannot be made due to limitations on available vehicle slots, the vehicle reservation processing unit 224 may skip that reservation and make the next reservation from the vehicle reservation list (at this time, the available vehicle slots may be checked again). An example of a reservation waiting list when the next reservation is made by skipping is shown in Table 3 below. Table 3 below shows a case where, for example, when a reservation cannot be made for date and time X3 and location Y, the next reservation for "date and time X4 and location Y" is made.
[0131] [Table 3]
[0132] The above describes three alternative means as an example. The vehicle reservation processing unit 224 may propose the alternative means in the order of "Modify," "Skip," and "Wait for Cancellation," or may propose all the alternative means at the same time.
[0133] 10 is an example, and the present disclosure is not limited thereto. In the example shown in Fig. 10, after referencing the "reservation available slots," the vehicle allocation reservation processing unit 224 refers to the "distribution available slots under the reservation conditions" to determine whether or not a reservation can be made, but this is not limiting, and the vehicle allocation reservation processing unit 224 may refer to the "distribution available slots under the reservation conditions" first, and then refer to the "reservation available slots."
[0134] <4-3. Modifications> The server 20 may limit the users who can make multiple reservations (for example, by distinguishing between priority members and general members and giving them different numbers of reservations), and may reserve a certain percentage of the total reservation slots for priority customers.
[0135] The server 20 may also allow a user to purchase the right to make multiple reservations in advance in one lump sum, and give such customers priority. The server 20 may also give preferential treatment to customers who set up regular reservations. This is because regular reservations have a low rate of cancellation due to user convenience, which increases the accuracy of vehicle dispatch predictions and contributes to efficient vehicle dispatch operations in the taxi dispatch server 40.
[0136] Furthermore, even if there is availability in the user's available reservation slots, if the reservation date and time is far away (for example, more than one month in the future), the vehicle reservation processing unit 224 may not execute the reservation for that distant date and time. Because the vehicle is on the vehicle reservation waiting list, the vehicle reservation processing unit 224 will automatically execute the reservation when the reservation date and time approaches.
[0137] Furthermore, if the reservation cannot be made even when the reservation date and time is approaching (for example, two days before), the server 20 notifies the user and presents alternatives, such as alternatives to transportation other than a taxi (such as a bus, hire car, or ride-sharing service) or changing the reservation date and location to a nearby available date and location.
[0138] In addition, in order to prevent no-shows (people who have made reservations not showing up without contacting the reservation center to cancel) and last-minute cancellations, the server 20 may notify the user a certain time before the reservation date and time (for example, two days before the reservation date) whether any changes or cancellations are necessary.
[0139] Furthermore, if the taxi dispatch server 40 reduces the number of available taxi slots for each time and location due to a sudden change in weather or a schedule change for an event that generates a large number of people, making it impossible to make a reservation (if the reservation is canceled), the sensing device 30 may present the user with an alternative solution, such as revising the reservation, along with an incentive (such as a discount coupon). For example, in the event of sudden rain, train cancellations, or a delayed event ending just before the last train, it may be possible to prepare more taxis around the station as an emergency measure. In this case, measures are taken to reduce the number of available taxi slots in surrounding locations in order to prepare more taxis. The taxi dispatch server 40 may cancel reservations, for example, starting with the latest reservation requested by the sensing device 30.
[0140] <<5. Supplementary Information>> Although the preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, the present technology is not limited to such examples. It is clear that a person skilled in the art of the present disclosure can conceive of various modified or altered examples within the scope of the technical ideas described in the claims, and it is understood that these also naturally fall within the technical scope of the present disclosure.
[0141] For example, a computer program can be created to cause hardware such as a CPU, ROM, and RAM built into the above-mentioned user terminal 10, server 20, sensing device 30, or taxi dispatch server 40 to perform the functions of the user terminal 10, server 20, sensing device 30, or taxi dispatch server 40. A computer-readable storage medium storing the computer program is also provided.
[0142] Furthermore, the effects described herein are merely descriptive or exemplary and are not limiting. In other words, the technology according to the present disclosure may achieve other effects that will be apparent to those skilled in the art from the description of this specification, in addition to or in place of the above-described effects.
[0143] The present technology can also be configured as follows. (1) An information processing device comprising a control unit that determines whether or not a taxi needs to be dispatched based on the sensing results of user behavior and the registered user behavior patterns. (2) The information processing device according to (1), wherein the behavioral pattern includes behavior related to the user taking a taxi. (3) The information processing device according to (2), wherein the behavior related to riding a taxi includes at least a sensing result of the behavior of the user up until riding a taxi. (4) The information processing device according to (2) or (3), wherein, when the same behavior related to taking a taxi occurs a predetermined number of times or more, the control unit registers the behavior as the behavior pattern. (5) The information processing device according to (4), wherein the control unit registers the behavior pattern when approval is obtained from the user. (6) The information processing device according to (2) or (3), wherein the control unit registers the behavior pattern based on a setting by the user. (7) The information processing device according to any one of (2) to (6), wherein the control unit modifies the registered behavior pattern based on a new sensing result. (8) The information processing device according to any one of (1) to (7), wherein the sensing results are acquired from one or more sensing devices. (9) The information processing device according to (8), wherein the sensing device includes a user terminal used by the user. (10) The information processing device described in any one of (1) to (9), wherein the control unit determines that a taxi needs to be dispatched when the sensing result of the user behavior matches the registered behavior pattern of the user. (11) The information processing device according to (10), wherein the control unit further executes dispatching of the taxi when approval is obtained from the user. (12) The information processing device according to (10), wherein the control unit executes dispatch of the taxi when it is determined that dispatch of a taxi is necessary. (13) The information processing device according to any one of (2) to (12), wherein the control unit issues a notification urging the user to act quickly if the user's behavior is behind the behavior pattern based on the sensing results of the user's behavior. (14) The processor: An information processing method including determining whether or not a taxi needs to be dispatched based on the results of sensing user behavior and registered user behavior patterns. (15) Computer, A program that functions as a control unit that determines whether or not a taxi needs to be dispatched based on the results of sensing user behavior and the registered user behavior patterns. (16) one or more sensing devices for sensing user behavior; an information processing device having a control unit that determines whether or not a taxi needs to be dispatched based on the sensing results of the user behavior acquired from the one or more sensing devices and the registered user behavior pattern; An information processing system comprising: [Explanation of symbols]
[0144] 10 User terminal 20 servers 210 Communications Department 220 Control Unit 221 Behavioral History Memory Processing Unit 222 Action pattern registration processing unit 223 Vehicle Dispatch Necessity Decision Department 224 Vehicle reservation processing unit 230 Storage section 30 Sensing Devices 40 Taxi dispatch server
Claims
1. An information processing device comprising a control unit that determines whether or not a taxi needs to be dispatched based on the sensing results of user behavior and the registered user behavior patterns.
2. The information processing device according to claim 1 , wherein the behavioral pattern includes behavior of the user related to taking a taxi.
3. The information processing device according to claim 2 , wherein the behavior related to taking a taxi includes at least a sensing result of the behavior of the user up until getting into the taxi.
4. The information processing device according to claim 2 , wherein when the same behavior related to taking a taxi occurs a predetermined number of times or more, the control unit registers the behavior as the behavior pattern.
5. The information processing device according to claim 4 , wherein the control unit registers the behavior pattern when approval is obtained from the user.
6. The information processing device according to claim 2 , wherein the control unit registers the behavior pattern based on a setting by the user.
7. The information processing device according to claim 2 , wherein the control unit modifies the registered behavioral pattern based on a new sensing result.
8. The information processing apparatus according to claim 1 , wherein the sensing results are obtained from one or more sensing devices.
9. The information processing apparatus according to claim 8 , wherein the sensing device includes a user terminal used by the user.
10. The information processing device according to claim 1 , wherein the control unit determines that a taxi needs to be dispatched when a result of sensing the user behavior matches a registered behavior pattern of the user.
11. The information processing device according to claim 10 , wherein the control unit executes dispatching of the taxi when approval is further obtained from the user.
12. The information processing device according to claim 10 , wherein the control unit executes dispatching of the taxi when it is determined that dispatching of a taxi is necessary.
13. The information processing device according to claim 2 , wherein the control unit issues a notification to urge the user to hurry up when the user's behavior is delayed compared to the behavior pattern based on a sensing result of the user's behavior.
14. The processor: An information processing method including determining whether or not a taxi needs to be dispatched based on the results of sensing user behavior and registered user behavior patterns.
15. Computer, A program that functions as a control unit that determines whether or not a taxi needs to be dispatched based on the results of sensing user behavior and the registered user behavior patterns.
16. one or more sensing devices for sensing user behavior; an information processing device having a control unit that determines whether or not a taxi needs to be dispatched based on the sensing results of the user behavior acquired from the one or more sensing devices and the registered user behavior pattern; An information processing system comprising:
Citation Information
Patent Citations
Method and system for vehicle-dispatching reservation and information processor used for them
JP2004185494A
Vehicle allocation information provision system and vehicle allocation reservation server
JP2007207077A
Information processing device, control method of information processing device, route provision server, control method for route provision server, behaviour proposal system, control program, and recording medium
JP2013250811A
Vehicle dispatch system
JP2015138324A
Vehicle allocation auxiliary system and vehicle allocation auxiliary program
JP2017068750A