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 .
Claim Rejections - 35 USC § 102
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 the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1-20 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Neishaboori et al. (US 2022/0397415).
In regard to claim 1, Neishaboori disclosed a method for a vehicle computing system of a host vehicle (HV), comprising:
receiving one or more messages from one or more remote vehicles (RVs) via Vehicle- to-Everything (V2X) communication, wherein each of the one or more messages comprise one or more RV parameters; Neishaboori [0030]
determining one or more HV parameters; Neishaboori [0022]-[0023]
performing target classification based on the one or more HV parameters and the one or more RV parameters of each of the one or more RVs to identify a subset of the one or more messages; Neishaboori [0039]
transmitting the subset of the one or more messages to an application of the vehicle computing system for processing. Neishaboori [0040]-[0046]
In regard to claim 2, Neishaboori disclosed the method of claim 1, wherein the one or more messages are safety messages. Neishaboori [0039]
In regard to claim 3, Neishaboori disclosed the method of claim 1, wherein the one or more RV parameters comprise one or more of location, speed, direction of travel, vehicle length, acceleration, yaw rate, and steering wheel angle. Neishaboori [0039]
In regard to claim 4, Neishaboori disclosed the method of claim 1, wherein the one or more HV parameters comprise one or more of location, speed, intended route, steering wheel angle, yaw rate, and vehicle length. Neishaboori [0022]-[0023]
In regard to claim 5, Neishaboori disclosed the method of claim 1, wherein performing target classification is further based on one or more environmental parameters, including traffic status and road geometry. Neishaboori [0039]
In regard to claim 6, Neishaboori disclosed the method of claim 1, further comprising determining a relative speed between the HV and each of the one or more RVs, and wherein performing target classification is based on the relative speed. Neishaboori [0039]
In regard to claim 7, Neishaboori disclosed the method of claim 6, wherein performing target classification comprises generating a dynamic target zone based on the one or more HV parameters, the one or more RV parameters, and the relative speed. Neishaboori [0039], [0047]
In regard to claim 8, Neishaboori disclosed a vehicle computing system of a host vehicle (HV), comprising:
one or more processors; and
a memory coupled to the one or more processors, the memory storing instructions that, when executed by the one or more processors, cause the one or more processors to:
receive one or more messages from one or more remote vehicles (RVs); Neishaboori [0030]
determine one or more parameters of the one or more RVs based on data in the one or more messages, wherein the one or more parameters of the one or more RVs comprise at least RV speed and RV direction of travel; Neishaboori [0039]
determine one or more conditions of the HV, wherein the one or more conditions of the HV comprise at least HV speed and HV direction of travel; Neishaboori [0039]
determine a relative speed between the HV and each of the one or more RVs based on the HV speed, RV speed, RV direction of travel, and HV direction of travel; Neishaboori [0039]
classify the one or more messages based on the one or more parameters of the one or more RVs, the one or more conditions of the HV, and the relative speed; Neishaboori [0039]
identify a subset of the one or more RVs as relevant targets based on classification; and Neishaboori [0040]-[0046]
transmit the subset of the one or more RVs for further processing by the vehicle computing system. Neishaboori [0040]-[0046]
In regard to claim 9, Neishaboori disclosed the vehicle computing system of claim 8, further comprising determining a target zone based on the one or more parameters of the one or more RVs, the one or more conditions of the HV, and the relative speed. Neishaboori [0039], [0047]
In regard to claim 10, Neishaboori disclosed the vehicle computing system of claim 8, further comprising determining one or more environmental conditions, including road geometry and traffic status. Neishaboori [0039]
In regard to claim 11, Neishaboori disclosed the vehicle computing system of claim 10, wherein the one or more environmental conditions are determined based on a global positioning system (GPS) associated with the vehicle computing system. Neishaboori [0022]
In regard to claim 12, Neishaboori disclosed the vehicle computing system of claim 9, wherein the target zone is determined by determining a zone length based on the relative speed and a Time-to-Collision (TTC) and determining a future position of the HV based on yaw rate and HV speed. Neishaboori [0030], [0039], [0054]
In regard to claim 13, Neishaboori disclosed the vehicle computing system of claim 8, wherein the one or more conditions of the HV further include vehicle location, direction of travel, and intended route. Neishaboori [0022]-[0023]
In regard to claim 14, Neishaboori disclosed the vehicle computing system of claim 8, wherein the one or more parameters of the one or more RVs further include vehicle location and direction of travel. Neishaboori [0039]
In regard to claim 15, Neishaboori disclosed the vehicle computing system of claim 8, wherein the further processing comprises determining one or more notifications to be presented to a driver based on messages corresponding to the subset of the one or more RVs. Neishaboori [0040]-[0046]
In regard to claim 16, Neishaboori disclosed a method for dynamic target classification, comprising:
determining one or more conditions based on one or more basic safety messages (BSMs) received by a vehicle computing system of a host vehicle (HV) from one or more RVs and one or more vehicle specifics of the HV; Neishaboori [0039]
generating a dynamic target zone based on the one or more conditions; Neishboori [0039], [0047]
determining relevancy of each of the one or more RVs based on the one or more conditions and the dynamic target zone; and Neishboori [0039], [0047]
transmitting a subset of the one or more BSMs corresponding to one or more relevant RVs for further processing. Neishboori [0039], [0047]
In regard to claim 17, Neishaboori disclosed the method of claim 16, wherein the one or more conditions comprise HV speed, RV speed of each of the one or more RVs, relative speed between the HV and each of the one or more RVs, HV location, and location of each of the one or more RVs. Neishaboori [0039]
In regard to claim 18, Neishaboori disclosed the method of claim 17, wherein relative speed between the HV and each of the one or more RVs is determined based on the HV speed and the RV speed of each of the one or more RVs. Neishaboori [0039]
In regard to claim 19, Neishaboori disclosed the method of claim 17, wherein the one or more conditions further comprise one or more environmental parameters, including road geometry and traffic status, and intended route of the HV. Neishaboori [0039]
In regard to claim 20, Neishaboori disclosed the method of claim 17, wherein generating the dynamic target zone based on the one or more conditions comprises determining a zone length based on the relative speed and a Time-To-Collision (TTC). Neishaboori [0039], [0047], [0054]
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Reddy US 2024/0265809
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Jeffrey R. Swearingen whose telephone number is (571)272-3921. The examiner can normally be reached M-F 8:00 am - 5:00 pm.
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, Oscar Louie can be reached at 571-270-1684. 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.
Jeffrey R. Swearingen
Primary Examiner
Art Unit 2445
/Jeffrey R Swearingen/Primary Examiner, Art Unit 2445
Prosecution Insights