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 .
Status of Claims
This is a Final Action for Request for Continued Examination (RCE) application Serial No. 18/358,443. Claims 21-40 have been examined and fully considered.
Claims 21, 23-25, 30, 32-34, and 39 have been amended.
Claims 21-40 are pending in Instant Application.
Response to Arguments/Rejections
Applicant’s arguments, see Remarks, filed 05/07/2025, with respect to the rejection(s) of claim(s) 21-40 under 35 USC § 112 and 103 have been fully considered and are persuasive. Therefore, the rejection has been withdrawn with respect to 35 USC § 112 and 103. However, upon further consideration, a new ground(s) of rejection is made in view of Basir at el. (Pub. No.: US 2013/0030605).
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.
Claim(s) 21-22, 30-31, and 39-40 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhang at el. (Pub. No.: US-2019/0317512; previously recorded), hereinafter, referred to as “Zhang” in view of Basir at el. (Pub. No.: US 2013/0030605), hereinafter, referred to as “Basir”.
Regarding [claim 1], Zhang teaches a computer-implemented method (see, Abstract), comprising:
obtaining sensor data associated with an environment surrounding an autonomous vehicle (see, Paragraphs and [0030]: “LIDAR unit 215 may sense objects in the environment in which the autonomous vehicle is located using lasers. LIDAR unit 215 could include one or more laser sources, a laser scanner, and one or more detectors, among other system components. Cameras 211 may include one or more devices to capture images of the environment surrounding the autonomous vehicle. Cameras 211 may be still cameras and/or video cameras. A camera may be mechanically movable, for example, by mounting the camera on a rotating and/or tilting a platform.”; and [0031]: “Sensor system 115 may further include other sensors, such as, a sonar sensor, an infrared sensor, a steering sensor, a throttle sensor, a braking sensor, and an audio sensor (e.g., microphone). An audio sensor may be configured to capture sound from the environment surrounding the autonomous vehicle.”; [0041]: “While autonomous vehicle 300 is moving along the route, localization module 301 may also obtain real-time traffic information from a traffic information system or server.”; and [0042]: “Based on the sensor data provided by sensor system 115 and localization information obtained by localization module 301, a perception of the surrounding environment is determined by perception module 302. The perception information may represent what an ordinary driver would perceive surrounding a vehicle in which the driver is driving.”;
generating, by a machine-learned cost model and based at least in part on the sensor data,…cost data descriptive of costs for a plurality of positions in the environment (see, Paragraph [0038]: “Based on driving statistics 123, machine learning engine 122 generates or trains a set of rules, algorithms, and/or models 124 for a variety of purposes, including trained models to determine if an obstacle detected by sensors of the ADV is a stop sign or a traffic light. Rules/algorithms 124 may further include traffic rules for the ADV to follow and algorithms to calculate a quartic and/or a quintic polynomial for a trajectory. Algorithms 124 may further include algorithms to generate trajectory candidates as a final trajectory. Algorithms 124 may further include algorithms to calculate trajectory costs for selecting a target trajectory from the trajectory candidates, including algorithms to calculate objective costs, safety costs, and comfort
costs. Algorithms 124 can then be uploaded onto ADVs for real-time trajectory generation for autonomous driving”);
generating a plurality of trajectory proposals for the autonomous vehicle, the plurality of trajectory proposals respectively corresponding to a plurality of potential paths of the autonomous vehicle through the environment (see, Paragraph [0021]: “a system generates a plurality of trajectory candidates for an autonomous driving vehicle (ADV) from a starting point to an end point of a particular driving scenario. The system generates a reference trajectory corresponding to the driving scenario based on a current state of the ADV associated with the starting point and an end state of the ADV associated with the end point, where the reference trajectory is associated with an objective. For each of the trajectory candidates, the system compares the trajectory candidate with the reference trajectory to generate an objective cost representing a similarity between the trajectory candidate and the reference trajectory”);
…
selecting a target trajectory from the one or more trajectory proposals based at least in part on the respective scores for the plurality of trajectory proposals (see, Paragraphs [0076]: “At block 1103, for each of the trajectory candidates, processing logic compares the trajectory candidate with the reference trajectory to generate an objective cost representing a similarity between the trajectory candidate and the reference trajectory. At block 1104, processing logic selects one of the trajectory candidates as a target trajectory for driving the ADV based on objective costs of the trajectory candidates”; and [0078][-[0079]: “for each of the trajectory candidates, processing logic further determines a changing rate of acceleration along the trajectory candidate, calculates a comfort cost for the trajectory candidate based on the changing rate of acceleration along the trajectory candidate, and calculates a total trajectory cost for the trajectory candidate based on the objective cost and the comfort cost.
The target trajectory can then be selected from the trajectory candidates as having a lowest total trajectory cost. In another embodiment, calculating a comfort cost for the trajectory candidate includes segmenting the trajectory candidate into a number of candidate segments, for each of the candidate segments, calculating a segment comfort cost for the candidate segment based on a changing rate of an acceleration associated with the candidate segment, and calculating the
comfort cost based on the segment comfort costs of the candidate segments. In another embodiment, the comfort cost is calculated based on a sum of segment comfort costs
of the candidate segments.”); and
controlling a motion of the autonomous vehicle based at least in part on the selected target trajectory (see, Paragraph [0052]: “trajectory generation module 308 can generate longitudinal trajectory candidates for ADV 101. The trajectory candidates may be generated in view of factors such as safety, comfort, and traffic rules. Trajectory evaluation module 309, also referred to as trajectory selection module, can then select one of the generated trajectory candidates as the trajectory to control the ADV based on evaluation criteria 315 and using cost
functions 316”; and [0063]: “Once trajectory candidates are generated from all possible end conditions, in one embodiment, an evaluation module, such as evaluation module 309 of FIG. 3A, evaluates each of the trajectory candidates for a best trajectory candidate. Trajectory candidate selector 411 can then select this best trajectory candidate to control the ADV.”).
As Zhang discloses
accessing, …, the generated cost data to obtain, for the plurality of trajectory proposals, respective scores for the plurality of trajectory proposals (see, Paragraph [0076]: “Referring to FIG. 11, at block 1101, generates a number of trajectory candidates for an autonomous driving vehicle (ADV) from a starting point to an end point of a particular driving scenario. At block 1102, processing logic generates a reference trajectory corresponding to the driving scenario based on a current state of the ADV associated with the starting point and an end state of the ADV associated with the end point, where the reference trajectory is associated with an objective. At block 1103, for each of the trajectory candidates, processing logic compares the trajectory candidate with the reference trajectory to generate an objective cost representing a similarity between the trajectory candidate and the reference trajectory”, however, Zhang does not explicitly disclose
…
accessing, using index values based at least in part on the plurality of potential paths, the generated indexed cost data to obtain, for the plurality of trajectory proposals, respective scores for the plurality of trajectory proposals;
…
Additionally, Basir teaches
….
accessing, using index values based at least in part on the plurality of potential paths, the generated indexed cost data to obtain, for the plurality of trajectory proposals, respective scores for the plurality of trajectory proposals (see, Abstract; Paragraphs [0022]-[0023]: “As another method for calculating a route, the route is calculated based upon a “safety index' 54 for the trip. A safety index 54 for potential routes is calculated based upon a road characteristics in the road database 76, such as number of lanes, hills, flat, visibility, historical traffic conditions, etc. as well as current traffic conditions 62, historical accident rates 64, route topography 66 (which may be part of the road database 76), etc. The system can give the user a number of routing options from the start to destination based time cost, distance cost, fuel cost and the safety index for each. The user can also specify a safety index goal 68, so that the system will determine routes that meet the safety index goal 68 and selects among those routes based upon other costs (e.g. time, energy consumption, etc.).”);
selecting a target trajectory from the one or more trajectory proposals based at least in part on the respective scores for the plurality of trajectory proposals (see, Paragraph [0023]: “The system can give the user a number of routing options from the start to destination based time cost, distance cost, fuel cost and the safety index for each. The user can also specify a safety index goal 68, so that the system will determine routes that meet the safety index goal 68 and selects among those routes based upon other costs (e.g. time, energy consumption, etc.).”)…
…
Accordingly, it would have been obvious to one of ordinary skill in the art before the filing of the invention by implement trajectory proposals based at least in part on the respective scores taught by Basir to yield similar successful results. One would be motivated to make this modification in order to convey calculating a route, the system may take into account one or more new considerations. First, the system may take into account a safety index; i.e. which route is safer. Second, the system may take into account which route will consume less energy, particularly where the vehicle is an electric vehicle, which has different efficiencies in certain types of road conditions. (see at least Paragraph [0005]).
As to [claim 22], Zhang in view of Kobilarov discloses the computer-implemented method of claim 21. Zhang in view of Basir teaches wherein: the cost data describes costs for possible positions that the autonomous vehicle can take within a planning horizon;
the respective potential path describes a plurality of proposed positions that the autonomous vehicle can take at a plurality of timesteps within the planning horizon; and the method comprises:
obtaining, from the indexed cost data, the cost values associated with the proposed positions at the plurality of timesteps. (see, Paragraph [0067]: “Referring to FIGS. 7 and 8, in one embodiment, a safety cost can be evaluated (via safety cost determiner 703) using a station-time graph, such as station-time graph 800 of FIG. 8. Station-time graph 800 can be station-time graph 610 of FIG. 6B having obstacles 612, 614, 616, and trajectory candidate 615 to be evaluated for safety. In one embodiment, trajectory candidate 615 is segmented, by trajectory segmenter 701, into a number of segments 801 according to a predetermined time resolution. Each of the segments 801 can have an associated end point 803 ( e.g., a timestamp ). Trajectory segmenter 701 then bounds end points 803 (or timestamps) with boxes 805. Boxes 805 can have a predetermined width that can represent a width of the ADV. In one embodiment, safety cost determiner 703 traverses each of the boxes 805 to determine if any edges of boxes 805 would intersect a boundary of any static/dynamic obstacles in station-time graph 800, e.g., obstacles 612, 614, 616. If there is an intersection ( e.g., a possible collision) then the trajectory candidate may be removed from selection. In another embodiment, a closest distance from trajectory candidate 615 to any boundaries of obstacles 612, 614, 615 can be calculated along all timestamps of trajectory candidate 615. The safety cost can be an inverse of the calculated distance, e.g., a closer distance has a higher cost. In this case, a trajectory candidate which is far away from surrounding obstacles, e.g., a lower cost, may be deemed safer than a trajectory candidate which may be closer to the surrounding obstacles.”; and [0078]: “for each of the trajectory candidates, processing logic further identifies an obstacle that is closest to the trajectory candidate, measure a distance between the trajectory candidate and the obstacle, calculates a safety cost associated with the trajectory candidate based on the distance between the trajectory candidate and the obstacle, and calculates a total trajectory cost for the trajectory candidate based on the objective cost and the safety cost. The target trajectory can then be selected from the trajectory candidates as having a lowest total trajectory cost.”; and [0079]: “In one embodiment, for each of the trajectory candidates, processing logic further determines a changing rate of acceleration along the trajectory candidate, calculates a comfort cost for the trajectory candidate based on the changing rate of acceleration along the trajectory candidate, and calculates a total trajectory cost for the trajectory candidate based on the objective cost and the comfort cost. The target trajectory can then be selected from the trajectory candidates as having a lowest total trajectory cost. In another embodiment, calculating a comfort cost for the trajectory candidate includes segmenting the trajectory candidate into a number of candidate segments, for each of the candidate segments, calculating a segment comfort cost for the candidate segment based on a changing rate of an acceleration associated with the candidate segment, and calculating the comfort cost based on the segment comfort costs of the candidate segments. In another embodiment, the comfort cost is calculated based on a sum of segment comfort costs of the candidate segments.”)
Additionally, Basir teaches wherein:
…
obtaining, from the indexed cost data, the cost values associated with the proposed positions at the plurality of timesteps (see, Paragraph [0023]: “calculating a route, the route is calculated based upon a “safety index' 54 for the trip. A safety index 54 for potential routes is calculated based upon a road characteristics in the road database 76, such as number of lanes, hills, flat, visibility, historical traffic conditions, etc. as well as current traffic conditions 62, historical accident rates 64, route topography 66 (which may be part of the road database 76), etc. The system can give the user a number of routing options from the start to destination based time cost, distance cost, fuel cost and the safety index for each. The user can also specify a safety index goal 68, so that the system will determine routes that meet the safety index goal 68 and selects among those routes based upon other costs (e.g. time, energy consumption, etc.).”).
Accordingly, it would have been obvious to one of ordinary skill in the art before the filing of the invention to further modify Zhang in view of Basir by combining obtaining, from the cost data, the cost values associated with the proposed positions at the plurality of timesteps as taught by Basir. One would be motivated to make this modification in order to convey calculating a route, the system may take into account one or more new considerations. First, the system may take into account a safety index; i.e. which route is safer. Second, the system may take into account which route will consume less energy, particularly where the vehicle is an electric vehicle, which has different efficiencies in certain types of road conditions. (see at least Paragraph [0005]).
Regarding claim 30 , recites analogous limitations that are present in claim 21, therefore claim 30 would be rejected for the same/similar premise above.
Regarding claim 31, recites analogous limitations that are present in claim 22, therefore claim 31 would be rejected for the same/similar premise above.
Regarding claim 39 recites analogous limitations that are present in claim 21, therefore claim 39 would be rejected for the same/similar premise above.
Regarding claim 40 recites analogous limitations that are present in claim 22, therefore claim 40 would be rejected for the same/similar premise above.
Claim(s) 27 and 36 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhang in view of Basir, and in view of Kobilarov et al. (Pub. No.: US-20200387158; previously recorded), hereinafter, referred to as “Kobilarov”.
As to [claim 27], Zhang in view of Basir teaches the computer-implemented method of claim 26. Kobilarov teaches further wherein the cost volume comprises a temporal dimension comprising the plurality of timesteps (see at least Paragraph [0020]: “the temporal logic formulas can include statements about the world that reflect proper driving behavior for an autonomous vehicle, for example. As candidate routes and trajectories are generated for the autonomous vehicles, the routes and trajectories can be evaluated using the temporal logic formulas to determine if the trajectories satisfy the temporal logic formulas , in which case , trajectories can be rejected, or evaluated with respect to other costs and constraints to select the highest performing trajectory”).
Accordingly, it would have been obvious to one of ordinary skill in the art before the filing of the invention to further modify Zhang in view of Basir by combining wherein the cost volume comprises a temporal dimension comprising the plurality of timesteps as taught by Basir. One would be motivated to make this modification in order to determine a trajectory based on optimizing safety, costs, and performance can correspond to improved safety outcomes and/or increased comfort for occupants of an autonomous vehicle (see at least Paragraph [0025]).
Regarding claim 36, recites analogous limitations that are present in claim 27, therefore claim 36 would be rejected for the same/similar premise above.
Claim(s) 28-29 and 37-38 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhang in view of Basir, and in view of Muller et al. (US-20190384303; previously recorded), hereinafter, referred to as “Muller”.
As to [claim 28], Zhang in view of Basir teaches the computer-implemented method of claim 21. As Zhang wherein generating the one or more trajectory proposals for the autonomous vehicle, however, neither Zhang nor Basir teaches
However, Muller teaches
….comprises: sampling a set of physically possible trajectories for the autonomous vehicle (see at least Paragraph [0024]: “Path planning may be used to aid in navigation through environments by autonomous machines controlled by autonomous systems (e.g., an autonomous driving software stack). In embodiments of the present disclosure, and to help determine a path for the autonomous vehicles , a deep neural network (DNN) e.g., a convolutional neural network (CNN) may be used to generate one or more trajectory points that correspond to a predicted or recommended trajectory for the autonomous vehicle”).
As to [claim 29], the combination of Zhang, Basir and Muller teaches the computer-implemented method of claim 28. Muller teaches further wherein the sampling comprises: sampling a shape of a curve (see at least Figure 2B; Paragraph [0026]: “the trajectory generated by the machine learning model may be more accurate and thus more effective in path planning for the vehicle. For example, where only two-dimensional (2D) points are used, the path around a lateral curve or turn that also includes a vertical curve (e.g., a hill) may be different than the same lateral curve or tum on a flat surface. This may result in less accurate trajectory points from the machine learning model (e.g., the path through the curve may be offset to the left or right, closer to the lane markings or boundary than center-of-the-lane driving)”); sampling a motion parameter comprising at least one of: a velocity parameter or an acceleration parameter; and combining the sampled shape and the sampled motion parameter to obtain a respective possible trajectory (see at least Paragraph [0066]: “The trajectory data 112 may be representative of a recommended trajectory 142. However, in some examples, the output 110 may include control data for following the recommended trajectory 142 (e.g., for controlling the vehicle 138 according to the recommended trajectory 142, such as steering angle, acceleration, deceleration, etc.). The trajectory data 112 may include, in some examples, a trajectory point(s) 140 (e.g., as represented by 2D or 3D coordinates in world space, and/or 2D coordinates in image space) along the recommended vehicle trajectory 142. In some examples, only a single trajectory point 140 (e.g., the next trajectory point for the vehicle 138 in the sequence of discretized trajectory steps) may be output by the machine learning model(s) 108A. In other examples, more than one trajectory point 140 may be output. As another example, an entire trajectory may be output, which may be extrapolated from two or more trajectory points 140”).
Regarding claim 37 recites analogous limitations that are present in claim 28, therefore claim 37 would be rejected for the same/similar premise above.
Regarding claim 38 recites analogous limitations that are present in claim 29, therefore claim 38 would be rejected for the same/similar premise above.
Possible Allowable Subject Matter
Claims 23-26 and 32-35 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
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to BAKARI UNDERWOOD whose telephone number is (571)272-8462. The examiner can normally be reached M - F 8:00 TO 4:30.
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, Abby Flynn can be reached on (571) 272-9588. 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.
/B.U./Examiner, Art Unit 3663
/JAMES M MCPHERSON/Examiner, Art Unit 3663