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 § 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.
Claim(s) 1-20 are rejected under 35 U.S.C. 103 as being unpatentable over Lubeck et al (U.S. 2009/0176508) and further in view of KO et al (U.S. 2020/0005240).
1. As per claims 1,17,18 Lubeck disclosed an information processing device comprising:
a receiver configured to acquire a transportation request requesting transportation of an object to be transported by a vehicle [the requester simply makes a request to be transported (or requests an item to be transported) using a smart MD equipped with software effective for accomplishing this request.] (Paragraph. 0020), including type data indicating whether the object to be transported is a passenger or a cargo [The request may contain additional information such as the destination location of the transportation request, the method of payment, and specific characteristics of what is to be transported. Characteristics may also include the number of individuals to be transported, the size and weight of packages to be delivered, a future time for the service to be performed and/or the type of material to be transported.] (Paragraph. 0029),
a controller configured to:
determine whether the object to be transported is the passenger or the cargo based on the type data [the requester receives responses to this message type containing information including location of transporters, the identity of the transporter acknowledged to service request, service fare, and credit card authorization status] (Paragraph. 0042).
calculate one or more driving route candidates [analyzing the geographic location information at the selected time intervals using the computer; comparing the analyzed location information with the scheduled location of the at least one vehicle along the predetermined route; and calculating the time-of-arrival of the at least one vehicle at the chosen location.] (Paragraph. 0012), and
extract a driving route from among the driving route candidates [Computer 104 analyzes the time-varying geographic location data, matches the locations with bus schedules, and computes times-of-arrival and other route information. This information may be transmitted to traveler 408 where it is displayed on his or her cell phone in real time] (Paragraph. 0045).
a transmitter configured to output the extracted driving route,
wherein the vehicle is caused to proceed along the extracted driving route in response to the transmitter outputting the extracted driving route transportation related to the passenger transportation request is completed, based on the driving route candidate [In another aspect of the present invention, and in accordance with its objects and purposes, the method for obtaining time-of-arrival information for at least one transportation vehicle following a predetermined route at a chosen location on the route, hereof, includes: providing a wireless communications network for routing messages; providing a computer for processing information in cooperation with the wireless communications network; sending the geographic location of the chosen location on the route using a first communications device] (Paragraph. 0012).
However Lubeck did not disclose in detail, “based on a travel time until end of transportation of the passenger who is the object to be transported in a case of determining that the object to be transported is the passenger, and based on a movement cost of the vehicle in a case of determining that the object to be transported is the cargo, wherein the controller is configured to dynamically update, in real time, between time-based criteria for passenger transportation and cost-based criteria for cargo transportation.
In the same field of endeavor KO disclosed, “The vehicle route planning unit 133 specifies a delivery route and a cost relating to deliveries for each combination of a candidate for a relay place between the areas and a relay time in the candidate for the relay place and specifies the delivery route as a vehicle route using the cost as an index (for example, a low cost). At this time, when each of the delivery vehicles arrives at the candidate for the relay place, the vehicle route planning unit 133 gives priority to the delivery route in which the number of cargos of in-area deliveries in which a delivery place is in a previous area is small. On the other hand, when each of the delivery vehicles does not include a cargo of an in-area delivery when arriving at the candidate for the relay place, the vehicle route planning unit 133 specifies the delivery route such that the driver who drives the delivery vehicle transfers to another delivery vehicle that arrives at the candidate for the relay place from another area and continues the delivery in the same area (Paragraph. 006).
It would have been obvious to one having ordinary skill in the art before the effective filing date was made to have incorporated the vehicle route planning unit 133 specifies a delivery route and a cost relating to deliveries for each combination of a candidate for a relay place between the areas and a relay time in the candidate for the relay place and specifies the delivery route as a vehicle route using the cost as an index (for example, a low cost). At this time, when each of the delivery vehicles arrives at the candidate for the relay place, the vehicle route planning unit 133 gives priority to the delivery route in which the number of cargos of in-area deliveries in which a delivery place is in a previous area is small. On the other hand, when each of the delivery vehicles does not include a cargo of an in-area delivery when arriving at the candidate for the relay place, the vehicle route planning unit 133 specifies the delivery route such that the driver who drives the delivery vehicle transfers to another delivery vehicle that arrives at the candidate for the relay place from another area and continues the delivery in the same area as taught by KO in the method and system of Lubeck to increase efficiency of routing of the vehicle based on the passengers or cargo movements.
2. As per claim 2 Lubeck -KO disclosed wherein the controller
3. As per claims 3,20 Lubeck -KO disclosed wherein the controller is configured to preferentially extract a driving route candidate with a lower movement cost as the driving route, than a driving route candidate with a higher movement cost from the driving route candidate, in a case of determining that the object to be transported is the cargo (KO, Paragraph. 0041). Claim 3 has the same motivation as to claim 1.
4. As per claim 4 Lubeck-KO disclosed wherein the controller
5. As per claim 5 Lubeck-KO disclosed wherein the controller is configured calculate, as the travel time for each driving route candidate, a value obtained by summing a calculated time over the passenger transportation request, wherein the calculated time is calculated based on the driving route candidate and is a time from a timing when the passenger transportation request is confirmed or a timing when the passenger transportation request is acquired to a scheduled timing when transportation related to the passenger transportation request is completed(Lubeck, Paragraph. 0012).
6. As per claim 6 Lubeck -KO disclosed wherein the controller is configured to calculate, as the movement cost for each driving route candidate, a scheduled driving distance or a scheduled driving time during the vehicle travels along the driving route candidate, based on the driving route candidate (Lubeck, Paragraph. 0045).
7. As per claim 7 Lubeck-KO disclosed wherein the controller is configured to calculate, as the movement cost for each driving route candidate, a value obtained by summing a scheduled driving distance or a scheduled driving time of the vehicle over entire vehicles, which are calculated based on the driving route candidate (Lubeck, Paragraph. 0029).
8. As per claim 8 Lubeck-KO disclosed wherein the controller
9. As per claim 9 Lubeck-KO disclosed wherein the transportation request includes a desired end timing at which a user desires to end transportation of the object to be transported, the controller is configured to extract the driving route from the driving route candidate for which a difference between a scheduled timing when the vehicle arrives at an end point candidate for ending transportation of the object to be transported and the desired end timing is equal to or less than a predetermined threshold (Lubeck, Paragraph. 0036-0037).
10. As per claim 10 Lubeck-KO disclosed wherein the transportation request includes a desired start timing at which a user desires to start transportation of the object to be transported, the controller is configured to extract the driving route from the driving route candidate for which a difference between a scheduled timing when the vehicle arrives at a start point candidate for starting transportation of the object to be transported and the desired start timing is equal to or less than a predetermined threshold (Lubeck, Paragraph. 0036-0037).
11. As per claim 11 Lubeck-KO disclosed wherein the predetermined threshold when the object to be transported is the cargo is set larger than the predetermined threshold when the object to be transported is the passenger (KO, Paragraph. 0039). Claim 11 has the same motivation as to claim 1.
12. As per claim 12 Lubeck-KO disclosed wherein the type data includes at least one of: information identifying an information terminal that sent the transportation request, information identifying an application that generated the transportation request, and information identifying a user operation related to the transportation request (Lubeck, Paragraph. 0011).
13. As per claim 13 Lubeck-KO disclosed further comprising; a database that associates and stores the vehicle and the extracted driving route, wherein the controller is configured to update the driving route stored in the database
14. As per claim 14 Lubeck-KO disclosed wherein after the controller determines that the object to be transported is the passenger, the controller: calculates the driving route candidate, extracts the driving route candidate in which a maximum number of passengers of the vehicle when the vehicle travels on the driving route candidate is equal to or less than a predetermined number of passengers, based on the transportation request, and extracts the driving route from the extracted driving route candidate based on the travel time (Lubeck, Paragraph. 0029).
15. As per claim 15 Lubeck-KO disclosed wherein after the controller determines that the object to be transported is the cargo, the controller:candidate, extracts the driving route candidate in which a maximum load of the vehicle when the vehicle travels on the driving route candidate is equal to or less than a predetermined amount, based on the transportation request, and extracts the driving route from the extracted driving route candidate based on the movement cost (Lubeck, Paragraph. 0012 and 0029).
16. As per claims 16,19 Lubeck-KO disclosed, wherein after the controller calculates the driving route candidate, the controller determines whether the object to be transported is the passenger or the cargo, in a case that the controller determines that the object to be transported is the passenger (Lubeck, Paragraph. 0029), the controller: extracts the driving route candidate in which a maximum number of passengers of the vehicle when the vehicle travels on the driving route candidate is equal to or less than a predetermined number of passengers, based on the transportation request (Lubeck, Paragraph. 0012), and extracts the driving route from the extracted driving route candidate based on the travel time, in a case that the controller determines that the object to be transported is the cargo, the controller: extracts the driving route candidate in which a maximum load of the vehicle when the vehicle travels on the driving route candidate is equal to or less than a predetermined amount, based on the transportation request, and extracts the driving route from the extracted driving route candidate based on the movement cost (Lubeck, Paragraph. 0045).
Response to Arguments
17. Applicant’s 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
18. THIS ACTION IS MADE FINAL. 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.
19. Any inquiry concerning this communication or earlier communication from the
examiner should be directed to Adnan Mirza whose telephone number is (571)-272-3885.
20. 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.
21. 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 un published 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