Securely pair in-vehicle wireless sensors with a central device

Abstract

Disclosed are methods, systems, apparatus, and computer program products for securely pairing a vehicle-mounted wireless sensor with a central device. In a specific embodiment, securely pairing a vehicle-mounted wireless sensor with a central device according to the present disclosure includes pairing the vehicle sensor device with a vehicle control system (VCS) using a pre-shared passkey. The pre-shared passkey is shared between the vehicle sensor device and the VCS via an out-of-band exchange. The embodiment also includes the vehicle sensor device sending an identifier of a resolvable private address (RPA) to the VCS. Additionally, the vehicle sensor device communicates with the VCS using the RPA. In this example embodiment, the RPA is periodically regenerated by the vehicle sensor device.

Description

Background Art

[0001] Wireless vehicle sensors, such as wireless tire pressure monitoring system (TPMS) sensors, have been introduced to provide vehicle sensor data to the vehicle control system via a radio frequency (RF) link. In particular, wireless TPMS sensors have been introduced in most automotive markets worldwide, and many regions have legislated for their use for safety or environmental reasons. The system is designed to alert drivers of underinflated tires. Current systems, such as TPMS, typically use a unidirectional RF link from the sensor to the vehicle to transmit critical data for sensing applications. This data can include pressure, temperature, position, speed / acceleration, a unique identifier (ID), or stimuli. For example, Tire Fill Assist (TFA) is a TPMS feature implemented using the vehicle's current unidirectional RF link. This feature allows the vehicle to communicate the status of the TPMS to the user, for example by using a horn and / or lights as feedback.

[0002] Bluetooth Low Energy (BLE) is a common short-range wireless standard used for two-way communication with wireless vehicle sensors. However, for many wireless vehicle sensors, having a user interface for pairing may not be practical. Allowing the vehicle to automatically learn its sensors during a driving cycle is not ideal. This process can take a long time to complete and is typically performed only while the vehicle is in motion. This results in the vehicle being unaware of the installed sensors for a period of time and unable to warn of pressure deviations. Therefore, the pairing process needs to be completed at the factory or other installation location. However, when BLE devices are widely used in vehicles, there may be many BLE devices transmitting simultaneously (for example, in a tire shop or production line setting), which means there will be significant crosstalk. Therefore, it can be very difficult or impossible to know which sensor is the intended target for pairing. Summary of the Invention

[0003] Embodiments according to the present disclosure are intended to securely pair on-vehicle wireless sensors with a central device. To pair wireless sensors with a vehicle control system at a vehicle assembly plant or other installation location, a pairing tool is used for the out-of-band exchange of a shared pass key. Before completing the pairing process, the pairing tool is used to exchange a shared pass key between the wireless sensor and the vehicle control system. In an example embodiment, the vehicle control system generates the pass key and provides the pass key to the pairing tool, which wirelessly transmits the pass key to the wireless sensor. In other embodiments, the pass key can be generated by the wireless sensor or the pairing tool. During the pairing process, the pass key exchanged in-band is compared with the pass key exchanged out-of-band to verify that the correct wireless sensor is being paired with the vehicle control system. Thus, a pass key verification mechanism can be implemented in wireless vehicle sensors without the need for a physical interface or display on the wireless sensor device. Pass key verification allows the vehicle control system to clearly identify the device as the pairing target.

[0004] To pair a wireless sensor with a wireless mobile device (e.g., a user's smartphone, tablet, smartwatch, etc.), the vehicle control system is configured to facilitate the exchange of identity information between the wireless sensor and the mobile device. A mobile device that has been paired with a vehicle can request the vehicle control system to provide identity information for pairing with the wireless sensor. The vehicle control system can provide the identity information required for the mobile device to initiate a direct pairing process with the wireless sensor. The vehicle control system can also provide the identity information to the wireless sensor so that the wireless sensor can be configured with a list of allowed devices (e.g., a whitelist) for filtering connection requests from the device. Thus, the identity credentials used to pair the wireless sensor device with the user's smart device can be shared by the vehicle control system that has been paired with each device.

[0005] In a particular embodiment, securely pairing a vehicle-mounted wireless sensor with a central device according to the present disclosure includes pairing the vehicle sensor device with a vehicle control system (VCS) using a pre-shared passkey. The pre-shared passkey is shared between the vehicle sensor device and the VCS via an out-of-band exchange. This embodiment also includes the vehicle sensor device sending an identifier, such as an identity resolving key (IRK) for a resolvable private address (RPA), to the VCS. Additionally, the vehicle sensor device communicates with the VCS using the RPA so that the VCS can use the identifier to resolve the address of the vehicle sensor device. In this example embodiment, the RPA is periodically regenerated by the vehicle sensor device.

[0006] In another embodiment, securely pairing a vehicle-mounted wireless sensor with a central device according to the present disclosure includes a vehicle control system (VCS) pairing the wireless vehicle sensor device using a pre-shared passkey shared between the vehicle sensor device and the central device via an out-of-band exchange. In this example embodiment, the VCS receives an identifier, such as an identity resolution key (IRK) of the vehicle sensor device, associates the identifier with a sensor identifier of the vehicle sensor device, receives a data packet identified by a resolvable private address (RPA) from the vehicle sensor device, and uses the identifier to identify the vehicle sensor device based on the RPA.

[0007] The foregoing and other objects, features, and advantages of the invention will be apparent from the following more particular description of exemplary embodiments of the invention as illustrated in the accompanying drawings, wherein like reference numerals generally represent like parts of exemplary embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1A shows an isometric diagram of a system for securely pairing vehicle-mounted wireless sensors with a central device according to the present disclosure;

[0009] Figure 1B Shown Figure 1A A top view of the system;

[0010] Figure 2 shows a block diagram of an exemplary pairing tool according to the present disclosure;

[0011] Figure 3 A block diagram illustrating an exemplary wireless vehicle sensor device according to the present disclosure is shown;

[0012] Figure 4 shows a block diagram of an exemplary vehicle control system according to the present disclosure;

[0013] Figure 5 A flowchart illustrating an example method for securely pairing an in-vehicle wireless sensor with a central device according to the present disclosure is shown;

[0014] Figure 6 A flowchart illustrating another example method for securely pairing an in-vehicle wireless sensor with a central device according to the present disclosure is shown;

[0015] Figure 7 A flowchart illustrating another example method for securely pairing an in-vehicle wireless sensor with a central device according to the present disclosure is shown;

[0016] Figure 8 A flowchart illustrating another example method for securely pairing an in-vehicle wireless sensor with a central device according to the present disclosure is shown;

[0017] Figure 9 A flowchart illustrating another example method for securely pairing an in-vehicle wireless sensor with a central device according to the present disclosure is shown;

[0018] Figure 10 A flowchart illustrating another example method for securely pairing an in-vehicle wireless sensor with a central device according to the present disclosure is shown;

[0019] Figure 11 A flowchart illustrating another example method for securely pairing an in-vehicle wireless sensor with a central device according to the present disclosure is shown;

[0020] Figure 12 A flowchart illustrating another example method for securely pairing an in-vehicle wireless sensor with a central device according to the present disclosure is shown;

[0021] Figure 13 A flowchart illustrating another example method for securely pairing an in-vehicle wireless sensor with a central device according to the present disclosure is shown;

[0022] Figure 14 A flow chart illustrating another example method for securely pairing an in-vehicle wireless sensor with a central device according to the present disclosure is shown. DETAILED DESCRIPTION

[0023] The terms used herein for the purpose of describing a particular example are not intended to limit further examples. Whenever a singular form such as "a", "an" and "the" is used and only a single element is neither explicitly nor implicitly defined as mandatory, further examples may also use plural elements to implement the same function. Similarly, when a function is subsequently described as being implemented using multiple elements, further examples may use a single element or processing entity to implement the same function. It should also be understood that the terms "comprises", "comprising", "includes" and / or "including" specify the presence of the features, integers, steps, operations, processes, behaviors, elements and / or parts when used, but do not exclude the presence or addition of one or more other features, integers, steps, operations, processes, behaviors, elements, parts and / or any groups thereof.

[0024] It should be understood that when an element is referred to as being "connected" or "coupled" to another element, these elements may be directly connected or coupled via one or more intermediate elements. If two elements A and B are combined using "or", this should be understood to disclose all possible combinations, i.e., only A, only B, and A and B. An alternative wording for the same combination is "at least one of A and B". The same applies to combinations of more than two elements.

[0025] Therefore, although the further examples are capable of various modifications and alternative forms, some specific examples thereof are shown in the figures and will be described in detail later. However, this detailed description does not limit the further examples to the specific forms described. The further examples may encompass all modifications, equivalents, and alternatives that fall within the scope of this disclosure. Throughout the description of the drawings, like numbers refer to similar or analogous elements that can be implemented identically or in modified form when compared to each other while providing the same or similar functions.

[0026] from Figure 1A and Figure 1B Initially, exemplary methods, apparatuses, and computer program products for securely pairing vehicle-mounted wireless sensors with a central device according to the present disclosure are described with reference to the accompanying drawings. Figure 1A An isometric diagram of a system (100) for securely pairing vehicle-mounted wireless sensors with a central device according to the present disclosure is shown. Figure 1B Shown Figure 1A Top view of the system. Figure 1A and Figure 1B The system includes a vehicle (101) equipped with a tire (103) and a wireless vehicle sensor device (105). Figure 1A and Figure 1B The embodiment shows that the wireless vehicle sensor device is a tire monitoring device (e.g., a TPMS sensor) for a tire (103), but it should be understood that the wireless vehicle sensor device (105) can be any vehicle sensor device configured for wireless communication, including but not limited to brake pad wear sensors, seat buckle sensors, and other wireless automotive sensors (109). In a specific embodiment, the wireless vehicle sensor device (105) can be a tire pressure monitoring system (TPMS) sensor and measures operating characteristics of the tire, such as tire pressure, tire temperature, and motion characteristics, and transmits the collected data to a vehicle control system (VCS) (107).

[0027] The VCS (107) controls various components and systems within the vehicle. For example, the VCS (107) may include multiple electronic control units (ECUs) configured to control one or more vehicle subsystems. An ECU is often referred to as the vehicle's "computer" and may be a central control unit or may be collectively referred to as one or more vehicle subsystem control units. In a particular embodiment, one of the subsystems in the VCS (107) is a TPMS that receives tire pressure and other measurements from wireless vehicle sensor devices (105). Other subsystems may include an engine control module (ECM), a powertrain control module (PCM), a transmission control module (TCM), a body control module (BCM), a central timing module (CTM), a general electronic module (GEM), a remote keyless entry module, and / or a suspension control module (SCM). In an embodiment according to the present disclosure, the VCS (107) includes a BCM including an antilock braking system (ABS) and an electronic stability program (ESP). Alternatively, the VCS (107) may include a telematics control unit (TCU) independent of vehicle-based sensors (e.g., aftermarket systems).

[0028] The wireless vehicle sensor device (105) may be equipped with a wireless transceiver for bidirectional wireless communication with the VCS (107), as described in more detail below. The VCS (107) may similarly be equipped with a wireless transceiver for bidirectional wireless communication with each wireless vehicle sensor device (105), as described in more detail below. The bidirectional wireless communication may be implemented using a communication technology such as Bluetooth Low Energy, Bluetooth Smart, or other low-power bidirectional communication technology designed to conserve consumed energy. Alternatively, the wireless vehicle sensor device (105) may include a unidirectional transmitter configured to transmit signals to the VCS (107).

[0029] The wireless vehicle sensor device (105) can be identified by a unique identification code (also referred to herein as a sensor identifier (ID)). For example, the sensor ID can be a Media Access Control (MAC) address of the wireless vehicle sensor device (105) or its communication component. As another example, the sensor ID can be a name, serial number, or other unique identifier. The sensor ID can be included in each transmission frame or can be associated with a specific transmission channel. However, when the vehicle sensor device (105) is installed on the vehicle (101) (e.g., on a vehicle assembly line or at a dealership), the wireless vehicle sensor device (105) must first be paired with the VCS (107). In a production environment, there may be many wireless sensors publishing their respective sensor IDs, and the VCS (107) must be able to associate the published sensor IDs with specific wireless sensors. In one example of a traditional Bluetooth pairing process, a Generic Access Profile (GAP) central device can generate an access code that is either displayed on the screen of the pairing device and confirmed by a technician, or manually entered by a technician into the physical interface of the pairing device. However, due to the compact size and embedded nature of the vehicle sensor, the vehicle sensor may not have a display for displaying the access code or a physical interface for entering the access code. In certain embodiments according to the present disclosure, a wireless pairing tool (113) (e.g., a handheld device or an assembly line station) is used to facilitate an out-of-band exchange of a shared passkey between the wireless vehicle sensor device (105) and the VCS (107), as will be explained in detail below.

[0030] After the vehicle (101) is owned by the owner, the user (e.g., the owner or a service technician) may wish to use the user's wireless device (115) (e.g., a smartphone) to directly initiate two-way communication with the wireless vehicle sensor device (105). Direct communication with the wireless vehicle sensor may be advantageous, for example, when the wireless vehicle sensor device (105) is a TPMS sensor configured to send tire inflation assist (TFA) data. However, in order to pair the wireless vehicle sensor device (105) with the user's wireless device (115), the user's wireless device (115) must also be able to identify the specific wireless vehicle sensor device (105). This identification process may be difficult due to crosstalk between other vehicle sensors and due to the security protocols implemented by the wireless vehicle sensor device (105). In certain embodiments according to the present disclosure, the VCS (107) facilitates the exchange of identity credentials between the wireless vehicle sensor device (105) and the user's wireless device (115), as will be explained in detail below.

[0031] constitute Figure 1A and Figure 1B The arrangement of the devices of the exemplary system shown is for explanation and not for limitation. As will be appreciated by those skilled in the art, a data processing system useful according to various embodiments of the present disclosure may include: Figure 1A and Figure 1B Additional servers, routers, other devices, and peer-to-peer architecture not shown. Figure 1A and Figure 1B Devices and other data processing systems may utilize communication protocols according to embodiments of the present disclosure, including but not limited to Transmission Control Protocol (TCP), Internet Protocol (IP), Bluetooth, Near Field Communication, Controller Area Network (CAN), Local Interconnect Network (LIN), Serial Peripheral Interface (SPI), FlexRay, and other protocols that will occur to those skilled in the art. Figure 1A and Figure 1B Various embodiments of the present disclosure may be implemented on a variety of hardware platforms in addition to the ones shown.

[0032] To further illustrate, Figure 2 A schematic diagram illustrating an exemplary implementation of a pairing tool (200) for securely pairing a vehicle-mounted wireless sensor with a central device according to an embodiment of the present disclosure is shown. Figure 2 The pairing tool (200) may include a controller (201), a memory (203), a transceiver (205), an antenna (207), and a vehicle communication bus interface (209). In some embodiments, the pairing tool (200) may further include a low frequency transmitter (211) configured to transmit a wake-up signal (e.g., a 125 kHz exciter signal for a low frequency system of a wireless vehicle sensor device).

[0033] The controller (201) of the pairing tool (200) may be configured to facilitate the wireless vehicle sensor device (e.g., Figure 3 The wireless vehicle sensor device (300) and the VCS (e.g., Figure 4The invention provides a method for exchanging shared passkeys between a pairing tool (200) and a VCS (400) of the present invention, and may include a suitably programmed processor, such as a dedicated microprocessor or microcontroller, or other programmable processing device. Standard components such as random access memory (RAM), analog-to-digital converter (ADC), input / output (I / O) interface, clock and central microprocessor (all not shown) may be provided, and these components are typically integrated into a single chip. Alternatively or additionally, a custom microcontroller such as an application specific integrated circuit (ASIC), a digital signal processor (DSP), a programmable logic array (PLA) such as a field programmable gate array (FPGA), or other data computing units according to the present disclosure may be used. For example, the shared passkey may be a randomly generated code or a sequential code for identifying a wireless vehicle sensor among a plurality of wireless vehicle sensors, and may be generated by any one of the pairing tool (200), the wireless vehicle sensor or the VCS. As another example, the shared passkey may be a VCS security parameter.

[0034] The controller (201) of the pairing tool (200) can be configured to send a shared pass key to the VCS when the pass key is generated by the pairing tool (200) or the wireless vehicle sensor device. The controller (201) of the pairing tool can also be configured to send a shared pass key to the wireless sensor device when the pass key is generated by the pairing tool (200) or the VCS or is a security parameter of the VCS. In a particular embodiment, the controller (201) of the pairing tool (200) can receive the pass key from the VCS via the transceiver (205) or the vehicle communication bus interface (209) and can store the pass key in the memory (203). The controller (201) of the pairing tool (200) can then send the pass key to the wireless vehicle sensor via the transceiver (205).

[0035] The transceiver (205) of the pairing tool can be coupled to the controller (201) and the antenna (207) and can be configured for two-way wireless communication with the wireless sensor device and, in some embodiments, with the VCS. For example, once the transceiver is configured to communicate with the VCS, the transceiver can be used to transmit tire parameters (e.g., tire pressure) to the VCS and receive vehicle parameters and configuration parameters from the VCS. The transceiver (233) can be configured to transmit the sensor ID to a remote device, such as an activation tool or activation station in an assembly line. The transceiver (205) can be configured to operate within a specific RF band (e.g., the Industrial, Scientific and Medical (ISM) 2.4 GHz band having a frequency range of 2.4 GHz to 2.5 GHz, including an unlicensed portion of the RF spectrum). In a specific embodiment, the transceiver (205) can be a Bluetooth protocol transceiver, such as a Bluetooth low energy transceiver or a Bluetooth Smart transceiver operating between 2.4 GHz and 2.4835 GHz. In an embodiment, the transceiver (205) may also be configured to send a 2.4 GHz band wake-up signal to a low power receiver of the wireless sensor device to transition the wireless sensor device from a standby state to an active state, in which the transceiver of the wireless sensor device is online.

[0036] To further illustrate, Figure 3 A diagram illustrating an exemplary implementation of a wireless vehicle sensor device (300) for securely pairing an onboard wireless sensor with a central device according to an embodiment of the present disclosure. Figure 3 The wireless vehicle sensor device (300) may include a controller (301), a memory (303), a battery (305), a transceiver (323), a wake-up module (325), and an antenna (307). In a particular embodiment, the wireless vehicle sensor device may be a tire monitoring device and may include one or more sensors (309), such as a pressure sensor (e.g., a piezoresistive transducer or a piezoelectric or capacitive-based pressure sensor for measuring air pressure in a corresponding tire), a temperature sensor, and a motion sensor (e.g., an accelerometer responsive to acceleration and / or changes in acceleration experienced during rotation of the corresponding tire).

[0037] The controller (301) of the wireless vehicle device (300) may be configured to connect the wireless vehicle device (300) to a VCS (e.g., Figure 4 As will be explained below, the controller (301) of the wireless vehicle device (300) can be configured to pair with a pairing tool (e.g., Figure 2The controller (301) of the wireless vehicle device (300) can communicate with the pairing tool (200) to send or receive a shared passkey for pairing with the VCS. As will be explained below, the controller (301) of the wireless vehicle device (300) can also be configured to pair with a user device (e.g., a smartphone) and provide sensor data (e.g., tire inflation assistance data) to the user device. The controller (301) of the wireless vehicle device (300) can include a suitably programmed processor, such as a dedicated microprocessor or microcontroller, or other programmable processing device. Standard components such as random access memory (RAM), analog-to-digital converters (ADCs), input / output (I / O) interfaces, clocks, and a central microprocessor (all not shown) can be provided, typically integrated onto a single chip. Alternatively or additionally, a custom microcontroller such as an application specific integrated circuit (ASIC), a digital signal processor (DSP), a programmable logic array (PLA) such as a field programmable gate array (FPGA), or other data computing unit according to the present disclosure can be used.

[0038] The transceiver (323) of the wireless vehicle sensor device (300) can be coupled to the controller (301) and the antenna (307) and can be configured for bidirectional wireless communication with other wireless modules, including but not limited to a vehicle control system (VCS), a wireless pairing tool, and a user device (e.g., a smartphone). For example, to pair with a VCS, the transceiver (323) and the wake-up module (325) can be used to communicate with the wireless pairing tool to send or receive a shared pass key as part of an out-of-band exchange of a shared pass key. As another example, the transceiver (323) can be used to share identity information with the VCS during the pairing process. As yet another example, once the transceiver (323) is paired with the wireless transceiver of the VCS, the transceiver (323) can be used to send sensor data (e.g., tire pressure) to the VCS and receive vehicle-provided parameters (e.g., identity information of the authentication device) and configuration parameters from the VCS. As yet another example, the transceiver (323) may be used to communicate with an authentication device, such as a user device, once the transceiver (323) has received the authentication device's identity information.

[0039] The transceiver (323) can be configured to operate within a specific RF frequency band, such as the ISM 2.4 GHz band having a frequency range of 2.4 GHz to 2.5 GHz, which includes an unlicensed portion of the RF spectrum. In certain embodiments, the transceiver (323) can be a Bluetooth protocol transceiver, such as a Bluetooth low energy transceiver or a Bluetooth Smart transceiver operating between 2.4 GHz and 2.4835 GHz. In other embodiments, the transceiver (323) can be other types of low-power radio frequency communication technologies designed to conserve energy consumed in tire monitoring devices.

[0040] The wake-up module (325) can be configured to receive an activation signal from a wireless pairing tool or other remote device. In an embodiment, the wake-up module can be a low frequency (LF) system comprising an LF coil with an associated tuning capacitor, an LF amplifier circuit, and a decoding circuit (all not shown). The LF system can detect a signal (e.g., a 125kHz signal) from a remote device via the LF coil and provide a wake-up signal to the controller (301). In another embodiment, the wake-up module (325) can be a low power receiver configured to receive an activation signal from a wireless pairing tool or other remote device and provide a wake-up signal to the controller (301). The low power receiver can be configured to communicate within the same RF band (i.e., the ISM 2.4 GHz band, with a frequency range of 2.4 GHz to 2.5 GHz) as the transceiver (323). Thus, a remote device such as a pairing tool or activation station in an assembly line can use the same transceiver used by the remote device to transmit an activation signal to the low power receiver to communicate with other sensors and devices (e.g., other Bluetooth protocol sensors). Therefore, no separate activation system (eg, LF system) is required to activate the wireless vehicle sensor device (300).

[0041] The memory (305) can be a non-volatile memory (e.g., flash memory) that stores sensor data, configuration parameters, security credentials, and / or local identifiers such as identity resolution keys (IRKs). The memory (305) can also store a data structure containing an allowed device list, which indicates a list of sensor IDs from which connection requests can be accepted. For example, the allowed device list can include devices that have been authenticated by the VCS. The allowed device list can also store a peer IRK for each sensor ID.

[0042] The wireless vehicle sensor device (300) may further include a communication interface (335) for organizing data according to a communication protocol for transmitting and receiving data via the transceiver (323). For example, the communication interface (335) may encapsulate the data in a data packet according to the Bluetooth protocol. The wireless vehicle sensor device (300) may further include a power interface (not shown) for supplying power received from the battery (305) to various components of the wireless vehicle sensor device (300).

[0043] The battery (305) can provide power to the power interface of the wireless vehicle sensor device (300). However, it is contemplated that other power sources (e.g., thermoelectric or piezoelectric generators, electromagnetic induction devices, and / or other energy harvesters) can be used instead of or in addition to the battery (305).

[0044] The antenna (307) can be used by the wireless vehicle sensor device (300) to transmit and receive RF signals. The antenna (307) can be coupled to the transceiver (323) for transmitting and receiving RF signals. The antenna (307) can also be coupled to the wake-up module (325) for receiving an RF activation signal.

[0045] In a particular embodiment, the wireless vehicle sensor device (300) can be installed on a vehicle at a vehicle dealership, tire dealership, repair shop, or vehicle original equipment manufacturer (OEM) assembly line. When the wireless vehicle sensor device (300) is activated and installed on or in a vehicle, the wireless vehicle sensor device (300) has not yet been paired with the vehicle's VCS. To pair with the VCS, the wireless vehicle sensor device (300) can send a pre-shared passkey along with the sensor ID of the wireless vehicle sensor device (300) to the wireless transceiver of the VCS. The pre-shared passkey can be sent during one or more communication frames sent from the wireless vehicle sensor device (300) to the VCS and can also be included in subsequent data packets. The VCS can then use the pre-shared passkey to identify the wireless vehicle sensor device (300) and associate the sensor ID (e.g., MAC address) of the wireless vehicle sensor device (300) with the identity of the sensor.

[0046] To facilitate sharing of a pre-shared passkey prior to pairing, the wireless vehicle sensor device (300) may be configured to receive a pre-shared passkey from a wireless pairing tool (e.g., Figure 2 The pairing tool (200) of the wireless vehicle sensor device (300) sends or receives a pre-shared pass key. For example, the shared pass key can be a randomly generated code or a sequential code for identifying the wireless vehicle sensor device (300) among a plurality of wireless vehicle sensors, and can be generated by any one of the pairing tool, the wireless vehicle sensor device (300), or the VCS. As another example, the shared pass key can be a VCS security parameter. The controller (301) of the wireless vehicle sensor device (300) can be configured to send the shared pass key to the pairing tool when the pass key is generated by the wireless vehicle sensor device (300). The controller (301) of the wireless vehicle sensor device (300) can also be configured to receive the shared pass key from the pairing tool when the pass key is generated by the pairing tool or the VCS or is a security parameter of the VCS.

[0047] In a particular embodiment, the controller (301) of the wireless vehicle sensor device (300) can receive a shared passkey generated by the VCS from the pairing tool via the transceiver (323) or the wake-up module (325). That is, the VCS can generate the shared passkey and provide the shared passkey to the pairing tool via a wired or wireless vehicle communication bus interface with the pairing tool, and the pairing tool can wirelessly send the shared passkey to the transceiver (323) or the wake-up module (325) of the wireless vehicle sensor device (300). The controller (301) can store the shared passkey generated by the VCS and received from the pairing tool in the memory (303) of the wireless vehicle sensor device (300). To pair the wireless vehicle sensor device (300) with the VCS, the wireless vehicle sensor device (300) can send the shared passkey to the VCS in a data packet containing the sensor ID of the wireless vehicle sensor device (300).

[0048] To enhance privacy, the controller (301) of the wireless vehicle sensor device (300) can also be configured to generate a resolvable private address (RPA) and use the RPA instead of the sensor ID to send communication data packets. The RPA can be generated based on a random number and a secret identity resolution key (IRK). As part of the pairing process, the IRK can be provided by the wireless vehicle sensor device (300) to the VCS so that the VCS can confirm the sensor ID by decoding the RPA using the IRK, thereby identifying the wireless vehicle sensor device (300). Therefore, the wireless vehicle sensor device (300) can periodically regenerate an RPA that can be decoded by the VCS, while preventing the wireless vehicle sensor device (300) from being tracked by unauthorized devices.

[0049] In order to pair the wireless vehicle sensor device (300) with an external wireless device that is not part of the VCS (e.g., a user's smartphone), the external wireless device must also have an IRK to identify the wireless vehicle sensor device (300) based on the published RPA. In addition, the wireless vehicle sensor device (300) can be configured to reject connection requests from unauthorized or unrecognized devices and thus can only allow connection requests from devices that have been added to the allowed device list. The controller (301) of the wireless vehicle sensor device (300) can be configured to receive the identity credentials of the external wireless device from the VCS and store the identity credentials on the allowed device list in the memory (303). For example, the received identity credentials can be the device ID of the external wireless device and, if it implements RPA, can be the IRK of the external wireless device. Subsequently, when a connection request is received from the external wireless device, the controller (301) of the wireless vehicle sensor device (300) can be configured to determine that the external wireless device making the request is an allowed device based on the sensor ID and the allowed device list. In response to determining that the requesting device is an allowed device, the controller (301) of the wireless vehicle sensor device (300) may be configured to accept the connection request and pair with the external wireless device.

[0050] To further illustrate, Figure 4 A diagram of an exemplary vehicle control system (VCS) (400) for securely pairing vehicle-mounted wireless sensors with a central device according to an embodiment of the present disclosure is shown. The VCS (400) includes a VCS controller (401) coupled to a memory (403) and a transceiver (405). The VCS controller (401) can be configured to obtain sensor readings related to vehicle operating conditions (e.g., from a central device). Figure 3 As will be explained below, the VCS controller (401) may also be configured to communicate with a pairing tool (e.g., Figure 2The VCS controller (401) may be configured to communicate with a pairing tool (200) to send or receive a shared passkey for pairing with the wireless vehicle sensor device. As will be explained below, the controller (401) of the VCS (400) may also be configured to pair with an external user device (e.g., a smartphone) and facilitate the exchange of identity credentials between the external user device and the wireless vehicle sensor device. For example, the controller (401) may provide configuration parameters to the wireless vehicle sensor device via the transceiver (405) for adding the external wireless device to a list of allowed devices, and the controller (401) may provide identity information of the wireless vehicle sensor device to the external wireless device via the transceiver (405). The VCS controller (401) may include or implement a microcontroller, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a programmable logic array (PLA) such as a field programmable gate array (FPGA), or other data computing unit according to the present disclosure. Sensor readings and data received from the wireless vehicle sensor device may be stored in the memory (403). The memory (403) may be a non-volatile memory, such as flash memory. For example, the VCS (400) may obtain vehicle operating condition data, such as sensor readings, from onboard sensors and / or vehicle tires.

[0051] To perform two-way wireless communication with a wireless vehicle sensor device, a pairing tool, and an external wireless device, the VCS (400) may include a transceiver (405) coupled to the VCS controller (401). For example, to pair with the wireless vehicle sensor device, the transceiver (405) may be configured to communicate with the wireless pairing tool to send or receive a shared passkey. As another example, once the transceiver (405) is paired with the wireless transceiver of the wireless vehicle sensor device, the transceiver (405) may be configured to receive sensor parameters (e.g., tire pressure) from the wireless vehicle sensor device and to send configuration parameters (e.g., identity information of the authentication device) to the wireless vehicle sensor device. As yet another example, the transceiver (405) may be configured to receive a request from an external device to pair with the wireless vehicle sensor device and to send an IRK for connecting to the wireless vehicle sensor device to the external wireless device.

[0052] The transceiver (405) can be configured to operate within a specific RF frequency band (e.g., the ISM 2.4 GHz band having a frequency range of 2.4 GHz to 2.5 GHz, which includes an unlicensed portion of the RF spectrum). In one embodiment, the transceiver (405) can be a Bluetooth protocol transceiver. The VCS (400) can also include a cloud transceiver (407) for cellular terrestrial communications, satellite communications, or both. For example, the cloud transceiver (407) can be used to transmit tire parameters (e.g., tire pressure) to a remote server. The cloud transceiver (407) can also be used to receive configuration parameters of the vehicle.

[0053] The VCS (400) may also include a controller area network (CAN) interface (409) for communicatively coupling vehicle sensors (417) and devices to the controller (401) (e.g., wheel speed sensors, yaw rate sensors, tilt sensors, and other sensors). The CAN interface (409) may couple an input / output (I / O) port (415) to the controller (401). The port (415) may be used to send or receive a shared pass key. For example, a pairing tool may be connected to the port for inputting or outputting a shared pass key. The CAN interface (409) may also couple a display interface (419) to the controller (401). The display interface (419) may be used to output a marker of a vehicle sensor parameter (e.g., a tire pressure parameter) to a dashboard or display of the vehicle. For example, the display port may be used to output a tire pressure marker to a dashboard or display to alert a driver that a tire monitoring device has detected low tire pressure in a tire.

[0054] In certain embodiments, to pair with a wireless vehicle sensor device, a VCS (400) may receive a pre-shared passkey associated with a unique sensor ID of the wireless vehicle sensor device from a wireless transceiver of the wireless vehicle sensor device (e.g., the wireless vehicle sensor device (300)). The pre-shared passkey may be sent during an initial communication packet sent from the wireless vehicle sensor device to the VCS (400) and may also be included in subsequent packets. The VCS (400) may compare a local instance of the pre-shared key with an instance of the pre-shared key received from the wireless vehicle sensor device to verify the identity of the wireless vehicle sensor device and may store the sensor ID of the wireless vehicle sensor device in a memory (403).

[0055] To facilitate sharing of a pre-shared passkey prior to pairing, the VCS (400) may be configured to receive a pre-shared passkey from a wireless pairing tool (e.g., Figure 2 The pairing tool (200) of the VCS (400) may be configured to send or receive a pre-shared pass key. For example, the shared pass key may be a randomly generated code or a sequential code that can be used to identify the wireless vehicle sensor device among a plurality of wireless vehicle sensors and may be generated by any one of the pairing tool, the wireless vehicle sensor device, or the VCS (400). As another example, the shared pass key may be a VCS security parameter. The controller (401) of the VCS (400) may be configured to send the shared pass key to the pairing tool when the pass key is generated by the VCS (400). The controller (401) of the VCS (400) may also be configured to receive the shared pass key from the pairing tool when the pass key is generated by the pairing tool or the wireless vehicle sensor device.

[0056] In certain embodiments, the controller (401) of the VCS (400) may receive a passkey via the transceiver (405) or the CAN interface (409) and / or may send the passkey to the pairing tool. That is, the controller (401) of the VCS (400) may generate a shared passkey and provide the shared passkey to the pairing tool via a wireless (e.g., Bluetooth) or wired connection, and the pairing tool may wirelessly send the shared passkey to the transceiver of the wireless vehicle sensor device. Subsequently, the controller (401) of the VCS (400) may receive the shared passkey from the wireless vehicle sensor device in a data packet including the sensor ID.

[0057] To enhance privacy, the controller (401) of the VCS (400) may also be configured to receive an IRK of the wireless vehicle sensor device and associate the IRK with a sensor ID stored in a data structure in the memory (405). When a data packet sent using the RPA is received by the controller (401), the IRK may be used to parse the RPA to confirm the sensor ID of the wireless vehicle sensor device that sent the data packet.

[0058] To facilitate pairing of the wireless vehicle sensor device with an external wireless device that is not part of the VCS (400) (e.g., a user's smartphone), the controller (401) of the VCS (400) may be configured to receive a request to connect to the wireless vehicle sensor device from the external wireless device via the transmitter (405) and provide the external wireless device with the sensor ID of the wireless vehicle sensor device obtained during pairing with the wireless vehicle sensor device. The controller (401) may also provide the external wireless device with the IRK of the wireless vehicle sensor device. The controller (401) of the VCS (400) may also be configured to send the credentials of the external wireless device to the wireless vehicle sensor device to be added to a list of allowed devices maintained on the wireless vehicle sensor device. For example, the controller (401) may send the device ID (e.g., MAC address) of the external wireless device and the IRK of the external wireless device (if it implements RPA) via the transceiver (405).

[0059] To further illustrate, Figure 5 A flow chart illustrating an exemplary method for securely pairing a vehicle-mounted wireless sensor with a central device according to an embodiment of the present disclosure is shown, which includes pairing (502) a vehicle sensor device (501) with a vehicle control system (VCS) (503) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device and the VCS (503) via an out-of-band exchange. Figure 2The vehicle sensor device (300) uses a pre-shared passkey to communicate with a vehicle control system (VCS) (503) (e.g., Figure 4 The invention relates to a method for pairing a vehicle sensor device (501) and a VCS (400) of a vehicle sensor device (501), wherein a pre-shared passkey is shared between the vehicle sensor device (501) and the VCS (503) via an out-of-band exchange, which can be performed by the vehicle sensor device (501) and the VCS (503) exchanging the pre-shared passkey via an external device (which is configured to communicate with both the vehicle sensor device (501) and the VCS (503). For example, before initiating communication between the vehicle sensor device (501) and the VCS (503), a device that is not a vehicle component can distribute the pre-shared passkey via a wireless connection to the vehicle sensor device (501) and a wired or wireless connection to the VCS (503).

[0060] The exchange of the pre-shared passkey is out-of-band because the passkey must be provided to the target paired device outside of the communication channel between the vehicle sensor device (501) and the VCS (503). For example, the pairing tool may communicate with the vehicle sensor device (501) via a wireless out-of-band connection, and the same pairing tool may communicate with the VCS (503) via a wireless interface (e.g., Bluetooth), or via a different type of wireless interface (e.g., WiFi), or via a wired connection to a vehicle communication bus or CAN interface. In a particular embodiment, the vehicle sensor device (501) may include a BLE transceiver that pairs with a BLE transceiver coupled to the VCS (503). The pre-shared passkey may be a randomly generated code (e.g., a 16-bit integer) or a security parameter.

[0061] Figure 5The method further includes sending (504) at least an identifier (e.g., an identity resolution key (IRK)) (505) for a resolvable private address (RPA) by the vehicle sensor device (501) to the VCS (503). The sending (504) at least one ID (505) for the resolvable private address (RPA) by the vehicle sensor device (501) to the VCS (503) can be performed by the vehicle sensor device (501) sending a data packet containing the IRK to the VCS (503). The VCS (503) can use the IRK to calculate a hash of the RPA using the IRK and a cryptographic function to resolve a sensor ID of the vehicle sensor device (503). The IRK can be programmed into the vehicle sensor device (501) by the OEM, configured in the vehicle sensor device (501) using a pairing tool, or randomly generated. The sensor ID can be a Bluetooth address, a public address, a MAC address, a static random address, or other address of the vehicle sensor device (501). In some embodiments, sending at least an identifier (e.g., an Identity Resolution Key (IRK)) of a Resolvable Private Address (RPA) (505) to the VCS (503) may be performed by a wireless tool (e.g., Figure 2 For example, the wireless tool may provide the IRK to be used by the vehicle sensor device (501) to the VCS (503).

[0062] Figure 5 The method further includes communicating (506) by the vehicle sensor device (501) with the VCS (503) using an RPA, wherein the RPA is periodically regenerated by the vehicle sensor device (501). Communicating (506) by the vehicle sensor device (501) with the VCS (503) using the RPA, wherein the RPA is periodically regenerated by the vehicle sensor device (501), may be performed by the vehicle sensor device (501) sending a data packet to the VCS (503) via a channel published using the RPA. An RPA timeout may cause a controller of the vehicle sensor device (501) to regenerate the RPA to prevent device tracking.

[0063] To further illustrate, Figure 6 A flow chart illustrating another exemplary method for securely pairing a vehicle-mounted wireless sensor with a central device according to an embodiment of the present disclosure is shown. Figure 5 Similar to the exemplary method, Figure 6The method further includes pairing (502) the vehicle sensor device (501) with a vehicle control system (VCS) (503) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device and the VCS (503) via an out-of-band exchange; sending (504) at least an identifier (e.g., an identity resolution key (IRK)) (505) of a resolvable private address (RPA) by the vehicle sensor device (501) to the VCS (503); and communicating (506) with the VCS (503) using the RPA, wherein the RPA is periodically regenerated by the vehicle sensor device (501).

[0064] Figure 6 Methods and Figure 5 The difference between the methods is Figure 6 The method further includes receiving (602) an identity credential (IC) (601) of the mobile device (603) from the VCS (503) by the vehicle sensor device (501). The receiving (602) the identity credential (601) of the mobile device (603) from the VCS (503) by the vehicle sensor device (501) can be performed by the vehicle sensor device (501) receiving a data packet including the identity credential of the mobile device (e.g., a user's smart device such as a smartphone) (which has sent a request to pair with the vehicle sensor device (501) to the VCS (503)). For example, the identity credential (601) can include a public address, a MAC address, an IRK, and / or other identification information of the mobile device (603). In this example, the VCS (503) has already been paired with the mobile device (603), and the VCS (503) has already been paired with the mobile device (603), and therefore has obtained information for the identity credential (601) from the mobile device (603).

[0065] Figure 6 Methods and Figure 5 The method is different in that Figure 6The method further includes adding (604) the identity credential (601) to the allowed device list by the vehicle sensor device (501). Adding (604) the identity credential (601) to the allowed device list by the vehicle sensor device (501) can be performed by the vehicle sensor device (501) storing the identity credential in a data structure (e.g., a whitelist) that includes identification information from which the vehicle sensor device (501) will accept connection requests. By filtering the devices from which the vehicle sensor device (501) will accept connection requests, power consumption can be reduced because the vehicle sensor device (501) does not need to respond to every request from every device, and the security of the vehicle sensor device (501) can also be enhanced.

[0066] To further illustrate, Figure 7 A flow chart illustrating an exemplary method for securely pairing a vehicle-mounted wireless sensor with a central device according to an embodiment of the present disclosure is shown. Figure 6 Similar to the exemplary method, Figure 7 The method further includes pairing (502) the vehicle sensor device (501) with a vehicle control system (VCS) (503) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device and the VCS (503) via an out-of-band exchange; sending (504) at least an identifier (e.g., an identity resolution key (IRK)) of a resolvable private address (RPA) to the VCS (503); communicating (506) with the VCS (503) using the RPA by the vehicle sensor device (501); wherein the RPA is periodically regenerated by the vehicle sensor device (501); receiving (602) an identity credential (601) of the mobile device (603) from the VCS (503); and adding the identity credential (601) to an allowed device list by the vehicle sensor device (501).

[0067] Figure 7 Methods and Figure 6 The difference between the methods is Figure 7The method further includes receiving (702) a wireless connection request (701) from a mobile device (603) by the vehicle sensor device (501). Receiving the wireless connection request (701) from the mobile device (603) by the vehicle sensor device (501) can be performed by the vehicle sensor device (501) receiving a communication request through a channel published using identity information of the mobile device (603). For example, the identity information can be a public address, a MAC address, an RPA, or other address of the mobile device. If the identity information includes an RPA, the RPA can be resolved by applying a peer IRK stored on the vehicle sensor device (501) (e.g., received from the VCS (503)). The vehicle sensor device (501) can filter the wireless connection request using an allowed device list to determine whether the vehicle sensor device (501) should accept the wireless connection request (701).

[0068] Figure 7 Methods and Figure 6 The method is different in that Figure 7 The method further includes accepting (704) a wireless connection request (701) from the mobile device (603) by the vehicle sensor device (501) in response to determining that the mobile device (603) is on the allowed device list. Accepting (704) the wireless connection request (701) from the mobile device (603) by the vehicle sensor device (501) in response to determining that the mobile device (603) is on the allowed device list can be performed by the vehicle sensor device (501) determining that the vehicle sensor device (501) can accept the wireless connection request (701) and pair with the mobile device based on identity information of the mobile device (603) and the allowed device list.

[0069] In a particular embodiment, the vehicle sensor device (501) includes a TPMS sensor, and the mobile device (603) is a smart device such as a smartphone. The mobile device (603) can be paired with the vehicle sensor device to receive tire inflation assistance data (including tire pressure measurements for the purpose of inflating the vehicle tires to the correct pressure).

[0070] To further illustrate, Figure 8 A flow chart illustrating an exemplary method for securely pairing a vehicle-mounted wireless sensor with a central device according to an embodiment of the present disclosure is shown. Figure 5 Similar to the exemplary method, Figure 8The method further includes pairing (502) the vehicle sensor device (501) with a vehicle control system (VCS) (503) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device (501) and the VCS (503) via an out-of-band exchange; sending (504) at least an identifier (505) for a resolvable private address (RPA) to the VCS (503); and communicating (506) with the VCS (503) using the RPA, wherein the RPA is periodically regenerated by the vehicle sensor device (501).

[0071] Figure 8 Methods and Figure 5 The method differs in that the vehicle sensor device (501) is paired (502) with the VCS (503) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device and the VCS (503) via an out-of-band exchange, including exchanging (802) the pre-shared passkey via a pairing tool (801) configured for wireless communication with the vehicle sensor device (501) and for communication with the VCS (503). The pre-shared passkey may be wirelessly sent or received by the vehicle sensor device (501) to the pairing tool (e.g., Figure 2 The pairing is performed using a pre-shared passkey from a pairing tool (200) of the vehicle sensor device (501). In an exemplary embodiment, the vehicle sensor device (501) may receive a pre-shared passkey from the wireless tool that is generated by the pairing tool, the VCS (503), or another device configured to facilitate pairing of the vehicle sensor device (501) with the VCS (503). In another exemplary embodiment, the vehicle sensor device (501) may send a pre-shared passkey generated by the vehicle sensor device (501) to the wireless tool. In a particular embodiment, the vehicle sensor device (501) may receive the pre-shared passkey from the pairing tool via a BLE transceiver. In other embodiments, the vehicle sensor device (501) may receive the passkey via a low frequency receiver (e.g., via a 125 kHz signal), a low power receiver (e.g., via a 2.4 GHz signal), Near Field Communication (NFC), or Radio Frequency Identification (RFID).

[0072] To further illustrate, Figure 9A flow chart illustrating an exemplary method for securely pairing a vehicle-mounted wireless sensor with a central device according to an embodiment of the present disclosure is shown. Figure 5 Similar to the exemplary method, Figure 9 The method further includes pairing (502) the vehicle sensor device (501) with a vehicle control system (VCS) (503) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device and the VCS (503) via an out-of-band exchange; sending (504) at least an identifier (505) for a resolvable private address (RPA) to the VCS (503); and communicating (506) with the VCS (503) using the RPA, wherein the RPA is periodically regenerated by the vehicle sensor device (501).

[0073] Figure 9 Methods and Figure 5 The method differs in that the vehicle sensor device (501) is paired (502) with the VCS (503) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device and the VCS (503) via an out-of-band exchange, including sending (903) the pre-shared passkey (901) to the VCS (503) in one or more communication frames. Sending (902) the pre-shared passkey to the VCS (503) in one or more communication frames can be performed by the vehicle sensor device (501) sending a data packet to the VCS (503) via a communication channel in which the sensor ID of the vehicle sensor device (501) is announced as part of an initial communication between the vehicle sensor device (501) and the VCS (503). For example, the pre-shared passkey can be sent in one or more initial communications so that the VCS (503) can identify the vehicle sensor device (501) based on the pre-shared passkey.

[0074] To further illustrate, Figure 10A flow chart illustrating an exemplary method for securely pairing an onboard wireless sensor with a central device according to an embodiment of the present disclosure is shown, comprising pairing (1002) a vehicle sensor device (VCS) (1001) with a wireless vehicle sensor device (1003) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device (1003) and the VCS (1001) via an out-of-band exchange. Pairing (1002) a vehicle sensor device (VCS) (1001) with a wireless vehicle sensor device (1003) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device (1003) and the VCS (1001) via an out-of-band exchange may be performed by the vehicle sensor device (1003) and the VCS (1001) exchanging the pre-shared passkey via an external device configured to communicate with both the vehicle sensor device (1003) and the VCS (1001). For example, before initiating communication between the vehicle sensor device (1003) and the VCS (1001), a device that is not a vehicle component (e.g., Figure 2 The pairing tool (200) can distribute the pre-shared pass key via a wireless connection with the vehicle sensor device (1003) and a wired or wireless connection with the VCS (1001).

[0075] Figure 10 The method further includes receiving (1004) by the VCS (1001) at least an address identifier (e.g., an identity resolution key (IRK)) of the vehicle sensor device (1003). Receiving (1004) by the VCS (1001) at least an address identifier of the vehicle sensor device (1003) may be performed by the VCS (1001) receiving a data packet containing the IRK sent by the vehicle sensor device (1003). In some examples, the VCS (1001) receives the IRK via a wireless tool (e.g., Figure 2 The pairing tool (200)) is used to receive the IRK.

[0076] Figure 10 The method further includes associating (1006) the address identifier with a sensor identifier of the vehicle sensor device (1003) by the VCS (1001). Associating (1006) the address identifier with the sensor identifier of the vehicle sensor device (1003) by the VCS (1001) may be performed by the VCS (1001) storing the IRK and the associated sensor identifier of the vehicle sensor device (1003) in a data structure.

[0077] Figure 10The method further includes receiving (1008) by the VCS (1001) a data packet (1005) identified by a resolvable private address (RPA) from the vehicle sensor device (1003). Receiving (1008) by the VCS (1001) the data packet (1005) identified by the RPA from the vehicle sensor device (1003) may be performed by the VCS (1001) receiving the data packet (1005) from the vehicle sensor device (1003) on a communication channel published using the RPA of the vehicle sensor device (1003).

[0078] Figure 10 The method further includes identifying (1010) the vehicle sensor device (1003) from the RPA by the VCS (1001) using the address identifier. Identifying (1010) the vehicle sensor device (1003) from the RPA by the VCS (1001) using the address identifier can be performed by the VCS (1001) using the address identifier (e.g., IRK) and a cryptographic function to calculate a hash of the RPA to resolve a sensor identifier associated with the vehicle sensor device (1003).

[0079] To further illustrate, Figure 11 A flow chart illustrating an exemplary method for securely pairing a vehicle-mounted wireless sensor with a central device according to an embodiment of the present disclosure is shown. Figure 10 Similar to the exemplary method, Figure 11 The method further includes pairing (1002) a vehicle sensor device (VCS) (1001) with a wireless vehicle sensor device (1003) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device (1003) and the VCS (1001) via an out-of-band exchange; receiving (1004) at least an address identifier of the vehicle sensor device (1003); associating (1006) the address identifier with a sensor identifier of the vehicle sensor device (1003); receiving (1008) a data packet (1005) identified by a resolvable private address (RPA) from the vehicle sensor device (1003); and identifying (1010) the vehicle sensor device (1003) from the RPA by the VCS (1001) using the address identifier.

[0080] Figure 11 Methods and Figure 10 The difference between the methods is Figure 11The method further includes receiving (1102) by the VCS (1001) a pairing request (1101) for the vehicle sensor device (1003) from the mobile device (1103). The receiving (1102) by the VCS (1001) of the pairing request (1101) for the vehicle sensor device (1003) from the mobile device (1103) may be performed by the VCS (1001) receiving a request from the mobile device (1103) (e.g., a user's smart device such as a smartphone) for identity information for communicating with a specific vehicle sensor device (1003). For example, the mobile device (1103) may be a device that has been paired with the VCS (1001) (e.g., via a Bluetooth connection) such that the VCS (1001) has recorded the identity information of the mobile device (e.g., a Bluetooth address, a device address, a public address, an IRK, etc.). In a specific embodiment, the vehicle sensor device (1003) may include a TPMS sensor, and the mobile device (1103) may be a smart device such as a smartphone. The mobile device (1103) may be paired with the vehicle sensor device (1003) to receive tire inflation assistance data (including tire pressure measurements for inflating the vehicle's tires to the correct pressure).

[0081] Figure 11 Methods and Figure 10 The method is different in that Figure 11 The method further includes sending (1104) a sensor identifier and an address identifier (e.g., an IRK) of the vehicle sensor device (1003) from the VCS (1001) to the mobile device (1103). Sending (1104) the sensor identifier and the address identifier of the vehicle sensor device (1003) from the VCS (1001) to the mobile device (1103) may be performed by the VCS (1001) identifying a stored IRK and other identification information of the vehicle sensor device (1003) and sending the IRK and other identification information to the mobile device (1103) (e.g., via a Bluetooth connection).

[0082] To further illustrate, Figure 12 A flow chart illustrating an exemplary method for securely pairing a vehicle-mounted wireless sensor with a central device according to an embodiment of the present disclosure is shown. Figure 11 Similar to the exemplary method, Figure 12The method further includes pairing (1002) a vehicle sensor device (VCS) (1001) with a wireless vehicle sensor device (1003) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device (1003) and the VCS (1001) via an out-of-band exchange; receiving (1004) at least an address identifier of the vehicle sensor device (1003); associating (1006) the address identifier with a sensor identifier of the vehicle sensor device (1003); and communicating (1007) with the VCS (1001). ) receiving (1008) a data packet (1005) identified by a resolvable private address (RPA) from a vehicle sensor device (1003); and identifying (1010) the vehicle sensor device (1003) from the RPA using an address identifier by the VCS (1001); receiving (1102) a pairing request (1101) of the vehicle sensor device (1003) from the mobile device (1103) by the VCS (1001); and sending (1104) a sensor identifier and an address identifier of the vehicle sensor device (1003) from the VCS (1001) to the mobile device (1103).

[0083] Figure 12 Methods and Figure 11 The difference between the methods is Figure 12 The method further includes sending (1202) identity information (1201) of the mobile device (1103) from the VCS (1001) to the vehicle sensor device (1003). Sending (1202) the identity information (1201) of the mobile device (1103) from the VCS (1001) to the vehicle sensor device (1003) can be performed by the VCS (1001) sending a stored public address, device address, IRK, or other identification information corresponding to the mobile device (1103) to the vehicle sensor device (1003). The identification information (1201) can be authenticated identity information of the mobile device (1103) because it is sent by the VCS (1001) that has been paired with the mobile device (1103). For example, the VCS (1001) can send configuration parameters to the vehicle sensor device (1003) so that the identity information of the mobile device (1103) is added to the allowed device list (i.e., whitelist) (1003) of the vehicle sensor device (1003).

[0084] To further illustrate, Figure 13 A flow chart illustrating an exemplary method for securely pairing a vehicle-mounted wireless sensor with a central device according to an embodiment of the present disclosure is shown. Figure 10 Similar to the exemplary method, Figure 13The method further includes pairing (1002) a vehicle sensor device (VCS) (1001) with a wireless vehicle sensor device (1003) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device (1003) and the VCS (1001) via an out-of-band exchange; receiving (1004) at least an address identifier of the vehicle sensor device (1003); associating (1006) the address identifier with a sensor identifier of the vehicle sensor device (1003); receiving (1008) a data packet (1005) identified by a resolvable private address (RPA) from the vehicle sensor device (1003); and identifying (1010) the vehicle sensor device (1003) from the RPA by the VCS (1001) using the address identifier.

[0085] Figure 13 Methods and Figure 10 The method differs in that a vehicle sensor device (VCS) (1001) is paired (1002) with a wireless vehicle sensor device (1003) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device (1003) and the VCS (1001) via an out-of-band exchange, including exchanging (1302) the pre-shared passkey via a pairing tool (1301) configured for wireless communication with the vehicle sensor device (1003) and for communication with the VCS (1001). The exchanging (1302) the pre-shared passkey via the pairing tool (1301) configured for wireless communication with the vehicle sensor device (1003) and for communication with the VCS (1001) can be performed by the VCS (1001) and a wireless tool (e.g., Figure 2The pairing tool (200) of the VCS (1001) may communicate with the pairing tool (200) to send or receive a pre-shared pass key. In an exemplary embodiment, the VCS (1001) may receive a pre-shared pass key generated by the pairing tool, the vehicle sensor device (1003), or other device configured to facilitate pairing of the vehicle sensor device (1003) with the VCS (1001) from the wireless tool. In some embodiments, the VCS (1001) also receives an IRK used by the vehicle sensor device (1003) from the wireless tool. In another exemplary embodiment, the VCS (1001) may send a pre-shared pass key generated by the VCS (501) to the wireless tool. In a particular embodiment, the VCS (1001) may send the pre-shared pass key to the pairing tool via a BLE transceiver. In other embodiments, the VCS (1001) may send the pass key to the VCS (1001) via a wired connection (e.g., a CAN interface of the VCS (1001)). In yet another embodiment, the pre-shared passkey may be a security parameter provided to the VCS (1001) of the pairing tool.

[0086] To further illustrate, Figure 14 A flow chart illustrating an exemplary method for securely pairing a vehicle-mounted wireless sensor with a central device according to an embodiment of the present disclosure is shown. Figure 10 Similar to the exemplary method, Figure 14 The method further includes pairing (1002) a vehicle sensor device (VCS) (1001) with a wireless vehicle sensor device (1003) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device (1003) and the VCS (1001) via an out-of-band exchange; receiving (1004) at least an address identifier of the vehicle sensor device (1003); associating (1006) the address identifier with a sensor identifier of the vehicle sensor device (1003); receiving (1008) a data packet (1005) identified by a resolvable private address (RPA) from the vehicle sensor device (1003); and identifying (1010) the vehicle sensor device (1003) from the RPA by the VCS (1001) using the address identifier.

[0087] Figure 14 Methods and Figure 10The method differs in that a vehicle sensor device (VCS) (1001) is paired (1002) with a wireless vehicle sensor device (1003) using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device (1003) and the VCS (1001) via an out-of-band exchange, including receiving (1402) the pre-shared passkey from the vehicle sensor device (1003) in one or more communication frames. Receiving (1402) the pre-shared passkey (1401) from the vehicle sensor device (1003) in an initial communication frame may be performed by the vehicle sensor device (1003) sending a data packet to the VCS (1001) over a communication channel published using a sensor ID of the vehicle sensor device (1003) as part of initial communication between the vehicle sensor device (1003) and the VCS (1001). For example, the pre-shared passkey (1401) may be sent in one or more initial communication frames so that the VCS (1001) can identify the vehicle sensor device (1003) based on the pre-shared passkey.

[0088] In view of the above description, readers will recognize that the benefits of securely pairing vehicle-mounted wireless sensors with a central device according to embodiments of the present disclosure include but are not limited to:

[0089] Wireless vehicle sensors can be securely paired with vehicle control systems using an out-of-band interface that does not require a physical or display interface on the vehicle sensor.

[0090] Enables direct pairing of a user's smart device with wireless vehicle sensors by sharing sensor pairing information between the vehicle control system and the user's smart device, even when the sensors use private addresses;

[0091] The user's smart device can initiate two-way communication with wireless vehicle sensors based on sensor pairing information obtained via the vehicle control system;

[0092] Power consumption of wireless vehicle sensors can be reduced by filtering connection requests based on whitelisted devices.

[0093] Exemplary embodiments of the present invention are primarily described in the context of a fully functional computer system for securely pairing vehicle-mounted wireless sensors with a central device. However, those skilled in the art will recognize that the present invention may also be embodied in a computer program product provided on a computer-readable storage medium for use with any suitable data processing system. Such a computer-readable storage medium may be any storage medium for machine-readable information, including magnetic, optical, or other suitable media. Examples of such media include magnetic or floppy disks in hard drives, optical disks for optical drives, magnetic tape, and other media that will occur to those skilled in the art. Those skilled in the art will immediately recognize that any computer system with suitable programming means will be capable of performing the steps of the method of the present invention embodied in a computer program product. Those skilled in the art will also recognize that while some of the exemplary embodiments described in this specification are directed toward software installed and executed on computer hardware, alternative embodiments implemented as firmware or hardware are also within the scope of the present invention.

[0094] The present invention may be a system, apparatus, method and / or computer program product. The computer program product may include a computer-readable storage medium (or media) having computer-readable program instructions thereon for causing a processor to execute various aspects of the present invention.

[0095] A computer-readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device (such as a punched card or a raised structure in a groove with instructions recorded thereon), and any suitable combination of the foregoing. Computer-readable storage media as used herein should not be construed as transient signals per se (such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., light pulses through fiber optic cables), or electrical signals transmitted through wires).

[0096] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network). The network can include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in a computer-readable storage medium within each computing / processing device.

[0097] The computer-readable program instructions for performing the operations of the present invention may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, and the like, and traditional procedural programming languages ​​such as the "C" programming language or similar programming languages. In some embodiments, electronic circuits including, for example, programmable logic circuits, field programmable gate arrays (FPGAs), or programmable logic arrays (PLAs) may execute the computer-readable program instructions by personalizing the electronic circuits with state information of the computer-readable program instructions to perform aspects of the present invention.

[0098] Various aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present invention. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0099] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing apparatus create a means for implementing the functions / actions specified in the flowcharts and / or block diagram blocks. These computer-readable program instructions can also be stored in a computer-readable storage medium, which can instruct the computer, programmable data processing apparatus, and / or other device to operate in a specific manner, such that the computer-readable storage medium having the instructions stored therein comprises an article of manufacture containing instructions for implementing various aspects of the functions / actions specified in the flowcharts and / or block diagram blocks.

[0100] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to generate a computer-implemented process, so that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / actions specified in the flowchart and / or block diagram blocks.

[0101] The flowcharts and block diagrams in the figures illustrate the possible implementation architectures, functions and operations of the systems, devices, methods and computer program products according to various embodiments of the present invention. In this regard, each box in the flowchart or block diagram can represent a part of a module, fragment or instruction, which includes one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions annotated in the box may not occur in the order annotated in the figure. For example, the two boxes shown in succession can actually be executed substantially simultaneously, or the boxes can sometimes be executed in the opposite order, depending on the functions involved. It will also be noted that each box in the block diagram and / or flowchart illustration and the combination of boxes in the block diagram and / or flowchart illustration can be implemented by a system based on dedicated hardware that performs a specific function or action or performs a combination of special-purpose hardware and computer instructions.

[0102] It should be understood from the foregoing description that the various embodiments of the present disclosure may be modified and altered without departing from the true spirit of the present disclosure. The descriptions in this specification are for illustrative purposes only and should not be construed as limiting. The scope of the present disclosure is limited only by the language of the appended claims.

Claims

1. A method for securely pairing a vehicle-mounted wireless sensor with a central device, the method comprising: pairing, by a vehicle sensor device, with a vehicle control system using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device and the vehicle control system via an out-of-band exchange; sending, by the vehicle sensor device, an identifier resolvable to a private address to the vehicle control system; and The resolvable private address is used by the vehicle sensor device to communicate with the vehicle control system, wherein the resolvable private address is periodically regenerated by the vehicle sensor device.

2. The method according to claim 1, further comprising: Receiving, by the vehicle sensor device, identity credentials of a mobile device from the vehicle control system; as well as The identity credential is added to an allowed device list by the vehicle sensor device.

3. The method according to claim 2, further comprising: Receiving, by the vehicle sensor device, a wireless connection request from the mobile device; as well as In response to determining that the mobile device is on the allowed device list, the wireless connection request from the mobile device is accepted by the vehicle sensor device.

4. The method according to claim 3, wherein: The wireless connection request is directed to the resolvable private address of the vehicle sensor device using the identifier provided by the vehicle control system to the mobile device.

5. The method according to claim 3, wherein: The vehicle sensor device includes a tire pressure monitoring system (TPMS) sensor, and wherein the vehicle sensor device transmits tire inflation assistance data to the mobile device.

6. The method according to claim 1, wherein The vehicle sensor device is paired with the vehicle control system using the pre-shared pass key, wherein the pre-shared pass key is shared between the vehicle sensor device and the vehicle control system via an out-of-band exchange, including exchanging the pre-shared pass key via a pairing tool configured for wireless communication with the vehicle sensor device and for communication with the vehicle control system.

7. The method according to claim 1, wherein The vehicle sensor device is paired with the vehicle control system using the pre-shared pass key, wherein the pre-shared pass key is shared between the vehicle sensor device and the vehicle control system via an out-of-band exchange, including sending the pre-shared pass key to the vehicle control system in one or more communication frames.

8. The method according to claim 1, wherein The pre-shared passkey is at least one of a randomly generated code and a security parameter provided by a vehicle control system.

9. The method according to claim 1, wherein: The vehicle sensor device is a Bluetooth enabled device.

10. The method according to claim 1, wherein The vehicle sensor device is a tire pressure monitoring system device.

11. A wireless vehicle sensor device for securely pairing an onboard wireless sensor with a central device, comprising: a transceiver configured for bidirectional communication; as well as The controller is configured as: pairing with a vehicle control system via the transceiver using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device and the vehicle control system via an out-of-band exchange; transmitting, via the transceiver, an identifier resolvable to a private address to the vehicle control system; and The resolvable private address is used by the vehicle sensor device to communicate with the vehicle control system via the transceiver, wherein the resolvable private address is periodically regenerated by the vehicle sensor device.

12. A method for securely pairing a vehicle-mounted wireless sensor with a central device, the method comprising: pairing, by a vehicle control system, with a wireless vehicle sensor device using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device and the vehicle control system via an out-of-band exchange; receiving, by the vehicle control system, at least an address identifier of the vehicle sensor device; associating, by the vehicle control system, the address identifier with a sensor identifier of the vehicle sensor device; receiving, by the vehicle control system, a data packet identified by the resolvable private address from the vehicle sensor device; and The vehicle sensor device is identified based on the resolvable private address using the address identifier.

13. The method according to claim 12, further comprising: receiving, by the vehicle control system, a pairing request for the vehicle sensor device from a mobile device; as well as The sensor identifier and address identifier of the vehicle sensor device are sent from the vehicle control system to the mobile device.

14. The method according to claim 13, further comprising: Identity information of the mobile device is sent from the vehicle control system to the vehicle sensor device.

15. The method according to claim 12, wherein: The pre-shared pass key is used by the vehicle control system to pair with the vehicle sensor device, wherein the pre-shared pass key is shared between the vehicle sensor device and the vehicle control system via an out-of-band exchange, including exchanging the pre-shared pass key via a pairing tool configured for wireless communication with the vehicle sensor device and for communicating with the vehicle control system.

16. The method according to claim 12, wherein: Pairing the vehicle sensor device with the vehicle control system using the pre-shared pass key, wherein the pre-shared pass key is shared between the vehicle sensor device and the vehicle control system via an out-of-band exchange, includes receiving the pre-shared pass key and a sensor identifier of the vehicle sensor device from the vehicle sensor device in one or more communication frames.

17. The method according to claim 12, wherein: The pre-shared passkey is at least one of a randomly generated code and a security parameter provided by a vehicle control system.

18. The method according to claim 12, wherein: The vehicle sensor device is a Bluetooth enabled device.

19. The method according to claim 12, wherein: The vehicle sensor device is a tire pressure monitoring system device.

20. A vehicle control system for securely pairing a vehicle-mounted wireless sensor with a central device, comprising: a transceiver configured for bidirectional communication; Memory; as well as The controller is configured as: pairing with a wireless vehicle sensor device via the transceiver using a pre-shared passkey, wherein the pre-shared passkey is shared between the vehicle sensor device and the vehicle control system via an out-of-band exchange; receiving, via the transceiver, an address identifier of the vehicle sensor device; associating the address identifier with a sensor identifier of the vehicle sensor device in a data structure stored in the memory; receiving, via the transceiver, a data packet identified by a resolvable private address from the vehicle sensor device; and The vehicle sensor device is identified based on the resolvable private address using the address identifier.

Images