Method and system for opening and/or using at least one vehicle

Abstract

A method for opening and/or using at least one vehicle may include receiving, by a mobile terminal, an identifier assigned to a target vehicle. The identifier may be transmitted to a server, and a key data set may be received from the server. The key data set and/or a code based on the key data set may be transmitted as a remote code to the target vehicle. The target vehicle may generate at least one local code after receiving the remote code, and may compare the remote code to the local code(s). The target vehicle may be opened and/or released, or a vehicle command may be executed if at least one of the local codes corresponds to the remote code.

Claims

1. A method for opening and/or using at least one vehicle, comprising: a) receiving, by a mobile terminal, an identifier, which is assigned to a target vehicle; b) transmitting the identifier, via a mobile wireless network, to a server; c) receiving, by the mobile terminal, a key data set from the server, wherein the key data set comprises a seed key, and wherein the mobile terminal generates a remote code using the seed key, by means of a pseudorandom number generator; d) transmitting to the target vehicle the key data set and/or a code generated based on the key data set as the remote code, via a direct connection and/or an ad hoc network between the target vehicle and the mobile terminal; e) receiving the remote code by the target vehicle; f) generating at least one local code by the target vehicle; g) comparing the remote code to the at least one local code by the target vehicle; h) opening and/or releasing the target vehicle and/or executing a vehicle command on the target vehicle upon determining that the at least one local code corresponds to the remote code.

2. The method according to claim 1, wherein generating the at least one local code and/or the remote code comprises generating the at least one local code and/or the remote code using a rolling code method and/or based on a rolling code method.

3. The method according to claim 1, wherein the at least one local code comprises a first and multiple further local codes, and wherein opening and/or release of the target vehicle does not take place only upon determining that none of the local codes corresponds to the remote code.

4. The method according to claim 1, wherein the direct connection is designed as a Bluetooth connection, an infrared connection, or a WLAN connection.

5. The method according to claim 1, wherein d) comprises transmitting a specification with respect to a point in time or time window and/or c) comprises receiving an indication with respect to a point in time or time window, wherein the generated remote code is valid at the point in time or during the time window.

6. The method according to claim 1 wherein the vehicle has first and second key data for generating a first key sequence or second key sequence, respectively, wherein the method further comprises: receiving key information by the mobile terminal at the vehicle; selecting the first or second key data using the key information; generating at least one code of the at least one local code using the selected key data; comparing the at least one generated local code to the received remote code; and opening and/or releasing the vehicle and/or executing a vehicle command upon determining that the remote code corresponds to the at least one generated local code of the selected key data.

7. A computer-readable storage medium, which contains instructions which cause at least one processor to implement the method according to claim 1 when the instructions are executed by the at least one processor.

8. The method according to claim 1, wherein the remote code loses its validity after one-time use by the target vehicle or loses its validity after a defined time span, or the remote code is only usable for opening and/or releasing the target vehicle within a predefined time window.

9. The method according to claim 4, wherein 1) the target vehicle and the server or 2) the mobile terminal and the server have timers that are each synchronized with one another, wherein the remote code and the at least one local code are generated continuously at equal time intervals.

10. The method according to claim 1, wherein the method furthermore further comprises: transmitting a command data set from the mobile terminal to the target vehicle, wherein the command data set comprises at least the vehicle command; receiving the command data set by the target vehicle; and executing at least the vehicle command upon determining that the at least one local code corresponds to the remote code.

11. The method according to claim 10, wherein the remote code is valid within a time window.

12. A system for opening and/or using a vehicle, comprising: at least one server, which comprises a database, and which receives at least one identifier from at least one mobile terminal, wherein the server determines a target vehicle using the database and the identifier; and a vehicle, including the following: a storage unit; a vehicle communication unit which is designed to receive a key data set and/or a code generated based on the key data set as a remote code via a direct connection and/or via an ad hoc network, wherein the key data set comprises a seed key, and wherein the mobile terminal generates the remote code using the seed key, by means of a pseudorandom number generator; and a vehicle processing unit designed to generate a local code and to compare the remote code to the local code; wherein the vehicle processing unit furthermore opens and/or releases the vehicle and/or executes a vehicle command upon determining that the remote code and the local code correspond.

13. The system according to claim 12, wherein the local code and/or the remote code are generated by a rolling code method, and/or are generated based on a rolling code method.

14. The system according to claim 12, wherein the key data set comprises a seed key, and wherein the system further comprises a mobile terminal, wherein the mobile terminal comprises: a terminal communication unit, which to receives the key data set; and a terminal processing unit, which generates the remote code using the seed key, by means of a pseudorandom number generator.

Description

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

(1) The foregoing summary, as well as the following detailed description of the invention, will be better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there are shown in the drawings embodiments which are presently preferred. It should be understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown. In the drawings:

(2) FIG. 1 shows a schematic view of the system according to the invention;

(3) FIG. 2 shows a schematic view of a bicycle;

(4) FIG. 3 shows a schematic view of a mobile terminal;

(5) FIG. 4 shows a schematic view of a server;

(6) FIG. 5 shows an exemplary database table;

(7) FIG. 6 shows a flow chart for a method for opening a vehicle;

(8) FIG. 7 shows a schematic view of the validity duration of remote codes;

(9) FIG. 8 shows a chronological representation of the validity duration of a remote code;

(10) FIG. 9 shows a database table having various seed keys;

(11) FIG. 10 shows a schematic illustration of various key sequences; and

(12) FIG. 11 shows a schematic illustration of a vehicle and a mobile terminal without Internet connection.

DETAILED DESCRIPTION OF THE INVENTION

(13) The same reference signs are used hereafter for identical or identically acting parts.

(14) FIG. 1 shows a schematic illustration of a system 1 for opening a vehicle 10 using a mobile terminal 20. The vehicle 10 is designed as a bicycle 10 in the described exemplary embodiment. Furthermore, the system 1 has a mobile terminal 20, which is designed in the present exemplary embodiment as a smart phone 20. The smart phone 20 is connected via a mobile wireless connection 5 to a server 30.

(15) The mobile wireless connection 5 can be a mobile wireless connection according to the LTE, UMTS, or GSM standard. Furthermore, the connection 5 can also be any further conceivable Internet connection. The connection 5 can be designed as wireless or wired.

(16) To open the bicycle 10, the smart phone 20 requests an identifier 15 from the bicycle 10. This identifier is transmitted via a direct connection 2 in the described exemplary embodiment. In this case, this is a Bluetooth connection in the present example. The smart phone 20 is therefore located within a receiving radius of the bicycle 10 to request the identifier, since otherwise a Bluetooth connection 6 could not be established.

(17) In other exemplary embodiments, the direct connection 2 can also be a WLAN connection 4 or an ad hoc network 3.

(18) The identifier 15 ensures a unique identification of the bicycle 10. The identifier 15 can therefore be a global unique identifier (GUID). It is not necessary to use a globally unique identifier. A number unique in the described system is also possible.

(19) The smart phone 20 transmits the received identifier 15 to the server 30 and requests a remote code 43 from the server 30. In the present exemplary embodiment, the smart phone 20 transmits the identifier 15 via an LTE connection 5 to the server 30.

(20) The server 30 thereupon executes a data query, wherein a remote code 43 is generated using the received identifier 15. For this purpose, the server 30 has a seed key stored in a database for every vehicle. Using a pseudorandom number generator, the server 30 generates a remote code 43 which can be used only by the bicycle 10.

(21) The server 30 transmits the generated remote code 43 to the smart phone 20.

(22) In other exemplary embodiments, the server 30 can transmit a key data set 40 to the smart phone 20 instead of the remote code 43. The key data set 40 can comprise the seed key in this case. The smart phone 20 can thus also be used for the purpose of generating a remote code 43.

(23) In a further exemplary embodiment, the server 30 transmits not only one remote code 43 to the mobile terminal 20, but rather a plurality of remote codes.

(24) The communication between mobile terminal 20 and server 30 can also be designed as encrypted, for example, by way of an asymmetrical encryption method such as PGP. The mobile terminal 20 and the server can thus each store a private key, wherein the messages between mobile terminal 20 and the server 30 are encrypted by a public key. The private keys are each used to decrypt the messages.

(25) The transmitted key data set 40 can thus comprise an encrypted remote code 43.

(26) The smart phone 20 can use the received remote code 43 to unlock the bicycle 20. For this purpose, the smart phone 20 transmits the received remote code 43 via a Bluetooth connection 6 to the bicycle 10. As shown in FIG. 2, the bicycle 10 has a vehicle communication unit 11, via which the remote code 43 can be received.

(27) In the present exemplary embodiment, the vehicle communication unit 11 is designed as a Bluetooth module. The bicycle 10 furthermore has a storage unit 17, in which the remote code 43 is written after reception by the vehicle communication unit 11. Using a pseudorandom number generator 14, the bicycle 10 can generate a local code 42, which is compared by a vehicle processing unit 12 to the received remote code 43. If remote code 43 and local code 42 correspond, the bicycle 10 is thus unlocked. The power supply of the bicycle 10 is furthermore ensured via a battery 16.

(28) FIG. 3 shows a schematic illustration of a mobile terminal 20. The mobile terminal 20 comprises a terminal communication unit 21, which is designed in the present exemplary embodiment as a Bluetooth communication unit 21. The terminal communication unit 21 has a communicative connection to a terminal storage unit 23. The mobile terminal 20 furthermore has a terminal processing unit 22, which has a communicative connection to the terminal storage unit 23.

(29) In one exemplary embodiment, the mobile terminal 20 can also have a pseudorandom number generator 24. Using the pseudorandom number generator 24, the mobile terminal is capable of independently generating remote codes 43.

(30) FIG. 4 shows the schematic illustration of a server 30. The server 30 has a server communication unit 33, which is designed in the present exemplary embodiment to provide an Internet connection. The server communication unit 33 has communicative connection to a server storage unit 31, in which a database 32, 32′ (see FIGS. 5 and 9) is stored. The server 30 furthermore has a server processing unit 34. The server 30 is also designed in one exemplary embodiment to generate remote codes 43 using a pseudorandom number generator. In a further exemplary embodiment, however, a large number of remote codes 43 can also be stored in the database 32.

(31) FIG. 5 shows a database table of the database 32, which is stored on the server 30. The illustrated database table comprises two columns, wherein vehicle identification numbers 15, 15′, 15″ are stored in a first column. A seed key 45, 45′, 45″ is assigned to each vehicle identification 15, 15′, 15″. Since a vehicle identification number 15, 15′, 15″ is uniquely assigned to each vehicle, a corresponding seed key 45, 45′, 45″ is assigned to each vehicle 10 via the database 32.

(32) In one exemplary embodiment, the server 30 determines the associated seed key 45, 45′, 45″ after receiving a vehicle identification 15, 15′, 15″. Using the determined seed key 45, 45′, 45″, the server 30 generates a remote code 43, which is transmitted via the server communication unit 33 to the smart phone 20.

(33) In other exemplary embodiments, the server 30 directly transmits the determined seed key 45, 45′, 45″.

(34) FIG. 6 shows a flow chart which illustrates the steps for opening a vehicle 10.

(35) In step S1, a mobile terminal 20 receives an identifier 15 from a vehicle 10. The identifier 15 is transmitted in step S2 via a mobile wireless network 5 to the server 30. In step S3, the server 30 generates a remote code 43 and transmits the remote code 43 to the mobile terminal 20.

(36) In a further exemplary embodiment, the server 30 transmits a seed key 45 to the mobile terminal. In still another exemplary embodiment, the server 30 transmits a plurality of remote codes 43 to the mobile terminal 20.

(37) After the reception of the remote code 43 from the server 30 on the mobile terminal 20, the mobile terminal 20 transmits the remote code 43 to the vehicle 10 in step S4. The transmission is executed in the present exemplary embodiment via a WLAN.

(38) In step S5, the vehicle 10 receives the remote code 43 and, in step S6, generates a local code 42. In step S7, the generated local code 42 and the received remote code 43 are compared to one another. If the two codes do not correspond, an error message is thus transmitted to the mobile terminal 20 in step S9. In a further exemplary embodiment, a counter can be incremented in step S9, so that after a number of attempts, preferably three attempts, the vehicle is permanently locked.

(39) If the generated local code 42 and the received remote code 43 correspond, the vehicle 10 is thus opened in step S8. In one exemplary embodiment, a control electronics unit can be used during the opening to actuate a positioning motor which opens a lock. Alternatively, a magnetic lock can also be used.

(40) In a further exemplary embodiment, an arbitrary vehicle command can be executed in step S8, which was transmitted together with the remote code 43 to the vehicle 10 in step S4.

(41) In subsequent step S10, the received remote code is (optionally) marked as invalid. This means that upon a further reception of the same remote code 43, it no longer functions. If a rolling code method is used, not only the present remote code 43 thus becomes invalid, but rather all remote codes lying before it with respect to time are also marked as invalid.

(42) FIG. 7 schematically shows the generation of local codes 42, 42′, 42″ and remote codes 43, 43′, 43″ in one exemplary embodiment, in which synchronized timers 13, 24 are used to generate remote and/or local codes at continuous time intervals. In the present exemplary embodiment, the vehicle 10 and the mobile terminal 20 comprise timers 13, 24 which are synchronized. At a first point in time T1, a remote code 43 is generated on the mobile terminal 20 and a local code 42 is generated on the vehicle 10. After passage of a validity duration 47, the local code 42 and the remote code 43 are marked as invalid. Subsequently, a new local code 42 and a new remote code 43 are generated at the point in time T2. These are in turn marked as invalid after passage of the validity duration 47, whereupon a new local code 42″ and a new remote code 43″ are subsequently generated.

(43) Because the remote and local codes are each marked as invalid, it is absolutely necessary for the timers 13, 24 used to be synchronized. The synchronization of the timers 13, 24 can be carried out either by a corresponding protocol during operation or upon delivery of the individual components.

(44) FIG. 8 shows an exemplary embodiment in which a generated remote code 43 is valid in a time window TF around a point in time T. It is thus possible that a point in time T is defined for a remote code 43 at which the remote code 43 is to be valid. Furthermore, it is possible to define a time window TF, for example, 5 minutes, which is used as a buffer or also lending duration. The remote code 43 can then only be used in the period of time T-TF and T+TF for opening a vehicle 10. Point in time T and duration TF can be transmitted as information with the remote code 43 from the mobile terminal 20 to the vehicle 10.

(45) FIG. 9 shows a table of a database 32′, in which a plurality of seed keys 45, 45′, 45″ of different types are assigned to a vehicle 10. An identifier 15 is assigned to three seed keys 45, 45′, 45″ in the example shown. One seed key type 48, 48′, 48″ specifies the validity duration of the remote code 43 generated using the seed keys 45, 45′, 45″.

(46) For example, the seed key type 48 can specify that the remote codes 43 which are generated using the seed key 45 have a validity of 30 minutes. Generated remote codes of the key type 48′ can have a validity of 60 minutes and remote codes of the key type 48″ can have a validity of 3 hours. The mobile terminal 20 generates a remote code 43 on the basis of the seed key 45, 45′, 45″ received from the server 30.

(47) The remote code 43 is transmitted to the vehicle 10. In order that the vehicle 10 can determine from which type 48, 48′, 48″ the remote code 43 is, the vehicle 10 has the same seed keys 45, 45′, 45″ as the server 30. The vehicle 10 generates local codes K1 to K6 for all seed keys 45, 45′, 45″ and compares the received remote code 43 to all generated local codes K1 to K6. Depending on which local code K1 to K6 corresponds to the received remote code 43, the vehicle can determine by which seed key 45, 45′, 45″ the local code K1 to K6 was generated. It may therefore be established by the comparison from which key type 48, 48′, 48″ the received remote code 43 is.

(48) If it is established, for example, that the received remote code 43 is from the type 48′, the vehicle 10 is thus released for 60 minutes.

(49) In one exemplary embodiment, the mobile terminal 20 transmits the key type 48, 48′, 48″ as information to the vehicle 10 together with the remote code 43. The vehicle 10 can then establish using the received key type 48, 48′, 48″ which seed key 45, 45′, 45″ it has to use to generate a local code 45.

(50) FIG. 10 shows various key sequences 46, 46′ 46″, which were generated on the vehicle 10. Each key sequence 46, 46′ 46″ is a seed key 45, 45′, 45″, which are each assigned to a different key type 48, 48′, 48″.

(51) FIG. 11 shows how a smart phone 20 can open a bicycle 10 without an existing Internet connection to a server 30. A remote code 43 is stored on the smart phone 20. The remote code 43 can be transmitted by means of a Bluetooth connection 6, a WLAN connection, or via an ad hoc network 3 to the bicycle 10. The bicycle 10 compares the received remote code 43 to a generated local code 42 and releases the bicycle 10 accordingly.

(52) It will be appreciated by those skilled in the art that changes could be made to the embodiments described above without departing from the broad inventive concept thereof. It is understood, therefore, that this invention is not limited to the particular embodiments disclosed, but it is intended to cover modifications within the spirit and scope of the present invention as defined by the appended claims.

LIST OF REFERENCE SIGNS

(53) 1 system 2 direct connection 3 ad hoc network 4 WLAN 5 mobile wireless network 6 Bluetooth connection 10, 10′, 10″ vehicle, target vehicle, bicycle 11 vehicle communication unit 12 vehicle processing unit 13, 24 timer 14, 24 pseudorandom number generator 15, 15′, 15″ identifier 16 battery, power supply 17, 31 storage unit 20 mobile terminal, smart phone 21 terminal communication unit 22 terminal processing unit 23 terminal storage unit 30 server 32, 32′ database 33 server communication unit 34 server processing unit 40 key data set 41 code 42, 42′, 42″ local code 43, 43′, 43″ remote code K1, K2 key from the type 48 K3, K4 key from the type 48′ K5, K6 key from the type 48″ 45, 45′, 45″ seed key 46, 46′, 46″ key sequence 47 validity duration 48, 48′, 48″ key type 50 command data set 51 vehicle command TS time span TA time intervals T, T1, T2, T3 point in time TF time window S1, S2, S3, step S4, S5, S6, S7, S8, S9, S10