In-vehicle device, portable terminal, and program

Abstract

To provide a technology that facilitates users' identification of a demand vehicle to board while preventing the leakage of personal information.SOLUTION: An exemplary in-vehicle device is installed in a demand vehicle that operates according to user reservation information and includes a controller. The controller receives a reservation ID wirelessly transmitted from a portable terminal, and when a received reservation ID, which is the reservation ID received, matches storage reservation ID contained in the reservation information stored in the in-vehicle device, generates an encryption key containing the storage reservation ID and a portion of the reservation information stored in the in-vehicle device other than the storage reservation ID and encrypts the information on the demand vehicle using the encryption key to transmit the information wirelessly.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to an in-vehicle device, a mobile terminal, and a program. [Background technology]

[0002] Demand vehicles are known in which the operating time and route are determined according to the reservation information of users (see, for example, Patent Document 1). Demand vehicles are shared vehicles in which the operating time and route are determined according to the reservation information of users, and include demand-type shared taxis, demand buses, etc.

[0003] Many on-demand vehicles do not have destination displays like route buses, and many on-demand shared taxis and buses look similar to each other. This makes it difficult for on-demand vehicle users to identify the vehicle they should board (the vehicle they have reserved). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-199179 Summary of the Invention [Problem to be solved by the invention]

[0005] Patent Document 1 discloses that an operation control center transmits reservation information to a user's mobile phone. The reservation information is information that can easily identify the vehicle to board (reserved vehicle).

[0006] However, there is a risk that the response time between the operation control center and the user's mobile phone will be slow, and in poor communication conditions, there is also a risk that communication between the operation control center and the user's mobile phone will not be established.

[0007] By adopting communications that do not use servers such as those at operation control centers, the problems of delayed responses and communication failures can be resolved, but in this case, it is necessary to consider the risk of personal information being leaked.

[0008] In view of the above circumstances, the present invention aims to provide a technology that makes it easy for users to identify the demand vehicle they should board while preventing the leakage of personal information. [Means for solving the problem]

[0009] An exemplary in-vehicle device of the present invention is mounted on a demand vehicle that operates according to user reservation information and includes a controller. The controller of the in-vehicle device receives a reservation ID wirelessly transmitted from a mobile terminal, and when a received reservation ID, which is the received reservation ID, matches a stored reservation ID, which is a reservation ID included in reservation information stored in the in-vehicle device, generates an encryption key including the stored reservation ID and a part of the reservation information stored in the in-vehicle device other than the stored reservation ID, and encrypts information of the demand vehicle using the encryption key and wirelessly transmits the encrypted information.

[0010] An exemplary mobile terminal of the present invention includes a controller that wirelessly transmits a reservation ID included in reservation information stored in the mobile terminal, generates a decryption key including the reservation ID and a part of the reservation information stored in the mobile terminal other than the reservation ID, receives encrypted and wirelessly transmitted information of a demand vehicle from an in-vehicle device, decrypts the information of the demand vehicle using the decryption key, and performs display based on the decrypted information of the demand vehicle. [Effects of the Invention]

[0011] According to an exemplary embodiment of the present invention, information about a demand vehicle, which corresponds to personal information about which vehicle to use, is encrypted using an encryption key including a reservation ID and a portion of the reservation information other than the reservation ID, and wirelessly transmitted from the in-vehicle device to a mobile terminal. By including the reservation ID in the encryption key, the uniqueness of the encryption key can be ensured. By including a portion of the reservation information other than the reservation ID in the encryption key, only the mobile terminal that stores the reservation information can decrypt the information about the demand vehicle wirelessly transmitted from the in-vehicle device, and a display based on the decrypted demand vehicle information can be performed. Therefore, while preventing the leakage of personal information, the user can easily identify the demand vehicle to board by displaying it on the mobile terminal. [Brief explanation of the drawings]

[0012] [Figure 1] Block diagram showing the general configuration of the vehicle dispatch management system [Figure 2] A diagram showing a schematic diagram of reservation information to which a reservation ID is assigned. [Figure 3] A diagram showing a schematic diagram of a demand vehicle operation plan [Figure 4] Block diagram showing the configuration of an in-vehicle device [Figure 5] Block diagram showing the configuration of a mobile terminal [Figure 6] FIG. 1 is a diagram showing an example of the positional relationship between an in-vehicle device and a mobile terminal; [Figure 7] Flowchart showing an example of processing by an in-vehicle device and a mobile terminal [Figure 8] FIG. 10 is a diagram showing a display example based on information on a demand vehicle on a mobile terminal; [Figure 9] FIG. 10 is a diagram showing another example of display based on information about a demand vehicle on a mobile terminal; DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the drawings.

[0014] <1. Vehicle dispatch management system> FIG. 1 is a block diagram showing a schematic configuration of a vehicle dispatch management system SYS1 according to an embodiment of the present invention.

[0015] As shown in FIG. 1, the vehicle dispatch management system SYS1 includes an in-vehicle device 1, a mobile terminal 2, and a management server 3. The in-vehicle device 1 and the management server 3 can communicate with each other via a communication network 4 such as the Internet. The mobile terminal 2 and the management server 3 can communicate with each other via the communication network 4. The in-vehicle device 1 and the mobile terminal 2 can communicate with each other via short-range wireless communication such as Bluetooth Low Energy (registered trademark). The communication distance of the short-range wireless communication between the in-vehicle device 1 and the mobile terminal 2 is approximately several tens to several hundreds of meters.

[0016] 1, the number of in-vehicle devices 1 connected to the communication network 4 is one, but the number of in-vehicle devices 1 connected to the communication network 4 may be multiple. Also, in the example shown in FIG. 1, the number of mobile terminals 2 connected to the communication network 4 is one, but the number of mobile terminals 2 connected to the communication network 4 may be multiple.

[0017] The mobile terminal 2 operated by a user (passenger) using a demand vehicle transmits reservation information including a boarding date and time when the user wishes to board, a boarding location where the user wishes to board, and a disembarking location where the user wishes to disembark to the management server 3, for example, using a reservation app on the mobile terminal 2. The management server 3 accepts reservation information from multiple users, assigns a unique reservation ID (Identification) to each piece of reservation information, and determines an operation plan for the demand vehicle to be used by each user according to the accepted reservation information. The management server 3 notifies the mobile terminal 2 that sent the reservation information that the reservation has been completed. The notification includes the reservation ID. The management server 3 notifies each on-board device 1 of the reservation information related to the demand vehicle in which each on-board device 1 is installed.

[0018] An on-board device 1 is mounted on each demand vehicle. The on-board device 1 may be a device that is permanently mounted on the demand vehicle, or a portable device that is mounted on the demand vehicle while the demand vehicle is in operation and can be carried from the demand vehicle. When there are multiple on-board devices 1 connected to the communication network 4, any two on-board devices 1 may be different types of devices. That is, for example, one on-board device 1 may be a device that is permanently mounted on the demand vehicle, and another on-board device 1 may be a portable device.

[0019] The mobile terminal 2 is, for example, a smartphone, a tablet terminal, a notebook personal computer, etc. When a plurality of mobile terminals 2 are connected to the communication network 4, any two mobile terminals 2 may be different types of terminals. That is, for example, any two mobile terminals 2 may be different types of smartphones. Alternatively, for example, one mobile terminal 2 may be a smartphone and another mobile terminal 2 may be a tablet terminal.

[0020] The management server 3 is a server located in a vehicle dispatch center or the like, or a cloud server.

[0021] In the following explanation, an example will be given in which the management server 3 receives three pieces of reservation information, assigns a reservation ID to each piece of reservation information as shown in Fig. 2, and determines an operation plan for a demand vehicle as shown in Fig. 3. Note that the start position, boarding position BP1, and disembarking positions DP1 to DP3 in Fig. 3 are each position information specified by, for example, latitude and longitude.

[0022] <2.In-vehicle equipment> 4 is a block diagram showing the configuration of the in-vehicle device 1 according to the embodiment of the present invention. As shown in FIG. 4, the in-vehicle device 1 includes a controller 110, a memory 120, a communication processing unit 130, a short-range wireless communication processing unit 140, and a GPS (Global Positioning System) processing unit 150.

[0023] The controller 110 includes a processing unit 110a including an MPU (Micro Processing Unit) and the like as a hardware resource.

[0024] The memory 120 includes a non-volatile memory such as a ROM (Read Only Memory) or a flash memory, and a volatile memory such as a RAM (Random Access Memory). All or part of the memory 120 may be a memory built into the controller 110. The memory 120 stores a program PG1. In the controller 110, the processing unit 110a executes the program PG1 stored in the memory 120, thereby realizing the functions of the program PG1. The program PG1 may be composed of multiple programs. If the processing unit 110a is provided with multiple MPUs, the multiple programs in the program PG1 may be executed by the multiple MPUs. The program PG1 is a program capable of wirelessly transmitting information about demand vehicles to the mobile terminal 2.

[0025] Under the control of the controller 110, the memory 120 stores the reservation information R1 (reservation information assigned a reservation ID) notified from the management server 3. The memory 120 of the in-vehicle device 1 mounted on the demand vehicle A stores, as the reservation information R1, the reservation information with the reservation ID ID1 and the reservation information with the reservation ID ID2 (see FIG. 3). The memory 120 of the in-vehicle device 1 mounted on the demand vehicle B stores, as the reservation information R1, the reservation information with the reservation ID ID3 (see FIG. 3). Hereinafter, the in-vehicle device 1 mounted on the demand vehicle A may be referred to as the in-vehicle device 1A.

[0026] The memory 120 stores vehicle information INF. The memory 120 of the in-vehicle device 1 mounted on the demand vehicle A stores, as the vehicle information INF, for example, the registration number displayed on the license plate of the demand vehicle A, the vehicle model of the demand vehicle A, an exterior image of the demand vehicle A, etc.

[0027] The communication processing unit 130 realizes two-way communication with a counterpart device such as the management server 3. The communication processing unit 130 includes a transmitting unit 131 that transmits any information to the counterpart device, and a receiving unit 132 that receives information transmitted from the counterpart device. Although the description of the communication processing unit 130, the transmitting unit 131, and the receiving unit 132 may be omitted below, in the in-vehicle device 1, transmission of information to the counterpart device is realized using the communication processing unit 130 (transmitting unit 131), and reception of information from the counterpart device is realized using the communication processing unit 130 (receiving unit 132).

[0028] The short-range wireless communication processing unit 140 realizes two-way short-range wireless communication with a counterpart device such as the mobile terminal 2. The short-range wireless communication processing unit 140 includes a transmitter 141 that transmits any information to the counterpart device, and a receiver 142 that receives information transmitted from the counterpart device. In the following, descriptions of the short-range wireless communication processing unit 140, the transmitter 141, and the receiver 142 may be omitted, but in the in-car device 1, transmission of information to the counterpart device is realized using the short-range wireless communication processing unit 140 (transmitter 141), and reception of information from the counterpart device is realized using the short-range wireless communication processing unit 140 (receiver 142).

[0029] The GPS processing unit 150 receives signals from a plurality of GPS satellites that form the GPS to detect the position of the in-vehicle device 1 (the current position of the in-vehicle device 1). The position information of the in-vehicle device 1 is sent from the GPS processing unit 150 to the controller 110.

[0030] <3. Mobile Devices> 5 is a block diagram showing the configuration of a mobile terminal 2 according to an embodiment of the present invention. As shown in FIG. 5, the mobile terminal 2 includes a controller 210, a memory 220, a communication processing unit 230, a short-range wireless communication processing unit 240, a camera 250, a GPS processing unit 260, and an interface unit 270.

[0031] The controller 210 includes a processing unit 210a including an MPU (Micro Processing Unit) and a GPU (Graphics Processing Unit) as hardware resources, and comprehensively controls the operation of each part of the mobile terminal 2. In the following description, any operation and processing executed by the controller 210 may be interpreted as operation and processing executed by the processing unit 210a.

[0032] The memory 220 includes non-volatile memory such as ROM or flash memory, and volatile memory such as RAM. All or part of the memory 220 may be memory built into the mobile terminal 2. The memory 220 stores a program PG2. The arithmetic processing unit 210a executes the program PG2 to realize the functions of the program PG2. The program PG2 may be composed of multiple programs including the program PG2a. When multiple MPUs are provided in the arithmetic processing unit 210a, the multiple programs in the program PG2 may be executed by the multiple MPUs. The program PG2a is an application program capable of reserving a demand vehicle and displaying information about the reserved demand vehicle.

[0033] Under the control of the controller 210, the memory 220 stores the reservation information (reservation information assigned a reservation ID) R2 notified by the management server 3. The memory 220 of the mobile terminal 2 that transmitted to the management server 3 the reservation information in which the boarding date and time is T1, the boarding location is BP1, and the disembarking location is DP1 stores, as the reservation information R2, the reservation information in which the reservation ID is ID1 (see FIG. 2). The memory 220 of the mobile terminal 2 that transmitted to the management server 3 the reservation information in which the boarding date and time is T1, the boarding location is BP1, and the disembarking location is DP2 stores, as the reservation information R2, the reservation information in which the reservation ID is ID2 (see FIG. 2). The memory 220 of the mobile terminal 2 that transmitted to the management server 3 the reservation information in which the boarding date and time is T5, the boarding location is BP1, and the disembarking location is DP3 stores, as the reservation information R2, the reservation information in which the reservation ID is ID3 (see FIG. 2). Hereinafter, the mobile terminal 2 that stores reservation information whose reservation ID is ID1 may be referred to as mobile terminal 21, the mobile terminal 2 that stores reservation information whose reservation ID is ID2 may be referred to as mobile terminal 22, and the mobile terminal 2 that stores reservation information whose reservation ID is ID3 may be referred to as mobile terminal 23.

[0034] The communication processing unit 230 realizes two-way communication with a counterpart device such as the management server 3. The communication processing unit 230 includes a transmitting unit 231 that transmits any information to the counterpart device, and a receiving unit 232 that receives information transmitted from the counterpart device. Although the description of the communication processing unit 230, transmitting unit 231, and receiving unit 232 may be omitted below, in the mobile terminal 2, transmission of information to the counterpart device is realized using the communication processing unit 230 (transmitting unit 231), and reception of information from the counterpart device is realized using the communication processing unit 230 (receiving unit 232).

[0035] The short-range wireless communication processing unit 240 realizes two-way short-range wireless communication with a counterpart device such as the in-vehicle device 1. The short-range wireless communication processing unit 240 includes a transmitter 241 that transmits any information to the counterpart device, and a receiver 242 that receives information transmitted from the counterpart device. Although the description of the short-range wireless communication processing unit 240, transmitter 241, and receiver 242 may be omitted below, in the portable terminal 2, transmission of information to the counterpart device is realized using the short-range wireless communication processing unit 240 (transmitter 241), and reception of information from the counterpart device is realized using the short-range wireless communication processing unit 240 (receiver 242).

[0036] Camera 250 captures an image of a subject within its own imaging area and generates image information of the image within the imaging area (hereinafter referred to as a captured image). The generated image information is sent to controller 210. Camera 250 captures images sequentially at a predetermined frame rate, thereby obtaining a plurality of captured images arranged in chronological order. A moving image (video) is formed from the plurality of captured images arranged in chronological order.

[0037] The GPS processing unit 260 receives signals from a plurality of GPS satellites that form the GPS to detect the position of the mobile terminal 2 (the current position of the mobile terminal 2). The position information of the mobile terminal 2 is sent from the GPS processing unit 260 to the controller 210.

[0038] The interface unit 270 is a man-machine interface between the mobile terminal 2 and a user of the mobile terminal 2 (a user who uses a demand vehicle), and outputs arbitrary information to the user of the mobile terminal 2 and receives arbitrary information from the user of the mobile terminal 2. The interface unit 270 includes a display screen 271, an operation unit 272, a microphone 273, and a speaker 274. The display screen 271 is configured with a liquid crystal display panel or the like, and displays arbitrary images under the control of the controller 210. That is, the controller 210 displays arbitrary images using the display screen 271. The operation unit 272 accepts arbitrary operation input from the user of the mobile terminal 2. The display screen 271 and the operation unit 272 may form a touch panel, and an operation on the operation unit 272 may be an operation on the touch panel. The microphone 273 picks up ambient sounds around the microphone 273 and converts the picked up sounds into electrical signals. The speaker 274 outputs arbitrary sounds under the control of the controller 210.

[0039] <4. Processing examples for in-vehicle devices and mobile terminals> Fig. 6 is a diagram schematically illustrating an example of the positional relationship between the in-vehicle device 1A and the mobile terminals 21 to 23. In the example of the positional relationship shown in Fig. 6, the demand vehicle A equipped with the in-vehicle device 1A is approaching the boarding position BP1, and the mobile terminals 21 to 23 are gathered at the boarding position BP1.

[0040] Fig. 7 is a flowchart showing an example of processing by the in-vehicle device 1A and the mobile terminals 21 to 23 in the example of the positional relationship shown in Fig. 6. The in-vehicle device 1A is in an operating state while the demand vehicle A is in operation, and is in a state where it can perform the processing shown in Fig. 7. The mobile terminals 21 to 23 are in a state where they can perform the processing shown in Fig. 7 if a reservation app is running.

[0041] In step S1, the in-vehicle device 1A detects approach to the riding position (in this example, riding position BP1). More specifically, when the distance between the current position of the demand vehicle A, i.e., the current position of the in-vehicle device 1A detected by the GPS processing unit 150, and the riding position BP1 becomes equal to or less than a threshold, the controller 110 of the in-vehicle device 1A detects approach to the riding position BP1. The threshold is preferably set to be equal to or less than the communication distance of short-range wireless communication realized using the short-range wireless communication processing units 140 and 240. When approach to the riding position BP1 is detected, the process proceeds to step S2.

[0042] In step S2, the in-vehicle device 1A broadcasts the trigger information. More specifically, the controller 110 of the in-vehicle device 1A broadcasts the trigger information by short-range wireless communication. Once the trigger information has been broadcast, the process proceeds to steps S3 to S5.

[0043] As described above, when the in-vehicle device 1A detects its approach to the boarding position BP1, it broadcasts the trigger information. In other words, in a situation where it is difficult to imagine that the in-vehicle device 1A is located near the mobile terminals 21 to 23, the in-vehicle device 1A does not broadcast the trigger information. This prevents the in-vehicle device 1A from transmitting the trigger information unnecessarily.

[0044] Furthermore, by using the trigger information simultaneously transmitted from the in-vehicle device 1A as a trigger to cause the mobile terminals 21 to 23 to proceed with processing, it is possible to prevent unnecessary processing on the mobile terminals 21 to 23 (for example, the simultaneous transmission of reservation IDs in a situation where it is difficult to imagine that the in-vehicle device 1A is located near the mobile terminals 21 to 23).

[0045] In this example, the trigger information is information on the boarding position BP1 included in the operation plan (travel route) of the demand vehicle A equipped with the on-vehicle device 1A. By using the information on the boarding position BP1 as the trigger information, it is possible to prevent the mobile terminal 2 that has made a reservation that does not include the boarding position BP1 from proceeding with useless processing in response to the trigger information.

[0046] In step S3, the controller 210 of the mobile terminal 21 compares the received trigger information with the reservation information R2 stored in the memory 220. The reservation information R2 stored in the memory 220 of the mobile terminal 21 is the reservation information whose reservation ID is ID1 (see FIG. 2). In the comparison process of step S3, it is confirmed that the information on the boarding position BP1 included in the trigger information is included in the reservation information R2. Since the information on the boarding position BP1 included in the trigger information is included in the reservation information R2, the process proceeds to step S6.

[0047] In step S6, the controller 210 of the mobile terminal 21 broadcasts the reservation ID (ID1) included in the reservation information R2 via short-range wireless communication. If the information on the boarding position BP1 included in the trigger information is not included in the reservation information R2, the controller 210 of the mobile terminal 21 does not broadcast the reservation ID via short-range wireless communication. This makes it possible to prevent unnecessary transmission of the reservation ID.

[0048] In step S4, the controller 210 of the mobile terminal 22 compares the received trigger information with the reservation information R2 stored in the memory 220. The reservation information R2 stored in the memory 220 of the mobile terminal 22 is the reservation information whose reservation ID is ID2 (see FIG. 2). The comparison process in step S4 confirms that the information on the boarding position BP1 included in the trigger information is included in the reservation information R2. Since the information on the boarding position BP1 included in the trigger information is included in the reservation information R2, the process proceeds to step S7.

[0049] In step S7, the controller 210 of the mobile terminal 22 broadcasts the reservation ID (ID2) included in the reservation information R2 via short-range wireless communication. If the information on the boarding position BP1 included in the trigger information is not included in the reservation information R2, the controller 210 of the mobile terminal 22 does not broadcast the reservation ID via short-range wireless communication. This makes it possible to prevent unnecessary transmission of the reservation ID.

[0050] In step S5, the controller 210 of the mobile terminal 23 compares the received trigger information with the reservation information R2 stored in the memory 220. The reservation information R2 stored in the memory 220 of the mobile terminal 23 is the reservation information having a reservation ID of ID3 (see FIG. 2). In the comparison process of step S5, it is confirmed that the information on the boarding position BP1 included in the trigger information is included in the reservation information R2. Since the information on the boarding position BP1 included in the trigger information is included in the reservation information R2, the process proceeds to step S8.

[0051] In step S8, the controller 210 of the mobile terminal 23 broadcasts the reservation ID (ID3) included in the reservation information R2 via short-range wireless communication. If the information on the boarding position BP1 included in the trigger information is not included in the reservation information R2, the controller 210 of the mobile terminal 23 does not broadcast the reservation ID via short-range wireless communication. This makes it possible to prevent unnecessary transmission of the reservation ID.

[0052] Once the reservation IDs have been broadcast, the process proceeds to step S9.

[0053] In step S9, the controller 110 of the in-vehicle device 1A receives the reservation ID (ID1) sent from the mobile terminal 21. Since the received reservation ID (ID1) matches the reservation ID included in the reservation information R1 stored in the memory 120 of the in-vehicle device 1A, the controller 110 generates an encryption key K21 including ID1 and a portion of the reservation information included in the reservation information R1 and having the reservation ID ID1 (e.g., information about the drop-off location). Note that the portion of the reservation information having the reservation ID ID1 that constitutes the reservation information R1 is information other than the reservation ID. When generating the encryption key K21, the vehicle dispatch management system SYS1 predetermines which information to use as part of the reservation information included in the reservation information R1 and having the reservation ID ID1. Therefore, the controller 210 of the mobile terminal 21 can determine what kind of key the encryption key K21 will be based on the reservation information R2 stored in the memory 220 of the mobile terminal 21. On the other hand, the controllers 210 of the mobile terminals 22 and 23 cannot ascertain from the reservation information R2 stored in the memories 220 of the mobile terminals 22 and 23 what kind of key the encryption key K21 will be.

[0054] In step S9, the controller 110 of the in-vehicle device 1A receives the reservation ID (ID2) sent from the mobile terminal 22. Since the received reservation ID (ID2) matches the reservation ID included in the reservation information R1 stored in the memory 120, the controller 110 generates an encryption key K22 including ID2 and a portion of the reservation information included in the reservation information R1 and having the reservation ID ID2 (e.g., information about the drop-off location). Note that the portion of the reservation information including the reservation ID ID2 that constitutes the reservation information R1 is information other than the reservation ID. When generating the encryption key K22, the vehicle dispatch management system SYS1 has previously determined which information to use as part of the reservation information included in the reservation information R1 and having the reservation ID ID2. Therefore, the controller 210 of the mobile terminal 22 can determine what kind of key the encryption key K22 will be based on the reservation information R2 stored in the memory 220 of the mobile terminal 22. On the other hand, the controllers 210 of the mobile terminals 21 and 23 cannot ascertain from the reservation information R2 stored in the memories 220 of the mobile terminals 21 and 23 what kind of key the encryption key K22 will be.

[0055] In addition, the controller 110 of the in-vehicle device 1A receives the reservation ID (ID3) sent from the mobile terminal 23, and since the received reservation ID (ID3) does not match the reservation ID included in the reservation information R1 stored in the memory 120 of the in-vehicle device 1A, it does not generate an encryption key including ID3.

[0056] Once the encryption key is generated, the process proceeds to steps S10 and S11.

[0057] In step S10, the controller 110 of the in-vehicle device 1A reads the vehicle information INF from the memory 120 of the in-vehicle device 1A, encrypts the vehicle information INF using the encryption key K21, and transmits the encrypted vehicle information INF simultaneously via short-range wireless communication. By using the encryption key K21, it is possible to prevent personal information of the user of the mobile terminal 21 (information such as which demand vehicle the user of the mobile terminal 21 uses) from being leaked to the user of the mobile terminal 22 and the user of the mobile terminal 23.

[0058] In step S11, the controller 110 of the in-vehicle device 1A reads the vehicle information INF from the memory 120 of the in-vehicle device 1A, encrypts the vehicle information INF using the encryption key K22, and transmits the encrypted vehicle information INF simultaneously via short-range wireless communication. By using the encryption key K22, it is possible to prevent personal information of the user of the mobile terminal 22 (information such as which demand vehicle the user of the mobile terminal 22 uses) from being leaked to the user of the mobile terminal 21 and the user of the mobile terminal 23.

[0059] Once the vehicle information INF has been broadcast, the process proceeds to steps S12 and S13.

[0060] In step S12, the controller 210 of the mobile terminal 21 receives the vehicle information INF sent from the in-vehicle device 1A and decrypts the vehicle information INF using the decryption key. The decryption key used in step S12 has the same configuration as the encryption key K21.

[0061] In step S13, the controller 210 of the mobile terminal 22 receives the vehicle information INF sent from the in-vehicle device 1A and decrypts the vehicle information INF using the decryption key. The decryption key used in step S13 has the same configuration as the encryption key K22.

[0062] Once the vehicle information INF is decoded, the process proceeds to steps S14 and S15.

[0063] In step S14, the controller 210 of the mobile terminal 21 performs display based on the vehicle information INF using the display screen 271. This display makes it easy for the user of the mobile terminal 21 to identify the demand vehicle (demand vehicle A) in which the user should ride.

[0064] In step S15, the controller 210 of the mobile terminal 22 performs display based on the vehicle information INF using the display screen 271. This display makes it easy for the user of the mobile terminal 22 to identify the demand vehicle (demand vehicle A) in which the user should ride.

[0065] 7, when the vehicle information INF is not updated, the in-vehicle device 1A may end the process when step S11 is completed, the mobile terminal 21 may end the process when step S14 is completed, the mobile terminal 22 may end the process when step S15 is completed, and the mobile terminal 23 may end the process when step S8 is completed. When the vehicle information INF includes the current location of the demand vehicle, etc., and the vehicle information INF is updated, the in-vehicle device 1A may return to the process of step S1 when step S11 is completed, the mobile terminal 21 may return to a state where it can perform the process of step S3 when step S14 is completed, the mobile terminal 22 may return to a state where it can perform the process of step S4 when step S15 is completed, and the mobile terminal 23 may return to a state where it can perform the process of step S5 when step S8 is completed. Note that when the vehicle information INF is updated, the in-vehicle device 1A may return to step S10, and may periodically repeat steps S10 and S11 until just before the vehicle arrives at the boarding position. This simplifies the processing of the in-vehicle device 1A and the mobile terminals 21 and 22, enabling quick transmission and reception of the vehicle information INF.

[0066] The above-mentioned in-vehicle device 1 and mobile terminal 2 communicate directly with each other via short-range wireless communication without going through the management server 3, which enables a fast communication response and allows the mobile terminal 2 to display information based on the demand vehicle even in an environment where the communication conditions of the communication network 4 are poor.

[0067] <5. Display example> FIG. 8 is a diagram showing a display example based on information about a demand vehicle on the mobile terminal 2. In the display example shown in FIG. 8, the controller 210 of the mobile terminal 2 uses the display screen 271 to display an image based on a camera image captured by the camera 250. A vehicle V1 is captured in the camera image. When a user of the mobile terminal 2 operates a touch panel including the display screen 271 and the operation unit 272 to tap an area capturing the vehicle V1, the controller 210 of the mobile terminal 2 performs image recognition on the registration number displayed on the license plate N1 included in the vehicle V1. If the image-recognized registration number matches the registration number included in the vehicle information INF, the controller 210 of the mobile terminal 2 displays a superimposed image in which an augmented reality image A1 (a pop-up image indicating that the vehicle is a demand vehicle to be boarded) based on the vehicle information INF is superimposed on the camera image. The use of augmented reality technology makes it even easier for the user of the mobile terminal 2 to identify the demand vehicle that the user should board.

[0068] It should be noted that the extraction of the vehicle V1 may be performed automatically, making the above-mentioned tap operation unnecessary.

[0069] Fig. 9 is a diagram showing another display example based on information about a demand vehicle on the mobile terminal 2. In the display example shown in Fig. 9, the controller 210 of the mobile terminal 2 displays a map image MP on which an icon P1 indicating the current location of a demand vehicle to be boarded and an icon P2 indicating the current location of the mobile terminal 2 are superimposed. When the display example shown in Fig. 9 is executed, map data is stored in the memory 220 of the mobile terminal 2, and the vehicle information INF includes the current location of the demand vehicle. Such a map display clarifies the positional relationship between the demand vehicle to be boarded and the user of the mobile terminal 2, making it even easier for the user of the mobile terminal 2 to identify the demand vehicle that they should board.

[0070] <6. Variations> For example, the trigger information may be a reservation ID (ID1 and ID2) related to the operation plan (travel route) of the demand vehicle A equipped with the on-vehicle device 1A. In this case, the result of the collation process in step S5 shown in Fig. 7 can be used to prevent the simultaneous transmission process in step S8 shown in Fig. 7 from being executed.

[0071] Furthermore, for example, the trigger information may be information unrelated to the operation plan (travel route) of the demand vehicle A equipped with the on-vehicle device 1A. In this case, the matching process in steps S3 to S5 shown in Fig. 7 can be omitted, and the controller 210 of the mobile terminal 2 may unconditionally broadcast the reservation ID via short-range wireless communication upon receiving the trigger information.

[0072] Also, for example, the processes in steps S3 to S5 shown in FIG. 7 may be omitted, and the controller 210 of the mobile terminal 2 may continue to broadcast the reservation ID via short-range wireless communication.

[0073] <7. Points to note> Various technical features disclosed in the description of the present invention may be modified in various ways without departing from the spirit of the technical creation. Furthermore, multiple embodiments and modifications disclosed in the description of the present invention may be combined to the extent possible. [Explanation of symbols]

[0074] 1...In-vehicle device 2. Mobile devices 3. Management Server 4. Communication Network SYS1... Vehicle dispatch management system

Claims

1. An on-board device mounted on a demand vehicle that operates according to user reservation information, Equipped with a controller, The controller Receive the reservation ID wirelessly transmitted from the mobile terminal, When the received reservation ID matches a stored reservation ID included in the reservation information stored in the vehicle-mounted device, the vehicle-mounted device generates an encryption key including the stored reservation ID and a portion of the reservation information stored in the vehicle-mounted device other than the stored reservation ID, and encrypts and wirelessly transmits information about the demand vehicle using the encryption key.

2. The controller Trigger information is wirelessly transmitted, The in-vehicle device according to claim 1 , wherein the in-vehicle device receives a reservation ID wirelessly transmitted from the portable terminal in response to the trigger information.

3. The in-vehicle device according to claim 2 , wherein the trigger information is information on a boarding position included in an operation plan of the demand vehicle.

4. The controller The in-vehicle device according to claim 3 , wherein the trigger information is wirelessly transmitted when a distance between the current position of the demand vehicle and the riding position becomes equal to or less than a threshold value.

5. A mobile terminal including a controller, The controller wirelessly transmitting a reservation ID included in the reservation information stored in the mobile terminal; generating a decryption key including the reservation ID and a part of the reservation information stored in the mobile terminal other than the reservation ID; A mobile terminal that receives encrypted and wirelessly transmitted information about a demand vehicle from an in-vehicle device, decrypts the information about the demand vehicle using the decryption key, and displays information based on the decrypted information about the demand vehicle.

6. The controller 6. The mobile terminal according to claim 5, wherein, upon receiving trigger information wirelessly transmitted from the in-vehicle device, the mobile terminal wirelessly transmits a reservation ID included in the reservation information stored in the mobile terminal.

7. The controller receiving trigger information wirelessly transmitted from the in-vehicle device; 6. The mobile terminal according to claim 5, wherein if information included in the trigger information is included in reservation information stored in the mobile terminal, a reservation ID included in the reservation information stored in the mobile terminal is wirelessly transmitted.

8. The mobile terminal according to claim 5 , wherein the display is a display of a superimposed image in which an augmented reality image based on information about the demand vehicle is superimposed on a camera image.

9. The mobile terminal according to claim 5 , wherein the display is a map display showing the location of the demand vehicle.

10. The computer installed in the demand vehicle that operates according to the user's reservation information receiving a reservation ID wirelessly transmitted from a mobile terminal; generating an encryption key including the stored reservation ID and a part of the reservation information stored in the on-board device mounted on the demand vehicle when the received reservation ID, which is the received reservation ID, matches with the stored reservation ID, which is the reservation ID included in the reservation information stored in the on-board device mounted on the demand vehicle; encrypting the information of the demand vehicle using the encryption key and wirelessly transmitting the encrypted information; A program that executes.

11. wirelessly transmitting a reservation ID included in the reservation information stored in the mobile terminal; generating a decryption key including the reservation ID and a part of the reservation information stored in the mobile terminal other than the reservation ID; receiving information about the demand vehicle that has been encrypted and wirelessly transmitted from the in-vehicle device; decrypting the information of the demand vehicle using the decryption key and performing a display based on the decrypted information of the demand vehicle; A program that causes a computer to execute the following.

Images