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 .
DETAILED ACTION
This final Office action is in response to applicant’s communication received on May 13, 2026, wherein claims 1-6 are currently pending.
Specification
In the response filed May 13, 2026, Applicant has changed the title from “Method” to “Method For Creating An Operation Schedule For An Extra Service.” (See Applicant’s “Amendment to the Specification” dated May 13, 2026).
Response to Arguments
Applicant's arguments have been fully considered but they are geared towards the newly amended claims and the newly added limitations. The newly amended claims with the newly added limitations are considered for the first time in the rejection below.
35 USC §101 discussion:
Applicant’s claimed concept is geared towards using obtained abstract information (where the information itself is abstract in nature – e.g. GTFS file information is all abstract information (public transportation schedules and associated geographic information), service information, extra service information, vehicle information, etc.,) to determine route information (with possible modifications). The abstract information is then displayed on generic/general purpose interface/display. As stated before, the claims recite acquiring/collecting information/data (where the information itself is abstract in nature – e.g. General Transit Feed Specification (GTFS) file data (which is known in the industry to contain public transportation schedules, geographic information, queues, constraints, costs, rules, performance, states, and the like – all abstract information), data analysis/manipulation (comparing information, solving for new/extra scenarios (transit/transportation services), arranging information (for scheduling), etc.,) to determine more data/information, possibly obtaining more abstract information/data, and providing this determined data/information for further analysis and decision-making (on creating new schedules). The claims clearly cover methods of organizing human activity (fundamental economic principles or practices (transit/transportation services and logistical management); and also managing personal relationships (creating schedules)).
The additional elements recited in the claims are generic/general-purpose computing/technology components/elements/terms (“file, display (abstract information) on interface/screen, management system,” (in independent claim 1); “management system,” “interface,” “processor,” (in claim 1’s dependent claims 2-6)); and in the context of the claims, the claims encompasses the above stated abstract idea (organizing human activity (fundamental economic principles or practices (transit/transportation services and logistical management); and also managing personal relationships (creating schedules))) – where this judicial exception is not integrated into a practical application. The CAFC has stated that it is not enough, however, to merely improve abstract processes by invoking a computer merely as a tool. Customedia Techs., LLC v. Dish Network Corp., 951 F.3d 1359, 1364 (Fed. Cir. 2020). The focus of the claims is simply to use computers and a familiar network as a tool to perform abstract processes (discussed above) involving simple information exchange. Carrying out abstract processes involving information exchange is an abstract idea. See, e.g., BSG, 899 F.3d at 1286; SAP America, 898 F.3d at 1167-68; Affinity Labs of Tex., LLC v. DIRECTV, LLC, 838 F.3d 1253, 1261-62 (Fed. Cir. 2016). And use of standard computers and networks to carry out those functions—more speedily, more efficiently, more reliably—does not make the claims any less directed to that abstract idea. See Alice Corp., 573 U.S. at 222-25; Customedia, 951 F.3d at 1364; Trading Techs. Int'l, Inc. v. IBG LLC, 921 F.3d 1084, 1092-93 (Fed. Cir. 2019); SAP America, 898 F.3d at 1167; Intellectual Ventures I LLC v. Symantec Corp., 838 F.3d 1307, 1314 (Fed. Cir. 2016); Electric Power Grp., LLC v. Alstom S.A., 830 F.3d 1350, 1353, 1355 (Fed. Cir. 2016); Intellectual Ventures I LLC v. Capital One Bank (USA), 792 F.3d 1363, 1367, 1370 (Fed. Cir. 2015); buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355 (Fed. Cir. 2014). Accordingly, the additional elements (“information processing apparatus,” “system,” (in independent claim 1)) do not integrate the abstract idea in to a practical application because it does not impose any meaningful limits on practicing the abstract idea – i.e. they are just post-solution/extra-solution activities.
The claims clearly do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the claims require no more than a generic computer to perform generic computer functions. The additional elements (“file, display (abstract information) on interface/screen, management system,” (in independent claim 1); “management system,” “interface,” “processor,” (in claim 1’s dependent claims 2-6)) or combination of elements in the dependent claims other than the abstract idea per se amounts to no more than: (i) mere instructions to implement the idea on a computer, and/or (ii) recitation of generic computer structure that serves to perform generic computer functions that are well-understood, routine, and conventional activities previously known to the pertinent industry. Applicant is directed to the following citations and references: Digitech Image., LLC v. Electronics for Imaging, Inc. (758 F.3d 1344 (2014) discussing U.S. Patent No. 6,128,415); and (2) Federal register/Vol. 79, No 241 issued on December 16, 2014, page 74629, column 2, Gottschalk v. Benson. Viewed as a whole, claims do not purport to improve the functioning of the computer itself, or to improve any other technology or technical field. Use of an unspecified, generic computer does not transform an abstract idea into a patent-eligible invention. Thus, the claims do not amount to significantly more than the abstract idea itself. See Alice Corp. v. CLS Bank Int'l, 110 USPQ2d 1976 (U.S. 2014).
Also see the rejection below
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-6 are rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter.
Note: The above discussion presented in the Response to Arguments section is fully incorporated in this rejection in addition to the rejection discussed below.
Regarding Step 1 (MPEP 2106.03) of the subject matter eligibility test per MPEP 2106.03, Claims 1-6 are directed to a method (i.e., process). Accordingly, all claims are directed to one of the four statutory categories of invention.
(Under Step 2) The claimed invention is directed to an abstract idea without significantly more.
(Under Step 2A, Prong 1 (MPEP 2106.04)) The independent claim (1) recites acquiring/collecting information/data (where the information itself is abstract in nature – e.g. General Transit Feed Specification (GTFS) file data (which is known in the industry to contain public transportation schedules, geographic information, queues, constraints, costs, rules, performance, states, and the like – all abstract information), data analysis/manipulation (comparing information, solving for new/extra scenarios (transit/transportation services), arranging information (for scheduling), etc.,) to determine more data/information, possibly obtaining more abstract information/data, and providing this determined data/information for further analysis and decision-making (on creating new schedules).
The limitations of the independent claim (1), under the broadest reasonable interpretation, covers methods of organizing human activity (fundamental economic principles or practices (transit/transportation services and logistical management); and also managing personal relationships (creating schedules)). If a claims limitation, under its broadest reasonable interpretation, covers the performance of the limitation as fundamental economic principles or practices (including hedging, insurance, mitigating risk); commercial or legal interactions (including agreements in the form of contracts; legal obligations; advertising, marketing or sales activities or behaviors; business relations); managing personal behavior or relationships or interactions between people (including scheduling, social activities, teaching, and following rules or instructions), then it falls within the “organizing human activities” grouping of abstract ideas. (MPEP 2106.04).
Accordingly, since Applicant's claims fall under organizing human activities grouping, the claims recite an abstract idea.
(Under Step 2A, prong 2 (MPEP 2106.04(d))) This judicial exception is not integrated into a practical application because but for the recitation of generic/general-purpose computing/technology components/elements/terms (“file, display (abstract information) on interface/screen, management system,” (in independent claim 1)), in the context of the independent claim (1), the claim encompass the above stated abstract idea (organizing human activity (fundamental economic principles or practices (transit/transportation services and logistical management); and also managing personal relationships (creating schedules))).
As shown above, the independent claim (1) recite generic/general-purpose computing/technology components/elements/terms/limitations (“file, display (abstract information) on interface/screen, management system,” (in independent claim 1)) which are recited at a high level of generality performing generic/general purpose computer/computing functions. (MPEP 2106.04). The generic/general-purpose computing/technology components/elements/terms/limitations are no more than mere instructions to apply the judicial exception (the above abstract idea – organizing human activity (fundamental economic principles or practices (transit/transportation services and logistical management); and also managing personal relationships (creating schedules))) in an apply-it fashion using generic/general-purpose computing/technology components/elements/terms/limitations (“file, display (abstract information) on interface/screen, management system,” (in independent claim 1)). The CAFC has stated that it is not enough, however, to merely improve abstract processes by invoking a computer merely as a tool. Customedia Techs., LLC v. Dish Network Corp., 951 F.3d 1359, 1364 (Fed. Cir. 2020). The focus of the claims is simply to use computers and a familiar network as a tool to perform abstract processes (discussed above) involving simple information exchange. Carrying out abstract processes involving information exchange is an abstract idea. See, e.g., BSG, 899 F.3d at 1286; SAP America, 898 F.3d at 1167-68; Affinity Labs of Tex., LLC v. DIRECTV, LLC, 838 F.3d 1253, 1261-62 (Fed. Cir. 2016). And use of standard computers and networks to carry out those functions—more speedily, more efficiently, more reliably—does not make the claims any less directed to that abstract idea. See Alice Corp., 573 U.S. at 222-25; Customedia, 951 F.3d at 1364; Trading Techs. Int'l, Inc. v. IBG LLC, 921 F.3d 1084, 1092-93 (Fed. Cir. 2019); SAP America, 898 F.3d at 1167; Intellectual Ventures I LLC v. Symantec Corp., 838 F.3d 1307, 1314 (Fed. Cir. 2016); Electric Power Grp., LLC v. Alstom S.A., 830 F.3d 1350, 1353, 1355 (Fed. Cir. 2016); Intellectual Ventures I LLC v. Capital One Bank (USA), 792 F.3d 1363, 1367, 1370 (Fed. Cir. 2015); buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355 (Fed. Cir. 2014). Accordingly, the additional elements (“file, display (abstract information) on interface/screen, management system,” (in independent claim 1)) do not integrate the abstract idea in to a practical application because it does not impose any meaningful limits on practicing the abstract idea – i.e. they are just post-solution/extra-solution activities.
(Under Step 2B (MPEP 2106.05)) The independent claim (1) do not include additional elements (“file, display (abstract information) on interface/screen, management system,” (in independent claim 1)) that are sufficient to amount to significantly more than the judicial exception because the claims do not recite an improvement to another technology or technical field, an improvement to the functioning of the computer itself, or meaningful limitations beyond generally linking the use of an abstract idea to a particular technological environment. The independent claims recite using generic/general-purpose computing/technology components/elements/terms/limitations (“file, display (abstract information) on interface/screen, management system,” (in independent claim 1)). For the role of a computer in a computer implemented invention to be deemed meaningful in the context of this analysis, it must involve more than performance of "well-understood, routine, [and] conventional activities previously known to the industry." Alice Corp. v. CLS Bank Int'l, 110 USPQ2d 1976 (U.S. 2014), at 2359 (quoting Mayo, 132 S. Ct. at 1294 (internal quotation marks and brackets omitted)). These activities as claimed by the Applicant are all well-known and routine tasks in the field of art – as can been seen in the specification of Applicant’s application (for example, see Applicant’s specification at, for example, figures 2-4 and paragraphs 0018-0027 [where Applicant recites general-purpose/generic computers/processors/etc., and generic/general-purpose computing components/devices/etc., in Applicant’s specification]) and/or the specification of the below cited art (used in the rejection below and on the PTO-892) and/or also as noted in the court cases in §2106.05 in the MPEP. Further, "the mere recitation of a generic computer cannot transform a patent ineligible abstract idea into a patent-eligible invention." Alice at 2358. None of the hardware offers a meaningful limitation beyond generally linking the system to a particular technological environment, that is, implementation via computers. Adding generic computer components to perform generic functions that are well‐understood, routine and conventional, such as gathering data, performing calculations, and outputting a result would not transform the claims into eligible subject matter. Abstract ideas are excluded from patent eligibility based on a concern that monopolization of the basic tools of scientific and technological work might impede innovation more than it would promote it. The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the claims require no more than a generic computer to perform generic computer functions. The additional elements (“file, display (abstract information) on interface/screen, management system,” (in independent claim 1)) or combination of elements in the claims other than the abstract idea per se amounts to no more than: (i) mere instructions to implement the idea on a computer, and/or (ii) recitation of generic computer structure that serves to perform generic computer functions that are well-understood, routine, and conventional activities previously known to the pertinent industry. Applicant is directed to the following citations and references: Digitech Image., LLC v. Electronics for Imaging, Inc. (758 F.3d 1344 (2014) discussing U.S. Patent No. 6,128,415); and (2) Federal register/Vol. 79, No 241 issued on December 16, 2014, page 74629, column 2, Gottschalk v. Benson. Viewed as a whole, the independent claims do not purport to improve the functioning of the computer itself, or to improve any other technology or technical field. Use of an unspecified, generic computer does not transform an abstract idea into a patent-eligible invention. Thus, the independent claim (1) does not amount to significantly more than the abstract idea itself. See Alice Corp. v. CLS Bank Int'l, 110 USPQ2d 1976 (U.S. 2014).
The dependent claims (2-6) further define the independent claims and merely narrow the described abstract idea, but not adding significantly more than the abstract idea. The dependent claims either individually or in combination are merely an extension of the abstract idea itself. The above rejection discussed for the independent claims fully applies to the dependent claims. In summary, the dependent claims (2-6) also cover methods of organizing human activity (fundamental economic principles or practices (transit/transportation services and logistical management); and also managing personal relationships (creating schedules)).
This judicial exception is not integrated into a practical application because the dependent claims and specification recite additional elements as generic/general-purpose computing/technology components/elements/terms/limitations (“management system,” “interface,” “processor,” (in claim 1’s dependent claims 2-6)) performing generic computer/computing/technology functions. (MPEP 2106.04). The dependent claims merely use the same general technological environment and instructions as the independent claims above to implement the abstract idea. The generic/general-purpose computing/technology components/elements/terms/limitations are no more than mere instructions to apply the judicial exception (organizing human activity (fundamental economic principles or practices (transit/transportation services and logistical management); and also managing personal relationships (creating schedules))) in an apply-it fashion using generic/general-purpose computing/technology components/elements/terms/limitations (“management system,” “interface,” “processor,” (in claim 1’s dependent claims 2-6)). Hence, the additional elements (“management system,” “interface,” “processor,” (in claim 1’s dependent claims 2-6)) do not integrate the abstract idea in to a practical application because they does not impose any meaningful limits on practicing the abstract idea – i.e. they are just post-solution/extra-solution activities.
Also, the dependent claims either individually or in combination are merely an extension of the abstract idea itself and the dependent claims (similar to the independent claims) do not include additional elements that are sufficient to amount to significantly more than the judicial exception because the claims require no more than a generic computer to perform generic computer functions. The additional elements (“management system,” “interface,” “processor,” (in claim 1’s dependent claims 2-6)) or combination of elements in the dependent claims other than the abstract idea per se amounts to no more than: (i) mere instructions to implement the idea on a computer, and/or (ii) recitation of generic computer structure that serves to perform generic computer functions that are well-understood, routine, and conventional activities previously known to the pertinent industry. Applicant is directed to the following citations and references: Digitech Image., LLC v. Electronics for Imaging, Inc. (758 F.3d 1344 (2014) discussing U.S. Patent No. 6,128,415); and (2) Federal register/Vol. 79, No 241 issued on December 16, 2014, page 74629, column 2, Gottschalk v. Benson. Viewed as a whole, dependent claims do not purport to improve the functioning of the computer itself, or to improve any other technology or technical field. Use of an unspecified, generic computer does not transform an abstract idea into a patent-eligible invention. Thus, the dependent claims do not amount to significantly more than the abstract idea itself. See Alice Corp. v. CLS Bank Int'l, 110 USPQ2d 1976 (U.S. 2014).
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.
Claims 1-6 are rejected under 35 U.S.C. 103 as being unpatentable over Gkiotsalitis et al., (US 2018/0032964) in view of Ramot et al., (US 2019/0311307).
As per claim 1, Gkiotsalitis discloses a method (Abstract [transit system]; ¶¶ 0002-0003 [transit services…plurality of vehicles (managed)], 0007-0010 [vehicles…transit system….transportation]), the method comprising:
acquiring information on an extra service based on a GTFS file containing information on the extra service to be additionally registered in an operation management system that manages operations of a plurality of vehicles or based on information on an operating service that has been registered in the operation management system, wherein the extra service is to be operated in addition to scheduled fixed route services ((note that the General Transit Feed Specification (GTFS) defines a common format for public transportation schedules and associated geographic information) ¶¶ 0002-0003 [transit services…plurality of vehicles (managed)], 0007-0010 [vehicles…transit system….transportation], 0006 [new frequency setting and allocation discussed in regards to transportations and, for example, demand and other factors/information – operationally reliable frequency setting solution is provided as the new frequency setting to a command center of the transit service], 0025 [automated bus dispatcher applies any new frequency setting allocations….automated bus dispatcher can be, for example, a dedicated server at a command center which; with 0056 [providing new frequencies to the operations command center and updating the time period slots and the allocated frequency values for each bus line; with 0064 [using General Transit Feed Specification (GTFS) data] and 0083]]], 0103 [new setting applied to online timetables, smartphone applications with access to such timetables and electronic displays, for example, at transit stops]; see also claim 1 of Gkiotsalitis);
displaying the acquired information on the extra service on a screen: in response to user assignment of a vehicle to the information on the extra service displayed on the screen, adding information on the vehicle assigned to the extra service to the information on the extra service (¶¶ 0025 [automated bus dispatcher can be, for example, a dedicated server at a command center which, upon receiving new frequency setting allocations, can apply the new frequency settings to new or existing electronic timetables stored in memory or on the web, alert drivers or buses of frequency changes and providing instructions and new or adapted routes as applicable, update electronic displays; with 0033 [dynamically display updated travel frequencies and/or connections]; 0046 [data can be utilized, for example by a command center including one or more computational processors and/or servers, to dynamically allocate the frequencies and update the relevant displays]; with claim 15 of Gkiotsalitis [automated bus dispatcher configured to electronically communicate an alert to a bus on a bus line of the transit service (i.e. from plurality of buses) to which the new frequency setting applies indicating new instructions or a new route to be followed by the bus based on the new frequency setting]]);
creating an operation schedule for the extra service based on the information on the extra service (¶¶ 0006 [timetable of the transit service is updated to include the new frequency setting], 0025 [upon receiving new frequency setting allocations, can apply the new frequency settings to new or existing electronic timetables], 0103 [new setting…applied to…timetables…electronic displays of timetables which are controlled by the methods/command center, and are thereby dynamically updated]; see also claim 1 of Gkiotsalitis); and
displaying information on the operation schedule on the screen (see citations above and see ¶¶ 0011 [electronic displays showing content], 0015 [displaying information in a dynamic manner – e.g. allocations of buses], 0103 [online timetables, smartphone applications with access to such timetables and electronic displays… the command center being configured to implement the methods according to embodiments of the invention, and to electronic displays of timetables which are controlled by the methods/command center, and are thereby dynamically updated]).
Gkiotsalitis does not explicitly state wherein the extra service is a one-time service;
Analogous art Ramot discloses wherein the extra service is a one-time service (¶¶ 0036 [assign one…additional ride service assignments], 0149 [the service parameters…include one…ride requests added to the real-time ride requests]).
Therefore, it would be obvious to one of ordinary skill in the art to include in Gkiotsalitis wherein the extra service is a one-time service as taught by analogous art Ramot since one of ordinary skill in the art at the time of the invention would have recognized that applying the known technique and concepts of Ramot (making one time changes/event/scheduling or multiple changes in transportation is old and well-known technique) would have yielded predictable results because the level of ordinary skill in the art demonstrated by the references applied shows the ability to incorporate such concepts and features into similar systems (KSR-D); and also since the claimed invention is merely a combination of old elements, and in the combination each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable (KSR-A). (MPEP 2141).
As per claim 2, Gkiotsalitis discloses the method according to claim 1, further comprising selecting the vehicle to be assigned to the extra service from among the plurality of vehicles excluding each vehicle that has already been assigned to any of operating services registered in the operation management system, and creates the operation schedule for the extra service by assigning the selected vehicle to the extra service (see claim 15 of Gkiotsalitis [automated bus dispatcher configured to electronically communicate an alert to a bus on a bus line of the transit service (i.e. from plurality of buses) to which the new frequency setting applies indicating new instructions or a new route to be followed by the bus based on the new frequency setting; see with ¶ 0102 [availability of bus drivers]]; and also see ¶¶ 0022 [changes…adding additional buses; see with 0087 [available buses…bus lines…based on current fleet]], 0047).
As per claim 3, Gkiotsalitis discloses the method according to claim 1, further comprising providing an interface that allows modification of a transit point and a time to pass the transit point included in the created operation schedule (see citations above for claim 1 and in addition see ¶¶ 0006 [travel time…waiting time…at transfer stops (transit point) [is modified/reduced/etc.,]], 0025 [automated bus dispatcher applies any new frequency setting allocations…automated bus dispatcher …server at a command center which, upon receiving new frequency setting allocations, can apply the new frequency settings to new or existing electronic timetables stored in memory or on the web, alert drivers or buses of frequency changes and providing instructions and new or adapted routes as applicable, update electronic displays at the bus or transit stops…decreased waiting times (at transit points/stops/etc.,); see with 0056]).
As per claim 4, Gkiotsalitis discloses the method according to claim 1, further comprising outputting information on the created operation schedule to a GTFS file ((note that the General Transit Feed Specification (GTFS) defines a common format for public transportation schedules and associated geographic information) ¶¶ 0064-0065 [discusses GTFS files and data; see with 0083 and 0103 [changes and modifications applied to system and devices and displayed – also timetables updated], 0033 [receive update instructions from a central computer system implementing the method in order to dynamically display updated and the system updated]]).
As per claim 5, Gkiotsalitis discloses the method according to claim 1, further comprising changing a service ID included in the information on the operating service that has been registered and acquires the information on the extra service (see citations above for claims 1-2 and also see ¶¶ 0083-0084 [specific bus lines (service ID) and selecting specific bus lines (service ID) and then discussing changes based on new information/frequencies/demands in 0089, 0091, 0099-0103 [bus line (specific service ID)…parameters changed…new frequency/etc., (extra services)…new settings applied]; see with 0100 [during bus operations and/or for identifying the weight factor values range that does not affect each proposed frequency setting solution, thereby allowing the service operator to select solutions…for each line (where each bus line is identified by its route/travel)]]).
As per claim 6, Gkiotsalitis discloses an apparatus comprising a processor, for improving travel mobility as a service (MaaS), configured to execute the method of claim 1 (claim is directed to intended (“improving travel mobility”) use and refers to the limitations of claim and is therefore rejected under the same rationale and citations presented for claim 1 above (see citations in claim 1); in addition see ¶¶ 0023-0025 [“provides improvements in transportation…improving bus operations…improvements in transit system”]).
Conclusion
The prior art made of record on the PTO-892 and not relied upon is considered pertinent to applicant's disclosure. For example, some of the pertinent art is as follows:
Taub et al., (US 2024/0320582): Discusses planning a public transit system including determining costs of providing a fixed-route service are provided. The systems and method can receive a set of fixed route lines and trips for the public transit system and a plurality of ride requests. The systems and method can include determining a plurality of possible proposals for each ride request of the plurality of ride requests based on the received set of fixed route lines and trips and/or one or more constraints, determine for each ride request a set of proposals of the plurality of proposals having the lowest overall cost to provide the fixed-route service and determine whether one or more of a subset of the fixed route lines or trips are to be removed from the received set of fixed route lines and trips.
Beaurepaire et al., (US 2020/0167702): Provides for managing a vehicle reservation used in an intermodal route. A routing platform determines that the intermodal route includes a segment to be traveled using a vehicle booked via the vehicle reservation, and another segment that is traveled using a different mode of transport for a user to reach the vehicle to travel the segment. The routing platform monitors an expiration period of the vehicle reservation and a user location of the user on the another segment. The routing platform calculates a probability that the user will reach the vehicle to travel the segment before an end of the expiration period based on the user location. The routing platform generates at least one route option based on the probability, wherein the at least one route option includes an extension the vehicle reservation, and/or a creation of another vehicle reservation for another vehicle.
Petralia et al., (US 2010/0280853): Provides a transportation route to a user. Travel information from the user, a plurality of transportation route goals ranked in a specified order by the user, and attribute information of a plurality of transit modes from a transit information system are received by the central system. An optimized transportation route is determined for the user through a correlation of the plurality of ranked transportation route goals and attribute information that corresponds to the received travel information. The transportation route comprises one or more of the plurality of transit modes. The optimized transportation route is transmitted to the user.
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.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to GURKANWALJIT SINGH whose telephone number is (571)270-5392. The examiner can normally be reached on M-F 8:30-5: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, Brian Epstein can be reached on 571-270-5389. 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.
/Gurkanwaljit Singh/
Primary Examiner, Art Unit 3625
Prosecution Insights