Systems and methods for pairing an offline key fob with a vehicle using vehicle connectivity

Abstract

The present disclosure provides "Systems and methods for pairing an offline key fob with a vehicle using vehicle connectivity." A system includes a vehicle system comprising one or more computing devices. The vehicle system is configured to, in response to receiving a secret key pairing request to pair an offline key fob with a vehicle, identify a user as an authorized user of the vehicle using an authorized action associated with the user, in response to the user being the authorized user, verify that the offline key fob is authorized to pair with the vehicle using authentication information provided by the offline key fob using a short-range communication protocol, transmit a device payload to the offline key fob using the short-range communication protocol, and pair with the offline key fob using the device payload to enable the offline key fob to control the vehicle.

Description

Technical Field

[0001] This disclosure generally relates to pairing a key fob with a vehicle, and more specifically, to pairing an offline key fob with a vehicle. Background Technology

[0002] The key fob can be paired with a vehicle to enable the key fob to access or control vehicle features, such as, but not limited to, remote start, unlocking / locking the vehicle doors and / or opening the vehicle's rear doors. To pair the key fob, the user can input an actuation to one or more defined buttons provided on the key fob to put the key fob into pairing mode. Summary of the Invention

[0003] In some aspects, this disclosure relates to a system including a vehicle system, the vehicle system including one or more computing devices configured to: in response to receiving a key pairing request to pair an offline key fob with a vehicle, identify a user as an authorized user of the vehicle using an authorization action associated with a user; in response to the user being an authorized user, verify that the offline key fob is authorized to pair with the vehicle using authentication information provided by the offline key fob using a short-range communication protocol; transmit a device payload to the offline key fob using the short-range communication protocol; and pair the device payload with the offline key fob to enable the offline key fob to control the vehicle.

[0004] In another aspect, this disclosure relates to a non-transitory computer-readable medium comprising instructions for pairing an offline key fob with a vehicle, the instructions performing operations when executed by one or more processors, including: identifying a user as an authorized user of the vehicle using an authorization action associated with a user in response to receiving a key pairing request to pair the offline key fob with the vehicle; verifying that the offline key fob is authorized to pair with the vehicle using authentication information provided by the offline key fob using a short-range communication protocol in response to the user being an authorized user; transmitting a device payload to the offline key fob using the short-range communication protocol; establishing a secure channel with the offline key fob using an encryption key in response to the offline key fob verifying the device payload; and pairing the offline key fob with the secure channel and the device payload to enable the offline key fob to control the vehicle.

[0005] In another aspect, this disclosure relates to a method for pairing an offline key fob with a vehicle. The method includes: in response to receiving a key pairing request to pair the offline key fob with the vehicle, the vehicle system identifies a user as an authorized user of the vehicle using an authorization action associated with a user; in response to the user being an authorized user, the vehicle system verifies that the offline key fob is authorized to pair with the vehicle using authentication information provided by the offline key fob using a Short Range Protocol (SLP), wherein the authentication information includes at least one of an identity certificate, a root certificate, or a private key; the vehicle system transmits the key fob pairing request to a remote server to obtain approval for pairing with the offline key fob; in response to the remote server approving the pairing, the vehicle system decrypts a signed payload message to obtain a device payload from the remote server; the vehicle system transmits the device payload to the offline key fob using the SLP; in response to the offline key fob verifying the device payload, establishes a secure channel with the offline key fob using an encryption key; and pairs the offline key fob with the secure channel, one or more shared data, and the device payload to enable the offline key fob to control the vehicle. Attached Figure Description

[0006] Figure 1 This is an example vehicle system and an offline key fob to be paired with said vehicle system.

[0007] Figure 2 This is an example block diagram of the vehicle system.

[0008] Figure 3A This is an example flowchart of the key pairing process for an offline keychain.

[0009] Figure 3B yes Figure 3A A follow-up view of an example flowchart of the key pairing process.

[0010] Figure 3C yes Figure 3B A follow-up view of an example flowchart of the key pairing process.

[0011] Figure 4 This is an example flowchart of another key pairing process for offline keychains. Detailed Implementation

[0012] Detailed embodiments of the invention are disclosed herein as needed; however, it should be understood that the disclosed embodiments are merely examples of the invention that can be embodied in various forms and alternative forms. The drawings are not necessarily drawn to scale; some features may be enlarged or minimized to show details of specific components. Therefore, the specific structural and functional details disclosed herein are not to be construed as limiting, but only as representative bases for teaching those skilled in the art to employ the invention in various ways.

[0013] Some technologies used to pair key fobs with vehicles may include security features designed to limit third-party attacks. For example, some pairing technologies use short-range, low-frequency radio and proprietary protocols, but these connections may lack any encryption or authentication to protect pairing data. Other pairing technologies may rely on a static personal identification number (PIN) or password embedded in the key fob to authenticate vehicle pairing, but this can raise concerns about strong short PINs or password leaks from dealer systems that have access to all values. Adding internet connectivity to the key fob can provide a direct interface for certificate management and pairing approval, but internet connectivity can increase the complexity of the key fob, component costs, and the electrical power required to power it.

[0014] This disclosure generally relates to a pairing technique for offline key fobs that uses the vehicle's connected telematics features and secure messaging payload to pair the offline key fob with the vehicle. That is, it supplements the offline key fob's connectivity through the vehicle or other agent to bypass complex key fobs with internet connectivity and / or key fobs using PIN or password connections.

[0015] refer to Figure 1 and Figure 2 The offline key fob 100 is paired with the vehicle 102 to provide access to the vehicle 102 using the offline key pairing process described herein (which may be referred to as the key pairing process). In some embodiments, the key pairing process is performed using a vehicle support system 104 for authenticating the offline key fob 100 and the vehicle 102. In other embodiments, the key pairing process is performed without the vehicle support system 104 and is implemented between the vehicle 102 and the offline key fob 100.

[0016] In some respects, the offline key fob 100 is a device that provides a narrow set of functions (e.g., remote start, unlocking / locking doors, opening / closing rear doors, alarm on / off). The offline key fob 100 also lacks internet connectivity and, in some instances, can be paired with a single vehicle. In some variations, the offline key fob 100 may include a limited user input-output interface, such as a few buttons or a touchpad, but no screen. In non-limiting examples, the offline key fob 100 may be a near-field communication (NFC) proximity access card, a radio frequency identification (RFID) proximity access card, and / or a wearable device with NFC or RFID functionality designed for vehicle access.

[0017] In some aspects, the offline key fob 100 includes a communication module 110, a control module 112, and a button 114 to control defined features of the vehicle 102. The communication module 110 may be configured to exchange signals using one or more short-range communication protocols (such as, but not limited to, radio frequency communication, NFC, Bluetooth-like communication, and / or ultra-wideband (UWB) communication). In a non-limiting example, the offline key fob 100 includes hardware and software components such as an antenna, memory, and an integrated chip configured to transmit and / or receive message signals using short-range communication protocols.

[0018] In one embodiment, the communication module 110 is configured to include a pairing module 116, which is configured to pair the offline key fob 100 with the vehicle 102 according to the offline key pairing process of this disclosure. In some aspects, the pairing module 116 includes: a microprocessor configured to execute a pairing routine; and a memory configured to store authentication information for authenticating the offline key fob 100. In a non-limiting example, the authentication information may include an identity certificate, a root certificate, and / or a private key. The authentication information is stored by the offline key fob 100 prior to pairing (e.g., during the manufacture of the offline key fob 100).

[0019] Control module 112 is configured to control features of vehicle 102 based on the actuation of button 114 once offline key fob 100 is paired with vehicle 102. For example, once paired, control module 112 transmits commands to start, lock, or unlock the vehicle based on the actuation of button 114. Control module 112 may include a microprocessor and a memory for storing instructions executable by the microprocessor to command vehicle 102 to perform control features in response to the actuation of the corresponding button 114.

[0020] Although the pairing module 116 is provided with the communication module 110, the pairing module 116 can be adapted to be part of the offline keychain 100 in various suitable ways, including but not limited to being part of the control module 112 or a separate module. Additionally, the offline keychain 100 can include a streamlined structure in which the communication module 110, the control module 112, and the pairing module 116 share components such as a microprocessor and / or memory, and do not need to have separate components.

[0021] Vehicle 102 can be any suitable vehicle 102 with selected features controllable by a remote key fob, such as a car, truck, and / or motorcycle. In a non-limiting example, vehicle 102 includes vehicle system 200, which includes infotainment system 202 and communication system 203. While specific systems have been identified, vehicle 102 may include other systems, such as vehicle drive systems for controlling drive operations of vehicle 102 (e.g., remote start, powertrain control, etc.) and / or body systems for controlling and monitoring structural components of the vehicle body (e.g., locking / unlocking doors, opening the trunk, etc.).

[0022] The infotainment system 202 is configured to exchange information with a user and provide access to various assistive features, such as creating user profiles and / or pairing key fobs. In some embodiments, the infotainment system 202 includes one or more user interface devices 204, a user profile module 206, and a key fob module 208. The infotainment system 202 may include one or more microprocessors and memory for storing instructions that can be executed by the microprocessors to perform the operations described herein, including those of the user profile module 206 and the key fob module 208.

[0023] User interface device 204 is configured to communicate with one or more users of vehicle 102 by providing information to and receiving information from users. In a non-limiting example, user interface device 204 includes: audio devices (e.g., speakers and / or microphones), display devices (e.g., head-up displays and / or liquid crystal displays with touchscreens) and / or buttons / knobs.

[0024] User profile module 206 is configured to acquire and store data related to the authorized user of vehicle 102. In a non-limiting example, the user can be the vehicle owner, and user profile module 206 can receive user information related to the vehicle owner from vehicle support system 104, which stores information related to vehicle 102 and the authorized user as part of the vehicle account. User information may include a username, a unique account associated with the authorized user and vehicle 102, a unique password set by the user for logging into the vehicle account, and / or operational preferences set by the authorized user, such as, but not limited to, optional settings for key fob pairing.

[0025] In some implementations, the authorized user during the key pairing process can be, for example, a technician at the manufacturing facility of vehicle 102 or the service center of vehicle 102. The technician can use security tools to pair the offline key fob 100 for authenticating the technician using various technologies such as unique passwords, user-associated identification information, and / or biometric verification.

[0026] The key fob module 208 is configured to initiate a pairing process for the offline key fob 100. For example, the option to pair the key fob with the vehicle 102 may be presented to the user by the infotainment system 202 as part of settings options on a graphical user interface. After selecting the option to pair the key fob, the key fob module 208 is configured to identify the user as an authorized user of the vehicle 102 using an authorization action associated with the user. In a non-limiting example, the selected authorization action may include: receiving a message from one or more key fobs already paired with the vehicle 102; obtaining and verifying login credentials associated with the authorized user; confirming a one-time password sent to and entered by the user; or biometric authentication (e.g., fingerprint, facial recognition). Using the expected response to the authorization action, if the expected response matches the input of the authorization action, the key fob module 208 is configured to identify the user as an authorized user.

[0027] In response to the user being an authorized user, the key fob module 208 is also configured to use authentication information from the offline key fob 100 to verify that the offline key fob 100 is authorized to pair with the vehicle 102. For example, the authorized user can be instructed to place the offline key fob 100 at a designated location 132, allowing the key fob module 208 to provide authentication information at that location using a short-range communication protocol. In some aspects, if the authentication information is verified, and if the vehicle support system 104 is able to authenticate the vehicle and the offline key fob 100, the key fob module 208 transmits a key fob pairing request to the vehicle support system 104 to obtain the device payload. Using the device payload, the key fob module 208 continues pairing with the offline key fob 100 to enable the offline key fob 100 to control the vehicle 102. Details regarding the pairing process of the offline key fob 100, in relation to the offline key fob 100, the vehicle 102, and the vehicle support system 104 will be discussed later. Figures 3A to 3C Describe it.

[0028] The communication system 203 is configured to communicate with various external devices / systems, such as, but not limited to, the offline key fob 100 and the vehicle support system 104. Therefore, among other components, the communication system 203 may also include: a telematics control unit (TCU) configured to establish communication according to a vehicle-to-the-world (V2X) protocol; a Bluetooth transceiver for communicating with devices using the Bluetooth protocol; and a Global Navigation Satellite System (GNSS) receiver. In some embodiments, the communication system 203 includes a short-range communication transceiver for communicating with devices such as the offline key fob 100 at a designated location 132 on the vehicle 102 or for portable computing. For example, the designated location 132 is provided in the passenger compartment and is equipped with an NFC transceiver and / or a UWB transceiver for communicating with devices.

[0029] Vehicle support system 104 is configured to manage vehicle accounts, including storing information related to authorized users of a vehicle (e.g., vehicle 102) and authenticating the corresponding vehicle and requesting key fobs to be paired with the vehicle. In some aspects, vehicle support system 104 includes a remote server configured to perform the functions described herein and communicate with external systems or devices including vehicle 102 using various communication protocols (including but not limited to cellular communication). In some aspects, vehicle support system 104 includes a vehicle account module 134 and a key fob authentication module 136.

[0030] Vehicle account module 134 is configured to generate, store, and manage vehicle account records that provide information related to vehicle 102 and one or more authorized users of vehicle 102. In a non-limiting example, during the boarding process, vehicle account module 134 is configured to associate a user (e.g., vehicle owner) with vehicle 102 using verification information (such as vehicle ownership or other legal documents). Users can use various technologies to perform the boarding process, including but not limited to: interfacing with vehicle 102's infotainment system 202; software applications supported by vehicle support system 104 and executed by portable computing devices (e.g., mobile phones, tablets); or software applications interfacing with websites associated with vehicle support system 104. Once completed, the vehicle owner is provided as an authorized user of vehicle 102 and is allowed to manage the keys to vehicle 102. In some aspects, the vehicle owner can identify other users as authorized users for managing the keys to vehicle 102.

[0031] The vehicle account module 134 is also configured to store preferences or settings to be associated with an authorized user. For example, the authorized user can select one or more authorization actions, and, if appropriate, can select the expected response from the authorized user. In another example, the authorized user can select optional verification (e.g., secondary verification) for pairing the key fob. In a non-limiting example, optional verification includes: requesting explicit approval from the authorized user 301 (e.g., owner, operator, administrator, etc.) via a mobile software application or web portal supported by the vehicle support system 104; delaying the approval response message for a selected period of time; canceling the pairing attempt; a cooling-off period that allows the authorized user 301 to take corrective actions before the offline key fob 100 can be activated; and a freezing feature that prohibits all pairing requests regardless of whether the vehicle 102 and / or the vehicle support system 104 have already authenticated the offline key fob 100, the authorized user 301, or the vehicle 102, thereby causing the key pairing process 300 to terminate.

[0032] The key fob authentication module 136 is configured to perform one or more authentication operations as part of the key fob pairing process of this disclosure. As detailed herein, the key fob authentication module 136 is configured to verify a pairing request from vehicle 102 by authenticating vehicle 102 and offline key fob 100. Once verified, the key fob authentication module 136 is configured to transmit an encrypted device payload message to vehicle 102, which is used by vehicle 102 to initiate a pairing sequence with offline key fob 100.

[0033] refer to Figure 3A , Figure 3B and Figure 3C An example key pairing process 300 is provided, performed by an offline key fob 100 with a pairing module 116, a vehicle 102 with a key fob module 208, and a vehicle support system 104 with a key fob authentication module 136.

[0034] In some implementations, when user 301 initiates a pairing request to add offline key fob 100, key pairing process 300 begins at operation 302, which can be requested using infotainment system 202. In some variations, key fob module 208 is configured to perform a pre-adjustment check to verify that it is in the appropriate condition for pairing with offline key fob 100. For example, the pre-adjustment check verifies that vehicle 102 is in park rather than in motion; ignition or power-on status is in the appropriate mode (e.g., on); the 12V battery is fully charged; modem authorization and vehicle owner login are completed (e.g., checking whether infotainment system 202 stores information related to the vehicle owner); internet connectivity is available; and / or valet parking or other service modes are not enabled.

[0035] At operation 304, the key pairing process 300 is configured to verify the requesting user 301 as an authorized user. That is, at operation 304A, the key fob module 208 requests the user 301 to provide an authentication action via one or more user interface devices 204, and at operation 304B, the user 301 provides the authentication action.

[0036] Once an authentication action is received, the key fob module 208 is configured to verify user 301 as an authorized user in response to the expected response of the authentication fulfillment action, or in other words, to satisfy the authentication policy. For example, a one-time password entered by user 301 matches a password of the key fob module 208 or a third-party entity; biometric input matches a stored biometric measurement; a message is received from a key fob already paired with vehicle 102; and / or user 301 confirms a pop-up message on a portable device associated with user 301.

[0037] If the authentication action does not meet the associated authentication policy, the key pairing process 300 ends, and user 301 is provided with a message indicating that user 301 is not authorized to add the offline key fob 100. In some service use cases where user 301's authentication cannot be verified, an authorized vehicle diagnostic tool can be used instead to provide initial authentication for starting the key learning process.

[0038] If user 301 is verified as an authorized user, the key fob module 208 will receive a message from the offline key fob 100. For example, at operation 306, the key fob module 208 is configured to request the authorized user to provide the offline key fob 100 at a specified location 132 to communicate with the offline key fob 100.

[0039] Once received at designated location 132 in operation 308, the key pairing process 300 performs offline key fob authentication at operation 310. That is, at operation 310A, the offline key fob 100 transmits the authentication information to the offline key fob module 208 at designated location 132 via a short-range communication protocol.

[0040] Using the authentication information, at operation 310B, the key fob module 208 is configured to verify the identity of the offline key fob 100 and use the identity certificate and root certificate to verify that the offline key fob 100 is authentic. The key fob module 208 is configured to authenticate the offline key fob 100 using a challenge-response handshake, during which the offline key fob module transmits a challenge to the offline key fob 100 in the form of a random value (e.g., operation 310C). At operation 310D, the offline key fob 100 processes the random value using a stored algorithm and private key or password via the pairing module 116 to generate a challenge response. Then, at operation 310E, the offline key fob 100 transmits the challenge response to the vehicle 102, and at operation 310F, the key fob module 208 verifies the challenge response. If the identity and authenticity of the offline key fob 100 are verified, the key fob module 208 saves the authentication information and records the status of the offline key fob 100 as pending.

[0041] If the offline key fob 100 cannot be recognized and / or authenticated, the key fob module 208 ends the key pairing process 300 and notifies the user 301 that the offline key fob 100 cannot be authenticated.

[0042] Following vehicle certification 102, the offline key fob 100 is further certified by the vehicle support system 104. (Reference) Figure 3BIn operation 311, the key fob module 208 transmits a key fob pairing request to the vehicle support system 104 via the communication system 203. In some aspects, the key fob pairing request is an encrypted telematics message requesting approval to pair with the offline key fob 100. The key fob pairing request may include information such as, but not limited to: the identity certificate of the offline key fob 100; the device type associated with the offline key fob 100 (e.g., the device type may include, for example, a key fob, card, or wearable device); the versions of the hardware and software employed by the offline key fob 100; and / or available diagnostic alerts shared by the offline key fob 100 and the vehicle 102 during pairing. The key fob pairing request may also include details of the vehicle 102, such as, but not limited to: the identity certificate or other unique identifier of the vehicle 102; the hardware and software versions of the vehicle 102; and / or any diagnostic alerts or vehicle status values.

[0043] In an implementation where the key fob pairing request is encrypted, at operation 312, the key fob authentication module 136 of the vehicle support system 104 is configured to have an appropriate key to decrypt telematics messages and access the information.

[0044] Using the information from the key fob pairing request, the key fob authentication module 136 is configured to perform a verification process between the offline key fob 100 and the vehicle 102 at operation 314. In a non-limiting example, the verification process for the offline key fob 100 includes: verifying the identity certificate of the offline key fob 100 as authentic using the root certificate; confirming, for example, that the identity certificate of the offline key fob 100 has not been revoked or otherwise invalidated using information from the manufacturer of the offline key fob 100; and / or verifying that the offline key fob 100 is not marked as lost or stolen in a database supported by a third party (e.g., the third party could be the key fob manufacturer and / or dealer).

[0045] At operation 314, the key fob authentication module 136 can perform similar checks on vehicle 102. For example, the key fob authentication module 136 verifies the vehicle 102's identity certificate and revocation status; uses information, for example, from the vehicle account module 134 to confirm whether the vehicle 102 has completed owner login; and verifies that vehicle 102 has not been marked as stolen in the database.

[0046] If either the verification associated with the offline key fob 100 and / or the vehicle 102 fails to be verified, the key fob authentication module 136 will transmit a rejection response as a telematics message to the vehicle 102 to notify the user 301 that the pairing process may not be completed. Figure 3B (Not shown in the image). In some embodiments, any pending data stored by vehicle 102 is also deleted.

[0047] If verification is successful, at operation 316, the key fob authentication module 136 generates a signed device payload. The device payload may include information used to authenticate vehicle 102 and establish a secure channel. The information in the device payload may include the vehicle 102's identity certificate; a public key or credential for a key exchange (Pake) protocol used for cryptographic authentication; a counter or server approval timestamp used to determine payload freshness; restrictions on the interfaces through which offline key fob 100 can communicate with vehicle 102; the radio technologies and versions supported by vehicle 102; and / or a list of mutually supported protocol versions.

[0048] At operation 318, the key fob authentication module 136 encrypts the signed device payload and transmits it to the vehicle 102 as an encrypted pairing response (e.g., an encrypted signed payload message). The encrypted pairing response may also include information indicating that the pairing request has been approved.

[0049] In some aspects, it may be necessary to wait for vehicle 102 to start, which may prompt you to put the pending key back onto the vehicle's internal NFC reader.

[0050] In some respects, because the offline key fob 100 does not have a connection to the vehicle support system 104 (e.g., an internet connection), the offline key fob 100 may not receive timely software updates (including updates to the public key) to verify the payload signature when the vehicle support system 104 can replace the signing key associated with it. To allow the vehicle support system 104 to freely generate new signing keys, the device payload includes a certificate of the current signing key used by the vehicle support system 104. In a non-limiting example, the payload and signature can be provided to the certificate using the Cryptographic Message Syntax (CMS) defined in Request for Comments (RFC) 5652.

[0051] The offline key fob 100 may later be able to use the root certificate already supplied to it to verify the authenticity of any new signing key certificate. Additionally, the offline key fob 100 can track the latest received valid start time within the signing key certificate to "revoke" all previous signing key certificates containing older timestamps (e.g., NotBefore timestamps) without using a large revocation list, a continuously running real-time clock consuming battery power, and / or active connectivity with the certificate management system supported by the vehicle support system 104.

[0052] In some respects, there may be an indefinite delay between vehicle 102 providing a key fob pairing request to vehicle 102 and receiving a pairing approval response from vehicle support system 104, allowing vehicle 102 to shut down and / or offline key fob 100 to be removed from designated location 132. In this case, vehicle 102 waits until the next time vehicle 102 is started to pair with offline key fob 100. If offline key fob 100 is no longer at designated location 132 and is not yet ready to complete pairing, infotainment system 202 may indicate via user interface device 204 that pairing approval has been received and provide instructions to place offline key fob 100 back at designated location 132.

[0053] Using the device payload, vehicle 102 and offline key fob 100 perform pairing process 320. In some aspects, key fob module 208 of vehicle 102 is configured to decrypt a message containing the device payload using an associated key and, at operation 320A, provide the device payload with the vehicle certificate to offline key fob 100. Pairing module 116 of offline key fob 100 is configured to perform a series of verifications at 320B. In a non-limiting example, offline key fob 100 is configured to verify the signature certificate, root certificate, and payload signature of vehicle support system 104 already supplied to offline key fob 100, and / or obtain vehicle pairing data associated with the vehicle (e.g., certificate, public key, PAKE credential, etc.).

[0054] In some respects, the offline key fob 100 may reject the device payload in response to failure to meet one or more authentications, or if a freshness value (e.g., a counter or date / time) indicates an old or replay message from a different vehicle no longer authorized to pair with the offline key fob 100. In the absence of authentication, the offline key fob 100 transmits a message indicating that pairing is unauthenticated and terminates the pairing process. Figure 3C (Not shown in the image).

[0055] If all verifications pass, at operation 320C, the offline key fob 100 instructs the vehicle 102 to continue the handshake for establishing a secure channel. Various technologies and protocols can be used to create a secure channel in a manner that provides mutual authentication, forward secrecy, and replay protection, such as the C(2e, 2s, Elliptic Curve Cryptography (ECC) Computational Diffie-Hellman (CDH)) technology from SP800-56A and the SPAKE2 protocol drafted as RFC 9382. For example, at operations 320D and 320E, the pairing module 116 of the offline key fob 100 and the key fob module 208 of the vehicle 102 respectively generate temporary keys (e.g., encryption keys), and at operation 320F, a temporary Diffie-Hellman handshake is performed to establish the secure channel.

[0056] After the handshake between Operation 320D and Operation 320E, a secure channel (Operation 320G) is established, and the secure channel itself can borrow from existing protocols to encrypt and authenticate all exchanged session data, such as Transport Layer Security (TLS) or GlobalPlatform's CP03.

[0057] Through this secure channel, at operation 320H, vehicle 102 and offline key fob 100 can share any data required for successful pairing. Shared data may include, but is not limited to: hardware and software information, supported radio capabilities, selected protocol version, keys and initial rolling code values ​​for remote commands, keys and data for performing out-of-band Bluetooth pairing, and data required to set up additional radio interfaces. Vehicle 102 and offline key fob 100 can also provide confirmation values ​​and can also send proofs via the secure channel to verify the successful delivery, export, and storage of exchanged data.

[0058] Once the pairing data has been successfully exchanged, the key fob module 208 notifies the pairing module 116 of pairing completion at operation 320I. The pairing module 116 stores data related to vehicle 102 at operation 320J and transmits a pairing completion message to vehicle 102 at operation 320K. At operation 320L, vehicle 102 closes the secure channel by discarding all temporary keys.

[0059] At operation 322, the key fob module 208 stores data associated with the offline key fob 100 and sets the status of the offline key fob 100 to active. In some embodiments, at operation 324, the key fob module 208 notifies an authorized user by using one or more user interface devices 204 and providing a message indicating that pairing is complete and the offline key fob 100 is activated. At operation 326, the key fob module 208 may also transmit a telematics message indicating successful pairing to the vehicle support system 104.

[0060] In some variations, the key pairing process 300 may include the vehicle support system 104 checking and performing one or more optional verifications enabled by the authorized user, as described above. For example, refer to Figure 3B At operation 350, the key fob authentication module 136 performs an optional verification process (e.g., secondary verification). At operation 350A, the key fob authentication module 136 determines whether to perform additional verification based on information provided in the vehicle account associated with the vehicle. At operation 350B, the key fob authentication module 136 performs enabled optional verification.

[0061] In addition to or in place of authorized user 301, the vehicle original equipment manufacturer may automatically enable optional verification based on factors such as instructing unauthorized vehicle key management. In a non-restrictive example, optional verification may be enabled based on the following: the brand and / or model of vehicle 102, the current geographic location of vehicle 102, the date and / or time the pairing request was generated, the region where vehicle 102 was sold, applicable cybersecurity regulations, analysis of recent vehicle thefts, and / or other factors instructing unauthorized vehicle key management.

[0062] Figure 3A , Figure 3B and Figure 3C The key pairing process 300 provides a secure process for authorized users to manage the offline key fob 100 and pair it with the vehicle 102. In some implementations, offline key fob 100 pairing can occur while the vehicle 102 is in a vehicle assembly facility. Sometimes, the key pairing process 300 may not be used because an authorized user 301 (e.g., the vehicle owner) may not be assigned and the boarding process may not be completed. The key pairing process 300 may also be unsuitable if the vehicle 102 does not have an existing vehicle key.

[0063] In one form, reference Figure 4The offline key fob 100 can be paired with the vehicle 102 using a key pairing process 400, which is different from the key pairing process 300. For example, when the vehicle 102 and the offline key fob 100 are in factory learning mode, the authorized user verification and other checks performed by the key fob pairing process can be skipped. Furthermore, the vehicle 102 does not communicate with the vehicle support system 104, and the user is a technician at the manufacturing facility.

[0064] With the offline key fob 100 at the designated location 132, the key pairing process 400 can begin. Figure 3A Operation 306 involves offline key fob authentication. That is, key fob module 208 is configured to receive authentication information from offline key fob 100. Even in factory learning mode, vehicle 102 can refuse to pair with offline key fob 100 that does not provide a valid identity certificate.

[0065] Following offline key fob authentication operation 306, at operation 402, key fob module 208 generates and transmits the unsigned device payload of offline key fob 100. At operation 404, offline key fob 100 obtains the vehicle's certificate and data provided in the unsigned device payload. Because offline key fob 100 is in factory learning mode, has not yet been paired with other vehicles, and has not yet been provided to customers, there is no concern that the driver will be helpless due to unauthorized pairing overwriting the current vehicle data. Therefore, offline key fob 100 verifies the payload and is ready for pairing. Therefore, at operation 406, pairing module 116 notifies vehicle 102 to initiate pairing.

[0066] Then, the key pairing process 400 continues to execute. Figure 3C The pairing process is performed in operation 320. Once pairing process 320 is complete, vehicle 102 and offline key fob 100 are removed from factory learning mode and locked at operations 408 and 410 respectively. Offline key fob 100 is now active and ready for use. In some embodiments, key fob module 208 may notify a technician that pairing is complete and offline key fob 100 is active.

[0067] Once vehicle 102 is assembled and communicating with vehicle support system 104, vehicle 102 can transmit telematics messages indicating pairing status to vehicle support system 104.

[0068] In some variations, once the offline key fob 100 and the vehicle have successfully exchanged and stored pairing data, the final pairing step may include setting up any additional radio devices, such as Bluetooth pairing, which may occur automatically or after additional user input (e.g., pressing and holding button 114 on the key fob).

[0069] The offline key fob pairing process disclosed herein (e.g., processes 300 and 400) enforces mutual authentication, uses strong encryption for data exchange, and is integrated with vehicle support system 104 to centrally manage when the offline key fob 100 can be paired with vehicle 102. The offline key fob pairing process also provides increased compatibility with variant offline pairing processes intended for use in vehicle assembly plants.

[0070] Unless otherwise expressly indicated herein, all numerical values ​​indicating mechanical / thermal properties, percentage of composition, dimensions and / or tolerances or other characteristics should be understood as being modified by the words “about” or “approximately” when describing the scope of this disclosure. Such modification is desired for various reasons, including: industrial practice; material, manufacturing and assembly tolerances; and testing capabilities.

[0071] In this application, a component (e.g., a communication module 110 having a pairing module 116, a control module 112, a user profile module 206, a key fob module 208, a vehicle account module 134, and a key fob authentication module 136) may be a part of, or include, the following: an application-specific integrated circuit (ASIC); a digital, analog, or mixed-signal analog / digital discrete circuit; a digital, analog, or mixed-signal analog / digital integrated circuit; a composable logic circuit; a field-programmable gate array (FPGA); a processor circuit (shared, dedicated, or grouped) that executes code; a memory circuit (shared, dedicated, or grouped) that stores code executed by the processor circuit; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-a-chip.

[0072] The term memory device is a subset of the term computer-readable medium. As used herein, the term computer-readable medium does not cover transient electrical or electromagnetic signals propagated through a medium (such as on a carrier wave); therefore, the term computer-readable medium can be considered tangible and non-transient. Non-limiting examples of non-transient tangible computer-readable media include non-volatile memory circuits (such as flash memory circuits, erasable programmable read-only memory circuits, or mask read-only circuits), volatile memory circuits (such as static random access memory circuits or dynamic random access memory circuits), magnetic storage media (such as analog magnetic tape or digital magnetic tape or hard disk drives), and optical storage media (such as Universal Serial Bus (USB) drives, optical discs (CDs), digital versatile discs (DVDs), or Blu-ray discs).

[0073] The devices and methods described in this application (e.g., processes 300 and 400, communication module 110 with pairing module 116, control module 112, user profile module 206, key fob module 208, vehicle account module 134, and key fob authentication module 136) can be implemented, partially or entirely, by a dedicated computer created by configuring a general-purpose computer (e.g., a computing device) to perform one or more specific functions embodied in a computer program. Function blocks, flowchart components, and other elements described above serve as software specifications that can be translated into computer programs through the routine work of a technician or programmer.

[0074] The description in this disclosure is merely exemplary in nature, and therefore, variations without departing from the spirit and scope of this disclosure are intended to be made within its scope. Such variations should not be considered as departing from the spirit and scope of this disclosure.

[0075] According to the present invention, a system is provided having a vehicle system, the vehicle system including one or more computing devices configured to: in response to receiving a key pairing request to pair an offline key fob with a vehicle, identify a user as an authorized user of the vehicle using an authorization action associated with a user; in response to the user being an authorized user, verify that the offline key fob is authorized to pair with the vehicle using authentication information provided by the offline key fob using a short-range communication protocol; transmit a device payload to the offline key fob using the short-range communication protocol; and pair the device payload with the offline key fob to enable the offline key fob to control the vehicle.

[0076] According to an embodiment, the one or more computing devices of the vehicle system are configured to: transmit a key fob pairing request to a remote server to obtain approval for pairing with the offline key fob; and decrypt a signed payload message in response to the remote server's approval of pairing to obtain the device payload from the remote server.

[0077] According to an embodiment, the short-range communication protocol includes at least one of a near-field communication protocol or an ultra-wideband protocol.

[0078] According to an embodiment, the authorization action includes at least one of the following: a message from one or more key fobs paired with the vehicle; obtaining and verifying login credentials associated with the authorized user; confirming a one-time password entered by the user; or biometric authentication.

[0079] According to an embodiment, the authentication information includes at least one of an identity certificate, a root certificate, or a private key.

[0080] According to an embodiment, to verify the offline key fob, the one or more computing devices of the vehicle system are configured to perform a challenge-response handshake with the offline key fob, and determine that the offline key fob is authorized to be paired with the vehicle in response to a challenge response from the offline key fob that has verified the expected response.

[0081] According to an embodiment, the invention further features a remote server configured to: decrypt the key pairing request from the vehicle system to obtain information associated with the vehicle and the offline key fob; verify the certificate of the offline key fob, the status of the offline key fob, and the status of the vehicle; and, in response to the verification of the certificate of the offline key fob, the status of the offline key fob, and the status of the vehicle, transmit an encrypted, signed payload message to authorize pairing of the offline key fob with the vehicle, wherein the one or more computing devices of the vehicle system are configured to decrypt the encrypted, signed payload message to obtain the device payload.

[0082] According to an embodiment, the remote server is configured to transmit the encrypted, signed payload message in response to a secondary verification independent of the authentication of the offline key fob.

[0083] According to an embodiment, the secondary verification is enabled by the user and includes at least one of the following: obtaining explicit approval from the authorized user; delaying the approval response message for a selected period of time; canceling the pairing attempt; providing a cooling-off period that allows the authorized user to take corrective action before the offline keychain can be activated; and determining whether the authorized user has enabled a ban on all pairing requests.

[0084] According to an embodiment, the one or more computing devices of the vehicle system are configured to: identify the user as the authorized user of the vehicle in response to the offline key fob and the vehicle not being in factory learning mode; and bypass the identification of the user as the authorized user of the vehicle by using an authorization action associated with the user in response to receiving a key pairing request to pair the offline key fob with the vehicle and in response to the offline key fob and the vehicle being in factory learning mode.

[0085] According to the present invention, a non-transitory computer-readable medium is provided having instructions for pairing an offline key fob with a vehicle, the instructions performing operations when executed by one or more processors, including: identifying a user as an authorized user of the vehicle using an authorization action associated with a user in response to receiving a key pairing request to pair the offline key fob with the vehicle; verifying that the offline key fob is authorized to pair with the vehicle using authentication information provided by the offline key fob using a short-range communication protocol in response to the user being an authorized user; transmitting a device payload to the offline key fob using the short-range communication protocol; establishing a secure channel with the offline key fob using an encryption key in response to the offline key fob verifying the device payload; and pairing the offline key fob with the secure channel and the device payload to enable the offline key fob to control the vehicle.

[0086] According to an embodiment, the invention is further characterized by instructions that, when executed by the one or more processors, perform operations including: transmitting a key fob pairing request to a remote server to obtain approval for pairing with the offline key fob; and decrypting a signed payload message in response to the remote server's approval of pairing to obtain the device payload from the remote server.

[0087] According to an embodiment, the short-range communication protocol includes at least one of a near-field communication protocol or an ultra-wideband protocol.

[0088] According to an embodiment, the authorization action includes at least one of the following: a message from one or more key fobs paired with the vehicle; obtaining and verifying login credentials associated with the authorized user; confirming a one-time password entered by the user; or biometric authentication.

[0089] According to an embodiment, the authentication information includes at least one of an identity certificate, a root certificate, or a private key.

[0090] According to an embodiment, the invention is further characterized by instructions that, when executed by the one or more processors, perform operations including: performing a challenge-response handshake with the offline key fob, and determining that the offline key fob is authorized to be paired with the vehicle in response to a challenge response from the offline key fob that has verified the expected response.

[0091] According to an embodiment, the invention is further characterized by instructions that, when executed by the one or more processors, perform operations including: decrypting the key pairing request to obtain information associated with the vehicle and the offline key fob; verifying the certificate of the offline key fob, the status of the offline key fob, and the status of the vehicle; and transmitting an encrypted, signed payload message to authorize pairing of the offline key fob with the vehicle in response to the verification of the certificate of the offline key fob, the status of the offline key fob, and the status of the vehicle, wherein the encrypted, signed payload message is decrypted to obtain the device payload.

[0092] According to an embodiment, the invention is further characterized by instructions that, when executed by the one or more processors, perform operations including: performing a secondary verification independent of the authentication of the offline key fob, wherein the encrypted, signed payload message is transmitted in response to satisfying the secondary verification.

[0093] According to an embodiment, the secondary verification is enabled by the user and includes at least one of the following: obtaining explicit approval from the authorized user; delaying the approval response message for a selected period of time; canceling the pairing attempt; providing a cooling-off period that allows the authorized user to take corrective action before the offline keychain can be activated; and determining whether the authorized user has enabled a ban on all pairing requests.

[0094] According to the present invention, a method for pairing an offline key fob with a vehicle includes: in response to receiving a key pairing request to pair the offline key fob with the vehicle, the vehicle system identifies a user as an authorized user of the vehicle using an authorization action associated with a user; in response to the user being an authorized user, the vehicle system verifies that the offline key fob is authorized to pair with the vehicle using authentication information provided by the offline key fob using a short-range communication protocol, wherein the authentication information includes at least one of an identity certificate, a root certificate, or a private key; the vehicle system transmits the key fob pairing request to a remote server to obtain approval for pairing with the offline key fob; in response to the remote server approving the pairing, the vehicle system decrypts a signed payload message to obtain a device payload from the remote server; the vehicle system transmits the device payload to the offline key fob using a short-range communication protocol; in response to the offline key fob verifying the device payload, the vehicle system establishes a secure channel with the offline key fob using an encryption key; and the vehicle system pairs the vehicle with the offline key fob using the secure channel, one or more shared data, and the device payload, so that the offline key fob can control the vehicle.

Claims

1. A system comprising: A vehicle system, the vehicle system including one or more computing devices, the one or more computing devices being configured to: In response to receiving a key pairing request to pair an offline key fob with a vehicle, the system uses an authorization action associated with the user to identify the user as an authorized user of the vehicle. In response to the user being the authorized user, the authentication information provided by the offline key fob using the Short Range Communication Protocol is used to verify that the offline key fob is authorized to be paired with the vehicle; The device payload is transmitted to the offline key fob using the short-range communication protocol. as well as The device payload is paired with the offline key fob to enable the offline key fob to control the vehicle.

2. The system of claim 1, wherein the one or more computing devices of the vehicle system are configured to: Transmit a keychain pairing request to a remote server to obtain approval for pairing with the offline keychain; and In response to the remote server approving the pairing, the signed payload message is decrypted to obtain the device payload from the remote server.

3. The system of claim 1, wherein the short-range communication protocol includes at least one of a near-field communication protocol or an ultra-wideband protocol.

4. The system of claim 1, wherein the authorization action includes at least one of the following: a message from one or more key fobs paired with the vehicle; obtaining and verifying login credentials associated with the authorized user; confirming a one-time password entered by the user; or biometric authentication.

5. The system of claim 1, wherein the authentication information includes at least one of an identity certificate, a root certificate, or a private key.

6. The system of claim 1, wherein, to verify the offline key fob, the one or more computing devices of the vehicle system are configured to perform a challenge-response handshake with the offline key fob and determine that the offline key fob is authorized to pair with the vehicle in response to a challenge response from the offline key fob that has verified the expected response.

7. The system of claim 1, further comprising: Remote server, the remote server being configured as follows: Decrypt the key pairing request from the vehicle system to obtain information associated with the vehicle and the offline key fob; Verify the certificate of the offline key fob, the status of the offline key fob, and the status of the vehicle; as well as In response to the verification of the certificate of the offline key fob, the status of the offline key fob, and the status of the vehicle, an encrypted, signed payload message is transmitted to authorize pairing of the offline key fob with the vehicle, wherein The one or more computing devices of the vehicle system are configured to decrypt the encrypted signed payload message to obtain the device payload.

8. The system of claim 7, wherein the remote server is configured to transmit the encrypted, signed payload message in response to a secondary verification independent of the authentication of the offline key fob.

9. The system of claim 8, wherein the secondary authentication is enabled by the user and includes at least one of the following: obtaining explicit approval from the authorized user; delaying the approval response message for a selected period of time; canceling the pairing attempt; providing a cooling-off period that allows the authorized user to take corrective action before being able to activate the offline key fob; and determining whether the authorized user has enabled a ban on all pairing requests.

10. The system of claim 1, wherein the one or more computing devices of the vehicle system are configured to: In response to the offline key fob and the vehicle not being in factory learning mode, the user is identified as the authorized user of the vehicle; and In response to receiving the key pairing request to pair the offline key fob with the vehicle and in response to the offline key fob and the vehicle being in the factory learning mode, the authorization action associated with the user is used to bypass the identification of the user as the authorized user of the vehicle.

11. A method for pairing an offline key fob with a vehicle, comprising: In response to receiving a key pairing request to pair an offline key fob with the vehicle, the vehicle system identifies the user as an authorized user of the vehicle using an authorization action associated with the user. In response to the user being the authorized user, the vehicle system uses authentication information provided by the offline key fob using a short-range communication protocol to verify that the offline key fob is authorized to be paired with the vehicle. The vehicle system transmits a key fob pairing request to a remote server to obtain approval for pairing with the offline key fob; In response to the remote server's approval of the pairing, the vehicle system decrypts the signed payload message to obtain the device payload from the remote server; The vehicle system uses the short-range communication protocol to transmit the device payload to the offline key fob; The vehicle system, in response to the offline key fob verifying the device's payload, establishes a secure channel with the offline key fob using an encryption key; as well as The vehicle system uses the secure channel, one or more shared data, and the device payload to pair the vehicle with the offline key fob, so that the offline key fob can control the vehicle.

12. The method of claim 11, wherein the short-range communication protocol includes at least one of a near-field communication protocol or an ultra-wideband protocol.

13. The method of claim 11, wherein the authorization action includes at least one of the following: a message from one or more key fobs paired with the vehicle; obtaining and verifying login credentials associated with the authorized user; confirming a one-time password entered by the user; or biometric authentication.

14. The method of claim 11, wherein the authentication information includes at least one of an identity certificate, a root certificate, or a private key.

15. The method of claim 11, further comprising performing a challenge-response handshake with the offline key fob, and determining that the offline key fob is authorized to pair with the vehicle in response to a challenge response from the offline key fob that has verified an expected response.

Images