JP6916101B2 - Sharing system - Google Patents

Description

The present invention relates to a sharing system that allows a common object to be used by a plurality of people.

Conventionally, as a sharing system in which one common object is used by a plurality of people, a car sharing system in which one shared vehicle is used by a plurality of people is well known (see Patent Documents 1 and 2 and the like). In this type of car sharing system, for example, the use of car sharing is registered in advance, the vehicle is reserved on a mobile terminal (high-performance mobile phone, etc.), and then the use of the vehicle is permitted within the reserved time. ..

Japanese Unexamined Patent Publication No. 2016-115077 Japanese Unexamined Patent Publication No. 2016-71834

In the conventional car sharing system, it is assumed that the vehicle is operated by only one mobile terminal that has been licensed to use the vehicle. Therefore, even if an attempt is made to lend the vehicle being shared to another user, there is a problem that it cannot be dealt with.

An object of the present invention is to provide a sharing system that enables one common object to be operated by a plurality of mobile terminals.

The sharing system that solves the above problems wirelessly communicates between a mobile terminal that can operate as a key of a common object by registering unique key information and an authentication device mounted on the common object. When the key information is authenticated and the operation of the operation target controlled through the electronic key system of the common object is performed on the mobile terminal, the operation target is operated by the authentication device in the authentication completed state. It is configured to include a plurality of usage permission units that enable the common object to be operated by the plurality of mobile terminals owned by each person.

According to this configuration, when operating a common object operation target with a mobile terminal, it is possible to operate the operation target not only with one mobile terminal but also with another mobile terminal. Therefore, one common object can be operated by a plurality of mobile terminals.

In the sharing system, the authentication device includes a plurality of authentication device-specific keys used for authenticating the key information in a memory, and the plurality of use permission units use any of the plurality of authentication device-specific keys to obtain the key information. It is preferable that the common object can be operated over a plurality of the portable terminals by confirming whether or not the common object can be correctly decoded and enabling the common object to be operated by the portable terminal that can be decoded. According to this configuration, a common object can be operated by a plurality of mobile terminals by a simple method of registering a plurality of authentication device unique keys in the memory of the authentication device.

In the sharing system, when the operation target is operated by the mobile terminal, the authentication device preferably identifies the mobile terminal from a terminal ID unique to each mobile terminal. According to this configuration, when the mobile terminal communicates with the authentication device to operate the operation target, the mobile terminal is identified by the terminal ID possessed by the mobile terminal, and the operation target is operated in a manner corresponding to each mobile terminal. Is possible.

In the sharing system, the mobile terminal is given a permission function for which operation is permitted for the common object, and the authentication device is used for each mobile terminal when the operation target is operated by the mobile terminal. It is preferable that the permission function is recognized from the terminal ID uniquely possessed by the user, and the operation target is operated according to the permission function. According to this configuration, it is possible to operate the operation target in a manner corresponding to the permission function set in each mobile terminal.

In the sharing system, when the authentication device includes time information used to set a date and time when the operation target can be operated by the authentication device, the mobile terminal is used only for a period determined from the time information. It is preferable that the operation of the operation target is permitted, and whether or not the time information is included in the key information is selected according to the permission function set in the mobile terminal. According to this configuration, when operating an operation target without the concept of time on the mobile terminal, it is possible to continue the state in which the operation target can be operated on the mobile terminal without a time limit.

According to the present invention, one common object can be operated by a plurality of mobile terminals.

The block diagram of the sharing system of one Embodiment. Communication sequence diagram of key information authentication. An image diagram of the work of registering key information in the second mobile terminal. Processing diagram of key information generation when time information is not included. Relationship diagram of parameters set for each mobile terminal. Communication sequence diagram when operating a band terminal to operate an in-vehicle device. A block diagram of another sharing system.

Hereinafter, an embodiment of the sharing system will be described with reference to FIGS. 1 to 6.
As shown in FIG. 1, the vehicle 1 includes an electronic key system 4 that wirelessly performs ID verification with the electronic key 2 to execute or permit the operation of the in-vehicle device 3. The electronic key system 4 is a key operation-free system that executes ID verification (smart verification) by narrow-range radio in the wake of communication from the vehicle 1. In the key operation free system, ID verification is automatically performed without directly operating the electronic key 2. The in-vehicle device 3 includes, for example, a door lock device 5, an engine 6, an in-vehicle communication device 7, and the like. The in-vehicle communication device 7 is preferably a communication device capable of communicating by, for example, Bluetooth (Bluetooth: registered trademark).

The vehicle 1 includes a collation ECU (Electronic Control Unit) 9 for ID collation, a body ECU 10 for managing the power supply of vehicle-mounted electrical components, and an engine ECU 11 for controlling the engine 6. These ECUs are electrically connected via a communication line 12 in the vehicle. The communication line 12 is, for example, CAN (Controller Area Network) or LIN (Local Interconnect Network). In each memory (not shown) of the collation ECU 9 and the electronic key 2, an electronic key ID of the electronic key 2 registered in the vehicle 1 and a key unique key used for ID verification authentication are registered. The body ECU 10 controls a door lock device 5 that switches the lock / unlock of the vehicle door 13.

The vehicle 1 includes a radio wave transmitter 16 that transmits radio waves in the vehicle 1 and a radio wave receiver 17 that receives radio waves in the vehicle 1. The radio wave transmitter 16 includes, for example, an outdoor use for transmitting radio waves outdoors and an indoor use for transmitting radio waves indoors. The radio wave transmitter 16 transmits radio waves in the LF (Low Frequency) band. The radio wave receiver 17 receives radio waves in the UHF (Ultra High Frequency) band. The electronic key system 4 communicates with the electronic key 2 by bidirectional communication of LF-UHF.

When the wake signal for activating the electronic key 2 is LF transmitted from the radio wave transmitter 16, when the electronic key 2 enters the communication area of the wake signal and receives it, the electronic key 2 is activated from the standby state and ID collation with the collation ECU 9 ( Perform smart collation). Smart verification includes, for example, electronic key ID verification for confirming the correctness of an electronic key ID, challenge-response authentication using a key-specific key (encryption key), and the like. When the collation ECU 9 confirms that the outdoor electronic key 2 and the ID collation (outdoor smart collation) are established, the collation ECU 9 permits or executes the locking / unlocking of the vehicle door 13 by the body ECU 10.

When the collation ECU 9 confirms that the ID collation (indoor smart collation) is established with the electronic key 2 in the room, the collation ECU 9 permits the power supply transition operation by the engine switch 18. As a result, for example, when the engine switch 18 is operated with the brake pedal depressed, the engine 6 is started.

The vehicle 1 of this example as a shared object 24 shared by a plurality of people includes a sharing system 21 that realizes sharing among a plurality of people. The sharing system 21 of this example is equipped with an authentication device 23 having an encryption key (authentication device unique key) capable of registering the encrypted key information Dk from the server 20 to the mobile terminal 22 and decrypting the key information Dk. The key information Dk is transmitted from the mobile terminal 22 to the vehicle 1, and the authentication device 23 authenticates the key information Dk. If the authentication is established, the operation of the operation target 25 provided in the vehicle 1 is permitted.

The mobile terminal 22 is preferably, for example, a high-performance mobile phone. The key information Dk is preferably a one-time key (one-time password) that is permitted to be used only once, for example. The operation target 25 is, for example, a door lock device 5 (vehicle door 13), a vehicle power supply (engine 6), an in-vehicle communication device 7, and the like. The in-vehicle communication device 7 can communicate with a wearable terminal or the like worn by the driver through, for example, Bluetooth communication.

The authentication device 23 controls the operation of the sharing system 21 and is independent of the hardware configuration of the electronic key system 4 of the vehicle 1. The authentication device 23 is wiredly connected to an element of the electronic key system 4 through a wiring 31 (for example, a jiga wire), and power is supplied from the battery + B of the vehicle 1. The authentication device 23 is wiredly connected to various ECUs such as the collation ECU 9, or is wiredly connected to the communication line 12 in the vehicle.

The mobile terminal 22 includes a terminal control unit 26 that controls the operation of the mobile terminal 22, a network communication module 27 that performs network communication in the mobile terminal 22, and a short-range wireless communication module 28 that performs short-range wireless communication in the mobile terminal 22. , A memory 29 capable of rewriting data is provided. The mobile terminal 22 acquires the key information Dk from the server 20 by the network communication module 27, and writes and saves the key information Dk in the memory 29. The short-range wireless communication is preferably Bluetooth, for example.

The mobile terminal 22 includes a user interface application 30 that manages the operation of the sharing system 21 in the mobile terminal 22. The user interface application 30 is provided in the terminal control unit 26, for example, by being downloaded from the server 20. In the memory 29 of the mobile terminal 22, a user authentication key required for communication when operating the vehicle 1 on the mobile terminal 22 is registered. The user authentication key is, for example, composed of a random number whose value changes each time it is generated, and may be registered in the sharing system 21 in advance, or may be generated and registered when the vehicle is used.

The authentication device 23 sets the date and time in the authentication device 23, the controller 33 that controls the operation of the authentication device 23, the short-range wireless module 35 that performs short-range wireless communication in the authentication device 23, the memory 36 that can rewrite data, and the authentication device 23. A timer unit 37 for management is provided. In the memory 36, an authentication device ID, which is a unique ID of each authentication device 23, and an authentication device unique key used for encrypted communication with the mobile terminal 22 are written and stored. The timer unit 37 includes, for example, a soft timer. The authentication device 23 has a one-to-one correspondence with the vehicle 1 by associating the authentication device ID with the vehicle ID (vehicle body number).

The authentication device unique key is a type of key used for authenticating the key information Dk of the mobile terminal 22. A plurality of authentication device unique keys are written and stored in the memory 36 of the authentication device 23. This is because one authentication device 23 can be operated by a plurality of mobile terminals 22 (in this example, the first mobile terminal 22a and the second mobile terminal 22b). This is not limited to the scene where the shared vehicle 1 is driven only by one first mobile terminal 22a. For example, while using the shared vehicle 1, the user returns to the shared vehicle 1 with another second mobile terminal 22b. The biometric information (pulse information) acquired by the wristwatch-type second mobile terminal 22b (so-called wearable terminal) is sent to the shared vehicle 1 by short-range radio while the vehicle is being loaded or the shared vehicle 1 is used, and the shared vehicle 1 is automatically performed. This is to realize the function of stopping. In the case of this example, for example, the authentication device unique key A, the authentication device unique key B, ... Are written and saved in the memory 36.

The authentication device 23 includes an operation control unit 38 that operates the in-vehicle device 3 through communication with the mobile terminal 22. The operation control unit 38 is provided on the controller 33. The operation control unit 38 controls the operation of various devices of the vehicle 1 when the operation is switched to the “authentication completed state” through communication with the mobile terminal 22.

The sharing system 21 includes a plurality of usage permission units 40 that enable the common object 24 to be operated by a plurality of mobile terminals 22 owned by each person. The multiple use permission unit 40 is provided in the controller 33 of the authentication device 23. The multiple use permission unit 40 of this example confirms which of the plurality of authentication device unique keys can correctly decrypt the key information Dk, and enables the common object 24 to be operated by the decrypted mobile terminal 22. By doing so, the common object 24 can be operated over a plurality of mobile terminals 22.

Next, the operation and effect of the sharing system 21 of the present embodiment will be described with reference to FIGS. 2 to 6. First, the procedure for reserving and registering the mobile terminal 22 as a vehicle key will be described with reference to FIG. Here, for example, an example in which the main user registers the mobile terminal 22 (first mobile terminal 22a) in the authentication device 23 will be given.

In step 101, the mobile terminal 22 (user interface application 30) and the server 20 execute user authentication for confirming the user who reserves the vehicle 1. In the user authentication of this example, the user ID and password are authenticated, and the usage reservation procedure for registering the vehicle 1 to be reserved is performed. In the usage reservation procedure, for example, the vehicle 1 to be used, the date and time, and the like are input. The user ID and password are input to the mobile terminal 22 and transmitted to the server 20 via network communication. When the user ID and password are input from the mobile terminal 22, the server 20 authenticates them, continues the process if the authentication is established, and forcibly terminates the process if the authentication is not established.

If the user authentication is established in step 102, the server 20 generates the key information Dk. The server 20 generates the key information Dk by using, for example, the authentication device unique key of the authentication device 23 mounted on the vehicle 1 used by the user. In the case of this example, the server 20 uses, for example, "reservation date and time", "terminal ID", "user authentication key", "time information", "permission function", etc. in plain text, and a predetermined encryption key (in this example, an authentication device). A unique key) is used as an encryption key, and a cipher statement is generated by passing these through an encryption formula (encryption algorithm), and this ciphertext is used as key information Dk.

Here, since the example in which the main user performs the registration work of the mobile terminal 22 is given, for example, "A" is used as the authentication device unique key. The terminal ID is a unique ID of the mobile terminal 22. The user authentication key is, for example, a key in which a different value is generated each time it is generated, and is a kind of key used in encrypted communication between the mobile terminal 22 and the authentication device 23. The time information is information used to correct the time of the timer unit 37 of the authentication device 23.

The permission function is a function requested by the user to be used during the usage procedure, that is, a function whose operation is permitted by the server 20 among various operations on the vehicle 1. When the main user performs an operation of registering his / her own mobile terminal 22 as a vehicle key, it is preferable that a "smart operation function" is set as a permission function. The smart operation refers to an operation of operating the vehicle 1 by the above-mentioned key operation free system.

In step 103, the server 20 transmits the generated key information Dk to the mobile terminal 22 via the network.
In step 104, the mobile terminal 22 (user interface application 30) and the authentication device 23 execute a short-range wireless communication (BLE: Bluetooth Low Energy) connection. Here, the authentication device 23 periodically transmits advertisements. When the mobile terminal 22 receives the advertisement within the reserved time for renting the vehicle 1, the mobile terminal 22 transmits the communication connection request to the authentication device 23. When the authentication device 23 receives the communication connection request from the mobile terminal 22, the authentication device 23 transmits a communication connection confirmation to the mobile terminal 22 to notify the other party that the communication has been established. As a result, BLE communication between the mobile terminal 22 and the authentication device 23 is established.

In step 105, when the communication connection (BLE connection) is completed, the authentication device 23 transmits a key information request requesting notification of the key information Dk registered in the mobile terminal 22.
In step 106, when the mobile terminal 22 (user interface application 30) receives the key information request from the authentication device 23, it transmits a key information notification notifying the authentication device 23 of the key information Dk registered in itself.

In step 107, when the authentication device 23 receives the key information Dk from the mobile terminal 22, the authentication device 23 executes the authentication operation of the key information Dk. In the case of this example, the multiple use permission unit 40 decrypts the key information Dk using the authentication device unique key registered in the authentication device 23. Here, a plurality of authentication device unique keys A, B, ... Are registered in the memory 36 of the authentication device 23 of this example. Therefore, the multiple use permission unit 40 decrypts the key information Dk by sequentially decrypting with these authentication device unique keys. Then, if the decryption of the key information Dk is successful, the multiple use permission unit 40 considers that the key information Dk received from the mobile terminal 22 is correct and succeeds in the authentication. On the other hand, if the authentication is not established, the multiple use permission unit 40 considers that the key information Dk is incorrect, fails the authentication, and disconnects the BLE communication connection.

In step 108, the authentication device 23 executes the user authentication key notification that notifies the mobile terminal 22 of the user authentication key when the authentication work of the key information Dk is completed correctly.
In step 109, when the mobile terminal 22 (user interface application 30) acquires the user authentication key, it transmits a key function on request to the authentication device 23. The key function on request is a request for switching the operation control unit 38 of the authentication device 23 to the on state (valid state).

In step 110, when the authentication device 23 receives the key function on request from the mobile terminal 22, the authentication device 23 switches the operation control unit 38 to the on state as a trigger. As a result, the authentication device 23 is in a state where the in-vehicle device 3 can be operated.

In step 111, the authentication device 23 stores the key information Dk and the user authentication key in the memory 36 of the authentication device 23 after the operation control unit 38 is switched to the ON state. Then, the mobile terminal 22 and the authentication device 23 shift to the "authentication completed state". As described above, the authentication device 23 is in a state where the vehicle door can be locked / unlocked and the engine can be started.

Here, as shown in FIG. 3, when the main user rents the shared vehicle 1 to another user (third party or the like), the main user operates his / her first mobile terminal 22a to rent the shared vehicle 1. I do. In this lending procedure, the main user first operates his / her first mobile terminal 22a to authenticate the user with the server 20. After the user authentication is completed, the main user inputs the reservation date and time (use date and time) desired by the other user, the terminal ID of the second mobile terminal 22b owned by the other user, the permission function to lend to the other user, and the like to the first mobile terminal 22a. do. The first mobile terminal 22a may acquire such information from the second mobile terminal 22b of another user through communication. The second mobile terminal 22b of this example is positioned as a bullet key, for example.

When lending the permission function to another user, if only the locking / unlocking of the vehicle door 13 is permitted, the "vehicle door locking / unlocking permission request" is input, and if only the starting of the engine 6 is permitted, the "engine start" is entered. If you want to enter the "permission request" and allow the vehicle power supply to operate up to the ACC transition, enter the "ACC transition permission request". Further, when permitting the Bluetooth communication function of the vehicle 1, the "Bluetooth communication permission request" is input.

After inputting the necessary items, the main user sends a loan procedure request to the server 20. When the server 20 receives the lending procedure request from the first mobile terminal 22a, the server 20 generates the key information Dk based on the request. In the case of this example, the server 20 uses, for example, "reservation date and time", "terminal ID", "user authentication key", "permission function", etc. in plain text, and an encryption key different from the above (this example is an authentication device unique key). ) Is used as an encryption key, and a cipher statement is generated by passing these through an encryption formula (encryption algorithm), and this ciphertext is used as key information Dk.

Here, since the example in which the shared vehicle 1 can be operated by the second mobile terminal 22b of another user is given, for example, "B" is used as the authentication device unique key. Further, in the permission function included in the key information Dk at this time, the permission request input by the main user on the first mobile terminal 22a when lending the permission function to another user is written. For example, when only locking / unlocking the vehicle door 13 is permitted when renting the vehicle 1, "vehicle door locking / unlocking permission" is written as a permission function.

The server 20 transmits the generated key information Dk to the second mobile terminal 22b of another user via the network. Then, the second mobile terminal 22b of another user authenticates the key information Dk with the authentication device 23, and if the key information Dk can be correctly decrypted, the authentication complete state is entered. That is, since the multiple use permission unit 40 can correctly decrypt the key information Dk with the authentication device unique key B, the vehicle operation on the second mobile terminal 22b is permitted. The process executed at this time is the same as in steps 104 to 111 described above, and thus the description thereof will be omitted.

Here, when it is better to set the usage time limit for the permission function, the key information Dk includes the time information Tr (in this example, the reservation date and time information). This is because, for example, permission functions related to the vehicle running system (smart operation function, vehicle door locking / unlocking function, engine start function, ACC transition request) are not good in terms of ensuring security against vehicle theft if unlimited use is permitted. , In the case of these functions, it is better to have a time limit for use.

On the other hand, as shown in FIG. 4, when it is not necessary to set the usage restriction in the permission function, the key information Dk does not include the time information Tr (in this example, the reservation date and time information). As described above, in the case of this example, the reservation date and time is an option (selection type) in which the presence / absence of setting is selected according to the permission function specified by the user. Therefore, a permission function (for example, a Bluetooth communication function) that does not have a concept of time can be freely used at any time regardless of time.

Here, as shown in FIG. 5, when the key information Dk of the mobile terminal 22 (first mobile terminal 22a, second mobile terminal 22b) in which the permission function related to the vehicle traveling system is set can be correctly decrypted, It is possible to acquire the "reservation date / time, terminal ID, user authentication key, time information, permission function" included in the key information Dk. That is, the reservation date and time, the terminal ID, the user authentication key, the time information, and the permission function can be associated with the mobile terminal 22 that can decrypt the key information Dk. Therefore, for example, the authentication device 23 can be made to recognize the date and time when the smart function, the locking / unlocking function of the vehicle door 13, the engine starting function, the ACC transition function of the vehicle power source, and the like can be used.

On the other hand, if the key information Dk of the mobile terminal 22 (first mobile terminal 22a, second mobile terminal 22b) for which the permission function for which there is no concept of time is set can be correctly decrypted, it is included in the key information Dk. It is possible to acquire the "terminal ID, user authentication key, permission function". That is, the mobile terminal 22 capable of decrypting the key information Dk can be associated with the terminal ID, the user authentication key, and the permission function, except for the parameter of the time information Tr.

As shown in FIG. 6, in step 201, it is assumed that the user turns on the operation request button on the mobile terminal 22 that has transitioned to the authentication completed state. The operation request button includes various buttons according to the permission function, such as a smart operation request button, a door unlock request button, a door lock request button, an engine start request button, an ACC transition request button, and a wireless communication request button. The operation request button is preferably a button displayed on the touch panel of the mobile terminal 22.

In step 202, when the mobile terminal 22 (user interface application 30) detects that the operation request button has been operated on the mobile terminal 22, the operation request signal corresponding to the operation request button is encrypted with the user authentication key. The operation request signal is a signal including a command corresponding to the operated operation request button, a terminal ID, and the like.

In step 203, the mobile terminal 22 (user interface application 30) transmits the encrypted operation request signal to the authentication device 23 via short-range radio.
In step 204, when the authentication device 23 receives the operation request signal from the mobile terminal 22, the authentication device 23 controls the operation of the in-vehicle device 3 based on this signal. In the case of this example, the operation control unit 38 identifies the mobile terminal 22 from the received terminal ID. Then, the operation control unit 38 executes the operation of the permission function according to the acquired terminal ID.

By the way, the first mobile terminal 22a is positioned as a vehicle key used by the main user. Therefore, it is preferable that the permission function registered in the first mobile terminal 22a is a smart operation function capable of freely operating the vehicle 1.

Here, it is assumed that a smart operation request signal is transmitted to the authentication device 23 as an operation request signal from the first mobile terminal 22a positioned so that the vehicle 1 can be freely operated. In this case, since the operation control unit 38 receives the smart operation request signal from the first mobile terminal 22a, it outputs the smart operation permission to the matching ECU 9 through the wiring 31. The collation ECU 9 switches to the smart operation permission state by receiving the smart operation permission from the operation control unit 38. Therefore, under the establishment of the outdoor smart verification, the vehicle door 13 is unlocked when the vehicle exterior door handle is touch-operated, and the vehicle door 13 is locked when the lock button of the vehicle exterior door handle is operated. Further, if the engine switch 18 is operated while the brake pedal is depressed under the establishment of the indoor smart collation, the engine 6 is started.

Further, the second mobile terminal 22b is positioned as a bullet key. This is because there is a situation in which the main user desires not to allow other users to use the vehicle 1 in full, but to permit only some functions. Therefore, for the second mobile terminal 22b used by another user, only the operation of opening and closing the vehicle door 13 and the operation of switching the vehicle power supply to ACC in order to listen to music by the in-vehicle audio, the in-vehicle wireless communication function (Bluetooth). Only the operation to switch on the communication function) is allowed. Therefore, it is preferable that the permission functions registered in the second mobile terminal 22b are door unlocking permission only, door locking permission only, engine start permission only, ACC transition permission only, and wireless communication permission only.

Here, it is assumed that the door unlock request signal is transmitted to the authentication device 23 as the operation request signal from the second mobile terminal 22b positioned as the bullet key. In this case, the operation control unit 38 receives the door unlock request signal from the second mobile terminal 22b, so that the door unlock permission is output to the collation ECU 9 through the wiring 31 and the vehicle door 13 is released to the body ECU 10. Lock it. The notification of the door unlock request may be output directly from the authentication device 23 to the body ECU 10 or may be output to the body ECU 10 through the communication line 12. The body ECU 10 unlocks the vehicle door 13 based on the obtained door unlocking permission.

Further, when the second mobile terminal 22b is a wearable terminal, it is assumed that the wireless communication request signal is transmitted from the wearable terminal to the authentication device 23 as an operation request signal. In this case, since the operation control unit 38 receives the wireless communication request signal from the wearable terminal, it outputs the wireless communication permission to the in-vehicle communication device (not shown) through the wiring 31 and between the wearable terminal and the in-vehicle communication device. To enable wireless communication. In the case of this example, the use of the wireless communication function has no time limit and is permitted to be used at all times. Therefore, when the function of sequentially monitoring the biological information (pulse information) is activated on the wearable terminal, the detected biological information (pulse information) can be continuously sent from the wearable terminal to the vehicle 1 without a time limit.

Further, when the vehicle 1 is equipped with a driving support function for automatically stopping the vehicle 1 in the event of an abnormality, it is assumed that a driving support request signal is transmitted from the second mobile terminal 22b to the authentication device 23. In this case, since the operation control unit 38 receives the driving support request signal from the second mobile terminal 22b, it outputs the driving support permission to the device (not shown) that controls the operation of the driving support function. Here, if the driving support function is set so that there is no time limit, the driving support function can be always operated regardless of the time.

By the way, in the case of this example, when the in-vehicle device 3 of the shared vehicle 1 is operated by the mobile terminal 22, the in-vehicle device 3 can be operated not only by one mobile terminal 22 but also by another mobile terminal 22. Therefore, one shared vehicle 1 can be operated by a plurality of mobile terminals 22.

The authentication device 23 includes a plurality of authentication device-specific keys used for authenticating the key information Dk in the memory 36. The multiple use permission unit 40 confirms which of the plurality of authentication device unique keys can correctly decrypt the key information Dk, and enables the vehicle 1 to be operated by the decrypted mobile terminal 22. The vehicle 1 can be operated over a plurality of mobile terminals 22. Therefore, the vehicle 1 can be operated by a plurality of mobile terminals 22 by a simple method of registering a plurality of authentication device unique keys in the memory 36 of the authentication device 23.

When the in-vehicle device 3 is operated by the mobile terminal 22, the authentication device 23 identifies the mobile terminal 22 from the terminal ID unique to each mobile terminal 22. Therefore, when the mobile terminal 22 communicates with the authentication device 23 to operate the in-vehicle device 3, the mobile terminal 22 is identified by the terminal ID possessed by the mobile terminal 22, and the in-vehicle device 3 is used in a manner corresponding to each mobile terminal 22. Can be activated.

Each of the mobile terminals 22 is provided with a permission function that allows the vehicle 1 to operate. When the in-vehicle device 3 is operated by the mobile terminal 22, the authentication device 23 recognizes the permission function from the terminal ID uniquely possessed by the mobile terminal 22, and operates the in-vehicle device 3 according to the permission function. Therefore, the in-vehicle device 3 can be operated in a manner corresponding to the permission function set in each mobile terminal 22.

When the authentication device 23 includes the time information Tr used to set the date and time when the in-vehicle device 3 can be operated by the authentication device 23, the mobile terminal 22 operates the in-vehicle device 3 only for a period determined by the time information Tr. Allow. The time information Tr is selected to be included or not included in the key information Dk according to the permission function set in the mobile terminal 22. Therefore, when the mobile terminal 22 operates the in-vehicle device 3 without the concept of time, the state in which the in-vehicle device 3 can be operated by the mobile terminal 22 can be continued without a time limit.

In addition, this embodiment can be implemented by changing as follows. The present embodiment and the following modified examples can be implemented in combination with each other within a technically consistent range.
-The authentication device 23 may be retrofitted to the vehicle 1 or may be pre-assembled to the vehicle 1.

-The authentication device 23 may be integrated with the verification ECU 9 and these may be one unit component.
-The request for the rental procedure of the vehicle 1 is not limited to being transmitted from the first mobile terminal 22a, but may be transmitted from the second mobile terminal 22b.

-The rental procedure of the vehicle 1 may be performed by using only the second mobile terminal 22b of another user without passing through the first mobile terminal 22a.
-Near field communication is not limited to Bluetooth communication, and can be changed to other communication methods.

-The key information Dk is not limited to the one-time key, and may be any information whose use is restricted.
-The encryption key used for encrypted communication may be any of, for example, an authentication device unique key, a user authentication key, and a key unique key. For example, switching the encryption key used in the middle of processing is advantageous for ensuring the security of communication. Further, the encryption key to be used is not limited to the above-mentioned key, and may be changed to various keys.

-The mounting location of the authentication device 23 is not particularly limited.
-The mobile terminal 22 is not limited to a high-performance mobile phone, and can be changed to various terminals.
-The mobile terminal 22 and the authentication device 23 may acquire the user authentication key by any procedure or method.

-The content included in the key information Dk can be changed to an aspect other than the embodiment.
-The key information Dk is not limited to being generated by the server 20, and may be anywhere as long as it is external.

-Any condition may be used for switching the operation control unit 38 to the effective (on state).
The operation-free electronic key system 4 is not limited to a system in which transmitters are arranged inside and outside the vehicle to determine the positions inside and outside the vehicle of the electronic key 2 and perform smart collation. For example, a system may be used in which antennas (LF antennas) are arranged on the left and right sides of the vehicle body, and the position of the electronic key 2 inside and outside the vehicle is determined by checking the combination of the responses of the electronic key 2 to the radio waves transmitted from these antennas.

-The ID verification imposed on the electronic key system 4 is not limited to the verification including the challenge response authentication, and at least any authentication or verification may be included as long as the electronic key ID verification is performed.

-The electronic key system 4 may be a wireless key system in which ID verification is executed, for example, triggered by communication from the electronic key 2.
-The electronic key 2 is not limited to the smart key (registered trademark) and may be a wireless key.

-As shown in FIG. 7, the collation ECU 9 and the authentication device 23 may have a structure in which they are connected wirelessly instead of by wire. In this case, a communication block 45 capable of communicating on the communication network of the electronic key system 4 is configured in the authentication device 23, and the electronic key ID and the key unique key are registered in the memory 36 of the authentication device 23. Then, when the authentication device 23 receives various request signals from the mobile terminal 22, the request corresponding to the signals is transmitted to the verification ECU 9 via the communication network of the electronic key system 4. As a result, the collation ECU 9 is operated to operate the in-vehicle device 3 in response to the request from the mobile terminal 22. In this case, since the authentication device 23 can be made wireless, wiring and the like can be eliminated.

-By providing a plurality of authentication device unique keys, the vehicle 1 is not limited to being compatible with a plurality of terminals. For example, one authentication device unique key may be commonly used among a plurality of mobile terminals 22, and one vehicle 1 may be operated by a plurality of mobile terminals 22.

-The sharing system 21 is not limited to being applied to the vehicle 1, and may be applied to other devices and devices such as a house (sharing house). Therefore, the common object 24 is not limited to the vehicle 1, and the operation target 25 is not limited to the in-vehicle device 3, and these can be changed to other members.

Next, the technical idea that can be grasped from the above-described embodiment and modified examples will be described.
(B) In the sharing system, it is preferable that the common object is a vehicle and the operation target is an in-vehicle device. According to this configuration, one vehicle can be operated by a plurality of mobile terminals 22.

(B) In the sharing system, when the operation target of the common object is operated by the mobile terminal, the authentication device in the authentication completed state is passed through the electronic key system provided in the common object. , It is preferable to operate the operation target. According to this configuration, the authentication device can be made wireless, so that wiring and the like can be eliminated.

1 ... Vehicle (shared vehicle), 2 ... Electronic key, 3 ... In-vehicle device, 4 ... Electronic key system, 21 ... Sharing system, 22 ... Mobile terminal, 22a ... 1st mobile terminal, 22b ... 2nd mobile terminal, 23 ... Authentication device, 24 ... Common object, 25 ... Operation target, 36 ... Memory, 40 ... Multiple use permission unit, Dk ... Key information, Tr ... Time information.

Claims (4)

The key information is authenticated wirelessly between a mobile terminal that can operate as a key of a common object by registering unique key information and an authentication device mounted on the common object, and the common object is used. This is a sharing system in which the operation target is operated by the authentication device in the authentication completed state when the operation of the operation target controlled through the electronic key system of the above is performed on the mobile terminal.
It is provided with a plurality of usage permission units that enable the common object to be operated by the plurality of mobile terminals owned by each person .
The plurality of mobile terminals are configured to include a first mobile terminal and a second mobile terminal different from the first mobile terminal.
The authentication device includes a plurality of authentication device-specific keys used for authenticating the key information in a memory, and each of the plurality of authentication device-specific keys corresponds to any one of the plurality of mobile terminals. And
When the first mobile terminal requests permission to operate the common object on the second mobile terminal, the permission information for enabling the common object to be operated on the second mobile terminal is the first. 2 The authentication device unique key corresponding to the mobile terminal is encrypted as an encryption key, and the encrypted permission information is used as the key information.
The multiple use permission unit confirms which of the plurality of authentication device unique keys can correctly decrypt the key information, and uses the second mobile terminal corresponding to the decrypted authentication device unique key. A sharing system that enables the common object to be operated over a plurality of the mobile terminals by enabling the common object to be operated . The sharing system according to claim 1, wherein the authentication device identifies the mobile terminal from a terminal ID unique to each mobile terminal when the operation target is operated by the mobile terminal. Each of the mobile terminals is provided with a permission function that allows operation of the common object.
The authentication device recognizes the permission function from the terminal ID unique to each mobile terminal when the operation target is operated by the mobile terminal, and operates the operation target according to the permission function. Or the sharing system according to 2. When the authentication device includes time information used to set a date and time when the operation target can be operated by the authentication device, the mobile terminal permits the operation of the operation target only for a period determined from the time information. death,
The sharing system according to claim 3 , wherein the time information is selected whether or not it is included in the key information according to the permission function set in the mobile terminal.

Images