Prosecution Insights
Last updated: November 20, 2026
Application No. 19/290,676

APPARATUS AND METHOD FOR PROVIDING REAL-TIME TRAFFIC INFORMATION

Non-Final OA §101§103
Filed
Aug 05, 2025
Priority
Dec 16, 2024 — RE 10-2024-0186674
Examiner
MACIOROWSKI, GODFREY ALEKSANDER
Art Unit
3658
Tech Center
3600 — Transportation & Electronic Commerce
Assignee
Kia Corporation
OA Round
1 (Non-Final)
61%
Grant Probability
Moderate
1-2
OA Rounds
1y 5m
Est. Remaining
72%
With Interview

Examiner Intelligence

Grants 61% of resolved cases
61%
Career Allowance Rate
74 granted / 122 resolved
+8.7% vs TC avg
Moderate +11% lift
Without
With
+10.9%
Interview Lift
resolved cases with interview
Typical timeline
2y 9m
Avg Prosecution
26 currently pending
Career history
162
Total Applications
across all art units

Statute-Specific Performance

§101
15.1%
-24.9% vs TC avg
§103
53.7%
+13.7% vs TC avg
§102
17.9%
-22.1% vs TC avg
§112
12.3%
-27.7% vs TC avg
Black line = Tech Center average estimate • Based on career data from 122 resolved cases

Office Action

§101 §103
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 . Status of Claims Claims 1 and 6 contains language that is being interpreted under 35 U.S.C. 112(f). Claims 1-16 are rejected under 35 U.S.C. 101 as being directed towards an abstract idea without significantly more. Claims 1 and 9 are rejected under 35 U.S.C. 103 as being unpatentable over John (US 2021/0172758). Claims 2-3 and 10-11 are rejected under 35 U.S.C. 103 as being unpatentable over John in view of Guan (US 2021/0174669). Claims 4-6 and 12-14 are rejected under 35 U.S.C. 103 as being unpatentable over John in view of Guan in view of Chandraker (US 2025/0148911). Claims 7-8 and 15-16 are rejected under 35 U.S.C. 103 as being unpatentable over John in view of Guan in view of Chandraker in view of Hranac (US 2014/0136089). Priority The priority date for this application is 12/16/2024. Claim Interpretation The following is a quotation of 35 U.S.C. 112(f): (f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph: An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof. The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked. As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph: (A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function; (B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and (C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function. Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function. Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function. Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are: “a traffic information collection unit configured to collect…”, “a traffic congestion section determination unit configured to determine…”, “a traffic congestion section information providing unit configured to provide traffic congestion section information…”, in Claim 1 and “a text generation unit configured to generate…” in Claim 6. Because these claim limitations are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, they are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof (See Paragraph [0045] of the Specification of the instant application). If applicant does not intend to have these limitations interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitations to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitations recite sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. Claim Rejections - 35 USC § 101 35 U.S.C. 101 reads as follows: Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title. Claims 1-16 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. A step-by-step analysis of the independent claims is provided below: Step 1: Is the claim to a process, machine, manufacture, or composition of matter? Yes, Claim 1 is directed towards an apparatus (machine) and Claim 9 is directed towards a method (process). Step 2A Prong One: does the claim recite an abstract idea, law of nature, or natural phenomenon? Yes, the independent claims recite, “collect[ing]…traffic information comprising a real-time travel speed”, “determin[ing] a normal speed range…”, “provid[ing] traffic congestion section information…”. These claim limitations represent an abstract idea as they are functions that can be performed solely within the human mind. Step 2A Prong Two: does the claim recite additional elements that integrate the judicial exception into a practical application? No, independent claims do not recite additional elements and therefore are not integrated into a practical application. Step 2B: does the claim recite additional elements that amount to significantly more than the judicial exception? No, as previously stated the independent claims do not recite additional elements and therefore cannot cause the claim to be directed away from the abstract idea and therefore does not cause the claim as-a-whole to amount to significantly more than the judicial exception. Dependent Claims: none of the dependent claims contain additional elements that would be sufficient to either integrate the abstract idea into a practical application or cause the claim as-a-whole to amount to significantly more than the judicial exception. Claim Rejections - 35 USC § 103 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. 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. The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows: 1. Determining the scope and contents of the prior art. 2. Ascertaining the differences between the prior art and the claims at issue. 3. Resolving the level of ordinary skill in the pertinent art. 4. Considering objective evidence present in the application indicating obviousness or nonobviousness. This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention. Claims 1 and 9 are rejected under 35 U.S.C. 103 as being unpatentable over John (US 2021/0172758). As per Claim 1: John teaches the following limitations: “An apparatus for providing real-time traffic information, the apparatus comprising: a traffic information collection unit configured to collect, in real time while a user vehicle is travelling along a travel route, traffic information comprising a real-time travel speed and a cause of traffic congestion” John Paragraph [0070] teaches real-time collection of traffic data including traffic speed. Figure 4 teaches identifying congestion compared to normal traffic and the cause of said congestion. “a traffic congestion section determination unit configured to determine a normal speed range based on the traffic information and determine a section with a real-time travel speed lower than a lower limit of the normal speed range as a traffic congestion section” John Figure 4 teaches identifying a normal route that has been slowed based on a congestion event and identifying an alternative route that is shorter. It would have been obvious to one of ordinary skill that the comparison of a normal speed would have a range of normally acceptable values. “and a traffic congestion section information providing unit configured to provide traffic congestion section information comprising at least one of a location of the traffic congestion section, the cause of the traffic congestion, or an expected delay time based on the traffic information and the traffic congestion section included in the travel route of the user vehicle.” John Figure 4 teaches identifying a location of traffic congestion. It would have been obvious to one of ordinary skill in the art, before the effective filing date, to modify the system taught by John with the range of normal values. One of ordinary skill in the art would have been motivated to make this modification, with a reasonable expectation of success, in order to make the system more effective by providing a useful range of normal values. As per Claim 9: this claim is substantially similar to Claim 1 and is therefore rejected using the same references and rationale. Claims 2-3 and 10-11 are rejected under 35 U.S.C. 103 as being unpatentable over John in view of Guan (US 2021/0174669). With regards to Claim 2, John teaches all of the limitations of Claim 1 but does not teach the following limitations that Guan teaches: “wherein the traffic information collection unit is further configured to collect the cause of the traffic congestion based on a real-time traffic image provided through an intelligent transport system and an image analysis model, and wherein the traffic information comprises at least one of real-time traffic accident information, rally information, event information, traffic control information, or roadwork information.” Guan [Abstract] teaches identifying traffic congestion based on traffic image data. It would have been obvious to one of ordinary skill in the art, before the effective filing date, to modify the system taught by John with the identification of traffic congestion via images taught by Guan. Guan and John are analogous references as they are both directed towards ascertaining traffic information. One of ordinary skill in the art would have been motivated to make this modification, with a reasonable expectation of success, in order to make the system more effective by utilizing a cheap sensor type to extract traffic information. With regards to Claim 3, John in view of Guan teaches all of the limitations of Claim 2 and further teaches the following limitations: “wherein the traffic congestion section determination unit is further configured to determine the normal speed range according to a preset cycle by using a traffic pattern prediction model that uses the real-time travel speed as training data. John Paragraph [0019] teaches training a machine learning system to determine normal travel speed on a road segment. With regards to Claim 10, this claim is substantially similar to Claim 2 and is therefore rejected using the same references and rationale. With regards to Claim 11, this claim is substantially similar to Claim 3 and is therefore rejected using the same references and rationale. Claims 4-6 and 12-14 are rejected under 35 U.S.C. 103 as being unpatentable over John in view of Guan in view of Chandraker (US 2025/0148911). With regards to Claim 4, John in view of Guan teaches all of the limitations of Claim 3 but does not teach the following limitations that Chandraker suggests: “wherein the traffic congestion section information providing unit comprises a vector generation unit configured to: generate a traffic information vector by dividing and expanding the traffic information based on at least one of a preset token count unit, a sentence boundary, or a paragraph boundary and performing vectorization; and generate a route vector by dividing and expanding the traffic congestion section included in the travel route of the user vehicle based on at least one of a preset token count unit, a sentence boundary, or a paragraph boundary and performing vectorization.” Chandraker Paragraph [0049] suggests using large language models to present traffic information. It would have been obvious to one of ordinary skill in the art, before the effective filing date, to modify the system taught by John in view of Guan with the large language model identification of traffic information suggested by Chandraker. These references are analogous as they are all related to traffic information acquisition. One of ordinary skill in the art would have been motivated to make this modification, with a reasonable expectation of success, in order to make the system more effective by using a known method of machine learning to facilitate traffic information. With regards to Claim 5, John in view of Guan in view of Chandraker suggests all of the limitations of Claim 4 and further suggests the following limitations: “wherein the traffic congestion section information providing unit further comprises a vector search unit configured to retrieve a traffic information vector that is close to the route vector.” Chandraker Paragraphs [0043]-[0045] suggest identifying routes by a large language model. It would have been obvious to one of ordinary skill in the art, before the effective filing date, to modify the system taught by John in view of Guan with the large language model identification of traffic information suggested by Chandraker. One of ordinary skill in the art would have been motivated to make this modification, with a reasonable expectation of success, in order to make the system more effective by using a known method of machine learning to facilitate traffic information. With regards to Claim 6, John in view of Guan in view of Chandraker suggests all of the limitations of Claim 5 and further teaches the following limitations: “wherein the traffic congestion section information providing unit further comprises a text generation unit configured to generate a sentence comprising at least one of the location of the traffic congestion section, the cause of the traffic congestion, or the expected delay time based on the retrieved traffic information vector and a preset sentence template, and wherein the traffic congestion section information providing unit is further configured to provide the traffic congestion section information based on the generated sentence.” John Figure 4 teaches producing a sentence based on cause of traffic congestion. With regards to Claim 12, this claim is substantially similar to Claim 4 and is therefore rejected using the same references and rationale. With regards to Claim 13, this claim is substantially similar to Claim 5 and is therefore rejected using the same references and rationale. With regards to Claim 14, this claim is substantially similar to Claim 6 and is therefore rejected using the same references and rationale. Claims 7-8 and 15-16 are rejected under 35 U.S.C. 103 as being unpatentable over John in view of Guan in view of Chandraker in view of Hranac (US 2014/0136089). With regards to Claim 7, John in view of Guan in view Chandraker teaches all of the limitations of Claim 6 but does not teach the following limitations that Hranac teaches: “wherein the expected delay time is determined based on the normal speed range and the real-time travel speed.” Hranac Paragraph [0030] teaches identifying the amount of delay based on the comparing live speed to normal speed for road segments. It would have been obvious to one of ordinary skill in the art, before the effective filing date, to modify the system taught by John in view of Guan in view of Chandraker with the delay time comparison taught by Hranac. These references are all analogous as they are all related to traffic information acquisition. It would have been obvious to one of ordinary skill in the art, before the effective filing date, to make these modifications in order to make the system more effective by providing more useful information. With regards to Claim 8. John in view of Guan in view of Chandraker in view of Hranac teaches all of the limitations of Claim 6 and further teaches the following limitations: “wherein the text generation unit is further configured to generate the sentence by using a retrieval-augmented generation large language model.” John Paragraph [0019] teaches outputting speed predictions based on a machine learning system. Figure 4 teaches this output being presented in sentence form. It would be obvious to one of ordinary skill in the art to use any machine learning method for producing this sentence. With regards to Claim 15, this claim is substantially similar to Claim 7 and is therefore rejected using the same references and rationale. With regards to Claim 16, this claim is substantially similar to Claim 8 and is therefore rejected using the same references and rationale. Related References Yang (US 2019/0310100) Related to dynamic lane-level navigation. Baik (US 2019/0172344) Relate to forecasting traffic conditions. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to Examiner Godfrey Maciorowski, whose telephone number is (571) 272-4652. The examiner can normally be reached on Monday-Friday from 7:30am to 5:00pm EST. Examiner interviews are available via telephone 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 examiner by telephone are unsuccessful the examiner’s supervisor, Thomas Worden can be reached on (571) 272-4876. The fax phone number for the organization where this application or proceeding is assigned is (571) 273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see https://ppair-my.uspto.gov/pair/PrivatePair. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /GODFREY ALEKSANDER MACIOROWSKI/Examiner, Art Unit 3658
Read full office action

Prosecution Timeline

Aug 05, 2025
Application Filed
Sep 04, 2026
Non-Final Rejection mailed — §101, §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12798507
CRASH DETECTION CIRCUIT FOR BATTERY MANAGEMENT UNIT
2y 0m to grant Granted Nov 17, 2026
Patent 12780264
OPERATION DEVICE FOR VEHICLE, VEHICLE, OPERATION PROCESSING METHOD, AND NON-TRANSITORY MEMORY MEDIUM
2y 0m to grant Granted Nov 03, 2026
Patent 12769306
CONTROL SYSTEM AND METHOD
4y 11m to grant Granted Oct 20, 2026
Patent 12736354
Apparatus and Method for Hybrid Navigation of a Pedestrian Tour
2y 7m to grant Granted Sep 15, 2026
Patent 12736366
ELEVATION IN TRAVERSABLE SURFACE MAPS FOR AUTONOMOUS VEHICLE NAVIGATION
2y 5m to grant Granted Sep 15, 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
61%
Grant Probability
72%
With Interview (+10.9%)
2y 9m (~1y 5m remaining)
Median Time to Grant
Low
PTA Risk
Based on 122 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