JP6514157B2 - Vehicle management system - Google Patents

Description

  The present invention relates to a vehicle management system using a portable device.

  Conventionally, as a vehicle management system of this type, a control module mounted on a vehicle is known that receives personal data from a portable device of a driver and sets the position of a seat or a mirror based on the personal data. (See, for example, Patent Document 1). Such a vehicle management system is configured to operate only when the driver carrying the portable device is near the vehicle from the viewpoint of security.

JP, 2015-534921, A (paragraph [0018], Drawing 2)

  However, the above-described conventional vehicle management system has a problem that it can not be used unless the driver carrying the portable device is near the vehicle.

  The present invention has been made in view of the above circumstances, and an object thereof is to provide a vehicle management system capable of remotely managing a vehicle.

  The invention according to claim 1 made to achieve the above object is a vehicle control device mounted on a vehicle and performing detection of a vehicle state and control of the vehicle, and short-distance wireless communication between the vehicle control device and the vehicle control device. A remote key that causes the vehicle control device to lock and unlock the vehicle door, a server connected to the vehicle control device via a network, and receiving and storing vehicle information from the vehicle control device, and the server And a portable device which is connected to a network, acquires the vehicle information from the server, or transmits an instruction to the vehicle control device to the server, and the remote key and the vehicle control device have predetermined timings. Share the encryption key to be updated, and the vehicle control device has a vehicle ID unique to the vehicle as one of the vehicle information, and a predetermined tie. To transmit the vehicle information and the encryption key to the server, and the portable device performs near field communication with the remote key to connect the encryption key and the vehicle ID in advance from the remote key. And the server receives the encryption key and the remote key ID from the portable device, and the vehicle receives the encryption key and the remote key ID from the portable device. Vehicle management system which permits the login of the portable device if the cryptographic key and the remote key ID from the portable device are correct by collating based on the cryptographic key and the vehicle ID already acquired from the control device It is.

  The vehicle control device according to claim 2 performs short-range wireless communication between a vehicle control device mounted on a vehicle and performing detection of a vehicle state and control of the vehicle, and the vehicle control device performs vehicle control. A remote key for locking and unlocking a door, a server connected to the vehicle control device via a network, and a server for receiving and storing vehicle information from the vehicle control device, and a network connected to the server from the server to the vehicle And a portable device for acquiring information or transmitting an instruction to the vehicle control device to the server, wherein the remote key and the vehicle control device share an encryption key to be updated at a predetermined timing. The vehicle control apparatus is configured to register a portable device ID unique to the portable device as one of the vehicle information, and a predetermined timing The vehicle information and the encryption key are configured to be transmitted to the server, and the portable device is configured to perform near field communication with the remote key to obtain the encryption key from the remote key. The server receives the encryption key and the mobile device ID from the mobile device, and the encryption key and the mobile device ID that have already obtained the encryption key and the mobile device ID acquired from the mobile device from the vehicle control device. And a vehicle management system that permits login of the portable device if the encryption key from the portable device and the portable device ID are correct.

  In the invention of claim 3, the portable device is configured to transmit an instruction to the vehicle control device to the server, the vehicle control device receives the instruction from the server, and the vehicle is transmitted according to the instruction. It is a vehicle management system according to claim 1 or 2 to control.

  In the invention of claim 4, a candidate of a user permitted to control the vehicle is registered in the portable device or the server, and the portable device is another portable device having a user ID for recognizing the user. A permission command for permitting the device to control the vehicle is transmitted to the server, and the vehicle control device performs near field communication with the another portable device to authenticate the user ID. The vehicle management system according to claim 3, wherein when the user ID is authenticated, control of the vehicle by the another portable device is permitted in accordance with the permission command.

[Invention of claims 1 and 2]
In the vehicle management system of the present invention, the remote key performs near field communication with the vehicle control device to cause the vehicle control device to lock and unlock the vehicle door. Also, the remote key and the vehicle control device share the encryption key that is updated at a predetermined timing. Then, the vehicle control device transmits the encryption key and the vehicle information to the server at a predetermined timing. A portable device is connected to the server via a network, and the portable device acquires vehicle information from the server, and transmits a command to the vehicle control device via the server. Thus, according to the present invention, it is possible to remotely manage a vehicle by a portable device. The timing when the encryption key is updated and the timing when the vehicle control device transmits the encryption key and the vehicle information to the server may be the same timing or different timings.

  Here, in the invention of claim 1, the portable device is configured to perform near field communication with the remote key, and acquires the encryption key and the remote key ID from the remote key. Then, when logging in to the server, the portable device transmits the encryption key and the remote key ID to the server. The server collates the encryption key and the remote key ID received from the portable device based on the encryption key and the vehicle ID already acquired from the vehicle control device. Specifically, since the remote key ID acquired from the portable device is linked to the vehicle ID, the server specifies the vehicle by the remote key ID acquired from the portable device. Then, when the encryption key acquired from the portable device matches the encryption key acquired from the vehicle control device of the specified vehicle, login of the portable device is permitted. Thus, in the present invention, the server collates the encryption key when permitting login of the portable device. As a result, security of the server can be improved as compared with the case where the server collates only the remote key ID and permits login of the portable device. Moreover, since the encryption key is updated at a predetermined timing, the security to the server can be further improved.

  In the invention of claim 2, the portable device is configured to perform near field communication with the remote key, and acquires the encryption key from the remote key. Then, when logging in to the server, the mobile device transmits the encryption key and the mobile device ID to the server. The server collates the encryption key and the mobile device ID received from the mobile device with the encryption key and the mobile device ID already acquired from the vehicle control device, and the encryption key and the mobile device ID acquired from the mobile device are correct. , Allow mobile device login. As described above, in the present invention, the server collates not only the portable device ID but also the encryption key when permitting login of the portable device. As a result, compared to the case where the server collates only the portable device ID and permits login of the portable device, security of the server can be improved. Moreover, since the encryption key is updated at a predetermined timing, the security to the server can be further improved.

[Invention of Claim 3]
According to the present invention, it is possible to remotely control the vehicle.

[Invention of Claim 4]
In the present invention, another portable device owned by a third party other than the owner of the vehicle enables the third party to control the vehicle within a predetermined range. This enables the owner of the vehicle, for example, to have a store clerk at a gas station, a dealer of the vehicle, etc. supply gasoline and replace parts even when he / she is far from the vehicle, and appropriate service regarding the vehicle It is possible to receive

Block diagram showing schematic configuration of vehicle management system Block diagram for explaining the communication performed between the vehicle control device and the remote key Block diagram for explaining communication performed between vehicle control device and cloud server Block diagram for explaining the communication performed between the cloud server, the smartphone and the remote key Time flow of processing executed by vehicle control unit and remote key Time flow of processing executed by smartphone and cloud server (A) Schematic of vehicle login screen, (B) Schematic of vehicle command screen Schematic of various command screen Schematic of movement command screen Schematic of maintenance request screen Time flow of processing executed by smartphone and cloud server in use example 1 Block diagram for explaining communication performed in vehicle management system of use example 3 Block diagram for explaining communication performed by the vehicle management system of use example 4 Time flow of processing executed by vehicle control device and cloud server in usage example 4 Block diagram for explaining communication performed in vehicle management system of use example 5

First Embodiment
As shown in FIG. 1, the vehicle management system 10 of the present embodiment includes a vehicle control device 20 mounted on a vehicle 90, a remote key 30, a cloud server 40, and a smartphone 50. The cloud server 40 corresponds to the “server” of the present invention, and the smartphone 50 corresponds to the “mobile device” of the present invention.

  The vehicle control device 20 includes a control unit 21, a communication unit 22, a short distance communication unit 23, and a storage unit 24, and includes various devices provided in the vehicle 90 (for example, the vehicle door shown in FIG. 2) It controls a door lock device 92, an air conditioner 93 and the like 91). The control unit 21 is connected to the communication unit 22, the short distance communication unit 23, and the storage unit 24 and controls the communication unit 22, the short range communication unit 23, and the storage unit 24. The communication unit 22 performs wireless communication with the cloud server 40 via a network line. The short distance communication unit 23 performs short distance wireless communication with the remote key 30 or the smartphone 50 by, for example, Bluetooth (registered trademark). The storage unit 24 stores a program executed by the control unit 21, vehicle information, an encryption key used for communication with the remote key 30, a remote key ID unique to the remote key 30 registered in the vehicle control device 20, etc. Ru. The vehicle information includes the vehicle ID unique to the vehicle 90, the current position of the vehicle 90, the locking state of the vehicle door 91, the on / off state of the air conditioner 93, and the like (for the vehicle door 91 and the air conditioner 93, FIG. See). Further, the remote key ID is linked to the vehicle ID before the vehicle 90 is purchased.

  The remote key 30 includes a control unit 31, a short range communication unit 33, and a storage unit 34, and controls the door lock device 92 (see FIG. 2) of the vehicle door 91 via the vehicle control device 20. The control unit 31 is connected to the short distance communication unit 33 and the storage unit 34, and controls the short distance communication unit 33 and the storage unit 34. The short distance communication unit 33 performs short distance wireless communication with the vehicle control device 20 or the smartphone 50 by, for example, Bluetooth. The storage unit 34 stores a program executed by the control unit 31, the above-described remote key ID, and the like.

  The cloud server 40 includes a control unit 41, a communication unit 42, and a storage unit 44, and stores vehicle information acquired from the vehicle control device 20. The control unit 41 is connected to the communication unit 42 and the storage unit 44 to control the communication unit 42 and the storage unit 44. The communication unit 42 communicates with the vehicle control device 20 or the smartphone 50 via a network line. The storage unit 44 stores a program executed by the control unit 41, vehicle information acquired from the vehicle control device 20, an encryption key, a remote key ID, and the like.

  The smartphone 50 includes a control unit 51, a communication unit 52, a short distance communication unit 53, and a storage unit 54. The control unit 51 is connected to the communication unit 52, the short range communication unit 53, and the storage unit 54, and controls the communication unit 52, the short range communication unit 53, and the storage unit 54. The communication unit 52 communicates with the cloud server 40 via a network line. The short distance communication unit 53 performs short distance wireless communication with the remote key 30 by Bluetooth, for example. The storage unit 54 stores a program that the control unit 51 executes. In addition, the storage unit 54 temporarily stores the remote key ID and the encryption key acquired from the remote key 30.

  7 (A), 7 (B), 8, 9 and 10, vehicle login screen G 7 A, vehicle command screen G 7 B, various command screens G 8, movement command screen displayed on the display unit of the smartphone 50. G9 and a maintenance request screen G10 are shown. A login button 71 and an initial setting button 72 are displayed on the vehicle login screen G7A (see FIG. 7A). The vehicle login screen G7A also displays a model name and the like of the vehicle 90 managed by the vehicle management system 10. The login button 71 is operated when the smartphone 50 logs in to the cloud server 40. The initial setting button 72 is used when registering the remote key ID. When login to the cloud server 40 of the smartphone 50 is completed, a vehicle command screen G7B (see FIG. 7B) is displayed.

  In the vehicle command screen G7B, various command buttons 73, a move command button 74, and a maintenance request button 75 are displayed. Further, a vehicle state display area 76 indicating the current state of the vehicle 90 is provided in the vehicle command screen G7B. The various command buttons 73 are operated when controlling the air conditioner 93 and the like of the vehicle 90. When the various command button 73 is operated, a various command screen G8 (see FIG. 8) is displayed. The movement command button 74 is operated when moving the vehicle 90 by automatic driving. When the movement command button 74 is operated, a movement command screen G9 (see FIG. 9) is displayed. The maintenance request button 75 is operated when requesting maintenance of the vehicle 90 to a vendor. When the maintenance request button 75 is operated, a maintenance request screen G10 (see FIG. 10) is displayed.

  In the various command screen G8, the contents of commands to the various devices of the vehicle 90 are displayed. In the example shown in FIG. 8, the contents of an instruction to the air conditioner 93, the stereo device 94, the vehicle seat and the mirror are shown. Specifically, the on / off switching button 181 and the detail setting button 182 are displayed on the various command screen G8 regarding the command to the air conditioner 93. When the on / off switching button 181 is turned on, a command to the air conditioner 93 is executed. The detail setting button 182 is operated when setting the content of the command to the air conditioner 93. The content of the command to the air conditioner 93 is displayed in the setting content display area 183. Further, on the various command screen G8, a driver setting button 184 and a detail setting button 185 are displayed regarding commands to the vehicle seat and the mirror. The driver setting button 184 sets the driver of the vehicle 90. The vehicle seat and the mirror adjust the positions of the seat and the mirror in accordance with the driver set by the driver setting button 184. The detail setting button 185 is operated when changing the positions of the sheet and the mirror. The driver candidates that can be set by the driver setting button 184 are displayed in the driver information display area 186.

  The movement instruction screen G9 displays detailed information on automatic driving of the vehicle 90. Specifically, in the movement command screen G9, the movement place display unit 191, the movement time display unit 194, and the automatic driving start button 198 are operated. Is displayed. The movement destination display unit 191 displays the movement destination of the vehicle 90 by automatic driving. The details of the destination of the vehicle 90 are displayed in the position information display area 193 and the map 196. The destination of the vehicle 90 can be changed by the selection button 192. When the selection button 192 is operated, the destination can be selected from the points registered in advance. Registration of a point is performed by long press on the map 196 and operation of the point registration button 197. Further, the traveling time display portion 194 displays the timing of the automatic driving of the vehicle 90. This timing may be set as the departure time of the vehicle 90 or may be set as the arrival time. The timing of the automatic driving is changed by the change button 195. The automatic driving start button 198 is operated when performing automatic driving with the contents displayed on the moving place display portion 191 and the moving time display portion 194.

  In the maintenance request screen G10, the content of maintenance requested to the vendor is displayed in the maintenance content display area 112. The contents of maintenance are changed by the setting change button 111 and the maintenance setting update button 113. When the setting change button 111 is operated, the contents of maintenance can be edited. The maintenance setting update button 113 is operated when reflecting the content of maintenance after editing. Then, when the reservation button 114 is operated, a request is made to the vendor with the contents of the maintenance displayed in the maintenance content display area 112.

  FIG. 2 is a block diagram showing communication performed between the vehicle control device 20 and the remote key 30. As shown in FIG. FIG. 5 is a time flow of processing executed by the vehicle control device 20 and the remote key 30 when the vehicle door 91 is unlocked. As shown in FIGS. 2 and 5, the vehicle control device 20 authenticates the remote key 30 by near field communication, and controls the door lock device 92 based on a signal received from the remote key 30. Specifically, when the vehicle control device 20 receives the remote key ID from the remote key 30 and the received remote key ID matches the remote key ID stored in the storage unit 24, the remote key 30 receives the remote key 30. The door lock device 92 is controlled based on the unlocking signal from In this case, the command from the remote key 30 is transmitted to the door lock device 92. On the other hand, when the remote key ID received by the vehicle control device 20 does not match the remote key ID stored in the storage unit 24, the vehicle control device 20 does nothing to the door lock device 92. In this case, the command from the remote key 30 will not be transmitted to the door lock device 92.

  The encryption key is updated at a predetermined timing. Specifically, the encryption key is updated at one or both of locking and unlocking of the vehicle door 91. In addition to the above-described timing, the encryption key may be performed each time a predetermined time elapses when the vehicle control device 20 and the remote key 30 are in a state where the short distance wireless communication is possible. Or at the timing of turning on the ignition. The new encryption key at the time of updating may be generated by the vehicle control device 20 or may be generated by the remote key 30. In the example shown in FIG. 5, a new encryption key is generated at the timing when the vehicle control device 20 receives the unlocking signal from the remote key 30, and the encryption key is transmitted to the remote key 30. In addition, the vehicle control device 20 updates the new encryption key after receiving a response signal that the remote key 30 has received the new encryption key. After receiving the encryption key update signal of the vehicle control device 20, the remote key 30 updates a new encryption key. The remote key 30 does not update a new encryption key when the encryption key update signal of the vehicle control device 20 can not be received due to the influence of noise or the like. As described later, the encryption key is used when the smartphone 50 logs in to the cloud server 40. At the time of login, the smartphone 50 uses the encryption key acquired from the remote key 30. Here, since the remote key 30 stores the previous encryption key and the current encryption key, both the previous encryption key and the current encryption key may be tried when the smartphone 50 is logged in. In addition, when it is known that the remote key 30 and the vehicle control device 20 are close as in driving, the remote key 30 and the vehicle control device 20 mutually confirm the update of the encryption key, The encryption key may be updated reliably.

  FIG. 3 is a block diagram showing communication performed between the vehicle control device 20 and the cloud server 40. As shown in FIG. As shown in the figure, the vehicle control device 20 uploads vehicle information to the cloud server 40. Uploading of the vehicle information is periodically performed at a predetermined timing (for example, each time a predetermined time elapses in the state of the ignition off). In addition, the vehicle control device 20 downloads a command stored in the cloud server 40 at a predetermined timing, and controls various devices of the vehicle 90 based on the command. The download of the command may be performed at the same timing as the upload of the vehicle information, or may be performed at a different timing.

  In addition, the vehicle control device 20 accesses the cloud server 40 using the encryption key shared with the remote key 30. The cloud server 40 stores the encryption key acquired from the vehicle control device 20 in the storage unit 44. When the encryption key is updated, the vehicle control device 20 accesses the cloud server 40 using the previous encryption key. Then, when a new encryption key is registered in the cloud server 40, the vehicle control device 20 also updates the encryption key to the new encryption key (see FIG. 5).

  FIG. 4 is a block diagram showing communication performed between the remote key 30, the smartphone 50 and the cloud server 40. Moreover, FIG. 6 is a time flow of the process which the smart phone 50 and the cloud server 40 perform. As shown in FIG. 4, the smartphone 50 acquires vehicle information stored in the cloud server 40. The smartphone 50 also transmits a command to the vehicle control device 20 to the cloud server 40. The cloud server 40 stores the command received from the smartphone 50 in the storage unit 44.

  In order for the smartphone 50 to acquire vehicle information from the cloud server 40 and to transmit a command to the cloud server 40, the smartphone 50 needs to log in to the cloud server 40. At the time of this login, the cloud server 40 authenticates the remote key ID of the remote key 30. The remote key ID is registered in the vehicle control device 20 before the sale of the vehicle 90, and is saved in the cloud server 40 as part of the vehicle information when the vehicle control device 20 uploads the vehicle information to the cloud server 40. Further, registration of the remote key 30 with the cloud server 40 may be manually registered together with registration of the vehicle ID as management of the cloud server 40.

  Here, when the cloud server 40 collates only the remote key ID of the remote key 30 when the smartphone 50 logs in, when the remote key ID is known to another user, a vehicle 90 that has risen to the cloud server 40 at any time. Can be confirmed, and it becomes possible to give a command to the vehicle 90. As an example in which the remote key ID is known to other users, when the remote key ID is read by a program such as a virus, or when the friend's smartphone is made to grasp the remote key ID. In order to prevent the use of the vehicle management system 10 by such unintended other users, in the present embodiment, an encryption key updated every time is used for collation. According to this configuration, other users can not keep track of the encryption key except when intentionally trying to let the smartphone of the other user know the remote key ID and the encryption key, thus improving security. It is possible. As described above, since the linking of the vehicle ID and the remote key ID is performed before the purchase of the vehicle 90, the encryption key can be exchanged without the special operation of the user, and the user purchases the vehicle 90. It becomes possible to use the vehicle management system 10 later without time and effort.

  Specifically, the smartphone 50 acquires the remote key ID and the encryption key from the remote key 30 by near field communication. Then, the smartphone 50 transmits the remote key ID and the encryption key to the cloud server 40 when logging in to the cloud server 40. The cloud server 40 collates the remote key ID acquired from the smartphone 50 with the encryption key based on the vehicle ID and the encryption key acquired in advance from the vehicle control device 20. Since the remote key ID acquired from the smartphone 50 is linked to the vehicle ID, the cloud server 40 identifies the vehicle 90 by the remote key ID acquired from the smartphone 50. Then, when the encryption key acquired from the smartphone 50 matches the encryption key acquired from the vehicle control device 20 of the identified vehicle 90, the cloud server 40 permits the login of the smartphone 50.

  In the present embodiment, as described above, the vehicle login screen G7A of the smartphone 50 is provided with the login button 71 to the cloud server 40 (see FIG. 7A). Then, when the login button 71 is operated, the smartphone 50 transmits a request signal of remote key ID and encryption key to the remote key 30 registered in advance. When receiving the request signal, the remote key 30 transmits the remote key ID and the encryption key to the smartphone 50. Here, when the smartphone 50 does not exist in the range in which the remote key 30 can communicate with the remote key 30, the smartphone 50 can not grasp the information of the remote key ID and the encryption key. If there is a remote key 30 of another person apart from the remote key 30 of the driver of the vehicle 90 near the smart phone 50, the remote key 30 and the smart phone 50 are tied in advance in order to distinguish those remote keys 30. It is preferable to attach it.

  As described above, in the vehicle management system 10 of the present embodiment, the remote key 30 and the vehicle control device 20 perform near field communication, and share the encryption key to be updated at a predetermined timing. In addition, the vehicle control device 20 transmits the vehicle information including the vehicle ID and the encryption key to the cloud server 40 at a predetermined timing. The smartphone 50 is connected to the cloud server 40 via a network, and the smartphone 50 can acquire vehicle information from the cloud server 40 and can transmit a command to the vehicle control device 20 via the cloud server 40. . As described above, in the vehicle management system 10 according to the present embodiment, the smartphone 50 can remotely manage the vehicle 90.

  Here, in the vehicle management system 10, the smart phone 50 can acquire the remote key ID and the encryption key from the remote key 30 by the short distance wireless communication, and the cloud server 40 permits login of the smart phone 50. Match remote key ID as well as encryption key. Thereby, in the vehicle management system 10, security of the cloud server 40 can be improved as compared with the case where the cloud server 40 collates only the remote key ID and permits the smartphone 50 to log in. Moreover, since the encryption key is updated at a predetermined timing of the vehicle door 91, security of the cloud server 40 can be further improved.

The following is an example of use of the vehicle management system 10 according to the present embodiment.
[Example 1]
In Use Example 1, the driver at a location away from the vehicle 90 remotely controls the air conditioner 93 (see FIG. 2) of the vehicle 90 with the smartphone 50. Specifically, as shown in FIG. 11, the driver presses the login button of the smartphone 50 possessed by the driver and wirelessly transmits the remote key ID and the encryption key to the remote key 30 registered in the smartphone 50. Give a command. The remote key 30 transmits the remote key ID and the encryption key to the smartphone 50. When the driver presses the air conditioner ON button on the application screen of the smartphone 50, a command to turn on the air conditioner 93 is sent from the smartphone 50 to the cloud server 40. This command may include information on the set temperature. Moreover, when the air-conditioner apparatus 93 is equipped with the timer function, the information regarding the time which turns on the air-conditioner apparatus 93 may be included. The cloud server 40 stores the command from the smartphone 50 in the storage unit 44. The command stored in the cloud server 40 is downloaded to the vehicle control device 20 at a predetermined timing. Then, the vehicle control device 20 turns on the air conditioner 93 according to the command downloaded from the cloud server 40.

  According to the use example 1, by turning on the air conditioner 93 before getting on the vehicle 90, the driver can keep the vehicle 90 at a comfortable temperature when getting on the vehicle 90.

[Example 2]
The use example 2 is a modification of the use example 1, and only the content of the command is different. In Use Example 2, automatic driving of the vehicle 90 is premised, and the vehicle 90 is remotely operated to move to a designated destination. Specifically, the driver sends an operation command to the cloud server 40 via the smartphone 50. The driving instruction includes information on the destination of the vehicle 90 and the estimated arrival time. The destination may be set based on the position information of the driver using the position information of the smartphone 50, or may be set using the map function of the smartphone 50. The driving command is stored in the cloud server 40 and downloaded to the vehicle control device 20 at a predetermined timing. Then, the vehicle control device 20 performs automatic driving of the vehicle 90 in accordance with the driving command downloaded from the cloud server 40.

  According to the use example 2, for example, when shopping at a shopping mall etc., it becomes possible to move the vehicle 90 parked in the parking lot to a specific place such as a taxi stand or a place where the driver is present. There is no need to move the parking lot with heavy luggage. Further, according to Use Example 2, when the driver is absent, it is also possible to cause the vehicle 90 to pick up and drop off children in accordance with the arrival and departure school of the school. It should be noted that if the destination of the vehicle 90 is limited to a specific place such as the taxi stand mentioned above, it will be easier to avoid problems such as GPS accuracy and security, and it will be a service that can be realistically performed in the near future. Be

  In Use Example 2, the vehicle 90 may be a rental car. In this case, the smartphone 50 may be owned by a car rental company or may be owned by a borrower of the vehicle 90. In the latter case, the application may be realized by installing an application required for using the vehicle management system 10 on the smartphone 50 of the lessee of the vehicle 90. Note that this application is preferably valid only during the term of the rental contract.

[Example 3]
The use example 3 is a modification of the use example 1 and the content of the command is different from using another smart phone.
As shown in FIG. 12, in the use example 3, music data stored in the smartphone 50 V owned by a third party (for example, a friend of the driver) different from the driver of the vehicle 90 is the vehicle 90 via the cloud server 40. Is downloaded to the stereo device 94 of FIG.

  The driver of the vehicle 90 logs into the cloud server 40 using the remote key ID and the encryption key acquired from the remote key 30 in a state where the smartphone 50V is near the remote key 30 by borrowing the smartphone 50V from a third party, etc. Do. The driver sends music data and a command to download the music data to the stereo device 94 from the smartphone 50 V to the cloud server 40. The command stored in the cloud server 40 is downloaded to the vehicle control device 20 at a predetermined timing. Then, the vehicle control device 20 downloads music data from the cloud server 40 in accordance with the instruction downloaded from the cloud server 40 and causes the stereo device 94 to read the music data. In Usage Example 3, it is preferable that the encryption key acquired by the smartphone 50V from the remote key 30 be erased after a predetermined time has elapsed.

[Example 4]
In the use example 4, even if the owner of the vehicle 90 is not near the vehicle 90, it is possible for the vendor to perform maintenance and the like of the vehicle 90. In Usage Example 4, the owner of the vehicle 90 receives the vendor ID of the vendor's smart phone 150 (see FIG. 13) from the vendor in advance to receive the vendor's service, and registers it in the smartphone 50 and the vehicle control device 20 . In Usage Example 4, the vendor ID corresponds to the “user ID” described in claim 3 and the smartphone 150 of the vendor corresponds to the “another mobile device” described in claim 3.

  As shown in FIGS. 13 and 14, in use example 4, the owner of the vehicle 90 first logs in to the cloud server 40. The smart phone 50 and the remote key 30 are used to log in to the cloud server 40 as in the above-described use example 1.

  Next, a request for maintenance from the smartphone 50 to the cloud server 40 is sent to the vendor. The maintenance request is sent to the vendor's smartphone 150 via the cloud server 40. In addition, the vehicle control device has a permission command for granting an authority for permitting an operation (for example, an opening / closing operation of a door, an opening operation of a bonnet, etc.) to the vehicle 90 necessary for maintenance from the cloud server 40 Downloaded to 20. In addition, although gasoline supply is shown as a specific example of the request | requirement of a maintenance by FIG. 14, parts replacement, oil exchange, etc. may be otherwise.

  The vendor who has received the maintenance request goes to the place where the vehicle 90 is located at the date and time designated by the owner of the vehicle 90. Information on the date and place of maintenance is included in the maintenance request. Further, when the trader can confirm the current position of the vehicle 90 by the GPS by the authority given by the owner of the vehicle 90, the information on the location of the maintenance may not be included in the maintenance request.

  The vehicle control device 20 acquires the trader ID from the smart phone 150 of the trader by near-field wireless communication with the smart phone 150 of the trader, and collates it with the trader ID registered in advance in the vehicle control device 20. Then, when the trader ID acquired from the smart phone 150 of the trader matches the trader ID registered in the vehicle control device 20, the vehicle control device 20 is determined by the permission command based on the permission command acquired from the cloud server 40. Within the specified range, control of the vehicle 90 by the vendor is permitted. In the fourth use example, the filler door of the vehicle 90 is automatically opened, and when the vehicle control device 20 authenticates the vendor ID, the filler door 95 of the vehicle 90 (see FIG. 13). Open the filler door.

  In Use Example 4, it becomes possible to control the vehicle 90 within a predetermined range by a third party different from the owner of the vehicle 90. As a result, even when the owner of the vehicle 90 is away from the vehicle 90, it is possible to allow a company such as a gas station or a dealer to perform maintenance such as gasoline supply and parts replacement, and receive appropriate service regarding the vehicle 90. It becomes possible. In addition, in order to distinguish the car dealer and the on-the-road vanity etc. who had a favor of the car dealer, the gasoline in the parking lot of the company that can only go to a credible trader who has gasoline put in when watching TV at home It is preferable that the vehicle 90 be used in a situation where the safety of the vehicle 90 can be secured to some extent.

  In the use example 4 described above, the maintenance request is sent to the vendor when the smartphone 50 logs in, but when the smartphone 50 logs in, the maintenance requirement is set, and the maintenance requirement is satisfied. When done, the maintenance request may be automatically sent to the vendor. In addition, as a maintenance requirement condition with respect to the maintenance for putting gasoline, for example, the gasoline is reduced to half or less, and the vehicle 90 is stopped at the company at 14 o'clock on a weekday.

  Moreover, in the above-mentioned usage example 4, before making a request for maintenance, the trader ID is registered in the smart phone 50, but the maker of the vehicle 90 and the trader form a partnership so that the vehicle ID A trader ID may be linked to the [B] user may associate with the trader by performing member registration etc., and the trader ID may be registered on the smartphone application, [C] the smart phone 50 or A plurality of vendors are registered in the cloud server 40, the maintenance request is sent to the plurality of vendors, and when the vendor receives the request, the vendor ID of the vendor is registered in the vehicle 90 (vehicle control apparatus 20) It is also good. In any case, the vendor ID registered in the vehicle 90 may be one or more than one.

[Example 5]
As shown in FIG. 15, Usage Example 5 is one in which the smart home appliance 200 is linked to the cloud server 40 of the vehicle management system 10. The smart home appliance 200 is a home appliance that has a communication function and improves convenience by linking with other devices. Examples of the smart home appliance 200 include a refrigerator, an intercom, an air conditioner, and a lighting device.

  As shown in FIG. 15, the smart home appliance 200 is provided with a home appliance control device 210. The home appliance control device 210 includes a control unit 211, a communication unit 212, a short distance communication unit 213, and a storage unit 214. The control unit 211 is connected to the communication unit 212, the short range communication unit 213, and the storage unit 214, and controls the communication unit 212, the short range communication unit 213, and the storage unit 214. The communication unit 212 performs wireless communication with the cloud server 240 via a network line. The short distance communication unit 213 performs short distance wireless communication with the smartphone 50 by, for example, wireless LAN or Bluetooth. The storage unit 214 stores programs executed by the control unit 212, home appliance information, and the like. In the home appliance information, the ID of the smart home appliance 200 (hereinafter referred to as "home appliance ID"), the password set by the owner of the smart home appliance 200 and the vehicle 90 for the smart home appliance 200, etc. Is included.

  In addition, the cloud server 240 includes a control unit 241, a communication unit 242, and a storage unit 244, and stores home appliance information acquired from the home appliance control device 200. The control unit 241 is connected to the communication unit 242 and the storage unit 244, and controls the communication unit 242 and the storage unit 244. The communication unit 242 communicates with the home appliance control device 200 via a network line. The storage unit 244 stores a program executed by the control unit 241, home appliance information acquired from the home appliance control device 210, and the like. The home appliance control device 210 periodically uploads home appliance information to the cloud server 240 at a predetermined timing.

  In the use example 5, the home appliance ID and the personal identification number of the smart home appliance 200 are registered in the smartphone 50 in advance. This registration is performed by near field communication between the smart phone 50 and the smart home appliance 200.

  Further, in the use example 5, when the vehicle control device 20 acquires home appliance information via the cloud server 40, the driver of the vehicle 90 can grasp home appliance information of the smart home appliance 200 in the vehicle 90. Specifically, when the smart phone 50 logs in to the cloud server 40 and the home appliance ID and the password of the smart 200 are input from the smart phone 50, vehicle information and home appliances are generated between the cloud server 40 and the cloud server 240. It becomes possible to exchange information. Therefore, when the vehicle control device 20 regularly downloads the vehicle information at a predetermined timing, the home appliance information is also downloaded. Thus, the home appliance information of the smart home appliance 200 is acquired by the vehicle control device 20. Note that, as with the above-described usage example 1, the encryption key and the mobile device ID are used for login to the cloud server 40.

  As household appliance information which vehicle control device 20 acquires, when smart household appliance 200 is a refrigerator, for example, the quantity of foodstuffs in a refrigerator, etc. are mentioned. In this case, when the vehicle control device 20 notifies the driver of the vehicle 90 of the home appliance information, the driver can buy back the insufficient food or the like when returning home by the vehicle 90. Further, when the smart home appliance 200 is an intercom, the home appliance information includes a list of visitors who are away. In this case, when the home appliance information is notified to the driver of the vehicle 90, the driver can return to the visitor's home when returning home by the vehicle 90. Further, when the smart home appliance 200 is the main system of home security, the home appliance information may be a state of closing of the house. In this case, it is possible for the driver to know lack of lock before leaving the vehicle 90.

Second Embodiment
In the first embodiment, the smartphone 50 is configured to acquire the encryption key and the remote key ID from the remote key 30 so that any smartphone can be used for the vehicle management system 10, but in the present embodiment, the smartphone 50 acquires only the encryption key from the remote key 30, and when logging in to the cloud server 40, a portable device ID unique to the smartphone 50 and the encryption key are used. In the present embodiment, it is assumed that the portable device ID is registered in advance in the vehicle control device 20. Also in the present embodiment, since the encryption key updated at a predetermined timing is used when the smartphone 50 logs in, security can be improved.

  Here, in the present embodiment, since it is necessary to perform the stringing registration of the smartphone 50 and the vehicle 90, the smartphone 50 not linked with the vehicle 90 can not access the cloud server 40. As a result, the security when the remote key 30 is lost can be maintained.

[Other embodiments]
The present invention is not limited to the above-described embodiment, and, for example, the embodiments described below are also included in the technical scope of the present invention, and various other variations are possible without departing from the scope of the invention. It can be changed and implemented.

  (1) In the above embodiment, the “mobile device” of the present invention is the smartphone 50, but it may be a notebook PC, a tablet PC, or a dedicated terminal device.

  (2) In the above embodiment, the smartphone 50 is configured not only to acquire vehicle information from the cloud server 40 but also to send an instruction to the vehicle control device 20 to the cloud server 40, but only to acquire vehicle information It may be Even in this case, the driver or owner of the vehicle 90 can grasp the state of the vehicle 90, such as the tire pressure and the remaining amount of gasoline, at a location far from the vehicle 90, for example.

  (3) In the above embodiment, the command from the smartphone 50 to the vehicle 90 is always transmitted to the vehicle 90 via the cloud server 40. However, when the smartphone 50 is in the short distance of the vehicle 90, the smartphone 50 is Directly to the vehicle 90.

  (4) The control of the vehicle 90 in the above embodiment may include controls such as seat position control and mirror position control in addition to the vehicle position, door lock control, and air conditioner control. In addition, it may be configured to be able to perform settings to implement these controls collectively. The vehicle information may include the amount of gasoline, the time of oil change, and the like.

  (5) In the above embodiment, the remote key ID and the vehicle ID may be separate IDs or the same ID.

  (6) In the above embodiment, the remote key ID is used also for locking and unlocking, but an ID different from that used for locking and unlocking may be used.

  (7) The music data in the usage example 3 of the above embodiment is data of the smartphone 50, but may be performed by specifying a URL.

  (8) In the usage example 5 of the above embodiment, the cloud server 40 unilaterally receives home appliance information, but vehicle information may be provided to the cloud server 240 connected to the smart home appliance 200. In this case, it may be made to know where the vehicle 90 is located, or when the vehicle 90 starts moving from the company, it is accessed by the cloud server 240 and it can be grasped by buzzer, voice or the like that it has started moving. In this case, the driver can automatically inform the family that he has begun to go home, and the driver's family must know that the driver has returned home, warm up the food, and ask the driver to do shopping etc. Is possible.

  (9) In the first embodiment, the smartphone 50 acquires the encryption key and the remote key ID from the remote key 30, and logs in to the cloud server 40. In the second embodiment, the smartphone 50 encrypts the remote key 30 from the remote key 30 Although the key is acquired, and the mobile device ID and the encryption key are used to log in to the cloud server 40, a user password may be provided to connect the smartphone 50 and the remote key 30. In addition, a user password may be provided to connect the smartphone 50 and the cloud server 40. Also in this configuration, since the encryption key updated at a predetermined timing is used when the smartphone 50 logs in, security can be improved.

  (10) In the first embodiment, the smartphone 50 acquires the encryption key and the remote key ID from the remote key 30, and logs in to the cloud server 40. In the second embodiment, the smartphone 50 encrypts the remote key 30 from the remote key 30 Although the key is obtained and configured to log in to the cloud server 40 using the mobile device ID and the encryption key, the mobile device ID, the remote key ID, and the encryption key are used to log in to the cloud server 40 It is good also as composition. Also in this configuration, since the encryption key updated at a predetermined timing is used when the smartphone 50 logs in, security can be improved.

  (11) In the above embodiment, the log-in button 71 (see FIG. 7A) is pressed on the vehicle log-in screen G7A of the smartphone 50 to acquire the encryption key. , And both the operation of the smartphone 50 and the operation of the remote key 30 may be performed at the time of cloud login. When the remote key unlock button is pressed, the remote key 30 can transmit and receive with the smartphone 50. By doing this, the possibility that the smartphone 50 acquires the ID of another remote key 30 is reduced. Moreover, in the configuration up to now, the remote key 30 is always in the reception standby state and consumes power in order to wait for the login command from the smartphone 50, but in this configuration, only when the unlock button is pressed, Since it is possible to wait for reception from the smartphone or to send data to the smartphone, power can be saved. Also in this configuration, since the encryption key updated at a predetermined timing is used when the smartphone 50 logs in, security can be improved.

10 Vehicle management system 20 Vehicle control device 30 Remote key 40 Cloud server (server)
50, 50V smartphone (mobile device)
90 vehicles 150 vendors' smartphones (another mobile device)

Claims (4)

A vehicle control device mounted on a vehicle for detecting a vehicle state and controlling the vehicle;
A remote key for performing near field communication with the vehicle control device to cause the vehicle control device to lock and unlock the vehicle door;
A server connected to the vehicle control device via a network and receiving and storing vehicle information from the vehicle control device;
And a portable device connected to the server via a network and acquiring the vehicle information from the server or transmitting an instruction to the vehicle control device to the server.
The remote key and the vehicle control device share an encryption key that is updated at a predetermined timing,
The vehicle control device is configured to have a vehicle ID unique to the vehicle as one of the vehicle information, and to transmit the vehicle information and the encryption key to the server at a predetermined timing.
The portable device is configured to perform near field communication with the remote key to acquire the encryption key and a remote key ID previously associated with the vehicle ID from the remote key.
The server receives the encryption key and the remote key ID from the mobile device, and the encryption key and the vehicle ID that have already acquired the encryption key and remote key ID acquired from the mobile device from the vehicle control device. A vehicle management system which permits login of the portable device if the encryption key from the portable device and the remote key ID are correct. A vehicle control device mounted on a vehicle for detecting a vehicle state and controlling the vehicle;
A remote key for performing near field communication with the vehicle control device to cause the vehicle control device to lock and unlock the vehicle door;
A server connected to the vehicle control device via a network and receiving and storing vehicle information from the vehicle control device;
And a portable device connected to the server via a network and acquiring the vehicle information from the server or transmitting an instruction to the vehicle control device to the server.
The remote key and the vehicle control device share an encryption key that is updated at a predetermined timing,
The vehicle control device is configured to register a mobile device ID unique to the mobile device as one of the vehicle information, and transmits the vehicle information and the encryption key to the server at a predetermined timing. Configured to
The portable device is configured to perform near field communication with the remote key to acquire the encryption key from the remote key.
The server receives the encryption key and the mobile device ID from the mobile device, and the encryption key and the mobile device that have already obtained the encryption key and the mobile device ID acquired from the mobile device from the vehicle control device. A vehicle management system for collating with an ID and permitting login of the portable device if the encryption key from the portable device and the portable device ID are correct. The portable device is configured to transmit an instruction to the vehicle control device to the server,
The vehicle management system according to claim 1, wherein the vehicle control device receives the command from the server and controls the vehicle according to the command. Candidates of users who are permitted to control the vehicle are registered in the mobile device or the server,
The portable device transmits, to the server, a permission command for permitting another portable device having a user ID for recognizing the user to control the vehicle.
The vehicle control device is configured to perform near field communication with the another portable device to authenticate the user ID, and when the user ID is authenticated, the vehicle control device performs the another portable device according to the permission command. The vehicle management system according to claim 3, wherein control of the vehicle is permitted.

Images