Patent No. US12277818 (titled "Remote Programming System And Method For Replacement Vehicle Keys") was filed by Ikeyless Llc on Jul 17, 2024.
’818 is related to the field of vehicle security systems, specifically the remote programming of engine control units (ECUs) to accept replacement keys. The background involves the problem of replacing lost or unavailable car keys, which traditionally requires a locksmith to physically visit the vehicle and use specialized equipment to reprogram the ECU. This process can be time-consuming and expensive, creating inconvenience for vehicle owners and challenges for entities managing fleets of vehicles.
The underlying idea behind ’818 is to enable remote reprogramming of vehicle ECUs by leveraging a networked system. The key inventive insight is to use a combination of an onboard diagnostic (OBD) interface , a mobile device, and a remote back-end server to securely and efficiently update the ECU's key acceptance parameters. This allows for reprogramming without requiring a locksmith's physical presence, reducing costs and improving efficiency.
The claims of ’818 focus on a method and a mobile computing device for remotely programming a vehicle to accept a replacement key. The method involves communicatively linking an interface device to a vehicle, linking the interface device with a mobile electronic device, and linking the mobile electronic device with a programming machine. The claims cover communicating identifying information about the vehicle to the programming machine, storing programming information received from the programming machine, and programming the vehicle to accept a tangible second key based on the stored programming information. A key aspect is displaying prompts on the mobile device directing an operator to physically interact with the vehicle.
In practice, the system works by first establishing a communication link between the vehicle's ECU and a remote server. This is achieved by plugging an OBD interface into the vehicle, which then connects to a mobile device (like a smartphone) via Bluetooth or a cable. The smartphone, running a dedicated application, then communicates with a back-end server over the internet. The server, after receiving vehicle identification data, provides specific programming instructions and data back to the smartphone, which then relays them to the ECU via the OBD interface. The operator is guided through the process by prompts on the smartphone, such as turning the ignition key to a specific position or pressing certain buttons on the dashboard.
This approach differentiates itself from prior solutions by eliminating the need for specialized locksmith equipment and on-site expertise. Instead of requiring a trained technician to physically manipulate the ECU, the system allows a less skilled operator to follow instructions provided by the remote server. The centralized server can also maintain a database of vehicle-specific programming procedures, ensuring compatibility and security. Furthermore, the system can log and verify successful reprogramming events, providing accountability and preventing fraudulent claims of unsuccessful key replacements.
In the late 2010s when ’818 was filed, at a time when vehicle ignition systems were commonly activated by keys containing unique identifying information, engine control units (ECUs) were programmed to recognize these keys. Programming a replacement key often required specialized equipment and trained locksmiths to physically access the vehicle's ECU. This process was often time-consuming and costly due to hardware or software constraints that made remote or automated key programming non-trivial.
The examiner allowed the claims because the prior art, specifically Nishidai and Wadhwani, did not teach or suggest a method that includes communicatively linking an interface device to a vehicle programmed to accept a first key, communicatively linking the interface device with a mobile electronic device, and then communicatively linking the mobile device with a programming machine. The examiner stated that the prior art also failed to teach communicating identifying information about the vehicle to the programming machine via the mobile device and communication networks, storing programming information received from the programming machine, and programming the vehicle to accept a second key based on the stored programming information, including displaying prompts on the mobile device to guide an operator through the programming sequence.
This patent contains 20 claims, with independent claims numbered 1, 11, and 20. The independent claims are generally directed to methods and a mobile computing device for programming a vehicle to accept a second key using a mobile electronic device, an interface device, and a programming machine. The dependent claims generally elaborate on and further define the elements and steps recited in the independent claims.
Definitions of key terms used in the patent claims.

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.
Date
Description
Get instant alerts for new documents