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 § 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.
Claim(s) 1-20 are rejected under 35 U.S.C. 103 as being unpatentable over Fouad et al (U.S. 2021/0339759) and further in view of Liu et al (U.S. 2016/0320194).
1. As per claims 1,12,17 Fouad disclosed a method comprising:
collecting sensor data from one or more in-vehicle sensors of a vehicle; processing the sensor data to determine one or more contextual parameter signals associated with the vehicle [Other in-vehicle sensors can include a microphone for collecting voice data or audio data, and sensors to collect physiological data. Data relating to the vehicle can also be collected. Additional sensors can be used to collect data outside the vehicle, including image sensors, radar sensors, weather sensors, light sensors, and so on. The cognitive state data is collected from the operator or passenger of a vehicle] (Paragraph. 0015), one or more passengers of the vehicle, or a combination thereof, [A vehicle travel route can include one or more segments. The mapping of the cognitive state data can be based on cognitive state data collected from the driver or operator of a vehicle, from passengers in the vehicle, from occupants of other vehicles, and so on] (Paragraph. 0047); determining a context associated with a trip engaged by the vehicle or the one or more passengers based on the one or more contextual parameter signals [The vehicle route mood map can enable vehicle route planning. In a usage example, a driver cognitive state of sadness can indicate that planning a beautiful vehicle travel route would be recommended. The route planning can include avoiding stressful areas when the vehicle occupant's cognitive state is one of stress. The route planning can include planning for other criteria or factors such as shortest route, least traffic, accident site avoidance, and the like. In embodiments, the vehicle route mood map can enable planning for routes to avoid road construction or to navigate road rearrangement, and so on. The vehicle route mood map can support other information updating. In embodiments, the vehicle route mood map can enable vehicle route redeployment. The vehicle route can be changed, updated, rerouted, redeployed, etc., based on a changed cognitive state of the vehicle driver, a traffic accident, changing weather conditions, etc] (Paragraph. 0050);
determining a routing cost factor based on the context;
determining, by a routing engine configured to access a geographic database a navigation route (Paragraph. 0054), navigation guidance information, or a combination thereof based on the routing cost factor [the navigation app can include Waze™, Google Maps™, or Apple Maps™. The rendering of information that was updated can also be based on other factors, parameters, thresholds, and so on. In embodiments, the information that was updated can include an emotion metric 214 for one or more segments of the vehicle travel route. An emotion metric can be used to determine one or more emotions, an intensity of an emotion, a duration of an emotion, and so on. The emotions can include happiness, sadness, anger, boredom, and so on. In embodiments, the emotion metric can be based on the analysis of the images of the vehicle occupant] (Paragraph. 0056); and
However, Foaud did not disclose in detail wherein the one or more contextual parameter signals include a weight of the one or more passengers, providing the navigation route, the navigation guidance information, or a combination thereof as an output to execute the navigation route or the navigation guidance information.
In the same field of endeavor Liu disclosed, “The passenger characteristics 306 may include one or more characteristics of a passenger desiring to make a trip. The passenger characteristics 306 may include trip-specific information for the passenger, and/or characteristics of the passenger that are independent of the particular trip. As some examples, the passenger characteristics 306 include passenger dimensions 334 (e.g., height, width, etc.), passenger weight 336 (e.g., kilograms), passenger comfort requirements 338 (e.g., heating/cooling settings, massaging seat settings, etc.), heath information (e.g., whether the passenger is sick, prone to motion sickness, has special allergies such as pollen or tobacco, etc., requiring different routes or accommodations), disabilities information 342 (e.g., whether the passenger has impairments in movement or other characteristics that may affect travel), and luggage 344 (e.g., information regarding count, weight, and/or dimensions of luggage). FIG. 4 illustrates an example data flow diagram 400 for constructing a route 226. As shown, the multi-mode routing engine 216 may receive the vehicle characteristics 302, the trip characteristics 304, the passenger characteristics 306, weather data 402 from the weather service 220, traffic data 404 from the traffic service 222, map data 406 from the map server 224, and reservation data 408 from the passenger reservation system 218. Using the received information, the multi-mode routing engine 216 may compute a route 226 including an ordered set of one or more paths 206 that may be traversed by a user. (Paragraph. 0047-0048).
It would have been obvious to one having ordinary skill in the art before the effective filing date was made to have incorporated The passenger characteristics 306 may include one or more characteristics of a passenger desiring to make a trip. The passenger characteristics 306 may include trip-specific information for the passenger, and/or characteristics of the passenger that are independent of the particular trip. As some examples, the passenger characteristics 306 include passenger dimensions 334 (e.g., height, width, etc.), passenger weight 336 (e.g., kilograms), passenger comfort requirements 338 (e.g., heating/cooling settings, massaging seat settings, etc.), heath information (e.g., whether the passenger is sick, prone to motion sickness, has special allergies such as pollen or tobacco, etc., requiring different routes or accommodations), disabilities information 342 (e.g., whether the passenger has impairments in movement or other characteristics that may affect travel), and luggage 344 (e.g., information regarding count, weight, and/or dimensions of luggage). FIG. 4 illustrates an example data flow diagram 400 for constructing a route 226. As shown, the multi-mode routing engine 216 may receive the vehicle characteristics 302, the trip characteristics 304, the passenger characteristics 306, weather data 402 from the weather service 220, traffic data 404 from the traffic service 222, map data 406 from the map server 224, and reservation data 408 from the passenger reservation system 218. Using the received information, the multi-mode routing engine 216 may compute a route 226 including an ordered set of one or more paths 206 that may be traversed by a user as taught by Liu in the method and system of Fouad to optimize the routing plans based on user preferences.
2. As per claims 2,13,18 Fouad-Liu disclosed wherein the routing cost factor includes an efficiency factor, a resilience factor, a reliability factor, a simplicity of route factor, a safety factor, a point of interest discovery factor, or a combination thereof (Liu, Paragraph. 0045). Claims 2,13 and 18 have the same motivation as claim 1.
3. As per claim 3 Fouad-Liu disclosed wherein the efficiency factor
relates to a power or fuel consumption of the vehicle, a carbon footprint of the vehicle, or a combination thereof (Liu, Paragraph. 0045). Claim 3 has the same motivation as claim 1.
4. As per claim 4 Fouad-Liu disclosed wherein the resilience factor relates to an availability of one or more back-up routes in case of traffic congestion or an accident (Fouad, Paragraph. 0012).
5. As per claim 5 Fouad-Liu disclosed wherein the reliability factor relates to an ability to reach a destination via a selected route given a current power or fuel level of the vehicle (Liu, Paragraph. 0045). Claim 5 has the same motivation as claim 1.
6. As per claim 6 Fouad-Liu disclosed wherein the simplicity of route factor relates to a number of road type changes, complex maneuvers, routing decision points, or a combination thereof (Fouad, Paragraph. 0038).
7. As per claim 7 Fouad-Liu disclosed wherein the safety factor relates to a number of vulnerable road users expected to be encountered (Fouad, Paragraph. 0039).
8. As per claim 8 Fouad-Liu disclosed wherein the point of interest discovery factor relates to a number of points of interest expected to be encountered, and wherein the points of interest expected to be encountered relates to at least one designated interest of the one or more passengers (Fouad, Paragraph. 0096).
9. As per claims 9,14,19 Fouad-Liu disclosed wherein the one or more contextual parameter signals include a number of the one or more passengers, a weight of the one or more passengers, an age of the one or more passengers, a time of day, or a combination thereof (Liu, Paragraph. 0047). Claim 9, 14 and 19 has the same motivation as claim 1.
10. As per claims 10,15,20 Fouad-Liu disclosed further comprising: determining a previous destination, a previous context, or a combination associated with the one or more contextual parameter signals, wherein the routing cost factor is further based on the previous destination, the previous context, or a combination thereof (Fouad, Paragraph. 0015).
11. As per claims 11,16 Fouad-Liu disclosed wherein the navigation route, the navigation guidance information, or a combination thereof is determined further based on one or more multi-task stop options (Liu, Paragraph. 0048). Claims 11 and 16 have the same motivation as claim 1.
Claim Rejections - 35 USC § 101
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.
12. Claims 1-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
101 Analysis – Step 1
Claim 1 is directed to a method, claim 12 is directed to an apparatus and claim 17 is directed to one or more non-transitory computer-readable media. Therefore, claims 1, 12 and 17 are within at least one of the four statutory categories.
101 Analysis – Step 2A, Prong I
Regarding Prong I of the Step 2A analysis in the 2019 PEG, the claims are to be analyzed to determine whether they recite subject matter that falls within one of the follow groups of abstract ideas: a) mathematical concepts, b) certain methods of organizing human activity, and/or c) mental processes.
Independent claim 1 includes limitations that recite an abstract idea (emphasized below) and will be used as a representative claim for the remainder of the 101 rejection. The other analogous claims 12 and 17 are rejected for the same reasons as the representative claim 1 as discussed here. Claim 1 recites:
A method comprising:
collecting sensor data from one or more in-vehicle sensors of a vehicle; processing the sensor data to determine one or more contextual parameter signals associated with the vehicle, one or more passengers of the vehicle, or a combination thereof, wherein the one or more contextual parameter signals include a weight of the one or more passengers,
determining a context associated with a trip engaged by the vehicle or the one or more passengers based on the one or more contextual parameter signals;
determining a routing cost factor based on the context; determining by a routing engine configured to access a geographic database a navigation route a navigation route, navigation guidance information, or a combination thereof based on the routing cost factor; and providing the navigation route, the navigation guidance information, or a combination thereof as an output to execute the navigation route or the navigation guidance information.
The examiner submits that the foregoing bolded limitation(s) constitute a “Extra solution activity” because under its broadest reasonable interpretation, the independent claims steps that occur before or after the claim abstract idea-such as merely collecting input data, storing it, displaying a result or sending a notification but do not make the claim patent-eligible.
101 Analysis – Step 2A, Prong II
Regarding Prong II of the Step 2A analysis in the 2019 PEG, the claims are to be analyzed to determine whether the claim, as a whole, integrates the abstract into a practical application. As noted in the 2019 PEG, it must be determined whether any additional elements in the claim beyond the abstract idea integrate the exception into a practical application in a manner that imposes a meaningful limit on the judicial exception. The courts have indicated that additional elements merely using a computer to implement an abstract idea, adding insignificant extra solution activity, or generally linking use of a judicial exception to a particular technological environment or field of use do not integrate a judicial exception into a “practical application.”
In the present case, the additional limitations beyond the above-noted abstract idea are as follows (where the underlined portions are the “additional limitations” while the bolded portions continue to represent the “abstract idea”):
An apparatus comprising: at least one processor; and at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following, collect sensor data from one or more in-vehicle sensors of a vehicle; process the sensor data to determine one or more contextual parameter signals associated with the vehicle, one or more passengers of the vehicle, or a combination thereof; wherein the one or more contextual parameter signals include a weight of the one or more passengers,
determine a context associated with a trip engaged by the vehicle or the one or more passengers based on the one or more contextual parameter signals; determine a routing cost factor based on the context; determine by a routing engine configured to access a geographic database a navigation route a navigation route, navigation guidance information, or a combination thereof based on the routing cost factor; and provide the navigation route, the navigation guidance information, or a combination thereof as an output to execute the navigation route or the navigation guidance information.
For the following reason(s), the examiner submits that the above identified additional limitations do not integrate the above-noted abstract idea into a practical application.
Regarding the additional limitations above, the examiner submits that these limitations are insignificant extra-solution activities that merely use a computer (processor) to perform the process. In particular, the receiving and casting steps from / using sensor system(s) are recited at a high level of generality (i.e. as a general means of receiving information and casting rays to detect information for use in the determining and other steps), and amounts to mere data gathering, which is a form of insignificant extra-solution activity. The disqualifying, associating and sending steps are also recited at a high level of generality and amounts to mere post solution action, which is a form of insignificant extra-solution activity. Lastly, claims 12 and 17 further recite “An apparatus comprising: at least one processor; and at least one memory including computer program code for one or more programs” and “A non-transitory computer-readable medium carrying one or more sequences of one or more instructions which, when executed by one or more processors” merely describes how to generally “apply” the otherwise mental judgements in a generic or general purpose vehicle control environment. See Alice Corp. Pty. Ltd. v. CLS Bank Int'l, 573 U.S. at 223 (“[T]he mere recitation of a generic computer cannot transform a patent-ineligible abstract idea into a patent-eligible invention.”). The device(s) and processor(s) are recited at a high level of generality and merely automates the steps. In order to expedite prosecution, Examiner also notes that the mere recitation of “determining a context associated with a trip engaged by the vehicle or the one or more passengers based on the one or more contextual parameter signals; determining a routing cost factor based on the context; determining a navigation route, navigation guidance information” in claim 1 and “collect sensor data from one or more in-vehicle sensors of a vehicle” in claim 12 are not significant enough to integrate the judicial exception into a practical application since the claims do not include a positive recitation of “determining a navigation route, navigation guidance information, or a combination thereof based on the routing cost factor; and providing the navigation route, the navigation guidance information, or a combination thereof as an output” (if supported by the specification, such limitation is an example of a significant enough limitation to integrate the judicial exception into a practical application).
Thus, taken alone, the additional elements do not integrate the abstract idea into a practical application. Further, looking at the additional limitation(s) as an ordered combination or as a whole, the limitation(s) add nothing that is not already present when looking at the elements taken individually. For instance, there is no indication that the additional elements, when considered as a whole, reflect an improvement in the functioning of a computer or an improvement to another technology or technical field, apply or use the above-noted judicial exception to effect a particular treatment or prophylaxis for a disease or medical condition, implement/use the above-noted judicial exception with a particular machine or manufacture that is integral to the claim, effect a transformation or reduction of a particular article to a different state or thing, or apply or use the judicial exception in some other meaningful way beyond generally linking the use of the judicial exception to a particular technological environment, such that the claim as a whole is not more than a drafting effort designed to monopolize the exception (MPEP § 2106.05). Accordingly, the additional limitation(s) do/does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea.
101 Analysis – Step 2B
Regarding Step 2B of the 2019 PEG, representative independent claim 9 does not include additional elements (considered both individually and as an ordered combination) that are sufficient to amount to significantly more than the judicial exception for the same reasons to those discussed above with respect to determining that the claim does not integrate the abstract idea into a practical application. As discussed above with respect to integration of the abstract idea into a practical application, the additional element of using a processor to perform the steps amounts to nothing more than applying the exception using a generic computer component. Generally applying an exception using a generic computer component cannot provide an inventive concept. And as discussed above, the additional limitations discussed above are insignificant extra-solution activities.
The additional limitations of receiving information and values/features detecting/detectable are well-understood, routine and conventional activities because the background recites that the sensors are all conventional sensors, and the specification does not provide any indication that the processor is anything other than a conventional computer. MPEP 2106.05(d)(II), and the cases cited therein, including Intellectual Ventures I, LLC v. Symantec Corp., 838 F.3d 1307, 1321 (Fed. Cir. 2016), TLI Communications LLC v. AV Auto. LLC, 823 F.3d 607, 610 (Fed. Cir. 2016), and OIP Techs., Inc., v. Amazon.com, Inc., 788 F.3d 1359, 1363 (Fed. Cir. 2015), indicate that mere collection or receipt of data over a network is a well‐understood, routine, and conventional function when it is claimed in a merely generic manner. The additional limitation of “creating the first map …,” is a well-understood, routine, and conventional activity because the Federal Circuit in Trading Techs. Int’l v. IBG LLC, 921 F.3d 1084, 1093 (Fed. Cir. 2019), and Intellectual Ventures I LLC v. Erie Indemnity Co., 850 F.3d 1315, 1331 (Fed. Cir. 2017), for example, indicated that the mere performance which in the instant application is creating a map is a well understood, routine, and conventional function. Hence, the claim is not patent eligible.
Dependent claim(s) 2-11, 13-16 and 18-20 do not recite any further limitations that cause the claim(s) to be patent eligible. Rather, the limitations of dependent claims are directed toward additional aspects of the judicial exception and/or additional elements that do not integrate the judicial exception into a practical application. Therefore, dependent claims 2-11, 13-16 and 18-20 are not patent eligible under the same rationale as provided for in the rejection of claims 1,12 and 17.
Therefore, claims 1-20 are ineligible under 35 USC §101.
Response to Arguments
13. Applicants’ arguments with respect to claim(s) 1-20 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
Conclusion
14. Any inquiry concerning this communication or earlier communication from the
examiner should be directed to Adnan Mirza whose telephone number is (571)-272-3885.
15. The examiner can normally be reached on Monday to Friday during normal
business hours. If attempts to reach the examiner by telephone are unsuccessful, the
examiner’s supervisor, Faris Almatrahi can be reached on (313)-446-4821.
16. 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 http://pair-direct.uspto.gov. Should you
have questions on access to the Private PAIR system, contact the Electronic Business
Center (EBC) at (866)-217-9197 (toll-free).
/ADNAN M MIRZA/Primary Examiner, Art Unit 3667
