Bi-directional tire pressure monitoring system (TPMS) learned and authenticated pairing

CN118991307APending Publication Date: 2024-11-22FORD GLOBAL TECH LLC
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202410568407.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-22
Filing Date
2024-05-09
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

Existing wireless technologies have security and privacy challenges in communication between vehicles and tire pressure monitoring systems (TPMS), especially when malicious third parties may intercept or eavesdrop on data, making it difficult to achieve secure pairing and data transmission. .

Method used

By using Bluetooth low power consumption (BLE) technology, security measures such as resolvable private address (RPA), link layer encryption and message authentication code (MAC) are adopted to achieve automatic learning and authentication pairing between TPMS sensors and vehicles, ensuring that Security and privacy of data transmission. The specific method includes generating a random number to derive the paired PIN and test values, generating a message authentication code using the HMAC function, and encrypting communication via a pre-shared key.

Benefits of technology

It realizes the secure sharing of secrets between TPMS sensors and vehicles, prevents data from being eavesdropped or tampered by malicious users, ensures the secure transmission and privacy protection of tire information, and solves the problems of malicious man-in-the-middle attacks and data spoofing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118991307A_ABST
    Figure CN118991307A_ABST
Patent Text Reader

Abstract

Systems and methods for implementing pairing of bidirectional tire pressure monitoring system (TPMS) learning and authentication are disclosed. The random values may be used to determine test values and paired PINs by using an HMAC (Hash-based Message Authentication Code) function and a pre-shared key accessible to the TPMS sensor and the vehicle (e.g., its controller system). Random values and test values may be broadcast by a TPMS sensor and received by a vehicle. The vehicle may compute a pairing PIN using a random value and a pre-shared key.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to systems and methods for secure tire pressure monitoring system (TPMS) pairing. Background Art

[0002] Wireless technologies, such as Bluetooth, provide the ability to perform communications between various devices. However, the use of wireless technologies can present many challenges around security and privacy. Determining whether to trust a device presents many challenges because wireless signals can be intercepted by malicious third parties who may attempt to eavesdrop on data being transmitted between paired devices, perform man-in-the-middle attacks by altering the data being transmitted, impersonate a device or device type in an attempt to gain trust, or other various malicious activities.

[0003] Therefore, using wireless technology (such as Bluetooth-based technology) to communicate between a vehicle and a tire pressure monitoring system (TPMS) presents many challenges. For example, the ability to securely pair a TPMS can be an important aspect of secure or protected communication. Summary of the invention

[0004] The techniques described herein may be used to allow a vehicle and a TPMS to establish a secure communication channel that may be used by the TPMS to relay tire information to the vehicle, where the tire information may be monitored, analyzed, presented, etc.

[0005] Protecting sensor data in a tire pressure monitoring system (TPMS) is relevant for various reasons. Wheel sensor communications can use wireless communication to send sensor data (such as tire data and static sensor ID) to the vehicle using ultra-high frequency (UHF) broadcasts. Security measures can be taken to prevent this data from being observed by other wireless devices within range of the vehicle. Security measures can be implemented for various purposes, such as preventing malicious users from spoofing data to create false flat tire alarms or causing other problems by hiding underinflated tires. Security measures can mitigate or eliminate privacy issues associated with broadcasting static sensor IDs, which can potentially be used to identify and / or track vehicles. In various embodiments, Bluetooth Low Energy (BLE) is used to implement secure two-way TPMS communications, which can address various privacy and / or security issues by using common security controls, such as using link layer encryption, variable resolvable private addresses (RPAs), and including message authentication codes (MACs) in TPMS messages.

[0006] Pairing of TPMS with a vehicle presents unique challenges. Bluetooth devices and their applications typically require various security keys that are to be shared in secret. This sharing of confidential cryptographic material typically occurs through pairing / binding following a manual action by the user (e.g., pressing a button to put the Bluetooth device into pairing mode, entering a pairing PIN on their phone, etc.), but these actions are not feasible when the TPMS sensor is expected to be automatically learned by the vehicle. In addition, authenticated pairing between Bluetooth devices typically involves user interaction with some input / output (I / O) device or peripheral device (e.g., a display on one device displays a temporary PIN, another device allows entry of a PIN via a keyboard, etc.), which is also not feasible for the vehicle to easily and automatically learn the TPMS sensor. In addition, it is impractical or even impossible to integrate a screen into a TPMS sensor. The technology described herein may include a protocol for establishing a shared secret between a TPMS sensor and a vehicle through an automatic learning process (or a manual learning event) while also keeping the shared secret data confidential and hidden from other nearby devices.

[0007] As described in more detail below, various embodiments of the present disclosure may be used to implement techniques for pairing for bidirectional tire pressure monitoring system (TPMS) learning and authentication. In various embodiments, a handshake process according to the following techniques is utilized to establish secure sharing of TPMS sensor data. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Detailed description is set forth with respect to the accompanying drawings. The use of the same reference numerals may indicate similar or identical items. Various embodiments may utilize elements and / or components other than those shown in the accompanying drawings, and some elements and / or components may not be present in various embodiments. The elements and / or components in the accompanying drawings are not necessarily drawn to scale. Throughout this disclosure, singular and plural terms may be used interchangeably, depending on the context.

[0009] Figure 1 A diagram is shown depicting an example of pairing for bi-directional tire pressure monitoring system (TPMS) sensor learning and authentication in accordance with at least one embodiment of the present disclosure.

[0010] Figure 2 A diagram is shown depicting an example of a technique for generating a test value and a corresponding pairing PIN that can be securely shared in accordance with at least one embodiment of the present disclosure.

[0011] Figure 3 A diagram is shown depicting an exemplary protocol for pairing of bi-directional tire pressure monitoring system (TPMS) learning and authentication in accordance with at least one embodiment of the present disclosure.

[0012] Figure 4A diagram depicting an exemplary protocol for bi-directional tire pressure monitoring system (TPMS) safety communications in accordance with at least one embodiment of the present disclosure is shown.

[0013] Figure 5 An illustrative example of a pairing process for two-way learning and authentication with a vehicle or its controller system is shown in accordance with one or more exemplary embodiments of the present disclosure.

[0014] Figure 6 An illustrative example of a process for pairing with a tire pressure monitoring system (TPMS) sensor for bidirectional learning and authentication is shown in accordance with one or more exemplary embodiments of the present disclosure.

[0015] Figure 7 A block diagram illustrating an example of a machine or system upon which any one or more of the techniques (eg, methodologies) discussed herein may be performed. DETAILED DESCRIPTION

[0016] Figure 1 A diagram 100 is shown depicting an example pairing of bi-directional tire pressure monitoring system (TPMS) sensor learning and authentication in accordance with at least one embodiment of the present disclosure.

[0017] In various embodiments, the TPMS sensor 102 may initialize, change, or otherwise determine a new resolvable private address (RPA). The RPA may refer to a temporary identifier (e.g., a Bluetooth address) that may be used to protect the privacy of a device when the device communicates with other devices. In various embodiments, the RPA may be used with Bluetooth Low Energy (BLE) technology, which may be described herein as an example of a type of wireless communication that facilitates two-way communication between the TPMS and the vehicle.

[0018] The RPA can be characterized as a randomly generated address that is different from the device's permanent MAC address. When a device advertises or scans for other devices nearby, it can use the RPA instead of its permanent MAC address. This makes it more difficult for others to track the movement of the device or identify it by its MAC address. In various embodiments, the RPA is not completely random and can encode non-random data that can be traced to an authorized party such as a device manufacturer or network administrator.

[0019] In various embodiments, after drive cycle detection, the vehicle controller system 104 will listen for new sensors, perform an automatic localization process, or perform various other steps to determine when a potential or candidate pairing partner is detected. This can be performed as part of a learning process to identify the locations of candidate sensors and whether they are attached to the vehicle and / or the locations of candidate sensors.

[0020] In various embodiments, the TPMS will perform a series of operations after driving cycle detection to determine a PIN and a test value. The PIN can refer to a temporary pairing PIN that can be used to establish a secure connection between the TPMS and the vehicle. In various embodiments, the PIN and the test value are derived from random values. As an example, the TPMS can generate a random number 106 and determine an input value. The input can be determined based entirely or in part on the random number 106. Additional information (such as protocol version) can be encoded in the input. The input value can be provided as an input to a one-way function (such as an HMAC (Hash-based Message Authentication Code) operation) to produce an output value. In various embodiments, the HMAC operation also operates based on a key, which can be a pre-shared key accessible to both the TPMS and the vehicle. The shared key can be provided to the TPMS and the vehicle as part of their respective manufacturing processes. Exemplary HMAC algorithms include HMAC-SHA-256, HMAC-SHA-512, HMAC-MD5, etc.

[0021] The output value of the one-way function can be used to determine a test value 108 and a pairing PIN 110. In various embodiments, the output is truncated, and the truncated portion of the output is used to determine the PIN according to a specific format. For example, if the HMAC output is an N-bit binary value, the truncated portion can be an M-bit binary value, where M < N. Modulo arithmetic can be performed to map the M-bit binary value to a decimal pairing PIN. For example, a BLE pairing PIN can have a value between 0 and 999,999 (base 10), and the pairing PIN can be calculated by computing the base 10 value of the M-bit binary value modulo 1,000,000. A second portion of the output value can be used to generate the test value. In various embodiments, the portions of the HMAC output used to generate the test value and the pairing PIN are non-overlapping portions of the HMAC output.

[0022] In various embodiments, the TPMS will broadcast a learning mode advertisement. As described above, the learning mode advertisement can include various data, such as RPA, random values, and test values. The learning mode advertisement can also include tire data, such as tire pressure values, temperature values, battery status information, signal strength, etc. It should be noted that in various embodiments, the learning mode advertisement will be broadcast in plain text and will not include the pairing PIN.

[0023] The vehicle controller system 104 can listen for learning mode announcements (e.g., using BLE technology) to determine if the announcement is for a sensor of the vehicle. For example, two vehicles adjacent to each other can receive learning announcements from the TPMS sensors of the other vehicle. Learning mode announcements from unlearned sensors can be tracked. RPA and tire data can be used to determine which candidate sensors are attached to the vehicle and which candidate sensors are not attached to the vehicle. RPA and tire data can be analyzed and used to discard random values ​​and test values ​​for unattached sensors.

[0024] In various embodiments, the vehicle determines that the RPA is associated with the attached sensor based on the learning mode announcement, and will use the random value and test value in the associated learning mode announcement to determine the pairing PIN of the attached sensor. It should be noted that although the pairing PIN is not directly transmitted in the learning mode announcement, the vehicle may still have the ability to derive the pairing PIN based on the random value and test value and by using a pre-shared key. The vehicle can use the random value 106 from the learning mode announcement to determine the input value of the one-way function. The input value can be based on additional data, such as a protocol version. If multiple protocol versions are supported, the vehicle can generate multiple input values. The input value can be used as an input to a keyed one-way function (e.g., an HMAC operation), which also uses a pre-shared key to generate an output value. The output value can be used to determine the calculated test value 108, for example, by obtaining a second part of the calculated test value (e.g., the last M bits of the output value). The calculated test value 108 can be compared with the test value included in the learning mode announcement. If the calculated test value matches the test value received from the learn mode announcement, the vehicle can use this as an indication that the vehicle is able to determine the pairing PIN 110 of the vehicle. The pairing PIN 110 can be determined by truncating the calculated output value and performing a modulo operation, for example, in the same manner as a TPMS sensor. Thus, the pairing PIN can be determined by the vehicle.

[0025] Once the vehicle has determined the pairing PIN 110 from the learning mode announcement, the vehicle can transmit a message to the TPMS sensor to connect to the potential sensor. The derived PIN can be placed on the BLE stack by the TPMS sensor. In various embodiments, the TPMS sensor and the vehicle can perform an authenticated BLE pairing with the located sensor by performing a pairing and binding process using the derived pairing PIN. This may involve key entry or digital comparison. Once the authenticated BLE pairing is completed, the vehicle can generate an integrity key (IK). The vehicle or TPMS sensor can start link layer encryption and execute a routine for establishing a BLE secure connection. The routine may include the mutual exchange of an identity resolution key (IRK) and a message integrity key. The IRK may refer to a unique key generated by a BLE-enabled device and used by both the BLE device and the authorization device to resolve the RPA and establish a connection.

[0026] The establishment of a BLE secure connection can be used to indicate the end of the learning mode, and normal TPMS operation can begin thereafter. The TPMS sensor can then activate a normal TPMS operating mode involving broadcasting a TPMS announcement. The TPMS announcement can include a new RPA (e.g., different from the learning mode RPA), tire data, and a tag. The tag can refer to a message authentication code (MAC). The tag can be used to provide a cryptographically verifiable guarantee of integrity and / or authenticity. In various embodiments, the vehicle uses the exchanged IRK to parse the new RPA from the learned sensor and uses the integrity key to verify the received tag. The vehicle can use the integrity key to calculate the tag on the received tire data. The calculated tag can be compared to the received tag, and if they match, the received tire data can be determined to be authentic. However, if the calculated tag does not match the received tag, the entire TPMS announcement may be discarded as untrustworthy.

[0027] In various embodiments, the TPMS sensor periodically changes the RPA and provides updated RPA values ​​to the vehicle using the IRK.

[0028] Figure 2 Diagram 200 is shown depicting an example of a technique for generating a test value and a corresponding pairing PIN that can be securely shared in accordance with at least one embodiment of the present disclosure.

[0029] Figure 2 A non-limiting illustrative example of how to derive a test value and a PIN that can be used in a pairing process for mutual authentication is depicted. The test value and the PIN can be generated by a tire pressure monitoring system (TPMS) sensor and used to establish a secure connection with a vehicle or its control unit over a wireless communication channel.

[0030] In various embodiments, a system (eg, a TPMS sensor) generates, obtains, or otherwise determines the random value 202. Figure 2 A random value is depicted in , but it can be a pseudo-random number generated deterministically using a seed value. In general, a random value as discussed herein can be a number that appears sufficiently random but is not necessarily generated using a truly unpredictable process (such as radioactive decay or atmospheric noise). For example, in various embodiments described herein, a pseudo-random number generator can be used to generate a random value.

[0031] Additional data 204 may refer to deterministic information used to determine an input value. Deterministic information may include information such as a version number, model number, or other information that is not necessarily different in multiple routines for generating test and PIN numbers. In some embodiments, additional data 204 is included in the TPMS notification message. In some embodiments, additional data 204 is a predetermined and limited list agreed upon in advance by the parties. For example, the additional data may encode a list of supported BLE protocol versions. In some embodiments, additional data 204 includes a random value.

[0032] In various embodiments, the HMAC function 206 refers to an HMAC (Hash Message Authentication Code) function that can be used to generate a message authentication code (MAC). A MAC refers to a cryptographic construct that can be used to verify the authenticity and integrity of a message. In various embodiments, the HMAC function 206 uses a one-way encryption function to generate a message authentication code using a secret key to create a message authentication code. Figure 2 The use of pre-shared key 208 as a secret key is depicted. In various embodiments, the HMAC function takes two inputs: an input message and a secret key. It then applies a specific hash algorithm to the message, combines it with the secret key, and applies the hash algorithm again to the result. Exemplary HMAC algorithms include HMAC-SHA-256, HMAC-SHA-512, HMAC-MD5, etc. This process generates a fixed-size output called an HMAC. The HMAC output is in Figure 2 is depicted as output 210 .

[0033] The pre-shared key 208 may refer to cryptographic material that is known and shared between two parties authorized to perform secure two-way communications. In some embodiments, the pre-shared key 208 refers to a symmetric cryptographic key that is accessible or known to both the TPMS sensor and the vehicle (e.g., a vehicle control unit). In some embodiments, the pre-shared key is a private key associated with the TPMS sensor that is also accessible to a service (e.g., a vehicle manufacturer server) that is accessible by a privileged entity (such as an authorized vehicle). For example, both the TPMS sensor and the vehicle may be registered to the same user, which grants the vehicle access to directly view the pre-shared key 208 or to cause the server to perform operations using the pre-shared key (e.g., HMAC function 206).

[0034] Output 210 may refer to the output value generated by the HMAC function 206. Output 210 can be used to derive test values and pairing PINs. According to at least one embodiment, the pairing PIN can be determined by providing output 210 as the input to a truncation 212 function that takes the first part of output 210. For example, if output 210 is X bits in length, truncation 212 can take the first Y bits of output 210, where Y < X. The truncated output can be a binary value. The truncated output can be provided as the input to a modulo 214 operation that maps the truncated output to a number between 0 and 999,999. PIN 216 may require the value to be between 000000 and 999999 (e.g., a six-digit decimal number with leading zeros if needed). According to various embodiments, PIN 216 is not shared in plaintext with other entities. The PIN can be used as part of a pairing or binding process between two entities such as the TPMS sensor and the vehicle control unit described above.

[0035] The same output 210 used to derive PIN 216 can also be used to derive test value 218. Test value 218 can be derived as a truncated portion of output 210. For example, if output 210 is X bits in length, test value 218 can be the last Z bits of output 210, where Z < X. In various embodiments, PIN 216 and test value 218 are derived from non-overlapping portions of output 210. For example, if output 210 is X bits in length, the first Y bits of output 210 can be used to derive PIN 216, and the last Z bits of output 210 can be used to derive test value 218, where X = Y + Z. In some embodiments, all of output 210 or a different portion (e.g., overlapping or non-overlapping) of output 210 is used to generate test value 218. For example, in one embodiment, a non-keyed cryptographic hash function, a checksum function, or a cyclic redundancy check using output 210 or a portion thereof is used to generate test value 218.

[0036] Figure 3 FIG. 300 is a diagram illustrating an exemplary protocol depicting a pairing for two-way tire pressure monitoring system (TPMS) learning and authentication in accordance with at least one embodiment of the present disclosure. Figure 3 The protocol depicted therein is used to establish a secure connection between TPMS sensor 302 and vehicle 304, which can be used to exchange cryptographic material (e.g., an integrity key).

[0037] In various embodiments, the TPMS sensor 302 is equipped with a BLE Identity Resolution Key (IRK). The IRK may refer to a unique key generated by a BLE enabled device and used by both the BLE device and the authorization device to resolve the RPA and establish a secure connection. Both the TPMS sensor 302 and the vehicle 304 may be equipped with or otherwise have access to a pre-shared secret key. The pre-shared secret key may be provided at the time of manufacturing and may be securely stored in, for example, a Trusted Platform Module (TPM) or a security module.

[0038] The TPMS sensor 302 may detect the start of a new drive cycle and change to a new resolvable private address (RPA). The RPA may refer to a temporary identifier (e.g., a Bluetooth address) that may be used to protect the privacy of a device when the device communicates with other devices. In various embodiments, the RPA may be used with Bluetooth Low Energy (BLE) technology, which may be considered an example of a type of wireless communication that facilitates two-way communication between the TPMS sensor 302 and the vehicle 304. The vehicle 304 may also independently determine the start of a new drive cycle or manual learning trigger 308.

[0039] The vehicle may use learn mode when new TPMS sensors are installed or when tires are rotated or replaced. The process for entering learn mode can vary depending on the vehicle, but generally involves following a series of steps in a specific order. In various embodiments, the vehicle enters learn mode when a button or combination of buttons on the dashboard or steering wheel is pressed in a specific order. The TPMS will then enter a special mode where it can detect the TPMS sensors and program them.

[0040] In various embodiments, detection of a new drive cycle or a manual learning trigger may initiate the start of an automatic learning period. The TPMS sensor 302 may determine a random value (e.g., generate a random number) and use the random value to derive a pairing PIN and a test value 310. For example, in conjunction with Figure 2The discussed techniques can be used to generate a pairing PIN and a test value. The TPMS sensor 302 can activate a learning mode broadcast 312 and broadcast a learning mode announcement 314. The TPMS sensor 302 can broadcast the above-mentioned RPA, random value, and test value in each learning mode announcement message. In addition, the learning mode announcement message may include tire data, such as measured pressure and / or temperature data. The vehicle 304 can track random / test values ​​316 from unlearned sensors. The temporarily received random value may include a tuple of the tracked RPA and random value. The vehicle 304 can use the RPA and tire data to determine the attached candidate sensors 318. The random values ​​and test values ​​of the unattached sensors can be discarded. The positions of the candidate sensors can be determined, for example, the positions of the vehicle can include the left front tire, the right front tire, the right rear tire, and the left rear tire. The corresponding RPA for each corresponding position can be determined based on the learning mode announcement.

[0041] Once one or more candidate sensors are identified, a temporary pairing PIN for each attached sensor can be derived using the pre-shared key and the random / test value. It should be noted that the PINs are not included in the announcement message because they may be viewed by other parties. The vehicle 304 may still have the ability to derive the pairing PIN based on the random value and test value received in the learning mode announcement and by using the pre-shared key. The vehicle can use the random value from the learning mode announcement to determine the input value of the HMAC function. The input value can be used as an input to a keyed one-way function (e.g., an HMAC operation) that also uses the pre-shared key to generate an output value. The output value can be used to determine the calculated test value, for example, by obtaining the second part of the calculated test value (e.g., the last M bits of the output value). The calculated test value can be compared with the test value included in the learning mode announcement. If the calculated test value matches the test value received from the learning mode announcement, the vehicle can use it as an indication that the vehicle is able to determine the pairing PIN of the vehicle. The pairing PIN can be determined by truncating the calculated output value and performing a modulo operation, for example, in the same manner as the TPMS sensor. Therefore, the pairing PIN can be determined by the vehicle. The TPMS sensor 302 may store the derived PIN in the BLE stack 322 , which allows it to determine whether the vehicle 304 possesses the correct pairing PIN.

[0042] In various embodiments, the vehicle 304 determines the calculated PIN and submits a request to connect to the TPMS sensor 302, which will be considered a candidate sensor. An authenticated BLE pairing with the TPMS sensor 302 can be performed, where the TPMS sensor 302 and the vehicle 304 are paired and bound 326 using the PIN. In various embodiments, a key entry or a numeric comparison is performed. The derived and calculated PINs must match in order to perform the pairing. In various embodiments, the vehicle 304 will generate an integrity key (IK) 328 for each learned sensor. For example, if the TPMS sensors on four tires are being learned, there may be a first IK generated for the first tire, a second IK generated for the second tire, a third IK generated for the third tire, and a fourth IK generated for the fourth tire. Each of the tires may also have its own corresponding BLE IRK.

[0043] The vehicle 304 may be coupled to each candidate sensor (e.g., Figure 3 A BLE secure connection is established between the TPMS sensor 302 of the embodiment of the present invention. The BLE secure connection can provide cryptographically verifiable confidentiality guarantees, and the secure connection can be used to exchange the BLE IRK and IK 332. Once the BLE IRK and IK have been exchanged, the secure connection can be terminated (e.g., end the connection 334) as a measure to increase battery life.

[0044] Once integrity keys have been exchanged with all learned sensors, the sensor (e.g., TPMS sensor 302) and vehicle 304 may exit learning mode 336, and normal TPMS operation may resume, e.g., as described below in conjunction with Figure 4 discussed.

[0045] Figure 4 A diagram 400 is shown depicting an exemplary protocol for bi-directional tire pressure monitoring system (TPMS) safety communications in accordance with at least one embodiment of the present disclosure. Figure 4 The protocol depicted in is used to establish a secure connection between the TPMS sensor 402 and the vehicle 404, which can be used to exchange cryptographic material (eg, integrity keys).

[0046] In various embodiments, both the TPMS sensor 402 and the vehicle 404 may have access to a message integrity key (IK). Figure 3 The described technique determines the IK. It is worth noting that it is possible that the test value and the random value are transmitted in plain text from the TPMS sensor 402 to the vehicle 404, and the vehicle 404 is able to calculate the pairing PIN by accessing the pre-shared secret key.

[0047] The TPMS sensor may send a TPMS notification 408 including a new RPA, tire data, and MAC. The MAC may be generated at least from the tire data and using the IK. The MAC may also be generated from the RPA.

[0048] In various embodiments, the vehicle 404 receives the TPMS announcement and uses the IRK to resolve the new RPA and uses the IK to verify the MAC 410 applied to the TPMS data. If the device has the IRK of the peer device, the RPA can be resolved by the device. In various embodiments, the resolvable private address has a 24-bit prand and a 24-bit hash. The prand and IRK of the peer device are used to resolve the address. When the vehicle 404 receives the resolvable private address, it extracts the hash and prand from it. A local hash value is then generated using the IRK of the peer device and the prand extracted from the address. The local hash value is compared to the hash extracted from the address. If they match, the address is resolved. If the device has more than one peer IRK, the device repeats the procedure for each stored IRK to determine whether the received resolvable private address is associated with any stored IRK. This is done until the address resolution of one of the IRKs is successful or all IRKs have been tried.

[0049] In various embodiments, the vehicle 404 calculates a MAC using the received tire data, RPA, etc., and determines whether the calculated MAC matches the received MAC. The MAC is calculated using the IK exchanged between the TPMS sensor 402 and the vehicle 404, for example, as described above in conjunction with Figure 3 If the values ​​match, the integrity and authenticity of the received message can be confirmed and the tire data can be accepted, but if they do not match, the received tire data can be discarded as potentially unreliable or untrustworthy. In various embodiments, the TPMS sensor 402 will periodically change the RPA 412 to provide privacy for the vehicle 404 and prevent tracking of the vehicle based on the broadcasted RPA value.

[0050] Figure 5An illustrative example of a process 500 for pairing with a vehicle or its controller system for two-way learning and authentication according to one or more exemplary embodiments of the present disclosure is shown. In at least one embodiment, some or all of the process 500 (or any other process described herein, or a variation and / or combination thereof) is executed under the control of one or more computer systems storing computer executable instructions, and may be implemented as code (e.g., computer executable instructions, one or more computer programs, or one or more applications) that is executed together on one or more processors, implemented by hardware, software, or a combination thereof. In at least one embodiment, the code is stored on a computer-readable storage medium in the form of a computer program storing a plurality of computer-readable instructions that can be executed by one or more processors. In at least one embodiment, the computer-readable storage medium is a non-transitory computer-readable medium. In at least one embodiment, at least some of the computer-readable instructions that can be used to perform the process 500 are not stored using only transient signals (e.g., propagated transient electrical or electromagnetic transmissions). The non-transitory computer-readable medium does not necessarily include non-transitory data storage circuits (e.g., buffers, caches, and queues) within the transceiver of the transient signal. Process 500 may be implemented in the context of various systems and methods described elsewhere in this disclosure, such as in conjunction with Figures 1 to 4 In at least one embodiment, process 500 or a portion thereof is implemented in conjunction with a tire pressure monitoring system (TPMS) sensor.

[0051] In various embodiments, process 500 begins with Figure 5 , and begins at step 502, where the system (e.g., TPMS sensor) executing process 500 detects the start of a new drive cycle or manual learning trigger. The manual learning trigger can be initiated by a user (e.g., a driver) by pressing a specific sequence or combination of buttons.

[0052] In various embodiments, process 500 includes step 504 to determine a random value. Although a random value is referenced in step 504, it can be a pseudo-random number generated deterministically using a seed value. In general, a random value as discussed herein can be a number that appears sufficiently random but is not necessarily generated using a truly unpredictable process (such as radioactive decay or atmospheric noise). For example, in various embodiments described herein, a pseudo-random number generator can be used to generate the random value.

[0053] In various embodiments, process 500 includes step 506 for determining a temporary pairing PIN and a test value based at least in part on the random value and the pre-shared key. Figure 2Techniques discussed herein determine a test value and a pairing PIN. For example, a TPMS sensor may generate a random value (e.g., using a seed), determine an input value by concatenating the random value with additional data, provide the input value as a message and a pre-shared key as a secret key to an HMAC function that produces an output value, use a first portion of the output value as a test value, and then perform truncation and modulo operations on a second portion of the output value to derive the pairing PIN. In various embodiments, non-overlapping portions of the output value of the HMAC are used to generate a test value and a pairing PIN, which can be used to make the entire protocol more secure.

[0054] In various embodiments, process 500 includes step 508 for broadcasting TPMS data, random values, and test values ​​to nearby vehicles. TPMS data can refer to tire data, such as temperature and pressure measurements. Random values ​​and test values ​​can be derived in the manner referenced above. When the TPMS is in notification mode, a resolvable private address (RPA), a test value, and a random value can be included in the TPMS notification message. The TPMS notification message can be transmitted in plain text, that is, no specific encryption material is required to view the RPA, TPMS data, random values, or test values.

[0055] In various embodiments, process 500 includes step 510 for determining whether the vehicle is connected. In various embodiments, a wireless connection (e.g., using Bluetooth technology) is used to establish a wireless connection between the TPMS sensor and the vehicle. If no connection is detected, process 500 can end immediately. Conversely, if a connection is established, process 500 can proceed to step 512.

[0056] In various embodiments, process 500 includes step 512 of attempting to pair / bind with the vehicle using the derived temporary PIN. As described above, the PIN can be derived from a random number generated or otherwise determined by the TPMS sensor. The vehicle can access the pairing PIN through the test value and the random value of the notification message transmitted by the TPMS sensor. For example, the vehicle can receive the TPMS notification message and extract the random value and the test value. The input value can be generated from the random value, and in some embodiments, the input value is the random value. In some embodiments, the input value is a combination of the random value and deterministic additional data (such as the supported protocol version). The vehicle can then use the input value and the pre-shared key to calculate the output value using the HMAC function. The calculated output value or a portion thereof can be compared with the test value. If the comparison passes, the calculated output value can be used to generate a calculated PIN, which can involve truncation operations, modulo operations, or a combination thereof. In various embodiments, the vehicle is able to successfully calculate the same PIN, which results in a successful authenticated pairing. If the vehicle cannot calculate the same PIN, it can indicate that the received notification is not generated by a real sensor that has access to the pre-shared key.

[0057] In various embodiments, process 500 includes step 514 for determining whether there is a successful authenticated pairing. A successful authenticated pairing may occur when the same PIN is secretly shared between the TPMS sensor and the vehicle through the test value and the random value. If the two entities have the same PIN, the authenticated pairing is successful and process 500 may proceed to step 516; conversely, if the same PIN is not successfully shared with the two entities, the authenticated pairing is unsuccessful and process 500 may terminate immediately.

[0058] In various embodiments, process 500 includes step 516 for establishing a secure connection. The secure connection can be implemented as BLE link layer encryption. The secure connection can be implemented as authenticated encryption, which provides cryptographically verifiable confidentiality and authenticity guarantees.

[0059] In various embodiments, process 500 includes step 518 for receiving a TPMS integrity key (IK) via a secure connection. In various embodiments, the IK is securely shared using a pairing PIN. For example, the pairing PIN may be encrypted using the pairing PIN acting as an encryption key or using an encryption key derived therefrom.

[0060] In various embodiments, process 500 includes step 520 of saving the IK and completing the sensor learning process. Upon completing sensor learning, the TPMS sensor may proceed to a normal TPMS operating mode, wherein TPMS annunciation messages are sent instead of TPMS learning mode messages. Upon completing process 500, the TPMS sensor and vehicle may have successfully completed a mutually authenticated pairing and learning process such that both entities have access to a securely and privately shared pairing PIN and integrity key.

[0061] Figure 6An illustrative example of a process 600 for pairing with a tire pressure monitoring system (TPMS) sensor for bidirectional learning and authentication according to one or more exemplary embodiments of the present disclosure is shown. In at least one embodiment, some or all of the process 600 (or any other process described herein, or a variation and / or combination thereof) is executed under the control of one or more computer systems storing computer executable instructions, and can be implemented as code (e.g., computer executable instructions, one or more computer programs, or one or more applications) that is executed collectively on one or more processors, implemented by hardware, software, or a combination thereof. In at least one embodiment, the code is stored on a computer-readable storage medium in the form of a computer program storing a plurality of computer-readable instructions executable by one or more processors. In at least one embodiment, the computer-readable storage medium is a non-transitory computer-readable medium. In at least one embodiment, at least some of the computer-readable instructions that can be used to perform the process 600 are not stored using only transient signals (e.g., propagated transient electrical or electromagnetic transmissions). The non-transitory computer-readable medium does not necessarily include non-transitory data storage circuits (e.g., buffers, caches, and queues) within the transceiver of the transient signal. Process 600 may be implemented in the context of various systems and methods described elsewhere in this disclosure, such as in conjunction with Figures 1 to 4 In at least one embodiment, process 600 or a portion thereof is co-implemented by a controller system of a vehicle. In various embodiments, steps of process 600 and / or other processes are performed by a vehicle that will utilize a controller system.

[0062] In various embodiments, process 600 begins with Figure 6 , and begins at step 602, where the system executing process 600 (e.g., a controller system of a vehicle) detects the start of a new drive cycle or manual learning trigger. The manual learning trigger can be initiated by a user (e.g., a driver) by pressing a specific sequence or combination of buttons.

[0063] In various embodiments, process 600 includes step 604 for listening for broadcasts from nearby TPMS sensors. In various embodiments, the broadcast messages are wirelessly transmitted using Bluetooth technology. In various embodiments, the announcement data includes tire data, a resolvable private address (RPA), etc. The announcement data can be stored by the vehicle.

[0064] In various embodiments, process 600 includes step 606 for determining the sensor most likely attached to the vehicle. As the annunciation data is collected and stored, it can be analyzed to determine which sensors are emitting data corresponding to the vehicle. For example, the annunciation data can be used in a learning mode to determine whether a sensor is attached to the vehicle and the location where the sensor is most likely attached, such as location FL (front left), FR (front right), RL (rear left), or RR (rear right).

[0065] In various embodiments, process 600 includes step 608 for determining whether the scan is complete. If the scan is not complete, the system can return to step 604 and continue to collect additional sensor data until there is at least one sensor that is determined to be a candidate sensor. Once the scan is complete, process 600 can proceed to step 610.

[0066] In various embodiments, process 600 includes step 610 of calculating a pairing PIN and a test value using a pre-shared key and the announcement data. The learning mode announcement message may include or otherwise encode the test value and the random value. The vehicle may obtain the random value and use the random value to generate an input value. In some cases, the input value is the random value. The input value and the pre-shared secret key may be provided to an HMAC function that calculates an output value. The calculated output value may be used to determine the calculated test value.

[0067] In various embodiments, process 600 includes step 612 for determining whether the calculated test value and the test value received from the learn mode announcement value match. If they are equal, the values ​​match. If the values ​​do not match, process 600 can terminate immediately, or the announcement data can simply be discarded. If the values ​​match, process 600 can proceed to step 614.

[0068] In various embodiments, process 600 includes connecting to the candidate sensor and attempting pairing / bonding using the calculated pairing PIN 614. The pairing / bonding process may be in accordance with the BLE standard and may involve exchanging information using the pairing PIN so that the TPMS sensor may be able to verify that the vehicle possesses the correct PIN.

[0069] In various embodiments, process 600 includes step 616 for determining whether authentication has been successful. In various embodiments, mutual authentication occurs when the TPMS sensor verifies that the vehicle possesses the correct PIN and the vehicle verifies that the TPMS sensor possesses the correct PIN. If not, process 600 can terminate immediately; otherwise, process 600 can proceed to step 618.

[0070] In various embodiments, process 600 includes step 618 for establishing a secure connection. The secure connection can be implemented as BLE link layer encryption. The secure connection can be implemented as authenticated encryption, which provides cryptographically verifiable confidentiality and authenticity guarantees.

[0071] In various embodiments, process 600 includes step 620 for generating a new TPMS integrity key (IK) and exchanging it with the TPMS sensor using a secure connection. The IK may be generated in any suitable manner. In some embodiments, the IK is derived from a pairing PIN.

[0072] In various embodiments, process 600 includes a step 622 for determining whether receipt of the IK is confirmed. In various embodiments, the TPMS sensor sends a confirmation message of successful receipt of the IK. In various embodiments, process 600 includes a step 624 for saving the IK for the sensor and completing sensor learning. In various embodiments, each IK is generated on a per-sensor basis, such that if there are four TPMS sensors, four separate IKs are generated, one for each sensor.

[0073] The machine (e.g., computer system) 700 may include any combination of the components shown. For example, the machine 700 may include a hardware processor 702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a tensor processing unit (TPU) including an artificial intelligence application specific integrated circuit (ASIC), a hardware processor core, or any combination thereof), a main memory 704, and a static memory 706, some or all of which may communicate with each other via an interconnect (e.g., a bus) 708. The machine 700 may also include a power management device 732, a graphics display device 710, an alphanumeric input device 712 (e.g., a keyboard), and a user interface (UI) navigation device 714 (e.g., a mouse). In an example, the graphics display device 710, the alphanumeric input device 712, and the UI navigation device 714 may be a touch screen display. The machine 700 may additionally include a storage device (i.e., a drive unit) 716, a signal generating device 718 (e.g., a data signal), a network interface device / transceiver 720 coupled to an antenna 730, and one or more sensors 728, such as a sound detection sensor (e.g., a microphone), an accelerometer, a magnetometer, a position sensor, etc. The machine 700 may include an output controller 734, such as a serial (e.g., Universal Serial Bus (USB)), parallel or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, other sensors, etc.).

[0074] The storage device 716 may include a machine-readable medium 722 on which is stored one or more sets of data structures or instructions 724 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 724 may also reside, in whole or in part, within the main memory 704, within the static memory 706, or within the hardware processor 702 during execution of the instructions by the machine 700. In an example, one or any combination of the hardware processor 702, the main memory 704, the static memory 706, or the storage device 716 may constitute a machine-readable medium. In various embodiments, one or more machines (e.g., the machine 700) are used to implement a controller system for a vehicle.

[0075] Although machine-readable medium 722 is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (eg, a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 724 .

[0076] Various embodiments may be implemented in whole or in part in software and / or firmware. This software and / or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable the execution of the operations described herein. The instructions may be in any suitable form, such as, but not limited to, source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such computer-readable media may include any tangible, non-transitory medium for storing information in a form that can be read by one or more computers, such as, but not limited to, read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, and the like.

[0077] The term "machine-readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 700; and causing the machine 700 to perform any one or more of the techniques of the present disclosure; or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of machine-readable media may include solid-state memory and optical and magnetic media. In an example, a large-capacity machine-readable medium includes a machine-readable medium having a plurality of particles having a rest mass. Specific examples of large-scale machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

[0078] The instructions 724 may further be transmitted or received over a communication network 726 using a transmission medium via a network interface device / transceiver 720 using any of a number of delivery protocols (e.g., frame relay, Internet Protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Exemplary communication networks may include DOCSIS, fiber optics, a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, a wireless data network (e.g., a wireless network known as The Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards, known as ), IEEE 802.16 series of standards), IEEE 802.15.4 series of standards, and peer-to-peer (P2P) networks, etc. In an example, the network interface device / transceiver 720 may include one or more physical sockets (e.g., Ethernet sockets, coaxial sockets, or telephone sockets) or one or more antennas to connect to the communication network 726. In an example, the network interface device / transceiver 720 may include multiple antennas to communicate wirelessly using at least one of the following: single-input multiple-output (SIMO) technology, multiple-input multiple-output (MIMO) technology, or multiple-input single-output (MISO) technology. The term "transmission medium" should be deemed to include any intangible medium having the following properties: capable of storing, encoding, or carrying instructions for execution by the machine 700; and including digital or analog communication signals or other intangible media for facilitating the communication of such software.

[0079] The operations and processes described and shown above can be implemented or performed in any suitable order when necessary in various embodiments. In addition, in some embodiments, at least a portion of the operations can be performed in parallel. In addition, in some embodiments, less or more operations than the described operations can be performed.

[0080] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The terms "computing device", "user device", "communication station", "station", "handheld device", "mobile device", "wireless device" and "user equipment" (UE) as used herein refer to a wireless communication device such as a cable box, a wearable smart device, a cellular phone, a smart phone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal or other personal communication system (PCS) device. The device may be mobile or fixed.

[0081] As used in this document, the term "communication" is intended to include transmission or reception, or both transmission and reception. This may be particularly useful in claims when describing the organization of data transmitted by one device and received by another device, but requiring only the functionality of one of those devices violates the claims. Similarly, a two-way data exchange between two devices (during which both devices transmit and receive) may be described as "communication" when only the functionality of one of those devices is claimed. The term "communication" as used herein with respect to wireless communication signals includes transmitting wireless communication signals and / or receiving wireless communication signals. For example, a wireless communication unit capable of transmitting wireless communication signals may include a wireless transmitter for transmitting wireless communication signals to at least one other wireless communication unit and / or a wireless communication receiver for receiving wireless communication signals from at least one other wireless communication unit.

[0082] As used herein, unless otherwise indicated, the use of ordinal adjectives "first," "second," "third," etc. to describe common objects indicates merely that different instances of similar objects are mentioned and is not intended to imply that the objects so described must be in a given sequence in time, space, ranking, or in any other manner.

[0083] Some embodiments may be used in conjunction with various devices and systems, such as wearable smart devices, personal computers (PCs), desktop computers, mobile computers, laptop computers, notebook computers, tablet computers, server computers, handheld computers, handheld devices, personal digital assistant (PDA) devices, handheld PDA devices, vehicle-mounted devices, off-vehicle devices, hybrid devices, vehicle devices, non-vehicle devices, mobile or portable devices, consumer devices, non-mobile or non-portable devices, wireless communication stations, wireless communication devices, wireless access points (APs), wired or wireless routers, wired or wireless modems, video devices, audio devices, audio-video (A / V) devices, wired or wireless networks, wireless area networks, wireless video area networks (WVANs), local area networks (LANs), wireless LANs (WLANs), personal area networks (PANs), wireless PANs (WPANs), and the like.

[0084] Some embodiments may be used in conjunction with: one-way and / or two-way radio communication systems, cellular radio-telephone communication systems, mobile phones, cellular phones, cordless phones, personal communication system (PCS) devices, PDA devices including wireless communication devices, mobile or portable global positioning system (GPS) devices, devices including GPS receivers or transceivers or chips, devices including RFID elements or chips, multiple-input multiple-output (MIMO) transceivers or devices, single-input multiple-output (SIMO) transceivers or devices, multiple-input single-output (MISO) transceivers or devices, devices with one or more internal antennas and / or external antennas, digital video broadcasting (DVB) devices or systems, multi-standard radio devices or systems, wired or wireless handheld devices (e.g., smart phones), wireless application protocol (WAP) devices, etc.

[0085] Some embodiments may be used in conjunction with one or more types of wireless communication signals and / or systems that comply with one or more wireless communication protocols, such as DOCSIS, radio frequency (RF), infrared (IR), frequency division multiplexing (FDM), orthogonal FDM (OFDM), time division multiplexing (TDM), time division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee, Ultra-Wideband (UWB), Global System for Mobile Communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE Advanced, Enhanced Data Rates for GSM Evolution (EDGE), etc. Other embodiments may be used in various other devices, systems and / or networks.

[0086] Embodiments according to the present disclosure are particularly disclosed in the attached claims, which relate to methods, storage media, devices, and computer program products, wherein any feature mentioned in one claim category (e.g., method) may also be claimed in another claim category (e.g., system). The dependencies or references in the attached claims are selected for formal reasons only. However, any subject matter resulting from deliberate reference to any previous claim (especially multiple dependencies) may also be claimed, so that any combination of claims and their features is disclosed and may be claimed, regardless of the dependencies selected in the attached claims. The subject matter that may be claimed includes not only the combination of features set forth in the attached claims, but also any other combination of features in the claims, wherein each feature mentioned in the claims may be combined with any other feature in the claims or with a combination of other features. In addition, any of the embodiments and features described or depicted herein may be claimed in a separate claim and / or in any combination with any embodiment or feature described or depicted herein or with any feature of the attached claims.

[0087] The above description of one or more embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0088] Certain aspects of the present disclosure are described above with reference to block diagrams and flow charts of systems, methods, devices and / or computer program products according to various embodiments. It should be understood that one or more blocks of the block diagrams and flow charts and combinations of blocks in the block diagrams and flow charts may be implemented by computer executable program instructions, respectively. Likewise, according to some embodiments, some blocks of the block diagrams and flow charts may not necessarily need to be executed in the order presented, or may not necessarily need to be executed at all.

[0089] These computer executable program instructions can be loaded onto a special purpose computer or other specific machine, processor, or other programmable data processing device to produce a specific machine, so that the instructions executed on the computer, processor, or other programmable data processing device create a device for implementing one or more functions specified in one or more flowchart boxes. These computer program instructions can also be stored in a computer-readable storage medium or memory, which can guide the computer or other programmable data processing device to act in a specific manner when executed, so that the instructions stored in the computer-readable storage medium produce a product including an instruction device for implementing one or more functions specified in one or more flowchart boxes. As an example, some embodiments may provide a computer program product, which includes a computer-readable storage medium having a computer-readable program code or program instructions implemented therein, and the computer-readable program code is suitable for being executed to implement one or more functions specified in one or more flowchart boxes. Computer program instructions can also be loaded onto a computer or other programmable data processing device to cause a series of operating elements or steps to be executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide elements or steps for implementing the functions specified in one or more flowchart boxes.

[0090] Therefore, the blocks of the block diagrams and flow charts support a combination of means for performing the specified functions, a combination of elements or steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow charts and the combination of blocks in the block diagrams and flow charts can be implemented by a dedicated hardware-based computer system or a combination of dedicated hardware and computer instructions that performs the specified functions, elements or steps.

[0091] Embodiments of the systems, devices, apparatuses and methods disclosed herein may include or utilize a special or general-purpose computer, which includes computer hardware, such as, for example, one or more processors and system memory as discussed herein. Computer executable instructions include, for example, instructions and data, which, when executed at a processor, cause a general-purpose computer, a special-purpose computer or a special-purpose processing device to perform a specific function or function group. Embodiments of the apparatus, systems and methods disclosed herein may communicate via a computer network. A "network" is defined as one or more data links that support the transmission of electronic data between a computer system and / or a module and / or other electronic devices.

[0092] Although the subject matter has been described in language specific to structural features and / or methodological acts, it should be understood that the subject matter defined in the appended claims may not necessarily be limited to the features or acts described above. Rather, the described features and acts are disclosed as exemplary forms of implementing the claims.

[0093] Although various embodiments of the present disclosure have been described above, it should be understood that various embodiments of the present disclosure are presented only by way of example and not by way of limitation. It will be understood by those skilled in the relevant art that various changes in form and detail may be made without departing from the spirit and scope of the present disclosure. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above exemplary embodiments, but should only be limited according to the attached claims and their equivalents. The foregoing description has been presented for the purpose of illustration and description. The foregoing description is not intended to be exhaustive or to limit the present disclosure to the precise form disclosed. In view of the above teachings, many modifications and variations are possible. In addition, it should be noted that any or all of the aforementioned optional embodiments may be used in any desired combination to form additional hybrid embodiments of the present disclosure. For example, any one of the functionalities described with respect to a particular device or component may be performed by another device or component. Unless otherwise specifically stated or otherwise understood in context when used, conditional languages ​​such as, in particular, "can", "may", "can" or "may" are generally intended to express that certain embodiments may include certain features, elements and / or steps, while other embodiments may not include certain features, elements and / or steps. Thus, such conditional language is generally not intended to imply that each feature, element, and / or step is in any way required for one or more embodiments.

[0094] In one aspect of the invention: each of the one or more learn mode advertisements includes a first resolvable private address (RPA); and each of the one or more TPMS advertisements includes a second RPA.

[0095] In one aspect of the invention, the method includes: changing the second RPA to a third RPA; and resolving the third RPA using the IRK.

[0096] In one aspect of the invention, deriving the pairing PIN and the test value includes: generating an HMAC (hash-based message authentication code) output using the random value and the pre-shared key; determining a first portion of the random value as the test value; truncating a second portion of the random value to produce a truncated HMAC output; and performing a modulo operation on the truncated HMAC output to produce the pairing PIN.

[0097] In one aspect of the invention, the first portion and the second portion are non-overlapping portions of the HMAC output.

[0098] In one aspect of the invention, the one or more learn mode advertisements are transmitted in clear text.

Claims

1. A tire pressure monitoring system (TPMS) sensor, comprising: One or more processors and memory, the memory storing executable instructions, the executable instructions causing the TPMS sensor to perform the following operations: Determine the random value; determining an input value based at least in part on the random value; deriving an output value based at least in part on the input value and a pre-shared secret key also accessible to the vehicle; determining a test value based at least in part on a first portion of the output value; determining a pairing PIN based at least in part on a second portion of the output value; Broadcasting at least one learning mode announcement, the at least one learning mode announcement comprising: Resolvable Private Address (RPA); sensor data measured by the TPMS sensor; said random value; and the test value; determining that the TPMS sensor is connected to the vehicle; performing a pairing process with the vehicle, the pairing process including authenticating that the vehicle has access to the pairing PIN; and Depending on the pairing process successfully authenticating the vehicle: establishing a secure connection with the vehicle; and An integrity key (IK) is received from the vehicle via the secure connection.

2. The TPMS sensor of claim 1 , wherein the executable instructions include additional instructions that further cause the TPMS sensor to: Broadcasting a TPMS notification, the TPMS notification including: Second RPA; second sensor data measured by the TPMS sensor; and A message authentication code (MAC) is determined based at least in part on the second sensor data and using the IK. 3 . The TPMS sensor of claim 1 , wherein the input value includes the random value and additional data.

4. The TPMS sensor of claim 1, wherein the output value is derived using an HMAC (Hash-based Message Authentication Code) function. 5 . The TPMS sensor of claim 1 , wherein the first portion and the second portion are non-overlapping portions of the output value. 6 . The TPMS sensor of claim 1 , wherein the pairing PIN is determined by at least truncating the output value to determine the second portion and applying a modulo operation to the second portion to generate the pairing PIN. 7 . The TPMS sensor of claim 1 , wherein the at least one learn mode advertisement is broadcast in clear text.

8. A non-transitory computer-readable storage medium storing executable instructions that, as a result of being executed by one or more processors of a controller system of a vehicle, cause the controller system to at least perform the following operations: Receiving one or more learn mode notifications from a tire pressure monitoring system (TPMS) sensor, one of the one or more learn mode notifications comprising: Resolvable Private Address (RPA); sensor data measured by the TPMS sensor; Random value; and Test value; determining that the TPMS sensor may be attached to the vehicle based at least in part on the sensor data; determining a calculated test value using the random value and a pre-shared key also accessible to the TPMS sensor; determining that the calculated test value matches the test value received from the TPMS sensor; determining a pairing PIN using the random value and the pre-shared key; performing a pairing process with the TPMS sensor using the pairing PIN; establishing a secure connection with the TPMS sensor; and An integrity key (IK) is provided to the TPMS sensor via the secure connection.

9. The non-transitory computer readable storage medium of claim 8, wherein the executable instructions further cause the controller system to: Receive a TPMS notification, the TPMS notification including: Second RPA; second sensor data measured by the TPMS sensor; and Message Authentication Code (MAC); determining a calculated MAC based at least in part on the second sensor data and using the IK; as well as The TPMS notification is determined to be authentic based at least in part on the calculated MAC matching the MAC received in the TPMS notification.

10. The non-transitory computer-readable storage medium of claim 8, wherein the calculated test value is determined at least by: determining an input value based at least in part on the random value; using an HMAC function to calculate an output value based at least in part on the input value and the pre-shared key; and The test value is extracted from at least a first portion of the output value.

11. The non-transitory computer-readable storage medium of claim 10, wherein the pairing PIN is determined based at least in part on a second portion of the output value.

12. The non-transitory computer-readable storage medium of claim 11, wherein the first portion and the second portion do not overlap.

13. The non-transitory computer-readable storage medium of claim 8, wherein the one or more learning mode advertisements are received using Bluetooth Low Energy (BLE).

14. A method comprising: A random value is determined by a tire pressure monitoring system (TPMS) sensor; deriving, by the TPMS sensor, a pairing PIN and a test value based at least in part on the random value and a pre-shared key; transmitting, by the TPMS sensor, one or more learn mode announcements, the one or more learn mode announcements comprising first sensor data, the random value, and the test value; determining, by a controller system of the vehicle, that the TPMS sensor is an attachment candidate sensor; determining, by the controller system of the vehicle, the pairing PIN using the random value, the test value, and the pre-shared key; performing an authenticated pairing process between the controller system and the TPMS sensor; establishing a secure connection between the controller system and the TPMS sensor; as well as An integrity key (IK) and an identity resolution key (IRK) are exchanged between the controller system and the TPMS sensor.

15. The method of claim 14, further comprising: transmitting, by the TPMS sensor, one or more TPMS annunciations, the one or more TPMS annunciations comprising second sensor data and a message authentication code (MAC) based at least in part on the second sensor data; as well as The authenticity and integrity of the one or more TPMS advisories are determined by the controller system of the vehicle.

Citation Information

Cited By

  • Commercial vehicle trailer TPMS sensor ID automatic identification method and system

    CN120769261A