CN110581876A - Vehicle-mounted equipment, shared vehicle management system and shared vehicle management method - Google Patents
Vehicle-mounted equipment, shared vehicle management system and shared vehicle management method Download PDFInfo
- Publication number
- CN110581876A CN110581876A CN201810595347.3A CN201810595347A CN110581876A CN 110581876 A CN110581876 A CN 110581876A CN 201810595347 A CN201810595347 A CN 201810595347A CN 110581876 A CN110581876 A CN 110581876A
- 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.)
- Granted
Links
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 an on-board device, a shared vehicle management system, and a shared vehicle management method, which can avoid unlocking failure even when authentication information cannot be obtained due to a failure, and can improve the unlocking efficiency of a shared vehicle. The vehicle-mounted device includes: a vehicle-mounted side receiving unit that receives the first key information and the authentication key information; an in-vehicle side transmitting unit that transmits response information to the management server when the first key information is received; an on-vehicle 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 the second key information with the authentication key information; the unlocking part is used for unlocking the shared vehicle when the comparison result is consistent; when the first key information is not extracted, the comparison unit extracts the second key information and compares the extracted second key information with the received authentication key information.
Description
Technical Field
the embodiment of the invention relates to vehicle-mounted equipment of a shared vehicle, a shared vehicle management system and a shared vehicle management method.
background
Currently, with the development of sharing economy, the utilization of sharing vehicles such as sharing automobiles is gradually accepted by the public. Where a user wishes to use a shared vehicle, the shared vehicle is unlocked or locked by obtaining authorization from a regulatory agency. In the prior art, a user often uses a user terminal owned by the user to send and receive information to and from a shared vehicle through wireless communication such as bluetooth and wifi to lock/unlock.
Wireless communication using bluetooth will be described as an example. First, a user makes a reservation for a shared vehicle to a management server for managing the shared vehicle through a network such as the internet by using a relevant APP provided in a terminal device, the management server receives a reservation request, returns a key corresponding to a specific shared vehicle to the user terminal, and transmits reservation request information, the key, information on the terminal device that made a reservation for the vehicle, and the like to the shared vehicle through remote communication (for security, for example, a telephone network), and the shared vehicle returns a response to the management server after receiving the above information.
And the shared vehicle completing the bidirectional identity authentication establishes a link with the terminal equipment by using the acquired information related to the terminal equipment, and authenticates the terminal equipment by using the secret key after the link is connected. For example, the shared vehicle connected through the bluetooth is matched with the terminal device for identity authentication, and the shared vehicle is unlocked after matching is successful.
However, since the management server does not necessarily communicate with the terminal and the user using the same network, if bidirectional authentication is unsuccessful due to a communication failure or interruption between the shared vehicle and the server, the shared vehicle may not obtain the key information from the server and cannot authenticate with the user terminal, and the server may not obtain the response information and cannot manage the shared vehicle. In this case, the display result of the user terminal is that the door unlocking of the reserved vehicle fails, the manager of the shared vehicle needs to be contacted, and it takes more time, and the user experience is poor.
disclosure of Invention
the present invention has been made in view of the above problems, and an object thereof is to provide an in-vehicle device, a shared vehicle management system, and a shared vehicle management method that can avoid an unlocking failure and improve the unlocking efficiency of a shared vehicle even when authentication information cannot be obtained due to a failure.
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 that receives the first key information transmitted from the management server and the authentication key information transmitted from the user terminal; an in-vehicle side transmission 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 storage unit that stores second key information in advance and stores the received first key information; a verification unit configured to extract the first key information or the second key information stored in the in-vehicle storage unit when the in-vehicle receiving unit receives authentication key information from the user terminal, and to verify 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 in-vehicle 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; transmitting the same first key information to the vehicle-mounted device and receiving the response information from the vehicle-mounted device; when the server transmitter-receiver unit does not receive the response information within a predetermined time after transmitting the first key information to the in-vehicle device, the server transmitter-receiver unit transmits, to the user terminal, second key information corresponding to identification information of a shared vehicle on which the in-vehicle device is mounted, which is stored in the server-side storage unit, as authentication key information, and when the first key information stored in the in-vehicle-side storage unit is not extracted, the collating unit extracts the second key information and collates the extracted second key information with the received authentication key information.
Another embodiment of the present invention is an in-vehicle device mounted on a shared vehicle, including: a vehicle-mounted receiving unit that receives the first key information transmitted from the management server and the authentication key information transmitted from the user terminal; an in-vehicle side transmission 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 storage unit that stores second key information in advance and stores the received first key information; a verification unit configured to extract the first key information or the second key information stored in the in-vehicle storage unit when the in-vehicle receiving unit receives authentication key information from the user terminal, and to verify 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 consistent; the verification unit extracts the second key information when the first key information stored in the on-vehicle storage unit is not extracted, and verifies 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 shared vehicle and the user terminal, so that even if the shared vehicle cannot obtain the first key due to the fact that a communication module of the shared vehicle is damaged or a communication signal is poor, the unlocking failure can be avoided, the unlocking efficiency of the shared vehicle can be improved, and the user experience is better while the user time is saved.
drawings
Fig. 1 is a schematic diagram illustrating the configuration of the 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 for explaining the authentication process 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 device in the shared vehicle management system according to the first embodiment.
Fig. 5 is a timing flowchart illustrating the shared vehicle management method according to the first embodiment.
Fig. 6 is a block diagram illustrating the configuration of the shared vehicle management system according to the second embodiment.
Fig. 7 is a timing flowchart illustrating the shared vehicle management method according to the second embodiment.
Description of the reference numerals:
1 managing a server; 2, user terminal; 3, vehicle-mounted equipment; 10 a server side storage module; 20 a server-side transceiver module; 30 vehicle-mounted side receiving modules; 40 vehicle-mounted side transmitting module; 50 vehicle-mounted side storage modules; 60 a comparison module; 70 unlocking the module; 80 share a vehicle determination module; 90 elimination of 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 refers to a vehicle that is provided by a supplier and can be rented and used by a user according to needs, the form of the shared vehicle is not limited, and the shared vehicle is an automobile for description.
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: an in-vehicle device 3 mounted on a shared vehicle; a user terminal 2, which is held by a user, and which can receive a request from the user and communicate with the in-vehicle device 3 and the server; the management server 1 is remotely connected to the user terminal 2 or the in-vehicle device 3 of the shared vehicle via a network such as the internet, and manages key information for unlocking the shared vehicle.
When the respective 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 makes a reservation of a shared vehicle by transmitting vehicle reservation information (i) to a management server 1 for managing the shared vehicle via a network such as the internet using a relevant APP provided in a user terminal 2, the management server 1 receives a reservation request, returns a key (ii) corresponding to a specific shared vehicle to the user terminal 2, and transmits reservation request information, information related to the terminal device 2, and the key (iii) to an in-vehicle device 3 by remote communication (for safety, for example, a telephone network), and the in-vehicle device 3, after receiving the reservation-related information and the key, returns response information (iv) to the management server 1, and completes bidirectional authentication between the in-vehicle device 3 and the management server 1 by (iv). The information transmitted in the bidirectional authentication may use various existing information formats and contents, or may use techniques such as data encryption to prevent falsification.
The in-vehicle device 3 that completes bidirectional authentication establishes a link with the user terminal 2 using the acquired information on the user terminal 2, and the in-vehicle device 3 compares 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 comparison is successful, thereby completing authentication.
secondly, the shared vehicle management system of the present invention can also cope with a case where bidirectional authentication between the in-vehicle device 3 and the management server 1 fails. Preferred embodiments of the present invention will be described below with reference to the accompanying drawings. In the different embodiments, the same reference numerals are used for the same or similar portions, and the duplicate description is appropriately omitted.
(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 the user. The user terminal 2 has hardware such as an antenna, a processor, and a memory, and is capable of operating a shared vehicle reservation program and communicating 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 approach a shared vehicle to be reserved and may 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 may 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 making a reservation for a shared vehicle, the user terminal 2 may first transmit reservation request information to the management server 1, and may include specification information (shared vehicle identifier) specifying a specific shared vehicle in the reservation request information in order to reserve the specific shared vehicle. Next, 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 shared 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, and the backup key corresponding to the specific shared vehicle (the in-vehicle device 3) can be extracted based on the identification information. The server-side storage module 10 may be a dedicated circuit capable of implementing 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 the lock of the 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 generated at random for a reserved vehicle by the management server side upon receiving the vehicle reservation information of the user terminal 2, or may be key information stored in advance. When the vehicle reservation information of the user terminal 2 includes the identification information of the shared vehicle, the server-side transmission/reception module 20 transmits the key to the user terminal 2 as the authentication key information corresponding to the identification information. The server-side transceiver module 20 also transmits the key (first key information) for unlocking the lock of the reserved shared vehicle, which is generated or stored as described above, to the in-vehicle device 3, and receives response information in response to the transmission of the key from the in-vehicle device 3, in response to the reception of the key by the in-vehicle device 3. When the server transceiver module 20 does not receive the response information within a predetermined time after transmitting the key to the in-vehicle device 3, the server transceiver module 20 extracts the spare key (second key) corresponding to the received identification information from the server-side storage module 10, and transmits the spare key to the user terminal 2 as the authentication key information. The predetermined time may be arbitrarily set according to the network property and the data transfer rate, and may be set to a threshold value larger than the time taken in the case of the normal transfer rate, for example. The server-side transceiver module 20 may be a dedicated circuit or a program module executed by a processor that can implement the above functions.
The in-vehicle apparatus 3 includes an in-vehicle side reception module 30, an in-vehicle side transmission module 40, an in-vehicle side storage module 50, a collation module 60, and an unlock module 70.
the vehicle-mounted side receiving module 30 is used for receiving 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 vehicle-mounted-side receiving module 30 may be a dedicated circuit capable of realizing the above functions or a program module executed by a processor.
The vehicle-mounted 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 the reception of the key information to the management server 1. The vehicle-mounted side transmission module 40 may be a dedicated circuit capable of realizing the above functions or a program module executed by a processor.
The on-vehicle side memory module 50 is used to store information required for unlocking. In particular, the on-board storage module 50 stores a spare key (second key information) corresponding to the on-board device in advance, and the spare key can be used for authentication of unlocking, and can be stored in the on-board storage module 50 when the on-board device 3 is shipped or maintained. And, in the case where the in-vehicle device 3 receives key information including a key from the management server 1, the in-vehicle-side storage module 50 also stores the received key information; the on-vehicle side storage module 50 may be a dedicated circuit capable of realizing the above functions or a program module executed by a processor.
the collation module 60 performs collation between the authentication key from the user terminal and the key held by the in-vehicle device 3. And the comparison result is used for unlocking. Specifically, when the vehicle-mounted-side receiving module receives authentication key information including an authentication key from the user terminal 2, the collation module 60 extracts the key or the spare key stored in the vehicle-mounted-side storage module, and 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, and when the key stored in the on-vehicle side storage module is not extracted, extracts the spare key stored in advance in the on-vehicle side storage module 50, and collates the extracted spare key with the received authentication key. The comparing module 60 may be a dedicated circuit or a program module executed by a processor capable of implementing the above functions.
The comparison module 60 may compare the key received from the management server 1 with the authentication key, and extract the spare key stored in advance in the in-vehicle storage module 50 to compare the spare key when the comparison result is inconsistent and the authentication fails. If the comparison of the spare keys does not match, information indicating that the authentication has failed is returned to the user terminal 2.
The unlocking module 70 unlocks the shared vehicle when the comparison result of the comparison module 60 is consistent. The unlock module 70 may record unlock state information such as unlock time and periodically report the unlock state information to the management server 1. The unlocking module 70 may be a dedicated circuit or a program module executed by a processor capable of implementing the above functions.
Each module of the in-vehicle device 3 according to the present invention may be implemented by a program module stored in a memory of the shared vehicle and executed by an independent processor, or may be implemented by a circuit module mounted in the shared vehicle and capable of implementing an operation of each program module and implemented in hardware.
In the first embodiment, the server-side storage module 10 corresponds to a "server-side storage unit", the server-side transmission/reception module 20 corresponds to a "server-side transmission/reception unit", the vehicle-side reception module 30 corresponds to a "vehicle-side reception unit", the vehicle-side transmission module 40 corresponds to a "vehicle-side transmission unit", the vehicle-side storage module 50 corresponds to a "vehicle-side storage unit", the comparison module 60 corresponds to a "comparison unit", and the unlock module 70 corresponds to an "unlock unit". The following describes a flow of a shared vehicle management method in the first embodiment with reference to fig. 3 to 5.
fig. 3 is a flowchart for explaining the authentication process 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 (a member approved by the shared vehicle management system or a user terminal that transmits a reservation, etc.) and the reserved or designated in-vehicle device 3 (step S301). Next, 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 predetermined time.
If the determination result in step S302 is yes, indicating that the key is successfully issued, the authentication process may be terminated.
When the determination result in step S302 is no due to a failure of the vehicle-mounted side transmission module of the vehicle-mounted device, 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 (vehicle-mounted device 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 transmission/reception module 20 of the management server 1 may continue to wait for the reception of the notification indicating whether 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 the in-vehicle apparatus 3.
Fig. 4 is a flowchart illustrating shared vehicle management by the in-vehicle device 3 in the shared vehicle management system according to the first embodiment.
First, the vehicle-mounted-side receiving module 30 of the vehicle-mounted device 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 vehicle-mounted-side storage module 50 (step 402).
next, when receiving an authentication request and an authentication key for the mounted share car from the user terminal 2 in step 403, the matching module 60 extracts the key stored in step 402 and compares the key with the authentication key (step S404), and when the comparison result shows that the key and the authentication key match, the unlock module 70 unlocks the share car (step S405). Here, if the collation results are not consistent, the unlocking is not performed.
When it is determined in step 401 that the key is not received from the management server 1, the process proceeds to step S406, and when an authentication request and an authentication key for the shared vehicle mounted are received from the user terminal 2 in step 406, the comparison module 60 extracts the spare key (second key information) stored in advance in the vehicle-mounted storage module 50, compares the extracted spare key with the authentication key (step S407), and when the comparison result is matched, the shared vehicle is unlocked by the unlocking module 70 (step S405). Here, if the collation results are not consistent, the unlocking is not performed.
next, the operation sequence of the shared vehicle management system in the case where the vehicle-mounted device 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 timing flowchart illustrating the 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 finds a usable shared vehicle, confirms the shared vehicle by scanning a code using a user terminal such as a mobile phone in the vicinity of the shared vehicle, and transmits shared vehicle reservation information including confirmation 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), where the user terminal 2 successfully receives the key information (step S504), and the in-vehicle device 3 fails to transmit the key to the in-vehicle device 3 because the key is not received due to network congestion or the like.
In this case, the user terminal 2 that has received the key information transmits the received key to the in-vehicle device 3 as an authentication key together with the authentication request (step S505), and the in-vehicle device 3 that has 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 backup key stored in advance is extracted for authentication, the authentication fails because the authentication key from the user terminal 2 does not match the backup key (step S506).
Next, the management server 1 waits for response information. When the response information from the in-vehicle device 3 is not received within the predetermined time, the management server 1 activates the spare key stored in association with the confirmation information of the shared vehicle (in-vehicle device 3) based on the confirmation information of the shared vehicle, transmits the spare key (second key information) to the user terminal 2 (step S507), and ends the processing.
the user terminal 2 receives the spare key (step S508), and transmits the spare key to the in-vehicle device 3 as the authentication key together with the authentication request (step S509). The in-vehicle device 3 that has received the authentication key and the authentication request extracts the backup key stored in advance, compares the extracted backup key with the authentication key (step S510), and determines whether the authentication is successful (step S511).
If the authentication is successful (yes in step S511), the process proceeds to step S513, the shared vehicle is unlocked, an unlock notification is transmitted to the user terminal 2, and the process is terminated. If the authentication is unsuccessful (no in step S511), the process proceeds to step S512, and the process is terminated after recommending another shared vehicle to the user terminal.
According to the embodiment, when the key information from the management server is not received, the vehicle-mounted equipment extracts the spare key stored by the vehicle-mounted equipment and compares the spare key with the authentication key information from the terminal, and unlocks according to the comparison result, so that the unlocking failure can be avoided even if the authentication information cannot be obtained due to a fault, and the unlocking efficiency of the shared vehicle can be improved.
(second embodiment)
The second embodiment is different from the first embodiment in that the management server 1 in the shared-vehicle management system further includes a shared-vehicle specifying module 80 and the in-vehicle device 3 further includes a removal module 90 in the second embodiment. Hereinafter, differences between the second embodiment and the first embodiment will be mainly described, and redundant description will be omitted as appropriate.
fig. 6 is a block diagram illustrating the configuration of the shared vehicle management system according to the second embodiment. As shown in fig. 6, the shared vehicle management system includes: an in-vehicle device 3 mounted on a shared vehicle; a user terminal 2, which is held by a user and can receive a user request and communicate with the in-vehicle device 3 and the network; the management server 1 is remotely connected to the user terminal 2 or the in-vehicle 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 collating module 60, an unlocking module 70, and a canceling module 90. The configurations 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 comparing module 60, and the unlocking module 70 are similar to those of the first embodiment, and detailed descriptions thereof are omitted.
the shared vehicle determination module 80 in the management server 1 is used to determine a 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 scanning a code 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 location of the user terminal 2, the use time period, the distribution of the shared vehicles, and the like.
In particular, when the server-side transceiver module 20 receives the user reservation information not including the determination information from the user terminal 2, the shared cart determination module 80 determines the shared cart based on the user reservation information and transmits a key to the user terminal 2 as an authentication key corresponding to the determination information; or transmits a spare key corresponding to the determined specifying information of the shared vehicle as the authentication key to the user terminal 2.
Further, the eliminating module 90 in the in-vehicle apparatus 3 can manage the respective key information stored in the in-vehicle-side storage module 50 of the in-vehicle apparatus 3. For example, the eliminating module 90 eliminates the key information stored in the vehicle-mounted-side storage module, which has been used in the collation process and for which the collation result is identical, after the collation module 60 is unlocked every time the collation result is identical.
In the second embodiment, the shared vehicle specifying module 80 corresponds to a "shared vehicle specifying unit", and the eliminating module 90 corresponds to an "eliminating unit". The operation sequence of the shared vehicle management system in the case where the in-vehicle device 3 has not successfully transmitted the response information due to a problem such as a network congestion or an abnormality in transmission of the in-vehicle device will be described below with reference to fig. 7. Fig. 7 is a timing flowchart illustrating the 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 shared vehicle reservation information to the management server 1 (step S701). The management server 1 receives the shared vehicle reservation information, and determines an idle shared vehicle closest to the user terminal 2 as a shared vehicle suitable for the user terminal 2, for example, according to 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 vehicle-mounted device 3 of the specified shared vehicle (step S705), the user terminal 2 receives the key information (step S704), and the vehicle-mounted device 3 also receives the key information (step S706). Thereby, the in-vehicle apparatus 3 returns response information indicating that the key information is 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 abnormality in transmission of the in-vehicle apparatus.
In this case, since the management server 1 does not receive the response information from the in-vehicle device 3 within the predetermined time, the management server 1 activates the spare key stored in association with the identification information of the identified shared vehicle (in-vehicle device 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 comes near the shared vehicle to be driven and establishes a communication link with the shared vehicle by bluetooth or the like. At this time, the user terminal 2 that has received the key information and the spare key transmits the spare key that has been received most recently to the in-vehicle device 3 as an authentication key together with an authentication request (step S710), the in-vehicle device 3 that has received the authentication key and the authentication request sequentially extracts the key and compares the key with the spare key and the authentication key that have been stored in advance to perform authentication (step S711), determines that the authentication has failed when the comparison results are unsuccessful twice (no in step S712), and transmits an authentication failure notification to the user terminal to end the process.
Here, after the user terminal 2 has correctly transmitted 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, compares the extracted key with the authentication key, but the authentication fails because the key does not match the authentication key, and further, the in-vehicle device 3 next extracts the spare key stored in advance, compares the extracted spare key with the authentication key, and determines that the authentication has succeeded because the spare key matches the authentication key, thereby determining that the authentication has succeeded in step S712. Therefore, the process proceeds to step S713, the shared vehicle is unlocked, an unlock notification is sent to the user terminal 2, and the process is terminated.
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 allocate the shared vehicles, so that the shared vehicles can be conveniently used by the user, and the time of the user is saved. In addition, the key which is used is eliminated in time, so that the key can be prevented from being used repeatedly and maliciously, and the safety of the shared vehicle management system is improved.
(other modification example)
The preferred embodiments of the present invention have been described above, but the present invention is not limited thereto, and different embodiments may be used in combination. The order of execution of the steps may be changed as appropriate.
In addition, some steps in the above embodiments may be omitted. For example, step S512 in fig. 5 may be omitted, and when the authentication fails, the process may be terminated 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 bidirectional authentication with the in-vehicle device 3, the management server 1 may directly transmit the second key as the spare key 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 receiving a plurality of pieces of key information from the management server 1, the in-vehicle device 3 may preferentially perform collation using the latest key information or may sequentially perform collation with the authentication key information from the user terminal 2 in the order of reception.
the spare key stored in advance in the in-vehicle device 3 may be a key different 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 distributed as program modules that can be executed by a computer and stored in a storage medium such as a magnetic disk (floppy (registered trademark), hard disk, or the like), an optical disk (CD-ROM, DVD, or the like), an optical disk (MO), or a semiconductor memory.
while the embodiments of the present invention have been described above, these embodiments are presented as examples and are not intended to limit the scope of the invention. These new embodiments may be implemented in various other ways, and various omissions, substitutions, and changes may be made without departing from the spirit of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are also included in the invention described in the claims and the equivalent scope thereof.
Claims (9)
1. A shared vehicle management system comprising 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 on-vehicle equipment includes:
A vehicle-mounted receiving unit that receives the first key information transmitted from the management server and the authentication key information transmitted from the user terminal;
An in-vehicle side transmission 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 storage unit that stores second key information in advance and stores the received first key information;
A verification unit configured to extract the first key information or the second key information stored in the in-vehicle storage unit when the in-vehicle receiving unit receives authentication key information from the user terminal, and to verify 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 consistent;
the management server includes:
A server-side storage unit that stores, in advance, identification information for identifying a shared vehicle on which the in-vehicle 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 server transmitter-receiver unit does not receive the response information within a predetermined time after the server transmitter-receiver unit transmits the first key information to the in-vehicle device, the server transmitter-receiver unit transmits second key information corresponding to the identification information of the shared vehicle on which the in-vehicle device is mounted, which is stored in the server-side storage unit, to the user terminal as authentication key information,
The verification unit extracts the second key information when the first key information stored in the on-vehicle storage unit is not extracted, and verifies the extracted second key information with the received authentication key information.
2. The shared vehicle management system of claim 1,
the shared vehicle is a shared automobile.
3. the shared vehicle management system of claim 1,
The server-side transmitting/receiving unit transmits, when receiving user reservation information including the identification information from the user terminal, the first key information as the authentication key information corresponding to the identification information to the user terminal, or transmits the second key information corresponding to the identification information as the authentication key information to the user terminal.
4. The shared vehicle management system of claim 1,
The management server further includes a shared vehicle specifying unit,
When the server-side transmitting/receiving unit receives, from the user terminal, user reservation information not including the identification information, the shared vehicle identification unit identifies a shared vehicle based on the user reservation information, and transmits the first key information to the user terminal as the authentication key information corresponding to the identification information; or transmitting the second key information corresponding to the identification information of the identified shared vehicle to the user terminal as the authentication key information.
5. The shared vehicle management system of claim 1,
The verification unit verifies the authentication key information with the first key information when the first key information and the second key information are stored in the on-vehicle storage unit, unlocks the shared vehicle when the verification result is coincident, and verifies the authentication key information with the second key information when the verification result is not coincident.
6. The shared vehicle management system of claim 1,
The above-mentioned in-vehicle apparatus further has a cancellation section,
the erasing unit erases the key information of the matching result stored in the on-vehicle storage unit after the matching unit is unlocked every time the matching result matches.
7. The shared vehicle management system of claim 1,
And when the user terminal receives a plurality of key information, the latest received key is used as authentication key information and is sent to the vehicle-mounted equipment.
8. An in-vehicle apparatus mounted on a shared vehicle, characterized by comprising:
A vehicle-mounted receiving unit that receives the first key information transmitted from the management server and the authentication key information transmitted from the user terminal;
An in-vehicle side transmission 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 storage unit that stores second key information in advance and stores the received first key information;
A verification unit configured to extract the first key information or the second key information stored in the in-vehicle storage unit when the in-vehicle receiving unit receives authentication key information from the user terminal, and to verify 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 consistent;
The verification unit extracts the second key information when the first key information stored in the on-vehicle storage unit is not extracted, and verifies the extracted second key information with the received authentication key information.
9. a shared vehicle management method is characterized by comprising the following steps:
A step in which a management server that manages key information for unlocking a shared vehicle transmits the same first key information to a user terminal that applies for the shared vehicle and to an in-vehicle device mounted on the shared vehicle;
transmitting, by the user terminal, 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 indicates that the authentication key information and the first key information match;
A step in which the management server transmits, to the user terminal, second key information corresponding to the in-vehicle device 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;
A step in which the user terminal transmits the received second key information to the in-vehicle device as the authentication key information; and
And a step in which the vehicle-mounted device stores the second key information in advance, and 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, the vehicle-mounted device compares the authentication key information received from the user terminal with the second key information, and when the comparison result shows that the authentication key information and the first key information match, unlocks the shared vehicle.
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 true CN110581876A (en) | 2019-12-17 |
| CN110581876B 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 (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100241857A1 (en) * | 2007-11-16 | 2010-09-23 | Okude Kazuhiro | Authentication method, authentication system, in-vehicle device, and authentication apparatus |
| 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 |
| US20170080896A1 (en) * | 2015-09-18 | 2017-03-23 | Ford Global Technologies, Llc | Method and apparatus for secure pairing based on fob presence |
| 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 |
-
2018
- 2018-06-11 CN CN201810595347.3A patent/CN110581876B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100241857A1 (en) * | 2007-11-16 | 2010-09-23 | Okude Kazuhiro | Authentication method, authentication system, in-vehicle device, and authentication apparatus |
| 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 |
| US20170080896A1 (en) * | 2015-09-18 | 2017-03-23 | Ford Global Technologies, Llc | Method and apparatus for secure pairing based on fob presence |
| 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 |
|---|---|
| CN110581876B (en) | 2023-05-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11451384B2 (en) | Vehicle access systems and methods | |
| JP6908451B2 (en) | Car sharing system and car sharing method | |
| US9070279B2 (en) | Electronic key registration system | |
| US10645578B2 (en) | System for using mobile terminals as keys for vehicles | |
| US9489789B2 (en) | Electronic key registration method and electronic key registration system | |
| US20150161832A1 (en) | Method and Apparatus for Virtual Key Delivery | |
| JP6426574B2 (en) | Car sharing system and vehicle loan return method | |
| CN106416332B (en) | Mobile phone capable of automatic pairing with motor vehicle and automatic pairing method | |
| US8269601B2 (en) | Multiuser vehicle utilization system and electronic key thereof | |
| US20190009747A1 (en) | Vehicle start method | |
| RU2695709C1 (en) | Locking and unlocking control system and locking and unlocking control method | |
| US20160140649A1 (en) | Method and Apparatus for Automated Rental Key Dispensal and Return | |
| CN103729915B (en) | Electronic key registration system and method | |
| US20140176301A1 (en) | Remote Function Fob for Enabling Communication Between a Vehicle and a Device and Method for Same | |
| CN109698854B (en) | Key information management device, key information management method, and computer-readable medium storing key information management program | |
| CN104973015A (en) | Remotely programmed keyless vehicle entry system | |
| US20130329890A1 (en) | Electronic key registration system | |
| CN103035054A (en) | NFC intelligent automobile key system with permission and authorization functions | |
| EP3453578B1 (en) | Unlocking control system and unlocking control method | |
| CN109697773B (en) | Key information management device and method, and key information sharing method | |
| US10812592B2 (en) | Method and apparatus for utilizing NFC to establish a secure connection | |
| JP2019036091A (en) | Vehicle security system and vehicle security method | |
| JP7056370B2 (en) | Authentication information issuing device and delivery system | |
| CN108737090B (en) | Method and apparatus for dynamic vehicle key generation and processing | |
| JP2013258491A (en) | Car sharing system and car sharing provisioning method |
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 |