Management apparatus, management system, management method, and program

Abstract

To enhance the protection of privacy of a user.SOLUTION: A management apparatus is configured to communicate with a vehicle terminal over a network, the vehicle terminal being used when a driver of a vehicle drives the vehicle on duty as a commercial vehicle which is transportation means of a user. The processor includes one or more processors, the processor being configured to: display, on a display device of the vehicle terminal, specific information regarding the user to be transported during a specific period, in accordance with an input made by the driver to the vehicle terminal, in the specific period from when the driver responds to a vehicle allocation request from the user to fix the vehicle allocation to when the driver completes transportation of the user; and display, on the display device of the vehicle terminal, regulated information which is information obtained by regulating at least part of the specific information regarding the user transported in the specific period, in accordance with the input made by the driver to the vehicle terminal, after the specific period.SELECTED DRAWING: Figure 13

Description

[Technical Field]

[0001] The present invention relates to a management device, a management system, a management method, and a program. [Background technology]

[0002] There are known technologies for dispatching a taxi in response to a user's request for dispatching a taxi. For example, Patent Document 1 discloses a technology for estimating the arrival times of the user and the taxi at the user's desired boarding location, matching the estimated results, and dispatching a taxi so as to minimize the difference between the estimated results. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2023-027694 Summary of the Invention [Problem to be solved by the invention]

[0004] Recently, the shortage of taxi drivers has become a serious problem in some regions. As a result, there are areas where the supply of taxis is insufficient to meet the demand for taxi dispatch. As a result, the introduction of ride-sharing (Japanese-style ride-sharing), in which ordinary drivers use their own cars to transport users for a fee, is progressing.

[0005] In ride sharing, in order for the driver to transport the user smoothly, information about the user being transported may be displayed on the driver's vehicle terminal. However, if information about the user can be displayed on the driver's vehicle terminal after the driver has completed transporting the user in the same way as during the transport, there is a risk that the user's privacy may not be adequately protected, since the information about the user is also the user's personal information.

[0006] In view of the above problems, an object of the present invention is to provide a management device, a management system, a management method, and a program that can improve the protection of user privacy. [Means for solving the problem]

[0007] In order to solve the above problem, the management device of the present invention is a management device that can communicate via a network with a vehicle terminal used by a vehicle driver when driving the vehicle as a commercial vehicle, which is a means of transportation for the user, and is equipped with one or more processors, and during a specific period from the time when the driver responds to the user's request for vehicle dispatch and the dispatch is confirmed to the time when the transportation of the user is completed, the processor displays specific information about the user who is transported during the specific period on the display device of the vehicle terminal in response to input by the driver into the vehicle terminal, and after the end of the specific period, displays post-restriction information, which is information after restricting at least some of the specific information about the user who was transported during the specific period, on the display device of the vehicle terminal in response to input by the driver into the vehicle terminal.

[0008] The post-restriction information may include information on the boarding area and disembarking area of ​​the user transported during the specified period, and the information on the boarding area may include information on the address of the boarding location of the user transported during the specified period from the larger area to a specified first part, but not include information on parts of the area narrower than the first part, and the information on the disembarking area may include information on the address of the disembarking location of the user transported during the specified period from the larger area to a specified second part, but not include information on parts of the area narrower than the second part.

[0009] The post-restriction information may be information after at least one of the specific information about the user has been restricted, including information about the user's name, information about the name of the boarding location, information about the name of the disembarking location, landmark information that assists in identifying at least one of the boarding location and the user, and message information sent and received between the user and the driver.

[0010] In order to solve the above problems, the management system of the present invention comprises a vehicle terminal used by a vehicle driver when driving the vehicle as a commercial vehicle that is a means of transportation for a user, and a management device capable of communicating with the vehicle terminal via a network, the vehicle terminal having one or more first processors and a display device, and the management device having one or more second processors, and the first processor is configured to, in response to an input by the driver to the vehicle terminal, make a display request for specific information regarding the user who will be transported during the specific period from the time when the driver responds to the user's request for vehicle dispatch and vehicle dispatch is confirmed to the time when transportation of the user is completed. The second processor, in response to receiving a request to display the specific information during the specific period, transmits the specific information to the vehicle terminal and displays it on the display device, and after the specific period ends, the first processor, in response to input from the driver to the vehicle terminal, transmits a request to display the history of business conducted during the specific period to the management device, and the second processor, in response to receiving a request to display the history of business conducted during the specific period, generates post-restriction information, which is information after restricting at least some of the specific information regarding the users who were transported during the specific period, and transmits the generated post-restriction information to the vehicle terminal and displays it on the display device.

[0011] In order to solve the above problem, the management method of the present invention has a computer that, during a specific period from the time when a vehicle driver responds to a user's request for vehicle dispatch and confirms the dispatch to the time when the transportation of the user is completed, displays specific information about the user who will be transported during the specific period on a display device of the vehicle terminal in accordance with input by the driver into the vehicle terminal, and after the end of the specific period, displays post-restriction information, which is information after restricting at least some of the specific information about the user who was transported during the specific period, on a display device of the vehicle terminal in accordance with input by the driver into the vehicle terminal.

[0012] In order to solve the above problem, the program of the present invention causes a computer to perform the following operations: during a specific period from the time when a vehicle driver responds to a user's request for vehicle dispatch and confirms dispatch to the time when the transportation of the user is completed, display specific information about the user who is being transported during the specific period on the display device of the vehicle terminal in accordance with input by the driver into the vehicle terminal; and after the end of the specific period, display post-restriction information, which is information after restricting at least some of the specific information about the user who was transported during the specific period, on the display device of the vehicle terminal in accordance with input by the driver into the vehicle terminal. [Effects of the Invention]

[0013] According to the present invention, it is possible to improve the protection of user privacy. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram for explaining an outline of a vehicle dispatch management system. [Figure 2] FIG. 2 is a block diagram illustrating the configuration of a user terminal. [Figure 3] FIG. 3 is a block diagram illustrating the configuration of the taxi terminal. [Figure 4] FIG. 4 is a block diagram for explaining the configuration of the NRS terminal and the associated devices. [Figure 5] FIG. 5 is a block diagram illustrating the configuration of the carrier terminal. [Figure 6] FIG. 6 is a block diagram illustrating the configuration of the vehicle dispatch management server. [Figure 7] FIG. 7 is a diagram illustrating the flow of transportation of a user. [Figure 8] FIG. 8 is a diagram showing an example of the pick-up screen. [Figure 9] FIG. 9 is a diagram showing an example of a details screen displayed on the display device when the details button on the pick-up screen is pressed. [Figure 10]FIG. 10 is a diagram showing another example of the details screen displayed on the display device when the details button on the pick-up screen is pressed. [Figure 11] FIG. 11 is a diagram showing an example of the actual vehicle screen. [Figure 12] FIG. 12 is a diagram showing an example of the menu screen. [Figure 13] FIG. 13 is a diagram illustrating the flow of processing when the business history confirmation button is pressed. [Figure 14] FIG. 14 is a diagram showing an example of the business history screen. DETAILED DESCRIPTION OF THE INVENTION

[0015] Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Dimensions, materials, and other specific values ​​shown in the embodiments are merely examples for facilitating understanding of the invention and, unless otherwise specified, do not limit the present invention. In this specification and drawings, elements having substantially the same functions and configurations are designated by the same reference numerals to avoid redundant explanation, and elements not directly related to the present invention are not shown.

[0016] (Management System 1) FIG. 1 is a block diagram for explaining an overview of a management system 1. The management system 1 includes a plurality of user terminals 20, a plurality of taxi terminals 30, a plurality of taxi vehicles 32, a plurality of NRS terminals 40, a plurality of NRS vehicles 42, one or more business operator terminals 50, and one or more management servers 60. In the management system 1, NRS vehicles 42 are included in addition to taxi vehicles 32 as commercial vehicles that serve as transportation means for users 2. Here, NRS is an abbreviation for Nippon-style Ride Share or Nihon-gata Ride Share, and refers to a service in which ordinary drivers transport users 2 for a fee using their own cars or the like.

[0017] Hereinafter, for ease of explanation, when referring to the taxi vehicle 32 and the NRS vehicle 42 collectively without distinction, they may be simply referred to as the vehicle. When referring to the taxi driver 3 of the taxi vehicle 32 and the NRS driver 4 of the NRS vehicle 42 collectively without distinction, they may be simply referred to as the driver. When referring to the taxi terminal 30 and the NRS terminal 40 collectively without distinction, they may be referred to as the vehicle terminal.

[0018] Furthermore, the work of a driver driving a vehicle as a commercial vehicle, which is a means of transportation for User 2, may be referred to as "duty." Furthermore, the work of performing duty, in other words, the driving time, may be referred to as "shift." Furthermore, the transportation unit from the time when the driver loads passengers into the vehicle to the time when the passengers are transported and payment is completed (in other words, the time when the passengers are dropped off) may be referred to as "sales." In other words, a driver will perform one or more sales during one shift of work.

[0019] The user terminal 20 is an electronic device owned by the user 2. The user 2 is a passenger in a commercial vehicle (such as a taxi vehicle 32 or an NRS vehicle 42). Examples of the user terminal 20 include a smartphone, a personal computer, and a tablet PC. In the management system 1, there are multiple combinations of users 2 and user terminals 20. Note that the user 2 in this embodiment is not limited to one person, and may refer to multiple people who can ride in one taxi vehicle 32.

[0020] FIG. 2 is a block diagram illustrating the configuration of the user terminal 20. The user terminal 20 includes a communication device 120, a processing device 122, a display device 124, an input device 126, and a storage device 128. The communication device 120 is communicatively connected to an external device, such as a management server 60, via a base station 5 and a network 6. The processing device 122 includes a semiconductor integrated circuit including a processor such as a central processing unit (CPU), a read-only memory (ROM) storing programs, and a random access memory (RAM) used as a work area. A user application for the management system 1 is installed on the user terminal 20. The processing device 122 runs the program to control the user application and function as a vehicle dispatch request unit 180 that assists the user 2 in inputting a vehicle dispatch request. The display device 124 includes a liquid crystal display, an organic electroluminescence (EL) display, or the like, and displays various information, such as an image of the user application used to make a vehicle dispatch request. The input device 126 includes a touch panel, switches, buttons, keys, a microphone for voice input, etc. superimposed on the display device 124, and accepts input from the user 2, such as information for requesting a vehicle dispatch. The storage device 128 is configured with storage means such as an HDD (Hard Disk Drive), SD memory, SSD (Solid State Drive), etc.

[0021] The taxi terminal 30 is an electronic device (computer) loaned to a taxi driver (first driver) 3 of a taxi vehicle (first vehicle) 32, or an electronic device (computer) owned by the taxi driver 3. The taxi terminal 30 is associated with the taxi vehicle 32. Examples of the taxi terminal 30 include a smartphone, a personal computer, and a tablet PC. The taxi terminal 30 is an example of a vehicle terminal (first vehicle terminal).

[0022] FIG. 3 is a block diagram illustrating the configuration of the taxi terminal 30. The taxi terminal 30 includes a communication device 130, a processing device 132, a display device 134, an input device 136, and a storage device 138. The communication device 130 is communicatively connected to external devices, such as the operator terminal 50 and the management server 60, via a base station 5 and a network 6. The processing device 132 includes a semiconductor integrated circuit including a processor (CPU), a ROM storing programs, and a RAM used as a work area. A vehicle application for the management system 1 is installed in the taxi terminal 30. The processing device 132 runs a program to control the vehicle application and function as a dispatch response unit 182 that supports the taxi driver 3 in inputting responses to dispatch requests. The display device 134 includes a liquid crystal display and an organic electroluminescence (EL) display, and displays various information, such as a notification that the taxi 32 has been the subject of a dispatch request (dispatch target notification) and information related to the dispatch request (boarding location, user information about the user 2, and disembarking location). Hereinafter, the target of a dispatch request may be referred to as the "dispatch target," and the vehicle that has been dispatched may be referred to as the "dispatch target vehicle." The input device 136 includes a touch panel, switches, buttons, keys, a microphone for voice input, etc. superimposed on the display device 134, and receives input from the taxi driver 3, such as acceptance of the dispatch request. The storage device 138 is composed of storage means such as an HDD, SD memory, or SSD. The taxi terminal 30 can acquire its own position on a map through location identification means such as a GPS (Global Positioning System).

[0023] The taxi driver 3 is a driver who holds a Class 2 driver's license for a standard vehicle and belongs to a taxi business (general passenger automobile transportation business). The taxi vehicle 32 is, for example, a vehicle that belongs to a taxi business and can transport the user 2 as a taxi business for a fee. In the management system 1, there are multiple combinations of taxi drivers 3, taxi vehicles 32, and taxi terminals 30. Note that in this embodiment, an example of a four-wheeled taxi (hire car) is given as the taxi vehicle 32 to be dispatched, but the taxi vehicle 32 is not limited to this example, and may include, for example, a motorcycle (motorcycle taxi) or the like as long as it is a vehicle capable of transporting people.

[0024] The NRS terminal 40 is an electronic device (computer) owned by the NRS driver (second driver) 4, and can be placed in the NRS vehicle (second vehicle) 42. Examples of the NRS terminal 40 include a smartphone, a personal computer, and a tablet PC. The NRS driver 4, for example, brings his / her own NRS terminal 40 into the NRS vehicle 42, which is his / her own private car, and drives the NRS vehicle 42. The NRS terminal 40 is not limited to being brought into the vehicle when driving, but may also be pre-installed in the NRS vehicle 42. The NRS terminal 40 is used when the NRS driver 4 is on duty. This makes it possible to use the NRS vehicle 42 as a commercial vehicle in place of the taxi vehicle 32. The NRS terminal 40 is an example of a vehicle terminal (second vehicle terminal).

[0025] 4 is a block diagram illustrating the configuration of the NRS terminal 40. The NRS terminal 40 includes a communication device 140, a processing device 142, a display device 144, an input device 146, and a storage device 148. The communication device 140 is connected to the outside, for example, a carrier terminal 50 or a management server 60, via the base station 5 and the network 6 so as to be able to communicate with the outside. The processing device 142 has a semiconductor integrated circuit including a processor (CPU), a ROM in which programs and the like are stored, a RAM used as a work area, and the like.

[0026] A driver application 200 (driver app in FIG. 4 ), which is a vehicle application for the management system 1, is installed on the NRS terminal 40. The driver application 200 is software that supports the driving of the NRS driver 4. The processing device 142 controls the driver application 200 by running the program, and functions as a vehicle dispatch response unit 184 and a display processing unit 202. The vehicle dispatch response unit 184 supports the NRS driver 4 in inputting responses to vehicle dispatch requests, etc.

[0027] The display device 144 includes a liquid crystal display and an organic EL display, and displays various information such as the fact that the NRS vehicle 42 has become a target for dispatch (dispatch target notification), information about the dispatch request (boarding location, disembarking location, information about user 2), and information about the roll call (roll call items, etc.). The input device 146 includes a touch panel, switches, buttons, keys, a microphone for voice input, a camera, etc. superimposed on the display device 144, and accepts input from the NRS driver 4, such as acceptance of the dispatch request. The storage device 148 is composed of storage means such as an HDD, SD memory, or SSD. The NRS terminal 40 can obtain its own position on a map through location identification means such as GPS.

[0028] The display processing unit 202 displays various information on the display device 144 in response to input from the NRS driver 4 to the NRS terminal 40 via the input device 146. In this case, the display processing unit 202 may specify the content to be displayed on the display device 144 under the control of the management server 60 or the business operator terminal 50, depending on the timing and content of the input from the NRS driver 4.

[0029] Hereinafter, for the sake of convenience, display device 134 and display device 144 may be collectively referred to as simply "display device" without distinction, and input device 136 and input device 146 may be collectively referred to as simply "input device" without distinction.

[0030] The NRS driver 4 is a driver who holds a Class 1 driver's license for a standard vehicle and is involved in a ride-sharing business (a private vehicle passenger transportation business for a fee). However, in this embodiment, an example will be described in which a taxi business also manages a ride-sharing business based on Article 78, Paragraph 3 of the Road Transportation Act. Therefore, the NRS driver 4 can be said to be a driver who is involved in a taxi business. The NRS driver 4 differs from the taxi driver 3 in that he or she does not hold a Class 2 driver's license for a standard vehicle or may have poor driver qualifications, driving skills, and knowledge. The NRS vehicle 42 is, for example, a vehicle driven by the NRS driver 4 and can transport users 2 for a fee as part of a ride-sharing business. The NRS vehicle 42 can be a private car or an idle taxi vehicle 32. The management system 1 can have multiple combinations of NRS drivers 4, NRS vehicles 42, and NRS terminals 40. Note that the NRS driver 4 cannot engage in so-called patrol business, which is to search for users 2 who want to ride while driving the taxi vehicle 32, as the taxi driver 3 does. However, in private car passenger transportation for a fee based on Article 78, Paragraph 3 of the Road Transportation Act, the NRS driver 4 can charge the user 2 a fee (fare) equivalent to that of a general passenger car transportation business as consideration for transporting the user 2. In addition, the NRS driver 4 may, for example, belong to a specified business such as a taxi business and perform the work of transporting the user 2.

[0031] Such taxi vehicles 32 and NRS vehicles 42 have designated operating areas in which they can operate. A taxi vehicle 32 can operate in the operating area where its taxi business office is located. For example, if the operating area is within Tokyo's special wards, the taxi vehicle 32 can operate in Tokyo's 23 wards, Musashino City, and Mitaka City. The operating area of ​​such a taxi vehicle 32 may be referred to as a transportation area.

[0032] The operating area of ​​the NRS vehicle 42 is included in the operating area of ​​the taxi vehicle 32 and is often smaller than that of the taxi vehicle 32. Furthermore, while the operating area of ​​the taxi vehicle 32 is limited in geographical area but not in time, the operating area of ​​the NRS vehicle 42 is not only limited in geographical area but also in time, such as only during periods (including seasons) when the supply of taxi vehicles 32 is insufficient to meet the demand. Thus, a taxi shortage in an area, period, or time zone where there is a shortage of taxi vehicles 32 is considered an "unavoidable case for the public welfare" under Article 78, Paragraph 3 of the Road Transportation Act, and a ride-sharing business is permitted. The operating area of ​​the NRS vehicle 42, like the operating area of ​​the taxi vehicle 32, is managed by a taxi operator, and is subject to the same regulations as the operating area of ​​the taxi vehicle 32. While this embodiment describes an example in which the operating area of ​​the NRS vehicle 42 is limited in both geographical area and time zone, the present invention is not limited to such an example, and there are also cases in which the operating area is limited only in geographical area and not in time zone.

[0033] FIG. 5 is a block diagram illustrating the configuration of the business operator terminal 50. The business operator terminal 50 is an information processing device (computer) owned by a business operator operating a taxi business. The business operator terminal 50 manages taxi vehicles 32 driven by taxi drivers 3 belonging to a taxi business and NRS vehicles 42 driven by NRS drivers 4. The business operator terminal 50 includes a communication device 150, a processing device 152, a display device 154, an input device 156, and a storage device 158. The communication device 150 is communicatively connected to external devices, such as taxi terminals 30, NRS terminals 40, and a management server 60, via a network 6. The processing device 152 includes a semiconductor integrated circuit including a processor (CPU), a ROM storing programs, and a RAM used as a work area. By running a program, the processing device 152 functions as a vehicle management unit 186 that manages vehicles belonging to the taxi business. The display device 154 includes a liquid crystal display (LCD) or an organic electroluminescence (EL) display, and displays various information, such as driver or vehicle information, obtained directly from the vehicle or via the management server 60. The input device 156 includes a keyboard, a touch panel superimposed on the display device 154, a microphone for voice input, a camera, etc., and receives input from an operator at the business. For example, the operator can talk to the driver or check images of the inside and outside of the vehicle, including images of the driver, through the business terminal 50. The storage device 158 is composed of storage means such as an HDD, SD memory, SSD, etc.

[0034] FIG. 6 is a block diagram illustrating the configuration of the management server 60. The management server 60 is an information processing device (computer) that manages vehicles belonging to taxi operators based on a contract between the dispatch management company and the taxi operator. The management server 60 is an example of a vehicle dispatch management device with server functions and is operated by the dispatch management company. The management server 60 can dispatch vehicles to users 2 in response to dispatch requests from user terminals 20. The management server 60 includes a communication device 160, a processing device 162, and a storage device 164. The communication device 160 is communicatively connected to external devices, such as the user terminal 20, the taxi terminal 30, the NRS terminal 40, and the operator terminal 50, via the network 6. The processing device 162 includes a semiconductor integrated circuit including a processor (CPU), a ROM storing programs and the like, and a RAM used as a work area. By running programs, the processing device 162 functions as functional units such as a user terminal control unit 170, a vehicle dispatch unit 172, and a vehicle terminal control unit 174. The user terminal control unit 170 controls user applications installed in the user terminal 20. The vehicle allocation unit 172 allocates a vehicle in response to a vehicle allocation request from the user 2. The vehicle terminal control unit 174 controls a vehicle application (for example, the driver application 200 of the NRS terminal 40) installed in the vehicle terminal. The storage device 164 is composed of storage means such as an HDD, SD memory, or SSD, and stores information about the user 2 and the vehicle.

[0035] When the management system 1 allocates a vehicle in response to a vehicle dispatch request (i.e., when dispatching a vehicle), for example, it matches multiple vehicle dispatch requests with multiple vehicles, thereby allocating one vehicle to, for example, one vehicle dispatch request from one user 2. Here, matching refers to a process of exclusively associating an arbitrary vehicle dispatch request with an arbitrary vehicle in a state where multiple vehicle dispatch requests and multiple vehicles exist. Note that, although one vehicle is allocated to one vehicle dispatch request, if multiple users 2 are allowed to ride in one vehicle, so-called carpooling, one vehicle may be allocated to multiple vehicle dispatch requests from multiple users 2.

[0036] 7 is a diagram illustrating the flow of transportation for user 2. In FIG. 7, an NRS terminal 40 is used as an example of a vehicle terminal, but the vehicle terminal is not limited to the NRS terminal 40 and may be a taxi terminal 30.

[0037] When user 2 wishes to ride in a vehicle, he or she makes a vehicle dispatch request through user terminal 20. Specifically, the vehicle dispatch request unit 180 of user terminal 20 launches a user application for making a vehicle dispatch request in response to an input operation by user 2. The user application displays a map of a predetermined range including the current location of user terminal 20, and also displays vehicles (e.g., taxi vehicles 32 and NRS vehicles 42) located near user terminal 20. The vehicle dispatch request unit 180 accepts user 2's vehicle dispatch request through input device 126. At this time, user 2 can set setting items for the vehicle to be boarded. The vehicle dispatch request unit 180 adds information related to the setting items set by user 2 and transmits the vehicle dispatch request to management server 60 (S10).

[0038] In addition to the initial setting of desired dispatch, the setting items include, for example, boarding location, disembarking location, payment information, dispatch category, taxi company, vehicle attributes, toll road information, etc.

[0039] The boarding location indicates the location on the map where User 2 wishes to board the vehicle. User 2 can set User 2's current location as the boarding location, or can set a desired location different from User 2's current location as the boarding location. The disembarking location indicates the location on the map where User 2 wishes to disembark. When User 2 sets the boarding location and disembarking location among the setting items, the fare calculated based on the set time, boarding location, and disembarking location is displayed on display device 124. In this way, User 2 can know in advance the fare that will be paid by boarding the vehicle.

[0040] When user 2 limits the vehicle dispatch targets to taxi vehicles 32 only, the drop-off location is not required input information but is information that can be input optionally. On the other hand, when user 2 includes NRS vehicles 42 in the vehicle dispatch targets, the drop-off location becomes required input information. This is because, in ride-sharing based on Article 78, Paragraph 3 of the Road Transportation Act, a requirement for dispatch (a requirement for dispatching an NRS vehicle 42) is that the fare must be determined in advance. Therefore, when including NRS vehicles 42 in the vehicle dispatch targets, user 2 must input the drop-off location in addition to the boarding location in order to calculate the fare in advance.

[0041] The payment information is information regarding payment of fees associated with vehicle use (e.g., fares and other additional fees). When an NRS vehicle 42 is included in the vehicle dispatch target, in addition to inputting the drop-off location, payment information also requires information regarding cashless automatic payment by credit card or the like (e.g., a credit card number). This is because ride-sharing services based on Article 78, Paragraph 3 of the Road Transportation Act require that a vehicle dispatch request be made through a user application and that cashless automatic payment be made as a requirement for vehicle dispatch. Here, automatic payment refers to a process in which, after the vehicle arrives at the drop-off location, the driver can bill User 2 for the fee associated with vehicle use based on User 2's automatic payment information, without User 2 paying cash or entering electronic money information into a cashless terminal. Thus, the NRS vehicle 42 differs from the taxi vehicle 32 in that the NRS vehicle 42 requires inputting the drop-off location and automatic payment information as a requirement for vehicle dispatch.

[0042] The dispatch category indicates the category of the vehicle to be dispatched. For example, as described above, taxi drivers 3 often hold Class 2 driver's licenses for standard vehicles and have high driver qualifications, driving skills, knowledge, etc. On the other hand, NRS drivers 4 vary in their driver qualifications, driving skills, knowledge, etc. As described above, even drivers who hold Class 2 driver's licenses for standard vehicles are not regularly employed as taxi drivers 3, and there are specific drivers who, for example, rent vehicles from taxi companies to transport users 2. These specific drivers often vary in their driver qualifications, driving skills, knowledge, etc. Note that when dispatching a specific vehicle driven by a specific driver, user 2 must also enter information about the drop-off location and automatic payment, just as with the NRS vehicle 42. Herein, vehicles with different dispatch requirements than taxi vehicle 32, including NRS vehicles 42 and specific vehicles, may be simply referred to as "required vehicles." Because driver qualifications, etc., vary depending on the vehicle, some users 2 may request dispatch of a taxi vehicle 32 driven by taxi driver 3. In this case, user 2 selects "only taxi vehicles 32" as the dispatch category. On the other hand, if the dispatch target is limited to taxi vehicles 32, user 2 will miss the opportunity to ride in a vehicle with requirements, even in a situation where a vehicle with requirements can be dispatched quickly. Therefore, user 2 may not limit the dispatch target to taxi vehicles 32, but may prefer taxi vehicles 32 and vehicles with requirements so that he or she can board a vehicle quickly. In this case, user 2 should select "taxi vehicles 32 and vehicles with requirements" as the dispatch category.

[0043] The taxi company indicates the company to which the taxi driver 3 or NRS driver 4 belongs as a taxi business. User 2 can specify the desired taxi company by inputting information into the taxi company setting items. Vehicle attributes indicate the type and equipment of the vehicle. Examples of vehicle attributes include whether or not the vehicle is a high-class vehicle (a so-called hire car), whether or not it is wheelchair accessible, whether or not it has sliding doors, etc. User 2 can specify the attributes of the vehicle he or she wishes to dispatch by inputting information into the vehicle attribute setting items.

[0044] The toll road information indicates whether or not to use a toll road such as an expressway. If the toll road information indicates that a toll road will be used, the toll road will be actively included in the route from the boarding point to the disembarking point.

[0045] The vehicle dispatch unit 172 of the management server 60 performs a matching process (S11) to combine (match) any one of the received vehicle dispatch requests with any one of the multiple vehicles that meets the setting items added to the vehicle dispatch request.

[0046] For example, the user terminal control unit 170 of the management server 60 sequentially accumulates vehicle dispatch requests received from the user terminal 20 in the storage device 164. The vehicle dispatch unit 172 of the management server 60 extracts all vehicle dispatch requests that have occurred in a specified business area up to a specified execution timing from the accumulated multiple vehicle dispatch requests. The vehicle dispatch unit 172 extracts one or more vehicles that satisfy specified extraction conditions from multiple vehicles that can accommodate user 2. The specified extraction conditions include, for example, conditions for various setting items related to the extracted vehicle dispatch requests. For each extracted vehicle dispatch request, the vehicle dispatch unit 172 extracts at least one vehicle that satisfies specified pairing conditions from the extracted vehicles and associates the extracted vehicle with the vehicle dispatch request. The specified pairing condition is that the vehicle's acceptable items must match all setting items of the vehicle dispatch request. The acceptable items are, for example, items that correspond to setting items of the vehicle dispatch request and indicate whether the vehicle and driver are acceptable. The vehicle allocation unit 172 exclusively matches vehicle allocation requests with vehicles for multiple combinations of associated vehicle allocation requests and vehicles. In the matching process, vehicle allocation requests and vehicles are matched such that one vehicle with the highest priority among at least one vehicle associated with each vehicle allocation request does not overlap with at least one vehicle associated with another vehicle allocation request. Various existing matching algorithms can be applied as a matching algorithm for vehicle allocation requests and vehicles.

[0047] The vehicle terminal control unit 174 of the management server 60 transmits information (notification of vehicle allocation target) indicating that the vehicle has become the target of the vehicle allocation request to the vehicle terminal (for example, the NRS terminal 40) located in the vehicle that has become the target of the vehicle allocation request (S12). The notification of vehicle allocation target corresponds to asking the driver of the vehicle that has become the target of the vehicle allocation whether or not to accept the vehicle allocation.

[0048] When the vehicle dispatch response unit 184 of the NRS terminal 40 receives the dispatch target notification, it notifies the NRS driver 4 that the vehicle has become the target of a vehicle dispatch request via the display device 144. In this way, the driver recognizes that his / her vehicle has become the target of a vehicle dispatch request, and can consider whether to accept the vehicle dispatch request.

[0049] When accepting the vehicle dispatch request, the driver accepts the vehicle dispatch request through the input device 146, for example, by tapping a position corresponding to an "accept request" button displayed on the display device 144. The vehicle dispatch response unit 184 transmits information regarding the acceptance of the vehicle dispatch request (acceptance response) to the management server 60 (S13).

[0050] When the vehicle terminal control unit 174 of the management server 60 receives the acceptance response, it confirms the dispatch of a vehicle in response to the dispatch request and transmits a dispatch decision notice indicating that the dispatch has been confirmed to the vehicle terminal (e.g., the NRS terminal 40) (S14). At the same time, the user terminal control unit 170 transmits a dispatch decision notice indicating that the dispatch has been confirmed to the user terminal 20 (S15).

[0051] Next, we will explain the flow after the NRS terminal 40 receives the dispatch decision notification. Note that although the NRS terminal 40 will be mentioned here, the same processing flow as after the NRS terminal 40 receives the dispatch decision notification may also be used after the taxi terminal 30 receives the dispatch decision notification.

[0052] Hereinafter, for the sake of convenience, the act of a vehicle that has been dispatched going to a boarding location of user 2 to pick up user 2 who has requested a vehicle dispatch may be referred to as "pick-up." Furthermore, the act of actually getting user 2 into a vehicle and transporting them to a disembarking location may be referred to as "delivery."

[0053] After the NRS terminal 40 receives the dispatch decision notification, the vehicle terminal control unit 174 of the management server 60 controls the driver application 200 of the NRS terminal 40 to switch the screen of the display device 144 of the NRS terminal 40 to a pick-up screen for the NRS vehicle 42 to pick up the driver. The display processing unit 202 of the NRS terminal 40 performs display processing of the pick-up screen under the control of the management server 60, as exemplified by arrow A20 in Figure 7 (S20).

[0054] 8 is a diagram showing an example of the pick-up screen 300. The pick-up screen 300 is displayed on the display device 144 after the dispatch of the vehicle is decided (in other words, after the dispatch request is accepted) and before the vehicle to be dispatched arrives at the boarding location of the user 2. In other words, the pick-up screen 300 is displayed on the display device 144 during the pickup.

[0055] For example, the pick-up screen 300 includes information on the current position 301 of the vehicle (specifically, the NRS vehicle 42 that is the dispatch target vehicle) on the map. The pick-up screen 300 also includes map information M1 of the surroundings of the vehicle's current position 301. For example, if both the vehicle's current position 301 and the boarding location position 303 fit within the map on the pick-up screen 300, the pick-up screen 300 includes information on the vehicle's current position 301 as well as information on the boarding location position 303 on the map.

[0056] Furthermore, for example, the pick-up screen 300 includes information on the boarding location address 302 included in the dispatch request. Note that the address in this embodiment is not limited to the meaning of a place of residence, but includes the meaning of a location and means information that identifies a place.

[0057] Pick-up screen 300 may include a navigation button B3. When navigation button B3 is pressed, a navigation application different from driver application 200 may be launched, and a screen showing a route from the current position of the vehicle to the pickup location may be displayed. Driver application 200 and the navigation application may be switchable with each other. Alternatively, the route to the pickup location may be displayed on a map on pick-up screen 300 of driver application 200.

[0058] The pick-up screen 300 may include a call button B4. The driver can press the call button B4 to make a call to the user terminal 20 of the user 2 who has sent the vehicle dispatch request.

[0059] The pick-up screen 300 may include a message button B5. The driver can press the message button B5 to send a message to the user terminal 20 of the user 2 who sent the ride request. In addition, the driver can check message information sent and received between the driver and the user 2 in response to pressing the message button B5.

[0060] Pick-up screen 300 includes a details button B6. Details button B6 is displayed, for example, in an area of ​​pick-up screen 300 where boarding location address 302 is displayed. The driver can press details button B6 to check detailed information about user 2.

[0061] FIG. 9 is a diagram showing an example of a details screen 300A that is displayed on the display device 144 when the details button B6 on the pick-up screen 300 is pressed.

[0062] When the details button B6 on the pick-up screen 300 is pressed, the display processing unit 202 of the NRS terminal 40 sends a display request for the details screen 300A to the management server 60. In response to receiving the display request, the vehicle terminal control unit 174 of the management server 60 sends detailed information about User 2 to the NRS terminal 40. In response to receiving the detailed information about User 2, the display processing unit 202 of the NRS terminal 40 causes the display device 144 to display the details screen 300A including the received detailed information.

[0063] The details screen 300A includes a boarding location tab 310 and a disembarking location tab 311 that can be switched between. The boarding location tab 310 is a switchable tab for mainly displaying information about the boarding location among information about the user 2. The disembarking location tab 311 is a switchable tab for mainly displaying information about the disembarking location among information about the user 2. In the example of FIG. 9, of the boarding location tab 310 and the disembarking location tab 311, the boarding location tab 310 is selected. Note that when the details button B6 is pressed, either the boarding location tab 310 or the disembarking location tab 311 may be displayed first.

[0064] Hereinafter, for ease of explanation, the screen in which the boarding location tab 310 of the details screen 300A is selected may be referred to as the boarding location tab screen. The screen in which the disembarking location tab 311 of the details screen 300A is selected may be referred to as the disembarking location tab screen. An example of the boarding location tab screen will be described below.

[0065] The boarding location tab screen includes map information M1 of the surroundings of the vehicle's current position 301. The boarding location tab screen includes information on the position 303 of the boarding location on the map.

[0066] The boarding location tab screen includes information on the boarding location address 302. As shown by "△△" in Fig. 9, the boarding location address 302 on the boarding location tab screen includes the part after the block number, for example, the part after the house number. In other words, the information on the boarding location address 302 on the boarding location tab screen can identify the boarding location of User 2.

[0067] If the boarding location has a name 312, the boarding location tab screen may include information on the boarding location name 312. In the example of Fig. 9, the name "XX Building" is associated with the boarding location address 302 and registered in advance, so information on the boarding location address 302 and the name 312 associated with the boarding location address 302 are displayed.

[0068] In addition, for example, User 2 may be able to register a specific name in advance with a specific address, such as by registering a name such as "Home" in association with the address of his or her home. In such a case, the boarding location tab screen may include information on the specific name registered by User 2 as information on the boarding location name 312.

[0069] The boarding location tab screen includes customer information 313 of user 2 who sent the ride dispatch request. The customer information 313 includes information related to the name of user 2. The customer information 313 may also include information related to the gender of user 2. The customer information 313 may also include information related to at least one of the age and generation of user 2.

[0070] The boarding location tab screen may include landmark information 314 for locating user 2. In the example of FIG. 9, the landmark information 314 presents the content, "I'm behind the intersection of the XX building, so please come around there." In this way, the landmark information 314 may include information about the geographical features of the boarding location. The landmark information 314 may also include information about objects present at the boarding location, such as information about the color of cars parked at the boarding location. The landmark information 314 may also include information related to identifying user 2, such as user 2's clothing. In other words, the landmark information 314 assists in identifying at least one of the boarding location and user 2.

[0071] Furthermore, the landmark information 314 may include information indicating a message that the NRS terminal 40 has received directly or indirectly from the user terminal 20. In other words, the landmark information 314 may be an example of message information transmitted and received between the user 2 and the driver. For example, after a vehicle is dispatched in response to the user 2's request for dispatch, the user 2 can send a message to the NRS terminal 40 of the vehicle that has been dispatched via the user terminal 20. The user 2 may send the landmark information 314 as the message. Furthermore, the NRS terminal 40 may be able to receive the landmark information 314 separately from the message sent by the user 2 after the vehicle is dispatched.

[0072] In this way, the boarding location tab screen displays detailed information about the boarding of user 2. By checking the detailed information displayed on the boarding location tab screen, the driver can quickly and accurately arrive at the boarding location and properly identify user 2.

[0073] Fig. 10 is a diagram showing another example of the details screen 300A that is displayed on the display device 144 when the details button B6 on the pick-up screen 300 is pressed. Fig. 10 shows the drop-off location tab screen that is displayed when the drop-off location tab 311 is tapped. The drop-off location tab screen displays detailed information about the drop-off of user 2.

[0074] The drop-off location tab screen includes information on the drop-off location address 322. As shown in "□□" in Fig. 10, the drop-off location address 322 on the drop-off location tab screen includes the part after the block number, for example, the part after the house number. In other words, the drop-off location address 322 information on the drop-off location tab screen can identify the drop-off location of User 2.

[0075] If the drop-off location has a name 323, the drop-off location tab screen may include information on the drop-off location name 323. In the example of Fig. 10, the name "△△ Building" is associated with the drop-off location address 322 and registered in advance, and therefore information on the name 323 associated with the drop-off location address 322 is displayed together with information on the drop-off location address 322. Furthermore, for example, the drop-off location tab may include information on a specific name registered by user 2 as information on the drop-off location name 323.

[0076] The drop-off location tab screen may include landmark information 324 that assists in identifying the drop-off location. The content of the landmark information 324 on the drop-off location tab screen may be different from the content of the landmark information 314 on the boarding location tab screen. For example, in the example of FIG. 10 , the landmark information 324 presents the content, "Get off in front of △△ Building." The landmark information 324 may include information about the geographical features of the boarding location, information about objects present at the drop-off location, etc.

[0077] Like the landmark information 314 on the boarding location tab screen, the landmark information 324 on the drop-off location tab screen may include information indicating a message that the NRS terminal 40 has received directly or indirectly from the user terminal 20. In other words, the landmark information 324 may be an example of message information transmitted and received between the user 2 and the driver.

[0078] Note that the landmark information 314 on the boarding location tab screen and the landmark information 324 on the disembarking location tab screen may not be transmitted from the user terminal 20 to the NRS terminal 40. Also, although the landmark information 314 on the boarding location tab screen and the landmark information 324 on the disembarking location tab screen can be transmitted from the user terminal 20 to the NRS terminal 40, the user 2 may not transmit the landmark information 314 and the landmark information 324. In such a case, the landmark information 314 on the boarding location tab screen and the landmark information 324 on the disembarking location tab screen may not be displayed.

[0079] Drivers can check the detailed information displayed on the drop-off location tab screen to arrive at the drop-off location quickly and accurately.

[0080] The details screen 300A includes a back button B9, which the driver can press to return to the pick-up screen 300.

[0081] 8, the pick-up screen 300 includes an arrival button B1. The arrival button B1 is intended to be pressed when the vehicle actually arrives at the boarding location or when the vehicle arrives within a predetermined distance (for example, within several tens of meters) from the boarding location.

[0082] When the Arrival button B1 is pressed, a signal (arrival signal) indicating that the vehicle has arrived near the boarding location is transmitted from the NRS terminal 40 to the user terminal 20 via the management server 60. More specifically, as shown in FIG. 7, upon receiving the press of the Arrival button B1, the display processing unit 202 of the NRS terminal 40 transmits a arrival signal to the management server 60 (S22). Upon receiving the arrival signal from the NRS terminal 40, the user terminal control unit 170 of the management server 60 transmits the arrival signal to the user terminal 20 (S23). Upon receiving the arrival signal, the processing device 122 of the user terminal 20 causes the display device 124 to display that the vehicle has arrived near the boarding location. This allows the user 2 to recognize that the vehicle has arrived near the boarding location.

[0083] Note that the arrival button B1 may be omitted from the pick-up screen 300 when the vehicle has not arrived within a predetermined distance from the boarding location, and may be added to the pick-up screen 300 when the vehicle has arrived within the predetermined distance from the boarding location. Alternatively, the arrival button B1 may be displayed on the pick-up screen 300 from the time the screen switches to the pick-up screen 300, regardless of the distance from the boarding location.

[0084] After pressing the arrival button B1, the map information M1 on the pick-up screen 300 may be enlarged and displayed with the vehicle at the center in preparation for the user 2 getting on.

[0085] 8, the pick-up screen 300 includes an actual vehicle button B2. The actual vehicle button B2 is intended to be pressed when the user 2 who sent the vehicle allocation request actually gets into the vehicle.

[0086] When the actual vehicle button B2 is pressed, a signal (actual vehicle signal) indicating that user 2 has boarded the NRS vehicle 42 is transmitted from the NRS terminal 40 to the management server 60. More specifically, as shown in FIG. 7, upon receiving the press of the actual vehicle button B2, the display processing unit 202 of the NRS terminal 40 transmits the actual vehicle signal to the management server 60 (S24). Upon receiving the actual vehicle signal, the vehicle terminal control unit 174 of the management server 60 changes the vehicle status from pick-up to actual vehicle. Then, the vehicle terminal control unit 174 controls the driver application 200 of the NRS terminal 40 to switch the screen of the display device 144 of the NRS terminal 40 from the pick-up screen to an actual vehicle screen for the NRS terminal 40 to perform actual driving. The display processing unit 202 of the NRS terminal 40 performs display processing of the actual vehicle screen under the control of the management server 60, as exemplified by arrow A30 in FIG. 7 (S30).

[0087] 11 is a diagram showing an example of the actual vehicle screen 320. The actual vehicle screen 320 is displayed on the display device 144 after the actual vehicle button B2 on the pick-up screen 300 is pressed and before transportation of user 2 is completed. In other words, the actual vehicle screen 320 is displayed on the display device 144 while the actual vehicle is in use.

[0088] The actual vehicle screen 320 includes information on the current position 301 of the vehicle (specifically, the NRS vehicle 42 transporting the user 2) on the map. The actual vehicle screen 320 also includes map information M1 of the surroundings of the vehicle's current position 301. For example, if both the vehicle's current position 301 and the drop-off location position 321 fit within the map on the actual vehicle screen 320, the actual vehicle screen 320 includes information on the vehicle's current position 301 as well as the drop-off location position 321 on the map.

[0089] Furthermore, for example, the actual vehicle screen 320 includes information on the drop-off location address 322 included in the dispatch request. As shown by "□□" in Fig. 11, the drop-off location address on the actual vehicle screen 320 includes the part after the block number, for example, the part after the house number. In other words, the information on the drop-off location address 322 can identify the drop-off location of user 2.

[0090] Furthermore, the actual vehicle screen 320 may include a details button B6, similar to the pick-up screen 300. When the details button B6 is pressed on the actual vehicle screen 320, the details screen 300A may be displayed, similar to when the details button B6 is pressed on the pick-up screen 300.

[0091] While driving the vehicle, the driver can arrive at the drop-off location quickly and accurately by checking the information on the vehicle screen 320 or the drop-off location tab screen of the details screen 300A, which is displayed by pressing the details button B6 on the vehicle screen 320.

[0092] The actual vehicle screen 320 includes an advance payment input button B10. The advance payment input button B10 is intended to be pressed when a toll road is used to transport the user 2. When a toll road toll is incurred, the driver presses the advance payment input button B10 to input the toll road toll.

[0093] The actual vehicle screen 320 includes a payment button B11. The payment button B11 is intended to be pressed when the vehicle actually arrives at the drop-off location.

[0094] 7, when the display processing unit 202 of the NRS terminal 40 receives a press of the payment button B11, it transmits a signal (payment signal) instructing the start of payment to the management server 60 (S32). When the vehicle terminal control unit 174 of the management server 60 receives the payment signal, it executes payment processing in accordance with the payment information set by the user 2 (S33).

[0095] When the payment process is completed, the vehicle terminal control unit 174 of the management server 60 sends a payment completion notice to the NRS terminal 40 (S34). When the display processing unit 202 of the NRS terminal 40 receives the payment completion notice, it causes the display device 144 to display that the payment has been completed. This allows the driver to recognize that the payment has been completed. Also, when the payment process is completed, the user terminal control unit 170 of the management server 60 sends a payment completion notice to the user terminal 20 (S35). When the processing device 122 of the user terminal 20 receives the payment completion notice, it causes the display device 124 to display that the payment has been completed. This allows the user 2 to recognize that the payment has been completed.

[0096] When the payment is completed in this manner, the transportation for the vehicle dispatch request of user 2 is completed. In other words, the driver completes one business transaction for the transportation of user 2. In response to the completion of the payment, the management server 60 may store in the storage device 164 the transportation history of the driver corresponding to the current vehicle dispatch request of user 2.

[0097] Hereinafter, for ease of explanation, the period from the time when the driver responds to user 2's dispatch request and the dispatch is confirmed (in other words, the time when the NRS terminal 40 receives the dispatch decision notification) to the time when the NRS vehicle 42 completes transportation of user 2 (in other words, the time when payment is completed) as shown by the double arrow A50 in Figure 7 may be referred to as a specific period.

[0098] With this configuration, the management system 1 displays specific information about the user 2 to be transported during the specific period on the display device of the vehicle terminal in response to input by the driver to the vehicle terminal during the specific period.

[0099] For example, specific information about the user 2 to be transported during a specific period is displayed on at least one of the pick-up screen 300, the details screen 300A, and the actual vehicle screen 320 in response to an input operation by the NRS driver 4 to the NRS terminal 40.

[0100] The specific information regarding user 2 may include information regarding the name of user 2, as illustrated in FIG. 9. Furthermore, the specific information regarding user 2 may include information regarding the boarding location address 302, which allows the boarding location to be identified, as illustrated in FIGS. 8 and 9. Furthermore, the specific information regarding user 2 may include information regarding the drop-off location address 322, which allows the drop-off location to be identified, as illustrated in FIG. 11. Furthermore, the specific information regarding user 2 may include information regarding the name of the boarding location, as illustrated in FIG. 9. Furthermore, the specific information regarding user 2 may include information regarding the name of the drop-off location, although not illustrated. Furthermore, the specific information regarding user 2 may include landmark information 314, as illustrated in FIG. 9. Furthermore, the specific information regarding user 2 may include information regarding messages sent and received between user 2 and the driver, although not illustrated. Furthermore, the specific information regarding user 2 may include information regarding the time when transportation of user 2 started (e.g., the time when the actual vehicle button B2 was pressed) and the time when transportation of user 2 was completed (e.g., the time when a payment completion notification was received), although not illustrated.

[0101] With this configuration, the driver can check various detailed information about user 2 while picking up the user and while driving the vehicle, which allows the driver to smoothly proceed with the pick-up and driving.

[0102] Next, a description will be given of processing after transportation of the user 2 is completed. The following description will be given with respect to the NRS terminal 40, but the taxi terminal 30 may also be processed in the same manner as the NRS terminal 40.

[0103] 7, when transportation of user 2 is completed, the vehicle terminal control unit 174 of the management server 60 controls the driver application 200 of the NRS terminal 40 to switch the screen of the display device 144 of the NRS terminal 40 to a menu screen indicating a state in which a vehicle can be dispatched. As shown by arrow A60 in FIG. 7, the display processing unit 202 of the NRS terminal 40 performs display processing of the menu screen under the control of the management server 60 (S60).

[0104] 12 is a diagram showing an example of the menu screen 340. The menu screen 340 is displayed on the display device 144 during the period from the completion of transportation for the user 2 until the next vehicle dispatch request is confirmed. In other words, the menu screen 340 is displayed when neither a pick-up nor a vehicle dispatch is being performed.

[0105] The menu screen 340 may include information on the vehicle dispatch status 341, for example, exemplified as "Accepting." "Accepting" indicates that a vehicle dispatch request is available for acceptance.

[0106] The menu screen 340 may also include a vehicle dispatch stop button 342 labeled "pause," for example.

[0107] When the vehicle dispatch stop button 342 is pressed, the vehicle dispatch response unit 184 of the NRS terminal 40 transmits stop request information requesting that vehicle dispatch be temporarily stopped to the management server 60. When the vehicle dispatch unit 172 of the management server 60 receives the stop request information, it performs processing to temporarily stop the dispatch of the NRS vehicle 42 corresponding to the received stop request information. Note that when the vehicle dispatch stop button 342 is pressed while vehicle dispatch is temporarily stopped, the vehicle dispatch response unit 184 may request the vehicle dispatch unit 172 to cancel the suspension of vehicle dispatch.

[0108] The menu screen 340 may also include information about the scheduled end date and time 343 of the current shift, such as "Scheduled end of shift: Month, Day, 1:00 AM." This allows the driver to confirm the scheduled end date and time of the current shift.

[0109] The menu screen 340 may also include an end-of-duty button 344 labeled "End of Duty."

[0110] For example, when the end time of the current shift has passed, the NRS driver 4 presses the duty end button 344 to end the current shift. When the duty end button 344 is pressed, the processing device 142 of the NRS terminal 40 performs processing to support necessary post-shift work, including post-shift roll call.

[0111] Menu screen 340 may also include a business history confirmation button 346 labeled "Business History." Business history confirmation button 346 may include information on the current number of business history items, for example, "6 items."

[0112] Fig. 13 is a diagram illustrating the flow of processing when the business history confirmation button 346 is pressed. As shown in Fig. 13, when the display processing unit 202 of the NRS terminal 40 receives an input operation of pressing the business history confirmation button 346 (S100), it transmits a history information request indicating a display request for the history of business conducted in one or more specific periods in the past to the management server 60 (S101).

[0113] When the vehicle terminal control unit 174 of the management server 60 receives the history information request, it identifies the NRS driver 4 corresponding to the NRS terminal 40 that sent the history information request, and reads out the history information of sales performed by the identified NRS driver 4 from the storage device 164 (S102). Note that the vehicle terminal control unit 174 may extract the history information of sales performed by the NRS driver 4 for a predetermined period of time (e.g., one week) from the current point in time as a reference point from the history information of all sales performed by the NRS driver 4.

[0114] The vehicle terminal control unit 174 generates post-restriction information, which is information after restricting at least a part of the specific information related to the user who performed transportation during the specific period, based on the read history information (S103). The post-restriction information will be described in detail later.

[0115] The vehicle terminal control unit 174 transmits the generated post-restriction information to the NRS terminal 40 (S104). Upon receiving the post-restriction information, the display processing unit 202 of the NRS terminal 40 displays the received post-restriction information on the display device 144 (S105). As a result, a business history screen including the post-restriction information is displayed on the display device 144.

[0116] 14 is a diagram showing an example of the business history screen 400. The business history screen 400 is displayed in response to pressing the business history confirmation button 346 on the menu screen. The business history screen 400 displays the history of one or more sales by the driver, by business.

[0117] The business history screen 400 includes information on business dates 402. The business history screen 400 also includes information on a series of business numbers 404 assigned to each business day.

[0118] The sales history screen 400 includes information on the sales amount 406 for each sales transaction, which allows the driver to check the sales amount for each sales transaction.

[0119] The business history screen 400 includes, for each business, information on the time 410 when user 2 boarded the vehicle. In other words, the time 410 when user 2 boarded the vehicle is the time when the actual vehicle button B2 was pressed. The business history screen 400 includes, for each business, information on the time 412 when transportation for user 2 was completed. In other words, the time 412 when transportation for user 2 was completed is the time when payment was completed.

[0120] The business history screen 400 includes information on the boarding area 420 for each business. In other words, the post-restriction information includes information on the boarding area 420 of user 2 who was transported during a specific period. The boarding area 420 can identify an area including the boarding location, but cannot identify the boarding location itself. For example, the boarding area 420 may include information on the address of the boarding location from the wider area to a predetermined first portion, and may not include information on a portion of the address that is narrower than the first portion. Specifically, the boarding area 420 may include information on the address of the boarding location up to the block number, but not information after the house number. Note that the boarding area 420 is not limited to a form that does not include information after the house number, and may, for example, include information up to the street name, but not information after the block number. The boarding area 420 is information after restricting information from the address of the boarding location that can identify the boarding location itself (for example, information after the house number).

[0121] The business history screen 400 includes information on the drop-off area 422 for each business. In other words, the post-restriction information includes information on the drop-off area 422 of user 2 who was transported during a specific period. The drop-off area 422 can identify an area including the drop-off location, but cannot identify the drop-off location itself. For example, the drop-off area 422 may include information on the drop-off location address 322 from the wider area to a predetermined second portion, and may not include information on a portion of the area narrower than the second portion. Specifically, the drop-off area 422 may include information on the drop-off location address 322 up to the block number, but not information after the house number. Note that the drop-off area 422 is not limited to a form that does not include information after the house number, and may, for example, include information up to the street name, but not information after the block number. The drop-off area 422 is information after restricting information from the drop-off location address 322 that can identify the drop-off location itself (for example, information after the house number).

[0122] As shown in FIG. 14 , customer information 313 of user 2 transported during each business trip (e.g., information related to the name of user 2) is not displayed on the business history screen 400. Furthermore, information on the name of the boarding location 312 and information on the name of the disembarking location 323 during each business trip are not displayed on the business history screen 400. Furthermore, landmark information 314 and landmark information 324 presented during each business trip are not displayed on the business history screen 400. Furthermore, message information sent and received between user 2 and the driver during each business trip is not displayed on the business history screen 400.

[0123] In addition, the business history screen 400 is not limited to not displaying all of the customer information 313, the name of the boarding location 312, the name of the disembarking location, the landmark information 314, and the message information, and may not display at least some of these.

[0124] Therefore, the post-restriction information may be information after at least one of the following specific information about user 2 has been restricted: information about user 2's name, information about the name of the boarding location 312, information about the name of the disembarking location, landmark information 314 that assists in identifying at least one of the boarding location and user 2, and message information sent and received between user 2 and the driver.

[0125] In this way, the business history screen 400 displays restricted information, which is information after restricting at least a portion of the specific information related to the user 2 who made a delivery during a specific period. In other words, in the management system 1, the information that can be confirmed on the business history screen 400 is limited to the restricted information.

[0126] This prevents the driver from checking the personal information of the user 2 who has transported the vehicle after the transport. In particular, since the NRS driver 4 can easily check the business history using the NRS terminal 40, limiting the information that can be checked on the business history screen 400 to the restricted information improves the protection of the user 2's privacy.

[0127] In addition, the business history screen 400 displays restricted information including, for example, information on the boarding area 420 and the disembarking area 422, so that the driver cannot check the personal information of User 2, but the driver can check an overview of past business operations.

[0128] After the dispatch is decided, if the driver and user 2 do not meet up properly, the dispatch request of user 2 may be canceled. In such a case, cancellation information 430 indicating the cancellation may be displayed on the business history screen 400. This allows the driver to confirm that the business has been canceled.

[0129] The business history screen 400 includes a back button 440. The driver can press the back button 440 to return to the menu screen 340.

[0130] Furthermore, when the business history confirmation button 346 on the menu screen 340 is pressed while the NRS vehicle 42 is in motion, the display processing unit 202 may not display the post-restriction information on the business history screen 400. In this case, for example, a warning message such as "Business history cannot be checked while the vehicle is in motion" may be displayed on the business history screen 400.

[0131] Furthermore, the business history screen 400 is not limited to a mode in which it can be displayed from the menu screen 340 during a driving shift, but may also be displayed by performing a predetermined input operation even after a driving shift has ended.

[0132] As described above, the management device (management server 60) of this embodiment is a management device (management server 60) that can communicate via a network (network 6) with a vehicle terminal (NRS terminal 40) that is used when a driver (NRS driver 4) of a vehicle (NRS vehicle 42) drives the vehicle (NRS vehicle 42) as a commercial vehicle, which is a means of transportation for a user (user 2), and is equipped with one or more processors (processing devices 162). The processors (processing devices 162) are configured to process the vehicle dispatch request of the user (user 2) from the time the driver (NRS driver 4) responds to the request and the dispatch is confirmed. During a specific period until the time when the transportation of the user (User 2) is completed, specific information about the user (User 2) who will be transported during the specific period is displayed on the display device (display device 144) of the vehicle terminal (NRS terminal 40) in accordance with input by the driver (NRS driver 4) to the vehicle terminal (NRS terminal 40). After the specific period ends, restricted information, which is information after restricting at least a portion of the specific information about the user (User 2) who was transported during the specific period, is displayed on the display device (display device 144) of the vehicle terminal (NRS terminal 40) in accordance with input by the driver (NRS driver 4) to the vehicle terminal (NRS terminal 40). With this configuration, after transporting during the specific period, the information that the driver can confirm about the user who transported is limited to the restricted information. This makes it possible to prevent the driver from confirming personal information of the user who transported after the transport. Therefore, the management device of this embodiment can improve protection of user privacy.

[0133] The post-restriction information may include information on the boarding area (boarding area 420) and the disembarking area (disembarking area 422) of the user (user 2) transported during the specified period. The boarding area (boarding area 420) information may include information on the boarding address of the user (user 2) transported during the specified period, from the widest area to a predetermined first portion, but not information on a portion narrower than the first portion. The disembarking area (disembarking area 422) information may include information on the disembarking address of the user (user 2) transported during the specified period, from the widest area to a predetermined second portion, but not information on a portion narrower than the second portion. With this configuration, after transport, the driver can check the boarding and disembarking areas of past business. As a result, although the driver cannot identify the user's boarding and disembarking locations after transport, he or she can check an outline of the user's past business. This allows the driver to look back on past business while protecting the user's privacy.

[0134] The post-restriction information may be information after at least one of the following specific information about the user (User 2): information about the user's (User 2's) name, information about the name of the boarding location (Name 312), information about the name of the drop-off location, landmark information (Landmark Information 314) that assists in identifying at least one of the boarding location and the user (User 2), and message information transmitted and received between the user (User 2) and the driver (NRS Driver 4) has been restricted. With this configuration, after transportation, the driver will not be able to confirm at least one of the user's name, the name of the boarding location, the name of the drop-off location, the landmark information, and the message information. Because the user's name, the name of the boarding location, the name of the drop-off location, the landmark information, and the message information are related to the user's personal information, this can improve protection of the user's privacy.

[0135] The management system (management system 1) of this embodiment includes a vehicle terminal (NRS terminal 40) used when a driver (NRS driver 4) of a vehicle (NRS vehicle 42) drives the vehicle (NRS vehicle 42) as a commercial vehicle, which is a means of transportation for a user (user 2), and a management device (management server 60) that can communicate with the vehicle terminal (NRS terminal 40) via a network (network 6). The vehicle terminal (NRS terminal 40) has one or more first processors (processing devices 142) and a display device (display device 144). The management device (management server 60) has one or more second processors (processing devices 162). The first processor (processing device 142) processes inputs of the driver (NRS driver 4) to the vehicle terminal (NRS terminal 40) during a specific period from when the driver (NRS driver 4) responds to a vehicle dispatch request from a user (user 2) and dispatch is confirmed to when transportation of the user (user 2) is completed. In response to the request, the second processor (processing device 162) transmits a display request for specific information regarding the user (user 2) who will transport during the specific period to the management device (management server 60), and in response to receiving the display request for the specific information for the specific period, the second processor (processing device 162) transmits the specific information to the vehicle terminal (NRS terminal 40) to display it on the display device (display device 144), and after the specific period ends, the first processor (processing device 142) transmits a display request for the history of business operations conducted during the specific period to the management device (management server 60) in response to input by the driver (NRS driver 4) to the vehicle terminal (NRS terminal 40), and in response to receiving the display request for the history of business operations conducted during the specific period, the second processor (processing device 162) generates post-restriction information, which is information after restricting at least some of the specific information regarding the user (user 2) who transported during the specific period, and transmits the generated post-restriction information to the vehicle terminal (NRS terminal 40) to display it on the display device (display device 144). With this configuration, after transporting during the specific period, the information that the driver can check regarding the user who transported is limited to the post-restriction information. This prevents the driver from checking the personal information of the user who has transported the goods after the delivery, and therefore, the management system of this embodiment can improve the protection of the user's privacy.

[0136] In the management method of this embodiment, a computer displays specific information about the user (User 2) who is transported during the specific period on the display device (display device 144) of the vehicle terminal (NRS terminal 40) in response to an input from the driver (NRS driver 4) to the vehicle terminal (NRS terminal 40) during the specific period from when the driver (NRS driver 4) of the vehicle (NRS vehicle 42) responds to a request for transportation from the user (User 2) and confirms the dispatch to when the transportation of the user (User 2) is completed. After the specific period ends, the computer displays restricted information, which is information after restricting at least some of the specific information about the user (User 2) who was transported during the specific period, on the display device (display device 144) of the vehicle terminal (NRS terminal 40) in response to an input from the driver (NRS driver 4) to the vehicle terminal (NRS terminal 40). With this configuration, after transporting during the specific period, the information that the driver can view about the user who transported the user is limited to the restricted information. This prevents the driver from viewing personal information about the user who transported the user after the transport. Therefore, according to the management method of this embodiment, it is possible to improve the protection of the user's privacy.

[0137] The program of this embodiment causes a computer to execute the following operations: displaying specific information about the user (user 2) who is transported during the specific period on the display device (display device 144) of the vehicle terminal (NRS terminal 40) in response to an input from the driver (NRS driver 4) to the vehicle terminal (NRS terminal 40) during the specific period from when the driver (NRS driver 4) of the vehicle (NRS vehicle 42) responds to a request for transportation from the user (user 2) and confirms the dispatch until when the transportation of the user (user 2) is completed; and displaying, after the specific period ends, restricted information, which is information after restricting at least some of the specific information about the user (user 2) who was transported during the specific period, on the display device (display device 144) of the vehicle terminal (NRS terminal 40) in response to an input from the driver (NRS driver 4) to the vehicle terminal (NRS terminal 40). With this configuration, after transporting during the specific period, the information that the driver can view about the user who transported the user is limited to the restricted information. This prevents the driver from viewing personal information about the user who transported the user after the transport. Therefore, according to the program of this embodiment, it is possible to improve the protection of the user's privacy.

[0138] While the preferred embodiments of the present invention have been described above with reference to the accompanying drawings, it goes without saying that the present invention is not limited to such embodiments. It is clear that those skilled in the art can conceive of various modifications and alterations within the scope of the claims, and it is understood that such modifications and alterations also fall within the technical scope of the present invention.

[0139] For example, in the above embodiment, an input operation of pressing various buttons displayed on the display device 144 of the NRS terminal 40 causes the processing corresponding to the various buttons to be executed. However, instead of pressing various buttons, the processing corresponding to the various buttons may be executed by swiping in a predetermined direction at a predetermined position on the screen of the display device 144. Also, instead of pressing various buttons, various processes may be executed by voice input. In this case, the display of the various buttons may be omitted.

[0140] Also provided are programs that cause a computer to function as the management server 60, and computer-readable storage media such as flexible disks, magneto-optical disks, ROMs, CDs, DVDs, and BDs on which the programs are recorded. Here, the program refers to data processing means written in any language or description method.

[0141] It should be noted that the processes shown in this specification do not necessarily have to be performed in chronological order according to the order shown in the flowcharts, and may include parallel or subroutine processes. [Explanation of symbols]

[0142] 1 Management System 2 users 6 Network 4 NRS Driver 40 NRS terminals 42 NRS vehicles 60 Management Server 142 Processing equipment 144 Display device 162 Processing equipment

Claims

1. A management device capable of communicating via a network with a vehicle terminal used when a vehicle driver drives the vehicle as a commercial vehicle that is a means of transportation for a user, one or more processors; The processor: During a specific period from when the driver responds to the user's request for vehicle dispatch and confirms the dispatch to when the transportation of the user is completed, specific information regarding the user to be transported during the specific period is displayed on a display device of the vehicle terminal in response to an input by the driver to the vehicle terminal; A management device that, after the end of the specific period, displays post-restriction information on the display device of the vehicle terminal, which is information after restricting at least some of the specific information regarding the user who was transported during the specific period, in accordance with input by the driver to the vehicle terminal.

2. The post-restriction information includes information on the boarding area and the disembarking area of ​​the user transported during the specific period, The information on the boarding area includes information on the address of the boarding location of the user transported during the specific period, from the widest area to a predetermined first part, and does not include information on an area narrower than the first part, The management device described in claim 1, wherein the information on the drop-off area includes information on the addresses of the drop-off locations of the users transported during the specific period, from the largest area to a specified second part, and does not include information on areas narrower than the second part.

3. The management device described in claim 1, wherein the post-restriction information is information after at least one of the specific information regarding the user, including information regarding the user's name, information regarding the name of the boarding location, information regarding the name of the disembarking location, landmark information that assists in identifying at least one of the boarding location and the user, and message information sent and received between the user and the driver, has been restricted.

4. a vehicle terminal used by a vehicle driver when driving the vehicle as a commercial vehicle that is a means of transportation for a user; a management device capable of communicating with the vehicle terminal via a network; Equipped with The vehicle terminal one or more first processors; a display device; The management device one or more second processors; The first processor During a specific period from when the driver responds to the user's request for vehicle dispatch and confirms the dispatch to when the transportation of the user is completed, a display request for specific information regarding the user who will be transported during the specific period is sent to the management device in response to an input by the driver to the vehicle terminal; The second processor In response to a display request for the specific information during the specific period, the specific information is transmitted to the vehicle terminal and displayed on the display device; The first processor After the specific period ends, in response to an input by the driver to the vehicle terminal, a display request for a history of business operations performed during the specific period is transmitted to the management device; The second processor In response to receiving a display request for the history of business conducted during the specific period, generate restricted information which is information obtained by restricting at least a portion of the specific information related to the user who made a delivery during the specific period; A management system that transmits the generated post-restriction information to the vehicle terminal and displays it on the display device.

5. The computer During a specific period from when the vehicle driver responds to the user's request for vehicle dispatch and confirms the dispatch to when the transportation of the user is completed, specific information regarding the user to be transported during the specific period is displayed on a display device of the vehicle terminal in response to input by the driver to the vehicle terminal; A management method in which, after the end of the specified period, post-restriction information, which is information after restricting at least some of the specific information regarding the user who was transported during the specified period, is displayed on a display device of the vehicle terminal in accordance with input by the driver to the vehicle terminal.

6. On the computer, During a specific period from when the vehicle driver responds to the user's request for vehicle dispatch and confirms the dispatch to when the transportation of the user is completed, specific information regarding the user to be transported during the specific period is displayed on a display device of the vehicle terminal in response to input by the driver to the vehicle terminal; After the specific period ends, in response to an input by the driver to the vehicle terminal, displaying post-restriction information, which is information after restricting at least a portion of the specific information regarding the user who was transported during the specific period, on a display device of the vehicle terminal. A program to make it happen.

Images