WO2021020843A1

WO2021020843A1 - Shared-vehicle authentication method, device, and system

Info

Publication number: WO2021020843A1
Application number: PCT/KR2020/009866
Authority: WO
Inventors: 우혁준; 이상민; 정성일
Original assignee: 주식회사 디지파츠
Priority date: 2019-07-26
Filing date: 2020-07-27
Publication date: 2021-02-04
Also published as: KR102056340B1

Abstract

A shared-vehicle authentication method in a vehicle sharing server linked with a driver terminal and a shared vehicle through a communication network comprises the steps of: receiving, from a first driver terminal, an authentication key request message including first biometric information; generating a first biometric code by using the first biometric information; generating a first authentication key on the basis of the first biometric code and a first history code; transmitting, to the first driver terminal, an authentication key response message including the first authentication key; receiving, from a second driver terminal, an authentication key request message including second biometric information; generating a second biometric code by using the second biometric information; generating a second authentication key on the basis of the second biometric code and a second history code; and transmitting, to the second driver terminal, an authentication key response message including the second authentication key.

Description

Shared vehicle authentication method, device and system

The present disclosure relates to a vehicle sharing service, and more particularly, to a shared vehicle authentication method, apparatus, and system capable of providing more secure user authentication for a shared vehicle.

In recent years, amid the global interest in the sharing economy, a car-sharing (vehicle sharing) service in which vehicles are shared by a large number of unspecified vehicles is rapidly spreading, and as the number of users using the vehicle sharing service increases, the number of shared vehicles is rapidly increasing.

Vehicle-sharing service is a kind of rental car service in which a specific vehicle is rented for as long as necessary by an unspecified number of vehicles. , You can select and reserve a desired shared vehicle using an app installed on a smartphone.

Therefore, in order to minimize the inconvenience of customers using the vehicle sharing service, the risk of vehicle theft, and hacking, it is very important that user authentication for the shared vehicle is more secure.

The present disclosure is designed to solve the problems of the prior art, and an object of the present disclosure is to provide a shared vehicle authentication method, apparatus, and system.

An object of the present disclosure according to an embodiment is to provide a shared vehicle authentication method, apparatus, and system capable of providing a safer and more convenient vehicle sharing service through stronger user authentication.

The present disclosure according to an embodiment provides a shared vehicle authentication method, apparatus, and system capable of safely providing a vehicle sharing service regardless of a network state.

The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned are clearly understood by those of ordinary skill in the technical field to which the present disclosure belongs from the following description. Can be.

The present disclosure may provide a vehicle sharing service providing method, apparatus, and system.

A shared vehicle authentication method in a vehicle sharing server linked to a driver terminal and a shared vehicle through a communication network according to an exemplary embodiment of the present disclosure includes receiving an authentication key request message including first biometric information from a first driver terminal; Generating a first biometric code using the first biometric information, generating a first authentication key based on the first biometric code and a first history code, and an authentication key response including the first authentication key Transmitting a message to the first driver terminal, receiving an authentication key request message including second biometric information from a second driver terminal, and generating a second biometric code using the second biometric information; Generating a second authentication key based on the second biometric code and a second history code, and transmitting an authentication key response message including the second authentication key to the second driver terminal, the second 2 The history code may be the first authentication key.

In an embodiment, the method includes receiving a shared vehicle user registration request message including a vehicle type identifier corresponding to the shared vehicle from the first driver terminal and a collection target biometric information type based on the vehicle type identifier And transmitting a biometric information request message including the determined biometric information type to be collected to the first driver terminal, wherein the first biometric information is collected according to the determined biometric information type to be collected. It may be biometric information.

In an embodiment, the determined collection target biometric information type may be plural according to the vehicle type identifier.

As an example, the collected biometric information type may include at least one of a fingerprint recognition information type, an iris recognition information type, a facial recognition information type, a palm print recognition information type, and a voice recognition information type.

In an embodiment, the generating of the first authentication key includes classifying the first biometric information into first to K individual biometric information according to the type of biometric information to be collected and the first to Kth individual biometric information After filtering the included noise, generating a first to K individual biocode using a corresponding generation function, synthesizing the first to K individual biocodes to generate a synthesized biocode, and the synthesized biocode and the It may include the step of generating the first authentication key by exclusively ORing the first history code in bit units.

In an embodiment, the method includes receiving a shared vehicle return request message including location information of the first driver terminal from the first driver terminal and obtaining location information of the second driver terminal from the second driver terminal. And determining whether the first driver and the second driver are in a transferable area based on the location information of the first to second driver terminals, and if the determination result is in a transferable area, the second driver And transmitting an authentication initiation request message to the terminal, and when the authentication initiation request message is received, the second driver terminal may perform user authentication for the shared vehicle using the second authentication key.

In an embodiment, the method includes transmitting a shared vehicle return acceptance message to the first driver terminal, if the determination result is in a transferable area, and the first driver terminal receives the shared vehicle return acceptance message , It is possible to delete the first authentication key.

As an embodiment, the method includes the step of sequentially registering a corresponding authentication key to the shared vehicle according to the generation order, and when the authentication key registration fails due to a network state transitioning to an error state, the registration failed authentication key is a server queue. And when the network state transitions to a normal state, all authentication keys stored in the server queue may be registered in the shared vehicle.

As an example, when the network state transitions to an error state, the shared vehicle server may check the network state by transmitting a KEEP ALIVE message at regular intervals.

For example, the first to second biometric information may be encoded and received in a code capable of error correction and/or error detection, and the first to Kth individual biometric information may be decoded and then filtered.

A vehicle sharing server interlocked with a driver terminal and a shared vehicle through a communication network according to another embodiment of the present disclosure includes a controller of the vehicle sharing server and a communication module for exchanging information with the driver terminal through the communication network with the shared vehicle, and the driver. A biometric information collection module that collects biometric information from a terminal, an authentication key generation module that generates an authentication key based on the biometric information, and a reservation setting module that sets a usage reservation for the driver terminal and the shared vehicle, wherein the The authentication key generation module includes means for generating a first biometric code using first biometric information received from a first driver terminal, a means for generating a first authentication key based on the first biometric code and the first history code, And means for generating a second biometric code using the second biometric information received from the second driver terminal and means for generating a second authentication key based on the second biometric code and the second history code, the second 2 The history code may be the first authentication key.

In an embodiment, when receiving a shared vehicle user registration request message including a vehicle type identifier corresponding to the shared vehicle from the first driver terminal, the controller determines a collection target biometric information type based on the vehicle type identifier And transmitting a biometric information request message including the determined biometric information type to be collected to the first driver terminal, wherein the first biometric information may be biometric information collected according to the determined biometric information type to be collected.

In an embodiment, the authentication key generation module comprises a biometric information input unit for classifying the first biometric information into first to K individual biometric information according to the type of biometric information to be collected and inputting the biometric information to a decoder, and the first to Kth individual biometric information. After filtering the noise included in the information, a biometric code generator that generates first to K individual biocodes using a corresponding generation function, and a synthesis unit that synthesizes the first to K individual biocodes to generate a synthesized biocode; And a key generator configured to generate the first authentication key by exclusively ORing the synthesized biometric code and the first history code on a bit-by-bit basis.

In an embodiment, when receiving a request message for returning the shared vehicle including the location information of the first driver terminal from the first driver terminal, the controller obtains the location information of the second driver terminal from the second driver terminal, and , Based on the location information of the first to second driver terminals, it is determined whether the first driver and the second driver are in a transferable area, and as a result of the determination, if they are in a transferable area, the second driver terminal When an authentication initiation request message is transmitted, and when the authentication initiation request message is received, the second driver terminal may perform user authentication for the shared vehicle using the second authentication key.

In an embodiment, if the controller is in an area in which the takeover is possible as a result of the determination, the first driver terminal transmits a shared vehicle return acceptance message, and the first driver terminal receives the shared vehicle return acceptance message, the first 1 You can delete the authentication key.

In an embodiment, the controller performs a procedure of sequentially registering a corresponding authentication key to the shared vehicle according to a generation sequence, and when the authentication key registration fails due to a network state transitioning to an error state, the registration failed authentication key is sent to the server. It is stored in a queue, and when the network state transitions to a normal state, all authentication keys stored in the server queue can be controlled to be registered in the shared vehicle.

As an example, when the network state transitions to an error state, the controller may check the network state by transmitting a KEEP ALIVE message at a predetermined period.

For example, the first to second biometric information may be encoded and received in a code capable of error correction and/or error detection.

The aspects of the present disclosure are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the present disclosure will be described in detail below by those of ordinary skill in the art. It can be derived and understood on the basis of.

The effects on the method, apparatus, and system according to the present disclosure will be described as follows.

The present disclosure has the advantage of providing a shared vehicle authentication method, apparatus, and system.

The present disclosure according to an embodiment has the advantage of providing a safer and more convenient vehicle sharing service through stronger user authentication.

The present disclosure according to an embodiment has an advantage of providing a vehicle sharing service safely regardless of a network state.

The present disclosure according to an embodiment has an advantage of reinforcing user authentication for a shared vehicle since an authentication key is generated using the driver's biometric information.

In the present disclosure according to an embodiment, a new authentication key is generated using a history code, which is an authentication key generated immediately before, corresponding to a corresponding shared vehicle, so that user authentication for a shared vehicle can be further strengthened.

According to the present disclosure according to an exemplary embodiment, since a digital key capable of driving a vehicle is provided to a driver only when user authentication is completed, vehicle security may be further strengthened.

The effects that can be obtained in the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those of ordinary skill in the art from the following description. will be.

The accompanying drawings are provided to aid understanding of the present disclosure, and provide embodiments of the present disclosure together with a detailed description. However, the technical features of the present disclosure are not limited to a specific drawing, and features disclosed in each drawing may be combined with each other to constitute a new embodiment.

1 is a block diagram of a system for providing a shared vehicle service according to an embodiment.

2 is a diagram for describing a procedure for registering a shared vehicle user according to an embodiment.

3 shows a biometric information mapping table according to an embodiment.

4 is a diagram illustrating a biometric information mapping table according to another embodiment.

5 is a block diagram illustrating a procedure for generating an authentication key in an authentication key generation module mounted on a vehicle sharing server according to an embodiment.

6 is a flowchart illustrating a procedure for providing an authentication key from a vehicle sharing server to a driver terminal according to an embodiment.

7 is a flowchart illustrating a procedure for providing an authentication key from a vehicle sharing server to a driver terminal according to another embodiment.

8 is a diagram for describing a method of controlling a shared vehicle in a system for providing a shared vehicle service according to an exemplary embodiment.

9 is a flowchart illustrating a procedure for registering an authentication key in the shared vehicle 110 by the vehicle sharing server 120 according to an embodiment.

10 is a flowchart illustrating a procedure for registering an authentication key in the shared vehicle 110 by the vehicle sharing server 120 according to another exemplary embodiment.

11 is a block diagram illustrating a structure of a vehicle sharing server according to an embodiment.

12 is a block diagram illustrating a structure of a shared vehicle according to an embodiment.

Hereinafter, an apparatus and various methods to which the embodiments of the present disclosure are applied will be described in more detail with reference to the drawings.

The suffixes "module" and "unit" for components used in the following description are given or used interchangeably in consideration of only the ease of preparation of the specification, and do not have meanings or roles that are distinguished from each other by themselves.

The suffixes "module" and "unit" for components used in the following description may be configured to include at least one of a software component and a hardware component.

In the description of the embodiment, in the case of being described as being formed on "upper (upper) or lower (lower)" of each component, the upper (upper) or lower (lower) two components directly contact each other or It includes all of the one or more other components formed by being disposed between the two components.

In addition, when expressed as "upper (upper) or lower (lower)", the meaning of not only an upward direction but also a downward direction based on one component may be included.

1, the shared vehicle service providing system 10 includes a shared vehicle 110, a vehicle sharing server 120, a first driver terminal 130, a second driver terminal 140, a communication network 150, and positioning. It may include a satellite 160 and the like.

All of the components of the shared vehicle service providing system 10 are not necessarily essential components, and may be configured as a part of them or may be additionally included.

The shared vehicle 110 is a terminal 111 mounted inside the vehicle-hereinafter referred to as a "shared vehicle terminal", a business card -, an external antenna 112 for a vehicle mounted outside the vehicle, and various electronic control units (ECU: Electronic Control Unit). , Not shown) and a vehicle security module 113. Here, the vehicle external antenna 112 may be mounted after being configured to be integrated into one or separately installed antennas for receiving signals from the positioning satellite 160 as well as antennas used for transmitting and receiving signals with the wireless network 151 .

In an embodiment, the vehicle security module 113 may exchange information with the shared vehicle terminal 111 through intra-vehicle communication-for example, controller area network (CAN) communication.

As another example, the vehicle security module 113 may be integrally mounted on the shared vehicle terminal 111 and configured.

The shared vehicle terminal 111 may access the communication network 150 through the vehicle external antenna 112 or may receive a signal from the positioning satellite 160. Here, the communication network 150 may include a wireless network 151 and an Internet network 152.

The shared vehicle terminal 111 may perform short-range wireless communication with the first to

second driver terminals

130 and 140. As an example, short-range wireless communication may include Bluetooth communication, Wi-fi communication, Radio Frequency IDentification (RFID), Ultra Wideband Band (UWB) communication, Zigbee communication, etc., but limited thereto. It doesn't work.

The first to

second driver terminals

130 and 140 may access the vehicle sharing server 120 through the communication network 150 and receive various vehicle sharing services after account registration.

For example, a user may select a shared vehicle suitable for his schedule by running a vehicle sharing service app installed on his terminal, and reserve the use of the selected shared vehicle.

The first to

second driver terminals

130 and 140 according to the embodiment may collect biometric information of a corresponding driver and transmit it to the vehicle sharing server 120. The vehicle sharing server 120 may generate an authentication key for a corresponding driver based on biometric information. The vehicle sharing server 120 may transmit the generated authentication key to the driver's terminal.

As an example, the driver terminal may transmit a shared vehicle user registration request message including the vehicle type identifier of the shared vehicle selected by the driver to the vehicle sharing server 120.

The vehicle sharing server 120 may determine biometric information to be collected corresponding to the vehicle type identifier based on a predefined biometric information mapping table-see FIG. 3 to be described later.

Here, the vehicle sharing server 120 may collect a plurality of biometric information according to the vehicle type identifier. For example, the higher the vehicle class-that is, the higher the price of the high-end vehicle-the number of collected biometric information may increase.

The vehicle sharing server 120 according to the embodiment may further determine biometric information to be collected in response to a corresponding driver based on the specifications of the driver terminal as well as the vehicle type identifier.

For example, a fingerprint recognition function and an iris recognition function may not be mounted depending on the specifications of the terminal. In this case, the vehicle sharing server 120 may control such that biometric information other than fingerprint identification information and iris identification information is collected by the corresponding terminal.

The biometric information according to the embodiment may include fingerprint recognition information, iris recognition information, facial recognition information, voice recognition information, retina recognition information, palmistry information, etc., but is not limited thereto.

For example, the vehicle sharing server 120 may generate an authentication key based on not only biometric information but also handwriting information, handwritten signature information, gesture information, and the like according to the vehicle type identifier.

For example, referring to FIG. 1, it is assumed that the second driver reserves the use of the shared vehicle 110 while the first driver is using the shared vehicle 110.

When there is a plurality of biometric information of the second driver, the vehicle sharing server 120 may generate an individual biometric code corresponding to the individual biometric information of the second driver and then synthesize the plurality of individual biometric codes into one. Thereafter, the vehicle sharing server 120 corresponds to the second driver using the synthesized biometric code and an authentication key previously generated corresponding to the first driver-hereinafter, referred to as "first authentication key" for convenience of explanation. An authentication key to be described-hereinafter, for convenience of explanation, a business card referred to as a "second authentication key" may be generated.

In addition, the driver may extend the expiration date of the currently driving shared vehicle through the vehicle sharing service app when changing the schedule. If there is a reservation for the vehicle for which the extension of use is requested, the vehicle sharing server 120 may search for at least one replacement vehicle for the corresponding reservation and provide the search result to the corresponding reservation terminal. The reservationer may select a replacement vehicle and transmit the selection result to the vehicle sharing server 120.

The user of the shared vehicle 110 may set or change a place and time to return the shared vehicle through the vehicle sharing service app.

The reservation of the shared vehicle 110 may change/cancel the reservation details.

The vehicle sharing server 120 may register a new shared vehicle or cancel the registration of an existing registered shared vehicle based on a request of the vehicle owner or a user evaluation result for the corresponding shared vehicle. As an example, the vehicle sharing server 120 may determine to cancel registration for a shared vehicle in which the number of vehicle maintenance during a unit period exceeds a reference value, an average user rating is less than the reference value, or a serious traffic accident has occurred.

The vehicle sharing server 120 may monitor the state of the communication network 150 and control transmission of an authentication key to the shared vehicle 110 according to the monitoring result.

For example, it may be impossible for the vehicle sharing server 120 to register the generated authentication key to the shared vehicle 110 when the communication network 150 is not normal. In this case, the vehicle sharing server 120 may sequentially store the generated authentication key in a predetermined queue. Here, a queue is one of the basic data structures of a computer, and refers to a format in which data that is put first comes out first is stored in a FIFO (First In First Out) structure. That is, the authentication keys generated by the vehicle sharing server 120 may be stored and managed in a queue in the order in which the corresponding shared vehicle is reserved. If the shared vehicle is returned or the reservation is changed, the authentication key stored in the queue may be rearranged.

When the communication network 150 is normal, the vehicle sharing server 120 may sequentially index all of the authentication keys stored in the internal queue and transmit it to the shared vehicle 110. The shared vehicle 110 may sequentially sort the received authentication keys according to the index and store them in an internal queue.

When the authentication key switch is requested from the vehicle sharing server 120, the shared vehicle 110 deletes the currently activated authentication key, and then reads one authentication key from an internal queue and activates it.

Referring to FIG. 2, the first driver terminal 130 may log in to the vehicle sharing server 120 through the shared vehicle service app (S201).

When a shared vehicle is selected by the first driver, the first driver terminal 130 transmits a shared vehicle user registration request message including a vehicle type identifier indicating the type of vehicle selected by the first driver to the vehicle sharing server 120 It can be transmitted to (S202 to S203). Here, the first driver may search for and select a shared vehicle that fits his schedule through selection of a predetermined menu in the shared vehicle service app.

The vehicle sharing server 120 may determine the type of biometric information to be collected based on the vehicle type identifier (S204). Here, the type of biometric information to be collected is an identifier for identifying the type of biometric information to be collected corresponding to the corresponding driver.

The vehicle type identifier according to the embodiment may be classified based on at least the vehicle class, and a plurality of different vehicle type identifiers may be assigned to the same vehicle class. As an example, the vehicle class may be determined based on the price of the vehicle, functions and options mounted on the vehicle, the year, mileage, and accident history.

The shared vehicle user registration request message according to an embodiment may further include a vehicle type identifier as well as a terminal type identifier for identifying the type of the terminal that transmitted the request message.

In this case, the vehicle sharing server 120 may determine the type of biometric information to be collected based on the vehicle type identifier and the terminal type identifier.

The vehicle sharing server 120 may transmit a biometric information request message including the determined biometric information type information to be collected to the first driver terminal 130 (S205).

The first driver terminal 130 may collect the biometric information of the first driver by driving a corresponding biometric sensor according to the type of biometric information to be collected (S206).

The first driver terminal 130 may transmit a biometric information response message including the first driver biometric information to the vehicle sharing server 120 (S207).

The vehicle sharing server 120 may generate at least one biometric code by filtering the first driver biometric information (S208). Here, the first driver's biometric information may be composed of a plurality of different types of biometric information. In this case, a biometric code for each biometric information type—that is, a plurality of individual biometric codes— may be generated.

The vehicle sharing server 120 may check whether the generated individual biometric codes are plural (S209).

As a result of the verification, if there are multiple, the vehicle sharing server 120 may synthesize a plurality of individual biometric codes into one, generate a final biometric code corresponding to the first driver, and then store it in the internal memory (S210).

As a result of the verification in step 209, if not plural-that is, singular -, the vehicle sharing server 120 may determine the generated individual biometric code as the final biometric code corresponding to the first driver.

When the generation of the final biometric code is completed, the vehicle sharing server 120 may transmit a shared vehicle user registration completion message to the first driver terminal 130 (S211).

3 shows a biometric information mapping table according to an embodiment.

Referring to FIG. 3, the biometric information mapping table 300 may include a vehicle type identifier 310 field, a vehicle class 320 field, and a collection target biometric information 330 field.

Collection target biometric information 330 for each vehicle type identifier 310 may be defined differently.

In addition, in the biometric information mapping table 300, the vehicle class 320 corresponding to the vehicle type identifier 310 may be defined identically or differently.

As shown in FIG. 3, the number of biometric information to be collected may be defined differently according to the vehicle class 320.

The vehicle class 320 may be determined based on a vehicle price, performance and options, year, mileage, accident history, user evaluation, and the like.

The biometric information to be collected according to an embodiment may include fingerprint recognition information, iris recognition information, facial recognition information, voice recognition information, palmistry recognition information, etc., but is not limited thereto.

The present disclosure has the advantage of providing a differentiated security service for each vehicle class by collecting more biometric information and generating a biometric code as the vehicle class increases.

Referring to FIG. 4, the biometric information mapping table 400 may include a terminal type identifier 410 field, a terminal grade 420 field, and a collection target biometric information 430 field.

The biometric information 430 to be collected for each terminal type identifier 410 may be defined differently.

In addition, in the biometric information mapping table 400, the vehicle class 320 corresponding to the terminal type identifier 410 may be defined identically or differently.

As shown in FIG. 4, the number of biometric information to be collected according to the terminal class 420 may be defined differently.

The terminal class 420 may be determined based on the performance and options of the terminal-in particular, the type and number of biosensors provided.

The biometric information to be collected according to the embodiment may include fingerprint recognition information, iris recognition information, facial recognition information, voice recognition information, handwriting recognition information, palmistry recognition information, etc., but is not limited thereto.

The present disclosure has an advantage of providing a differentiated security service for each terminal level by collecting more biometric information and generating a biometric code as the terminal level increases.

5, the authentication key generation module 500 largely includes a biometric information input unit 510, a filter 520, a biometric code generation unit 530, a synthesis unit 540, and a key generation unit 550. Can be configured.

The biometric information input unit 510 includes a distribution unit 511 for classifying the biometric information of the N-th driver received from the terminal according to the biometric information type, and the first to first to decode the K pieces of biometric information classified by the distribution unit 511. It may be configured to include a Kth biometric information decoder 512.

The biometric information of the N-th driver may be plural, and each biometric information may be encoded in the terminal with a code capable of error correction and/or error detection, and then transmitted to the vehicle sharing server 120 through the communication network 150. have.

For example, codes capable of error correction and/or error detection include Block Codes, Reed-Solomon codes, Convolutional Codes, Turbo codes, and CRC ( Cyclic Redundancy Codes), and the like, but are not limited thereto.

The filter 520 extracts the recognition target data for each biometric information data decoded by the first to Kth biometric information decoder 512, and removes noise components included in the extracted recognition target data. It may be configured to include the unit 520.

For example, when the biometric information type is a fingerprint, the filter unit may extract only data within a certain radius from the center of the fingerprint and remove a noise component included in the extracted data.

The biometric code generation unit 530 may be configured to include first to K biometric code generation units that generate individual biometric codes corresponding to the biometric information type based on the output data of the first to Kth filter units 520. .

The first to K-th biometric code generation units may generate individual biometric codes corresponding to their own biometric information type by using different generation functions of the same order.

The synthesis unit 540 may synthesize at least one individual biometric code output by the biometric code generation unit 530 and output one synthesized biometric code.

As an example, the first to K individual biocodes output by the biometric code generation unit 530 are composed of bit strings of the same length, and the combining unit 540 is an exclusive OR ( Exclusive-OR) can be applied to generate and output one synthetic biometric code.

The key generator 550 may generate an Nth driver authentication key based on the N-1th driver authentication key and the synthesized biometric code.

For example, the key generator 550 may generate the Nth driver authentication key through an exclusive-OR of the N-1th driver authentication key and the synthesized biometric code.

Referring to FIG. 6, the first driver terminal 130 may transmit an authentication key request message including biometric information of the first driver to the vehicle sharing server 120 (S601 ).

The vehicle sharing server 120 may generate a first biometric code based on the biometric information of the first driver (S602).

The vehicle sharing server 120 may generate a first authentication key corresponding to the first driver based on the history code and the first biometric code (S603). If the first driver is the first user to use the shared vehicle 110, a preset initial value may be used as the history code.

The vehicle sharing server 120 may transmit an authentication key response message including the first authentication key to the first driver terminal 130 (S604).

The first driver terminal 130 may perform user authentication for the vehicle security system or vehicle security module and the first driver by using the first authentication key (S605). When user authentication is completed, the first driver can use the shared vehicle.

The vehicle sharing server 120 may set a reservation for the second driver terminal 140 and the shared vehicle 110 being used by the first driver (S606). In this case, the second driver terminal 140 may transmit the biometric information of the second driver to the vehicle sharing server 120.

The vehicle sharing server 120 may generate a second biometric code based on the biometric information of the second driver (S607).

The vehicle sharing server 120 may receive a shared vehicle return request message including the location information of the first driver terminal from the first driver terminal 130 (S608).

The vehicle sharing server 120 may obtain the location information of the second driver terminal from the terminal 140 of the second driver who is the next use reservation person for the shared vehicle 110 (S609).

The vehicle sharing server 120 may determine whether the first driver and the second driver are in a transferable area based on the acquired location information of the first to second driver terminals 130 and 140 (S610). For example, if the first driver and the second driver are within a certain radius-for example, 15 m -, the vehicle sharing server 120 may determine whether the first driver and the second driver are in a transferable area.

As a result of the determination in step 610, if the vehicle sharing server 120 is in a transferable area, the vehicle sharing server 120 may generate a second authentication key for the second driver based on the history code and the second biometric code (S612). Here, as the history code, the first authentication key may be used.

The vehicle sharing server 120 may transmit a shared vehicle return acceptance message to the first driver terminal 130 (S613).

The first driver terminal 130 may delete the first authentication key when the shared vehicle return acceptance message is received (S614).

The vehicle sharing server 120 may transmit a shared vehicle use start message including the second authentication key to the second driver terminal 140 (S615).

The second driver terminal 140 may perform user authentication for the vehicle security system or the vehicle security module and the second driver through the second authentication key (S616).

As a result of the determination in step 610, if the vehicle is not in a transferable area, the vehicle sharing server 120 may transmit a refusal message to return the shared vehicle to the first driver terminal 130 (S611).

According to the exemplary embodiment of FIG. 6, since the present disclosure generates an authentication key using at least one driver's biometric information, user authentication for a shared vehicle can be further strengthened.

Referring to FIG. 7, the first driver terminal 130 may transmit an authentication key request message including biometric information of the first driver to the vehicle sharing server 120 (S701 ).

The vehicle sharing server 120 may generate a first biometric code based on the biometric information of the first driver (S702).

The vehicle sharing server 120 may generate a first authentication key corresponding to the first driver based on the history code and the first biometric code (S703). If the first driver is the first user to use the shared vehicle 110, a preset initial value may be used as the history code.

The vehicle sharing server 120 may transmit an authentication key response message including the first authentication key to the first driver terminal 130 (S704).

The first driver terminal 130 may perform user authentication for the vehicle security system or the vehicle security module and the first driver by using the first authentication key (S705). When user authentication is completed, the first driver can use the shared vehicle.

The vehicle sharing server 120 may set a reservation for the second driver terminal 140 and the shared vehicle 110 being used by the first driver (S706).

The second driver terminal 140 may transmit an authentication key request message including the biometric information of the second driver to the vehicle sharing server 120 (S707).

The vehicle sharing server 120 may generate a second biometric code based on the biometric information of the second driver (S708).

The vehicle sharing server 120 may generate a second authentication key for the second driver based on the history code and the second biometric code (S709). Here, as the history code, the first authentication key may be used.

The vehicle sharing server 120 may transmit an authentication key response message including the second authentication key to the second driver terminal 140 (S710). In this case, the second driver terminal 140 may store the received second authentication key in the internal memory, and may not start the user authentication procedure.

The vehicle sharing server 120 may receive a shared vehicle return request message including the location information of the first driver terminal from the first driver terminal 130 (S711).

The vehicle sharing server 120 may acquire the location information of the second driver terminal 140 from the terminal 140 of the second driver who is the next use reservation person for the shared vehicle 110 (S712).

The vehicle sharing server 120 may determine whether the first driver and the second driver are in a transferable area based on the acquired location information of the first to second driver terminals 130 and 140 (S713). For example, if the first driver and the second driver are within a certain radius-for example, 15 m -, the vehicle sharing server 120 may determine whether the first driver and the second driver are in a transferable area.

As a result of the determination in step 713, if the vehicle is in a transferable area, the vehicle sharing server 120 may transmit a shared vehicle return acceptance message to the first driver terminal 130 (S715).

When the shared vehicle return acceptance message is received, the first driver terminal 130 may delete the first authentication key (S716).

The vehicle sharing server 120 may transmit an authentication initiation request message to the second driver terminal 140 (S717).

When the authentication initiation request message is received, the second driver terminal 140 may perform user authentication for the vehicle security system or the vehicle security module and the second driver using the second authentication key stored in the internal memory (S718). .

As a result of the determination in step 713, if the vehicle is not in a transferable area, the vehicle sharing server 120 may transmit a refusal message to return the shared vehicle to the first driver terminal 130 (S714). As an example, the shared vehicle return refusal message is “The next shared vehicle user will not be identified near you. Please check the return location again.”

According to the embodiment of FIG. 7 described above, the present disclosure generates a new authentication key using a history code that is an authentication key generated immediately in response to the corresponding shared vehicle, so that user authentication for the corresponding shared vehicle can be further strengthened. There is this.

Referring to FIG. 8, the first driver terminal 130 may transmit an authentication key request message including biometric information of the first driver to the vehicle sharing server 120 through the communication network 150 (S801 ).

The vehicle sharing server 120 may generate a first authentication key for the first driver based on the biometric information of the first driver (S802).

The vehicle sharing server 120 may transmit an authentication key response message including the first authentication key to the first driver terminal 130 through the communication network 150 (S803).

In addition, the vehicle sharing server 120 may transmit an authentication key registration request message instructing to activate the first authentication key to the secured shared vehicle 110 through the communication network 150 (S804 to S805). As an example, the vehicle sharing server 120 may register an authentication key generated in the shared vehicle 110 in connection with the vehicle security module 113.

In this case, the shared vehicle 110 may activate the first authentication key (S806).

The first driver terminal 130 may encrypt the first authentication key according to a predetermined encryption algorithm (S807).

The first driver terminal 130 may transmit an authentication request message including the encrypted first authentication key to the shared vehicle 110 through short-range wireless communication (S808).

The shared vehicle 110 may decrypt the encrypted first authentication key (S809) and determine whether the decrypted authentication key is valid (S810). When the decrypted authentication key is the same as the currently activated authentication key, the shared vehicle 110 may determine that the corresponding authentication key is valid.

As a result of the determination, if the authentication key is valid, the shared vehicle 110 may release the security setting after generating the digital key (S812).

The shared vehicle 110 may transmit an authentication completion message including a digital key to the first driver terminal 130 through short-range wireless communication (S813).

The first driver terminal 130 may control the vehicle using a digital key (S814).

In step 710, if the authentication key is not valid, the shared vehicle 110 accesses an unauthorized user using an alarm means provided in the vehicle-including, for example, a horn, lighting, headlight, etc. It is possible to output a predetermined warning alarm for warning (S815).

The shared vehicle 110 may transmit location information of the shared vehicle 110 and a black box image captured when the warning alarm is output to the vehicle sharing server 120 (S816).

The vehicle sharing server 120 may transmit a theft warning message including current location information of the vehicle and a black box photographed image to a terminal of the owner of the shared vehicle 110 registered in advance (S817).

According to the embodiment of FIG. 8, the present disclosure provides the driver with a digital key capable of driving a vehicle only when user authentication is completed through an authentication key generated based on biometric information, thereby enhancing vehicle security. have.

Referring to FIG. 9, when the vehicle sharing server 120 generates a first authentication key corresponding to a first subscriber, the vehicle sharing server 120 may transmit an authentication key registration request message including the first authentication key to the shared vehicle 110 ( S901 to S902). In this case, the authentication key registration related message may be processed by the vehicle sharing server 120 and the vehicle security module 113 of the shared vehicle 110.

If the first subscriber is a customer who uses the shared vehicle 110 for the first time (or the first customer on the day, the first customer in the current month, or the first customer in the year), the vehicle sharing server 120 is the vehicle security module 113 It can be instructed to activate the first authentication key.

After activating the first authentication key according to the authentication key registration request message, the shared vehicle 110 may transmit an authentication key registration completion message to the vehicle sharing server 120 (S903 to S904).

When the vehicle sharing server 120 generates a second authentication key corresponding to the second subscriber, the vehicle sharing server 120 may transmit an authentication key registration request message including the second authentication key to the shared vehicle 110 (S905 to S906).

After storing the second authentication key in the queue, the shared vehicle 110 may transmit an authentication key registration completion message to the vehicle sharing server 120 (S907 to S908).

When the vehicle sharing server 120 generates a third authentication key corresponding to the third subscriber, the vehicle sharing server 120 may transmit an authentication key registration request message including the third authentication key to the shared vehicle 110 (S909 to S910).

After storing the third authentication key in the queue, the shared vehicle 110 may transmit an authentication key registration completion message to the vehicle sharing server 120 (S911 to S912).

When the vehicle sharing server 120 is requested to return the shared vehicle 110 from the terminal of the first subscriber, the vehicle sharing server 120 may transmit an authentication key call request message to the shared vehicle 110 (S913 to S914).

The shared vehicle 110 may delete the second authentication key from the queue after converting the activated authentication key to the second authentication key (S915).

Subsequently, the shared vehicle 110 may transmit an authentication key conversion completion message to the vehicle sharing server 120 (S916).

According to the embodiment of FIG. 9, the present disclosure immediately transmits the generated authentication key to the shared vehicle 110 when the network state is normal, and the shared vehicle 110 stores the authentication key in the internal queue in the order of creation. And management, so that even if a network error occurs, user authentication can be safely performed.

Referring to FIG. 10, when the vehicle sharing server 120 generates a first authentication key corresponding to a first subscriber in a state in which the network is normal, the vehicle sharing an authentication key registration request message including the first authentication key 110 ) Can be transmitted (S1001 to S1003). In this case, the authentication key registration related message may be processed by the vehicle sharing server 120 and the vehicle security module 113 of the shared vehicle 110.

After activating the first authentication key according to the authentication key registration request message, the shared vehicle 110 may transmit an authentication key registration completion message to the vehicle sharing server 120 (S1004 to S1005).

When the vehicle sharing server 120 generates a second authentication key corresponding to the second subscriber, the vehicle sharing server 120 may transmit an authentication key registration request message including the second authentication key to the shared vehicle 110 (S1006 to S1007).

If the authentication key registration completion message is not received within a predetermined time after transmission of the authentication key registration request message, the vehicle sharing server 120 may transition the network state to an error state (S1008).

When the vehicle sharing server 120 transitions to a network error state, the vehicle sharing server 120 may store the second authentication key in the server queue (S1009).

The vehicle sharing server 120 may transmit a network status check message-for example, a Keep Alive Message-to the shared vehicle 110 at regular intervals to monitor the network status.

As a result of monitoring, when the network is not restored, the vehicle sharing server 120 may store an authentication key newly generated in response to the shared vehicle 110 in the server queue (S1010).

As a result of monitoring, when a network error is recovered, the vehicle sharing server 120 may transition the network state to a normal state.

When the network transitions to a normal state, the vehicle sharing server 120 may transmit all authentication keys stored in the server queue corresponding to the shared vehicle 110 to the shared vehicle 110 through an authentication key registration request message (S1013). ).

The shared vehicle 110 may store the received authentication keys in the vehicle queue in the order in which they were generated, and then transmit an authentication key registration completion message to the vehicle sharing server 120 (S1014 to S1015).

The vehicle sharing server 120 may delete all authentication keys stored in the server queue corresponding to the shared vehicle 110 (S1016).

The present disclosure through the embodiment of FIG. 10 has an advantage of providing a stable vehicle sharing service by safely transmitting an authentication key to the shared vehicle 110 even if a network error occurs.

Referring to FIG. 11, the vehicle sharing server 120 includes a communication module 1101, a location information collection module 1102, a biometric information collection module 1103, an authentication key generation module 1104, a reservation setting module 1105, and It can be configured to include a storage module 1106 and a controller 1109.

The communication module 1101 may process signals transmitted and received through the communication network 150.

The location information collection module 1102 may acquire location information of a shared vehicle and location information of a driver terminal periodically or when a specific event occurs.

The biometric information collection module 1003 may collect biometric information of a corresponding driver from a driver terminal. Here, the driver's biometric information may include a plurality of types.

The authentication key generation module 1004 may generate a unique authentication key for a corresponding driver corresponding to a corresponding shared vehicle based on the biometric information collected from the driver terminal.

The detailed structure and operation of the authentication key generation module 1004 will be replaced with the description of the above drawings.

The reservation setting module 1105 may set a usage reservation for a corresponding shared vehicle according to a request from a driver terminal, and perform a function of changing/cancelling the set reservation.

The reservation setting module 1005 may configure a predetermined user interface screen for setting/changing/canceling a shared vehicle reservation.

The reservation setting module 1005 may update the reservation details for the shared vehicle based on a result of processing according to a request for delayed return of the shared vehicle driver and an early return request.

The storage module 1106 may maintain a biometric information mapping table 1107 and a server queue 1108.

The biometric information mapping table 1107 is replaced with the description of FIGS. 3 to 4 described above.

The server queue 1108 may be generated and managed in units of registered shared vehicles.

The management method for the server queue 1108 is replaced with the description of FIGS. 9 to 10 described above.

The specific operation of the controller 1050 is replaced with a description of the operation of the vehicle sharing server 120 on the shared vehicle service providing system of FIGS. 1 to 10 described above.

Referring to FIG. 12, the shared vehicle 120 includes a wireless communication module 1201, a vehicle security module 1201, an alarm module 1203, an internal communication network 1204, a storage unit 1205, and a positioning module 1207. , A black box 1208 and a vehicle controller 1209 may be included.

The wireless communication module 1201 may process signals transmitted and received through the communication network 150.

In addition, the wireless communication module 1201 may exchange information with a terminal through short-range wireless communication.

As an example, short-range wireless communication may include Bluetooth communication, Wi-fi communication, Radio Frequency IDentification (RFID), Ultra Wideband Band (UWB) communication, Zigbee communication, etc., but limited thereto. It doesn't work.

The vehicle security module 1202 may authenticate a user based on an authentication key generated by the vehicle sharing server 120.

In addition, the vehicle security module 1202 may manage an authentication key stored in the vehicle queue 1206.

In addition, the vehicle security module 1202 may generate a digital key according to a user authentication result and transmit the generated digital key to a terminal of a corresponding user.

In addition, the vehicle security module 1202 may control the alarm module 1203 to output a warning alarm according to the user authentication result.

When the warning alarm is output, the vehicle security module 1202 may obtain information on the current location of the vehicle from the positioning module 1207 and obtain an image photographed by the black box 1208. The vehicle security module 1202 may transmit the acquired vehicle location information and image information to the vehicle sharing server 120.

When user authentication is completed, the vehicle security module 1202 may unlock the vehicle controller 1209 and control the user to drive the vehicle using a digital key.

Detailed operations of the vehicle security module 1202 are replaced with the description of the above-described drawings.

It is obvious to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from essential features of the present disclosure.

Therefore, the detailed description above should not be construed as restrictive in all respects and should be considered as illustrative. The scope of the present disclosure should be determined by reasonable interpretation of the appended claims, and all changes within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

Claims

In the shared vehicle authentication method in a vehicle sharing server linked to a driver terminal and a shared vehicle through a communication network,

Receiving an authentication key request message including first biometric information from a first driver terminal;

Generating a first biometric code using the first biometric information;

Generating a first authentication key based on the first biometric code and a first history code;

Transmitting an authentication key response message including the first authentication key to the first driver terminal;

Receiving an authentication key request message including second biometric information from a second driver terminal;

Generating a second biometric code using the second biometric information;

Generating a second authentication key based on the second biometric code and a second history code; And

Transmitting an authentication key response message including the second authentication key to the second driver terminal

Including,

Receiving a shared vehicle return request message including location information of the first driver terminal from the first driver terminal;

Acquiring location information of the second driver terminal from the second driver terminal;

Determining whether the first driver and the second driver are in a transferable area based on location information of the first to second driver terminals; And

As a result of the determination, if it is in an area where the takeover is possible, transmitting an authentication start request message to the second driver terminal

Including more,

The second history code is the first authentication key,

The second driver terminal, when the authentication initiation request message is received, performs user authentication for the shared vehicle by using the second authentication key.
The method of claim 1,

Receiving a shared vehicle user registration request message including a vehicle type identifier corresponding to the shared vehicle from the first driver terminal;

Determining a type of biometric information to be collected based on the vehicle type identifier; And

Transmitting a biometric information request message including the determined biometric information type to be collected to the first driver terminal

And wherein the first biometric information is biometric information collected according to the determined type of biometric information to be collected.
The method of claim 2,

The shared vehicle authentication method, characterized in that the determined collection target biometric information types are plural according to the vehicle type identifier.
The method of claim 3,

The biometric information type to be collected includes at least one of a fingerprint recognition information type, an iris recognition information type, a facial recognition information type, a palmprint recognition information type, and a voice recognition information type.
The method of claim 4,

Generating the first authentication key,

Classifying the first biometric information into first to K individual biometric information according to the type of biometric information to be collected;

Filtering noise included in the first to Kth individual biometric information and generating first to K individual biometric codes using a corresponding generation function;

Synthesizing the first to K individual biometric codes to generate a synthetic biometric code; And

Generating the first authentication key by exclusively ORing the synthesized biometric code and the first history code in bit units

Shared vehicle authentication method comprising a.
The method of claim 1,

As a result of the determination, if it is in a transferable area, transmitting a shared vehicle return acceptance message to the first driver terminal, and when the first driver terminal receives the shared vehicle return acceptance message, the first authentication key Shared vehicle authentication method, characterized in that to delete.
The method of claim 1,

Including the step of sequentially registering a corresponding authentication key to the shared vehicle according to the generation sequence, and when the authentication key registration fails due to a network state transitioning to an error state, the registration failed authentication key is stored in a server queue, When the state transitions to a normal state, all authentication keys stored in the server queue are registered in the shared vehicle.
The method of claim 7,

The shared vehicle server, when the network state transitions to an error state, transmits a KEEP ALIVE message at regular intervals to check the network state.
The method of claim 1,

The first to second biometric information is encoded and received in a code capable of error correction and/or error detection.
In a vehicle sharing server that is linked with a driver terminal and a shared vehicle through a communication network,

A controller for controlling input/output and overall operation of the vehicle sharing server;

A communication module for exchanging information with the driver terminal through the communication network with the shared vehicle;

A biometric information collection module for collecting biometric information from the driver terminal;

An authentication key generation module that generates an authentication key based on the biometric information; And

Reservation setting module for setting a reservation for use of the driver terminal and the shared vehicle

Including,

The authentication key generation module

Means for generating a first biometric code using the first biometric information received from the first driver terminal;

Means for generating a first authentication key based on the first biometric code and a first history code;

Means for generating a second biometric code using the second biometric information received from the second driver terminal;

Means for generating a second authentication key based on the second biometric code and a second history code

Including, the second history code is the first authentication key,

The controller,

Upon receiving the shared vehicle return request message including the location information of the first driver terminal from the first driver terminal, the location information of the second driver terminal is obtained from the second driver terminal, and the first to second drivers Based on the location information of the terminal, it is determined whether the first driver and the second driver are in a transferable area, and as a result of the determination, if they are in a transferable area, an authentication initiation request message is transmitted to the second driver terminal. ,

The second driver terminal, when the authentication initiation request message is received, performs user authentication for the shared vehicle by using the second authentication key.
The method of claim 10,

The controller is

When receiving a shared vehicle user registration request message including a vehicle type identifier corresponding to the shared vehicle from the first driver terminal, a collection target biometric information type is determined based on the vehicle type identifier, and the determined collection target biometric information A vehicle sharing server, wherein a biometric information request message including a type is transmitted to the first driver terminal, wherein the first biometric information is biometric information collected according to the determined biometric information type to be collected.
The method of claim 11,

Vehicle sharing server, characterized in that the determined collection target biometric information type is plural according to the vehicle type identifier.
The method of claim 12,

The collected biometric information type is a vehicle sharing server including at least one of a fingerprint recognition information type, an iris recognition information type, a facial recognition information type, a palm print recognition information type, and a voice recognition information type.
The method of claim 13,

The authentication key generation module,

A biometric information input unit for classifying the first biometric information into first to K individual biometric information according to the type of biometric information to be collected and inputting it to a decoder;

A biometric code generator configured to generate first to K individual biometric codes by using a corresponding generation function after filtering noise included in the first to Kth individual biometric information;

A synthesis unit for synthesizing the first to K individual biocodes to generate a synthetic biocode; And

A key generation unit generating the first authentication key by exclusively ORing the synthesized biometric code and the first history code by bit unit

Vehicle sharing server comprising a.
The method of claim 10,

The controller,

As a result of the determination, if it is in a transferable area, transmits a shared vehicle return acceptance message to the first driver terminal,

The vehicle sharing server, wherein the first driver terminal deletes the first authentication key upon receiving the shared vehicle return acceptance message.
The method of claim 10,

The controller,

Performs a procedure of sequentially registering a corresponding authentication key to the shared vehicle according to the generation sequence, and when the authentication key registration fails because the network state transitions to an error state, the registration failed authentication key is stored in the server queue, and the network Vehicle sharing server, characterized in that when the state transitions to the normal state, controlling all the authentication keys stored in the server queue to be registered in the shared vehicle.
The method of claim 16,

The controller,

When the network state transitions to an error state, a vehicle sharing server that checks the network state by transmitting a KEEP ALIVE message at regular intervals.
The method of claim 10,

The vehicle sharing server, characterized in that the first to second biometric information is encoded and received as a code capable of error correction and/or error detection.