Method for registering digital vehicle keys in a virtual wallet and associated devices

Abstract

The present invention relates to a method comprising the following steps: - reception, by a system (1), of a first identifier and a second identifier transmitted by a user terminal (5) previously transmitted to the user terminal (5) by the device (2) via wireless communication requiring proximity between the user terminal (5) and the device (2), - verification by the system (1) of the existence of a correspondence between two stored reference identifiers corresponding respectively to the first identifier and the second identifier, - provided that said correspondence exists, transmission by the system (1): - of a pairing password to the user terminal (5), - of a verifier to a control unit (3) of the vehicle (4), the verifier being configured to allow the establishment of a secure communication channel between the user terminal (5) and the control unit (3) of the vehicle (4). Figures in the abstract: Fig.3.

Description

Title of the invention: Method for recording digital keys of a vehicle in a virtual wallet and associated devices FIELD OF THE INVENTION

[0001] The invention relates to digital key services for vehicles, in particular motor vehicles. STATE OF THE ART

[0002] Vehicle manufacturers are launching digital key services (also known as "phone-as-a-key services") to replace traditional keys with a terminal such as a mobile phone. The terminal can be used, for example, to unlock a vehicle door or start the vehicle's engine.

[0003] However, current digital key services lack ergonomics.

[0004] Indeed, users experience difficulties in initiating the procedure for pairing a vehicle with their mobile phone and proving that they are actually the owner of the vehicle in order to finalize the pairing of the two devices.

[0005] Manufacturers also provide a smart card comprising at least one contact and / or contactless communication interface as a backup solution in order to be able to use the vehicle even when the terminal is not usable, for example when it is out of service or discharged.

[0006] However, current digital key services do not offer services related to the smart card. The user of a vehicle cannot therefore carry out simple operations such as blocking the smart card or ordering a new one. Furthermore, it is not provided that several smart cards can be used with the same vehicle. Thus, in the event of a problem with the card and the terminal, the user can no longer use his vehicle. Statement of the invention

[0007] An aim of the invention is therefore to offer a new service to the user facilitating the pairing of his mobile telephone with the vehicle and the management of smart cards.

[0008] For this purpose, a pairing initialization method is proposed comprising the following steps:

[0009] - reception, by a system, of a first identifier and a second identifier transmitted by a user terminal, the first identifier being specific to a vehicle and the second identifier being specific to a device, the first identifier and the second identifier having been previously transmitted to the user terminal by the device by wireless communication requiring proximity between the terminal and the device,

[0010] - verification by the system of the existence, in a database, of a corres correspondence between two reference identifiers stored in the database corresponding respectively to the first identifier and the second identifier,

[0011] - provided that said correspondence exists in the database, transmission by the system:

[0012] - a pairing password to the user terminal,

[0013] - from a verifier to a vehicle control unit, the verifier being configured to authorize establishment of a secure communication channel between the terminal and the vehicle control unit provided that a candidate password transmitted by the user terminal to the vehicle control unit corresponds to said transmitted pairing password.

[0014] Thus, the procedure for pairing the vehicle to the terminal is simplified. Indeed, the user only needs to place the smart card near his mobile phone to start the pairing procedure and provide a password, sent by the system to his phone, to prove that he is the owner of the vehicle in order to finalize the pairing.

[0015] In addition, the system serves as an interface between the user and the digital key services. Additional services linked to the smart card, such as blocking the smart card, ordering a new smart card or pairing several smart cards with the vehicle, can therefore be directly configured and centralized in the system to be easily accessible by the user by connecting to the system, particularly in the event of a problem with the smart card.

[0016] We can predict the steps of: - reception, by the system, of the two reference identifiers, the two reference identifiers being transmitted by the vehicle control unit, - storing the two reference identifiers in the database after their reception.

[0017] The following steps can be planned: - reception, by the system, of a dissociation order between the first identifier and the second identifier, the dissociation order being issued by the user terminal and comprising at least one of the first and second identifiers; - provided that a correspondence between at least one of the two reference identifiers stored in the system database and at least one of the first identifier and the second identifier included in the order of dissociation exists in the database, deletion of the correspondence in the database; and - transmission by the system of a dissociation request to the control unit of the vehicle, said request being configured to inform the vehicle control unit that a deletion of said correspondence has been made in the database and to command the vehicle control unit to dissociate the device and / or the user terminal from the vehicle control unit, the control unit being configured to, after receiving the dissociation request from the system, not process commands emanating from the device and / or the user terminal.

[0018] We can further provide a step of: - saving the reference identifier corresponding to the first identifier in a second database different from the database before deleting the correspondence in the database.

[0019] The following steps can be planned: - reception by the system of a command from a second device distinct from the device; - transmission, by the system and to a device supplier, of the command.

[0020] It may be provided in particular that the system also transmits the first identifier specific to the vehicle to the device supplier.

[0021] The following steps can be planned: - receiving a notification issued by the vehicle control unit, the notification informing the system of a pairing request between a second device and the vehicle control unit, the second device being distinct from the device; - upon receipt of said notification, transmission to the user terminal by the system of an invitation to accept the pairing request; - receipt by the system of a response to the invitation, the response indicating whether the pairing request is accepted or not; and - transmission to the vehicle control unit, by the system, of an authorization or a refusal of the pairing request depending on said response.

[0022] It can be provided that the transmission of the first identifier and the second identifier to the user terminal comprises: - near field communication (NFC), or - an optical reading, by the user terminal, of a pattern representative of the first and second identifiers and displayed by the device, the pattern being for example a bar code or a QR code.

[0023] It can be provided that the device is a smart card.

[0024] According to the invention, a system is also provided comprising:

[0025] - a communication interface configured to receive a first identifier and a second identifier transmitted by a user terminal, the first identifier being specific to a vehicle and the second identifier being specific to a device, the first identifier and the second identifier having been previously transmitted to the user terminal by the device by wireless communication requiring proximity between the terminal and the device, the system being configured to verify the existence, in a database, of a correspondence between two reference identifiers stored in the database corresponding respectively to the first identifier and to the second identifier; and - a communication interface configured to transmit: - a pairing password to the user terminal, - a verifier to a vehicle control unit, provided that said correspondence exists in the database, the verifier being configured to authorize an establishment of a secure communication channel between the terminal and the vehicle control unit provided that a candidate password transmitted by the user terminal to the vehicle control unit matches the transmitted pairing password.

[0026] The invention further provides a computer program product comprising first program code instructions for controlling the execution of the steps of the method according to the invention, when the first code instructions are executed by a system; and optionally second program code instructions for controlling the execution of the steps of a second method, when the second code instructions are executed by a user terminal, the second method comprising: - reception, by the user terminal, of the first identifier and the second identifier, transmitted by the device, - transmission, by the user terminal, to the system, of the first identifier and the second identifier received. DESCRIPTION OF FIGURES

[0027] We will now present an embodiment of the invention by way of non-limiting example with the support of the drawings in which:

[0028] [Fig.l] schematically illustrates near-field communications between an internal reader of the vehicle and the user terminal;

[0029] [Fig.2] illustrates a map of the exchanges between a system, a device and a vehicle control unit before the vehicle is first started;

[0030] [Fig.3] illustrates a map of the exchanges between the system, the device, the vehicle control unit and the user terminal after the first start of the vehicle;

[0031] [Fig.4] is a flowchart of an embodiment of the method according to the invention;

[0032] [Fig.5] is a flowchart illustrating additional steps to the flowchart of [Fig.4];

[0033] [Fig.6] is a flowchart illustrating further steps additional to the flowchart of [Fig.4]; and

[0034] [Fig.7] is a flowchart illustrating further steps in addition to the flowchart of [Fig.4]. DETAILED DESCRIPTION OF THE INVENTION Devices

[0035] Referring to [Fig. 1], a vehicle 4 comprises an internal reader 6 and a control unit 3.

[0036] The internal reader 6 comprises: - a first communication interface 61 configured to exchange data, for example via near-field communication, for example of the NFC type (NFC for “Near Field Communication” in English terminology) or Bluetooth, with a user terminal 5 and / or a device 2, 22; and - a second communication interface 62 configured to transmit data with the control unit 3 of the vehicle 4. - A push button 65 configured to control the transmission of a dissociation order between a first identifier relating to the vehicle 4 and a second identifier relating to the device 2, 22;

[0037] The first communication interface 61 may for example be located in the passenger compartment 63 of the vehicle, or at the door 64, or both.

[0038] With reference to Figures 2 and 3, the control unit 3 comprises: - a first communication interface 31; - a second communication interface 32; and - a first memory (not shown in the figures).

[0039] The first and second interfaces 31, 32 are configured as transmitters (according to the English terminology “Poller”) and / or receivers (according to the English terminology “Listener”) in a near-field communication mode, for example NFC (according to the English terminology “NFC reader”) or Bluetooth, respectively with a device 2 and a user terminal 5. It is also provided that the first communication interface 31 is configured as transmitters and / or receivers in a near-field communication mode, for example NFC (according to the English terminology “NFC reader”) or Bluetooth with a second device 22 or several devices.

[0040] Those skilled in the art will refer to the following documents NFC Analog Technical Specification 2.1 - NFC Forum, NFC Digital Protocol Technical Specification 2.1 as well than to the document Digital Key Release 3, Technical Specification 1.1.0 - Car Connectivity Consortium to configure and size the first communication interface 31 and the second communication interface 32.

[0041] For example, as a receiver, the first interface 31 is configured to receive from the device 2 an identifier specific to the device 2. As a transmitter, the first interface 31 is configured to transmit to the device 2 an identifier specific to the vehicle 4.

[0042] Furthermore, the second communication interface 32 is configured to establish a secure communication channel between the control unit 3 of the vehicle 4 and the user terminal 5. The establishment of the secure channel may for example follow a security protocol of the SPAKE2+ type by means of the first secret transmitted to the control unit 3 of the vehicle 4, for example a password verifier (or verifier in the remainder of the document) configured to authorize the establishment of the secure channel between the terminal 5 and the control unit 3 of the vehicle 4 provided that a candidate password transmitted by the user terminal 5 to the control unit 3 of the vehicle 4 corresponds to a second secret, for example a pairing password, previously transmitted to the user terminal 5 by a system 1.

[0043] Those skilled in the art will refer to the documents Network Working Group Internet Draft: SPAKE2+, an Augmented SPAKE, draft-bar-cfrg-spake2plus-00, March 9, 2020, and Digital Key Release 3, Technical Specification 1.1.0 - Car Connectivity Consortium to configure the establishment of the secure communication channel.

[0044] The control unit 3 may further comprise a third communication interface 33 configured to transmit the identifier specific to the vehicle 4 and the identifier specific to the device 2 to the system 1, or to transmit identifiers specific to several devices.

[0045] The control unit 3 may also comprise a fourth communication interface 34 configured to receive the first secret transmitted by the system 1. The memory of the control unit 3 is configured to store data, for example the first secret. In particular, the memory is configured to store the password verifier transmitted by the system 1. In addition, the memory is configured to store the identifier specific to the vehicle 4 and the identifier specific to the device 2. It is also provided that the memory of the control unit 3 is configured to store a second password verifier transmitted by the system 1 or a plurality of password verifiers of a plurality of devices transmitted by the system 1.It is also provided that the memory of the control unit 3 is configured to store the second identifier specific to the second device 22 or several identifiers specific to each device of a plurality of devices.

[0046] The control unit 3 of the vehicle 4 is further configured not to process the requests transmitted by the user terminal 5, for example when the user terminal reader 5 is in proximity to the internal reader 6 at the door 64 or in the passenger compartment 63, and by a device 2, 22. In this case, the control unit 3 of the vehicle 4 deletes the identifier specific to the device 2, 22 so that said device 2, 22 can no longer be recognized by said control unit 3 of the vehicle 4 and, the control unit 3 of the vehicle 4 deletes the first secret and deactivates the secure communication channel between said control unit 3 of the vehicle 4 and the user terminal 5.

[0047] The device 2 and the second device 22 may be smart cards comprising at least: - a second memory (not shown in the figures); and - a communication interface 21.

[0048] The communication interface 21 of the devices 2, 22 comprises an NFC module, and an antenna coil. The antenna coil has one or more coplanar coaxial windings parallel to the plane of the smart card, and consequently has a magnetic axis perpendicular to the plane of the smart card. The communication interface 21 of the devices 2, 22 (smart card) is configured to carry out NFC (near field contactless) communication with an external NFC terminal, for example the user terminal 5 (for example a smart phone or smartphone in English terminology) via the antenna coil.When the smart card (devices 2, 22) and the external NFC terminal (user terminal 5) are placed sufficiently close to each other, the antenna coil of the smart card is inductively coupled to an antenna coil of the external NFC terminal (user terminal 5), and data can be exchanged using conventional NFC techniques such as those defined by ISO 14443, ISO 15693. For this purpose, the antenna coil of the smart card is combined with passive components (e.g. capacitors) to form an antenna circuit tuned to an operating frequency of the external NFC terminal (user terminal 5), for example 13.56 MHz.

[0049] According to other embodiments, the communication interface 21 may comprise one of the following elements:

[0050] - a Bluetooth module;

[0051] - an electronic module configured to exchange data with the NFC terminal external, for example the user terminal 5, when there is contact between the external terminal and the communication interface 21 according to the ISO7816-2:2017 standard of October 2017 or the ISO7810:2019 standard of December 2019;

[0052] - a pattern, for example a barcode or a QR code (for “Quick response” in Anglo-Saxon terminology), displayed by device 2, 22.

[0053] The communication interface 21 of the devices 2, 22 is further configured to receive identifiers, for example the first identifier, by the control unit 3 of the vehicle 4 and / or the internal reader 6, and transmit identifiers, for example the second identifier, to the control unit 3 of the vehicle 4 and / or the internal reader 6. The first identifier and the second identifier may be respectively the identifier specific to the vehicle 4 and the identifier specific to the device 2.

[0054] According to one embodiment, the communication interface 21 of the devices 2, 22 is configured to transmit identifiers, for example the first identifier and the second identifier, to the user terminal 5 by near-field communication. The first identifier being specific to the vehicle 4 and the second identifier being specific to the device 2.

[0055] According to another embodiment, the communication interface 21 of the devices 2, 22 is configured to transmit identifiers, for example the first identifier and the second identifier, to the user terminal 5 by optical reading, by the terminal 5, of a pattern representative of the first identifier and the second identifier and displayed by the device 2, the pattern being for example a bar code or a QR code.

[0056] The memory is configured to store the first identifier and the second identifier.

[0057] The user terminal 5 comprises at least: - a third memory (not shown); - a first communication interface 51;

[0058] - a second communication interface 52;

[0059] - a third communication interface 53; and

[0060] - a fourth communication interface 54.

[0061] The user terminal 5 may be a mobile terminal, for example of the “smartphone” type, or a fixed terminal, for example a computer.

[0062] According to one embodiment, the communication interface 51 of the user terminal 5 is configured to receive the first identifier and the second identifier transmitted by the device 2 by near-field communication, for example of the NFC or Bluetooth type. The first identifier being specific to the vehicle 4 and the second identifier being specific to the device 2.

[0063] According to another embodiment, the communication interface 51 of the terminal 5 is configured to receive the first identifier and the second identifier transmitted by the device 2 by optical reading, by the user terminal 5, of a pattern representative of the first identifier and the second identifier and displayed by the device 2, the pattern being for example a bar code or a QR code.

[0064] It is also provided that the communication interface 51 of the user terminal 5 is configured to receive identifiers transmitted by a second device 22 or by each device of a plurality of devices.

[0065] The second communication interface 52 of the user terminal 5 is configured to exchange data with the system 1.

[0066] The third communication interface 53 of the user terminal 5 is configured to exchange data with the control unit 3 of the vehicle 4. For example, the third communication interface 53 of the user terminal 5 is configured to transmit the second secret to the control unit of the vehicle.

[0067] The fourth communication interface 54 of the user terminal 5 is configured to transmit data to the internal reader 6, for example the second secret.

[0068] The memory of the user terminal 5 is configured to store data, for example the second secret. In particular, the memory is configured to store the pairing password transmitted by the system 1. In addition, the memory is configured to store the first identifier and the second identifier. It is also provided that the memory stores a plurality of identifiers.

[0069] The user terminal 5 may comprise a computer program product, for example a mobile telephone application, comprising code instructions executed by a processor of the user terminal 5 configured to control the communication interfaces 51, 52, 53, 54 of the user terminal 5 and the third memory of the user terminal 5.

[0070] The first secret and the second secret, for example, respectively, the password verifier and the pairing password, are transmitted by the system 1 comprising: - a database (not shown) configured to initially record a reference identifier specific to the vehicle 4, the first and second secrets associated with the reference identifier specific to the vehicle 4, then the identifier specific to the vehicle 4 and the identifier specific to the device 2 transmitted by the control unit 3 of the vehicle 4; and - a server (not shown) comprising: - a communication interface 11 configured to receive the first identifier and the second identifier transmitted by the user terminal 5; - a second communication interface 12 configured to transmit the first secret to the control unit 3 of the vehicle 4; and - a third communication interface 13 configured to receive the identifier specific to the vehicle 4 and the identifier specific to the device 2 transmitted by the control unit 3 of the vehicle 4.

[0071] The database may further be configured to store a plurality of secrets. It may also be configured to store the identifier specific to a second device 22 or several identifiers specific to each device of a plurality of devices.

[0072] The communication interface 11 can further be configured to receive several identifiers transmitted by the user terminal 5. For example, the identifier specific to the second device 22 or several identifiers specific to each device of a plurality of devices.

[0073] The server can also be configured to verify that there is a correspondence, in the database, between identifiers transmitted by the control unit 3 of the vehicle 4 stored in the database and identifiers transmitted by the user terminal 5 to the server of the system 1 and previously received by the user terminal 5 from the device 2.

[0074] In this case, the server further comprises a fourth communication interface 14 configured to transmit the second secret to the user terminal 5 provided that there is a correspondence, in the database, between the two identifiers transmitted by the control unit 3 of the vehicle 4 stored in the database and, respectively, the identifiers transmitted by the user terminal 5 to the server of the system 1 and previously received by the user terminal 5 from the device 2.

[0075] The second communication interface 12 can further be configured to transmit the first secret to the control unit 3 of the vehicle 4 provided that there is a correspondence, in the database, between the two identifiers transmitted by the control unit 3 of the vehicle 4 stored in the database and, respectively, the identifiers transmitted by the user terminal 5 to the server of the system 1 and previously received by the user terminal 5 from the device 2.

[0076] The server can also be configured to delete a correspondence between at least one of the two reference identifiers stored in the database of the system 1 and at least one of the first identifier and the second identifier received by a dissociation order, on the condition that a correspondence exists in the database, between at least one of the two reference identifiers stored in the database of the system 1 and at least one of the first identifier and the second identifier included in the dissociation order.

[0077] In this case, the server further comprises a second database configured to record the reference identifier before deleting the correspondence.

[0078] The fourth communication interface 14 is further configured to transmit an error message to the user terminal 5 in the event that the match does not exist in the database.

[0079] For example, the error message may invite the user to contact technical support for the vehicle 4 or the device 2.

[0080] The communication interface 11 is further configured to receive a dissociation order between the first identifier and the second identifier, the dissociation order association being issued by the user terminal 5.

[0081] The second communication interface 12 is configured to transmit a dissociation request to the control unit 3 of the vehicle 4 comprising: - information, intended for the control unit 3 of the vehicle 4, notifying that a deletion of said correspondence has been carried out in the database; and - a command from the control unit 3 of the vehicle 4 to dissociate the device 2, 22 and / or the user terminal 5 with the control unit of the vehicle 4.

[0082] For example, the command may comprise code instructions which, when executed by the control unit 3 of the vehicle 4, implement a deletion of the identifier specific to the device 2 and / or the identifier specific to a second device 22 and / or several identifiers specific to each device of a plurality of devices and of the first secret and implement a deactivation of the secure communication channel between said control unit 3 of the vehicle 4 and the user terminal 5

[0083] According to another embodiment, the dissociation request is issued by a push button 65 of the internal reader 6.

[0084] The system 1 may further comprise several interconnected servers.

[0085] The second secret may be a pairing password that can be recognized by the password checker. Methods

[0086] With reference to [Fig.4], a method jointly implemented by the system 1, the control unit 3 of the vehicle 4, the device 2 and the user terminal 5 comprises the following steps.

[0087] During a step E1, the device 2 transmits the identifier specific to the device 2 to the control unit 3 of the vehicle 4 and the control unit 3 of the vehicle 4 transmits the identifier specific to the vehicle 4 to the device 2.

[0088] During a step E2, the vehicle 4 is started for the first time.

[0089] During a step E3, the system 1 receives the identifier specific to the device 2 and the vehicle-specific identifier 4 transmitted by the control unit 3 of the vehicle 4.

[0090] During a step E4, a user of the vehicle 4 transmits via the user terminal 5 a request to the system 1 in order to start an attempt to pair the user terminal 5 with the vehicle 4, for example via the application of the automobile manufacturer of the vehicle 4.

[0091] At this stage, the user terminal 5 asks the user to bring the device 2 closer to the user terminal 5, for example by notifying him via the application by a message.

[0092] During a step E5, the device 2 transmits the identifier specific to the device 2 and the identifier specific to the vehicle 4 to the user terminal 5 via wireless communication requiring proximity between the device 2 and the user terminal 5, by for example by near field communication (NFC), or via optical reading by the user terminal 5 of a pattern representative of the identifiers and displayed by the device 2, the pattern being for example a bar code or a QR code.

[0093] During a step E6, the user terminal 5 transmits the identifier specific to the device 2 and the identifier specific to the vehicle 4 to the system 1.

[0094] During a step E7, the system 1 verifies the existence of a correspondence, in the database, between the two identifiers transmitted by the control unit 3 of the vehicle 4 stored in the database and, respectively, the identifiers transmitted by the user terminal 5 to the system 1, received by the user terminal 5 from the device 2 during the step E5.

[0095] In the case where the correspondence exists, the system 1 transmits during a step E8 the second secret associated with the pair of identifiers stored in the database to the user terminal 5.

[0096] Then, during a step E9, the first secret is transmitted by the system 1 to the control unit 3 of the vehicle 4.

[0097] The first secret may for example be the password verifier and the second secret the pairing password. In this case, the user terminal 5 transmits to the control unit 3 of the vehicle 4 via near field communication (NFC) a candidate password, the password verifier thus authorizing the establishment of the secure communication channel between the terminal 5 and the control unit 3 of the vehicle 4 provided that the candidate password transmitted by the user terminal 5 to the control unit 3 of the vehicle 4 corresponds to the pairing password transmitted by the system 1 to the user terminal 5.

[0098] If the verifier gives his authorization, the secure communication channel between the control unit 3 of the vehicle 4 and the user terminal 5 is established during a step E10.

[0099] During a step Eli, the user is invited, for example by receiving a notification on his terminal 5, to pair his terminal 5 with the vehicle 4. He can, for example, place his terminal 5 near the internal reader 6 of the vehicle 4 to carry out the pairing. By pairing, we mean a procedure for generating, sharing and storing cryptographic keys between the control unit 3 of the vehicle 4 and the user terminal 5, via the secure communication channel, in order to allow the user terminal 5 to be able to interact with the vehicle 4 (for example, to allow the user terminal 5 to be able to control different components of a vehicle, for example, opening the doors, or starting the engine).

[0100] The user terminal 5 is paired with the vehicle 4.

[0101] The user can then interact with the various components of the vehicle 4 in near-field communication. For example, he can bring his user terminal 5 or his device 2 of the handle to unlock the doors of the vehicle 4 then, when he takes his place in the passenger compartment, he can place his terminal 5 in or near the internal reader 6 of the vehicle 4 to start the engine.

[0102] In the case where the correspondence does not exist between the identifiers, during the verification carried out in step E7, the system 1 transmits, during a step E71, to the user terminal 5 an error message instead of the second secret, the error message indicating that the user terminal 5 is not authorized to communicate with the vehicle 4, or to initiate the establishment of a secure channel.

[0103] With reference to [Fig.5], the user can pair several devices to the vehicle 4.

[0104] During a step E100, the system 1 receives a notification sent by the control unit 3 of the vehicle 4 informing the system 1 of a pairing request between a second device 22 and the control unit 3 of the vehicle 4.

[0105] Upon receipt of the notification, the system 1 transmits to the user terminal 5 a second notification inviting it to accept the pairing request during a step E101.

[0106] During a step E102, the system 1 receives a response to the second notification by the user terminal 5.

[0107] The response may for example be a request transmitted by the user terminal indicating whether the pairing request is accepted or not.

[0108] In the case where the response indicates that the pairing request is accepted, the system 1 transmits to the control unit 3 of the vehicle 4 an authorization of the pairing request during a step El 13.

[0109] The control unit 3 of the vehicle 4 is capable of receiving the specific identifier of the second device 22 transmitted by the second device 22.

[0110] During a step E1 14, the system 1 transmits to the user terminal 5 a message indicating to the user to pair the second device 22.

[0111] In an alternative embodiment, the vehicle control unit 4 displays a message to the user to indicate to him to pair the second device 22.

[0112] During a step El 15, the user places the second device 22 near the control unit 3 of the vehicle 4.

[0113] During a step E1 16, the identifier specific to the second device 22 is transmitted to the control unit 3 of the vehicle 4, to be stored there, and the control unit 3 of the vehicle 4 transmits the identifier specific to the vehicle 4 to the second device 22, to be stored there, via a wireless communication requiring proximity between the second device 22 and the control unit 3, for example by a near field communication (NFC). In an alternative embodiment, the transmission of the identifier specific to the second device 22 is carried out by a optical reading, by the control unit 3 of the vehicle 4, of a pattern representative of the first identifier and displayed by the second device 22, the pattern being for example a bar code or a QR code.

[0114] During a step El 17, the control unit 3 of the vehicle 4 transmits to the system 1 the identifier specific to the second device 22 and the identifier specific to the vehicle 4.

[0115] In the case where the response indicates that the pairing request is refused, the system 1 transmits, to the control unit 3 of the vehicle 4, a message refusing the pairing request during a step El23.

[0116] In this case, the second device 22 is not paired with the vehicle 4.

[0117] With reference to [Fig.6], the user can further request a second device 22 directly from the manufacturer according to the following steps.

[0118] During a step E201, the system 1 receives a command from a second device 22 distinct from the device 2 by the user.

[0119] During a step E202, the system 1 transmits the command and optionally the vehicle-specific identifier to a device supplier.

[0120] For example, the command may be transmitted in the form of a request by system 1.

[0121] Thus, the second device 22 storing its own device identifier 22 and / or displaying a pattern of its own device identifier 22 is sent by the device supplier to the user. Optionally, the sent device 22 also stores the identifier specific to the vehicle 4 and / or displays a pattern of the identifier specific to the vehicle 4. In an alternative embodiment, the pattern displayed by the second device 22 is representative of the identifier specific to the device 22 and the identifier specific to the vehicle 4 in the form, for example, of a bar code or QR code.

[0122] Then, steps E100, E101, E102 and E113 to E117 can be implemented by the user to pair the second device 22 with the vehicle 4.

[0123] During an optional step E203, the device provider records in the database of the system 1 the identifier specific to the second device 22.

[0124] With reference to [Fig.7] the user can delete the pairing of the user terminal 5 and / or the device 2 to the vehicle 4 according to the following steps.

[0125] During a step E301, the system 1 receives a dissociation order between the first identifier and the second identifier, the dissociation order being sent by the user terminal 5.

[0126] For example, the order can be issued and transmitted by the user terminal 5, to the system 1, in the form of a request comprising at least one of the first identifier and the second identifier.

[0127] According to another embodiment, the order can be issued by the push button 65 of internal drive 6.

[0128] In the case where a correspondence between at least one of the two reference identifiers stored in the database of the system 1 and at least one of the first identifier and the second identifier received by the request exists in the database, the correspondence in the database is deleted during a step E311.

[0129] Then the system 1 transmits, during a step E312, a dissociation request to the control unit 3 of the vehicle 4 to inform the control unit 3 of the vehicle 4 that a deletion of said association has been carried out in the database and to command the control unit 3 of the vehicle 4 to dissociate the device 2 and / or the user terminal 5 with the control unit of the vehicle 4.

[0130] During a step E313, the control unit 3 of the vehicle 4 deletes the identifier specific to the device 2, so that said device 2 can no longer be recognized by said control unit 3 of the vehicle 4, and deletes the first secret.

[0131] During a step E314, the control unit deactivates the secure communication channel between said control unit 3 of the vehicle 4 and the user terminal 5.

[0132] Thus, the control unit 3 of the vehicle 4 no longer processes commands, for example requests, emanating from the user terminal 5 and / or the device 2.

[0133] The deletion may be preceded by a step E300 in which a backup of the reference identifier corresponding to the first identifier is carried out in a second database different from the database.

[0134] In the case where the correspondence between at least one of the two reference identifiers stored in the database of the system 1 and at least one of the first identifier and the second identifier received by the dissociation request does not exist in the database, then the system 1 transmits an error message to the user terminal 5 during a step E321. For example, the error message may invite the user to contact technical support for the vehicle 4 or the device 2.

Claims

Claims

1. A method for initializing pairing comprising the following steps: - reception, by a system (1), of a first identifier and a second identifier transmitted by a user terminal (5), the first identifier being specific to a vehicle (4) and the second identifier being specific to a device (2), the first identifier and the second identifier having been previously transmitted to the user terminal (5) by the device (2) by wireless communication requiring proximity between the user terminal (5) and the device (2), - verification by the system (1) of the existence, in a database, of a correspondence between two reference identifiers stored in the database corresponding respectively to the first identifier and the second identifier, - provided that said correspondence exists in the database, transmission by the system (1): - of a pairing password to the user terminal (5),- from a verifier to a control unit (3) of the vehicle (4), the verifier being configured to authorize establishment of a secure communication channel between the user terminal (5) and the control unit (3) of the vehicle (4) provided that a candidate password transmitted by the user terminal (5) to the control unit (3) of the vehicle (4) corresponds to said transmitted pairing password.,

2. Method according to claim 1, further comprising steps of: - reception, by the system (1), of the two reference identifiers, the two reference identifiers being transmitted by the control unit (3) of the vehicle (4), - storage of the two reference identifiers in the database after their reception.

3. Method according to any one of the preceding claims, further comprising the following steps: - reception, by the system (1), of a dissociation order between the first identifier and the second identifier, the dissociation order being issued by the user terminal (5) and comprising at least one of the first and second identifiers; - provided that a correspondence between at least one of the two reference identifiers stored in the database of the system (1) and at least one of the first identifier and the second identifier included in the dissociation order, exists in the database, deletion of the correspondence in the database; and - transmission by the system (1) of a dissociation request to the control unit (3) of the vehicle (4), said request being configured to inform the control unit (3) of the vehicle (4) that a deletion of said correspondence has been carried out in the database and to command the control unit (3) of the vehicle (4) to dissociate the device (2) and / or the user terminal (5) from the control unit (3) of the vehicle (4), the control unit (3) being configured to, after receiving the dissociation request from the system (1), not process commands emanating from the device (2) and / or the user terminal (5).

4. Method according to claim 3, further comprising a step of: - saving the reference identifier corresponding to the first identifier in a second database different from the database before deleting the correspondence in the database.

5. Method according to any one of the preceding claims, further comprising the following steps: - reception by the system (1) of a command from a second device (22) distinct from the device (2); - transmission, by the system (1) and to a device supplier, of the command.

6. Method according to any one of the preceding claims, further comprising the following steps: - receiving a notification issued by the control unit (3) of the vehicle (4), the notification informing the system (1) of a pairing request between a second device (22) and the control unit (3) of the vehicle (4), the second device (22) being distinct from the device (2); - upon receipt of said notification, transmission to the user terminal (5) by the system (1) of an invitation to accept the pairing request; - receiving by the system (1) a response to the invitation, the response indicating that the pairing request is accepted or not; and - transmission to the control unit (3) of the vehicle (4), by the system (1), of an authorization or a refusal of the pairing request depending on said response.

7. Method according to one of the preceding claims, in which the transmission of the first identifier and the second identifier to the user terminal (5) comprises: - a near field communication (NFC), or - an optical reading, by the user terminal (5), of a pattern representative of the first and second identifiers and displayed by the device (2), the pattern being for example a bar code or a QR code.

8. Method according to one of the preceding claims, in which the device (2) is a smart card.

9. System (1) comprising: - a communication interface (11) configured to receive a first identifier and a second identifier transmitted by a user terminal (5), the first identifier being specific to a vehicle (4) and the second identifier being specific to a device (2), the first identifier and the second identifier having been previously transmitted to the user terminal (5) by the device (2) by wireless communication requiring proximity between the terminal (5) and the device (2), the system (1) being configured to verify the existence, in a database, of a correspondence between two reference identifiers stored in the database corresponding respectively to the first identifier and the second identifier;and - a communication interface (12, 13) configured to transmit: - a pairing password to the user terminal (5), - a verifier to a control unit (3) of the vehicle (4), provided that said correspondence exists in the database, the verifier being configured to authorize an establishment of a secure communication channel between the terminal (5) and the control unit (3) of the vehicle (4) provided that a candidate password transmitted by the user terminal (5) to the control unit (3) of the vehicle (4) corresponds to the pairing password transmitted.;

10. A computer program product comprising first program code instructions for controlling the execution of the steps of a first method according to any one of claims 1 to 8, when the first code instructions are executed by a system (1); and optionally second program code instructions for controlling the execution of the steps of a second method, when the second code instructions are executed by a user terminal (5), the second method comprising: - reception, by the user terminal (5), of the first identifier and the second identifier transmitted by the device (2), - transmission, by the user terminal (5), to the system (1), of the first identifier and the second identifier received.

Images