Prosecution Insights
Last updated: November 04, 2026
Application No. 18/908,092

System and Methods for Staging Data and Updating Vehicle Modules Using Staged Data

Non-Final OA §103§DOUBLEPATENT
Filed
Oct 07, 2024
Priority
Oct 29, 2023 — provisional 63/594,016 +2 more
Examiner
NGUYEN, PHILLIP H
Art Unit
Tech Center
Assignee
Integrated Engineering LLC
OA Round
1 (Non-Final)
91%
Grant Probability
Favorable
1-2
OA Rounds
9m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 91% — above average
91%
Career Allowance Rate
556 granted / 613 resolved
+30.7% vs TC avg
Moderate +12% lift
Without
With
+11.5%
Interview Lift
resolved cases with interview
Typical timeline
2y 10m
Avg Prosecution
13 currently pending
Career history
629
Total Applications
across all art units

Statute-Specific Performance

§101
16.3%
-23.7% vs TC avg
§103
41.5%
+1.5% vs TC avg
§102
30.3%
-9.7% vs TC avg
§112
7.5%
-32.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 613 resolved cases

Office Action

§103 §DOUBLEPATENT
DETAILED ACTION Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . This Office Action is in response to the filing date of 10/7/2024. Claims 1-20 are pending and have been considered below. Double Patenting The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b). The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13. The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer. Claims 1, 19, and 20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claim 1 of U.S. Patent No. 12112159. Claims 1, 19, and 20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claim 1 of U.S. Patent No. 12112158. Although the claims at issue are not identical, they are not patentably distinct from each other. U.S. Patent No. 12112159 Instant Application: 18908092 1. A system for staging data and updating vehicle modules using staged data, the system comprising: 1. A system for staging data and updating vehicle modules using staged data, the system comprising: a user interface device, wherein the user interface device is configured to: receive and store a re-program file from a server; and display a graphical user interface configured to receive a user input to initiate a re-program process for at least one onboard module of a vehicle; and a programming device configured to be physically and communicably coupled to an onboard port of the vehicle, wherein the onboard port is configured to be communicably coupled with the at least one onboard module, the programming device is configured to be communicably coupled, via a wired or wireless communication, to the user interface device, and the programming device is configured to: a programming device configured to be physically and communicably coupled to an onboard port of a vehicle, wherein the onboard port is configured to be communicably coupled with an onboard module, the programming device is configured to be communicably coupled, via Bluetooth low-energy communication, to a user interface device, and the programming device is configured to: receive, via a defined sequence of messages with the user interface device, and store, via defined operations with a local cache, one or combinations of: receive, via a defined sequence of messages with the user interface device, and store, via defined operations with a local data structure, one or combinations of: data checksum map metadata, protocol map metadata, data checksum map information, protocol map information, and a data map (collectively, mapping-and-byte data); data checksum map metadata, protocol map metadata, data checksum map information, protocol map information, and a data map (collectively, mapping-and-byte data); in response to receiving an instruction message from the user interface device, re-program the at least one onboard module using the mapping-and-byte data; and in response to receiving an instruction message from the user interface device, re-program the onboard module using the mapping-and-byte data; and in response to determining a checksum condition is satisfied, transmit a re-program success message to the user interface device. in response to determining a checksum condition is satisfied, transmit a re-program success message to the user interface device. U.S. Patent No. 12112158 Instant Application: 18908092 1. A system for staging data and updating vehicle modules using staged data, the system comprising: 1. A system for staging data and updating vehicle modules using staged data, the system comprising: a user interface device, wherein the user interface device is configured to: receive and store a re-program file from a server; and display a graphical user interface configured to receive a user input to initiate a re-program process for at least one onboard module of a vehicle; and a programming device configured to be physically and communicably coupled to an onboard port of the vehicle, wherein the onboard port is configured to be communicably coupled with the at least one onboard module, the programming device is configured to be communicably coupled, via a wired or wireless communication, to the user interface device, and the programming device is configured to: a programming device configured to be physically and communicably coupled to an onboard port of a vehicle, wherein the onboard port is configured to be communicably coupled with an onboard module, the programming device is configured to be communicably coupled, via Bluetooth low-energy communication, to a user interface device, and the programming device is configured to: receive, via a defined sequence of messages with the user interface device, and store, via defined operations with a local cache: receive, via a defined sequence of messages with the user interface device, and store, via defined operations with a local data structure, one or combinations of: data checksum map metadata, protocol map metadata, data checksum map information, protocol map information, and a data map (collectively, mapping-and-byte data); data checksum map metadata, protocol map metadata, data checksum map information, protocol map information, and a data map (collectively, mapping-and-byte data); in response to receiving an instruction message from the user interface device, re-program the at least one onboard module using the mapping-and-byte data; and in response to receiving an instruction message from the user interface device, re-program the onboard module using the mapping-and-byte data; and in response to determining a checksum condition is satisfied, transmit a re-program success message to the user interface device. in response to determining a checksum condition is satisfied, transmit a re-program success message to the user interface device. Claim Rejections - 35 USC § 103 The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claims 1, 19 and 20 are rejected under 35 U.S.C. 103 as being unpatentable over U.S. Pub. No. 20200219335 to Mintz in view of U.S. Pub. No. 20230327882 to Jayaraman. Per claim 1, Gintz teaches a system for staging data and updating vehicle modules using staged data, the system comprising: a programming device configured to be physically and communicably coupled to an onboard port of a vehicle, wherein the onboard port is configured to be communicably coupled with an onboard module, the programming device is configured to be communicably coupled, via Bluetooth low-energy communication, to a user interface device, and the programming device is configured to: receive, via a defined sequence of messages with the user interface device, and store, via defined operations with a local data structure, one or combinations of: data checksum map metadata, protocol map metadata, data checksum map information, protocol map information, and a data map (collectively, mapping-and-byte data) (see at least paragraphs [0508 & 0511-0516] “The serialized reprogramming request contains the J2534 OEM communications functions, and data, or programming sequence, required to install the ECU profile selected from the manufacturer…” and “Client device 4260 also comprises modules 4261 and 4266. Module 4261 receives the serialized reprogramming command from the system server and retransmits it to local device 4263… the application also establishes a wireless connection by Wi-Fi or Bluetooth (or both) with the local device in order to transfer the reprogramming command request. The reprogramming request is then uploaded to the local device… Buffer 4275 is a data buffer for the J2534 OEM communication functions and data messages submitted for transfer to the vehicle device. In buffer 4275, functions and messages are queued and ordered to reduce the possibility of receiving an error from the vehicle device…”); in response to receiving an instruction message from the user interface device, re-program the onboard module using the mapping-and-byte data (see at least paragraph [0512] “… The deserialized data consists of the J2534 OEM communication function request and data sent from the technician device. The functions are used to communicate with a vehicle device to initiate and execute the ECU reprogramming…”); and in response to determining a checksum condition is satisfied, transmit a re-program success message to the user interface device (see at least paragraph [0499] “… local device 112 will log completion and serialize the message. At step 4200, local device 112 will transmit a completion message to client device 110…”). Mintz does not explicitly teach: bluetooth low-energy communication; and in response to determining a checksum condition is satisfied, transmit a re-program success message to the user interface device. Jayaraman teaches an analogous art relates to installing updates to a vehicle, comprising: Bluetooth low-energy communication (see at least paragraph [0059] “The network devices 908 may each include any of various devices that enable the described components to send and/or receive data from external devices over networks. Examples of suitable network devices 908 include an Ethernet interface, a Wi-Fi transceiver, a cellular transceiver, or a Bluetooth or Bluetooth low energy (BLE)”); and in response to determining a checksum condition is satisfied, transmitting, by the programming device, a re-program success message to the user interface device (see at least paragraphs [0046 & 0051] “At operation 716, the diagnostic tool 110 completes the update session. In an example, the diagnostic tool 110 may be disconnected from the diagnostic port 108. In some examples, the diagnostic tool 110 may also receive a confirmation from the central gateway 112 that the update is completed. After operation 716, the process 700 ends….” & “At operation 806, and as discussed at operation 714, the central gateway 112 performs installation of the updates 602. In an example, the central gateway 112 may receive the updates 602 from the diagnostic tool 110 and may validate that those updates are included on the manifest 502 for installation. The central gateway 112 may also verify correctness of checksums of the updates that are indicated in the manifest 502”). It would have been obvious for a person of an ordinary skilled in the art as of the effective filing date of the claimed invention to modify the teaching of Gintz to incorporate the teaching of Jayaraman to verify the checksum of the updates for correctness. One would have been motivated to verify the checksum of the updates for correctness to ensure correctness of the updates. Per claims 19 and 20, Gintz teaches a computer-implemented method for staging data and updating vehicle modules using staged data, the computer-implemented method comprising: receiving, at a programming device via a defined sequence of messages with a user interface device, and store, at the programming device via defined operations with a local data structure, one or combinations of: data checksum map metadata, protocol map metadata, data checksum map information, protocol map information, and a data map (collectively, mapping-and-byte data) (see at least paragraphs [0508 & 0511-0516] “The serialized reprogramming request contains the J2534 OEM communications functions, and data, or programming sequence, required to install the ECU profile selected from the manufacturer…” and “Client device 4260 also comprises modules 4261 and 4266. Module 4261 receives the serialized reprogramming command from the system server and retransmits it to local device 4263… the application also establishes a wireless connection by Wi-Fi or Bluetooth (or both) with the local device in order to transfer the reprogramming command request. The reprogramming request is then uploaded to the local device…Buffer 4275 is a data buffer for the J2534 OEM communication functions and data messages submitted for transfer to the vehicle device. In buffer 4275, functions and messages are queued and ordered to reduce the possibility of receiving an error from the vehicle device…”); in response to receiving an instruction message from the user interface device, re-programing, by the programming device, an onboard module using the mapping-and-byte data (see at least paragraph [0512] “… The deserialized data consists of the J2534 OEM communication function request and data sent from the technician device. The functions are used to communicate with a vehicle device to initiate and execute the ECU reprogramming…”); and in response to determining a checksum condition is satisfied, transmitting, by the programming device, a re-program success message to the user interface device (see at least paragraph [0499] “… local device 112 will log completion and serialize the message. At step 4200, local device 112 will transmit a completion message to client device 110…”), wherein the programming device is configured to be physically and communicably coupled to an onboard port of a vehicle, the onboard port is configured to be communicably coupled with the onboard module, and the programming device is configured to be communicably coupled, via a wireless communication, to the user interface device (see at least FIG. 1; see also paragraph [0497] “client device 110 will establish a connection with local device 112 via a local area network, Wi-Fi or Bluetooth, or wide area network, GSM, once J2534 Mode is enabled…”). Gintz does not explicitly teach in response to determining a checksum condition is satisfied, transmitting, by the programming device, a re-program success message to the user interface device. Jayaraman teaches an analogous art relates to installing updates to a vehicle, comprising: in response to determining a checksum condition is satisfied, transmitting, by the programming device, a re-program success message to the user interface device (see at least paragraphs [0046 & 0051] “At operation 716, the diagnostic tool 110 completes the update session. In an example, the diagnostic tool 110 may be disconnected from the diagnostic port 108. In some examples, the diagnostic tool 110 may also receive a confirmation from the central gateway 112 that the update is completed. After operation 716, the process 700 ends….” & “At operation 806, and as discussed at operation 714, the central gateway 112 performs installation of the updates 602. In an example, the central gateway 112 may receive the updates 602 from the diagnostic tool 110 and may validate that those updates are included on the manifest 502 for installation. The central gateway 112 may also verify correctness of checksums of the updates that are indicated in the manifest 502”). It would have been obvious for a person of an ordinary skilled in the art as of the effective filing date of the claimed invention to modify the teaching of Gintz to incorporate the teaching of Jayaraman to verify the checksum of the updates for correctness. One would have been motivated to verify the checksum of the updates for correctness to ensure correctness of the updates. Allowable Subject Matter Claims 2 and 12 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to PHILLIP H NGUYEN whose telephone number is (571)270-1070. The examiner can normally be reached Monday-Friday 9:00AM-5:00PM. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Wei Zhen can be reached at (571) 272-3708. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /PHILLIP H NGUYEN/Primary Examiner, Art Unit 2191
Read full office action

Prosecution Timeline

Oct 07, 2024
Application Filed
Oct 07, 2026
Non-Final Rejection mailed — §103, §DOUBLEPATENT (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12783224
APPLICATION DISPOSITION DEFINITION AGENT TO UPDATE APPLICATIONS WITHOUT ACCESS TO SOURCE CODE
3y 12m to grant Granted Nov 03, 2026
Patent 12769526
SYSTEM AND METHOD FOR MAPPING SOURCE CODE COMPONENTS AND RISKS TO RUNTIME
3y 3m to grant Granted Oct 20, 2026
Patent 12762221
Bi-directional Cross-Platform Library for Automated Reflection
4y 0m to grant Granted Oct 13, 2026
Patent 12761883
SECURING SOFTWARE DEVELOPMENT CYCLES WITH ARTIFICIAL INTELLIGENCE CUSTOMIZATION
2y 8m to grant Granted Oct 13, 2026
Patent 12761906
VEHICULAR ELECTRONIC CONTROL DEVICE, REWRITING PROGRAM, AND DATA STRUCTURE
3y 0m to grant Granted Oct 13, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
91%
Grant Probability
99%
With Interview (+11.5%)
2y 10m (~9m remaining)
Median Time to Grant
Low
PTA Risk
Based on 613 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month