Rke signal wake-up method, vehicle controller, and remote keyless entry system
Patent Information
- Application Number
- CN202611137465.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-29
- Publication Date
- 2026-10-16
AI Technical Summary
[0004]本申请提供RKE信号唤醒方法、车辆控制器及远程无钥匙进入系统，可以解决相关技术中开放频段下同频干扰信号易误触发控制器唤醒、整车静态电流异常升高的问题
[0015]本申请实施例提供的技术方案带来的有益效果包括：
Smart Images
Figure CN122934254A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle technology, specifically to an RKE signal wake-up method, a vehicle controller, and a remote keyless entry system. Background Technology
[0002] When a user presses a button on the smart key, the radio frequency transmission module inside the key sends a modulated radio frequency signal to the controller at a specific frequency. The signal in the specific frequency band causes the RKE receiving module at the ECU to change between high and low levels. The ECU is woken up from sleep mode by a hardware interrupt and immediately wakes up from low-power sleep mode to normal working mode. Then, the signal is demodulated, decoded and validated to execute the corresponding commands such as opening the door, locking the door, and finding the vehicle.
[0003] Existing technologies suffer from a high false wake-up rate: In open frequency bands, there are numerous co-frequency radio frequency signals from other wireless devices (such as tire pressure monitoring, wireless doorbells, industrial remote controls, smart home gateways, and neighboring vehicle RKE signals). Any co-frequency signal that meets physical layer characteristics will trigger the controller to be falsely woken up from sleep mode, causing an abnormal increase in the vehicle's static current. Summary of the Invention
[0004] This application provides an RKE signal wake-up method, a vehicle controller, and a remote keyless entry system, which can solve the problems of co-frequency interference signals in open frequency bands easily triggering controller wake-up and abnormal increase in vehicle static current in related technologies.
[0005] In a first aspect, embodiments of this application provide an RKE signal wake-up method, applied to a vehicle controller, comprising: Before the vehicle controller enters sleep mode, configure the tag field corresponding to the legitimate key to the RKE receiving module; When the vehicle controller is in a sleep state, the RKE receiving module receives radio frequency signals, which include encrypted data segments and unencrypted tag fields; In the dormant state, the hardware circuit of the RKE receiving module compares the received tag field with the tag field corresponding to the configured legitimate key; If the comparison results match, the RKE receiving module outputs a wake-up signal to wake up the vehicle controller from the sleep state to the normal working state; if the comparison results do not match, the RKE receiving module does not generate a wake-up signal, and the vehicle controller remains in the sleep state. After the vehicle controller is woken up, it decrypts and verifies the encrypted data segment, and executes the corresponding control command after the verification is successful.
[0006] In conjunction with the first aspect, in one implementation, the tag field corresponding to the legitimate key is acquired through a key matching learning phase and stored in the non-volatile memory of the vehicle controller, the key matching learning phase including: Receive the RKE signal sent by the key; Extract the tag field from the RKE signal; The acquired tag field is stored in the non-volatile memory of the vehicle controller.
[0007] In conjunction with the first aspect, in one implementation, configuring a tag field corresponding to a valid key to the RKE receiving module includes: Read the tag field from non-volatile memory; Write the read tag field into the register inside the RKE receiver module.
[0008] In conjunction with the first aspect, in one implementation, the marking field is a fixed field that remains unchanged in each frame of radio frequency signal transmitted by the same key.
[0009] In conjunction with the first aspect, in one implementation, the marker fields corresponding to different legitimate keys are all different.
[0010] In conjunction with the first aspect, in one implementation, the marker field is derived from the vehicle VIN code or ECU hardware ID.
[0011] In conjunction with the first aspect, in one implementation, the wake-up signal is a hardware interrupt signal, and the main processing unit kernel remains in a deep sleep state during the comparison of the marked fields by the vehicle controller.
[0012] In conjunction with the first aspect, in one embodiment, in the frame structure of the radio frequency signal, the marker field is appended to the end of the encrypted data segment and transmitted continuously with the encrypted data segment.
[0013] Secondly, embodiments of this application provide a vehicle controller, including: The system includes a main processing unit, an RKE receiving module connected to the main processing unit, and a memory connected to the main processing unit. The memory stores a tag field corresponding to a valid key. Before entering a sleep state, the main processing unit configures the tag field to the RKE receiving module. When the main processing unit is in a sleep state, the RKE receiving module receives a radio frequency signal containing an encrypted data segment and an unencrypted tag field, and compares the received tag field with the configured tag field using hardware. If the comparison matches, a wake-up signal is generated and sent to the main processing unit; if the comparison does not match, no wake-up signal is generated. The main processing unit, upon being woken up, decrypts the encrypted data segment and executes control commands.
[0014] Thirdly, embodiments of this application provide a remote keyless entry system, including a smart key and a vehicle controller in the second aspect; the smart key is used to send the radio frequency signal, the radio frequency signal including an encrypted data segment and an unencrypted tag field, the tag field being a fixed field.
[0015] The beneficial effects of the technical solutions provided in this application include: By setting an unencrypted fixed marker field in the radio frequency signal that is independent of the encrypted data segment, the RKE receiving module performs the marker field matching and verification by hardware circuitry during the vehicle controller's sleep phase. The controller is only triggered to wake up when the match is found, and the encrypted data segment is then decrypted and verified after wake-up. This technical solution solves the problems of co-frequency interference signals in open frequency bands easily triggering controller wake-up and abnormally increasing vehicle static current in related technologies. At the same time, it resolves the technical contradiction that the encrypted RKE signal data is randomized and cannot be used for sleep wake-up screening.
[0016] This solution can complete the initial signal screening without waking up the main processing unit, intercepting most co-channel interference and illegal signals before the wake-up process, significantly reducing the probability of false wake-ups and effectively controlling the vehicle's sleep power consumption. The decoupled design of the tag field and encrypted data segment ensures the information security of signal transmission through the encrypted data segment, meeting automotive-grade information security requirements, while the fixed tag segment enables precise wake-up screening, balancing safety compliance and low power consumption requirements. At the same time, the hardware-level matching mechanism is compatible with the existing RKE system architecture, with low implementation cost and strong adaptability, and can significantly improve the anti-interference capability and wake-up reliability of the RKE system while meeting automotive-grade static current requirements. Attached Figure Description
[0017] Figure 1 This is a schematic diagram of the RKE data frame structure of this application; Figure 2 This is a flowchart illustrating the ECU and key matching process for this application. Figure 3 This is a flowchart of the RKE signal wake-up process in this application; Figure 4 This is a schematic diagram of the hardware structure of the vehicle controller involved in the embodiment of this application. Detailed Implementation
[0018] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.
[0019] First, some of the technical terms used in this application will be explained to help those skilled in the art understand this application.
[0020] RKE: Remote Keyless Entry system, which enables remote control functions such as locking, unlocking, and locating the vehicle via radio frequency wireless signals, is a mainstream body control configuration for passenger cars.
[0021] BCM: Body Control Module is the core controller for the vehicle's RKE function. It is responsible for receiving radio frequency signals, verifying legitimacy, and controlling the output of actuators such as door locks. It needs to maintain a low-power monitoring mode when the vehicle is in sleep mode.
[0022] AES128: 128-bit Advanced Encryption Standard, is a commonly used symmetric encryption algorithm in the field of automotive-grade information security. It is used for the encrypted transmission of RKE command data, and can resist replay attacks and signal cracking, ensuring communication security.
[0023] Marker field: In this scheme, the unencrypted fixed feature sequence appended to the end of the RKE radio frame is used only for physical layer hardware wake-up matching, does not carry instruction data, and is logically independent of the encrypted data segment.
[0024] Static current: The vehicle's standby current when the vehicle is in sleep mode is off. It is a core automotive-grade indicator for measuring the power consumption level of the body controller. Frequent false wake-ups will cause the static current to rise abnormally, thus depleting the battery's power.
[0025] Hardware interrupt: A processor wake-up mechanism triggered by changes in peripheral device voltage levels. It does not require the kernel to actively poll and listen, and is the core wake-up triggering method for low-power hibernation systems.
[0026] Non-volatile memory: A storage medium that can retain data persistently after power failure, such as EEPROM and Flash, used to store configuration data that needs to be stored for a long time, such as vehicle key keys and pairing information.
[0027] Vehicle controller: also known as the on-board electronic control unit (ECU), is the core control carrier for RKE functions.
[0028] With the development of automotive electronics technology, Remote Keyless Entry (RKE) systems have become standard equipment in passenger vehicles. In traditional solutions, the vehicle controller responds to radio frequency signals via hardware interrupts when in sleep mode. Upon being woken up, it performs signal demodulation, decoding, and validity verification before executing the corresponding control commands. Within the open ISM radio frequency band, there are numerous co-frequency radio signals from other wireless devices, including tire pressure monitoring systems, wireless doorbells, industrial remote controls, smart home gateways, and neighboring vehicle RKE signals. Any co-frequency signal that meets physical layer characteristics can trigger the controller to be incorrectly woken from sleep mode, leading to an abnormal increase in the vehicle's static current and shortening its idle time. Simultaneously, with the gradual implementation of automotive information security regulations and internal security standards of car manufacturers, RKE signals must be encrypted using algorithms such as AES128. After encryption, each frame of data exhibits random characteristics, rendering traditional pre-screening mechanisms based on data characteristics ineffective. This makes it impossible to distinguish legitimate key signals from interference signals without decryption, making it difficult to simultaneously meet low power consumption and information security requirements. Therefore, this application proposes an RKE signal wake-up method, a vehicle controller, and a remote keyless entry system.
[0029] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.
[0030] In a first aspect, embodiments of this application provide an RKE signal wake-up method, applied to a vehicle controller, comprising: Before the vehicle controller enters sleep mode, configure the tag field corresponding to the legitimate key to the RKE receiving module; When the vehicle controller is in sleep mode, the RKE receiver module receives radio frequency signals, which include encrypted data segments and unencrypted tag fields. In sleep mode, the hardware circuit of the RKE receiver module compares the received tag field with the tag field corresponding to the configured legitimate key; If the comparison results match, the RKE receiving module outputs a wake-up signal to wake the vehicle controller from sleep mode to normal operation mode; if the comparison results do not match, the RKE receiving module does not generate a wake-up signal, and the vehicle controller remains in sleep mode. After the vehicle controller is woken up, it decrypts and verifies the encrypted data segment, and executes the corresponding control command after the verification is successful.
[0031] In this embodiment, the vehicle controller pre-configures the hardware for the legitimate key marking field before entering sleep mode. During the sleep phase, the RKE receiving module independently monitors the radio frequency signal and performs matching and verification of the unencrypted marking field through hardware circuitry. Only when the marking matches successfully is the controller awakened. After awakening, the controller decrypts and verifies the encrypted data segment. Based on this two-level mechanism of hardware marking initial screening and post-wake-up decryption verification, legitimate key signals and co-frequency interference signals can be quickly distinguished without decrypting the signal. This solves the problems of open-frequency co-frequency signals easily triggering controller wake-up and abnormally increasing vehicle static current in related technologies. At the same time, it overcomes the technical contradiction that encrypted RKE signal data is randomized and cannot be used for sleep-wake-up screening. Under the premise of ensuring information security, it significantly reduces the probability of false wake-up and effectively controls the vehicle's sleep power consumption.
[0032] Through actual testing, this solution can distinguish between legitimate signals and interference signals in the same frequency band using only fixed marker segments without decryption, reducing the false wake-up rate by more than 90% compared to traditional solutions. Furthermore, the entire marker matching process is completed independently by the hardware circuit, and the main kernel does not need to start during the wake-up determination period. The increase in static current of the whole vehicle is less than 50μA, which fully meets the automotive-grade power consumption requirements.
[0033] Furthermore, in one embodiment, the tag field corresponding to the legitimate key is obtained through a key matching learning phase and stored in the non-volatile memory of the vehicle controller. The key matching learning phase includes: Receive the RKE signal sent by the key; Extract the tag field from the RKE signal; The acquired tag field is stored in the non-volatile memory of the vehicle controller.
[0034] In this embodiment, during the vehicle key pairing learning phase, after the controller enters the legitimate pairing mode, it receives the radio frequency signal of the key to be paired, independently parses the marker field information from the signal frame, and stores it separately from the encryption key information in non-volatile memory. The data will not be lost after power failure. Through the learning mechanism of independently storing the marker field, the binding and persistent storage of the wake-up marker can be completed without modifying the original key pairing and security authentication process. This solves the problem that the existing encrypted RKE system lacks a dedicated wake-up identifier and cannot achieve accurate wake-up screening. It is compatible with the existing RKE key learning process, has low implementation cost, and strong adaptability.
[0035] Furthermore, in one embodiment, configuring the tag field corresponding to the legitimate key to the RKE receiving module specifically includes: Read the tag field from non-volatile memory; Write the read tag field into the register inside the RKE receiver module.
[0036] In this embodiment, before the vehicle controller enters deep sleep mode, the main processing unit reads the tag fields corresponding to all legitimate keys from the non-volatile memory and writes them in batches into the hardware matching register built into the RKE receiving module. After configuration, the main processing unit enters sleep mode, and the subsequent tag comparison is completed independently by the RKE module based on the configuration values in the register, without needing to access the controller memory again. By pre-writing the matching benchmark into the hardware register, the wake-up determination is completely independent of the main kernel and memory access, solving the problem of traditional solutions requiring the main processor to be started and having high power consumption during wake-up verification. This ensures that the comparison process is purely hardware-executed, with minimal increase in the vehicle's static current, meeting automotive-grade low-power requirements.
[0037] Furthermore, in one embodiment, the marker field is a fixed field that remains unchanged in each frame of radio frequency signal transmitted by the same key.
[0038] In this embodiment, each frame of radio frequency signal sent by the smart key consists of two parts: an encrypted data segment generated using encryption algorithms such as AES128, with each frame's data changing randomly to ensure the confidentiality of the instruction information; and a marker field that does not participate in encryption operations, with the sequence content of the marker field remaining completely fixed across all frames sent by the same key. This decoupling design of the fixed marker segment and the random encryption segment preserves the information security capabilities of the encryption mechanism while providing stable and identifiable characteristics for hardware wake-up matching. This resolves the core contradiction of randomized encrypted signal data that cannot be used for physical layer wake-up screening, achieving a balance between information security and low-power wake-up.
[0039] Furthermore, in one embodiment, the tag fields corresponding to different legitimate keys are different from each other.
[0040] In this embodiment, each legitimate smart key is assigned a unique sequence of marker fields. Multiple sets of corresponding markers are synchronously stored in the vehicle controller's non-volatile memory and the RKE receiver module register. The RKE hardware circuit simultaneously compares all configured markers; a successful match in any set triggers a wake-up. This single-key unique marker design supports the legitimate use of multiple keys while accurately distinguishing signals from different keys, avoiding false wake-ups caused by keys of the same model from neighboring vehicles or universal remote controls operating on the same frequency band. This further narrows the wake-up trigger range and improves the wake-up accuracy and anti-interference capability of the RKE system.
[0041] Furthermore, in one embodiment, the marker field is derived from the vehicle VIN code or ECU hardware ID.
[0042] In this embodiment, the tagging field is generated based on the vehicle VIN code or ECU hardware ID using a fixed derivation algorithm. Vehicles of the same model and configuration have consistent tagging fields, while controllers of different models and hardware versions naturally have different tagging fields. This eliminates the need for additional vehicle-specific configuration, achieving signal isolation between vehicle models. The mechanism of deriving tags based on hardware identity information naturally distinguishes RKE signals from different models, avoiding cross-model interference between signals of the same frequency and the risk of cross-model forgery. It inherently possesses vehicle model isolation capabilities, reducing configuration management costs and security risks during mass production.
[0043] Furthermore, in one embodiment, the wake-up signal is a hardware interrupt signal, and the main processing unit kernel remains in a deep sleep state during the comparison of the marked fields by the vehicle controller.
[0044] In this embodiment, the entire process of sampling, identifying, and comparing the marked field is completed by the hardware state machine of the RKE receiving module, without the main processing unit kernel participating in the calculation. After a match is found, the RKE module outputs a level transition signal, which triggers the main processing unit to wake up from deep sleep via a hardware interrupt pin. Throughout the comparison cycle, the main kernel remains in sleep mode, and only the RKE receiving module is in a low-power listening state. This solves the problems of traditional solutions requiring the main kernel to be started for wake-up determination and resulting in high static current. It minimizes the power consumption for wake-up determination, and the increase in static current of the entire vehicle meets automotive-grade requirements, effectively extending the vehicle's idle range.
[0045] Furthermore, in one embodiment, in the frame structure of the radio frequency signal, a marker field is appended to the end of the encrypted data segment and transmitted continuously with the encrypted data segment.
[0046] In this embodiment, the radio frequency signal retains the original frame structure of the encrypted data segment, with only a fixed-length marker field appended to the end of the frame. Both are continuously modulated and transmitted within the same radio frequency frame. The receiving end receives data sequentially according to frame timing, and the hardware circuit directly extracts the marker segment from the end of the frame for matching, without needing to modify the original frame header, encryption segment's transmission protocol, or parsing logic. This frame structure design with the frame appended eliminates the need to reconstruct the radio frequency communication protocol, requiring almost no modification to the existing transmitter hardware or receiver front-end circuitry. It solves the problems of high replacement costs and incompatibility with existing architectures associated with new solutions, resulting in a short implementation cycle, low deployment cost, and strong adaptability. It can quickly achieve compatibility with existing RKE / BCM architectures, facilitating rapid mass production and application.
[0047] To make this solution easier to understand, the complete workflow is explained in detail with reference to the accompanying diagrams. The specific steps are as follows: Step 1: The smart key generates encrypted data segments according to automotive-grade information security requirements. It uses the AES128 symmetric encryption algorithm to encrypt unlocking, locking, and vehicle location commands. Each frame of encrypted data changes randomly to ensure the confidentiality of the command information. Figure 1The encrypted field portion of the radio frequency frame structure.
[0048] Step 2: Simultaneously design an unencrypted fixed marker field on the smart key end. Each valid smart key corresponds to a unique marker field sequence. This field does not participate in encryption operations and remains constant across all radio frequency frames emitted by the same key. The marker field is appended to the end of the encrypted data segment frame. Both are continuously modulated and transmitted within the same radio frequency frame. Figure 1 The marker field portion of the radio frequency frame structure.
[0049] Step 3: During the key matching learning phase, the vehicle controller enters the legitimate pairing mode, receives the RKE radio frequency signal sent by the smart key to be matched, independently parses the marker field information from the signal frame, and persistently stores the marker field and encryption key information in the non-volatile memory of the vehicle controller. Figure 2 The key learning process.
[0050] Step 4: Before the vehicle controller enters deep sleep mode, the main processing unit reads the tag fields corresponding to all valid keys from the non-volatile memory, writes them in batches into the hardware matching register inside the RKE receiver module, and completes the wake-up baseline configuration. Figure 3 The configuration process before hibernation.
[0051] Step 5: When the vehicle controller is in sleep mode, the main processing unit core remains in deep sleep, with only the RKE receiver module in low-power listening mode. Upon receiving an RF signal, the RKE receiver module directly extracts the frame end marker field through its internal hardware matching circuit and compares it with the valid marker in the register. Figure 3 Hardware matching process.
[0052] Step 6: If the flag fields match, the RKE receiving module outputs a level transition signal, triggering the vehicle controller's main processing unit to wake up from deep sleep via a hardware interrupt pin; if the comparison fails, it is determined to be co-channel interference or an illegal signal, no interrupt signal is generated, and the vehicle controller remains in sleep mode. Figure 3 The wake-up determination process.
[0053] Step 7: After the vehicle controller wakes up to normal operating status, it decrypts and verifies the validity of the encrypted data segment in the radio frequency signal. If the verification is successful, it parses out the specific instructions and executes corresponding control actions such as unlocking, locking, and vehicle location. Figure 3 The decryption and execution process.
[0054] Secondly, such as Figure 4 As shown, Figure 4 This is a schematic diagram of the hardware structure of the vehicle controller involved in the embodiments of this application. The embodiments of this application provide a vehicle controller, including: The system comprises: a main processing unit; an RKE receiving module connected to the main processing unit; and a memory connected to the main processing unit. The memory stores the tag field corresponding to the valid key. Before entering a sleep state, the main processing unit configures the tag field to the RKE receiving module. When the main processing unit is in a sleep state, the RKE receiving module receives an RF signal containing an encrypted data segment and an unencrypted tag field, and compares the received tag field with the configured tag field using hardware. If the comparison matches, a wake-up signal is generated and sent to the main processing unit; if the comparison does not match, no wake-up signal is generated. The main processing unit, upon being woken up, decrypts the encrypted data segment and executes control commands.
[0055] In this embodiment, the various units within the vehicle controller work collaboratively: the non-volatile memory persistently stores the tag field and encryption key of the legitimate key; the main processing unit completes the hardware register configuration of the tag field before entering deep sleep; the RKE receiving module has a built-in hardware matching circuit, independently undertaking signal monitoring and tag verification during the sleep period, triggering an interrupt to wake up the main processing unit only when the tag matching is successful; after waking up, the main processing unit performs decryption, verification, and instruction execution. Through this division of labor architecture, where the hardware module is responsible for initial screening and the main kernel is responsible for high-level verification, a low false wake-up, low static current, and high security RKE wake-up function is achieved without changing the overall hardware framework of the controller. This solves the problems of high false wake-up rate and difficulty in balancing power consumption and security in traditional controllers, improving the overall performance of the vehicle's RKE system.
[0056] Furthermore, in one embodiment, the main processing unit is also used to perform processing in the key matching learning phase, specifically including: receiving the RKE signal sent by the key to be matched in the legal pairing mode, parsing and obtaining the tag field from the RKE signal, and storing the obtained tag field into a non-volatile memory.
[0057] In this embodiment, during the key pairing learning phase, the vehicle controller's main processing unit enters a valid pairing mode to receive the key's radio frequency signal. It independently parses the marker field information from the signal and persistently stores it separately from the encryption key information in non-volatile memory, ensuring data integrity even after power failure. Through this independent marker field learning and storage mechanism, the binding and persistent storage of the wake-up identifier can be completed without modifying the existing key pairing and security authentication process. This ensures compatibility with existing RKE key learning processes, resulting in low implementation costs and strong adaptability.
[0058] Furthermore, in one embodiment, when the main processing unit configures the tag field corresponding to the legitimate key to the RKE receiving module, it is specifically used to: read all the tag fields corresponding to the legitimate keys from the non-volatile memory, and write the read tag fields into the hardware matching register inside the RKE receiving module.
[0059] In this embodiment, before the vehicle controller enters deep sleep mode, the main processing unit retrieves the tag fields of all legitimate keys from non-volatile memory and writes them in batches into the hardware matching register built into the RKE receiving module as a comparison benchmark. After configuration, the main processing unit can enter sleep mode, and the subsequent tag comparison is completed independently by the RKE receiving module based on the register data, without accessing the controller memory. By pre-hardening the matching benchmark into the hardware register, the wake-up decision is completely independent of the main kernel and memory access, ensuring that the comparison process is purely hardware-based, resulting in a very small increase in the vehicle's static current and meeting automotive-grade low-power requirements.
[0060] Furthermore, in one embodiment, the marker field in the radio frequency signal received by the RKE receiving module is a fixed field that remains unchanged in each frame of radio frequency signal sent by the same legitimate key, and is logically independent of the encrypted data segment.
[0061] In this embodiment, the encrypted data segment of the radio frequency signal is generated using encryption algorithms such as AES128, and the data in each frame changes randomly to ensure the confidentiality of the instructions. The tag field does not participate in the encryption operation, and the tag sequence of all frames with the same key remains constant. Through the decoupling design of the fixed tag segment and the random encryption segment, the information security capability of the encryption mechanism is preserved, while providing stable and identifiable features for hardware wake-up matching. This solves the core contradiction of randomized encrypted signal data that cannot be used for physical layer wake-up screening, achieving a balance between information security and low-power wake-up.
[0062] Furthermore, in one embodiment, the non-volatile memory stores a tag field corresponding to multiple legal keys, and the tag fields corresponding to different legal keys are different from each other.
[0063] In this embodiment, each legitimate smart key is assigned a unique sequence of marker fields, all of which are stored in non-volatile memory and synchronously configured in the matching register of the RKE receiver module. The hardware circuit of the RKE receiver module can simultaneously compare all configured markers, and a successful match in any set of markers triggers a wake-up. Through the design of a unique marker for each key, while supporting the legitimate use of multiple keys, the system can accurately distinguish signals from different keys, effectively avoiding false wake-ups caused by keys of the same model in neighboring vehicles or universal remote controls on the same frequency band. This further narrows the wake-up trigger range and improves the wake-up accuracy and anti-interference capability of the RKE system.
[0064] Furthermore, in one embodiment, the tag field is derived from the vehicle VIN code or ECU hardware ID and stored in non-volatile memory.
[0065] In this embodiment, the tag field is generated based on the vehicle's unique identification information using a fixed derivation algorithm. Vehicles of the same model and configuration have consistent tag fields, while controllers of different models and hardware versions naturally have different tag fields. Signal isolation between vehicle models can be achieved without additional configuration for each vehicle. The mechanism of deriving tags based on hardware identification information makes the RKE signals of different models naturally distinguishable, avoiding cross-model interference between signals of the same frequency and the risk of cross-model forgery. It naturally has vehicle isolation capabilities, reducing configuration management costs and security risks in the mass production stage.
[0066] Furthermore, in one embodiment, the wake-up signal output by the RKE receiving module is a hardware interrupt signal; during the tag field comparison, the kernel of the main processing unit remains in a deep sleep state, and only the RKE receiving module is in a low-power listening and matching state.
[0067] In this embodiment, the entire process of sampling, identifying, and comparing the marked field is completed by the hardware state machine of the RKE receiving module, without the main processing unit kernel participating in the calculation. After a match is found, the RKE receiving module outputs a level transition signal, which triggers the main processing unit to wake up from deep sleep via a hardware interrupt pin. Throughout the entire comparison cycle, the main kernel remains in sleep mode, and only the RKE receiving module maintains low-power monitoring, minimizing the power consumption for wake-up determination. The vehicle's static current increment meets automotive-grade requirements, effectively extending the vehicle's idle range.
[0068] Furthermore, in one embodiment, in the frame structure of the radio frequency signal, the marker field is appended to the end of the encrypted data segment, and the two are transmitted continuously in the same radio frequency frame; the RKE receiving module is used to extract the marker field according to the frame timing to perform hardware comparison.
[0069] In this embodiment, the radio frequency signal retains the original frame structure of the encrypted data segment, with only a fixed-length marker field appended to the end of the frame. Both are continuously modulated and transmitted within the same radio frequency frame. The RKE receiving module receives data according to frame timing and directly extracts the marker segment at the end of the frame for matching, without needing to modify the original frame header, encryption segment's transmission protocol, or parsing logic. This compatible frame structure design with the frame appended eliminates the need to reconstruct the radio frequency communication protocol, requires almost no modification to existing transmitter hardware or receiver front-end circuitry, has a short implementation cycle, low deployment cost, and facilitates rapid mass production applications.
[0070] It should be noted that the main processing unit, RKE receiving module, and memory described in this embodiment can be independent hardware circuit units or integrated into the same chip or module. The vehicle controller can specifically be a body control module (BCM), a gateway controller, or a separate keyless entry control unit. Connections between modules can be implemented via internal buses (such as SPI, I2C, etc.) or board-level circuitry; this application does not impose specific limitations on this. Those skilled in the art can choose specific hardware implementations based on actual needs; any implementation that achieves the above functions is within the scope of this document.
[0071] Thirdly, embodiments of this application provide a remote keyless entry system, including a smart key and a vehicle controller of the second aspect; the smart key is used to send radio frequency signals, the radio frequency signals including encrypted data segments and unencrypted tag fields, the tag fields being fixed fields.
[0072] In this embodiment, the smart key assembles encrypted command data and fixed marker fields into frames according to a frame structure and then continuously transmits them through the radio frequency module. The vehicle controller, following the aforementioned two-level verification mechanism, first completes marker field matching and wake-up triggering via hardware, and then the main kernel completes decryption verification and command execution, forming a complete closed-loop solution from the transmitter to the receiver. The entire system, without altering the original encryption security architecture, adds physical layer marker wake-up filtering capabilities, solving the problems of high false wake-up rate, large static current, and difficulty in balancing encryption and low power consumption in traditional RKE systems. This significantly improves the system's anti-interference capability, reduces the vehicle's static power consumption, and is compatible with existing system architectures, possessing extremely high engineering application value.
[0073] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.
[0074] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.
[0075] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.
[0076] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.
[0077] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.
[0078] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
1. An RKE signal wake-up method, applied to a vehicle controller, characterized in that, include: Before the vehicle controller enters sleep mode, configure the tag field corresponding to the legitimate key to the RKE receiving module; When the vehicle controller is in a sleep state, the RKE receiving module receives radio frequency signals, which include encrypted data segments and unencrypted tag fields; In the dormant state, the hardware circuit of the RKE receiving module compares the received tag field with the tag field corresponding to the configured legitimate key; If the comparison results match, the RKE receiving module outputs a wake-up signal to wake up the vehicle controller from the sleep state to the normal working state; if the comparison results do not match, the RKE receiving module does not generate a wake-up signal, and the vehicle controller remains in the sleep state. After the vehicle controller is woken up, it decrypts and verifies the encrypted data segment, and executes the corresponding control command after the verification is successful.
2. The RKE signal wake-up method as described in claim 1, characterized in that, The tag field corresponding to the legitimate key is obtained through the key matching learning phase and stored in the non-volatile memory of the vehicle controller. The key matching learning phase includes: Receive the RKE signal sent by the key; Extract the tag field from the RKE signal; The acquired tag field is stored in the non-volatile memory of the vehicle controller.
3. The RKE signal wake-up method as described in claim 2, characterized in that, Configure the tag field corresponding to the legitimate key to the RKE receiving module, including: Read the tag field from non-volatile memory; Write the read tag field into the register inside the RKE receiver module.
4. The RKE signal wake-up method as described in claim 1, characterized in that, The marking field is a fixed field that remains unchanged in every frame of radio frequency signal transmitted by the same key.
5. The RKE signal wake-up method as described in claim 1, characterized in that, The marker fields corresponding to different valid keys are all different.
6. The RKE signal wake-up method as described in claim 1, characterized in that, The tag field is derived from the vehicle VIN code or ECU hardware ID.
7. The RKE signal wake-up method as described in claim 1, characterized in that, The wake-up signal is a hardware interrupt signal. During the comparison of the marked fields, the main processing unit kernel of the vehicle controller remains in a deep sleep state.
8. The RKE signal wake-up method as described in claim 1, characterized in that, In the frame structure of the radio frequency signal, the marker field is appended to the end of the encrypted data segment and transmitted continuously with the encrypted data segment.
9. A vehicle controller, characterized in that, include: Main processing unit; The RKE receiving module is connected to the main processing unit; A memory, connected to the main processing unit, is used to store a tag field corresponding to a valid key. The main processing unit configures the tag field to the RKE receiving module before entering a sleep state. The RKE receiving module receives an radio frequency signal including an encrypted data segment and an unencrypted tag field when the main processing unit is in a sleep state, and compares the received tag field with the configured tag field using hardware. If the comparison matches, a wake-up signal is generated and sent to the main processing unit; if the comparison does not match, no wake-up signal is generated. The main processing unit, after being woken up, decrypts the encrypted data segment and executes control commands.
10. A remote keyless entry system, characterized in that, It includes a smart key and a vehicle controller as described in claim 9; the smart key is used to transmit the radio frequency signal, the radio frequency signal including an encrypted data segment and an unencrypted tag field, the tag field being a fixed field.