IP Library › Granted Patent US 12,277,818
Granted Patent B1
US 12,277,818 · App. 18/775,350 · Granted Apr 15, 2025

Remote programming system and method for replacement vehicle keys

Inventors: Terry Tonsing (St. Louis, MO); Patrick Linsenbardt (St. Louis, MO)
Assignee: iKeyless, LLC
G07C9/00817B60R25/20G07C5/008B60R2325/205G07C2009/00825G07C2009/00841
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,277,818
App. No.
18/775,350
Granted
Apr 15, 2025
Kind
B1
Abstract

A remote programming system for engine control units of vehicles operates by coupling an onboard diagnostic interface device with an engine control unit of a vehicle, communicatively linking the interface device with a hand held device, communicatively linking the hand held device with a back end programming machine that is remotely located from the vehicle, communicating identifying information about the vehicle to the programming machine via the interface device, the hand held device, and the communication network(s), determining an action and programming information needed to program the engine control unit of the vehicle to accept a replacement key, sending the action and programming information from the programming machine to the hand held device via the communication network(s), and programing the engine control unit of the vehicle to accept the replacement key to activate the vehicle using or responsive to use of the action and programming information.

Claims (37)

1. A method comprising:

communicatively linking an interface device to a vehicle that is programmed to accept a first key for activating the vehicle;

communicatively linking the interface device with a mobile electronic device, wherein the mobile electronic device includes an installed software application that communicates with the interface device;

communicatively linking, via one or more communication networks, the mobile electronic device with a programming machine;

communicating, by the installed software application, identifying information about the vehicle to the programming machine via the mobile electronic device and the one or more communication networks;

storing programming information received from the programming machine via the one or more communication networks, wherein the programming information is provided by the programming machine in response to the identifying information about the vehicle; and

based on the stored programming information, programming the vehicle to accept a tangible second key for activating the vehicle, wherein programming includes displaying, by the mobile electronic device, one or more prompts directing an operator to press or otherwise physically engage with at least one interactive physical element of the vehicle in furtherance of carrying out a sequence of actions that program the vehicle to accept the tangible second key.

2. The method of claim 1 , wherein the mobile electronic device is one of a mobile phone, a tablet, a laptop computer, or hand-operated electronic device.

3. The method of claim 1 , wherein programming the vehicle to accept the tangible second key includes storing unique identifying information of the tangible second key in a memory accessible by the vehicle.

4. The method of claim 1 , wherein communicatively linking the interface device with the mobile electronic device includes one or more of: establishing a wireless communication connection between the interface device and the mobile electronic device, or connecting the interface device and the mobile electronic device with one or more wires or cables.

5. The method of claim 1 , wherein unique identifying information of the tangible second key is stored in a first memory associated with the tangible second key and, after programming the vehicle, is stored in a second memory associated with the vehicle.

6. The method of claim 5 , wherein the unique identifying information of the tangible second key includes one or more of a make, model, year, or vehicle identification number, or any information associated with the vehicle available via the OBD-II standard.

7. The method of claim 1 , wherein the identifying information about the vehicle is used by the programming machine to select the programming information from among different sets of programming information that are associated with different vehicles.

8. The method of claim 1 , wherein programming the vehicle to accept the tangible second key comprises programming the vehicle to no longer accept the first key.

9. The method of claim 1 , further comprising providing an indication that the vehicle was successfully programmed to accept the tangible second key.

10. The method of claim 1 , wherein communicatively coupling the interface device to the vehicle comprises establishing a wireless connection.

11. A method comprising:

communicatively linking, via one or more communication networks, a mobile electronic device with a programming machine;

causing the mobile electronic device to communicate identifying information about a vehicle to the programming machine via the one or more communication networks, wherein the vehicle is programmed to accept a first key for activating the vehicle;

storing programming information received from the programming machine via the one or more communication networks, wherein the programming information is provided by the programming machine in response to the identifying information about the vehicle;

communicatively linking an interface device to the vehicle;

communicatively linking the mobile electronic device with the interface device; and

programming the vehicle to accept a tangible second key for activating the vehicle, wherein the programming includes use of the stored programming information to display, by the mobile electronic device, one or more prompts directing an operator to press or otherwise physically engage with at least one interactive physical element of the vehicle in furtherance of carrying out a sequence of actions that program the vehicle to accept the tangible second key.

12. The method of claim 11 , wherein the mobile electronic device is one of a mobile phone, a tablet, a laptop computer, or hand-operated electronic device.

13. The method of claim 11 , wherein programming the vehicle to accept the tangible second key includes receiving and storing unique identifying information of the tangible second key in a memory accessible by the vehicle.

14. The method of claim 11 , wherein communicatively linking the mobile electronic device with the interface device includes one or more of: establishing a wireless communication connection between the interface device and the mobile electronic device, or connecting the interface device and the mobile electronic device with one or more wires or cables.

15. The method of claim 11 , wherein unique identifying information of the tangible second key is stored in a first memory associated with the tangible second key and, after programming the vehicle, is stored in a second memory associated with the vehicle.

16. The method of claim 11 , wherein the identifying information about the vehicle includes one or more of a make, model, year, vehicle identification number, or any information associated with the vehicle available via the OBD-II standard.

17. The method of claim 11 , further comprising using the identifying information about the vehicle to select the programming information from among different sets of programming information that are associated with different vehicles.

18. The method of claim 11 , wherein programming the vehicle to accept the tangible second key comprises programming the vehicle to no longer accept the first key.

19. The method of claim 11 , further comprising providing an indication that the vehicle was successfully programmed to accept the tangible second key.

20. A mobile computing device comprising one or more processors and memory storing instructions that, in response to execution by the one or more processors, cause the one or more processors to:

communicatively linking the mobile electronic device with an interface device that is communicatively linked to a vehicle, wherein the vehicle is programmed to accept a first key for activating the vehicle, and wherein the mobile electronic device includes an installed software application that communicates with the interface device;

communicatively linking, via one or more communication networks, the mobile electronic device with a programming machine;

communicating, by the installed software application, identifying information about the vehicle to the programming machine via the mobile electronic device and the one or more communication networks;

storing programming information received from the programming machine via the one or more communication networks, wherein the programming information is provided by the programming machine in response to the identifying information about the vehicle; and

based on the stored programming information, displaying, by the mobile computing device, one or more prompts directing an operator to press or otherwise physically engage with at least one interactive physical element of the vehicle in furtherance of carrying out a sequence of actions that program the vehicle to accept a tangible second key for activating the vehicle.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2024
From: EZ KEY PROGRAMMING, LLC (DE); EZ KEY PROGRAMMING, LLC (MO)
To: IKEYLESS, LLC
Reel/Frame 068166/0169 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE ENTITY TYPE AND REPLACE PREVIOUSLY RECORDED ON REEL 68029 FRAME 78. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Aug 2, 2024
From: TONSING, TERRY; LINSENBARDT, PATRICK
To: EZ KEY PROGRAMMING, LLC
Reel/Frame 068292/0774 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 19, 2024
From: TONSING, TERRY; LINSENBARDT, PATRICK
To: EZ KEY PROGRAMMING, LLC
Reel/Frame 068029/0078 →
Continuity (5)
Continuation 18594872 · Mar 4, 2024
Continuation 17545059 · Dec 8, 2021
Continuation 16842426 · Apr 7, 2020
Continuation 15896845 · Feb 14, 2018
Provisional Application 62583130 · Nov 8, 2017
References Cited (44)
US 5864297A · Sollestre · 1999 [cited by applicant]
US 6434455B1 · Snow · 2002 [cited by applicant]
US 6501369B1 · Treharne · 2002 [cited by applicant]
US 6512461B1 · Benzie · 2003 [cited by applicant]
US 8688313B2 · Margol · 2014 [cited by applicant]
US 9002536B2 · Hatton · 2015 [cited by applicant]
US 9684500B2 · Margol · 2017 [cited by applicant]
US 10650628B2 · Tonsing · 2020 [cited by applicant]
US 10755506B2 · Determann · 2020 [cited by applicant]
US 11120654B2 · Johnson · 2021 [cited by applicant]
US 11127230B2 · Johnson · 2021 [cited by applicant]
US 11232661B2 · Tonsing · 2022 [cited by applicant]
US 20050267655A1 · Gessner · 2005 [cited by applicant]
US 20090278656A1 · Lopez · 2009 [cited by applicant]
US 20110032075A1 · Alrabady · 2011 [cited by applicant]
US 20110106374A1 · Margol · 2011 [cited by applicant]
US 20130069761A1 · Tieman · 2013 [cited by applicant]
US 20130237189A1 · Nishidai · 2013 [cited by examiner]
US 20140232521A1 · Kawamura · 2014 [cited by examiner]
US 20140266587A1 · Lopez · 2014 [cited by applicant]
US 20140380296A1 · Pal · 2014 [cited by examiner]
US 20150010145A1 · Iwashita · 2015 [cited by examiner]
US 20150062441A1 · Martin · 2015 [cited by examiner]
US 20160267730A1 · Wadhwani · 2016 [cited by examiner]
US 20180211463A1 · Mala · 2018 [cited by applicant]
US 20200384554A1 · Robertson · 2020 [cited by applicant]
US 20210035390A1 · Determann · 2021 [cited by applicant]
US 20210237175A1 · Robertson · 2021 [cited by applicant]
US 20220092899A1 · Tonsing · 2022 [cited by applicant]
US 20240203181A1 · Tonsing · 2024 [cited by applicant]
Automotive Electronic Solutions LLC “Pre & Post Scans,” Webpage, Longview, TX, https://www.autoesolutions.com/electronic-auto-services, 4 pages. [cited by applicant]
Autel, MaxiSys MS906 User Manual, 106 pages, dated Oct. 2015. [cited by applicant]
Smartbox Automotive, How to Program a Proximity Remote, https://www.youtube.com/watch?v=rftmpt5ubeU, datedYoutube.com, Retrieved from: Nov. 4, 2016. [cited by applicant]
Garcia, Flavio D., et al., Lock It and Still Lose It—On the (In) Security of Automotive Remote Keyless Entry Systems, 25th USENIX Security Symposium, 17 pages, dated Aug. 10, 2016. [cited by applicant]
Autodiagnos, Key programming using INcodes and OUTcodes—Ford ‘Coded’ PATS, 2 pages, Retrieved on Apr. 30, 2024. [cited by applicant]
Smartbox Automotive, How to Program a FOBIK, Youtube.com, dated Nov. 4, 2016. [cited by applicant]
Snap-On Tools, Ford PATS Key Programming—Diagnostic Quick Tips | Snap-On Training Solutions, Youtube.com, dated Dec. 16, 2015. [cited by applicant]
Alse Mexicana, Dodge Journey 2012 RFH, Youtube.com, dated Dec. 8, 2011. [cited by applicant]
Advanced Diagnostics USA, 2017 Ford Mustang GT Prox, Youtube.com, dated Mar. 4, 2017. [cited by applicant]
Tcodemvp, MVP / TCode PRO Infiniti G37, Youtube.com, dated Mar. 29, 2009. [cited by applicant]
Bigkrisp, How to Program Proximity Key—Remote to Nissan Sentra, Youtube.com, dated Jun. 15, 2015. [cited by applicant]
Autosmartadvisor, 2011 Nissan Cube Proximity—MVP & TCODE—PRO, Youtube.com, dated 2011. [cited by applicant]
Edgemotors, VW Audi Immobilizer Key Programming Smart Key by Edge Motors, Youtube.com, dated Nov. 7, 2015. [cited by applicant]
FCA wiTECH, Advantages of wiTech 2.0, Youtube.com, dated May 19, 2016. [cited by applicant]