CN110581876B - Vehicle-mounted device, shared vehicle management system and shared vehicle management method - Google Patents
Vehicle-mounted device, shared vehicle management system and shared vehicle management method Download PDFInfo
- Publication number
- CN110581876B CN110581876B CN201810595347.3A CN201810595347A CN110581876B CN 110581876 B CN110581876 B CN 110581876B CN 201810595347 A CN201810595347 A CN 201810595347A CN 110581876 B CN110581876 B CN 110581876B
- Authority
- CN
- China
- Prior art keywords
- key information
- vehicle
- user terminal
- information
- shared vehicle
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Lock And Its Accessories (AREA)
Abstract
The invention provides a vehicle-mounted device, a shared vehicle management system and a shared vehicle management method, which can avoid unlocking failure and improve the unlocking efficiency of a shared vehicle even when authentication information cannot be obtained due to failure. The in-vehicle apparatus includes: a vehicle-mounted side receiving unit that receives the first key information and the authentication key information; a vehicle-mounted side transmitting unit that transmits response information to the management server when receiving the first key information; an on-vehicle side storage unit that stores second key information in advance and stores the received first key information; a comparison unit that extracts the first key information or the second key information, and compares the extracted first key information or second key information with the authentication key information; an unlocking unit for unlocking the shared vehicle when the comparison result is consistent; the collation unit extracts the second key information when the first key information is not extracted, and collates the extracted second key information with the received authentication key information.
Description
Technical Field
The embodiment of the invention relates to an on-vehicle device of a shared vehicle, a shared vehicle management system and a shared vehicle management method.
Background
Currently, with the development of sharing economy, the use of sharing vehicles such as sharing automobiles is increasingly accepted by the public. Wherein the user wishes to use the shared vehicle, the shared vehicle is unlocked or locked by obtaining authorization from the authority. In the prior art, users often use their own user terminals to perform locking/unlocking by sending and receiving information with a sharing vehicle through wireless communication such as bluetooth, wifi and the like.
Wireless communication using bluetooth is described as an example. First, a user reserves a shared vehicle with a management server for managing the shared vehicle via a network such as the internet by using an APP provided in a terminal device, and after receiving a reservation request, the management server returns a key corresponding to a specific shared vehicle to a user terminal, and transmits reservation request information, the key, information on the terminal device reserving the vehicle, and the like to the shared vehicle via remote communication (for security reasons, for example, a telephone network), and the like, and after receiving the above information, the shared vehicle returns a response to the management server, and the connection between the shared vehicle and the server is bidirectional identity authentication, and data encryption or the like can be used to prevent tampering.
The sharing vehicle which completes the bidirectional identity authentication establishes a link with the terminal equipment by using the acquired information related to the terminal equipment, and performs authentication with the terminal equipment by using a secret key after the link. For example, the identity authentication is performed by matching key information between the Bluetooth connected shared vehicle and the terminal equipment, and the shared vehicle is unlocked after the matching is successful.
However, since the management server does not necessarily use the same network for communication with the terminal and the user, if the two-way authentication is unsuccessful due to a communication failure or interruption between the shared vehicle and the server, the shared vehicle may not acquire key information from the server and cannot authenticate with the user terminal, and the server may not acquire response information and cannot manage the shared vehicle. In this case, the display result of the user terminal is that the door of the reserved car fails to be unlocked, an administrator of the shared car needs to be contacted, more time is required, and the user experience is poor.
Disclosure of Invention
The present invention has been made in view of the above-described problems, and an object of the present invention is to provide an in-vehicle apparatus, a shared vehicle management system, and a shared vehicle management method that can prevent unlocking failure even when authentication information cannot be obtained due to a failure, and can improve the unlocking efficiency of a shared vehicle.
An embodiment of the present invention is a shared vehicle management system including an in-vehicle device mounted on a shared vehicle, a management server that manages key information for unlocking the shared vehicle, and a user terminal that communicates with the in-vehicle device and the management server, the in-vehicle device including: a vehicle-mounted receiving unit configured to receive first key information transmitted from the management server and authentication key information transmitted from the user terminal; a vehicle-mounted-side transmitting unit that transmits response information indicating that the first key information is received to the management server when the first key information is received from the management server; an on-vehicle side storage unit which stores second key information in advance and stores the received first key information; a collation unit configured to extract the first key information or the second key information stored in the in-vehicle storage unit when the in-vehicle reception unit receives the authentication key information from the user terminal, and collate the extracted first key information or second key information with the authentication key information transmitted from the user terminal; and an unlocking unit for unlocking the shared vehicle when the comparison result of the comparison unit is identical; the management server includes: a server-side storage unit that stores, in advance, identification information for identifying a shared vehicle on which the vehicle-mounted device is mounted, in association with the second key information; a server-side transmitting/receiving unit configured to transmit the first key information to the user terminal as the authentication key information for the shared vehicle; the same first key information is sent to the vehicle-mounted equipment, and the response information is received from the vehicle-mounted equipment; when the response information is not received within a predetermined time after the server transmitting/receiving unit transmits the first key information to the in-vehicle device, the server transmitting/receiving unit transmits, to the user terminal, second key information stored in the server-side storage unit and corresponding to the identification information of the shared vehicle on which the in-vehicle device is mounted, as authentication key information, and the collation unit extracts the second key information and collates the extracted second key information with the received authentication key information when the first key information stored in the in-vehicle storage unit is not extracted.
Another embodiment of the present invention is an in-vehicle apparatus mounted on a shared vehicle, including: a vehicle-mounted side receiving unit that receives first key information transmitted from a management server and authentication key information transmitted from a user terminal; a vehicle-mounted-side transmitting unit that transmits response information indicating that the first key information is received to the management server when the first key information is received from the management server; an on-vehicle side storage unit which stores second key information in advance and stores the received first key information; a collation unit configured to extract the first key information or the second key information stored in the in-vehicle storage unit when the in-vehicle reception unit receives the authentication key information from the user terminal, and collate the extracted first key information or second key information with the authentication key information transmitted from the user terminal; an unlocking unit for unlocking the shared vehicle when the comparison result of the comparison unit is identical; the collation unit extracts the second key information when the first key information stored in the in-vehicle storage unit is not extracted, and collates the extracted second key information with the received authentication key information.
According to the embodiment of the invention, two keys are used in the authentication between the sharing vehicle and the user terminal, so that unlocking failure can be avoided even if the sharing vehicle cannot obtain the first key due to the fact that the communication module of the sharing vehicle is damaged or the communication signal is bad and the like, the unlocking efficiency of the sharing vehicle can be improved, and user time is saved, and meanwhile user experience is better.
Drawings
Fig. 1 is a schematic diagram illustrating the configuration of a shared vehicle management system.
Fig. 2 is a block diagram illustrating the configuration of the shared vehicle management system according to the first embodiment.
Fig. 3 is a flowchart illustrating authentication processing of the management server in the shared vehicle management system according to the first embodiment.
Fig. 4 is a flowchart illustrating shared vehicle management of the in-vehicle devices in the shared vehicle management system according to the first embodiment.
Fig. 5 is a sequence flow chart illustrating a shared vehicle management method according to the first embodiment.
Fig. 6 is a block diagram illustrating a configuration of a shared vehicle management system according to the second embodiment.
Fig. 7 is a sequence flow chart illustrating a shared vehicle management method according to the second embodiment.
Description of the reference numerals:
1, a management server; 2, a user terminal; 3 on-board equipment; 10 a server side storage module; a server-side transceiver module; 30 vehicle-mounted side receiving modules; 40 vehicle-mounted side transmitting module; 50 vehicle-mounted side storage modules; 60 control modules; 70 unlocking the module; 80 a shared vehicle determination module; 90 eliminate the module.
Detailed Description
The shared vehicle management system mainly comprises vehicle-mounted equipment mounted on a shared vehicle, a management server for remotely managing the shared vehicle through wireless communication and a user terminal held by a user.
The shared vehicle is a vehicle provided by a provider and a user can select rental use as needed, and the form of the shared vehicle is not limited, and the shared vehicle is described as an automobile.
Fig. 1 is a schematic diagram illustrating a general configuration of a shared vehicle management system. As shown in fig. 1, the shared vehicle management system includes: a vehicle-mounted device 3 mounted on the shared vehicle; a user terminal 2 which is held by a user, can accept a request from the user, and communicates with the in-vehicle device 3 and the server; the management server 1 is connected to the user terminal 2 or the vehicle-mounted device 3 of the shared vehicle via a network such as the internet, and manages key information for unlocking the shared vehicle.
When the network communications are normal, the management server 1 issues a key to the in-vehicle device 3 and the user terminal 2, and the in-vehicle device 3 and the user terminal 2 perform authentication of the key to unlock the shared vehicle. Specifically, first, the user uses the APP provided in the user terminal 2 to transmit the vehicle reservation information (1) to the management server 1 that manages the shared vehicle via a network such as the internet to reserve the shared vehicle, and after receiving the reservation request, the management server 1 returns the key (2) corresponding to the specific shared vehicle to the user terminal 2, and transmits the reservation request information, the information related to the terminal device 2, and the key (3) to the in-vehicle device 3 via remote communication (for security, for example, a telephone network), and the in-vehicle device 3 returns the response information (4) to the management server 1 after receiving the information related to the reservation and the key, and completes the bidirectional identity authentication between the in-vehicle device 3 and the management server 1 via (3) (4). The information transmitted in the bidirectional identity authentication can use various existing information formats and contents, and can also use technologies such as data encryption and the like to prevent tampering.
The vehicle-mounted device 3 which completes the bidirectional identity authentication establishes a link with the user terminal 2 by using the acquired information related to the user terminal 2, the vehicle-mounted device 3 collates the authentication key from the user terminal 2 with the key from the management server 1 through the established link, and returns success information to the user terminal 2 when the collation is successful, thereby completing the authentication (5).
Next, the shared vehicle management system of the present invention is also capable of coping with a case where the bidirectional identity authentication between the in-vehicle apparatus 3 and the management server 1 fails. Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. In the different embodiments, the same reference numerals are used for the same or similar parts, and duplicate explanation is omitted as appropriate.
(first embodiment)
Fig. 2 is a block diagram illustrating the configuration of the shared vehicle management system according to the first embodiment. As shown in fig. 2, the shared vehicle management system includes a user terminal 2, an in-vehicle device 3, and a management server 1.
The user terminal 2 is a terminal that can use a shared vehicle reservation application, such as a mobile phone held by a user. The user terminal 2 is capable of running a shared-vehicle reservation program by having hardware such as an antenna, a processor, and a memory, and communicates with the in-vehicle device 3 and the management server 1 to transmit and receive information related to the shared-vehicle reservation process. For example, the user terminal 2 may be close to a shared vehicle to be reserved, and transmit and receive data to and from the in-vehicle device 3 by wireless connection such as bluetooth or wired connection. The user terminal 2 may be connected to the remote management server 1 via a network such as the internet, and transmit and receive data to and from the management server 1. The user terminal 2 may be a terminal device such as a personal computer. When reservation of a shared vehicle is to be made, the user terminal 2 first transmits reservation request information to the management server 1, and may include identification information (shared vehicle identifier) for identifying a specific shared vehicle in the reservation request information in order to reserve the specific shared vehicle. Then, the user terminal 2 can acquire authentication key information including an authentication key for unlocking the shared vehicle from the management server 1, and the user terminal 2 transmits the acquired authentication key to the in-vehicle device 3 to request authentication unlocking. If the unlocking is successful, the user of the user terminal can use the sharing vehicle.
The management server 1 includes a server-side storage module 10 and a server-side transceiver module 20. The server-side storage module 10 stores in advance identification information for identifying the shared vehicle on which the in-vehicle device 3 is mounted in association with the spare key (second key information). The identification information is an identifier for identifying each shared vehicle managed by the management server 1, so that a spare key corresponding to a specific shared vehicle (in-vehicle apparatus 3) can be extracted based on the identification information. The server-side storage module 10 may be a dedicated circuit capable of achieving the above functions or a program module executed by a processor.
The server-side transceiver module 20 can generate a key (first key information) for unlocking a lock of a shared vehicle to be reserved, and transmit the key to the user terminal 2 as authentication key information for the shared vehicle. The key may be key information randomly generated for the reserved vehicle when the management server receives the vehicle reservation information of the user terminal 2, or may be key information stored in advance. When the identification information of the shared vehicle is included in the vehicle reservation information of the user terminal 2, the server-side transmission/reception module 20 transmits a key to the user terminal 2 as authentication key information corresponding to the identification information. The server-side transceiver module 20 transmits the above-described generated or stored key (first key information) for unlocking the lock of the shared vehicle to be reserved to the in-vehicle apparatus 3, and receives response information for responding to the transmission of the key from the in-vehicle apparatus 3, as a response to the reception of the key by the in-vehicle apparatus 3. When the response information is not received within a predetermined time after the server transceiver module 20 transmits the key to the in-vehicle apparatus 3, the server transceiver module 20 extracts a spare key (second key) corresponding to the received determination information from the server-side storage module 10, and transmits the spare key to the user terminal 2 as authentication key information. The predetermined time may be arbitrarily set according to the network property and the data transfer speed, and may be set to a threshold value larger than the time taken in the case of the normal transfer speed, for example. The server-side transceiver module 20 may be a dedicated circuit capable of achieving the above functions or a program module executed by a processor.
The in-vehicle apparatus 3 includes an in-vehicle side receiving module 30, an in-vehicle side transmitting module 40, an in-vehicle side storing module 50, a collation module 60, and an unlocking module 70.
The in-vehicle side reception module 30 is used to receive data from the management server 1 or the user terminal 2. For example, the in-vehicle side reception module 30 receives the key transmitted from the management server 1 and the authentication key information transmitted from the user terminal 2. The in-vehicle-side receiving module 30 may be a dedicated circuit capable of achieving the above functions or a program module executed by a processor.
The in-vehicle side transmission module 40 is used for transmitting data to the management server 1 or the user terminal 2. For example, when the in-vehicle side reception module 30 receives key information including a key from the management server 1, the in-vehicle side transmission module 40 transmits response information indicating that the key information is received to the management server 1. The in-vehicle side transmission module 40 may be a dedicated circuit capable of realizing the above functions or a program module executed by a processor.
The in-vehicle side memory module 50 is used to store information required for unlocking. In particular, a spare key (second key information) corresponding to the own vehicle-mounted device is stored in advance in the vehicle-mounted side memory module 50, and the spare key can be stored in the vehicle-mounted side memory module 50 at the time of shipment or maintenance of the vehicle-mounted device 3 and can be used for authentication of unlocking. Also, in the case where the in-vehicle apparatus 3 receives the key information including the key from the management server 1, the in-vehicle side storage module 50 also stores the received key information; the on-vehicle side memory module 50 may be a dedicated circuit capable of achieving the above functions or a program module executed by a processor.
The collation module 60 collates the authentication key from the user terminal with the key held by the in-vehicle apparatus 3. And the control results are used for unlocking. Specifically, when the in-vehicle side receiving module receives the authentication key information including the authentication key from the user terminal 2, the collation module 60 extracts the key or the spare key stored in the in-vehicle side storage module, collates the extracted key or spare key with the authentication key transmitted from the user terminal 2. Here, the collation module 60 preferentially extracts the key received from the management server 1 for collation, extracts the spare key stored in advance in the in-vehicle side storage module 50 when the key stored in the in-vehicle side storage module is not extracted, and collates the extracted spare key with the received authentication key. The collation module 60 may be a dedicated circuit capable of realizing the above functions or a program module executed by a processor.
The collation module 60 may collate the key received from the management server 1 with the authentication key, and if the authentication fails due to inconsistent collation results, extract the spare key stored in advance in the in-vehicle storage module 50 and collate the key. If the backup key is not matched, information indicating authentication failure is returned to the user terminal 2.
The unlocking module 70 unlocks the sharing vehicle when the comparison result of the comparison module 60 is consistent. The unlocking module 70 may record unlocking state information such as unlocking time and report the information to the management server 1 at regular intervals. The unlocking module 70 may be a dedicated circuit capable of realizing the above functions or a program module executed by a processor.
The respective modules of the in-vehicle device 3 of the present invention may be configured by program modules stored in a memory of the shared vehicle and executed by separate processors, or may be configured by circuit modules installed in the shared vehicle and capable of realizing the operations of the respective program modules, and may be realized in hardware.
In the first embodiment, the server-side storage module 10 corresponds to the "server-side storage section", the server-side transceiver module 20 corresponds to the "server-side transceiver section", the vehicle-mounted side receiving module 30 corresponds to the "vehicle-mounted side receiving section", the vehicle-mounted side transmitting module 40 corresponds to the "vehicle-mounted side transmitting section", the vehicle-mounted side storage module 50 corresponds to the "vehicle-mounted side storage section", the collation module 60 corresponds to the "collation section", and the unlocking module 70 corresponds to the "unlocking section". The flow of the shared vehicle management method in the first embodiment is described below with reference to fig. 3 to 5.
Fig. 3 is a flowchart illustrating authentication processing of the management server 1 in the shared vehicle management system according to the first embodiment.
The management server 1 is mainly responsible for issuing keys to the user terminal 2 and the in-vehicle device 3 in the shared vehicle management system. Specifically, the authentication process is started upon receiving a reservation request from the user terminal 2 or according to a schedule. First, a key (first key information) which may be randomly generated is transmitted to the authorized user terminal 2 (member authorized by the shared vehicle management system or user terminal transmitting reservation, etc.) and the reserved or designated in-vehicle apparatus 3 (step S301). Next, the response information indicating that the key has been received from the in-vehicle apparatus 3 is waited for, and it is determined in step S302 whether or not the response information has been received from the in-vehicle apparatus 3 within a prescribed time.
If the determination result in step S302 is yes, that means that the key is successfully issued, the authentication process may be ended.
When the determination result in step S302 is no due to a failure of the in-vehicle side transmission module of the in-vehicle apparatus, a network congestion, or the like, the server transceiver module 20 of the management server 1 extracts a spare key (second key) corresponding to the shared vehicle (in-vehicle apparatus 3) to be unlocked from the server side storage module 10, and transmits the spare key to the user terminal 2 as authentication key information (step S303). Thereby, the authentication process is completed.
In addition, the server-side transceiver module 20 of the management server 1 may continue to wait for receiving a notification indicating whether or not the in-vehicle device 3 is unlocked when the determination result in step S302 is yes. The notification may be issued by the user terminal 2 or by the in-vehicle apparatus 3.
Fig. 4 is a flowchart illustrating shared vehicle management of the in-vehicle device 3 in the shared vehicle management system according to the first embodiment.
First, the in-vehicle side reception module 30 of the in-vehicle apparatus 3 determines whether or not the key is received from the management server 1 (step 401), and if it is determined that the key is received from the management server 1 (yes in step 401), returns response information indicating that the key information is received to the management server 1, and stores the received key in the in-vehicle side storage module 50 (step 402).
Next, when an authentication request and an authentication key for the mounted shared vehicle are received from the user terminal 2 in step 403, the collation module 60 extracts the key stored in step 402 and the authentication key to collate (step S404), and when the collation result is identical, the shared vehicle is unlocked by the unlocking module 70 (step 405). Here, if the collation results are inconsistent, unlocking is not performed.
If it is determined in step 401 that the key is not received from the management server 1, the flow proceeds to step S406, and when an authentication request and an authentication key for the mounted shared vehicle are received from the user terminal 2 in step S406, the collation module 60 extracts a spare key (second key information) stored in advance in the vehicle-mounted side storage module 50, collates the extracted spare key with the authentication key (step S407), and when the collation result is identical, unlocks the shared vehicle by the unlocking module 70 (step 405). Here, if the collation results are inconsistent, unlocking is not performed.
Next, an operation sequence of the shared vehicle management system in a case where the in-vehicle apparatus 3 does not receive the first key information due to a problem such as network congestion will be described with reference to fig. 5. Fig. 5 is a sequence flow chart illustrating a shared vehicle management method according to the first embodiment.
As shown in fig. 5, when the user desires to use the shared vehicle, the user can find a usable shared vehicle, identify the shared vehicle by using a user terminal scan code such as a mobile phone in the vicinity of the shared vehicle, and transmit shared vehicle reservation information including identification information of the shared vehicle to the management server 1 (step S501). After receiving the shared vehicle reservation information (step S502), the management server 1 transmits key information to the user terminal 2 and the in-vehicle device 3 (step S503), wherein the user terminal 2 receives the key information smoothly (step S504), but the in-vehicle device 3 does not receive the key due to network congestion or the like, and the transmission of the key to the in-vehicle device 3 fails.
In this case, the user terminal 2 that received the key information transmits the received key as an authentication key to the in-vehicle device 3 together with the authentication request (step S505), and the in-vehicle device 3 that received the authentication key and the authentication request extracts the key, but fails in authentication because the key information from the management server 1 is not received. Even if the authentication is performed by extracting the pre-stored spare key, the authentication from the user terminal 2 fails because the authentication key does not match the spare key (step S506).
Next, the management server 1 waits for response information. When the response message from the in-vehicle apparatus 3 is not received within the predetermined time, the management server 1 starts the spare key stored in association with the confirmation message of the shared vehicle (in-vehicle apparatus 3) based on the confirmation message of the shared vehicle, transmits the spare key (second key information) to the user terminal 2 (step S507), and ends the process.
The user terminal 2 receives the spare key (step S508), and transmits the spare key as an authentication key to the in-vehicle apparatus 3 together with the authentication request (step S509). The in-vehicle device 3 that received the authentication key and the authentication request extracts a pre-stored spare key, collates the extracted spare key with the authentication key (step S510), and determines whether authentication is successful (step S511).
If the authentication is successful (yes in step S511), the process proceeds to step S513, where the shared vehicle is unlocked, and the user terminal 2 is sent with an unlock notification to end the process. If the authentication is unsuccessful (no in step S511), the flow proceeds to step S512, and the process ends after recommending another shared vehicle to the user terminal.
According to the present embodiment, when the key information from the management server is not received, the vehicle-mounted device extracts the spare key stored in the vehicle-mounted device and the authentication key information from the terminal, and performs unlocking according to the comparison result, so that unlocking failure can be avoided even when the authentication information cannot be obtained due to a failure, and the unlocking efficiency of the shared vehicle can be improved.
(second embodiment)
The second embodiment differs from the first embodiment in that, in addition to the first embodiment, the management server 1 in the shared-vehicle management system further has a shared-vehicle determination module 80, and the in-vehicle apparatus 3 further has a cancellation module 90. The following mainly describes differences between the second embodiment and the first embodiment, and redundant description is omitted as appropriate.
Fig. 6 is a block diagram illustrating a configuration of a shared vehicle management system according to the second embodiment. As shown in fig. 6, the shared vehicle management system includes: a vehicle-mounted device 3 mounted on the shared vehicle; a user terminal 2 which is held by a user, can accept a request from the user, and communicates with the in-vehicle device 3 and the network; the management server 1 is connected to the user terminal 2 or the vehicle-mounted device 3 of the shared vehicle via a network such as the internet, and manages key information for unlocking the shared vehicle.
The management server 1 includes a server-side storage module 10, a server-side transceiver module 20, and a shared vehicle determination module 80. The in-vehicle apparatus 3 includes an in-vehicle side receiving module 30, an in-vehicle side transmitting module 40, an in-vehicle side storing module 50, a collation module 60, an unlocking module 70, and an elimination module 90. The configuration of the user terminal 2, the server-side storage module 10, the server-side transceiver module 20, the in-vehicle-side receiving module 30, the in-vehicle-side transmitting module 40, the in-vehicle-side storage module 50, the collation module 60, and the unlocking module 70 is similar to that of the first embodiment, and thus detailed description thereof is omitted.
The shared-vehicle determining module 80 in the management server 1 is used to determine the shared vehicle to be used by the user. In the second embodiment, the user terminal may not specify the shared vehicle to be used by the code scanning or the like, but the shared vehicle determination module 80 in the management server 1 determines the shared vehicle using the user terminal 2 according to the position of the user terminal 2, the use period, the distribution situation of the shared vehicle, and the like.
In particular, when the server-side transceiver module 20 receives the user reservation information excluding the determination information from the user terminal 2, the shared-vehicle determination module 80 determines the shared vehicle based on the user reservation information, and transmits a key as an authentication key corresponding to the determination information to the user terminal 2; or transmits a spare key corresponding to the determined information of the determined shared car as an authentication key to the user terminal 2.
Further, the cancellation module 90 in the in-vehicle apparatus 3 can manage the respective pieces of key information stored in the in-vehicle side storage module 50 of the in-vehicle apparatus 3. For example, the cancellation module 90 cancels the key information stored in the in-vehicle side storage module that has been used in the collation process and the collation result is the coincidence, after the collation module 60 is unlocked each time the collation result is coincidence.
In the second embodiment, the shared vehicle determining module 80 corresponds to a "shared vehicle determining section", and the cancelling module 90 corresponds to a "cancelling section". The following describes operation sequence of the shared vehicle management system when the in-vehicle device 3 does not successfully transmit the response information due to a problem such as a network congestion or an abnormality in-vehicle device transmission, with reference to fig. 7. Fig. 7 is a sequence flow chart illustrating a shared vehicle management method according to the second embodiment.
As shown in fig. 7, when the user desires to use the shared vehicle, the user terminal 2 such as a mobile phone is used to transmit the shared vehicle reservation information to the management server 1 (step S701). The management server 1 receives the shared-vehicle reservation information, and determines, for example, the idle shared vehicle closest to the user terminal 2 as the shared vehicle suitable for the user terminal 2 based on the position of the user terminal 2 (step S703).
Next, the management server 1 transmits the key information to the user terminal 2 and the determined in-vehicle device 3 of the shared vehicle (step S705), the user terminal 2 receives the key information (step S704), and the in-vehicle device 3 also receives the key information (step S706). Thus, the in-vehicle apparatus 3 returns response information indicating that the key information was received to the management server 1 (step S707), and at this time, the in-vehicle apparatus 3 does not successfully transmit the response information to the management server 1 due to a problem such as network congestion or an in-vehicle apparatus transmission abnormality.
In this case, since the management server 1 does not receive the response information from the in-vehicle apparatus 3 for a predetermined time, the management server 1 enables the spare key stored in correspondence with the determined determination information of the shared vehicle (in-vehicle apparatus 3), transmits the spare key (second key information) to the user terminal 2 (step S708), and ends the process.
The user terminal 2 receives the spare key (step S709), and at this time, the user is set up to come near the shared vehicle to be driven and establish a communication link with the shared vehicle by bluetooth or the like. At this time, the user terminal 2 that received the key information and the spare key transmits the latest received spare key as an authentication key together with the authentication request to the in-vehicle apparatus 3 (step S710), the in-vehicle apparatus 3 that received the authentication key and the authentication request sequentially extracts the key and the spare key stored in advance and collates the key with the authentication key to perform authentication (step S711), determines that authentication has failed when both collation results are unsuccessful (no in step S712), and transmits an authentication failure notification to the user terminal to end the process.
Here, after the user terminal 2 correctly transmits the spare key as the authentication key, the in-vehicle device 3 first extracts the key received from the management server 1 in step S706, collates the extracted key with the authentication key, but fails in authentication due to the fact that the key does not agree with the authentication key, and further, the in-vehicle device 3 next extracts the spare key stored in advance, collates the extracted spare key with the authentication key, and succeeds in authentication due to the fact that the spare key agrees with the authentication key, and determines that authentication is successful in step S712. Therefore, the process advances to step S713, where the shared vehicle is unlocked, and the process is terminated after the unlock notification is transmitted to the user terminal 2.
According to the present embodiment, the same technical effects as those of the first embodiment can be obtained.
In addition, according to the embodiment, the management server can automatically distribute the shared vehicles, so that the user can use the shared vehicles conveniently, and the time of the user is saved. In addition, the used secret key is eliminated in time, so that the secret key can be prevented from being maliciously reused, and the safety of the shared vehicle management system is improved.
(other modifications)
The preferred embodiments of the present invention have been described above, but the present invention is not limited thereto, and various embodiments may be used in combination. The order of execution of the steps may be changed as appropriate.
Further, part of the steps in the above embodiments may be omitted. For example, in step S512 in fig. 5, if authentication fails, the process may be ended without recommending another shared vehicle to the user terminal 2.
Further, since the management server 1 may transmit the key to the user terminal 2 after performing the bidirectional identity authentication with the in-vehicle device 3, the management server 1 may transmit the second key as the spare key directly to the user terminal 2 without transmitting the first key to the user terminal 2 when the management server 1 does not receive the response information.
When a plurality of pieces of key information are received from the management server 1, the in-vehicle device 3 may preferentially collate the latest key information or collate the latest key information with the authentication key information from the user terminal 2 in the order of reception.
The spare key stored in advance on the in-vehicle apparatus 3 side may be a different key from the key information transmitted from the management server 1 or may be the same key.
The management server 1 and the in-vehicle device 3 of the present invention may be provided as program modules executable by a computer, and may be stored in a storage medium such as a magnetic disk (floppy (registered trademark), hard disk, etc.), an optical disk (CD-ROM, DVD, etc.), an optical disk (MO), or a semiconductor memory.
While the present invention has been described with reference to several embodiments, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments may be implemented in other various forms, and various omissions, substitutions, and changes may be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and spirit of the invention, and are also included in the invention described in the scope of the claims and their equivalents.
Claims (9)
1. A shared vehicle management system is provided with an in-vehicle device mounted on a shared vehicle, a management server for managing key information for unlocking the shared vehicle, and a user terminal for communicating with the in-vehicle device and the management server,
the above-mentioned vehicle-mounted device includes:
a vehicle-mounted receiving unit configured to receive first key information transmitted from the management server and authentication key information transmitted from the user terminal;
a vehicle-mounted-side transmitting unit that transmits response information indicating that the first key information is received to the management server when the first key information is received from the management server;
an on-vehicle side storage unit which stores second key information in advance and stores the received first key information;
a collation unit configured to extract the first key information or the second key information stored in the in-vehicle storage unit when the in-vehicle reception unit receives the authentication key information from the user terminal, and collate the extracted first key information or second key information with the authentication key information transmitted from the user terminal; and
an unlocking unit for unlocking the shared vehicle when the comparison result of the comparison unit is identical;
the management server includes:
a server-side storage unit that stores, in advance, identification information for identifying a shared vehicle on which the vehicle-mounted device is mounted, in association with the second key information;
a server-side transmitting/receiving unit that transmits the first key information to the user terminal as the authentication key information for the shared vehicle, transmits the same first key information to the in-vehicle device, and receives the response information from the in-vehicle device;
when the response information is not received within a predetermined time after the server transmitting/receiving unit transmits the first key information to the in-vehicle device, the server transmitting/receiving unit transmits, to the user terminal, second key information stored in the server-side storage unit and corresponding to the identification information of the shared vehicle on which the in-vehicle device is mounted,
the collation unit extracts the second key information when the first key information stored in the in-vehicle storage unit is not extracted, and collates the extracted second key information with the received authentication key information.
2. The shared vehicle management system as recited in claim 1, wherein,
the shared vehicle is a shared vehicle.
3. The shared vehicle management system as recited in claim 1, wherein,
the server-side transmitting/receiving unit transmits the first key information to the user terminal as the authentication key information corresponding to the identification information or transmits the second key information corresponding to the identification information to the user terminal as the authentication key information when receiving user reservation information including the identification information from the user terminal.
4. The shared vehicle management system as recited in claim 1, wherein,
the management server further includes a shared vehicle determination unit,
when the server-side transmitting/receiving unit receives user reservation information not including the determination information from the user terminal, the shared vehicle determining unit determines a shared vehicle based on the user reservation information, and transmits the first key information as the authentication key information corresponding to the determination information to the user terminal; or transmitting the second key information corresponding to the specified information of the specified shared vehicle to the user terminal as the authentication key information.
5. The shared vehicle management system as recited in claim 1, wherein,
when the first key information and the second key information are stored in the in-vehicle storage unit, the collation unit collates the authentication key information with the first key information, and when the collation result is identical, the unlocking unit unlocks the shared vehicle, and when the collation result is not identical, the collation unit collates the authentication key information with the second key information.
6. The shared vehicle management system as recited in claim 1, wherein,
the above-described in-vehicle apparatus further has an eliminating portion,
the erasing unit erases the key information stored in the on-vehicle side storage unit, which has been used in the collation process and matches the collation result, after the collation unit is unlocked each time the collation result matches.
7. The shared vehicle management system as recited in claim 1, wherein,
when the user terminal receives the plurality of key information, the latest received key is transmitted to the vehicle-mounted device as authentication key information.
8. An in-vehicle apparatus mounted on a shared vehicle, comprising:
a vehicle-mounted side receiving unit that receives first key information transmitted from a management server and authentication key information transmitted from a user terminal;
a vehicle-mounted-side transmitting unit that transmits response information indicating that the first key information is received to the management server when the first key information is received from the management server;
an on-vehicle side storage unit which stores second key information in advance and stores the received first key information;
a collation unit configured to extract the first key information or the second key information stored in the in-vehicle storage unit when the in-vehicle reception unit receives the authentication key information from the user terminal, and collate the extracted first key information or second key information with the authentication key information transmitted from the user terminal;
an unlocking unit for unlocking the shared vehicle when the comparison result of the comparison unit is identical;
the collation unit extracts the second key information when the first key information stored in the in-vehicle storage unit is not extracted, and collates the extracted second key information with the received authentication key information.
9. A shared vehicle management method, comprising:
a step of transmitting the same first key information to a user terminal applying for the shared vehicle and the vehicle-mounted device mounted on the shared vehicle by a management server for managing key information for unlocking the shared vehicle;
the user terminal transmitting the received first key information to the in-vehicle device as authentication key information corresponding to the in-vehicle device;
transmitting response information indicating that the first key information is received to the management server when the first key information is received by the in-vehicle device, comparing the authentication key information received from the user terminal with the first key information, and unlocking the shared vehicle when the comparison result is identical;
a step in which the management server transmits second key information corresponding to the in-vehicle device to the user terminal as authentication key information when the response information is not received within a predetermined time after the first key information is transmitted to the in-vehicle device;
the user terminal transmitting the received second key information to the in-vehicle device as the authentication key information; and
and a step of, when the vehicle-mounted device receives the authentication key information from the user terminal and does not receive the first key information from the management server, collating the authentication key information received from the user terminal with the second key information, and unlocking the shared vehicle when the collation result is identical.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810595347.3A CN110581876B (en) | 2018-06-11 | 2018-06-11 | Vehicle-mounted device, shared vehicle management system and shared vehicle management method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810595347.3A CN110581876B (en) | 2018-06-11 | 2018-06-11 | Vehicle-mounted device, shared vehicle management system and shared vehicle management method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110581876A CN110581876A (en) | 2019-12-17 |
| CN110581876B true CN110581876B (en) | 2023-05-26 |
Family
ID=68809876
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810595347.3A Active CN110581876B (en) | 2018-06-11 | 2018-06-11 | Vehicle-mounted device, shared vehicle management system and shared vehicle management method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110581876B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2013254270A (en) * | 2012-06-05 | 2013-12-19 | Sage Co Ltd | Vehicle management system, vehicle management method, program and computer-readable recording medium in car sharing system |
| CN105100879A (en) * | 2014-05-13 | 2015-11-25 | 阿尔派株式会社 | Vehicle-mounted device and device authentication method |
| CN105262586A (en) * | 2015-10-28 | 2016-01-20 | 铁将军汽车电子有限公司 | Key distribution method and apparatus for automobile theftproof equipment |
| WO2017207641A1 (en) * | 2016-06-03 | 2017-12-07 | Volkswagen Aktiengesellschaft | Apparatus, system and method for dynamic identification and key managemement for vehicle access |
| JP2018003330A (en) * | 2016-06-28 | 2018-01-11 | トヨタ自動車株式会社 | Lock and unlock system and key unit |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101855861A (en) * | 2007-11-16 | 2010-10-06 | 富士通天株式会社 | Authentication method, authentication system, on-vehicle device, and authentication device |
| US20170080896A1 (en) * | 2015-09-18 | 2017-03-23 | Ford Global Technologies, Llc | Method and apparatus for secure pairing based on fob presence |
-
2018
- 2018-06-11 CN CN201810595347.3A patent/CN110581876B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2013254270A (en) * | 2012-06-05 | 2013-12-19 | Sage Co Ltd | Vehicle management system, vehicle management method, program and computer-readable recording medium in car sharing system |
| CN105100879A (en) * | 2014-05-13 | 2015-11-25 | 阿尔派株式会社 | Vehicle-mounted device and device authentication method |
| CN105262586A (en) * | 2015-10-28 | 2016-01-20 | 铁将军汽车电子有限公司 | Key distribution method and apparatus for automobile theftproof equipment |
| WO2017207641A1 (en) * | 2016-06-03 | 2017-12-07 | Volkswagen Aktiengesellschaft | Apparatus, system and method for dynamic identification and key managemement for vehicle access |
| JP2018003330A (en) * | 2016-06-28 | 2018-01-11 | トヨタ自動車株式会社 | Lock and unlock system and key unit |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110581876A (en) | 2019-12-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10668896B2 (en) | Car sharing system and car sharing method | |
| US9070279B2 (en) | Electronic key registration system | |
| JP6426574B2 (en) | Car sharing system and vehicle loan return method | |
| JP6662965B2 (en) | Car sharing system and vehicle lending return method | |
| CN110091828B (en) | Vehicle key control method and device | |
| EP3312060B1 (en) | Vehicle start method | |
| US10645578B2 (en) | System for using mobile terminals as keys for vehicles | |
| US10659457B2 (en) | Information processing device, information processing system, and information processing method | |
| CN106416332B (en) | Mobile phone capable of automatic pairing with motor vehicle and automatic pairing method | |
| KR101881167B1 (en) | Car control system | |
| US20150161832A1 (en) | Method and Apparatus for Virtual Key Delivery | |
| US20170372547A1 (en) | Locking and unlocking system, server used for locking and unlocking system and method for executing locking and unlocking system | |
| CN103035054A (en) | NFC intelligent automobile key system with permission and authorization functions | |
| JP2019036091A (en) | Vehicle security system and vehicle security method | |
| KR101745443B1 (en) | Authentication system for driver of vehicle | |
| JP7056370B2 (en) | Authentication information issuing device and delivery system | |
| CN108737090B (en) | Method and apparatus for dynamic vehicle key generation and processing | |
| CN113709695A (en) | Vehicle use authorization method and system | |
| JP2013258491A (en) | Car sharing system and car sharing provisioning method | |
| CN113763602B (en) | Information processing apparatus, information processing method, and non-transitory storage medium | |
| JP2005081995A (en) | On-vehicle terminal device, and vehicular operation control system | |
| CN110581876B (en) | Vehicle-mounted device, shared vehicle management system and shared vehicle management method | |
| CN110304017B (en) | Vehicle-mounted authentication device, authentication method, and storage medium | |
| JP2020021161A (en) | Communication device | |
| JP4699853B2 (en) | Insurance authentication apparatus, authority holding apparatus, authority delegation system, authority delegation permission method, and authority delegation permission program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |