Vehicle and service management device

Abstract

The vehicle is provided with: a communication unit that receives operating information from a management server; a control unit that operates the vehicle based on the operating information from the communication unit; a management unit that manages the compartment of the vehicle in which a service user receives service from a service provider; and an interface unit that is set to establish a correspondence between the service-related information provided by the service provider and the compartment.

Description

Technical Field

[0001] This invention relates to management systems, management devices, management methods, and procedures.

[0002] This application claims priority based on Japanese Patent Application No. 2017-119131 filed in Japan on June 16, 2017, the contents of which are incorporated herein by reference.

[0003] This application claims priority based on Japanese Patent Application No. 2017-118691 filed in Japan on June 16, 2017, the contents of which are incorporated herein by reference.

[0004] This application claims priority based on Japanese Patent Application No. 2017-118698 filed in Japan on June 16, 2017, the contents of which are incorporated herein by reference.

[0005] This application claims priority based on Japanese Patent Application No. 2017-118699, filed in Japan on June 16, 2017, the contents of which are incorporated herein by reference.

[0006] This application claims priority based on Japanese Patent Application No. 2017-118745, filed in Japan on June 16, 2017, the contents of which are incorporated herein by reference.

[0007] This application claims priority based on Japanese Patent Application No. 2017-119025 filed in Japan on June 16, 2017, the contents of which are incorporated herein by reference.

[0008] This application claims priority based on Japanese Patent Application No. 2017-118719 filed in Japan on June 16, 2017, the contents of which are incorporated herein by reference.

[0009] This application claims priority based on Japanese Patent Application No. 2017-118689 filed in Japan on June 16, 2017, the contents of which are incorporated herein by reference.

[0010] This application claims priority based on Japanese Patent Application No. 2017-118915 filed in Japan on June 16, 2017, the contents of which are incorporated herein by reference. Background Technology

[0011] In recent years, the development of autonomous driving technology that enables vehicles to travel along a path to their destination has been progressing (see Patent Document 1).

[0012] Prior art literature

[0013] Patent documents

[0014] Patent Document 1: Japanese Patent Application Publication No. 2017-83446 Summary of the Invention

[0015] The problem that the invention aims to solve

[0016] Sometimes, it is preferable if an autonomous vehicle can be used for multiple purposes.

[0017] This invention was made in consideration of such circumstances, and one of its objectives is to provide a vehicle and service management device that enables more flexible use of vehicles.

[0018] Methods for solving problems

[0019] The vehicle and service management device of the present invention adopts the following structure.

[0020] (1): A vehicle according to one aspect of the present invention includes: a communication unit that receives operating information from a management server; a control unit that operates the vehicle based on the operating information from the communication unit; a management unit that manages the compartments of the vehicle in which service users receive services from service providers; and an interface unit that is configured to establish a correspondence with service association information provided by the service provider and the compartments.

[0021] (2): In the above scheme (1), the communication unit sends a control signal for controlling the interface unit to the management server or the service provider, based on the access status of the service user relative to the vehicle.

[0022] (3): In the above (2) scheme, the interface includes an external display, and the vehicle also has a display control unit, which uses the external display to execute the display mode specified by the service provider in relation to a control signal.

[0023] (4): In the above (1) scheme, the vehicle is further equipped with a utilization status detection unit for detecting the utilization status of the vehicle compartment, and the communication unit sends the detection signal of the utilization status detection unit to the service provider.

[0024] (5): In the above (1) scheme, the vehicle is equipped with an external environment detection unit that detects the outside of the compartment, and the communication unit sends the detection signal of the external environment detection unit to the service provider.

[0025] (6): In the above scheme (1), the communication unit receives a service signal sent from the service provider, and the vehicle further includes: a compartment control signal generation unit that generates a control signal corresponding to the received service signal and sends it to a machine configured in the compartment; and an operation control signal generation unit that sends the control signal corresponding to the service signal to the control unit.

[0026] (7): In the above (1) scheme, the vehicle has an attribute sharing unit that shares the attributes of the compartment with the management server or the service provider, and the interface unit is set in correspondence with the attributes.

[0027] (8): In the above (1) scheme, the interface unit performs the operation of the external device via the service provider.

[0028] (9): In the above scheme (1), the interface unit performs a path change to a specific destination provided to the service provider.

[0029] (10): In the above-mentioned (1) solution, the interface unit further includes: a display unit that displays the items provided by the service provider; and an operation information sending unit that sends operation information to the service provider via the communication unit.

[0030] (11): In the above (1) scheme, the control unit includes an autonomous driving control unit that performs autonomous driving based on external detection sensors and location information sensors, and the interface unit allows the service user to use information during the execution of the autonomous driving and during the service user's ride.

[0031] (12): In the above (1) scheme, the interface provides information to the service user before or after the service user boards the compartment.

[0032] (13): In the above (3) scheme, the vehicle also has a storage unit for storing entries for external display, and the display control unit downloads the entries from an external device and updates the entries stored in the storage unit.

[0033] (14): In the above (1) scheme, the vehicle further includes: a driving unit that does not have a cabin; and a first connecting part disposed in the driving unit and connected to an upper structure, the upper structure being installed in the driving unit in a detachable manner, the management unit obtaining driving unit information including the model information of the driving unit from the management server, and connecting an upper structure whose model matches the obtained driving unit information using the first connecting part.

[0034] (15): A service management device according to one aspect of the present invention includes: a determination unit that determines a vehicle used by a service provider; and a vehicle information providing unit that sends information related to the vehicle corresponding to the vehicle determined by the determination unit to the service provider, wherein the service management device includes: a service information input unit that inputs service information of the service provider; and an interface control unit that sends a control signal to the vehicle based on the service information to control the information transmission between the vehicle and the service provider.

[0035] (16): In the above (15) scheme, the interface control unit allows the vehicle information providing unit to send information about the interval during which the service user receives the service provider's service while riding in the vehicle to the service provider.

[0036] (17): In the above (15) scheme, the interface control unit includes a path update unit that allows the vehicle's path or destination to be updated by control signals from the service provider.

[0037] (18): In the above (15) scheme, the interface control unit further includes an external display control unit that controls the external display of the vehicle via a control signal from the service provider.

[0038] (19): In the above (15) scheme, the interface control unit has a service operation control unit, which executes the sending of information related to the vehicle to the service provider based on the control signal from the vehicle.

[0039] (20): In the above (15) scheme, the determining unit determines the vehicle from vehicles in a specific region.

[0040] (21): In the above (15) scheme, the determining unit determines the vehicle based on the location information provided by the service provider and the pick-up and drop-off location information provided by either the service provider or the service user.

[0041] (22): In the above (21) scheme, the determining unit determines multiple vehicles for the service provider based on the location information and the boarding / alighting location information.

[0042] (23): In the above (15) scheme, the service management device further includes: a vehicle location management unit that detects the location of multiple vehicles; and a service location management unit that establishes an association with the service information corresponding to the multiple vehicles, and the interface control unit provides environmental information to the multiple vehicles, service users or service providers based on the location information and service information obtained from the multiple vehicles.

[0043] (24): In the above (23) scheme, the interface control unit determines the service implementation status in the region as the environmental information based on the location information obtained from the plurality of vehicles and the service attribute information corresponding to the plurality of vehicles.

[0044] (25): In the above (15) scheme, the service management device further includes a storage unit for storing the display mode of the vehicle relative to the service information, and the interface control unit enables the entry data stored in the storage unit to be selectively used by the vehicle based on the service information.

[0045] Invention Effects

[0046] According to (1), more flexible use of vehicles can be achieved. Attached Figure Description

[0047] Figure 1 This is a perspective view showing an autonomous vehicle 100.

[0048] Figure 2 This is a structural diagram showing the driving unit 110.

[0049] Figure 3 This is a diagram used to illustrate the processing steps of autonomous driving.

[0050] Figure 4 This is a front view showing an example of the connecting part 151.

[0051] Figure 5 This is a perspective view showing the driving body M including the first upper unit 200A.

[0052] Figure 6 This is a structural diagram showing the first upper unit 200A and the driving unit 110.

[0053] Figure 7 This is a perspective view showing the driving body M including the second upper unit 200B.

[0054] Figure 8 This is a perspective view showing the driving body M, including the third upper unit 200C.

[0055] Figure 9 This is a perspective view showing the driving body M, including the fourth upper unit 200D.

[0056] Figure 10 This is a perspective view showing the driving body M, including the fourth upper unit 200D.

[0057] Figure 11 This is a perspective view showing the driving body M, including the fifth upper unit 200E.

[0058] Figure 12 This is a perspective view showing the driving body M, including the sixth upper unit 200F.

[0059] Figure 13 This is a perspective view showing a first variant of the autonomous vehicle 100.

[0060] Figure 14 This is a perspective view showing a second variant of the autonomous vehicle 100.

[0061] Figure 15 This is a structural diagram showing an example of vehicle utilization system 1.

[0062] Figure 16 This is a structural diagram showing the first upper unit 200A and the driving unit 110 in the second embodiment.

[0063] Figure 17 This is a diagram showing an example of the external display unit 202b.

[0064] Figure 18 This is a diagram showing an example of the external display unit 202b.

[0065] Figure 19 This is a structural diagram of the service provision system 2, which includes a vehicle 100 (autonomous vehicle 100), according to the third embodiment.

[0066] Figure 20 This is a diagram showing an example of the structure of the driving unit 110 according to the third embodiment.

[0067] Figure 21 This is a diagram showing an example of the structure of a vehicle management device 300 mounted on a vehicle 100.

[0068] Figure 22 This is a diagram illustrating an example of the structure of a service provider device 600.

[0069] Figure 23 This is a diagram illustrating an example of the structure of the service management device 700.

[0070] Figure 24 This is a flowchart illustrating an example of the processing flow performed in service providing system 2.

[0071] Figure 25 This is a structural diagram of a service provision system a1, which includes a service management device a300.

[0072] Figure 26 This is a structural diagram of vehicle A200.

[0073] Figure 27This is an example diagram showing the contents of a384, which is a list of ride requests.

[0074] Figure 28 This is a diagram illustrating an example of the scope information a386 that the service can provide.

[0075] Figure 29 This is a diagram (Figure 1) illustrating the situation where a ride-sharing plan is decided.

[0076] Figure 30 It shows a reflection Figure 29 The diagram shows an example of the content of the ride-sharing plan's schedule information a388.

[0077] Figure 31 This is a diagram (Figure 2) illustrating the situation where the carpooling plan is decided.

[0078] Figure 32 It shows a reflection Figure 31 The diagram shows an example of the content of the ride-sharing plan's schedule information a388.

[0079] Figure 33 This is a flowchart illustrating an example of the processing flow performed by the service management device a300.

[0080] Figure 34 This is an example of an IM screen that asks whether the details of a ride request can be changed.

[0081] Figure 35 This diagram illustrates the situation where a ride-sharing plan is determined in a first variation of the second embodiment.

[0082] Figure 36 It shows a reflection Figure 35 The diagram shows an example of the content of the ride-sharing plan's schedule information a388.

[0083] Figure 37 This diagram illustrates the situation where a ride-sharing plan is determined in a second variation of the second embodiment.

[0084] Figure 38 It shows a reflection Figure 37 The diagram shows an example of the content of the ride-sharing plan's schedule information a388.

[0085] Figure 39 This is a diagram illustrating an example of the contents of a 384A list of ride requests for a third variation of the second embodiment.

[0086] Figure 40 This is a diagram illustrating an example of the service providing range information a386A in a third variation of the second embodiment.

[0087] Figure 41 This is a diagram schematically illustrating the driving controls performed by vehicle a200.

[0088] Figure 42 This is a structural diagram of a service provisioning system a2, which includes a service management device a700, as a fourth variation of the second embodiment.

[0089] Figure 43 This is a diagram showing an example of the structure of the vehicle management device a510 mounted on vehicle a500.

[0090] Figure 44 This is a diagram illustrating an example of the structure of a service provider device a600.

[0091] Figure 45 This is a diagram illustrating an example of the structure of the service management device a700.

[0092] Figure 46 This is a flowchart illustrating an example of the process executed in service providing system a2.

[0093] Figure 47 This is a structural diagram of the vehicle distribution system b1.

[0094] Figure 48 This is a structural diagram of vehicle B100.

[0095] Figure 49 This is a functional structure diagram of facility terminal B200.

[0096] Figure 50 This is a functional structure diagram of the user terminal b300.

[0097] Figure 51 This is an example of a screen showing facility reservations.

[0098] Figure 52 This is an example of a car booking screen.

[0099] Figure 53 This is a functional structure diagram showing the pick-up and drop-off management device b400.

[0100] Figure 54 This is an example diagram showing facility reservation information b421.

[0101] Figure 55 This is an example of a vehicle reservation information b422.

[0102] Figure 56 This is a diagram showing an example of vehicle allocation status information b423.

[0103] Figure 57 This is a diagram illustrating an example of movement status information b425.

[0104] Figure 58 This is a flowchart illustrating an example of processing actions in vehicle b100.

[0105] Figure 59 This is a flowchart illustrating an example of processing actions in vehicle b100.

[0106] Figure 60 This is a flowchart illustrating an example of the processing actions in the pick-up and drop-off management device 400b.

[0107] Figure 61 This is a flowchart illustrating an example of the processing actions in the pick-up and drop-off management device 400b.

[0108] Figure 62 This is a flowchart illustrating an example of the processing actions in the pick-up and drop-off management device 400b.

[0109] Figure 63 This diagram is used to illustrate an example that utilizes the vehicle allocation system b1.

[0110] Figure 64 Another example of the vehicle allocation system b1 will be explained.

[0111] Figure 65 This is a functional structure diagram of the service provider device b600.

[0112] Figure 66 This is a functional structure diagram of the service management device B700.

[0113] Figure 67 This is a functional structure diagram of the vehicle management device b910 mounted on vehicle b100.

[0114] Figure 68 This is a flowchart illustrating an example of the processing flow performed in the vehicle allocation system b1A.

[0115] Figure 69 This is a structural diagram of vehicle system c1.

[0116] Figure 70 This is a diagram showing the structure inside the autonomous vehicle c100.

[0117] Figure 71 This is an example of an IM (Instant Messaging) screen for a store.

[0118] Figure 72 This is a functional structure diagram of the C100 autonomous vehicle.

[0119] Figure 73 This is a flowchart illustrating an example of processing actions in an autonomous vehicle c100.

[0120] Figure 74 This diagram illustrates the usage of the C100 autonomous vehicle.

[0121] Figure 75 This is a structural diagram of the vehicle system c2 of the first variation of the fourth embodiment.

[0122] Figure 76 This is a sequence diagram illustrating an example of the processing method performed by vehicle system c2.

[0123] Figure 77 This diagram illustrates the utilization configuration of the first vehicle c500 and the second vehicles c600 and c700.

[0124] Figure 78 This is a structural diagram of the event-based vehicle matching system d1 in the fifth embodiment.

[0125] Figure 79 This is a structural diagram of vehicle d200 according to the fifth embodiment.

[0126] Figure 80 This is an example of the event vehicle matching settings screen IM1.

[0127] Figure 81 This is a diagram showing an example of the contents of event table d172.

[0128] Figure 82 This is a diagram showing an example of the contents of vehicle allocation table d173.

[0129] Figure 83 This is a diagram showing an example of the contents of vehicle attribute table d174.

[0130] Figure 84 This is an example of the event vehicle matching setting screen IM2 displayed on the display unit d120 after the event vehicle matching is performed.

[0131] Figure 85 This is a diagram showing an example of the contents of vehicle information DBd175.

[0132] Figure 86 This is a diagram showing an example of the content of notification result management information d176.

[0133] Figure 87 This diagram illustrates the event notification for the d200 vehicle.

[0134] Figure 88 This is an example of an event notification screen IM3 displayed on the HMId232 of vehicle d200.

[0135] Figure 89This is an example of an event notification screen IM4 sent to vehicle d200 that responded to the request to participate.

[0136] Figure 90 This diagram illustrates the situation where the indicator d160 indicates the parking position of the vehicle d200.

[0137] Figure 91 This is an example diagram showing the contents of parking location management information d177.

[0138] Figure 92 This is a flowchart illustrating an example of the processing flow performed by the event vehicle matching device d100 according to the fifth embodiment.

[0139] Figure 93 This is a structural diagram of the event vehicle matching system d2 of the first variation of the fifth embodiment.

[0140] Figure 94 This is an example of an event information screen IM5 displayed on the terminal device d500.

[0141] Figure 95 This is an example of the pick-up and drop-off settings screen IM6.

[0142] Figure 96 This is a diagram illustrating an example of the content of user management information d178.

[0143] Figure 97 This diagram illustrates the use of vehicle d200 for pick-up and drop-off.

[0144] Figure 98 This is a flowchart illustrating an example of the processing flow performed by the event dispatching device d100A of the first variant of the fifth embodiment.

[0145] Figure 99 This is an example of an IM7 navigation screen showing travel plans.

[0146] Figure 100 This is a structural diagram of the event vehicle matching system d3 of the second variation of the fifth embodiment.

[0147] Figure 101 This is a diagram illustrating an example of the structure of a vehicle management device d270 mounted on a vehicle d200, representing a second variation of the fifth embodiment.

[0148] Figure 102 This is a diagram illustrating an example of the structure of a service provider device d700, a second variation of the fifth embodiment.

[0149] Figure 103This is a diagram illustrating an example of the structure of the event vehicle dispatching device d100B, a second variation of the fifth embodiment.

[0150] Figure 104 This is a sequence diagram illustrating an example of the processing flow of the event matching system d3 in the second variation of the fifth embodiment.

[0151] Figure 105 This is a diagram showing an outline of the in-vehicle performance device e1 in the sixth embodiment.

[0152] Figure 106 This is a functional structure diagram showing an example of the structure of the in-vehicle performance device e1 according to the sixth embodiment.

[0153] Figure 107 This is a diagram showing an example of a response image GP1A indicating the detection of a shooting action.

[0154] Figure 108 This is a diagram showing an example of a response image GP1B indicating that a shot has been fired.

[0155] Figure 109 This is a diagram showing an example of a response image GP1C representing the score information.

[0156] Figure 110 This is a flowchart illustrating an example of the operation of the in-vehicle performance device e1 according to the sixth embodiment.

[0157] Figure 111 This is a functional structure diagram illustrating an example of the structure of the in-vehicle performance device e2 of the first variation of the sixth embodiment.

[0158] Figure 112 This is an example of a display of a response image shown by another in-vehicle performance device e2, illustrating a first variation of the sixth embodiment.

[0159] Figure 113 This is a diagram illustrating an example of the results of a shooting game based on the territory area rule derived from the driving path.

[0160] Figure 114 This is a diagram illustrating an example of winning or losing in a shooting game under territory area rules.

[0161] Figure 115 This is a functional structure diagram illustrating an example of the structure of the in-vehicle performance device 3 of the second variation of the sixth embodiment.

[0162] Figure 116 This is a diagram illustrating an example of the contents of resume information e500-2.

[0163] Figure 117This is a diagram illustrating an example of the contents of service provider information e500-3.

[0164] Figure 118 This is a structural diagram of the vehicle control system f according to the implementation method.

[0165] Figure 119 This is a structural diagram of the vehicle f200 according to the implementation method.

[0166] Figure 120 This is an example of a screen IM1 showing the entry request.

[0167] Figure 121 This is a diagram showing an example of the contents of different vehicle entry data f342.

[0168] Figure 122 This is an example of the content of advertising information for different car models, f344.

[0169] Figure 123 This is a diagram showing an example of the content of user information f346.

[0170] Figure 124 This is an example of an image showing the result screen IM2 for an entry.

[0171] Figure 125 This is a diagram showing an example of the contents of the display condition data f278A.

[0172] Figure 126 This diagram illustrates the situation where items are displayed on the display unit f272 outside the vehicle.

[0173] Figure 127 This diagram is used to illustrate the speed control of vehicle f200.

[0174] Figure 128 This diagram illustrates the control over the display of advertising information.

[0175] Figure 129 This is a flowchart illustrating an example of the processing flow performed by vehicle f200.

[0176] Figure 130 This is a structural diagram of a service provisioning system f2 including a vehicle f200, illustrating a first variation of the seventh embodiment.

[0177] Figure 131 This is a diagram showing an example of the structure of the vehicle management device f210A mounted on vehicle f200.

[0178] Figure 132 This is a diagram illustrating an example of the structure of a service provider device f600.

[0179] Figure 133This is a diagram illustrating an example of the structure of the service management device f700.

[0180] Figure 134 This is a diagram showing an example of the contents of the display condition data f139.

[0181] Figure 135 This diagram is used to explain the processing of the update unit 744.

[0182] Figure 136 This is a flowchart illustrating an example of the process executed in service providing system f2.

[0183] Figure 137 It is a perspective view of vehicle f200 with an exterior display unit f272 that shows information about users who have made reservations.

[0184] Figure 138 This is a diagram of vehicle f200 viewed from the side, showing the exterior display unit f272 displaying information about users who have made reservations.

[0185] Figure 139 It is a perspective view of vehicle f200 with an exterior display unit f272 displaying service attributes.

[0186] Figure 140 This is a diagram of vehicle f200 viewed from the side, showing the exterior display unit f272 displaying information about the service attributes.

[0187] Figure 141 It is a perspective view of vehicle f200, which has an exterior display unit f272 that displays information related to the event.

[0188] Figure 142 This is a diagram of vehicle f200 viewed from the side, showing the exterior display unit f272 that displays information related to the event.

[0189] Figure 143 This is a picture of the vehicle viewed from the rear.

[0190] Figure 144 It is a perspective view of vehicle f200 with an exterior display unit f272 that displays information indicating that it is a regional sampling vehicle.

[0191] Figure 145 This is a structural diagram of vehicle system g1.

[0192] Figure 146 This is a structural diagram of vehicle G100.

[0193] Figure 147 This is a functional structure diagram of the room equipment G200.

[0194] Figure 148 This is a functional structure diagram of the management server g300.

[0195] Figure 149 This is a diagram showing an example of the contents of interface information g322.

[0196] Figure 150 This is a diagram showing an example of room information g322.

[0197] Figure 151 This is a sequence diagram illustrating an example of the processing performed by vehicle system g1.

[0198] Figure 152 This is a sequence diagram illustrating an example of the processing performed by vehicle system g1.

[0199] Figure 153 This is a diagram illustrating an example of a child-facing room reproduced inside vehicle g100.

[0200] Figure 154 This is an illustration showing an example of a café-style room recreated inside vehicle g100.

[0201] Figure 155 This is a diagram illustrating an example of a work-oriented room reproduced within vehicle g100.

[0202] Figure 156 This is an illustration showing an example of a user's own living room reproduced inside vehicle g100.

[0203] Figure 157 This is a diagram showing the combined room area g700 when viewed from above, where vehicle g100 and room g600 are combined.

[0204] Figure 158 This is a diagram showing the separation of vehicle g100 and room g600 from above.

[0205] Figure 159 This is a structural diagram of the vehicle system h1 according to the ninth embodiment.

[0206] Figure 160 This is a structural diagram of vehicle h200 according to the ninth embodiment.

[0207] Figure 161 This is a diagram showing an example of the content of user information h351.

[0208] Figure 162 This is a diagram showing an example of a ride request screen h400 displayed on the display unit of the terminal device h100.

[0209] Figure 163This is an example of a ride request result screen h410 displayed on the terminal device h100.

[0210] Figure 164 This is a diagram showing an example of the contents of path information h353.

[0211] Figure 165 This diagram illustrates the situation of vehicle h200 traveling in a patrol area.

[0212] Figure 166 This is a flowchart illustrating an example of the process performed by the vehicle management device h300.

[0213] Figure 167 This is a flowchart illustrating an example of the processing flow performed by vehicle h200.

[0214] Figure 168 This is a structural diagram of the vehicle system h2 of the first variation of the ninth embodiment.

[0215] Figure 169 This is a structural diagram of the station communication device H600.

[0216] Figure 170 This diagram illustrates a scenario where user U makes a travel request through the station communication device h600.

[0217] Figure 171 This is a structural diagram of the vehicle system h3 of the second variation of the ninth embodiment.

[0218] Figure 172 This is a structural diagram of vehicle h200B, a second variation of the ninth embodiment.

[0219] Figure 173 This is a diagram used to illustrate the processing of decision events.

[0220] Figure 174 This is a structural diagram of the vehicle h200C, a third variation of the ninth embodiment.

[0221] Figure 175 This is a structural diagram of the service management system i1 in the tenth embodiment.

[0222] Figure 176 This is a structural diagram of the i200 vehicle. Detailed Implementation

[0223] The vehicle and service management apparatus of the present invention will now be described with reference to the accompanying drawings. The autonomous vehicle of the present invention is, for example, a vehicle that maximizes the degrees of freedom of the superstructure provided with the autonomous driving function in a trolley-like form, and can be used for various purposes by giving it versatility. In the embodiments shown below, the autonomous vehicle, for example, can change at least one of the shape and function of the superstructure according to its purpose by changing the superstructure. "Autonomous vehicle" refers, for example, to an autonomous vehicle that substantially does not require driving operation.

[0224] In the following description, structures with the same or similar functions are labeled with the same number. Furthermore, repeated descriptions of these structures are sometimes omitted. "Based on XX" means "at least based on XX," and also includes cases where it is based on other elements besides XX. "Based on XX" is not limited to the direct use of XX, but can also include cases based on elements obtained through operations or processing of XX. "XX" is any element (e.g., any information).

[0225] <First Implementation Method>

[0226] [Overall structure of autonomous vehicles]

[0227] The first embodiment will be described below. Figure 1 This is a perspective view showing the autonomous vehicle 100 according to the first embodiment. In the first embodiment, the unit excluding the superstructure 200 described later is referred to as "autonomous vehicle 100". On the other hand, the unit combining the autonomous vehicle 100 and the superstructure 200 is referred to as "driving body M" or "moving body M".

[0228] The autonomous vehicle 100 is a flat plate without a cabin, seats, etc. "Flat plate" broadly means flat and is not limited to the meaning of a flat or solid shape. For example, "flat plate" also includes cases with bends or curves, concave or convex parts, or hollow parts. "Flat plate" can also be described as "flat".

[0229] In this embodiment, the autonomous vehicle 100 is a plate-shaped vehicle whose maximum height from the ground G is less than 1.5 times the diameter D of the wheel W (described later). Alternatively, the autonomous vehicle 100 is a plate-shaped vehicle whose maximum thickness in the height direction (excluding the wheel W, which in this embodiment is the same as the maximum thickness of the driving unit 110 described later) is less than or equal to the diameter D of the wheel W. The structure of such an autonomous vehicle 100 will be described in detail below. Hereinafter, the autonomous vehicle 100 will be simply referred to as "vehicle 100". The vehicle 100 includes, for example, a driving unit 110 and a connecting mechanism 150.

[0230] [Driving Unit]

[0231] The driving unit 110 is a plate-shaped driving unit with automatic driving function, forming the main part of the vehicle 100. The driving unit 110 is a plate-shaped unit without a passenger compartment, seats, etc. For example, the driving unit 110 is a plate-shaped unit whose maximum thickness T in the height direction, excluding the wheels W, is less than or equal to the diameter D of the wheel W. The driving unit 110 can be installed on the superstructure 200 in a detachable manner (see reference). Figure 5 , Figures 7-12 "Installation" means, for example, that the superstructure 200 is placed on the travel unit 110, but also includes the state in which the superstructure 200 is not fixed to the travel unit 110.

[0232] like Figure 1 As shown, the driving unit 110 has a mounting area R for mounting the superstructure 200 in a detachable manner and a plurality of wheels W. The "mounting area R" will be described later. The plurality of wheels W includes drive wheels driven by the drive force output device 116, described later. The driving unit 110 is, for example, a driving unit with four or more wheels W, but it can also be a driving unit with two or three wheels W, such as a motorized two-wheeled vehicle or other vehicles. The plurality of wheels W includes a first wheel W1 and a second wheel W2. The second wheel W2 is located rearward than the first wheel W1 in the vehicle's direction of travel X.

[0233] Figure 2 This is a structural diagram showing the driving unit 110. The driving unit 110 includes, for example, an external monitoring unit 111, a communication device 112, a navigation device 113, a lane recommendation device 114, an automatic driving control unit 115, a drive force output device 116, a braking device 117, a steering device 118, a linkage mechanism control unit 119, and a power module 120 (see reference). Figure 6 Interface 121 (refer to) Figure 6 ) and storage unit 122. In the following description, vehicle 100 is sometimes referred to as "this vehicle 100". The connection mechanism control unit 119 will be described later.

[0234] The navigation control device 113b, lane recommendation device 114, automatic driving control unit 115, and linkage mechanism control unit 119 of the navigation device 113 described below can each be implemented by a processor such as a CPU (Central Processing Unit) executing a program (software) stored in memory. Alternatively, they can be implemented by hardware such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or GPU (Graphics Processing Unit). Furthermore, they can be implemented through the coordinated use of software and hardware. The program can be pre-stored in a storage device such as an HDD (Hard Disk Drive) or flash memory, or it can be stored in a removable storage medium such as a DVD or CD-ROM, and installed into the storage device by assembling the storage medium into the drive device.

[0235] The external monitoring unit 111 includes, for example, cameras, radar, LIDAR (Light Detection and Ranging), and object recognition devices that perform sensor fusion processing based on their outputs. The external monitoring unit 111 estimates the types of objects present in the vicinity of the vehicle 100 (in particular, vehicles, pedestrians, and bicycles), and outputs the estimated object types along with their position and speed information to the autonomous driving control unit 115.

[0236] The communication device (wireless communication unit) 112 is, for example, a wireless communication module used for connecting to a network NW, communicating directly with the terminal device 500 of the user of the vehicle 100, and communicating directly with the terminal devices of other vehicles, pedestrians, etc. For example, without the communication connector 121a and gateway device 121b described later, the communication device 112 can also communicate with the HMI (Human Machine Interface) 202 (see reference 121b) provided on the upper structure 200 via the communication device 201 on the upper structure 200. Figure 6Direct communication is also possible. That is, the communication device 112 can also obtain information input to the HMI 202 (e.g., information indicating input operations to the driving control unit 202a) via wireless communication with the communication device 201 of the superstructure 200. The communication device 112 performs wireless communication based on Wi-Fi, DSRC (Dedicated Short Range Communications), Bluetooth (registered trademark), or other communication standards. Multiple devices corresponding to the application may also be prepared as the communication device 112. For example, the communication device 112 obtains instructions related to the driving of the vehicle 100 (e.g., instructions related to the destination) from the user's terminal device 500 (or the user-operated HMI 202). The communication device 112 is an example of an "acquisition unit." For example, the communication device 112 obtains information related to the destination of the vehicle 100. The communication device 112 outputs the obtained information to the navigation device 113 and the automatic driving control unit 115. Network NW includes the Internet, WAN (Wide Area Network), LAN (Local Area Network), public lines, carrier equipment, dedicated lines, wireless base stations, etc. The user's terminal device 500 is, for example, a smartphone, tablet, personal computer, etc.

[0237] Navigation device 113 includes, for example, a GNSS (Global Navigation Satellite System) receiver 113a and a navigation control device 113b. The GNSS receiver 113a determines its own position (the position of vehicle 100) based on radio waves from GNSS satellites (e.g., GPS satellites). The navigation control device 113b includes, for example, a CPU and various storage devices, and controls the overall navigation device 113. Map information (navigation map) is stored in the storage devices. The navigation map is a map (including road information) that represents roads using nodes and lines. The navigation control device 113b refers to the navigation map to determine the path (driving plan) from the position of vehicle 100 determined by the GNSS receiver 113a to the destination of vehicle 100 obtained by the communication device 112. The navigation control device 113b is an example of a "driving plan generation unit". The navigation control device 113b can also use the communication device 112 to send the position and destination of vehicle 100 to a navigation server (not shown) and obtain the path from the navigation server. The navigation control device 113b outputs information about the route determined or identified using any of the above methods to the lane recommendation device 114.

[0238] The lane recommendation device 114 includes, for example, an MPU (Micro Processing Unit) and various storage devices. The storage devices contain high-precision map information more detailed than the navigation map. This high-precision map information includes, for example, information such as the road width, gradient, curvature, and signal location for each lane. The lane recommendation device 114 determines the preferred lane for driving along the path input from the navigation device 113 and outputs it to the automatic driving control unit 115.

[0239] The automatic driving control unit 115 has one or more processors such as a CPU and an MPU, as well as various storage devices. The automatic driving control unit 115 is an example of an "automatic driving control unit." In this embodiment, the automatic driving control unit 115 also serves as the control unit for the overall control of the driving unit 110. The automatic driving control unit 115 drives the driving unit 110 automatically, based on the principle of driving in the recommended lane determined by the recommended lane determination device 114, in a way that avoids contact with objects whose position and speed have been input from the external monitoring unit 111. The automatic driving control unit 115 executes various events sequentially, for example. These events include constant-speed driving events (driving at a certain speed in the same driving lane), following driving events (following a vehicle ahead), lane changing events, merging events, branching events, emergency stop events, toll station events (for passing through a toll station), and handover events (for ending automatic driving and switching to manual driving). During the execution of these events, actions are sometimes planned to avoid obstacles based on the surrounding conditions of the vehicle 100 (the presence of surrounding vehicles and pedestrians, lane narrowing caused by road construction, etc.).

[0240] The automatic driving control unit 115 generates a target trajectory for the future travel of the vehicle 100. The target trajectory may include, for example, speed elements. For instance, the target trajectory may be represented as a track arranging the locations (track points) that the vehicle 100 should reach at predetermined travel distances. Independently, target speeds and target accelerations are generated as part of the target trajectory at predetermined sampling times (e.g., a fraction of a second). Track points may also be the locations that the vehicle 100 should reach at that sampling time at predetermined sampling times. In this case, the target speed and target acceleration information are represented by the intervals between track points.

[0241] Figure 3This diagram illustrates the processing steps of autonomous driving. First, as shown in the diagram above, the navigation device 113 determines or identifies a path. This path is, for example, a rough path without lane distinctions. Next, as shown in the middle diagram, the lane recommendation device 114 determines a recommended lane that is easy to follow along the path. Then, as shown in the diagram below, the autonomous driving control unit 115 generates track points for traveling as close to the recommended lane as possible while avoiding obstacles, and controls some or all of the drive force output device 116, braking device 117, and steering device 118 to travel along the track points (and the accompanying speed curves). This division of labor is just one example; for example, the autonomous driving control unit 115 may also perform the processing centrally.

[0242] The drive force output device 116 outputs the driving force (torque) used to drive the driving unit 110 to the wheels W. The drive force output device 116 is an example of a "drive source". The drive force output device 116 may include, for example, a combination of an internal combustion engine, an electric motor, and a transmission, and a power ECU that controls them. In this embodiment, the drive force output device 116 includes a drive motor 116a. The power ECU controls the above-described structure according to information input from the automatic driving control unit 115.

[0243] Braking device 117 includes, for example, a brake caliper, a hydraulic cylinder that transmits hydraulic pressure to the brake caliper, an electric motor that generates hydraulic pressure in the hydraulic cylinder, and a braking ECU. The braking ECU controls the electric motor according to information input from the automatic driving control unit 115, so that braking torque corresponding to the braking operation is output to each wheel. Braking device 117 may also include a mechanism as a backup for transmitting hydraulic pressure generated by the operation of the brake pedal included in the driving control unit (e.g., the driving control unit 202a of the superstructure 200 described later) to the hydraulic cylinder via the master hydraulic cylinder. Braking device 117 is not limited to the structure described above, and may also be an electronically controlled hydraulic braking device that transmits hydraulic pressure from the master hydraulic cylinder to the hydraulic cylinder according to information input from the automatic driving control unit 115.

[0244] The steering system 118 includes, for example, a steering ECU and an electric motor. The electric motor, for example, applies force to a rack and pinion mechanism to change the orientation of the steering wheels. The steering ECU drives the electric motor according to information input from the automatic driving control unit 115 or from the driving controls, thereby changing the orientation of the steering wheels.

[0245] like Figure 6As shown, the power module 120 includes a battery 120a and a battery management unit (not shown) that controls the battery 120a. The power module 120 supplies power from the battery 120a to the various devices of the driving unit 110 (external monitoring unit 111, communication device 112, navigation device 113, lane recommendation device 114, automatic driving control unit 115, drive force output device 116, braking device 117, steering device 118, coupling mechanism control unit 119, etc.). That is, the various devices of the driving unit 110 share a portion of the power supplied to the upper unit (described later) to operate. The power module 120 supplies power from the battery 120a to the various devices of the upper unit via the power supply connector 121c and regulator 121d of the interface 121 (described later).

[0246] Interface 121 may include, for example, a communication connector 121a, a gateway device 121b, a power supply connector 121c, and a regulator (power conversion device) 121d.

[0247] The power supply connector 121c and regulator 121d of interface 121 are examples of a "power supply interface," and the communication connector 121a and gateway device 121b of interface 121 are examples of a "first communication interface." Additionally, the communication connector 121a is also an example of a "communication interface." The communication connector 121a is electrically connected to the gateway device 121b. The communication connector 121a is exposed to the outside of the driving unit 110, allowing for physical and electrical connection to the communication connector 209a of the upper structure 200.

[0248] Gateway device 121b is an example of a "communication control unit". Gateway device 121b can communicate with the superstructure 200 via communication connector 121a. For example, gateway device 121b communicates with gateway device 209b of the superstructure 200. For example, gateway device 121b performs comparison and authentication between the superstructure 200 and the driving unit 110 based on the control of at least one of the automatic driving control unit 115 and the control unit 208 of the superstructure 200 (e.g., comparison and authentication between gateway device 121b and gateway device 209b). Comparison and authentication include, for example, a process of authenticating that the sender of the frame is a legitimate party by comparing the ID (sending ID) assigned to the frame sent from one of gateway device 121b and gateway device 209b with information pre-stored by the other of gateway device 121b and gateway device 209b (e.g., information stored in storage unit 122). The comparison and authentication process includes, for example, gateway device 121b authenticating that the superstructure 200 that sent the frame is a legitimate superstructure 200 by comparing the ID (sending ID) assigned to the frame sent from gateway device 209b with pre-stored information (e.g., information stored in storage unit 122). "Legitimate" means, for example, that vehicle 100 and superstructure 200 can be combined (e.g., their specifications are consistent) or that superstructure 200 belongs to a trustworthy owner (an owner pre-registered in a register).

[0249] For example, gateway device 121b detects the category of the superstructure 200 connected to interface 121 through the aforementioned comparison and authentication. "Category" includes "form". For example, gateway device 121b detects the category of the superstructure 200 connected to interface 121 based on the ID (transmission ID) assigned to the frame sent from gateway device 209b and the corresponding table T (a table in which multiple IDs are associated with multiple superstructures 200) stored in storage unit 122. Autonomous driving control unit 115 identifies the function, power consumption, etc., of the superstructure 200 based on the content authenticated by gateway device 121b (e.g., the category of the superstructure 200). Information representing the function, power consumption, etc., of various superstructures 200 is stored in storage unit 122, for example, as part of table T. Autonomous driving control unit 115 identifies, for example, the function, power consumption, etc., corresponding to the detected category of the superstructure 200 based on the category of the superstructure 200 and table T.

[0250] Gateway device 121b can acquire various information from communication device 201, HMI 202, seat device 203, collision sensor 204, airbag device 205, and control unit 208 of the superstructure 200 via gateway device 209b of the superstructure 200. Gateway device 121b is another example of an "acquisition unit". For example, gateway device 121b acquires information from HMI 202 indicating the operation input to driving operation device 202a of HMI 202 via gateway device 209b of the superstructure 200. Gateway device 121b outputs the information acquired from HMI 202 to automatic driving control unit 115. As a result, automatic driving control unit 115 can control the driving of vehicle 100 based on the information indicating the operation input to driving operation device 202a of HMI 202.

[0251] The power connector 121c is electrically connected to the battery 120a of the power module 120 via the regulator 121d. The power connector 121c is exposed to the outside of the driving unit 110, allowing for physical and electrical connection to the power connector 209c of the superstructure 200.

[0252] Regulator 121d adjusts the supplied electrical power (e.g., voltage) output to the upper structure 200 via power connector 121c. Regulator 209d may be, for example, an inverter that converts regenerative power output from drive motor 116a into direct current. For example, based on the control of automatic driving control unit 115, regulator 121d adjusts the power output from power module 120 to power corresponding to the function and power consumption of the upper structure 200, and supplies the adjusted power to the upper structure 200.

[0253] The driving unit 110 has one or more interfaces 121 having the functions described above. For example, the driving unit 110 has multiple interfaces 121 having the functions described above. The multiple interfaces 121 are separately configured in multiple locations of the driving unit 110. According to this structure, the degree of freedom in the location of the connectors, etc. of the upper structure 200 is increased. Therefore, the versatility of the vehicle 100 is further increased.

[0254] The storage unit 122 is implemented, for example, by a hybrid storage device consisting of RAM (Random Access Memory), ROM (Read Only Memory), HDD (Hard Disk Drive), flash memory, or a combination thereof.

[0255] Next, return Figure 1The mounting area R of the travel unit 110 will be described below. The mounting area R is a region where the upper structure 200 can be mounted (e.g., placed), and is a region that can support the upper structure 200 from below. In this embodiment, the mounting area R is formed as a generally horizontal plane. The mounting area R forms part of the upper surface of the travel unit 110. For example, the mounting area R forms the uppermost surface of the travel unit 110. For example, the mounting area R is located at a height of less than 1.5 times the diameter D of the wheel W relative to the ground G in contact with the wheel W.

[0256] In this embodiment, the mounting area R has a size that extends from approximately the same position as the first wheel W1 to approximately the same position as the second wheel W2 in the vehicle's travel direction X. For example, the mounting area R extends in the vehicle's travel direction from a position forward of the first wheel W1 to a position rearward of the second wheel W2. In this embodiment, the mounting area R is provided along the entire length of the travel unit 110 in the vehicle's travel direction X.

[0257] like Figure 1 As shown, in this embodiment, the driving unit 110 has a first base 131, a second base 132, a raised portion 133, a first upright portion 134, and a second upright portion 135. The first base 131 and the second base 132 are arranged separately in the vehicle width direction Y with respect to the center of the vehicle 100. The raised portion 133 is disposed between the first base 131 and the second base 132, and is located approximately at the center of the vehicle 100 in the vehicle width direction Y. The raised portion 133 protrudes upward with respect to the first base 131 and the second base 132.

[0258] The first upright portion 134 is located on the side opposite to the raised portion 133 relative to the first base portion 131. The first upright portion 134 rises upward from the end of the first base portion 131. Thus, a first recess 136, defined by the first upright portion 134, the first base portion 131, and the raised portion 133, is formed between the first upright portion 134 and the raised portion 133. Similarly, the second upright portion 135 is located on the side opposite to the raised portion 133 relative to the second base portion 132. The second upright portion 135 rises upward from the end of the second base portion 132. Thus, a second recess 137, defined by the second upright portion 135, the second base portion 132, and the raised portion 133, is formed between the second upright portion 135 and the raised portion 133.

[0259] Furthermore, in this embodiment, the raised portion 133 has a first plane 133a extending along the entire length of the travel unit 110 in the vehicle travel direction X. The first raised portion 134 has a second plane 134a extending along the entire length of the travel unit 110 in the vehicle travel direction X. The second raised portion 135 has a third plane 135a extending along the entire length of the travel unit 110 in the vehicle travel direction X. In this embodiment, the mounting area R is formed by these first to third planes 133a, 134a, and 135a.

[0260] [Linked Organizations]

[0261] Next, the connecting mechanism 150 will be described. The connecting mechanism 150 has one or more connecting portions 151. The multiple connecting portions 151 are separately arranged at multiple positions in the vehicle's longitudinal direction X and the vehicle's width direction Y. Each connecting portion 151 is connected to an upper structure 200 that is detachably mounted relative to the travel unit 110, and the upper structure 200 is fixed relative to the travel unit 110. The connecting portion 151 is an example of a "first connecting portion".

[0262] Figure 4 This is a front view showing an example of the connecting part 151. (Example) Figure 4 As shown, one example of the connecting portion 151 has a base 151a fixed to the travel unit 110 and an engaging portion (movable portion) 151b that can move forward and backward relative to the base 151a. The engaging portion 151b can move between a first position where it enters the inside of the engaging hole h provided in the upper structure 200 and engages with the engaging hole h, and a second position where it moves out of the engaging hole h. When the connecting portion 151 moves to the first position via the engaging portion 151b, the upper structure 200 is fixed to the travel unit 110. On the other hand, when the connecting portion 151 moves to the second position via the engaging portion 151b, the fixing relative to the upper structure 200 is released. The upper structure 200 can be removed from the travel unit 110 when the fixing by the connecting portion 151 is released. The connecting portion 151 may also have only the engaging portion 151b without the base 151a. In this case, the engaging part 151b may also be provided in the first upright part 134 and the second upright part 135 of the driving unit 110 (in Figure 1 (Refer to the double-dotted line in the middle). The connecting part 151 is not limited to the example above. The connecting part 151 is any structure that connects to the upper structure 200, and is not limited to a specific structure.

[0263] The linkage control unit 119 activates the linkage unit 151, for example, based on the control of the automatic driving control unit 115. That is, the linkage control unit 119 controls the linkage unit 151 to switch the state of the vehicle 100 between a state in which the upper structure 200 is fixed to the driving unit 110 and a state in which the upper structure 200 can be removed from the driving unit 110.

[0264] [Superstructure]

[0265] Next, the first upper unit 200A, which is an example of the upper structure 200, will be described. Figure 5 This is a perspective view showing the vehicle body M including the first upper unit 200A. The first upper unit 200A is a unit that enables the vehicle 100 to have the same functions as a general passenger car. For example, the first upper unit 200A has a body 210 with a passenger compartment 211. The passenger compartment 211 is an example of a "room that passengers can enter". The upper structure 200, for example, has a size that covers the entire mounting area R of the vehicle body 110.

[0266] Figure 6 This is a structural diagram showing the first upper unit 200A and the driving unit 110. Figure 6 In the diagram, only a portion of the functions of the driving unit 110 are shown. For example... Figure 6 As shown, the first upper unit 200A includes a communication device 201, an HMI 202, a seat device 203, a collision sensor 204, an airbag device 205, a headlight 206, a taillight 207, a control unit 208, and an interface 209.

[0267] Communication device (wireless communication unit) 201 is, for example, used with network NW (refer to) Figure 2 A wireless communication module that connects to or directly communicates with the communication device 112 of the vehicle 100. The communication device 201 performs wireless communication based on Wi-Fi, DSRC (Dedicated Short Range Communications), Bluetooth, or other communication standards. Multiple communication devices may also be prepared as the communication device 201, depending on the application.

[0268] HMI 202 includes, for example, a steering wheel, accelerator pads, brake pads, and other driving controls (operation devices) 202a for performing operations related to the driving of vehicle 100 (e.g., auxiliary operations or operations in manual driving mode), a touch panel display device, speakers, microphones, etc. Information input to HMI 202 (e.g., information indicating input operations to driving controls 202a) is transmitted via gateway device 209b (or communication device 201) and received by gateway device 121b (or communication device 112) of vehicle 100.

[0269] Seat assembly 203 is located within vehicle compartment 211 for passenger seating. Collision sensor 204 is located on vehicle body 210 to detect collisions input to vehicle body 210. Airbag assembly 205 operates based on the detection results of collision sensor 204. Headlights 206 and taillights 207 are, for example, housed in first recess 136 and second recess 137 of driving unit 110. Headlights 206 and taillights 207 may also be located as part of driving unit 110 instead of as part of superstructure 200. These communication devices 201, HMI 202, seat assembly 203, collision sensor 204, airbag assembly 205, headlights 206, and taillights 207 are connected via power connector 209c of first superstructure 200A to power connector 121c of driving unit 110, receiving power from battery 120a of power module 120 of driving unit 110.

[0270] The body 210, communication device 201, HMI 202, seat device 203, collision sensor 204, airbag device 205, headlights 206, and taillights 207 are each provided as modules, for example. These modules can be configured in positions or combinations desired by the user. One or more of these modules can also be appropriately provided in the second to sixth upper units 200B to 200F shown below.

[0271] The control unit 208 controls the communication device 201, HMI 202, seat device 203, collision sensor 204, airbag device 205, headlight 206, taillight 207, and interface 209. The control unit 208 can be implemented by a processor such as a CPU executing a program (software) stored in memory, or by hardware such as an LSI, ASIC, FPGA, or GPU, or through a combination of software and hardware. The program can be pre-stored on storage devices such as HDDs and flash memory, or on removable storage media such as DVDs and CD-ROMs, and installed onto the storage device via the drive assembly.

[0272] Interface 209 may include, for example, a communication connector 209a, a gateway device 209b, a power supply connector 209c, and a regulator (power conversion device) 209d.

[0273] The communication connector 209a is an example of a "communication interface". The communication connector 209a is electrically connected to the gateway device 209b. When the first upper unit 200A is installed in the driving unit 110, the communication connector 209a can be physically and electrically connected to the communication connector 121a of the driving unit 110. That is, when the first upper unit 200A is installed in the driving unit 110, each device in the driving unit 110 shares a portion of the communication content of each device in the first upper unit 200A.

[0274] Gateway device 209b is an example of a "communication control unit". Gateway device 209b can communicate with gateway device 121b of driving unit 110 via communication connector 209a. Gateway device 209b performs comparison and authentication between superstructure 200 and driving unit 110 based on control of at least one of automatic driving control unit 115 and control unit 208 of superstructure 200 (e.g., comparison and authentication between gateway device 121b and gateway device 209b). Comparison and authentication include, for example, gateway device 209b authenticating that the vehicle 100 that sent the frame is a legitimate vehicle 100 by comparing the ID (sending ID) assigned to the frame sent from gateway device 121b with pre-stored information. For example, gateway device 209b detects the type of driving unit 110 connected to interface 209 through the above comparison and authentication. For example, gateway device 209b detects the category of driving unit 110 connected to interface 209 based on the ID (transmission ID) assigned to the frame sent from gateway device 121b.

[0275] The power supply connector 209c is electrically connected to various devices of the first upper unit 200A via the regulator 209d. The power supply connector 209c is exposed to the outside of the first upper unit 200A, allowing for physical and electrical connection to the power supply connector 121c of the driving unit 110.

[0276] The regulator 209d adjusts the power supplied from the travel unit 110 via the power supply connector 209c to the desired power supply (e.g., voltage) relative to the various devices of the first upper unit 200A. For example, based on the control of the control unit 208, the regulator 209d adjusts the power supplied from the travel unit 110 to power corresponding to the function and power consumption of the various devices of the first upper unit 200A, and supplies the adjusted power to the various devices of the first upper unit 200A. Either the regulator 121d of the travel unit 110 or the regulator 209d of the upper structure 200 may be omitted.

[0277] In this embodiment, the travel unit 110 can replace the first upper unit 200A by carrying one or more upper structures 200. Hereinafter, other examples of upper structures 200 installed in the travel unit 110 in place of the first upper unit 200A will be described. However, the shape and function of the upper structures 200 that can be installed in the travel unit 110 are not limited to the examples described below.

[0278] Figure 7 This is a perspective view showing a vehicle M including a second upper unit 200B, which is another example of an upper structure 200. The second upper unit 200B is a unit that enables the vehicle 100 to have functions substantially the same as a typical truck. For example, the second upper unit 200B has a body 210 having a cab 211 and a cargo box 213. The cargo box 213 is an example of a "cargo support section capable of supporting cargo". The other structures of the second upper unit 200B are substantially the same as those of the first upper unit 200A.

[0279] Figure 8 This is a perspective view of a vehicle M including a third upper unit 200C, which is another example of an upper structure 200. The third upper unit 200C is a unit that enables the vehicle 100 to have entertainment functions. For example, the third upper unit 200C does not have a room and is open above and on all four sides. The third upper unit 200C has a base 220 fixed to the vehicle unit 110 by a connecting mechanism 150 and multiple pads 221 mounted on the base 220. The third upper unit 200C can travel, for example, on private land or private roads. Users can enjoy flower viewing and sightseeing by using the third upper unit 200C.

[0280] Figure 9 and Figure 10 This is a perspective view showing a vehicle M including a fourth upper unit 200D, which is another example of an upper structure 200. The fourth upper unit 200D is a unit that becomes part of the building 230 (home, building, etc.). In other words, the vehicle 100 provides mobility to a part of the building 230 by connecting to it. By using the fourth upper unit 200D, users can move to other locations while living and working within the building 230.

[0281] For example, such as Figure 9 As shown, the fourth upper unit 200D is connected to the vehicle 100 and can move while mounted on the vehicle 100. On the other hand, as... Figure 10As shown, the fourth upper unit 200D and the vehicle 100 can be separated from each other. In this case, the vehicle 100 can leave the fourth upper unit 200D while leaving the fourth upper unit 200D in the building 230 and move there. From the state of leaving the fourth upper unit 200D, the vehicle 100 can move downwards from the fourth upper unit 200D and reconnect with the fourth upper unit 200D.

[0282] In this embodiment, the structure 230 includes a support structure 231 that supports the fourth upper unit 200D, which is placed in the structure 230, from at least one side and below when the vehicle 100 moves while the fourth upper unit 200D is placed in the structure 230. For example... Figure 9 As shown, the support structure 231 has, for example, a track 235 and a support portion 236.

[0283] Track 235 is provided on the side of structure 230. The fourth upper unit 200D has a locking member 161 supported by track 235 from the side and below. The fourth upper unit 200D is supported by track 235 by entering the inside of track 235 through locking member 161.

[0284] The support portion 236 is disposed in the region below the fourth upper unit 200D when the fourth upper unit 200D is connected to the building 230. When the vehicle 100 moves away from the fourth upper unit 200D while leaving the fourth upper unit 200D on the building 230, the support portion 236 replaces the vehicle 100 and supports the fourth upper unit 200D from below. For example, the support portion 236 is formed by a column or crane whose upper end, supporting the fourth upper unit 200D from below, is movable in the height direction. For example, when the vehicle 100 is below the fourth upper unit 200D, the support portion 236 is housed in a housing portion, for example, provided on the ground G, without contacting the vehicle 100. On the other hand, when the vehicle 100 moves while leaving the fourth upper unit 200D on the building 230, the support portion 236 moves upward in contact with the fourth upper unit 200D, supporting the fourth upper unit 200D from below.

[0285] Figure 11This is a perspective view of a vehicle M including a fifth upper unit 200E, which is another example of an upper structure 200. The fifth upper unit 200E is a unit that enables the vehicle 100 to function as a cargo transport device. The fifth upper unit 200E includes a base plate 240 fixed to the vehicle unit 110 by a connecting mechanism 150. The base plate 240 is another example of a "cargo support capable of supporting cargo". Multiple cargoes P are loaded on the base plate 240 and fixed to the base plate 240 by fixing members not shown. By using the fifth upper unit 200E, the user can transport more than one cargo P in a factory, collection yard, or other work site.

[0286] Figure 12 This is a perspective view of a vehicle M including a sixth upper unit 200F, which is another example of an upper structure 200. The sixth upper unit 200F is a unit that enables the vehicle 100 to function as a surrounding monitoring device. The sixth upper unit 200F includes a sensor unit 250 fixed to the vehicle unit 110. The sensor unit 250 includes a camera and a communication device capable of transmitting images or videos captured by the camera to a server or similar facility in a management center. The vehicle 100 can move along a designated path while the sensor unit 250 is installed. By using the sixth upper unit 200F, the user can conduct inspections (anomaly detection) of any location.

[0287] Based on the structure of the first embodiment described above, a vehicle 100 that can be used for multiple purposes can be provided. That is, in this embodiment, a vehicle 100 that can be installed on any superstructure 200 is provided. As a result, many operators can independently develop their own solutions, and a wide range of functions specifically designed for various purposes can be provided.

[0288] In the first embodiment, the driving unit 110 can customize the function of the vehicle 100 by interchangeably carrying multiple superstructures 200. With such a structure, for example, it can function as a passenger car or truck during the daytime, and during the nighttime (the sleep time under daytime use) it can function as a driving vehicle M for other purposes such as a transport platform with automatic driving function in a factory or the like.

[0289] [First Variation of the First Embodiment]

[0290] Next, a first variation of the first embodiment will be described. Figure 13 This is a perspective view showing a first variation of the first embodiment. (As shown) Figure 13 As shown, in this modified example, when one or more other vehicles 100 are loaded on top of one vehicle 100, the vehicle 100 located at the bottom can move.

[0291] In a first variation, the first upright portion 134 and the second upright portion 135 are inclined relative to the vertical direction, for example, in a manner that places them on the outer side of the vehicle width direction Y as they move upwards. Furthermore, among the plurality of vehicles 100 overlapping in the height direction, the first recess 136 and the second recess 137 of the travel unit 110 of the lowermost vehicle 100 receive at least a portion of the first base 131 and the second base 132 of the travel unit 110 of the vehicle above it. The lower surface of the protrusion 133 of each travel unit 110 forms a third recess 138 that is recessed upwards. Also, among the plurality of vehicles 100 overlapping in the height direction, at least a portion of the protrusion 133 of the travel unit 110 of the lowermost vehicle 100 is received in the third recess 138 formed by the protrusion 133 of the travel unit 110 of the vehicle above it.

[0292] As a result, the overlap thickness of multiple vehicles 100 is reduced.

[0293] From another perspective, the raised portion 133 of the lowermost vehicle 100's running unit 110 supports the previous vehicle 100 from below by contacting its running unit 110. The raised portion 133 is an example of a "support portion" supporting the running unit 110 of the previous vehicle 100. The inner surfaces (surfaces forming parts of the first recess 136 and the second recess 137) of the lowermost vehicle 100's running unit 110 support the previous vehicle 100 from below by contacting its running unit 110. The first and second raised portions 134 and 135 are each another example of a "support portion" supporting the running unit 110 of the previous vehicle 100.

[0294] Furthermore, the wheels W of the driving unit 110 of the lowest vehicle 100 are in contact with the ground G, and the driving unit 110 of the lowest vehicle 100 can travel while multiple vehicles 100 are mounted on top of it. For example, the driving unit 110 of the lowest vehicle 100 is electrically connected to the battery 120a of the driving unit 110 of the vehicles 100 mounted above it via a terminal 121 or the like. Thus, the driving unit 110 of the lowest vehicle 100 can travel using power supplied from the batteries 120a of one or more overlapping driving units 110 of other vehicles 100.

[0295] However, the structure for stacking multiple vehicles 100 is not limited to the examples described above. For example, the first erected portion 134 and the second erected portion 135 may also be erected in the vertical direction. The multiple vehicles 100 may also be simply stacked in the height direction.

[0296] [Second variation of the first embodiment]

[0297] Next, a second variation of the first embodiment will be described. Figure 14 This is a perspective view showing a second variation of the first embodiment. (As shown) Figure 14 As shown, in the second variation, the driving unit 110 of the vehicle 100 has a connecting portion 153 and a connecting portion 155. The driving unit 110 may also have only either the connecting portion 153 or the connecting portion 155.

[0298] One of the connecting parts 153 is a connecting part that connects to the travel unit 110 of another vehicle 100 that is parallel to the travel unit 110 in the vehicle width direction Y. By connecting to the travel unit 110 of another vehicle 100 through the connecting part 153, multiple vehicles 100 are mutually fixed. Thus, multiple vehicles 100 can travel as a unit. The connecting part 153 is an example of a "second connecting part". The travel unit 110 can be connected to the travel unit 110 of another vehicle 100 with one wheel W removed, or it can be connected to the travel unit 110 of another vehicle 100 without removing the wheel W.

[0299] The other connecting part 155 is a connecting part that connects to the travel unit 110 of another vehicle 100 that is parallel to the travel unit 110 in the vehicle travel direction X. Through the connection part 155 with the travel unit 110 of the other vehicle 100, multiple vehicles 100 are mutually fixed. Thus, multiple vehicles 100 can travel as a unit. The connecting part 155 is another example of a "second connecting part".

[0300] Based on the structures of the first and second modifications of the first embodiment described above, the superstructure 200, for example, has a size that is within the range of multiple interconnected vehicles 100. That is, by connecting multiple vehicles 100 via connecting parts 153 or 155, a superstructure 200 of a size that cannot be supported by a single vehicle 100 can be provided. This further increases the degree of freedom of the superstructure 200.

[0301] While the first embodiment and several variations thereof have been described above, the structure of the embodiments is not limited to the examples described above. For example, the vehicle 100 may also be constructed as follows: Figure 15The vehicle utilization system 1 shown is used. That is, the vehicle utilization system 1 includes one or more information processing devices 700 disposed externally on the vehicle 100. The information processing device 700, for example, has a communication unit 710 and an information processing unit 712 capable of communicating with the vehicle 100 and the user's terminal device 500 via a network NW. The information processing unit 712 may include some or all of the functional units included in the driving unit 110 of the vehicle 100 (e.g., navigation control device 113b, lane recommendation device 114, automatic driving control unit 115). The information processing unit 712 can be implemented by a processor such as a CPU executing a program (software) stored in memory, or it can be implemented by hardware such as an LSI, ASIC, FPGA, or GPU, or it can be implemented through a combination of software and hardware.

[0302] Furthermore, in the first embodiment described above, the vehicle 100 was described as being the same size as a typical passenger car or truck. However, the size of the vehicle 100 is not limited to the example described above. The size of the vehicle 100 could also be, for example, the size of a bed, or even smaller.

[0303] [Third variation of the first embodiment]

[0304] Next, a third variation of the first embodiment will be described. Figure 16 This is a structural diagram showing the first upper unit 200A and the driving unit 110 in a third modification of the first embodiment. As shown in the example, in addition to the driving control unit 202a described above, the HMI 202 of the first upper unit 200A in the third modification of the first embodiment also includes an external display unit 202b, a memory 202c, and a usage status detection unit 202e. Furthermore, the first upper unit 200A in the third modification of the first embodiment also includes a service provisioning device 212.

[0305] The external display unit 202b is, for example, an organic EL (ElectroLuminescence) display attached to the surface of the vehicle body on the outside of the vehicle 100. Alternatively, the external display unit 202b may be an LCD (Liquid Crystal Display) embedded in the vehicle body, or it may be a display panel that serves as part or all of the vehicle body. Furthermore, the external display unit 202b may be a movable display device equipped with a drive unit. In this case, the external display unit 202b is housed in a position where the display surface is not visible from outside the vehicle when not displaying items such as still images or moving images, and is moved by the drive unit to a position where the display surface is visible from outside the vehicle when items are to be displayed. Alternatively, the external display unit 202b may be a light-transmitting liquid crystal panel formed in at least a portion of the windshield, side windows, and rear window of the vehicle 100.

[0306] Figure 17 and Figure 18 This is a diagram showing an example of the external display unit 202b. (As shown...) Figure 17 , Figure 18 As illustrated, for example, the external display unit 202b displays trademarks and logos indicating the services provided via vehicle 100, information indicating the content of the services (in the illustrated example, an English conversation school), the destination of vehicle 100, and information on the service provision status (information indicating whether users outside the vehicle can board vehicle 100 and use the service), etc.

[0307] return Figure 16 As explained, the memory 202c is implemented using storage devices such as RAM, ROM, HDD, and flash memory. The memory 202c stores, for example, firmware (drivers) obtained from external devices (application servers, etc.). The firmware is the program (software) used to control various devices connected to the control unit 208 (hereinafter referred to as equipment), such as the communication device 201, HMI 202, seat device 203, collision sensor 204, airbag device 205, and service providing device 212. Firmware is an example of "control information for equipment." The firmware stored in the memory 202c can be updated periodically or irregularly. Additionally, identification information for each piece of equipment can be stored in the memory 202c.

[0308] The utilization status detection unit 202e detects the utilization status of each compartment of the vehicle 100 based on the user, the presence or absence of cargo, and its location. A compartment refers to the space within the upper structure 200 of the vehicle 100, which is a space where users can ride or carry cargo. The utilization status detection unit 202e can also detect the utilization status of the compartments based on the detection results of load sensors and in-vehicle cameras (neither shown).

[0309] Service providing device 212 is a machine installed by a service provider (service owner) that utilizes the interior and exterior of vehicle 100 for services. For example, service providing device 212 outputs images and conversational audio of a third party to provide the compartment of vehicle 100 as a place for the use of services such as an English conversation classroom, displays advertisements on external display unit 202b, or sends information to the terminal device (e.g., smartphone) of the user in the compartment.

[0310] The control unit 208 sends various information to the driving unit 110. For example, the control unit 208 controls the gateway device 209b to send information indicating the connection status of equipment connected to itself (control unit 208) to the gateway device 121b of the driving unit 110. The information indicating the connection status of the equipment may include, for example, the aforementioned firmware information, equipment identification information, etc. The gateway device 209b is an example of a "second communication interface".

[0311] The control unit 208 can also control the communication device 201 to send information indicating the connection status of the equipment to the communication device 112 of the driving unit 110. The communication device 201 is another example of a "second communication interface".

[0312] When the service provider 212 is wirelessly connected to the user's terminal device 500 via Wi-Fi (registered trademark), Bluetooth, or the like, the control unit 208 can also send information indicating the connection status of the equipment to the communication device 112 of the driving unit 110 via the terminal device 500 connected to the service provider 212. The terminal device 500 connected to the service provider 212 is another example of a "second communication interface".

[0313] When information indicating the connection status of equipment is transmitted to the driving unit 110 via wireless communication, an external server device may also exist between the first upper unit 200A and the driving unit 110. This server device replaces the gateway device 121b and gateway device 209b to perform the comparison and authentication performed between the gateway device 121b and gateway device 209b.

[0314] When the gateway device 121b or communication device 112 of the driving unit 110 receives information indicating the connection status of the equipment from the control unit 208, it outputs this information to the automatic driving control unit 115. The automatic driving control unit 115 may, for example, authenticate that the superstructure 200 is a legitimate superstructure 200 based on the information indicating the connection status of the equipment output by the gateway device 121b or communication device 112.

[0315] In the case where an external server device exists between the first upper unit 200A and the driving unit 110, the communication device 112 of the driving unit 110 can receive information indicating the results of the comparison and authentication performed by the server device. In this case, the automatic driving control unit 115 can authenticate that the upper structure 200 is a legitimate upper structure 200 based on the results of the comparison and authentication performed by the server device.

[0316] According to the structure of the third variation of the first embodiment described above, similar to the first embodiment, a vehicle 100 that can be used for multiple purposes can be provided. Therefore, it is possible to enable many operators to develop independently, and to provide a wide range and in-depth range of functions specifically tailored to various applications.

[0317] [Fourth variation of the first embodiment]

[0318] Next, a fourth variation of the first embodiment will be described. Figure 19 This is a structural diagram of a service provisioning system 2, which includes a vehicle 100 (autonomous vehicle 100), as a fourth variation of the first embodiment. The service provisioning system 2 includes one or more vehicles 100, multiple terminal devices 500, a service provider device 600, and a service management device 700. The multiple terminal devices 500 include a terminal device 500a used by the service provider S and a terminal device 500b used by the service applicant A. These components can communicate with each other via a network NW. The service provider S provides its service to the service user U. Although the service applicant A and the service user U are shown as different people in the diagram, they could be the same person. "Used by service applicant A" could include, for example, a terminal device in an internet cafe, which could be used by a non-specific number of users and is temporarily used by the service applicant A.

[0319] Figure 20 This is a diagram showing an example of the structure of the driving unit 110 according to the third embodiment. The automatic driving control unit 115 of the driving unit 110 according to the third embodiment includes a vehicle state sharing permission unit 115a.

[0320] The vehicle status sharing permission unit 115a allows information sharing of the driving unit 200A with respect to equipment connected to the first upper unit 200A or to a terminal device 500 connected to equipment (such as service provision device 212). This information is based on the identification information of equipment connected to the first upper unit 200A and firmware update information obtained from the service management device 700. For example, the identification information of the equipment can be obtained by receiving information stored in the memory 202c of the control unit 208 via the communication device 112 of the driving unit 110. Similarly, the firmware update information can be obtained by receiving information stored in the storage unit 800 of the service management device 700 via the communication device 112 of the driving unit 110. In addition, the vehicle status sharing permission unit 115a can also allow information sharing of the driving unit 200A relative to the first upper unit 200A or the terminal device 500 determined based on the identification information of the equipment connected to the first upper unit 200A and the firmware update information obtained from the service management device 700.

[0321] [Terminal Device]

[0322] Terminal device 500 is, for example, a smartphone, tablet, or personal computer. Terminal device 500 activates an application or browser, etc., to utilize service providing system 2, supporting the services described below. In the following description, it is assumed that terminal device 500 is a smartphone and the application (service applicant application) is running. The service user application communicates with service management device 700 based on the operation of service applicant A, sending requests from service applicant A to service management device 700, or sending push notifications based on information received from service management device 700. Service management device 700 is another form of the "information processing device" described in the first embodiment.

[0323] Terminal devices 500 (500a and 500b) send service utilization request information to service management device 700, for example, including the following: Location information, such as information determined by a GPS receiver built into terminal device 500. Other information is obtained based on information input by service requester A or service user U. Desired service provider attribute information refers to information related to the attributes of the service provider S desired by service user U. Attributes may include, in addition to the type of service provided, age, gender, personality (type), etc. Regarding attributes, service management device 700 may not assign a completely identical service provider S, but rather prompt the service user U to select or confirm.

[0324] [Service utilizes delegated information]

[0325] User ID

[0326] • Location information (latitude, longitude, altitude)

[0327] • We hope to utilize spatial information (e.g., the number of people, the number of seats, etc.).

[0328] • Hoping to utilize service provider attribute information

[0329] • Hope to utilize service ID

[0330] • We hope to utilize interval information

[0331] Information on the desired service usage time period for service users.

[0332] Settlement and authentication information

[0333] [vehicle]

[0334] The structure related to driving control of vehicle 100 (e.g., structure related to autonomous driving) in the fourth variation of the first embodiment is the same as the structure of vehicle 100 in the first embodiment and the first variation. That is, vehicle 100 is an autonomous driving vehicle, a vehicle with wireless communication capabilities as described below. Figure 21 This figure shows an example of the structure of a vehicle management device 300 mounted on a vehicle 100. The vehicle management device 300 is mounted, for example, on a first upper unit 200A. The vehicle management device 300 includes, for example, a communication unit 320, an authentication unit 330, an HMI 340, and a vehicle / compartment management unit 350.

[0335] Communication unit 320 is a wireless communication device. Communication unit 320 communicates with service management device 700 via network NW. Authentication unit 330 performs authentication processing for service initiation based on instructions from service management device 700.

[0336] The HMI340, for example, accepts input operations from equipment and outputs information from the equipment as images and sounds. For example, the HMI340 includes a touch panel display device, speakers, microphones, etc.

[0337] The vehicle / compartment management unit 350 includes, for example, a utilization status detection unit 352, a utilization permit unit 354, an authentication unit 356, and an external control permit unit 358. The vehicle 100 has one or more spaces (compartments) that can be used by service users U and service providers S. The utilization status detection unit 352 detects the utilization status of each compartment. For example, the utilization status detection unit 352 detects whether each compartment is currently in use. Figure 21The description of vehicle 100 includes a regular passenger car, but vehicle 100 can also be a trailer, bus, van, or other vehicle of a size that can accommodate more than one passenger in each of the compartments created by dividing the interior. The permission unit 354, for example, allows the use of a pre-designated compartment, such as unlocking the door, if the authentication unit 356 successfully authenticates the passenger. The authentication unit 356 performs authentication, such as verifying the identity of the service user U or service provider S who intends to board the vehicle.

[0338] The external control authorization unit 358 determines whether to allow control of the driving unit 110 corresponding to the user's operation of the equipment based on the identification information of each piece of equipment connected to the first upper unit 200A and the control information of the equipment obtained from the service management device 700. For example, sometimes, a user U riding in a compartment of the upper structure 200 operates the driving unit 110 via a terminal device 500 connected to the service providing device 212. In this case, the external control authorization unit 358 allows the user U to operate the driving unit 110 if the combination of the driving unit 110 to be operated by the user U, which is authenticated based on the identification information of each piece of equipment connected to the first upper unit 200A and the control information of the equipment obtained from the service management device 700, and the first upper unit 200A provided in the upper structure 200 where the user U is riding, is a normal combination.

[0339] The communication unit 320 of the vehicle management device 300 may, for example, send vehicle information, including the following, to the service management device 700.

[0340] [Vehicle Information]

[0341] • Identify the driving unit ID of driving unit 110

[0342] • Identify the upper unit ID of the upper unit 200A

[0343] • Location information (latitude, altitude, longitude)

[0344] • Cubicle utilization status (information on cubicles in use, user IDs of users using the services, and information on available cubicles, etc.)

[0345] • Driving status (speed, acceleration, angular velocity, status of onboard equipment, etc.)

[0346] • Information about service provider S (service provider ID, information about the services being implemented, service implementation time, etc.)

[0347] • Information related to equipment (equipment identification information, coded data obtained by encoding the equipment identification information, etc.)

[0348] Figure 22 This diagram illustrates an example of the structure of a service provider device 600. The service provider device 600 is, for example, a device capable of monitoring the status of multiple service providers and automatically responding to orders from a service management device 700. The service provider device 600 includes, for example, a communication unit 610, an order processing unit 620, a status management unit 630, and a storage unit 650.

[0349] The communication unit 610 communicates with the service management device 700 and other devices via the network NW. The order processing unit 620 processes service orders received from the service management device 700. The order processing unit 620 determines whether the content of the service order falls within the scope of service provision information already sent to the service management device 700, and proceeds with the order processing if it is determined to be within the scope. The status management unit 630 manages the status (appointment status, work status, etc.) of the service provider S registered with the service provider device 600, and provides service provision information to the service management device 700.

[0350] Service provider device 600 may send service provision information, for example, to service management device 700, including information related to services that service provider S is able to accept orders for.

[0351] [Service Provider Information]

[0352] • Authentication ID

[0353] • Control information for equipment (e.g., firmware update information, action requirements, information transmission requirements, etc.)

[0354] Service Name

[0355] • Control signals

[0356] [Service Management Device]

[0357] Figure 23This diagram illustrates an example of the structure of a service management device 700. The service management device 700 includes, for example, a communication unit 710, an acquisition unit 720, a service information input unit 730, a planning and decision unit 740, a route instruction unit 750, an authentication unit 760, a judgment unit 770, and a storage unit 800. The components other than the communication unit 710, the service information input unit 730, and the storage unit 800 are implemented by executing programs (software) using hardware processors such as CPUs. Some or all of these components can also be implemented by hardware (circuits; including circuitry) such as LSIs, ASICs, FPGAs, and GPUs, or through the coordinated operation of software and hardware. The program can be pre-stored in storage devices such as HDDs and flash memory, or stored in removable storage media such as DVDs and CD-ROMs, and installed by mounting the storage media onto a drive device. The storage unit 800 is implemented using HDDs, flash memory, RAM, ROM, etc.

[0358] The communication unit 710 includes, for example, a network card for connecting to the network NW. The communication unit 710 communicates with the vehicle management device 300, the terminal device 500, the service provider device 600, etc., via the network NW.

[0359] The acquisition unit 720 obtains service utilization request information from the terminal device 10 via the communication unit 710, obtains vehicle information from the vehicle management device 300 of the pre-registered vehicle 100, and obtains service provision information from the service provider device 600.

[0360] The service information input unit 730 receives input from the service provider S regarding the type and content of the services to be provided.

[0361] The planning and decision-making unit 740 determines the available services that service user U can enjoy based on available vehicle information 820 and service provision information, and provides information related to the determined available services to service user U's terminal device 500.

[0362] More specifically, the planning decision unit 740, based on the available vehicle information 820 and the desired usage range contained in the service provision information, sets a usage permission range in the driving path of the vehicle 100 in which the service provider S can occupy at least a portion (e.g., a compartment) of the vehicle 100.

[0363] The route instruction unit 750 instructs the vehicle 100 on the route it should travel by having the communication unit 710 send information about the start and end positions of the service user U and the service provider S to the vehicle 100.

[0364] The authentication department 760 performs authentication of the service user U based on communication with the terminal device 500, and performs authentication at the start of service provision.

[0365] The determination unit 770 determines whether the service user U and the service provider S are using vehicle 100.

[0366] The planning decision unit 740 performs various processes based on the determination result of the judgment unit 770. For example, the planning decision unit 740 may accept a change of desired usage area only if the judgment unit 770 determines that both service user U and service provider S are using vehicle 100. This could occur, for example, if service provider S proposes a change of destination to service user U or if the final destination is changed during service based on information provided to vehicle 100. Alternatively, the planning decision unit 740 may also prioritize allocating the vehicle 100 to service user U if the judgment unit 770 determines that service user U is already using vehicle 100 (i.e., if a service extension or other service request has been made during service usage) at the time the acquisition unit 720 receives the service usage request information.

[0367] For example, service management information including the following content is stored in storage unit 800.

[0368] [Service Management Information]

[0369] • Identify the user ID of service client A (service user U)

[0370] • Service ID that identifies the services provided by service provider S

[0371] • Driving unit ID and upper unit ID

[0372] Firmware ID of Upper Unit 200A

[0373] • Firmware ID of driving unit 110

[0374] • Encoded data from the vehicle side

[0375] Encoded data from service providers

[0376] • Current location information of vehicle 100

[0377] Service Provider ID

[0378] Figure 24This is a flowchart illustrating an example of the processing flow performed in service provision system 2. First, service commissioner A (service user U) uses terminal device 500 to authenticate with the authentication unit 760 of service management device 700 (step S200). When authentication by authentication unit 760 is successful, service commissioner A (service user U) uses terminal device 500 to send service utilization request information to service management device 700 (step S202). The service utilization request information is obtained by acquisition unit 720 and saved to storage unit 800 as service request management information 832.

[0379] After obtaining the service utilization request information, the acquisition unit 720 of the service management device 700 queries the service provider device 600 for service provision information (step S204). Multiple service provider devices 600 may exist depending on the attributes of the provided service or the service operator; in this case, the acquisition unit 720 may query multiple service provider devices 600 simultaneously. The status management unit 630 of the service provider device 600 replies to the service management device 700 with service provision information associated with the services that can accept orders (indicating the content of the services that can accept orders) (step S206).

[0380] On the other hand, the acquisition unit 720 of the service management device 700 queries the vehicle management device 300 for usage status (vehicle information) (step S208). The vehicle / compartment management unit 350 of the vehicle management device 300 replies to the service management device 700 with the usage status detected by the usage status detection unit 352 (step S210). It should be noted that the processing of steps S208 and S210 can also be performed asynchronously at any time as shown in the flowchart.

[0381] Next, the planning and decision unit 740 determines the available vehicles based on the service utilization request information and the information obtained in step S210, and generates available vehicle information (step S212). Multiple vehicles may be determined in step S212; in this case, the final vehicle determination may be performed until step S224, which will be described later. Then, the planning and decision unit 740 determines the available services that the service user can enjoy based on the available vehicle information and the service provision information that can accept orders obtained in step S206 (step S212), and sends available service information indicating the content of the determined available services to the terminal device 500 (step S214).

[0382] Service applicant A (service user U) reviews available service information, and as a result, uses terminal device 500 to order a service from service management device 700 (step S216). The planning and decision unit 740 of service management device 700 extracts the portion of the service accepted in step S216 that is undertaken by the service provider, and orders a service from service provider device 600 (step S218).

[0383] The order processing unit 620 of the service provider device 600 sends the intention to accept a service order to the service management device 700 (step S220). At the same time, the order processing unit 620 sends the order details to the service provider's terminal device (not shown in this embodiment).

[0384] When the service provider device 600 receives an order acceptance instruction, the route instruction unit 750 of the service management device 700 sets the route that the service delivery vehicle 100 should travel (step S222).

[0385] Next, the authentication unit 760 of the service management device 700 performs authentication processing for service initiation on the authentication unit 330 of the service provider device 600 and the vehicle 100. The route indication unit 750 indicates the route set in step S222 to the vehicle 100. The service provider device 600 performs service initiation authentication and determines the final vehicle as needed. The authentication unit 330 of the vehicle management device 300 of the vehicle 100 performs vehicle-side authentication and starts or plans to drive on the indicated route (step S224).

[0386] During the authentication process in S224, for example, the service provider device 600 obtains information about the equipment connected to the usable upper unit 200A. That is, the equipment information is sent from the vehicle 100 side to the service provider device 600 side. Here, authentication can be performed through two stages: the upper unit 200A and the equipment. If the owner of the upper unit 200A is different from the service provider, the functions of the vehicle status sharing license unit 115a of the driving unit 110 that can be performed by the upper unit 200A or the equipment connected to the upper unit 200A can also be separately specified by the owner or the operation manager.

[0387] Afterwards, the service user U rides in vehicle 100 (step S226), and when additional services are available, the planning decision unit 740 prompts the terminal device 500 for additional services (step S228).

[0388] When service user U is riding in vehicle 100 (S226), the service provider can set whether or not the equipment in the vehicle 100 can be used. In this case, the vehicle status sharing permission unit 115a allows the setting information regarding the use permission of the equipment to be shared with the service management device 700. It should be noted that the setting regarding the use permission of the equipment can also be performed by the service management device 700. The equipment includes, for example, a video playback device and a power supply device installed in the compartment. When the use of the equipment is permitted, the passenger riding in vehicle 100 can operate or use the equipment. At this time, the driving status of vehicle 100, the operation information or usage information of the equipment, etc., can also be shared with the service provider device 600 with the permission of the vehicle status sharing permission unit 115a.

[0389] When a service user views the content of an additional service and subscribes to it using terminal device 500 (step S230), the planning and decision unit 740 of the service management device 700 subscribes to the service provider device 600 for the additional service (step S232). The order processing unit 620 of the service provider device 600 sends a message indicating acceptance of the additional service subscription to the service management device 700 (step S234).

[0390] In the processing of S234, for example, when a passenger orders a service via equipment (e.g., when a specific video item is played using the equipment), the order processing unit 620 of the service provider device 600 simultaneously resets the route and destination suitable for the service and instructs the vehicle 100. More specifically, the functional units such as the order processing unit 620 of the service provider device 600, in accordance with the content of items such as sightseeing guides, correct the route by passing through the routes set by the service provider device 600 or adjust the passing speed according to the indicated time. In this case, any functional unit of the service provider device 600 provided in the upper unit 200A is an example of an "external control authorization unit". As a result, the services provided by the service provider can be associated with the equipment arbitrarily configured in the vehicle 100 and the control state of the vehicle 100, which can improve the freedom of the service provider to configure equipment linked to driving.

[0391] When a message indicating acceptance of an order for additional services is received, the route instruction unit 750 of the service management device 700 instructs the vehicle 100 to modify the route or change the destination (step S236).

[0392] According to the structure of the fourth variation of the first embodiment described above, similar to the first embodiment or the first variation, a vehicle 100 that can be used for multiple purposes can be provided. Therefore, it is possible to enable many operators to develop independently, and to provide a wide range and in-depth range of functions tailored to specific applications.

[0393] <Second Implementation Method>

[0394] Next, the second embodiment will be described. The second embodiment includes, for example, a service management device, service provisioning system, service management method, and procedure applicable to the autonomous vehicle of the first embodiment. The service management device manages services provided by a service user riding in a moving vehicle with a service provider. This service can primarily refer to the ride itself, or it can refer to riding in the vehicle and performing certain actions. Examples of the former include services where service providers such as childcare workers, caregivers, and nurses ride in the vehicle with service users who are not preferred to ride alone (e.g., infants, the elderly, patients, and people with disabilities). It should be noted that even when referring to the ride itself, it can include ancillary services such as the service provider caring for an infant who is the service user.

[0395] The services described as a second embodiment are applied for, for example, through electronically transmitted and transmitted ride requests. The person sending the above request (the service applicant) can be the service user themselves or someone else (family members, etc.). In addition, the vehicle used in this service is, for example, an autonomous vehicle that requires virtually no driving operation. Hereinafter, we will assume the use of an autonomous vehicle, but a manually driven vehicle may also be used.

[0396] The second embodiment will now be described. In the second embodiment, the service mainly refers to sharing the ride, assuming that the service provider is required to share the ride throughout the entire distance the service user travels in the vehicle.

[0397] [Overall Structure]

[0398] Figure 25This is a structural diagram of a service provision system a1, including a service management device a300. Service provision system 1 includes one or more terminal devices a100 used by one or more service applicants A, one or more terminal devices a150 used by one or more service providers, one or more vehicles a200, and a service management device a300. These components can communicate with each other via a network NW. The network NW includes the Internet, WAN, LAN, public lines, carrier equipment, dedicated lines, wireless base stations, etc. Service provider S provides services to service user U. In the diagram, service applicant A and service user U are shown as different individuals, but they can also be the same person. It should be noted that "used by service applicant A or service provider S" can also include terminal devices such as those in internet cafes that can be used by a non-specific number of people temporarily by service applicant A or service provider S.

[0399] [Terminal Device]

[0400] Terminal device a100 may be, for example, a smartphone, tablet, or personal computer. Terminal device a100 is used to launch applications or browsers from service providing system a1, supporting the services described below. In the following description, it is assumed that terminal device a100 is a smartphone and the application (service applicant application) is running. The service user application communicates with service management device a300 based on the actions of service applicant A, sending requests from service applicant A to service management device a300, or sending push notifications based on information received from service management device a300.

[0401] Terminal device a150 is similar to terminal device a100, and may be, for example, a smartphone, tablet, or personal computer. Terminal device a150 supports the services described below for launching applications or browsers used to participate in service provisioning system a1. The following description assumes that terminal device a150 is a smartphone and the application (service provider application) is running. The service provider application communicates with service management device a300 based on the operations of service provider S, sending acceptance information from service provider S to service management device a300, or sending push notifications based on information received from service management device a300.

[0402] [vehicle]

[0403] Vehicle A200 is a vehicle that has at least a cabin. Figure 26This is a structural diagram of vehicle a200. Vehicle a200 includes, for example, an external monitoring unit a210, a communication device a220, a navigation device a230, a lane recommendation device a240, an automatic driving control unit a250, a drive force output device a260, a braking device a262, and a steering device a264.

[0404] The external monitoring unit a210 includes, for example, cameras, radar, LIDAR (Light Detection and Range), and object recognition devices that perform sensor fusion processing based on their outputs. The external monitoring unit a210 estimates the types of objects present in the vicinity of the vehicle a200 (especially vehicles, pedestrians, and bicycles) and outputs them, along with their position and speed information, to the automatic driving control unit a250.

[0405] Communication device a220 is, for example, a wireless communication module used for connecting to a network NW or for direct communication with other vehicle, pedestrian, or other terminal devices. Communication device a220 performs wireless communication based on Wi-Fi, DSRC (Dedicated Short Range Communications), Bluetooth (registered trademark), or other communication standards. Multiple devices corresponding to different applications can also be prepared as communication device a220.

[0406] The navigation device a230 includes, for example, an HMI (Human Machine Interface) a232, a GNSS (Global Navigation Satellite System) receiver a234, and a navigation control device a236. The HMI a232 includes, for example, a touch panel display, a speaker, and a microphone. The HMI a232 outputs images and sound, and receives input from passengers. For example, the HMI a232 displays the route to the destination visually, and displays or outputs information to urge passengers to operate the vehicle a200.

[0407] GNSS receiver a234 determines its own position (the position of vehicle a200) based on radio waves from GNSS satellites (e.g., GPS satellites). Navigation control device a236, for example, includes a CPU (Central Processing Unit) and various storage devices, and controls the entire navigation device a230. Map information (navigation map) is stored in the storage devices. The navigation map is a map that uses nodes and lines to represent roads. Navigation control device a236 refers to the navigation map to determine the path from the position of vehicle a200 determined by GNSS receiver a234 to the destination specified using HMI a232. Alternatively, navigation control device a236 can also use communication device a220 to send the position of vehicle a200 and destination to a navigation server (not shown), and obtain the path from the navigation server. In this embodiment, the path to the destination is sometimes specified by service management device a300. It should be noted that the path may also include information on stops for the user to board or disembark and the arrival time at the destination. The navigation control device a236 outputs the information of the path determined by any of the above methods to the lane recommendation device a240.

[0408] The lane recommendation device a240 includes, for example, an MPU (Micro Processing Unit) and various storage devices. The storage devices hold high-precision map information more detailed than the navigation map. This high-precision map information includes, for example, information such as the road width, slope, curvature, and signal location for each lane. The lane recommendation device a240 determines the preferred lane for driving along the path input from the navigation device a230 and outputs it to the automatic driving control unit a250.

[0409] The autonomous driving control unit a250 has one or more processors, such as a CPU and an MPU, and various storage devices. The autonomous driving control unit a250 drives the vehicle a200 automatically, based on the principle of driving in the recommended lane determined by the recommended lane determination device a240, and avoiding contact with objects whose position and speed have been input from the external monitoring unit a210. The autonomous driving control unit a250 executes various events sequentially, such as constant speed driving in the same driving lane, following driving events, lane changing events, merging events, branching events, emergency stop events, toll gate events for passing through toll gates, and handover events for ending autonomous driving and switching to manual driving. Furthermore, during the execution of these events, evasive actions are sometimes planned based on the surrounding conditions of the vehicle a200 (the presence of surrounding vehicles and pedestrians, lane narrowing caused by road construction, etc.).

[0410] The automatic driving control unit a250 generates a target trajectory for the future travel of vehicle a200. The target trajectory includes, for example, speed elements. For instance, the target trajectory is represented by a sequence of locations (track points) that vehicle M should reach. Track points are locations that vehicle M should reach at predetermined travel distances. Independently, target speeds and target accelerations are generated as part of the target trajectory at predetermined sampling times (e.g., a fraction of a second). Alternatively, track points can also be positions that vehicle M should reach at that sampling time at predetermined sampling times. In this case, the target speed and target acceleration information are represented by the intervals of the track points.

[0411] The processing procedure for autonomous driving is described in the first embodiment. Figure 3 And related explanations, detailed explanations omitted. It should be noted that the drive force output device a260 has the same function as the drive force output device a116 mentioned above, the braking device a262 has the same function as the braking device a117 mentioned above, and the steering device a264 has the same function as the steering device a118.

[0412] The drive force output device a260 outputs the driving force (torque) used to propel the vehicle to the drive wheels. The drive force output device a260 may include, for example, a combination of an internal combustion engine, an electric motor, and a transmission, and a power ECU that controls them. The power ECU controls the aforementioned structure according to information input from the automatic driving control unit a250 or information input from a driving control device not shown.

[0413] Braking device a262 includes, for example, a brake caliper, a hydraulic cylinder that transmits hydraulic pressure to the brake caliper, an electric motor that generates hydraulic pressure in the hydraulic cylinder, and a braking ECU. The braking ECU controls the electric motor according to information input from the automatic driving control unit a250 or from the driving controls, so that braking torque corresponding to the braking operation is output to each wheel. Braking device a262 may also include, as a backup, a mechanism for transmitting hydraulic pressure generated by the operation of the brake pedal included in the driving controls via a master hydraulic cylinder to another hydraulic cylinder. It should be noted that braking device a262 is not limited to the structure described above; it may also be an electronically controlled hydraulic braking device that controls an actuator according to information input from the automatic driving control unit a250 to transmit hydraulic pressure from the master hydraulic cylinder to another hydraulic cylinder.

[0414] The steering system a264 includes, for example, a steering ECU and an electric motor. The electric motor, for example, applies force to a rack and pinion mechanism to change the direction of the steering wheels. The steering ECU drives the electric motor according to information input from the automatic driving control unit a250 or from the driving controls, thereby changing the direction of the steering wheels.

[0415] [Service Management Device]

[0416] return Figure 25 The service management device a300 includes, for example, a communication unit a310, an acquisition unit a320, a planning and decision unit a333, a path indication unit a340, and a storage unit a380.

[0417] The communication unit a310 is, for example, a network card used for connecting to the network NW. The storage unit a380 is implemented using an HDD, flash memory, RAM, ROM, etc. The communication unit 310 communicates with terminal devices a100 and a150 and vehicle a200 via the network NW.

[0418] The acquisition unit a320, the planning and decision-making unit a330, and the route instruction unit a340 are implemented, for example, by a processor such as a CPU executing a program (software) stored in the storage unit a380. Alternatively, some or all of these functional units can also be implemented by hardware such as LSIs, ASICs, or FPGAs, or through the coordinated use of software and hardware.

[0419] The acquisition unit a320 obtains a ride-sharing request from the terminal device a100 of service applicant A via the communication unit a310 and the network NW, and registers it in the storage unit a380 as a ride-sharing request list a384. Additionally, the acquisition unit a320 obtains a service availability notification from the terminal device a150 of service provider S via the communication unit a310 and the network NW, and registers it in the storage unit a380 as service availability information a386. It should be noted that the user information a382 includes personal information of service applicant A, service user U, and service provider S.

[0420] Figure 27 This diagram illustrates an example of the contents of a ride-sharing request list a384. As shown, the ride-sharing request list a384 establishes a correspondence between the applicant ID (identifying the pre-registered service applicant A), the number of service users, the desired pick-up location, the destination, the desired pick-up time, and a "plan decided" flag indicating whether the plan has been completed (e.g., 1 indicates the plan has been completed, 0 indicates the plan has not been decided). Information other than the "plan decided" flag is determined by the service applicant A's input via the service application on terminal device a100 and sent as a ride-sharing request to service management device a300. The distance from the desired pick-up location to the destination is an example of a "first pick-up interval." Hereinafter, the series of information in the ride-sharing request list a384 that corresponds to a user ID is sometimes referred to as a record. It should be noted that ride-sharing requests do not need to be made with each use; multiple ride-sharing requests can be made together. For example, a request can be made to request ride-sharing service from the desired pick-up location to the destination at a predetermined time on a weekday.

[0421] Figure 28 This is a diagram illustrating an example of the content of service availability information a386. As shown, service availability information a386 is information that establishes a correspondence between the service provider ID, which is the identification information of the pre-registered service provider S, and the service availability date, service availability time period, service availability area, etc.

[0422] The planning decision unit a330 determines the ride-sharing plan for service user U and service provider S based on the ride-sharing requests registered in the ride-sharing request list a384. In the second embodiment, the planning decision unit a330 determines the method in which the service provider S takes the vehicle a200 (the second travel section) to include the section from the desired travel section to the destination in the ride-sharing request.

[0423] Figure 29 This is a diagram (Figure 1) illustrating the scenario of deciding on a ride-sharing plan. The ride-sharing plan is set when conditions are met, such as both the desired pick-up location and the destination being within the service availability area, and the period after adding the expected driving time to the desired pick-up time being within the service availability time period. At the desired pick-up location of service user U, service provider S has already boarded vehicle a200. After dropping off service user U at the destination, vehicle a200 proceeds to the desired location. A nursery or similar facility exists at the destination.

[0424] Figure 30 It shows a reflection Figure 29 The diagram shows an example of the operation schedule information a388 of the ride-sharing plan. As shown, service provider S with service provider ID "A" boards the vehicle at parking location (1), and service user U, corresponding to service applicant with application ID "0001", boards the vehicle at parking location (2), which is the desired pick-up location. Service user U gets off at parking location (3), which is the destination, and goes to the nursery. Then, the vehicle a200 carrying service provider S moves to the place where service user U is waiting for the next service, or takes service provider S to their home.

[0425] Here, it could also be a service provider S sharing a ride with multiple service users U. In this case, the ride-sharing plan would be as follows: Figure 31 As shown, the schedule information a388 is executed as indicated. Figure 32 The decision was made as shown. Figure 31 This is a diagram (Figure 2) illustrating the situation where the carpooling plan is decided. Figure 32 It shows a reflection Figure 31The diagram illustrates an example of the content of the schedule information a388 for a ride-sharing plan. In the illustrated example, for vehicle a200 in the state of service provider S's ride, firstly, service user U(1) corresponding to service applicant A with applicant ID "0001" rides, and service user U(2) corresponding to service applicant A with applicant ID "0002" rides. Service users U(1) and U(2) get off at the same destination. Thus, the planning decision unit a330 can also determine the ride-sharing plan in a way that allows one service provider S to ride with multiple service users U, even if the interval in which service provider S rides in vehicle a200 includes the interval from the desired pick-up location of multiple users U to their destination.

[0426] Figure 33 This is a flowchart illustrating an example of the processing flow performed by the service management device a300. First, the service management device a300 determines whether a ride-sharing request has been received from the terminal device a100 (step S100a). When a ride-sharing request is received from the terminal device a100, the service management device a300 appends the content contained in the ride-sharing request to the ride-sharing request list 384 (step S102a).

[0427] Next, the service management device a300 determines whether the time for deciding the ride-sharing plan has arrived (step S104a). If the time for deciding the ride-sharing plan has not arrived, the process returns to step S100a. The time for deciding the ride-sharing plan can be arbitrarily determined, but for example, it can be determined to arrive at predetermined intervals (e.g., approximately every 10 minutes) during the operating hours of the service provision system 1.

[0428] When the time comes for a ride-sharing plan to be decided, the service management device a300 retrieves the record with the plan decided flag set to 0 from the ride-sharing request overview a384 (step S106a). Next, the service management device a300 refers to the service availability information 386 and retrieves the service provider S that can provide ride-sharing services according to the ride-sharing request (step S108a).

[0429] Next, the service management device a300 determines whether there is a service provider S that can share a ride under the condition of a ride request (step S110a). If there is a service provider S that can share a ride under the condition of a ride request, the service management device a300 determines the ride plan for the service user U corresponding to the record extracted in step S106a and appends it to the operation schedule information a388 (step S112a). At this time, the service management device a300 changes the plan determined flag in the extracted record to 1.

[0430] On the other hand, if there is no service provider S that can provide a ride according to the ride request, the service management device a300 determines whether there is a service provider S that can provide a ride if the conditions of the ride request are changed within a certain range (step S114a). Here, a certain range means, for example, tens of hours in terms of time, and for example, hundreds of meters in terms of location.

[0431] If an affirmative determination is obtained in step S114a, the service management device a300 causes the communication unit a310 to send a message to the terminal device a100 asking whether the content of the ride-sharing request can be changed (step S116a). Upon receiving this message, the terminal device a100 displays a screen asking whether the content of the ride-sharing request can be changed. Figure 34 This diagram illustrates an example of an IM screen that asks whether the details of a ride request can be changed. The IM screen displays the intention that the desired time of travel is unavailable and information about the alternative arrival time. It also includes buttons for agreeing to the time change instruction and a "no" button. When the user presses either button, the service application on terminal device a100 sends information indicating the operation to service management device a300. It should be noted that the same applies to changes in location.

[0432] return Figure 33 The service management device a300 determines whether the service applicant A has agreed to the change based on the content received from the terminal device a100 (step S118a). The service management device a300 determines that the consent has been obtained if the button on the terminal device a100 is operated, and determines that the consent has not been obtained if the button is not operated.

[0433] If the change is approved, the service management device a300 determines the ride-sharing plan for the service user U corresponding to the record extracted in step S106 based on the modified content, and appends it to the schedule information a388 (step S112a). At this time, the service management device a300 changes the plan-determined flag in the extracted record to 1. On the other hand, if the change is not approved or if a negative determination is made in step S114, the service management device a300 controls the communication unit a310 to send a notification (non-notification) to the terminal device a100 indicating that the ride-sharing request cannot be responded to (step S120a). At this time, the service management device a300 can delete the extracted record or search again at the next ride-sharing plan determination time.

[0434] After completing steps S110a to S120a, the service management device a300 determines whether records corresponding to all service requesters A have been retrieved (step S122a). If no records corresponding to all service requesters A have been retrieved, the process returns to step S106a. If records corresponding to all service requesters A have been retrieved, the route instruction unit a340 of the service management device a300 sends the operation schedule added or updated in this process to the vehicle a200 (step S124a). It should be noted that when using a manually driven vehicle, the service management device a300 notifies the driver's terminal device or the vehicle terminal device of the change request for the ride request.

[0435] According to the first embodiment described above, services provided by service providers within a vehicle can be appropriately managed.

[0436] [First variation of the second embodiment]

[0437] The first variation of the second embodiment will be described below. Regarding the structural diagram and the basic functions of each device, reference will be made to… Figures 25-28 And related explanations. In the first variation of the second embodiment, "service" refers to a service performed on the basis of riding in the vehicle. For example, any service provided by a service provider S within the vehicle a200, such as foreign language education, hairdressing, massage, or assistance with legal procedures.

[0438] Therefore, in the first variation of the second embodiment, the service provider S does not need to ride in the same vehicle for the entire distance during which the service user U rides. Furthermore, the scenario where the service user U becomes the service requester A is primarily envisioned. The planning and decision unit a330 of the second embodiment determines the distance (second travel interval) during which the service provider S travels to the vehicle a200 within the range specified by the service availability information a386.

[0439] Figure 35 This diagram illustrates the scenario of determining a ride-sharing plan in a first variation of the second embodiment. As shown, service provider S can board vehicle a200 while service user U is already in the vehicle. Service user U may be using vehicle a200 to receive foreign language education from service provider S and go to work, for example. Figure 36 It shows a reflection Figure 35 The diagram shows an example of the content of the ride-sharing plan's schedule information a388.

[0440] According to the first variation of the second embodiment described above, services provided by a service provider within a vehicle can be appropriately managed.

[0441] [Second Variation of the Second Embodiment]

[0442] The following describes a second variation of the second embodiment. Regarding the structural diagram and the basic functions of each device, references are made to... Figures 25-28 And related explanations. In a second variation of the second embodiment, the service does not end within the vehicle a200, but continues at the facility where the service user U disembarks. Hereinafter, the service performed during the ride will be referred to as the ride service, and the service provided after disembarking will be referred to as the post-disembarkation service. In the third embodiment, the destination in the ride request is set as the location for receiving the post-disembarkation service. The service provider S providing the ride service and the service provider S# providing the post-disembarkation service can be the same person or different people. In the former case, the planning decision unit a330 decides the ride plan for service provider S to disembark with service user U at the destination. Hereinafter, this will be the premise.

[0443] The services offered include assistance with procedures when purchasing land. In this case, services such as "explanation of the procedures by service provider S inside vehicle a200, and a convenient stop at the real estate office for signing and stamping after disembarking" are provided. The planning and decision-making department a330 can also automatically make online reservations if service provider S requires a reservation at the facility used at the destination.

[0444] Figure 37 This diagram illustrates the scenario of deciding on a ride-sharing plan in a second variation of the second embodiment. Service user U and service provider S ride together and complete the necessary procedures, then proceed to the real estate agency, their destination, and disembark together. At the real estate agency, they then complete procedures such as signing and stamping. Figure 38 It shows a reflection Figure 37 The diagram shows an example of the content of the ride-sharing plan's schedule information a388.

[0445] According to the second variation of the second embodiment described above, services provided inside the vehicle and after getting off the vehicle can be appropriately managed.

[0446] [Third variation of the second embodiment]

[0447] The third variation of the second embodiment will now be described. Regarding the structural diagram and the basic functions of each device, reference will be made to… Figures 25-28 And related explanations. In a third variation of the second embodiment, the service management device a300 manages multiple services. Furthermore, the service user U (or service requester A) can select and accept the desired service from among the multiple services.

[0448] Figure 39This diagram illustrates an example of the contents of the ride request overview a384A in the third variation of the second embodiment. The third variation of the second embodiment adds service types and the need for post-disembarkation services to the ride requests. The need for post-disembarkation services can also be automatically added in the service management device a300 after the service type is specified. It should be noted that the need for service types and post-disembarkation services may not be specified with each ride request, but rather automatically determined by the service requester A if they have made an agreement to request only a specific service type.

[0449] Figure 40 This diagram illustrates an example of the service provision range information a386A in a third variation of the second embodiment. In this third variation of the second embodiment, the service provider S pre-declares the types of services it can provide. The service management device a300 accepts this declaration and registers it in the service provision range information a386A.

[0450] The planning and decision-making unit a330 of the third variation of the second embodiment executes the plan for each service type. Figure 33 The following steps, S104a, are equivalent to the processing. Thus, it is possible to assign the service provider S to the service user U according to each type of service.

[0451] According to the third variation of the second embodiment described above, various services can be selectively provided.

[0452] Control of Autonomous Vehicles

[0453] In the various modifications of the second embodiment described above (especially in the first to third modifications), the vehicle a200 can also perform driving control that adjusts the time required to reach the destination in accordance with the time predetermined for service provision. For example, the ride request includes information about the desired service provision time, and the schedule sent from the route instruction unit a340 to the vehicle a200 includes the predetermined service provision time.

[0454] Figure 41 This diagram schematically illustrates the driving control performed by vehicle a200. For example, when the vehicle a200 reaches a reference point, such as an intermediate point leading to the destination, its automatic driving control unit a250 compares the elapsed time up to that point with a predetermined time. Furthermore, if the elapsed time is shorter than the estimated time elapsed to reach the reference point, the system slows down the remaining journey or stops at designated locations, thus delaying arrival at the destination. This ensures sufficient service delivery time.

[0455] [Fourth variation of the second embodiment]

[0456] The fourth variation of the second embodiment will be described below. Figure 42 This is a structural diagram of a service provisioning system a2, which includes a service management device a700 according to the fourth variation of the second embodiment. The service provisioning system a2 includes one or more terminal devices 100 used by one or more service applicants A, one or more vehicles a500, one or more terminal devices a150 used by one or more service providers S, a service provider device a600, and a service management device a700. These components can communicate with each other via a network NW. The service provider S provides services to the service user U. In the diagram, service applicant A and service user U are shown as different people, but they could also be the same person. It should be noted that "used by service applicant A" can include terminal devices such as those in internet cafes that can be used by a non-specific number of people, and are temporarily used by service applicant A.

[0457] [Terminal Device]

[0458] The hardware and basic functions of the terminal device a100 are the same as in the second embodiment. The terminal device a100 is used to launch applications or browsers from the service providing system a2, supporting the services described below. In the following description, it is assumed that the terminal device a100 is a smartphone and the application (service applicant application) is running. The service user application communicates with the service management device a700 based on the operation of the service applicant A, sending requests from the service applicant A to the service management device a700, or sending push notifications based on information received from the service management device a700.

[0459] Terminal device a100 sends service request information, for example, to service management device a700, including the following: Location information, for example, information determined by a GPS receiver built into terminal device a100. Other information is obtained based on information input by service requester A or service user U. Desired service provider attribute information is information related to the attributes of the service provider S desired by service user U. Attributes may include, in addition to the type of service provided, age, gender, personality (type), etc. Regarding attributes, service management device a700 may not assign a fixed, identical service provider S, but rather prompt service user U to select or confirm.

[0460] [Service utilizes delegated information]

[0461] User ID

[0462] • Location information (latitude, longitude, altitude)

[0463] • We hope to utilize spatial information (e.g., the number of people, the number of seats, etc.).

[0464] • Hoping to utilize service provider attribute information

[0465] • Hope to utilize service ID

[0466] • We hope to utilize interval information (information from the first interval).

[0467] Information on the desired service usage time period for service users.

[0468] Settlement and authentication information

[0469] [vehicle]

[0470] The structures related to the driving control of vehicle a500 (e.g., structures related to autonomous driving) are the same as those of vehicle a200 in the second embodiment. That is, vehicle a500 is an autonomous driving vehicle, and as described below, it is a vehicle with wireless communication capabilities. Figure 43 This figure shows an example of the structure of a vehicle management device a510 mounted on a vehicle a500. The vehicle management device a510 includes, for example, a communication unit a520, an authentication unit a530, and a vehicle / compartment management unit a550.

[0471] Communication unit a520 is a wireless communication device. Communication unit a520 communicates with service management unit a700 via network NW. Authentication unit a530 performs authentication processing for service initiation based on instructions from service management unit a700.

[0472] The vehicle / compartment management device a550 includes, for example, a usage status detection unit a552, a usage permit unit a554, and an authentication unit a556. A vehicle a500 has one or more spaces (compartments) that can be used by service users U and service providers S. The usage status detection unit a552 detects the usage status of each compartment. For example, the usage status detection unit a552 detects whether each compartment is currently in use. Figure 43 The description of vehicle a500 includes ordinary passenger cars, but vehicle a500 can also be a trailer, bus, van, or other vehicle of a size that can accommodate more than one passenger in each of the divided compartments of the interior. The Permit Department a554, for example, allows the use of a pre-designated compartment, such as unlocking the door, upon successful authentication by the Certification Department a556. The Certification Department a556 performs authentication, such as verifying the identity of the service user U or service provider S who intends to board the vehicle.

[0473] The vehicle management device a510, for example, sends vehicle information, including the following, to the service management device a700.

[0474] [Vehicle Information]

[0475] Vehicle ID

[0476] • Location information (latitude, altitude, longitude)

[0477] • Cubicle utilization status (information on cubicles in use, user IDs of service users currently using the service, and available cubicle information, etc.)

[0478] • Driving status (speed, acceleration, angular velocity, status of onboard equipment, etc.)

[0479] • Information about service provider S (service provider ID, information about the services being implemented, service implementation time, etc.)

[0480] Figure 44 This diagram illustrates an example of the structure of a service provider device a600. The service provider device a600 is, for example, a device capable of monitoring the status of multiple service providers and automatically responding to orders from a service management device a700. The service provider device a600 includes, for example, a communication unit a610, an order processing unit a620, a status management unit a630, and a storage unit a650.

[0481] The communication unit a610 communicates with the service management device a700 and others via the network NW. The order processing unit a620 processes service orders from the service management device a700. The order processing unit a620 determines whether the content of the service order falls within the scope of the service provision information already sent to the service management device a700, and proceeds with the order processing if it is determined to be within the scope. The status management unit a630 manages the status (appointment status, work status, etc.) of the service provider S registered with the service provider device a600, and provides service provision information to the service management device a700.

[0482] Service provider device a600 may, for example, send service provision information, including the following: The service provision information is information associated with the services that service provider S is able to accept.

[0483] [Service Provider Information]

[0484] · Order ID

[0485] Service Name

[0486] Information on those responsible for implementation

[0487] Service provider attribute information

[0488] • Information regarding the time period for which the service provider desires the service.

[0489] • Necessary vehicle compartment information

[0490] Information on the regions where services are available

[0491] • Facility location information (service provision location information outside of vehicles)

[0492] Service Status

[0493] [Service Management Device]

[0494] Figure 45 This diagram illustrates an example of the structure of a service management device a700. The service management device a700 includes, for example, a communication unit a710, a first acquisition unit a720, a second acquisition unit a722, a third acquisition unit a724, a vehicle determination unit a730, a planning decision unit a740, a route instruction unit a750, an authentication unit a760, a judgment unit a770, and a storage unit a800. The components other than the communication unit a710 and the storage unit a800 are implemented by executing programs (software) using hardware processors such as CPUs. Some or all of these components can also be implemented by hardware (circuit unit; including circuitry) such as LSIs, ASICs, FPGAs, and GPUs, or through the cooperation of software and hardware. The program can be pre-stored in storage devices such as HDDs and flash memory, or stored in removable storage media such as DVDs and CD-ROMs, and installed by mounting the storage media to a drive device. The storage unit 800 is implemented using HDDs, flash memory, RAM, ROM, etc.

[0495] The communication unit a710 is, for example, a network card used for connecting to the network NW. The communication unit a710 communicates with the terminal device a100, the vehicle management device a510, the service provider device a600, etc. via the network NW.

[0496] The first acquisition unit a720 obtains service utilization request information from the terminal device a100 via the communication unit a710. The second acquisition unit a722 obtains vehicle information from the vehicle management device a510 of the pre-registered vehicle a500 via the communication unit a710. The third acquisition unit a724 obtains service provision information from the service provider terminal a600 via the communication unit a710.

[0497] The vehicle determination unit a730 determines the usable vehicle a500 based on the service utilization request information and vehicle information, and generates usable vehicle information a820. Specifically, the vehicle determination unit a730 compares the desired space information, desired interval information, and service utilization time period information contained in the service utilization request information with the location information and compartment utilization status contained in the vehicle information, and determines the vehicle a500 that meets the conditions contained in the service utilization request information in terms of location information and compartment utilization status.

[0498] The planning and decision-making unit a740 determines the available services that service user U can enjoy based on available vehicle information a820 and service provision information, and provides information related to the determined available services to service user U's terminal device a100.

[0499] More specifically, the planning decision unit a740 sets a second section in which the service provider S occupies at least a portion (e.g., a compartment) of the vehicle a500, based on the available vehicle information a820 and the service provision information. It then sets a third section in which the service user U and the service provider S occupy at least a portion of the vehicle a500, based on the overlap between the desired section information (information of the first section) in the service utilization request information and the second section. It should be noted that if the service provider S is already in the vehicle a500 before the first section is set, the planning decision unit a740 may also set the second section simultaneously with the first section, starting from the current position of the vehicle a500.

[0500] Furthermore, the planning decision unit a740 sets a third interval within the overlap range between the information on possible service delivery locations included in the service delivery information and the first interval. Moreover, the planning decision unit a740 sets the third interval in a manner that ensures the time period during which service user U occupies at least a portion of vehicle a500 matches the service user's desired service usage time period, and in a manner that ensures the time period during which the service provider occupies the vehicle matches the service provider's desired service delivery time period. "Time period" includes moments such as start time and end time, as well as the length of time. For example, if the service usage time period desired by service user U is not included in the service delivery time period desired by service provider S, the planning decision unit a740 may adjust the time period during which service user U occupies at least a portion of vehicle a500 compared to the service usage time period desired by service user U, so that it is included in the service delivery time period. Conversely, if the service delivery time period desired by service provider S is not included in the service usage time period desired by service user S, the planning decision unit a740 may adjust the time period during which service provider S occupies at least a portion of vehicle a500 compared to the service delivery time period desired by service provider S, so that it is included in the service usage time period. Furthermore, the planning department a740 determines available services based on the established third interval.

[0501] In addition, when multiple service providers S provide services to a certain service user U in sequence, the planning decision unit a740 may also set up a second interval corresponding to each of the multiple service providers S, and set up multiple third intervals corresponding to each second interval.

[0502] As another function, the planning decision unit a740 can also update the first interval to the point where the first interval ends at the service delivery location outside the vehicle, based on instructions from the service user U using the terminal device a100. In this case, the planning decision unit 740 can also, based on instructions from the service user U using the terminal device a100 (or automatically), use the communication unit a710 to send reservation information to the facility located at the service delivery location outside the vehicle, use the communication unit a710 to receive the reservation result, and use the communication unit a710 to send the reservation result to the service user U's terminal device a100.

[0503] The route instruction unit a750 instructs the vehicle a500 on the route to be traveled by sending the information of the service user U’s start and end positions and the service provider S’s start and end positions to the vehicle a500 through the communication unit a710.

[0504] The authentication department a760 performs authentication of the service user U based on communication with the terminal device a100, and performs authentication at the start of service provision.

[0505] The determination unit a770 determines whether the vehicle a500 is being used by the service user U and the service provider S, respectively.

[0506] The planning decision unit a740 performs various processes based on the determination result of the determination unit 770. For example, the planning decision unit a740 may accept a change in the first interval (update the first interval) only if the determination unit a770 determines that both the service user U and the service provider S are using the vehicle a500. This could occur, for example, if the service provider S proposes a change of destination to the service user U or if the final destination is changed during the service based on information provided to the vehicle a500. Furthermore, the planning decision unit a740 may also prioritize allocating the vehicle a500 to the service user U if the determination unit a770 determines that the service user U is already using the vehicle a500 (i.e., if a service extension or other service request has been made during service use) at the time the first acquisition unit a720 receives the service use request information.

[0507] In addition to user information a810 related to the registered service user U and the aforementioned available vehicle information a820, the storage unit a800 also stores service management information a830. Service management information a830 includes, for example, service request management information a832, reservation management information a834, and ongoing service management information a836. In service request management information a832, each service usage request obtained by the first acquisition unit a720 is recorded. In reservation management information a834, information such as the reservation usage interval, reservation usage time period, route, and scheduled arrival time of each route is stored for each service. In ongoing service management information a836, information such as service status, service attributes, and service provider ID is registered.

[0508] Figure 46 This is a flowchart illustrating an example of the processing flow performed in the service provision system a2. First, the service commissioner A (service user U) uses the terminal device a100 to authenticate the user with the authentication unit a760 of the service management device a700 (step S200a). When the authentication unit a760 successfully authenticates the user, the service commissioner A (service user U) uses the terminal device a100 to send service utilization request information to the service management device a700 (step S202a). The service utilization request information is obtained by the first acquisition unit and stored in the storage unit a800 as service request management information a832.

[0509] After obtaining the service utilization request information, the third acquisition unit a724 of the service management device a700 queries the service provider device 600a for service provision information (step S204a). Multiple service provider devices a600 may exist depending on the attributes of the provided service or the service operator; in this case, the third acquisition unit a724 may query multiple service provider devices a600 simultaneously. The status management unit a630 of the service provider device a600 replies to the service management device a700 with service provision information associated with the services that can accept orders (representing the content of the services that can accept orders) (step S206a).

[0510] On the other hand, the second acquisition unit a722 of the service management device a700 queries the vehicle management device a510 for usage status (vehicle information) (step S208a). The vehicle / compartment management unit a550 of the vehicle management device a510 replies to the service management device a700 with the usage status detected by the usage status detection unit a552 (step S210a). It should be noted that the processing of steps S208a and S210a can also be performed asynchronously at any time as shown in the flowchart.

[0511] Next, the vehicle determination unit a730 determines the available vehicles based on the service utilization request information and the information obtained in step S210a, and generates available vehicle information (step S212a). Multiple vehicles may be determined in step S212a; in this case, the final vehicle determination may be performed until step S224a, which will be described later. Then, the planning determination unit a740 determines the available services that the service user can enjoy based on the available vehicle information and the service provision information that can accept orders obtained in step S206a (step S212a), and sends available service information indicating the content of the determined available services to the terminal device 100 (step S214a).

[0512] Service applicant A (service user U) reviews available service information, and as a result, uses terminal device a100 to order a service from service management device a700 (step S216a). The planning and decision unit a740 of service management device a700 extracts the portion of the service ordered in step S216a that is undertaken by the service provider, and orders the service from service provider device a600 (step S218a).

[0513] The order processing unit a620 of the service provider device a600 sends the intention to accept a service order to the service management device a700 (step S220a). At the same time, the order processing unit a620 sends the order details to the service provider's terminal device (not shown in this embodiment).

[0514] When the service provider device a600 receives an order acceptance instruction, the route instruction unit a750 of the service management device 700 sets the route that the service delivery vehicle a500 should travel (step S222a).

[0515] Next, the authentication unit a760 of the service management device a700 performs authentication processing for service initiation on the service provider device a600 and the authentication unit a530 of the vehicle a500. The route instruction unit a750 instructs the vehicle a500 on the route set in step S222a. The service provider device a600 performs service initiation authentication and determines the final vehicle as needed. In the vehicle management device a510 of the vehicle a500, the authentication unit a530 performs vehicle-side authentication and starts or schedules travel on the indicated route (step S224a).

[0516] Subsequently, service user U boards vehicle a500 (step S226a). When additional services are available, the planning decision unit a740 prompts the terminal device a100 for the additional services (step S228a). The service user reviews the content of the additional services. After ordering the additional services using the terminal device a100 (step S230), the planning decision unit a740 of the service management device a700 orders the additional services from the service provider device a600 (step S232a). The order processing unit a620 of the service provider device a600 sends information indicating acceptance of the additional service order to the service management device a700 (step S234a). Upon receiving the information indicating acceptance of the additional service order, the route instruction unit a750 of the service management device a700 instructs vehicle a500 to modify the route and change the destination (step S236a).

[0517] According to the fourth variation of the second embodiment described above, in addition to achieving the same effect as the second embodiment, since vehicle information is obtained from the pre-registered vehicle a500 candidates and the available vehicle a500 is determined based on the service utilization request information, more active utilization of vehicle a500 can be promoted.

[0518] For example, the service management device a300 (a700) can also be mounted on vehicle a200 (a500).

[0519] In addition, when the vehicle a200 (a500) is a manually driven vehicle, the communication unit a310 (a710) can communicate with the terminal device of the driver of the vehicle a200 (a500) via the network NW.

[0520] Alternatively, vehicle a200 (a500) can also be a remotely operated vehicle. In this case, vehicle a200 (a500) transmits various information obtained from external monitoring unit a210 to an external device via communication device a220. The external device generates (or plays) an image representing the surrounding conditions of vehicle a200 (a500) based on the received information and displays it to the remote operator. At this time, to compensate for communication delays, pre-reading processing can be used to correct the image, etc. The remote operator operates the driving controls based on the displayed image. The content of the operation performed on the driving controls is transmitted to vehicle a200 (a500), and vehicle a200 (a500) drives based on the received operation content.

[0521] <Third Implementation Method>

[0522] Next, the third embodiment will be described. In the third embodiment, the implementation of the pick-up and drop-off management device, pick-up and drop-off management method, and vehicle applicable to the vehicle shown in the first embodiment will be described. The vehicle assigned in this system is, for example, an autonomous vehicle that basically does not require driving operation. In addition, the assigned vehicle waits at various prepared vehicle stations in an unassigned state, and after arriving at the destination, it moves to an available vehicle station near the destination and waits.

[0523] Figure 47 This is a structural diagram of the vehicle dispatch system b1. The vehicle dispatch system b1 includes one or more vehicles b100, one or more facility terminals b200, one or more user terminals b300, and a pick-up and drop-off management device b400. These components can communicate with each other via a network NW. The network NW includes the Internet, WAN, LAN, public lines, carrier equipment, dedicated lines, wireless base stations, etc.

[0524] [vehicle]

[0525] Vehicle b100 is, for example, a vehicle with four or more wheels that can be used by multiple users. Figure 48 This is a structural diagram of vehicle b100. Vehicle b100 includes, for example, an external monitoring unit b110, a communication device b120, a navigation device b130, a lane recommendation device b140, an automatic driving control unit b150, a drive force output device b160, a braking device b162, a steering device b164, and a vehicle allocation management unit b170. Each of the external monitoring unit b110, communication device b120, navigation device b130, lane recommendation device b140, automatic driving control unit b150, drive force output device b160, braking device b162, and steering device b164 has, for example, the features described in the second embodiment above. Figure 26The external monitoring unit a210, communication device a220, navigation device a230, lane recommendation device a240, automatic driving control unit a250, drive force output device a260, braking device a262, and steering device a264 have the same structure, therefore detailed descriptions are omitted here. Furthermore, regarding the automatic driving processing in the third embodiment, the method described in the first embodiment is referenced. Figure 3 And related explanations, detailed explanations omitted.

[0526] The vehicle allocation management unit b170 includes an input / output unit b171, a storage unit b172, a vehicle allocation control unit b173, a status acquisition unit b174, a user information acquisition unit b175, and an order acquisition unit b176.

[0527] The input / output unit b171 includes input units such as a mouse, keyboard, touch panel, microphone, sensor, and camera, and output units such as a display and speaker. The storage unit b172 is implemented by HDD, flash memory, RAM, ROM, etc.

[0528] The vehicle control unit b173, status acquisition unit b174, user information acquisition unit b175, and order acquisition unit b176 are implemented, for example, by a processor such as a CPU executing a program (software) stored in the storage unit b172. Furthermore, some or all of these functional units can also be implemented by hardware such as LSI, ASIC, FPGA, and GPU, or through the coordinated operation of software and hardware.

[0529] The vehicle dispatch control unit b173 sets navigation setting information to the navigation control unit b136 based on the pick-up and drop-off schedule received from the pick-up and drop-off management unit b400 using the communication device b120. The pick-up and drop-off schedule refers to the schedule used to ensure that the pick-up and drop-off vehicles, which are booked in conjunction with the facility's reservation details, travel in accordance with the facility's reservation. This schedule includes the location information of the pick-up location, the arrival time to the pick-up location, the location information of the destination, the arrival time to the destination, and the number of passengers. The pick-up location is the location where the user boards the vehicle. The navigation setting information includes the pick-up location, the arrival time to the pick-up location, the destination, and the arrival time to the destination.

[0530] The status acquisition unit b174 acquires information including the vehicle's movement status (hereinafter referred to as status information) and transmits this information to the pick-up and drop-off management unit b400 using the communication device b120. The status information includes information that establishes a correspondence between the date and time and the position of the vehicle b100 determined by the GNSS receiver b134, and information indicating the arrival time at the destination obtained by the navigation control device b136. Furthermore, the status acquisition unit b174 can also acquire vehicle allocation status and arrival status based on the vehicle b100's position information and navigation setting information determined by the GNSS receiver b134, and include these in the status information. Vehicle allocation status includes, for example, vehicle waiting, partial waiting, completed ride, moving, and completed journey. Arrival status includes, for example, on time, delayed, and delayed due to congestion. It should be noted that vehicle allocation status can also be input by the user using the input / output unit b171, or it can be the result parsed by the status acquisition unit b174 based on sensor detection results, images captured by a camera, or video.

[0531] The user information acquisition unit b175 uses, for example, the input / output unit b171 to acquire user-related information (hereinafter referred to as user information) and sends it to the pick-up and drop-off management unit b400 using the communication device b120. User information includes, for example, the number of passengers, the user's gender, age, ethnicity, hobbies or feelings, facility-related questionnaires, the number and weight of personal belongings, the presence or absence of a wheelchair, and the presence or absence of a stroller. For example, the user information acquisition unit b175 can also acquire the number of passengers and the user's gender by analyzing sensor detection results, images captured by a camera, and videos. Furthermore, the user information acquisition unit b175 can also acquire information such as the level of engagement of conversations among users inside the vehicle, user satisfaction, and emotions by analyzing sound data detected by a microphone.

[0532] The order acquisition unit b176 uses, for example, the input / output unit b171 to obtain order information (hereinafter referred to as order instruction information) for services or items provided by the facility, and sends it to the pick-up and drop-off management unit b400 using the communication device b120. Thus, users traveling in the vehicle b100 can pre-order items or services to be provided upon arrival at the facility using an online menu.

[0533] [Facility Terminal]

[0534] Facility terminal b200 is a terminal installed in a facility that can be booked by users and used by the facility's administrator. Examples of such facilities include hotels, inns, restaurants, hospitals, beauty salons, and cultural schools. Facility terminal b200 can be, for example, a personal computer, smartphone, or tablet.

[0535] Figure 49 This is a functional structure diagram of facility terminal b200. Facility terminal b200 includes, for example, a communication device b210, an input unit b220, an output unit b230, a storage unit b240, and a control unit b250.

[0536] Communication device b210 is, for example, a communication interface for connecting to a network NW or for direct communication with the reception and management device 400. Communication device b210 may include, for example, a NIC (Network Interface Card), and may also perform wireless communication based on Wi-Fi, DSRC (Dedicated Short Range Communications), Bluetooth (registered trademark), or other communication standards. Multiple communication devices may also be prepared as communication device b210, depending on the application.

[0537] Input unit b220 includes, for example, a keyboard, mouse, touch panel, microphone, etc. Output unit b230 includes, for example, a display, speaker, etc. Storage unit b240 is implemented by HDD, flash memory, RAM, ROM, etc.

[0538] The control unit b250 is implemented, for example, by executing a program (software) stored in the storage unit b240 using a processor such as a CPU. Alternatively, some or all of these functional units can be implemented by hardware such as LSI, ASIC, FPGA, or GPU, or through a combination of software and hardware. For example, based on information received from the receiving and management device 400, the control unit b250 displays web pages viewed by a browser, application pages viewed by an application program, etc., on the output unit b230.

[0539] [User Terminal]

[0540] User terminal b300 is the terminal used by the user. User terminal b300 is, for example, a personal computer, smartphone, tablet, etc. Figure 50 This is a functional structure diagram of the user terminal b300. The user terminal b300 includes, for example, a communication device b310, an input unit b320, an output unit b330, a storage unit b340, a control unit b350, and a GNSS receiver b360. It should be noted that structures identical to those in the vehicle b100 and facility terminal b200 are referred to by the same names, and detailed descriptions are omitted.

[0541] Here, refer to Figure 51 , 52 An example of an operation screen displayed on the output section b330 of the user terminal b300 will be described. Figure 51This diagram illustrates an example of a facility reservation screen. The facility reservation screen b370 is an operation screen displayed when a user requests a facility reservation using the input section b320. The facility reservation screen b370 includes facility reservation information b371, pick-up and drop-off service information b372, and a reservation button b373.

[0542] Facility reservation content b371 is a screen that displays the items required for reserving a facility and accepts selections and input from users for each item. Items in facility reservation content b371 include, for example, date and time, facility name, number of users, user name, contact information, special notes, and pick-up and drop-off services.

[0543] The pick-up and drop-off service content b372 is a screen that displays the items required for booking a car and accepts selections and inputs from the user for each item. The pick-up and drop-off service content b372 includes, for example, items for selecting the outbound or return route or either route, and for selecting the arrival or departure time to the pick-up location (station, airport, etc.) or destination.

[0544] The reservation button b373 is an operation button that accepts reservations displayed under the facility reservation content b371 and the pick-up and drop-off service content b372. When the reservation button b373 is operated, the control unit b350 generates facility reservation information based on the reservation content displayed under the facility reservation content b371 and the pick-up and drop-off service content b372, and sends it to the pick-up and drop-off management device b400 using the communication device b310.

[0545] After the control unit b350 sends the facility reservation information, it displays the vehicle reservation screen on the output unit b330 based on the information received from the pick-up and drop-off management device b400 using the communication device b310. It should be noted that in this embodiment, the example described is "displaying the pick-up and drop-off schedule generated by the pick-up and drop-off management device b400 based on the facility reservation information on the vehicle reservation screen, allowing the user to confirm the pick-up and drop-off details and then accept the vehicle reservation," but the present invention is not limited to this. For example, it is also possible that the user does not need to confirm the pick-up and drop-off details, and the pick-up and drop-off management device b400 accepts both the facility reservation and the vehicle reservation by receiving the facility reservation information.

[0546] Figure 52 This diagram illustrates an example of a vehicle reservation screen. The vehicle reservation screen b380 is an operation screen displaying a pick-up and drop-off schedule generated by the pick-up and drop-off management device b400 based on facility reservation information. The vehicle reservation screen b380 includes pick-up and drop-off details b381 and a reservation button b382.

[0547] The pick-up and drop-off content b381 is a screen that displays the pick-up and drop-off schedule generated by the pick-up and drop-off management device b400, which is required for booking a vehicle, and allows the user to edit a portion of the schedule. The pick-up and drop-off content b381 includes items such as date and time, number of users, pick-up location, arrival time to pick-up location, destination, and arrival time to destination.

[0548] The reservation button b382 is an operation button for accepting reservations displayed in the pick-up and drop-off content b381. When the reservation button b382 is activated, the control unit b350 generates vehicle reservation information based on the reservation content displayed in the pick-up and drop-off content b381 and sends it to the pick-up and drop-off management device b400 using the communication device b310. Here, the control unit b350 can include this intention in the vehicle reservation information if the pick-up and drop-off content remains unchanged, or it can include only the changes to the pick-up and drop-off content in the vehicle reservation information.

[0549] [Pick-up and Drop-off Management Device]

[0550] Next, refer to Figures 53-57 The connection and delivery management device B400 will be explained. Figure 53 This is a functional structure diagram of the pick-up and drop-off management device b400. The pick-up and drop-off management device b400 includes, for example, a communication device b410, a storage unit b420, and a control unit b430. The communication device b410 is, for example, a NIC for connecting to a network NW. The communication device b310 communicates with the vehicle b100, the facility terminal b200, and the user terminal b300 via the network NW. The storage unit b420 is implemented using HDD, flash memory, RAM, ROM, etc.

[0551] The control unit b430 includes a facility reservation unit b431, a vehicle allocation reservation unit b432, a vehicle allocation management unit b433, an acquisition unit b434, and a status management unit b435. Some or all of these structures are implemented, for example, by a processor such as a CPU executing programs (software) stored in the storage unit b420. Alternatively, some or all of these functional units can also be implemented using hardware such as LSI, ASIC, FPGA, or GPU, or through a combination of software and hardware.

[0552] The facility reservation unit b431 reserves facilities based on facility reservation information received from the user terminal b300 via the communication device b410 and the network NW. The facility reservation information includes reservation details related to the facility reserved by the user, such as the reservation date and time, facility name, address, number of people reserving, user name, contact information, special notes, and pick-up / drop-off services. The facility reservation unit b431 may also refer to an external server connected via the network NW to obtain the availability of the facility specified by the user and send it to the user terminal b300. Based on the received facility reservation information, the facility reservation unit b431 stores various information in the facility reservation information b421 in the storage unit b420. Furthermore, the facility reservation unit b431 may also create information indicating the user's reliability based on the user's past facility reservation history and include it in the facility reservation information b421. User reliability may include, for example, an evaluation value corresponding to the reservation cancellation rate and an evaluation value corresponding to the frequency of use.

[0553] Facility reservation information b421 indicates the details of each facility's reservation. Figure 54 This is an example diagram showing facility reservation information b421. (As shown...) Figure 54 As shown, facility reservation information b421 establishes a correspondence between the user management key, facility management key, facility reservation details, optional service information, and reservation status, all linked to the reservation management key. The reservation management key is unique information used to identify each reservation. The user management key is unique information used to identify each user. The facility management key is unique information used to identify each facility. The facility reservation details include the reservation date and time, facility name, address, number of participants, user name, contact information, and any special notes. The optional service information includes information indicating whether optional services such as pick-up and drop-off are desired. The reservation status indicates the status of the facility reservation, such as reservation in progress, reservation completed, or cancelled.

[0554] The vehicle reservation unit b432 creates a pick-up and drop-off schedule based on facility reservation information received from the user terminal b300 via communication device b410 and network NW, and reserves a pick-up and drop-off vehicle for the facility. Based on the user's specifications, the vehicle reservation unit b432 reserves a pick-up and drop-off vehicle for the route to or from the facility, or both. Alternatively, the vehicle reservation unit b432 can send the pick-up and drop-off schedule created based on the facility reservation information to the user terminal b300 before reserving a pick-up and drop-off vehicle, and reserve the vehicle after the user accepts the reservation instruction.

[0555] The vehicle reservation unit b432, based on facility reservation information, sets the facility as the destination or departure point and creates a pick-up and drop-off schedule to meet the specified arrival time. For example, based on the reservation date and time, number of participants, facility name, etc., contained in the facility reservation information, the vehicle reservation unit b432 determines the reservation date and time, number of participants, pick-up location or destination, and their arrival time for the pick-up and drop-off vehicles. In addition to facility reservation information, the vehicle reservation unit b432 can also receive information from the user terminal b300 related to the means of transportation to the facility (e.g., airplane, Shinkansen), and create pick-up and drop-off schedules corresponding to airport arrival times up to hotels, and to stations up to restaurants, and send them to the user terminal b300. When a vehicle is reserved based on the created pick-up and drop-off schedule, the vehicle reservation unit b432 stores various information in the vehicle reservation information b422 of the storage unit b420 based on the created pick-up and drop-off schedule. In addition, the vehicle reservation department b432 can also create information indicating the reliability of the user based on the user's past vehicle reservation status and include it in the vehicle reservation information b422.

[0556] Vehicle reservation information b422 indicates the reservation details for each pick-up and drop-off vehicle. Figure 55 This is an example diagram showing vehicle reservation information b422. (As shown...) Figure 55 As shown, vehicle reservation information b422 establishes a correspondence between the user management key, vehicle ID, pick-up and drop-off schedule, and reservation status and the reservation management key. The vehicle ID is unique information used to identify each vehicle.

[0557] The vehicle allocation management department (b433) allocates the pick-up and drop-off vehicles reserved by the vehicle allocation reservation department (b432) based on the reservation details. The vehicle allocation by the vehicle allocation management department (b433) includes the processing of allocating pick-up and drop-off vehicles according to each pick-up and drop-off schedule (hereinafter referred to as allocation processing) and the processing of instructing the allocated pick-up and drop-off vehicles to perform automatic driving in accordance with the pick-up and drop-off schedule (hereinafter referred to as driving instruction processing).

[0558] In the allocation process, the vehicle management department b433 reads the reservation details corresponding to the pre-determined allocation period (e.g., from 00:00 to 24:00 the following day) from the vehicle reservation information b422, and allocates the responsible vehicles b100 according to the pick-up and drop-off schedules contained in the read information. For example, based on the previous and subsequent reservation status, the vehicle management department b433 selects vehicles registered in the vehicle information b424 that can accommodate the number of users in the reservation and can reach the pick-up location and destination in a manner that meets the reservation arrival time. The vehicle information b424 contains information related to the vehicle b100, such as information that establishes a correspondence between the vehicle ID, the vehicle station where the vehicle b100 is parked, the current location (latitude, longitude, altitude) of the vehicle b100, the address required for communication with the vehicle b100, and the driving status.

[0559] Additionally, the vehicle allocation management department b433 can allocate vehicles b100 in a manner that minimizes the travel distance from the previous destination to the next pick-up location, preventing delays in the pick-up and drop-off schedule due to congestion or other factors outside the designated pick-up and drop-off routes. Furthermore, the vehicle allocation management department b433 can allocate vehicles b100 such that the required number of vehicles b100 for pick-up and drop-off to facilities within a specified area are waiting at designated vehicle stations. The vehicle allocation management department b433 establishes a correspondence between the allocated pick-up and drop-off schedule and the vehicle ID of the assigned vehicle b100, and writes this information to the vehicle allocation status information b423. It should be noted that immediately after writing to the vehicle allocation status information b423, all vehicle allocation statuses are set to "unallocated."

[0560] It should be noted that when creating a pick-up and drop-off schedule, if the reservation time included in the facility reservation information is within the allocation period, the vehicle allocation reservation department b432 can also refer to both the facility reservation information b421 and the vehicle allocation status information b423 to create a pick-up and drop-off schedule suitable for the user and capable of allocating pick-up and drop-off vehicles. For example, based on the reservation date and time, number of reservations, facility name, etc., contained in the facility reservation information b421, the vehicle allocation reservation department b432 creates a first schedule including the reservation date and time of the pick-up and drop-off vehicles, the number of reservations, the pick-up location or destination, and their arrival time. If there is a vehicle b100 that can be allocated according to the first schedule, the first schedule is set as the pick-up and drop-off schedule. On the other hand, if there is no vehicle b100 that can be allocated according to the first schedule, the vehicle allocation reservation department 432 can also modify part or all of the first schedule by allocating vehicle b100 to create a second schedule and set it as the pick-up and drop-off schedule. Therefore, if the facility is booked several days in advance, a pick-up and drop-off service can be booked according to the user's desired schedule regardless of the status of vehicle B100; if the facility is booked several hours in advance, a pick-up and drop-off service can be booked according to the schedule where a vehicle is available.

[0561] In the driving instruction processing, the vehicle allocation management department b433 uses the communication device b410 to send the driving start instruction and the pick-up and drop-off schedule to the vehicle b100 at the prescribed time, and rewrites the vehicle allocation status of the vehicle allocation status information b423 during the pick-up and drop-off.

[0562] The vehicle allocation status information b423 includes information related to the vehicle reserved or the vehicle in the allocation, such as information set in vehicle b100 and information indicating the vehicle allocation status. Figure 56 This is an example diagram showing vehicle allocation status information b423. (As shown...) Figure 56 As shown, vehicle allocation status information b423 establishes a correspondence between the usage date and time, number of users, pick-up location and arrival time, destination and arrival time, vehicle allocation status, and vehicle ID. Vehicle allocation status indicates the allocation status of the assigned vehicle b100, and is updated, for example, by the vehicle allocation management department b433.

[0563] The acquisition unit b434 obtains information such as movement status, allocation status, and arrival status from the vehicle b100 assigned by the vehicle allocation management unit b433. For example, the acquisition unit b434 receives status information periodically sent from the vehicle b100 using the communication device b410, and writes various information into the movement status information b425 of the storage unit b420 based on the received status information.

[0564] Mobility status information b425 indicates the status of vehicle b100 in the vehicle. Figure 57 This is a diagram illustrating an example of movement status information b425. (As shown...) Figure 57 As shown, the movement status information b425 establishes a correspondence between the current vehicle b100's location information, the arrival target time to the pickup location at the current time, the arrival target time to the destination at the current time, the vehicle assignment status, the arrival status, and the measurement date and time. This information is stored, for example, in a table prepared for each vehicle b100. The measurement date and time is the date and time on which the status information is generated in the vehicle b100. The location information indicates the location of the vehicle b100 as determined by the GNSS receiver b134 of the vehicle b100 at the measurement date and time. The arrival target time is the arrival target time derived by the navigation control device b136 of the vehicle b100 at the measurement date and time. The arrival status indicates the arrival condition of the assigned vehicle b100, for example, the arrival status obtained by the status acquisition unit b174 of the vehicle b100 at the measurement date and time.

[0565] The status management unit b435 uses the communication device b410 to notify at least one of the user terminal b300 and the facility terminal b200 of the movement status obtained by the acquisition unit b434. The status management unit b435 may refer to the movement status information b425 to notify the facility terminal b200 of messages corresponding to changes in vehicle allocation status, or messages corresponding to arrival status, when a delay occurs in the vehicle b100. For example, after the user boards the vehicle b100 assigned by the vehicle allocation management unit 433, the status management unit b435 will notify the facility terminal b200 of the start of movement to the facility or the arrival time at the facility.

[0566] The Status Management Unit b435 determines whether the number of passengers differs from the number of reservations based on the passenger information obtained by the Acquisition Unit b434. If they differ, the Status Management Unit b435 notifies the facility terminal b200 of the change in the number of reservations. Additionally, the Status Management Unit b435 notifies the corresponding facility terminal b200 of the ordering instruction information obtained by the Acquisition Unit b434.

[0567] If the arrival time of vehicle b100, allocated by vehicle allocation management department b433, to the pick-up location or the destination is delayed, the status management department b435 shall notify at least one of the user terminal b300 and the facility terminal b200, accepting at least one of the changes or cancellations of the vehicle allocation reservation and the facility reservation. Changes may include extensions of usage time, postponements of usage days, changes to the pick-up location, or changes to the destination. Furthermore, if the user, notified of the delay in the arrival time of vehicle b100 allocated by vehicle allocation management department b433, neither accepts the cancellation or change of the vehicle allocation nor the change of the facility reservation, the status management department b435 may also accept both the cancellation of the vehicle allocation and the cancellation of the facility reservation.

[0568] The status management department b435 refers to the mobility status information b425 and updates the vehicle allocation status information b423 when the vehicle allocation status changes.

[0569] [flow chart]

[0570] Next, refer to Figure 58 , 59 An example of the processing action in vehicle b100 will be explained. Figure 58 , 59 This is a flowchart illustrating an example of processing actions in vehicle b100.

[0571] First, the vehicle allocation control unit b173 determines whether a driving start instruction has been received from the pick-up and drop-off management unit b400 using the communication device b120 (step S101b). If a driving start instruction has been received, the vehicle allocation control unit b173 instructs the navigation device b130 and the automatic driving control unit b150 to start driving based on the pick-up and drop-off schedule received along with the driving start instruction (step S102b). Thereby, the navigation device b130 sets the pick-up and drop-off locations, destinations, and routes corresponding to their arrival times in accordance with the pick-up and drop-off schedule, and the automatic driving control unit b150 begins automatic driving according to the set routes.

[0572] The status acquisition unit b174 determines whether it is a pre-determined first notification opportunity (step S103b). The first notification opportunity is a pre-determined time when the vehicle b100 notifies the status information during the pick-up process, such as the time when autonomous driving begins, the time when the arrival time at the pick-up location is delayed compared to the scheduled arrival time, the time when the vehicle arrives at the pick-up location, the time when the user boards the vehicle b100, or the time when a predetermined time has elapsed since the last notification. If it is determined to be a first notification opportunity, the status acquisition unit b174 acquires the status information and sends it to the pick-up management device b400 using the communication device b120 (step S104b).

[0573] The vehicle allocation control unit b173 determines whether it has received a vehicle allocation cancellation instruction from the pick-up and drop-off management device b400 using the communication device b120 (step S105b). If a vehicle allocation cancellation instruction is received, the vehicle allocation control unit b173 instructs the navigation device 130 and the automatic driving control unit b150 to terminate the automatic driving operation along the set route (step S106b). Here, the navigation device b130 can also receive a new destination setting from the user using the HMI b131. It should be noted that when the vehicle allocation control unit b173 receives instructions from the pick-up and drop-off management device b400 regarding changes to the pick-up location, destination, and their arrival time using the communication device b120, it instructs the navigation device b130 and the automatic driving control unit b150 to change the navigation setting information.

[0574] The status acquisition unit b174 determines whether all users are on board vehicle b100 (step S107b). For example, based on the location of vehicle b100 determined by GNSS receiver b134, the status acquisition unit b174 determines that all users are on board vehicle b100 if all predetermined pick-up locations have been passed. Alternatively, the status acquisition unit b174 can also determine that all users are on board vehicle b100 if the user inputs information about all users being on board vehicle b100 using input / output unit b171, and the number of passengers obtained from analyzing images taken inside the vehicle matches the reserved number of users. If it is determined that all users are on board vehicle b100, the status acquisition unit b174 generates status information indicating that the ride is complete and sends it to the pick-up and drop-off management device b400 using communication device b120 (step S108b).

[0575] The status acquisition unit b174 determines whether it is a pre-determined second notification opportunity (step S109b). The second notification opportunity is a pre-determined time to notify the user of status information while all users are riding in the vehicle b100. Examples include when all users are riding in the vehicle b100, when the arrival time at the destination is delayed compared to the scheduled arrival time, and when a predetermined time has elapsed since the last notification. If it is determined to be a second notification opportunity, the status acquisition unit b174 acquires the status information and sends it to the pick-up and drop-off management device b400 using the communication device b120 (step S110b).

[0576] The user information acquisition unit b175 determines whether user information has been acquired (step S111b). For example, if the input / output unit b171 receives input from the user regarding the number of passengers, the user's gender, and age, the user information acquisition unit b175 generates user information including the number of passengers, the user's gender, and age, and sends it to the pick-up and drop-off management device b400 using the communication device b120 (step S112b).

[0577] The order acquisition unit b176 determines whether it has obtained the order instruction information (step S113b). For example, if the user selects at least one menu from the online menu using the input / output unit b171, the order acquisition unit b176 generates order instruction information for ordering the selected menu and sends it to the delivery management device b400 using the communication device b120 (step S114b).

[0578] The vehicle dispatch control unit b173 determines whether the destination has been reached based on the output from the navigation control unit b136 (step S115b). When the position of the vehicle b100, as determined by the GNSS receiver b134, enters the designated range of the destination, the navigation control unit b136 notifies the vehicle dispatch control unit b173 that the destination has been reached. Upon notification of arrival at the destination, the vehicle dispatch control unit b173 sets the vehicle station as the next destination and instructs the navigation unit b130 and the automatic driving control unit b150 to perform automatic driving (step S116b). It should be noted that if a new pick-up / drop-off schedule is received while moving towards the vehicle station, the vehicle dispatch control unit b173 proceeds to step S101b.

[0579] Next, refer to Figure 60 , 61 Sections 62 and 62 will be used to illustrate an example of the processing action in the delivery management device 400b. Figure 60 , 61 62 is a flowchart illustrating an example of the processing operation in the pick-up and drop-off management device 400b.

[0580] First, the facility reservation unit b431 determines whether it has received facility reservation information from the user terminal b300 using the communication device b410 (step S201b). If it is determined that facility reservation information has been received, the facility reservation unit b431 refers to the external server managing facility reservations to determine whether the facility represented by the received facility reservation information can be reserved. If it can be reserved, the facility reservation unit b431 saves various information in the facility reservation information b421 of the storage unit b420 based on the received facility reservation information (step S202b). Thus, the facility represented by the facility reservation information is reserved. It should be noted that if it cannot be reserved, the facility reservation unit b431 may also use the communication device b410 to notify the user terminal b300 of this intention and accept the reservation with other content.

[0581] Next, the facility reservation unit b431 determines whether the received facility reservation information includes the content of the requested pick-up and drop-off service (step S203b). If it is determined that the facility reservation information includes the content of the requested pick-up and drop-off service, the facility reservation unit b431 instructs the vehicle allocation reservation unit b432 to create a pick-up and drop-off schedule. Then, the vehicle allocation reservation unit b432 determines whether the reservation time contained in the facility reservation information is included in the allocation period after the allocation process has ended (step S204b). If the reservation time is not included in the allocation period after the allocation process has ended, the vehicle allocation reservation unit b432 creates a pick-up and drop-off schedule with reference to the facility reservation information b421 and sends it to the user terminal b300 using the communication device b410 (step S205b). On the other hand, if the reservation time is included in the allocation period after the allocation process has ended, the vehicle reservation unit b432 refers to both the facility reservation information b421 and the vehicle status information b423 to create a pick-up and drop-off schedule that can allocate the vehicle b100, and sends it to the user terminal b300 using the communication device b410 (step S206b).

[0582] The vehicle reservation unit b432 determines whether a vehicle reservation instruction has been received from the user terminal b300 using the communication device b410 (step S207b). If it is determined that a vehicle reservation instruction has been received, the vehicle reservation unit b432 saves the reservation details in the vehicle reservation information b422 in the storage unit b420 based on the pick-up and drop-off schedule sent to the user terminal b300 (step S208b). As a result, the pick-up and drop-off vehicle for the reserved facility is reserved.

[0583] The vehicle allocation management unit b433 performs the allocation process, writing various information into the vehicle allocation status information b423 (step S209b). Next, the vehicle allocation management unit b433 determines whether it is a suitable time to allocate a vehicle by referring to the vehicle allocation reservation information b422 (step S210b). The vehicle allocation time is the time when the pick-up and drop-off vehicle will travel to the pick-up location. It is derived by calculating the travel time from the current location of the vehicle b100 to the pick-up location in reverse order, so as to arrive at the pick-up location before the determined arrival time. If the vehicle allocation time has been reached, the vehicle allocation management unit b433 sends the driving start instruction and the pick-up and drop-off schedule read from the vehicle allocation reservation information b422 to the vehicle b100 using the communication device b410 (step S211b). In addition, the vehicle allocation management unit b433 changes the vehicle allocation status corresponding to the vehicle ID of the allocated vehicle b100 to "vehicle picking up" in the vehicle allocation status information 423.

[0584] The status management unit b435 refers to the mobility status information b425 and determines whether the acquisition unit b434 has acquired new status information (step S212b). If it is determined that new status information has been acquired, the status management unit b435 determines whether the arrival at the pickup location is delayed (step S213b). For example, the status management unit b435 compares the latest arrival target time of the pickup location stored in the mobility status information b425 with the arrival time of the pickup location stored in the vehicle dispatch status information b423.

[0585] If a delay in arrival at the pick-up location is determined, the status management unit b435 uses the communication device b410 to send information confirming the cancellation or change of the vehicle or facility reservation, along with the vehicle's movement status, to the user terminal b300 (step S214b). For example, the status management unit b435 sends the movement status, including the target arrival time at the pick-up location, the vehicle b100's current location, and the target arrival time at the destination, to the user terminal b300. Next, the status management unit b435 uses the communication device b410 to send the vehicle b100's movement status to the facility terminal b200 (step S215b). For example, the status management unit b435 sends the movement status, including the target arrival time or delay time at the facility, to the facility terminal b200.

[0586] On the other hand, if it is determined in step S21b2 that no status information has been obtained, the vehicle allocation management unit b433 determines whether a vehicle allocation cancellation instruction has been received from the user terminal b300 using the communication device b410 (step S216b). If a vehicle allocation cancellation instruction is received, the vehicle allocation management unit b433 uses the communication device b410 to send the vehicle allocation cancellation instruction to the vehicle b100 (step S217b). In addition, the vehicle allocation management unit b433 uses the communication device b410 to send the vehicle allocation cancellation to the facility terminal b200 (step S218b). Here, the vehicle allocation management unit b433 may also receive a vehicle allocation reservation change instruction from the user terminal b300 and send the change to the vehicle 100 and the facility terminal b200. In addition, the vehicle allocation management unit b433 may also receive the reservation cancellation or reservation change instruction to the facility using the communication device b410 along with the vehicle allocation cancellation or reservation change instruction, and transmit this intention to the facility terminal b200.

[0587] On the other hand, if it is determined in step S216b that no vehicle allocation cancellation instruction has been received from the vehicle allocation management unit b433, the status management unit b435 determines whether a travel status indicating completion of the ride has been received from the user terminal b300 using the communication device b410 (step S219b). If it is determined that no travel status indicating completion of the ride has been received, the status management unit b435 returns to step S212b and repeats the process.

[0588] If, in step S219b, a movement status indicating completion of the ride is received, the status management unit b435 uses the communication device b410 to send a message to the facility terminal b200 indicating that all users have boarded the vehicle b100 (step S220b). Next, based on the status information and user information received from the vehicle b100 using the communication device b410, the status management unit b435 determines whether the number of passengers and the number of reservations are the same (step S221b). If the number of passengers and the number of reservations are different, the status management unit b435 uses the communication device b410 to send a message to the facility terminal b200 to change the number of reservations to the number of passengers (step S222b).

[0589] Next, the status management unit b435 determines whether status information has been received from the vehicle b100 using the communication device b410 (step S223b). If it is determined that status information has been received, the status management unit b435 determines, based on the received status information, whether the arrival time at the destination is delayed compared to the scheduled time (step S224b). If it is determined that the arrival time at the destination is delayed compared to the scheduled time, the status management unit b435 uses the communication device b410 to send the movement status of the vehicle b100 to the facility terminal b200 (step S225b).

[0590] Next, the status management unit b435 determines whether an order instruction has been received from the vehicle b100 using the communication device b410 (step S226b). If it is determined that an order instruction has been received, the status management unit 435 uses the communication device b410 to send the order instruction to the facility terminal b200 (step S227b).

[0591] Next, the status management unit b435 determines whether it has received status information indicating whether it has arrived at its destination from the vehicle b100 using the communication device b410 (step S228b). If it determines that it has received status information indicating that it has arrived at its destination, the status management unit b435 rewrites the vehicle allocation status of the vehicle allocation status information b423 and the movement status information b425 to "movement completed", and sends a message indicating that it has arrived at its destination to the facility terminal b200 using the communication device b410 (step S229b).

[0592] Next, refer to Figure 63The overview of the vehicle allocation system b1 is explained. Figure 63 This diagram is used to illustrate an example utilizing the vehicle allocation system b1. Figure 63 In the example shown, assume that a reservation has been made for accommodation at hotel b530, a reservation for dining at restaurant b540, a shuttle bus from airport b520 to hotel b530, and a shuttle bus from hotel b530 to restaurant b540.

[0593] (1) First, user U1 uses user terminal b300 in their home b510 to send facility reservation information and vehicle reservation information to pick-up and drop-off management device b400 to make reservations for facilities and pick-up and drop-off vehicles.

[0594] (2) When the time for vehicle allocation is reached, the pick-up and drop-off management device b400 causes the pre-assigned vehicle b100A to go to the airport b520, which is the pick-up location.

[0595] (3) Vehicle b100A obtains status information such as movement status and notifies the pick-up and drop-off management device 400.

[0596] (4) In the event of a delay in the arrival of vehicle b100A at airport b520, the pick-up and drop-off management device b400 shall notify the facility terminal b200 of hotel b530 and the user terminal b300 of user U1. For example, if the user terminal b300 instructs the pick-up and drop-off management device b400 to cancel the vehicle assignment, the pick-up and drop-off management device b400 shall notify vehicle b100A of the vehicle assignment cancellation, instruct it to proceed to the vehicle station, and notify the facility terminal b200 of hotel b530 of the intention.

[0597] (5) When vehicle b100A arrives at airport b520, it will notify user terminal b300 and pick-up and drop-off management device b400 of user U1 of the arrival and parking information.

[0598] The pick-up and drop-off management device b400 transmits the received content to the facility terminal b200 of hotel b530. Then, after user U1 boards vehicle b100A, vehicle b100A departs towards hotel b530.

[0599] (6) Vehicle b100A will notify the pick-up and drop-off management device b400 of the user U1's vehicle ride and other movement status. The pick-up and drop-off management device b400 will then transmit the received information to the facility terminal b200 of the hotel b530.

[0600] (7) In the event of a delay in the arrival of vehicle b100A at hotel b530, the pick-up and drop-off management device b400 shall notify the facility terminal b200 of hotel b530 of the intention.

[0601] (8) When vehicle b100A arrives at hotel b530, it will notify the pick-up and drop-off management device b400 of the arrival and user U1's disembarkation. The pick-up and drop-off management device b400 will then transmit the received information to the facility terminal b200 of hotel b530.

[0602] (9) Vehicle b100A moves toward the vehicle station or the next scheduled pick-up location.

[0603] (10) Subsequently, the pick-up and drop-off management device b400 allocates vehicle b100B according to the reservation time of restaurant b540, and notifies the user terminal b300 that vehicle b100B is heading to hotel b530, which is the pick-up location. Vehicle b100A obtains the movement status while moving towards hotel b530 and notifies the pick-up and drop-off management device 400. In the event of a delay in arrival at hotel b530, the pick-up and drop-off management device b400 notifies the user terminal b300 of this.

[0604] (11) When vehicle b100B arrives at hotel b530, it notifies user terminal b300 and pick-up and drop-off management device b400 of the arrival and parking location. Then, when user U1 boards vehicle b100B, vehicle 100B departs for restaurant b540.

[0605] (12) The vehicle b100B notifies the pick-up and drop-off management device b400 of the user U1’s travel status and other movement status.

[0606] (13) In the event of a delay in the arrival of vehicle b100B at restaurant b540, or in the event of receiving an ordering instruction from the online menu, the pick-up and drop-off management device b400 shall notify the facility terminal b200 of this intention.

[0607] (14) When vehicle b100B arrives at restaurant b540, it will notify the pick-up and drop-off management device b400 of information indicating that it has arrived and that user U1 has disembarked.

[0608] (15) Vehicle b100B moves toward the vehicle station or the next scheduled pick-up location.

[0609] Next, refer to Figure 64 Here is another example of the vehicle allocation system b1. Figure 64 This diagram is used to illustrate another example of the use of vehicle allocation system 1. For example... Figure 64 As shown, vehicle b100C can also pick up passengers at multiple pick-up points P1, P2, and P3 to travel to their destination.

[0610] According to the third embodiment described above, a vehicle allocation reservation unit b432 that creates pick-up and drop-off schedules and reserves vehicles based on facility reservation content, and a vehicle allocation management unit b433 that allocates vehicles reserved by the vehicle allocation reservation unit b432 according to the pick-up and drop-off schedule, can provide a pick-up and drop-off service that is linked to the reserved facility.

[0611] Users can reserve vehicles according to the pick-up and drop-off schedule generated by the pick-up and drop-off management device b400 based on facility reservation information, thus ensuring transportation to and from the facility. Furthermore, since the pick-up and drop-off schedule is generated based on facility reservation information, detailed information for vehicle reservation is not required, reducing hassle for users. Additionally, by providing pick-up and drop-off services as part of the facility's service, customer traffic can be increased; and by providing services to users, transportation costs can be reduced.

[0612] Users can obtain information such as vehicle allocation and delay status from the moving vehicle b100, and thus confirm the allocation and delay status and decide on subsequent actions.

[0613] By obtaining information about the user's travel status, vehicle delays, and arrival time from the moving vehicle b100, the facility can prepare to welcome the user upon arrival, thereby improving service.

[0614] Users can easily change or cancel their facility reservations and shuttle service reservations if the shuttle service is delayed.

[0615] Users can change passenger numbers and make reservations from the moving vehicle b100, thus reducing waiting time compared to making reservations upon arrival at the facility. Furthermore, by accepting passenger number changes and reservations in advance, the facility can smoothly guide users. Additionally, if vehicle b100 has accepted a reservation from a user, the facility can prioritize guiding users who have made pre-orders.

[0616] By obtaining user information from the moving vehicle b100, the facility can provide services tailored to the user's attributes. For example, it can prepare seats corresponding to the number of users, their gender, and age, and provide goods and services that match the user's preferences.

[0617] [Second variation of the third embodiment]

[0618] Hereinafter, a second variation of the third embodiment will be described. In the following description, parts having the same functions as those described in the third embodiment above will be labeled with the same names and reference numerals, and specific descriptions related to those functions will be omitted.

[0619] The following example illustrates how a service provider with partial or full access to the pick-up and drop-off management device b400 and facility terminal b200 can collectively manage the pick-up and drop-off of vehicle b100 to users. It should be noted that the pick-up and drop-off management device b400A includes, for example, a pick-up and drop-off management device b400, a service provider device b600, a service management device b700, and a vehicle management device b910.

[0620] [Service Provider]

[0621] Service providers may offer additional services beyond pick-up and drop-off to users before or during the pick-up and drop-off process. Figure 63 In the example shown, the service provider could be the person in charge of facilities such as airport b520, hotel b530, and restaurant b540, or the manager of vehicle b100. Alternatively, the service provider could be a mediator who, in addition to providing supplementary services, coordinates and manages the reservation schedules of vehicle b100, airport b520, hotel b530, restaurant b540, etc., in an overall manner.

[0622] The additional services provided by the service provider may include goods or services that the user can enjoy while traveling in vehicle b100, or services provided at shops or other service locations that the user needs to visit during their transportation. Goods or services enjoyed while traveling may include watching paid informational programs or receiving a massage inside vehicle b100. Additionally, the service provider may dispatch a service provider to vehicle b100 to provide goods or services that can be enjoyed while traveling. Furthermore, a service provision device may be installed in vehicle b100. This service provision device may be, for example, a massage device. The service provision device may also be a vending machine the size of vehicle b100.

[0623] Additionally, the service provider can suggest available services to users currently riding in vehicle b100 based on user information obtained by user information acquisition unit b175. For example, if the analysis of user information obtained by user information acquisition unit b175 indicates that the user's condition appears unwell, the service provider can also provide medication from the service provision device. Furthermore, the service provider can also have input / output unit b171 display or sound a suggestion to the user to visit nearby rest areas, medical facilities, pharmacies, etc.

[0624] Users can order additional services provided by the service provider before taking the vehicle b100 (e.g., when booking a ride) or during the ride in the vehicle b100.

[0625] When the order acquisition unit b176 receives an order for additional services from a user via the input / output unit b171, it sends the order details to the service provider device b600 that manages the additional services.

[0626] [Service Provider Device]

[0627] Figure 65 This is a functional structure diagram of service provider device b600. Service provider device b600 is, for example, a device capable of monitoring the status of multiple service providers and automatically responding to orders from users and service managers. Service provider device b600 includes, for example, a communication unit b610, an order processing unit b620, a status management unit b630, and a storage unit b650 (not shown).

[0628] The communication unit b610 communicates with the pick-up and drop-off management device b400 and others via the network NW. The order processing unit b620 processes service orders from users. The order processing unit b620 determines whether the content of the service order is service provision information that has already been sent to the pick-up and drop-off management device b400, and proceeds with the order processing if it is determined that it has not been sent. The status management unit b630 manages the status (appointment status, work status, etc.) of service providers registered with the service provider device b600, and provides service provision information to the service management device b700 and the pick-up and drop-off management device b400. The service management device b700 will be described later.

[0629] Service provider device b600 may send service provision information, including, for example, the following: service provision information is information associated with the services that the service provider is able to accept orders for.

[0630] [Service Provider Information]

[0631] • Identification ID (the ID that identifies the service provider)

[0632] User ID

[0633] • Necessary vehicle compartment information (information on the interior space required for service provision)

[0634] • Facility location information

[0635] • Service delivery location information (target facility information)

[0636] • Service provides time slot information (reservation information)

[0637] • User pick-up location

[0638] • Service status information (information corresponding to the implementation status and progress of the services provided by the service provider)

[0639] • User-defined information (e.g., adding information to service inputs, notes, etc.)

[0640] It should be noted that service status information corresponds to the implementation status of multiple additional services implemented within vehicle b100, such as the percentage of progress or the remaining time in minutes. Additionally, service status information can be represented by values ​​indicating states such as "before provisioning," "in progress," or "end of provisioning."

[0641] It should be noted that the communication unit b610 of the service provider device b600 can also switch the display content of the display device such as the input / output unit b171 based on the communication result. For example, the service provider device b600 displays "The start time of service provision is approaching" or "Service provision has started" on the input / output unit b171.

[0642] [Service Management Device]

[0643] Figure 66 This is a functional structure diagram of the service management device b700. The service management device b700 includes, for example, a communication unit b710, a service information acquisition unit b720, a vehicle determination unit b730, a planning decision unit b740, a route instruction unit b750, an authentication unit b760, a judgment unit b770, and a storage unit b800. The components other than the communication unit b710 and the storage unit b800 are implemented by executing programs (software) using hardware processors such as CPUs. Some or all of these components can also be implemented by hardware (circuit unit; including circuitry) such as LSIs, ASICs, FPGAs, and GPUs, or through the coordinated operation of software and hardware. The program can be pre-stored on storage devices such as HDDs and flash memory, or stored on removable storage media such as DVDs and CD-ROMs, and installed by mounting the storage media onto a drive device. The storage unit b800 is implemented using HDDs, flash memory, RAM, ROM, etc.

[0644] The communication unit b710 is, for example, a network interface card (NIC) for connecting to the network NW. The communication unit b710 communicates via the network NW with communication devices such as the vehicle management unit b170 of the vehicle b100, the service provider device b600, the service management device b700, and the vehicle management device b910, through a dedicated API (Application Programming Interface) provided by the service management device b700. The user-related information provided by the dedicated API does not include the user's personal information (e.g., name), but for example, the vehicle b100's identification information can be set as the user ID.

[0645] The service information acquisition unit b720 obtains service information from the communication devices of the vehicle allocation management unit b170, etc., of the vehicle b100 via the communication unit b710. The service information is, for example, the service utilization request information shown below.

[0646] [Service utilizes delegated information]

[0647] User ID

[0648] • Location information (latitude, longitude, altitude)

[0649] • Hope to utilize service ID

[0650] • We hope to utilize interval information

[0651] Information on the time period during which the user wishes to utilize the service.

[0652] Settlement and authentication information

[0653] In addition, the service information acquisition unit b720 can also obtain service provision information from the service provider device b600. The service information acquisition unit b720 obtains the location information corresponding to the service provision location, the service provider's identification information, and the user's identification information from the service provision information, and outputs them to the planning and decision-making unit b740.

[0654] The vehicle determination unit b730 determines the usable vehicle b100 based on the service utilization request information and vehicle information, and generates usable vehicle information b820. Specifically, the vehicle determination unit b730 compares the desired space (compartment), desired interval, and service utilization time period information contained in the service utilization request information with the location information and compartment utilization status contained in the vehicle information, and determines the vehicle b100 that meets the conditions contained in the service utilization request information in terms of location information and compartment utilization status.

[0655] The planning and decision-making department b740 determines the available services that the user can enjoy based on the available vehicle information b820 and the service provision information, and provides the information related to the determined available services to the vehicle allocation management unit b170 of the user's vehicle b100.

[0656] More specifically, the planning decision unit b740 sets the range in which the service provider occupies at least a portion (e.g., a compartment) of the vehicle b100 based on the available vehicle information b820 and the service provision information, and sets the desired range information in the service utilization entrustment information.

[0657] In addition, when multiple service providers sequentially provide services to a user, the planning decision unit b740 can also set intervals corresponding to each of the multiple service providers.

[0658] The planning and decision-making unit b740 includes, for example, an access point acquisition unit b742. The access point acquisition unit b742 acquires access points. Access points can be, for example, locations where users utilize supplementary services, or locations where users or service providers board and alight to receive supplementary services. The access points acquired by the access point acquisition unit b742 can be measured location information (latitude, longitude, altitude) or estimated location information.

[0659] As another function, the planning decision unit b740 can also update the usage range according to the instructions from the user of the vehicle b100, such that the usage range ends at the service provision location outside the vehicle. In this case, the planning decision unit b740 can also determine the operation plan according to the instructions from the user of the vehicle b100 (or automatically), use the communication unit b710 to send reservation information to the facilities at the service provision location outside the vehicle, use the communication unit b710 to receive the reservation results, and use the communication unit b710 to send the reservation results to the user's vehicle b100.

[0660] Furthermore, when the arrival time at the facility needs to be changed due to a user ordering additional services, the planning decision unit b740 sends an adjustment for the change in arrival time to the facility terminal b200 and the pick-up and drop-off management device b400 via the communication unit b710. In this case, the processing performed by the planning decision unit b740 is the same as the processing performed by the status management unit b435 of the pick-up and drop-off management device b400 in cases of arrival time delays or delays in arrival time at the destination; therefore, detailed explanations of the processing are omitted.

[0661] The route instruction unit b750 instructs the vehicle b100 on the route it should travel by sending the user's start and end positions and the service provider's start and end positions to the vehicle b100 via the communication unit b710.

[0662] The authentication department b760 performs authentication of the user based on communication with the vehicle management unit b170, and performs authentication at the start of service provision.

[0663] The determination department b770 determines whether the user and the service provider are using the vehicle b100.

[0664] The planning decision unit b740 uses the determination result of the judgment unit b770 to perform various processes. For example, the planning decision unit b740 may accept (update) a change in the service provision area only if the judgment unit b770 determines that both the user and the service provider are using vehicle b100. This could occur, for example, if the service provider proposes to the user to add a route or if the final destination is changed based on information provided to vehicle b100 to provide additional services. Furthermore, if the judgment unit b770 determines that the user is already using vehicle b100 (i.e., if a service extension or other service request has been made during service use) at the time the service information acquisition unit b720 receives the service use request information, the planning decision unit b740 may prioritize allocating the vehicle b100 to the user.

[0665] In the storage unit b800, in addition to user information b810 related to registered users and the aforementioned available vehicle information b820, service management information b830 is also stored. Service management information b830 includes, for example, service request management information b832, reservation management information b834, and ongoing service management information b836. In service request management information b832, service usage request information obtained by the service information acquisition unit b720 is recorded. In reservation management information b834, information such as reservation usage interval, reservation usage time period, route, and scheduled arrival time at the route is stored for each service. In ongoing service management information b836, service status information, service attributes, and service provider ID (service provider identification information) are registered. Service attributes, for example, are information that classifies the services that the service provider can provide when observed by the user receiving information from the service provider and the service management device b700, such as values ​​indicating the service provider's business type (food, retail, etc.) and the order of fee allocation.

[0666] The service status information maintained by the service management information b836 during execution is updated, for example, when the authentication process for service initiation is performed by the authentication unit b760. By managing the service management information b830, the service management device b700 can comprehensively manage the status of the users of the vehicle b100 (e.g., user information obtained by the input / output unit b171) and the status of the vehicle 100's operation plan. Furthermore, the determination unit b770 can also set the status attributes determined based on the user's usage information and the vehicle b100's operation information (e.g., information such as the user prioritizing arrival time and forgoing additional services) from the service status information as the determination result.

[0667] In addition, the status attributes determined based on the user's usage information and the vehicle b100's operation information include, in addition to the degree of arrival (e.g., earlier than scheduled, on time, later than scheduled) determined relative to the progress of the operation plan including additional services, values ​​representing the surrounding environment and driving status (e.g., rain, congestion, traffic restrictions, low SoC (State of Charge), malfunction, accident) determined based on the vehicle b100's sensing data.

[0668] [Vehicle Management Device]

[0669] Figure 67 This is a functional structure diagram of the vehicle management device b910 installed in vehicle b100. The vehicle management device b910 includes, for example, a communication unit b920, an authentication unit b930, and a vehicle management unit b950.

[0670] Communication unit b920 is a wireless communication device. Communication unit b920 communicates with service management device b700 via network NW. Authentication unit b930 performs authentication processing for service initiation based on instructions from service management device b700.

[0671] Vehicle management department b950 includes, for example, a usage status detection department b952, a usage permit department b954, and an authentication department b956. Vehicle b100 has one or more usable spaces (compartments), and the usage status detection department b952 detects the usage status of each compartment. For example, the usage status detection department b952 detects whether each compartment is in use. Vehicle b100 is not limited to ordinary passenger cars; it can also be a trailer, bus, van, or other vehicle of a size where each compartment in the divided interior can accommodate one or more passengers. The usage permit department b954, for example, allows the use of a pre-designated compartment, such as unlocking the door, upon successful authentication by the authentication department b956. The authentication department b956 performs authentication, such as verifying the identity of the service provider intending to board the vehicle.

[0672] The vehicle management device b910, for example, sends vehicle information, including the following, to the service management device b700.

[0673] [Vehicle Information]

[0674] Vehicle ID

[0675] • Location information (latitude, altitude, longitude)

[0676] • Utilization status of partitions

[0677] • Driving status (speed, acceleration, angular velocity, status of onboard equipment, etc.)

[0678] • Service provider information (service provider ID, information about the services being implemented, service implementation time, etc.)

[0679] Figure 68 This is a flowchart illustrating an example of the processing flow performed in the vehicle dispatch system b1A. It should be noted that the following example uses the scenario of "the service provider ordering an additional service during the ride, and the user disembarking at a destination different from the user's initial destination (the location where the additional service is provided)" to illustrate the processing flow.

[0680] First, the user authenticates themselves by connecting the input / output unit b171 of vehicle b100 to the authentication unit b760 of service management device b700 (step S300b). Next, the user sends service request information to service provider device b600 (step S301b). Service provider device b600 interprets the received service request information (step S302b) and sends reservation information to service management device b700 based on the interpreted service request information (step S303b).

[0681] The service management device b700 processes the vehicle dispatch service order based on the reservation information sent by the service provider device b600, and sends the order information to the vehicle management device b910 (step S304b). The vehicle management device b910 uses the received order information to cause the pick-up and drop-off management device b400 to generate a pick-up and drop-off reservation (step S305b).

[0682] The service management device b700 initiates vehicle allocation service to the user based on the order information (step S306b), and sends the service start notification to the service provider device b600 and the vehicle management device b910. The vehicle management device b910 recognizes the service start and notifies the vehicle b100, etc., using a dedicated API (step S307b).

[0683] Service provider device b600 begins to acquire and update vehicle allocation information for vehicle b100 (step S308b). Vehicle b100 begins to move towards the vicinity of the pick-up location (step S309b). Service management device b700 determines the pick-up location and sends it to service provider device b600 (step S310b). Service provider device b600 notifies vehicle b100 of the pick-up location (step S312b) and sends a display control instruction to input / output unit b171 via vehicle management device b910 (step S313b). Vehicle management device b910 switches the vehicle display to input / output unit 171b (step S314b).

[0684] Vehicle management device b910 allows users to board vehicle 100 at the pick-up location (step S315b), and users board vehicle b100 (step S316b). Service provider device b600 updates vehicle status information (step S317b), and vehicle management device b910 updates sensor information (step S318b).

[0685] The service provider device b600 generates information related to the additional services it can provide and outputs it to the input / output unit b171, etc. (step S319b). The user selects and orders the additional services (step S320b). The service provider device b600 updates the vehicle status and service utilization request information related to the provided additional services, and sends the updated content to the service management device b700 (step S321b).

[0686] The service management device b700 processes the changes in the path and destination accompanying the provision of additional services and sends the processing results to the vehicle management device b910 (step S322b).

[0687] The vehicle management device b910 notifies the service provider device b600 that the destination has been reached (step S323b). The user disembarks from the vehicle b100 (step S324b). The service provider device b600 begins providing additional services to the user (step S325b). This concludes the processing of this flowchart.

[0688] For example, the status management unit b435 can also use the communication device b410 to send information for accepting vehicle allocation changes and information for confirming vehicle allocation cancellations to the user terminal b300. Furthermore, the user can also notify the user terminal b300, for example, of a change in pick-up location, to the pick-up management device b400. The status management unit b435 of the pick-up management device b400 can also notify the vehicle b100 of the changed pick-up location, indicating a route change, and send the change information to the user terminal b300.

[0689] Furthermore, all or part of the structure of the pick-up and drop-off management device b400 can also be mounted on the vehicle b100. Thus, for example, a user can directly request pick-up and drop-off service from the vehicle b100 using the user terminal b300. Additionally, if the requested vehicle b100 is unavailable, the vehicle b100 can also transmit the pick-up and drop-off request to another vehicle b100.

[0690] In addition, when the pick-up and drop-off management device b400 receives the arrival time of the pick-up location specified by the user using the user terminal b300 and the arrival time of the destination, it can also create a pick-up and drop-off schedule based on this information and facility reservation information.

[0691] Additionally, the user terminal b300 can periodically send information indicating the user's location as determined by the GNSS receiver b360 to the pick-up and drop-off management device b400. Based on the received information, the pick-up and drop-off management device b400 tracks the current location of the user and the vehicle b100, sets the pick-up location as the meeting point of the user and vehicle b100, and changes the set pick-up location to the meeting point of the user and vehicle b100. Furthermore, the vehicle b100 can also set the meeting point of the user and vehicle b100 as the pick-up location and set its own path based on the user's location information and its own location information received from the pick-up and drop-off management device b400.

[0692] Furthermore, the user terminal b300 can accept vehicle cancellation instructions through various operations. For example, the user terminal b300 receives information confirming vehicle cancellation and reports it to the user using the output unit b330. Subsequently, the user terminal b300 can also receive extension instructions, vehicle cancellation instructions, etc. from the user using the input unit b320. If no instructions are input using the input unit b320 within a certain period of time, it can also accept both facility reservations and vehicle reservations.

[0693] In addition, if a return vehicle has also been reserved, the user can pre-book the arrival time at the pick-up location, or use the user terminal b300 to request a vehicle to be picked up by the pick-up management device b400 when leaving the facility.

[0694] Furthermore, if there are users with similar pick-up and drop-off schedules before the vehicle allocation time, the pick-up and drop-off management device b400 can also use the same vehicle to create pick-up and drop-off schedules for different groups of users to ride together, and allocate vehicle b100. For example, this could involve picking up and dropping off users who arrived at the same airport on the same flight to the same hotel, or picking up and dropping off users from the same hotel to other nearby restaurants. By using vehicle b100 to achieve shared rides in this way, the facility can reduce vehicle allocation costs. In this case, the facility can also provide rewards to users.

[0695] Alternatively, the service management device b700 can replace the pick-up and drop-off management device b400 to manage vehicle reservations, or both the pick-up and drop-off management device b400 and the service management device b700 can be used to manage vehicle reservations.

[0696] <Fourth Implementation Method>

[0697] Next, the fourth embodiment will be described. This fourth embodiment is an implementation of a vehicle system to which the vehicle shown in the first embodiment is applicable. Furthermore, the autonomous vehicle in the fourth embodiment is, for example, a vehicle that requires virtually no driving operation. In the vehicle system, an autonomous vehicle is used to provide a guidance service that takes the user to a shop selected by the user. Hereinafter, an example of a food shop being guided by the autonomous vehicle will be used. The autonomous vehicle prepares samples of the goods, dishes, and their ingredients that will be offered at the guided shop. The user can sample the food before selecting a shop. This includes offering food in restaurants, selling goods in specialty shops, etc.

[0698] Figure 69 This is a structural diagram of vehicle system c1. Vehicle system c1 includes one or more autonomous vehicles c100 and one or more terminal devices c200 used by one or more product providers P. These components can communicate with each other via network NW. Network NW includes the Internet, WAN, LAN, public lines, carrier equipment, dedicated lines, wireless base stations, etc.

[0699] The autonomous vehicle c100 is, for example, a vehicle with four or more wheels that multiple users U can ride in, but it can also be a motorized two-wheeler or other vehicle. The autonomous vehicle c100 carries food samples and moves between promotional points such as in front of stations and tourist attractions, and uses autonomous driving to bring users U to the store R that provides the food samples.

[0700] Terminal devices c200 include, for example, smartphones, tablets, and personal computers.

[0701] Figure 70 This is a diagram showing the structure inside the autonomous vehicle c100. Figure 70 This is a view of the autonomous vehicle C100 from above. Inside the autonomous vehicle C100 are a shelf unit C102, a seat C104, and a touch panel C106.

[0702] The shelf section c102, which forms part of the vehicle's compartments, is itself composed of multiple vehicle compartments and has a mounting surface capable of holding multiple food samples SM1, SM2, etc. On the mounting surface of the shelf section c102, there are mounting spaces (areas) AR1, AR2, etc., which serve as vehicle compartments, for example, depending on the type of food sample or the store. The illustrated areas AR1, AR2, etc., are mounting spaces allocated to stores R1, R2, etc., and hold food samples SM1, SM2, etc. For example, sample numbers 1, 2, etc., are assigned to areas AR1, AR2, etc., and labels TG indicating the assigned sample numbers are installed. It should be noted that the type and quantity of food samples placed in each area can be arbitrarily determined by the store, and multiple types of food samples can be placed. Furthermore, the shelf section c102 may also be equipped with refrigeration or insulation functions on the mounting surface. It should be noted that, in the following description, a single division on the autonomous vehicle c100 is defined as a compartment of the autonomous vehicle c100. However, multiple divisions consisting of multiple divisions (e.g., storage spaces) can also be treated as a single compartment. That is, as long as the compartments can recognize each other, their respective inclusion relationships and independence can be appropriately determined according to their purpose and the managers of each compartment.

[0703] The touch panel c106 is, for example, a touch panel display device. A store screen IM, including store information, is displayed on the touch panel c106 in a correspondence with the food samples placed on the shelf c102. Figure 71 This diagram illustrates an example of a store screen IM. The store information includes images and illustrations of food samples for each store, the store name, illustrations of the food offered in each store, and advertisements for each store. The IM screen displays a switching image IM0 that receives an image switching instruction, and multiple store screens IM1, IM2, etc., corresponding to multiple stores R1, R2, etc. For example, a portion of each store screen IM1, IM2, etc., displays the corresponding sample number 1, 2, etc. Store screens IM1, IM2, etc., can display all store information simultaneously, or can switch automatically or upon user interaction with the touch panel c106. For example, store screens IM1, IM2, etc., initially display illustrations of food samples, and upon receiving a touch operation on the switching image IM0, switch to advertisements for each store. The touch panel c106 is an example of an "operation unit".

[0704] Additionally, a GO switch SW1 and a DELI switch SW2 are installed in or near a portion of the IM1, IM2, etc. screens of each store. The GO switch SW1 indicates movement to the corresponding store. The DELI switch SW2 indicates delivery to the corresponding store. The GO switch SW1 and DELI switch SW2 are another example of an "operation unit." Furthermore, the store IM1 associated with the GO switch SW1 is an example of a "route location." Delivery to the corresponding store is an example of "delivery content."

[0705] Next, refer to Figure 72 The functional structure of the autonomous vehicle C100 is explained. Figure 72 This is a functional structure diagram of an autonomous vehicle c100. In addition to the aforementioned touch panel c106, the autonomous vehicle c100 also includes a store guidance device c108, an external monitoring unit c110, a communication device c120, a navigation device c130, a lane recommendation device c140, an autonomous driving control unit c150, a drive force output device c160, a braking device c162, and a steering device c164. Each of the external monitoring unit c110, communication device c120, navigation device c130, lane recommendation device c140, autonomous driving control unit c150, drive force output device c160, braking device c162, and steering device c164, for example, possesses the features described in the second embodiment above. Figure 26 The external monitoring unit a210, communication device a220, navigation device a230, lane recommendation device a240, automatic driving control unit a250, drive force output device a260, braking device a262, and steering device a264 have the same structure, therefore detailed descriptions are omitted here. It should be noted that in the navigation device c130, the destination can also be set by the shop guidance device c108. The navigation device c130 and lane recommendation device c140 are examples of a "route setting unit". Furthermore, regarding the automatic driving processing in the fourth embodiment, the method described in the first embodiment is referenced. Figure 3 And related explanations, detailed explanations omitted.

[0706] The store guidance device c108 has one or more processors such as a CPU and an MPU, as well as various storage devices. It should be noted that the store guidance device c108 can also be implemented as part of the automatic driving control unit c150. Based on the user U's operation of the touch panel c106, the store guidance device c108 instructs the navigation device c130 to guide users to the store specified by the user U. Additionally, the store guidance device c10g can also, based on the user U's operation of the touch panel c106, send information representing the instructions from the user U to the terminal device c200 using the communication device c120. It should be noted that the store guidance device c108 can also include the touch panel c106.

[0707] It should be noted that in the navigation device c130, the destination can also be set by the store guidance device c108. The navigation device c130 and the recommended lane determination device c140 are examples of a "route setting unit".

[0708] Next, refer to Figure 73 An example of a processing action in an autonomous vehicle c100 will be explained. Figure 73 This is a flowchart illustrating an example of processing actions in an autonomous vehicle c100. This processing is an example of a situation where user U performs an operation on the store screen IM2.

[0709] For example, when the store guidance device c108 receives a touch operation from user U on the store screen IM2 displayed on the touch panel c106 (step S1c), it switches the screen of the touched store screen IM2 (step S2c). For example, after tasting the food sample, user U can view information related to the store corresponding to the store screen IM2 displayed on the touch panel c106 and decide whether to go to that store.

[0710] Next, the store guidance device c108 assumes, for example, that a touch operation has been performed on the touch panel c106 to select the GO switch SW1 for store R2 (step S3c). As a result, the store guidance device c108 establishes corresponding identification information (e.g., the store ID of store R2) based on the GO switch SW1, and displays an input screen on the touch panel c106 to receive information related to store guidance. This information includes the number of people going to the store, the desired departure time, etc. Upon input of this information, the store guidance device c108 sets the specified store R2 as the destination and instructs the navigation device c130 to begin autonomous driving (step S4c). The navigation device c130 outputs the predicted arrival time to store R2, outputs the result to the store guidance device c108, and outputs the route information to store R2 to the lane recommendation device c140. In addition, the store guidance device c108 uses the communication device c120 to send information related to the input store guidance, the arrival prediction time derived by the navigation device c130, etc., to the terminal device c200 of the designated store R2 (step S5c).

[0711] Next, the store guidance device c108 assumes, for example, that a touch operation on the DELI switch SW2 of store R2 has been received on the touch panel c106 (step S6c). As a result, the store guidance device c108 displays the order screen of store R2 on the touch panel c106 (step S7). The order screen displays the order menu and its associated costs, including buttons for ordering specific menu items, specifying the order quantity, and input fields for specifying the collection location and collection time. The store guidance device c108 then uses the communication device c120 to send the information entered on the order screen (hereinafter referred to as order information) to the terminal device c200 of the designated store R2 (step S8c). This concludes the processing of this flowchart.

[0712] Next, refer to Figure 74 The utilization modes of the autonomous vehicle C100 are explained. Figure 74 This diagram illustrates the usage of the autonomous vehicle c100. Before station A, the autonomous vehicle c100 is in standby mode. Standby mode refers to the state where food samples can be sampled inside the vehicle and where it can pick up or drop off food samples from the store that provided them. In standby mode, the digital sign c170 installed on the outside of the autonomous vehicle c100 displays the option to sample food inside the vehicle. It should be noted that the digital sign is an electronic display device such as a monitor or an electronic display device including a speaker.

[0713] (1) User U, who has arrived at station A, boards the waiting autonomous vehicle c100. (2) After tasting a food sample in the autonomous vehicle c100, user U touches the GO switch SW1 corresponding to the store R3 they wish to visit. (3) The autonomous vehicle c100 then drives itself to store R3, transporting user U there. The digital sign c170 displays "Moving". (4) User U disembarks from the autonomous vehicle c100 and enters store R3.

[0714] (5) Afterwards, the autonomous vehicle c100 can wait for user U in front of store R3 until the dining and shopping in store R3 is finished, and then take user U to station B. Alternatively, it can go to station B without waiting for user U. It can also pick up other users U who have come out of store R and take them to station B. Station B is, for example, the station closest to store R3 or the station adjacent to station A. In addition, the autonomous vehicle c100 can also wait in front of store R3 for a certain period of time. (6) Then, the autonomous vehicle c100 waits at station B for a certain period of time. During the waiting period, food samples that can be tasted in the vehicle are displayed on the digital sign c170. (7) User U who has gotten off at station B gets into the waiting autonomous vehicle c100, tastes the food samples in the autonomous vehicle c100, and touches the DELI switch SW2 corresponding to store R3 that wants to order delivery. (8) Thus, the autonomous vehicle c100 sends the order information to the terminal device c200 of store R3. (9) Then, store R3 uses the store's delivery motorcycle C300 to deliver the goods to user U.

[0715] On the other hand, (10) even if no user U appears after a certain period of time from when the autonomous vehicle c100 stops in front of station B, the autonomous vehicle c100 moves to station A and waits.

[0716] (11) Moreover, even if no user U appears after a certain period of time from when the car is parked in front of station A, the autonomous vehicle c100 moves to station B and waits.

[0717] Through this usage model, user U can sample food and then go to the store R that provides the samples. Therefore, even when visiting unfamiliar areas due to travel or work, users can still reach their favorite specialty stores, restaurants, and other shops. Furthermore, since the autonomous vehicle c100 transports user U to store R, it significantly improves user convenience, especially when the desired specialty store or restaurant is located in a difficult-to-reach area or when the user is unsure of the route.

[0718] Furthermore, the movement of the autonomous vehicle C100 between multiple promotional points can encourage user engagement. While the autonomous vehicle C100 is moving between these points, digital signage C170 can be used to display guidance services offered by the autonomous vehicle C100, as well as audio, animation, and still images informing users about delivery services. This allows for widespread dissemination of information to users unaware of the services offered.

[0719] According to the fourth embodiment described above, the system includes an automatic driving control unit c150 for autonomous driving of the vehicle, a shelf c102 for holding food samples, and a first switch (GO switch SW1) for indicating movement to a store. When the first switch is operated, the automatic driving control unit c150 moves the vehicle to the designated store, which improves the convenience for the user U when moving to the store that provides food.

[0720] Furthermore, the convenience for the user U can be further improved by having a second switch (DELI switch SW2) for instructing the store to send food samples to the source of the food sample, and a communication device c120 for sending the sent content to the terminal device of the store management when the second switch is operated.

[0721] [First variation of the fourth embodiment]

[0722] Next, a first variation of the fourth embodiment will be described. Figure 75 This is a structural diagram of the vehicle system c2 of the first variation of the fourth embodiment. The vehicle system c2 includes one or more first vehicles c500, one or more second vehicles c600 and c700, and one or more terminal devices c200 used by one or more product providers P. These components can communicate with each other via a network NW. The first vehicle c500 has the same structure as the autonomous driving vehicle c100. The second vehicles c600 and c700 are structures obtained by removing the shelf section c102, touch panel c106, and store guidance device c108 from the autonomous driving vehicle c100, and have seats for users U to sit on.

[0723] The first vehicle, c500, carries food samples and moves between promotional points such as the station area and tourist attractions. User U can board the first vehicle c500, sample the food samples, and use the touch panel c106, GO switch SW1, and DELI switch SW2 to request guidance and delivery to store R. When user U requests guidance to store R, the second vehicles c600 and c700 pick up user U from the first vehicle c500, allowing user U to board and be driven to store R via automatic driving. DELI switch SW2 is an example of a "fourth switch."

[0724] The shop guidance device c108 of the first vehicle c500 can also use the communication device c120 to receive current location information successively sent from multiple second vehicles c600, c700, etc., and save it in the storage device. The first vehicle c500 can also refer to the storage device to determine the optimal second vehicle from among the multiple second vehicles c600, c700, etc., as the vehicle to take the user U to the designated shop R. The optimal second vehicle includes, for example, the second vehicle closest to the first vehicle c500 that is not currently being used for user pick-up and drop-off and that can accommodate a specified number of users U, and the second vehicle that can arrive at the first vehicle c500 earliest.

[0725] Next, refer to Figure 76 An example of the processing method handled by the vehicle system c2 will be explained. Figure 76 This is a sequence diagram illustrating an example of a processing method handled by vehicle system c2.

[0726] For example, the first vehicle c500 may receive a touch operation on the touch panel c106 for the GO switch SW1 of store R3 (step S101c). As a result, the store guidance device c108 displays an input screen on the touch panel c106 to receive input related to store guidance information. Furthermore, the store guidance device c108, referring to its own storage device, retrieves the optimal second vehicle from among a plurality of second vehicles c600 and c700 (step S102c). Then, the store guidance device c108 sends information indicating the location of the first vehicle c500 to the optimal second vehicle (e.g., second vehicle c600) obtained through the retrieval, and entrusts the pick-up and drop-off of user U to the designated store R3 (step S103c).

[0727] The second vehicle c600, having received a pick-up request from the first vehicle c500, goes to the parking location of the first vehicle c500 to pick up the user U. For example, if the optimal second vehicle c600 obtained through retrieval is not near the first vehicle c500 (e.g., within a 5m radius), the navigation device c130 of the second vehicle c600 sets a path for moving to the vicinity of the first vehicle c500 based on information indicating the location of the first vehicle c500 (step S104c). The automatic driving control unit c150 enables the second vehicle c600 to drive automatically based on the set path. Then, after the second vehicle c600 parks near the first vehicle c500, the navigation device c130 of the second vehicle c600 sets the destination of the second vehicle c600 to shop R3 based on the request from the first vehicle c500 (step S105c). After the user U boards the second vehicle c600, the automatic driving control unit c150 enables the second vehicle c600 to drive automatically to shop R3.

[0728] The navigation device c130 of the second vehicle c600 uses the communication device c120 of the second vehicle c600 to send information such as the number of users U guiding to store R3 and the predicted arrival time to store R3 to the terminal device c200 (step S106c). The terminal device c200 displays the received information on the display unit and notifies the product provider P (step S107c).

[0729] Next, the first vehicle c500, for example, assumes that it receives a touch operation on the DELI switch SW2 of store R3 on the touch panel c106 (step S10c8). As a result, the store guidance device c108 displays the order screen of store R3 on the touch panel c106. The store guidance device c108 uses the communication device c120 to send the entered order information to the terminal device c200 of the designated store R3 (step S109c). The terminal device c200 displays the received information on the display unit and notifies the product provider P (step S110c).

[0730] Next, refer to Figure 77 The utilization modes of the first vehicle c500 and the second vehicles c600 and c700 are described. Figure 77 This diagram illustrates the usage of the first vehicle c500 and the second vehicles c600 and c700. The first vehicle c500 is parked in front of station A. The number plate c170 on the first vehicle c500 indicates that food samples can be tasted inside the vehicle.

[0731] (21) User U1, who has arrived at Station A, enters the first vehicle c500 parked at Station A. (22) After tasting the food sample in the first vehicle c500, user U1 touches the GO switch SW1 corresponding to the store R4 that he wants to visit, and gets off the first vehicle c500.

[0732] The store guidance device c108 of the first vehicle c500 selects the best second vehicle c600 from multiple second vehicles c600, c700, etc., and sends information to the second vehicle c600 indicating the parking position of the first vehicle c500. (23) The second vehicle c600 moves to station A where the first vehicle c500 is parked. (24) Then, the user U1 gets into the second vehicle c600 that comes to meet him. (25) The second vehicle c600 drives automatically to the designated store R4 according to the instructions of the first vehicle c500 and transports the user U1 to the store R4. Here, the digital sign c170 of the second vehicle c600 shows "moving". (26) The user U1 gets off the second vehicle c600 and enters the store R4.

[0733] (27) Afterwards, the second vehicle c600 may wait in front of shop R4 until the dining and shopping activities in shop R4 are completed, and then transport user U1 to station A. Alternatively, it may pick up other users U2 who have exited shop R4 and transport them to designated locations. Furthermore, if the second vehicle c600 receives a pick-up / drop-off request from the first vehicle c500, it may return to station A. It should be noted that the second vehicle c600 may also wait in front of shop R4 for a certain period of time.

[0734] Assume that while user U1 is being picked up from store R4 by the second vehicle c600, user U3 gets off at station A. At this time, since the second vehicle c600 is picking up and dropping off the customer at the store, the first vehicle c500 is parked at station A. (28) User U3 gets into the first vehicle c500. (29) After tasting the food sample in the first vehicle c500, user U3 touches the GO switch SW1 corresponding to the store R5 that he / she wants to visit, and gets off the first vehicle c500.

[0735] The store guidance device c108 of the first vehicle c500 selects the best second vehicle c700 from multiple second vehicles c600, c700, etc., and sends information to the second vehicle c700 indicating the parking position of the first vehicle c500. (30) The second vehicle c700 moves to station A where the first vehicle c500 is parked. (31) Then, the user U3 gets into the second vehicle c700 that comes to meet him. (32) The second vehicle c700 drives automatically to the designated store R5 according to the instructions of the first vehicle c500, and transports the user U3 to the store R5. Here, the digital sign c170 of the second vehicle c700 shows "moving". (33) The user U3 gets off the second vehicle c700 and enters the store R5.

[0736] (34) Afterwards, the second vehicle c700 may wait in front of shop R54 until the dining and shopping at shop R5 is finished, and then transport user U3 to station A. Alternatively, it may pick up other users U4 who have exited shop R5 and transport them to designated locations. Furthermore, if the second vehicle c700 receives a pick-up / drop-off request from the first vehicle c500, it may return to station A. It should be noted that the second vehicle c700 may also wait in front of shop R5 for a certain period of time.

[0737] With this utilization method, since the first vehicle c500 carrying food samples is parked in a designated location, the replenishment and replacement of food samples become simple, and the hygiene of the food samples can be improved. Furthermore, since nearby autonomous vehicles can be used as a second vehicle, a vehicle system c2 that can easily suppress the number of first vehicles can be implemented.

[0738] According to the fourth embodiment described above, the system includes: a first vehicle c500, which has a shelf c102 capable of holding food samples and a third switch (GO switch SW1) for calling up a second vehicle c600, c700... which is an autonomous driving vehicle; and the second vehicles c600, c700... which are called up by operating the third switch, pick up the user from the first vehicle c500, and take the user to a designated store by autonomous driving. Thus, the first vehicle c500 can be kept parked in a designated position while the second vehicles c600, c700... guide the user to the store.

[0739] While an example of placing multiple food samples SM1, SM2, etc. on the shelf section c102 is given, it is also possible to place sample items other than food samples (e.g., beverage sample containers, daily necessities, cosmetics, fragrances, etc.).

[0740] <Fifth Implementation Method>

[0741] Next, the fifth embodiment will be described. In the fifth embodiment, embodiments of the event-based vehicle matching device, event-based vehicle matching method, procedure, and management system applicable to the vehicle of the first embodiment will be described. It should be noted that in the following description, it is assumed that the vehicle used in the event-based vehicle matching system including the event-based vehicle matching device is an autonomous vehicle. An autonomous vehicle is a vehicle capable of automatically controlling at least one of its acceleration, deceleration, and steering. An autonomous vehicle can be manually driven by a passenger. Furthermore, an autonomous vehicle includes a vehicle capable of operating unmanned. Additionally, the vehicle used in the event-based vehicle matching system can also be a manually driven vehicle. Furthermore, the event-based vehicle matching system is an example of a "management system."

[0742] Figure 78 This is a structural diagram of the event-based vehicle matching system d1 according to the fifth embodiment. The event-based vehicle matching system d1 includes an event-based vehicle matching device d100, one or more vehicles d200, and a terminal device d300 used by the owners O of the one or more vehicles d200. These components can communicate with each other via a network NW. The network NW includes the Internet, WAN, LAN, public lines, carrier equipment, dedicated lines, wireless base stations, etc.

[0743] [Event vehicle matching device]

[0744] The event vehicle matching device d100 includes, for example, a communication unit d110, a display unit d120, a display control unit d130, an event vehicle candidate decision unit d140, an event notification unit d150, an instruction unit d160, and a storage unit d170. The display control unit d130, the event vehicle candidate decision unit d140, the event notification unit d150, and the instruction unit d160 are implemented, for example, by a processor such as a CPU executing a program (software) stored in the storage unit d170. Alternatively, some or all of these functional units can be implemented by hardware (circuit unit; including circuitry) such as LSI, ASIC, FPGA, and GPU, or through the coordinated use of software and hardware. The program can be pre-stored in the storage unit d170 such as an HDD or flash memory, or stored on a removable storage medium such as a DVD or CD-ROM, and installed in the storage unit d170 by mounting the storage medium to a drive unit (not shown). Furthermore, a structure that combines part or all of the event vehicle candidate decision unit d140 and the event notification unit d150 is an example of an "adjustment unit". Additionally, the event notification unit d150 is an example of a "notification unit".

[0745] The communication unit d110 is, for example, a network card used for connecting to the network NW. The communication unit d110 communicates with the vehicle d200, the terminal device d300, and other external devices via the network NW.

[0746] Display unit d120 is an LCD, OLED, or similar display device. Display unit d120, under the control of display control unit d130, displays various information related to event dispatch to, for example, the administrator of event dispatch device d100. Additionally, display unit d120 may also have a touch panel-type receiving unit that accepts information input and confirms operations by touching the display screen with fingertips.

[0747] The display control unit d130 controls the display unit d120 by displaying various information related to event vehicle allocation. Additionally, the display control unit d130 receives input from managers or other personnel via the display screen of the display unit d120 and determines operation-related information. For example, the display control unit d130 receives information from managers or other personnel related to the event being held, and information related to the area where the event is being held. Events include large-scale or medium-scale gatherings with limited durations, such as music festivals (festivals) and food festivals; seasonal events such as the first shrine visit of the New Year, flower viewing, sea bathing, and skiing; major sporting events such as the Olympics; expositions; and various events such as shrine visits by local public organizations or regional businesses. The area is, for example, an area where multiple vehicles can park. Details regarding the functions of the display control unit d130 will be described later.

[0748] The event vehicle candidate decision unit d140 receives information related to the event and the region where the event will be held from the display control unit d130. Referring to the vehicle allocation table d173 stored in the storage unit d170, it determines the vehicle attributes and the number of vehicles for each attribute to participate in the event. Details regarding the function of the event vehicle candidate decision unit d140 will be described later.

[0749] The event notification unit d150 notifies one or both of the vehicles 200 and their owner O (terminal devices d300) of information related to the event and inquires whether the vehicle 200 will participate in the event as a service provider, for vehicles 200 selected by the event vehicle candidate decision unit d140. The owner O may be a service manager who oversees the provision of services by vehicle d200, or a passenger of vehicle d200. The event notification unit d150 also receives responses to the inquiries. Details regarding the functions of the event notification unit d150 will be described later.

[0750] When the vehicle d200, which is providing service during an event, travels near the event venue area, the instruction unit d160 assigns a parking location within that area and instructs the vehicle d200 or its owner O on information related to the assigned location. "Near the event venue area" refers to a distance within a specified range (e.g., within 100m) from the event venue corresponding to the area ID. Details regarding the function of the instruction unit d160 will be described later.

[0751] The storage unit d170 is implemented using HDD, flash memory, RAM, ROM, etc. The storage unit d170 stores, for example, map information d171, event table d172, vehicle allocation table d173, vehicle attribute table d174, vehicle information database d175, notification result management information d176, parking location management information d177, and other information.

[0752] [Vehicle] Vehicle d200 is, for example, a vehicle with four or more wheels, but it can also be a motorized two-wheeled vehicle or other vehicles. In addition, vehicle d200 can also be, for example, a towing vehicle that can tow and unload a cargo box, or a vehicle that is integrated with the cargo box. Figure 79This is a structural diagram of the vehicle d200 according to the fifth embodiment. The vehicle d200 includes, for example, an external monitoring unit d210, a communication device d220, a navigation device d230, a lane recommendation device d240, an automatic driving control unit d250, a drive force output device d260, a braking device d262, and a steering device d264. The automatic driving control unit d250 includes, for example, a processor such as a CPU that executes programs (software) stored in a storage unit (not shown) within the vehicle d200. Each of the external monitoring unit d210, communication device d220, navigation device d230, lane recommendation device d240, automatic driving control unit d250, drive force output device d260, braking device d262, and steering device d264 has, for example, the features described in the second embodiment above. Figure 26 The external monitoring unit a210, communication device a220, navigation device a230, lane recommendation device a240, automatic driving control unit a250, drive force output device a260, braking device a262, and steering device a264 have the same structure, therefore detailed descriptions are omitted here. It should be noted that in the fifth embodiment, HMId232 displays event notification information and inquiry information from the event vehicle matching device d100 on the screen, and can also notify via sound. Furthermore, HMId232 can also receive response information to inquiries operated by passengers and send the received response information to the event vehicle matching device d100. Additionally, navigation control device d236 can also send the position of vehicle d200 determined by GNSS receiver d234 to event vehicle matching device d100 at a predetermined time. Regarding the automatic driving processing in the fifth embodiment, the method described in the first embodiment is referenced. Figure 3 And related explanations, detailed explanations omitted.

[0753] [Terminal Device]

[0754] return Figure 78 The terminal device d300 is, for example, a smartphone, tablet, or personal computer. In the terminal device d300, for example, for launching an application or browser that utilizes the event matching system, the services described below are supported. In the following description, it is assumed that the terminal device d300 is a smartphone and the application (event matching application) is running.

[0755] Terminal device d300 includes, for example, a communication unit d310, an information acquisition unit d320, and a display unit d330. The communication unit d310 is, for example, a network card for connecting to a network NW. The communication unit d310 communicates with the event dispatching device d100 and other external devices via the network NW.

[0756] The information acquisition unit d320 is implemented by executing a program (software) stored in a storage unit (not shown) using a processor such as a CPU. Alternatively, the information acquisition unit d320 can also be implemented using hardware (circuit unit; including circuitry) such as LSI, ASIC, FPGA, or GPU, or through a combination of software and hardware. The program can be pre-stored in the storage unit or stored on a removable storage medium such as a DVD or CD-ROM, and installed in the storage unit by mounting the storage medium to a drive device. For example, the information acquisition unit d320 acquires event-related information and query information from the event matching device d100. The information acquisition unit d320 achieves this function, for example, by activating an event matching application installed on the terminal device d300. Furthermore, the information acquisition unit d320 can also have the function of acquiring or sending emails sent from the event matching device d100 using email software installed on the terminal device d300.

[0757] Display unit d330 is an LCD, OLED, or similar display device. Display unit d330 displays event-related information and query information acquired by information acquisition unit d320. Additionally, display unit d330 may also have a touch panel-type receiving unit function, capable of receiving information operated by the owner O relative to the displayed content. The operated information is, for example, a response to a query. Display unit d330 transmits the received response information to event dispatching device d100 via communication unit d310.

[0758] [Specific processing details in the event-based vehicle matching system d1 of the fifth embodiment]

[0759] The following describes the specific processing content of the event vehicle allocation system d1 in the fifth embodiment. When the event vehicle allocation device d100 receives an instruction from the administrator or others to perform the event vehicle allocation processing in the first embodiment, it displays the event vehicle allocation setting screen IM1 on the display unit d120.

[0760] Figure 80 This diagram illustrates an example of the event vehicle allocation setting screen IM1. The event vehicle allocation setting screen IM1 shows an event venue designation area d410 for specifying the event venue (area), an event designation area d412 for specifying the event, an event duration designation area d414 for specifying the event duration, and a confirmation operation area d416 for determining whether to execute or cancel vehicle allocation based on input content. It should be noted that the layout of the event vehicle allocation setting screen IM1 is not limited to the displayed items. Figure 71 For example. Additionally, regarding the other screen IMx (x: a natural number greater than 2) as described below, the layout and items can also be changed arbitrarily.

[0761] The display control unit d130 receives event-related information input to the event venue designated area d410 via operator input. The display control unit d130 displays a map information button in the event venue designated area d410. When the administrator selects the map information button, the map information contained in the map information d171 stored in the storage unit d170 is displayed on the display unit d120. Here, the map information d171 includes, for example, road information relative to each road represented using nodes and lines, traffic restriction information, residential information (address and postal code), and facility information. The road information includes information indicating the road type (e.g., highway, toll road, national highway, prefectural road), the number of lanes, the area of ​​emergency stopping lanes, the width of each lane, the road gradient, the road location (including three-dimensional coordinates of longitude, latitude, and altitude), the curvature of lane curves, the location of lane merging and branching points, and road signs. Additionally, map information d171 may also include identification information (area ID) for identifying the parking area where vehicle d200 is parked, as well as information related to the location and size of each area ID.

[0762] The display control unit d130 can also display map information on the display unit d120, and accept the location touched by the administrator as input for the event venue.

[0763] Additionally, the display control unit d130 accepts information about events input into the event designation area d412 via operator input. For example, the display control unit d130 displays a list box containing multiple pre-defined events in the event designation area d412, and accepts information about an event selected by the administrator from among the multiple events. The events displayed in the list box are stored in the event table d172.

[0764] Figure 81 This diagram illustrates an example of the contents of event table d172. In event table d172, a correspondence is established between event content and the event ID that identifies the event. For example, the event "Food Festival" is associated with event ID "I002".

[0765] Additionally, the display control unit d130 accepts information about the event period input into the event period designation area d414, which is determined by the administrator's operation input. For example, the display control unit d130 accepts date information by selecting the start and end dates of the event from a list box.

[0766] In addition, the display control unit d130 accepts the execution of the event dispatch by accepting the selection of the OK button in the operation area d416, and confirms the cancellation of the event dispatch by accepting the selection of the Cancel button.

[0767] The event vehicle candidate decision unit d140, based on the information received by the display control unit d130 regarding the region and event-related information, refers to the vehicle allocation table d173 stored in the storage unit d170, adjusts the vehicle attributes and the number of each vehicle attribute of the vehicles participating in the event d200, and determines the candidate vehicle d200 to be notified by the event notification unit d150.

[0768] Figure 82 This diagram illustrates an example of the contents of vehicle allocation table d173. In vehicle allocation table d173, a correspondence is established between vehicle attribute IDs and the number of vehicles for each attribute, and region IDs and event IDs. The region ID is identification information for identifying the region. The vehicle attribute ID is identification information for identifying the attributes of vehicle d200 participating in the event. Vehicle attributes, for example, indicate the type of service provided by vehicle d200 or its cargo compartment, and the specific content of the service. The attribute content can also be stored in storage unit d170 as vehicle attribute table d174.

[0769] Figure 83 This diagram illustrates an example of the contents of vehicle attribute table d174. In vehicle attribute table d174, attribute content is correlated with vehicle attribute IDs. For example, attribute content includes food stalls serving prescribed dishes like curry and ramen, convenience store vehicles selling various types of food and daily necessities, and lodging vehicles providing accommodation for users. Additionally, attribute content includes electric / fuel vehicles supplying batteries and fuel to multiple vehicles participating in an event.

[0770] return Figure 82 The number of vehicles in vehicle allocation table d173 represents the number of vehicles that can be parked in the area with the region ID. For example, in Figure 74 The example shows that when an event with event ID "I001" is held in region "A001", 20 vehicles with vehicle ID "T004" are allocated. Alternatively, when a different event (event ID "I002") is held in the same region "A001", 10 vehicles with vehicle ID "T001" and 10 vehicles with vehicle ID "T002" are allocated. The event vehicle candidate decision unit d140 can also receive instructions from administrators to create, modify, or delete various information in the vehicle allocation table d173, and adjust vehicle attributes, numbers, etc., relative to the region and event based on the received instructions.

[0771] The event vehicle candidate decision unit d140, referring to the vehicle allocation table d173 and the vehicle attribute table d174, outputs information related to the vehicle attributes and number of vehicles to the display control unit d130. The display control unit d130 then displays the information related to the vehicle attributes and number of vehicles determined by the event vehicle candidate decision unit d140 on the display unit d120.

[0772] Figure 84 This diagram shows an example of the event vehicle allocation setting screen IM2 displayed on the display unit d120 after an event vehicle allocation is performed. The event vehicle allocation setting screen IM2 displays the categories and number of vehicles scheduled for allocation. Regarding the number of vehicles, it displays the category and number of vehicles allocated by the vehicle allocation table d173. Furthermore, the display control unit d130 displays the number of allocated vehicles in a manner that can be changed by the administrator, allowing the number to be arbitrarily changed and adjusted through administrator input. The display control unit d130 can also update the number of vehicles in the vehicle allocation table d173 based on the number adjusted through the administrator's input.

[0773] Additionally, the event vehicle matching setting screen IM2 displays the confirmation operation area d420. When the OK button is selected via the confirmation operation area d420, the display control unit d130 accepts the execution of the event vehicle matching; when the Cancel button is selected, it confirms the cancellation of the event vehicle matching.

[0774] Furthermore, when the event vehicle candidate decision unit d140 accepts the execution of event vehicle allocation based on the event vehicle allocation setting screen IM2, it determines the candidate vehicle d200 to participate in the event based on the set vehicle category and number, referring to the vehicle information DBd175 stored in the storage unit d170. For example, the event vehicle candidate decision unit d140 refers to the vehicle information DBd175 and obtains the number of vehicle IDs corresponding to the vehicle attribute IDs set by the vehicle allocation table d173.

[0775] Figure 85 This diagram illustrates an example of the contents of vehicle information DBd175. In vehicle information DBd175, a correspondence is established between the vehicle ID (identification information for identifying vehicle d200), the vehicle communication address used to communicate with vehicle d200, the owner address used to communicate with the terminal device d300 (the owner of vehicle d200), and the vehicle's location information, and the vehicle attribute ID. The vehicle communication address is an IP address used to communicate with the communication device of vehicle d200, or an email address, telephone number, etc., assigned to vehicle d200. The owner address is an IP address used to communicate with the terminal device d300, or an email address, telephone number, etc., assigned to the terminal device d300. Location information refers to information (e.g., latitude, longitude) sent by each vehicle d200 at specified times to determine the location of vehicle d200.

[0776] The event notification unit d150, for the candidate vehicle d200 determined by the event vehicle candidate decision unit d140, obtains the address of one or both of the vehicle d200 and the terminal device d300 of the vehicle's owner O, and notifies the obtained address of information and inquiries related to the event. The event notification unit d150 may also notify via email, telephone call, machine voice notification, or application installed on the vehicle d200 and terminal device d300.

[0777] In addition, the event notification unit d150 updates the notification result management information d176 stored in the storage unit d170 based on the participation response obtained from the vehicle d200 or terminal device d300 of the object.

[0778] Figure 86 This diagram illustrates an example of the content of notification result management information d176. In notification result management information d176, a correspondence is established between the notification flag and the participation flag and the vehicle ID of the notification. The notification flag identifies whether the event-related information and inquiry information have been notified to the terminal device d300 of the vehicle d200 corresponding to the vehicle ID or the owner O of vehicle d200 via the event notification unit d150. Figure 86 In the example, the event notification unit d150 sets the notification flag to "1" when a notification is given and to "0" when no notification is given, but the identification information of the flag is not limited to this. The same applies to other flags described later.

[0779] Additionally, the participation flag is a marker that identifies whether a vehicle with a specific vehicle ID is participating in the notified event. The participation flag is set by the event notification unit d150 based on the query result corresponding to the query information in the notification. Figure 86 In the example, when participating in the event as a service provider, the participation flag is set to "1", and when not participating in the event as a service provider or without responding to the query information, the participation flag is set to "0".

[0780] Figure 87 This diagram illustrates the event notification sent to vehicle D200. Figure 87 In the example, the event notification unit d150, for instance, notifies the number of vehicles with event-related information and inquiry information according to the vehicle order (e.g., vehicle ID order) set in the vehicle information DBd175 for each vehicle attribute.

[0781] Additionally, the event notification unit d150 can also notify a number of vehicles registered in vehicle information DBd175 that belong to the vehicle attribute IDs participating in the event, and these vehicles are ordered in ascending order of distance from the area where the event is being held, of event-related information and inquiries. Figure 87 In the example, four vehicles d200a to d200d are notified in order of their distance from the event venue "A001" from closest to furthest. By notifying the vehicles closest to the event venue first, vehicle d200 can quickly assemble at the event venue.

[0782] Figure 88 This is an example of an event notification screen IM3 displayed on the HMId232 of vehicle d200. It should be noted that... Figure 88 And then Figure 89 The screen shown can also be displayed on the terminal device d300. The event notification screen IM3 includes, for example, an event notification area d430 displaying information related to the event notified from the event vehicle dispatching device d100, and an inquiry confirmation area d432 asking whether the user will participate in the event as a service provider. The event notification area d430 displays, for example, the event venue, event content, event duration, and desired services. Additionally, the inquiry confirmation area d432 displays a button to confirm participation. When the HMI d232 accepts the passenger's selection of the "participate" button from vehicle d200, it sends a response indicating the inte...

Claims

1. A vehicle, wherein: The vehicle has: a communication unit that receives operation information from a management server; a control unit that operates the vehicle based on the operation information from the communication unit; a management unit that manages the compartment of the vehicle in which the service user receives service from the service provider; as well as an interface part, which is set to establish a corresponding relationship between the service-related information provided by the service provider and the compartment, The communication unit transmits a control signal for controlling the interface unit to the management server or the service provider, using the access status of the service user to the vehicle as a trigger condition. The interface unit includes an external display, The vehicle further includes a display control unit configured to execute a display mode designated by the service provider using the external display in response to a control signal.

2. The vehicle according to claim 1, wherein: The vehicle further includes a usage status detection unit for detecting a usage status of a compartment of the vehicle. The communication unit transmits the detection signal of the usage status detection unit to the service provider.

3. The vehicle according to claim 1, wherein: The vehicle includes an external environment detection unit for detecting the outside of the compartment. The communication unit transmits the detection signal of the external environment detection unit to the service provider.

4. The vehicle according to claim 1, wherein: The communication unit receives a service signal transmitted from the service provider. The vehicle also has: a booth control signal generating unit, which generates a control signal corresponding to the received service signal and sends the control signal to a device arranged in the booth; and An operation control signal generating unit sends a control signal corresponding to the service signal to the control unit.

5. The vehicle according to claim 1, wherein: The vehicle includes an attribute sharing unit for sharing the attribute of the compartment with the management server or the service provider. The interface unit is set corresponding to the attribute.

6. The vehicle according to claim 1, wherein: The interface section performs an operation of an external device via the service provider.

7. The vehicle according to claim 1, wherein: The interface unit executes a route change to a specific destination provided by the service provider.

8. The vehicle of claim 1, wherein: The interface portion further comprises: A display unit that displays items provided by the service provider; and An operation information transmitting unit transmits operation information to the service provider via the communication unit.

9. The vehicle of claim 1, wherein: The control unit includes an automatic driving control unit for automatic driving based on an external detection sensor and a position information sensor. The interface unit permits the service user to use information when the automatic driving is being executed and the service user is riding in the vehicle.

10. The vehicle of claim 1, wherein: The interface unit provides information to the service user before or after the service user gets on the compartment.

11. The vehicle according to claim 1, wherein: The vehicle further includes a storage unit for storing items for external display. The display control unit downloads the entry from an external device and updates the entry stored in the storage unit.

12. The vehicle of claim 1, wherein: The vehicle further comprises: a travel unit having no cabin; and a first connecting portion provided on the travel unit and connected to an upper structure, the upper structure being detachably mounted on the travel unit. The management unit acquires travel unit information including model information of the travel unit from the management server, and connects the superstructure having a model matching the acquired travel unit information using the first connection unit.

13. A service management device comprising: a determination unit that determines vehicles utilized by a service provider; as well as a vehicle information providing unit that transmits information related to the vehicle corresponding to the vehicle identified by the identification unit to the service provider, in, The service management device comprises: A service information input unit for inputting service information of the service provider; as well as an interface control unit, which sends a control signal to the vehicle based on the service information to control information transmission between the vehicle and the service provider, The interface control unit further includes an external display control unit that controls an external display of the vehicle in response to a control signal from the service provider.

14. The service management device according to claim 13, wherein: The interface control unit permits the vehicle information providing unit to transmit information on a section in which a service user receives the service of the service provider while riding the vehicle to the service provider.

15. The service management device according to claim 13, wherein: The interface control unit includes a route updating unit that allows updating of a route or a destination of the vehicle in response to a control signal from the service provider.

16. The service management device according to claim 13, wherein: The interface control unit includes a service operation control unit configured to transmit information related to the vehicle to the service provider in response to a control signal from the vehicle.

17. The service management device according to claim 13, wherein: The identification unit identifies the vehicle from vehicles within a specific area.

18. The service management device according to claim 13, wherein: The identification unit identifies the vehicle based on the position information provided by the service provider and the boarding and alighting position information provided by any one of the service provider and the service user.

19. The service management device according to claim 18, wherein: The specifying unit specifies the plurality of vehicles for the service provider based on the position information and the boarding and getting-off position information.

20. The service management device according to claim 13, wherein: The service management device also has: a vehicle position management unit that detects positions of a plurality of the vehicles; and a service location management unit, which associates the service information corresponding to the plurality of vehicles, The interface control unit provides environmental information to the plurality of vehicles, service users, or the service provider based on the position information and service information acquired from the plurality of vehicles.

21. The service management device according to claim 20, wherein: The interface control unit determines a regional service implementation status as the environmental information based on the position information acquired from the plurality of vehicles and the service attribute information corresponding to the plurality of vehicles.

22. The service management device according to claim 13, wherein: The service management device further includes a storage unit for storing a display form of the vehicle with respect to the service information. The interface control unit enables the entry data stored in the storage unit to be selectively used by the vehicle based on the service information.

Images