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 .
Novel/Non-Obvious Subject Matter
Examiner has determined that all of Applicant’s claims have overcome having prior art rejections. The reason for this is that Examiner does not believe that, at the time of Applicant’s priority date, it would have been obvious for a person of ordinary skill in the art to combine prior art disclosures to result in the particular combinations of elements/limitations in the claims, including the particular configurations of the elements/limitations with respect to each other in the particular combinations, without the use of impermissible hindsight.
Specifically, each of Applicant’s independent claims contains language which incorporates the flight attributes in the specification’s appendix. There are a significant number of such attributes listed there, such that it would be not be obvious to combine that large number of particular attributes into the claims without the use of impermissible hindsight. See the indefiniteness rejections in this Office action for further details.
See the Conclusion section of this Office action for relevant prior art references found in the prior art search.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1-20 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
First, several of the claims, including all three independent claims contain references to the flight attribute appendix of Applicant’s specification. There are a significant number of such flight attributes listed there. While incorporating all of those specific attributes into the independent claims (and the rest of the claims, at least via dependency) has helped the claims overcome having prior art rejections, the claims have also been significantly narrowed in a way that it is not clear that Applicant intended. Therefore, all of the claims are indefinite for at least this reason. Please clarify Applicant’s intention in the next Office action, such as by replacing the references to the appendix with direct recitation in the claims of any particular attributes that Applicant wishes to be given patentable weight.
Second, claim 17 is directed to a system, but the preamble and body of the claim then proceed to recite a method. This renders claim 17 and its dependent claims to be indefinite.
Third, the sixth line of claim 14 and the sixth line of claim 17 use the words “such as” to introduce examples of metadata of a user. It is unclear if the examples are meant to be required parts of the claim, or if they are only meant to express possibilities of what such metadata could be. This renders claims 14 and 17, and their dependent claims, to be indefinite for that reason.
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.
Claim(s) 1-13 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
As per Claim(s) 1, Claim(s) 1 recite(s):
- plan and book flights utilizing intelligence from unstructured user input with a language model;
- receiving an input flight travel query reflecting a user intention;
- wherein an intelligence model has been trained based on user data of a user's flight preferences, flight schedules and many variables relating to flights;
- wherein intelligence to understand the user intent is to find the best semantic matches to the user input, external context, flight attributes as specified in appendix FLIGHT ATTRIBUTES and the available inventory;
- analyzing the input flight travel query using the trained intelligence model;
- generating possible flights in terms of dates, airports, nonstop or not, fastest time and number of stops based on the input flight travel query, external context, flight attributes as specified in the appendix FLIGHTS ATTRIBUTES and the user's flight preferences.
Each of the above limitations falls within the abstract-idea category of “Certain methods of organizing human activity.” Specifically, those limitations relate to the following subject matter that is grouped into the category of “Certain methods of organizing human activity”:
- commercial or legal interactions (including agreements in the form of contracts; legal obligations; advertising, marketing or sales activities or behaviors; business relations): helps book a flight which is commonly a commercial interaction;
- managing personal behavior or relationships or interactions between people (including social activities, teaching, and following rules or instructions): manages what flight a user might take; also manages interactions between a consumer and an airline, each such side possibly involving humans.
To the extent that any of these limitations are recited alongside recitations of generic computer components, as described below in this rejection: If a claim limitation, under its broadest reasonable interpretation, covers subject matter recognized as certain methods of organizing human activity but for the recitation of generic computer components, then it falls within the “Certain method of organizing human activity” grouping of abstract ideas. Accordingly, the claim(s) recite an abstract idea.
This judicial exception is not integrated into a practical application because the additional elements when considered both individually and as an ordered combination do not integrate the abstract idea into a practical application. The claim(s) recite the following additional elements/limitations, each of which are addressed in the list below with the reason(s) why they do not integrate the abstract idea into a practical application:
- computer-implemented; artificial intelligence; a computer system: These element(s)/limitation(s) amount to mere instructions to apply an exception. See MPEP 2106.05(f). In making this determination, examiners may consider whether the claim invokes computers or other machinery merely as a tool to perform an existing process. Mere instructions to apply an exception is a consideration with respect to both integration of an abstract idea into a practical application and significantly more. MPEP 2106.05(f)(2) states: “Use of a computer or other machinery in its ordinary capacity for economic or other tasks (e.g., to receive, store, or transmit data) or simply adding a general purpose computer or computer components after the fact to an abstract idea (e.g., a fundamental economic practice or mathematical equation) does not provide significantly more. See Affinity Labs v. DirecTV, 838 F.3d 1253, 1262, 120 USPQ2d 1201, 1207 (Fed. Cir. 2016) (cellular telephone); TLI Communications LLC v. AV Auto, LLC, 823 F.3d 607, 613, 118 USPQ2d 1744, 1748 (Fed. Cir. 2016) (computer server and telephone unit).” This is the case with these particular claim element(s)/limitation(s). Those elements/limitations do not meaningfully limit the claim because implementing an abstract idea on a generic computer does not integrate the abstract idea into a practical application, similar to how the recitation of the computer in the claim in Alice amounted to mere instructions to apply the abstract idea of intermediated settlement on a generic computer. Therefore, these particular claim element(s)/limitation(s) do not integrate the abstract idea into a practical application for at least this reason.
Thus, taken alone, the additional elements do not integrate the abstract idea into a practical application. Looking at the limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually. There is no indication that the combination of elements improves the functioning of a computer or improves any other technology.
Accordingly, the additional elements do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea. The claim(s) are directed to an abstract idea.
The claim(s) do not include additional elements that are sufficient to amount to significantly more than the judicial exception, either individually or as an ordered combination. As discussed above with respect to integration of the abstract idea into a practical application, the additional elements of computer-related components amount to no more than mere instructions to apply the exception using generic computer components. Mere instructions to apply an exception using generic computer components cannot provide an inventive concept.
The claim(s) are not patent eligible.
As per dependent claim(s) 2-13, these claim(s) incorporate the above abstract idea via their dependencies on the respective independent claim(s). The additional element(s)/limitation(s) of the respective independent claim(s) do not integrate the abstract idea into a practical application, nor do they add significantly more, with respect to those dependent claim(s), under the same reasoning as above with respect to the respective independent claim(s).
Those dependent claim(s) add the following generic computer components, which do not integrate the abstract idea into a practical application, nor add significantly more, under the same reasoning as given above with respect to generic computer components in the independent claim(s). Those additional generic computer components and their corresponding dependent claim(s) are as follows:
- machine learning (claims 2, 8, and 10).
The remaining added elements/limitations of those dependent claim(s) do not integrate the abstract idea into a practical application nor add significantly more because they all merely add further functional step(s) and/or detail to the abstract idea; as part of the abstract idea, they cannot integrate into a practical application or be significantly more than the abstract idea of which they are a part. For example, claim 11 merely adds detail regarding the training data.
Thus, taken alone, the additional elements do not integrate the abstract idea into a practical application, nor add significantly more. Looking at the limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually. There is no indication that the combination of elements improves the functioning of a computer or improves any other technology.
Claim(s) 1-13 are therefore not drawn to eligible subject matter as they are directed to an abstract idea that is not integrated into a practical application and is without significantly more.
Claim(s) 14-16 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
As per Claim(s) 14, Claim(s) 14 recite(s):
- plan and book flights utilizing intelligence from unstructured user input with a large language model (LLM);
- receiving an input flight travel query reflecting a user intention;
- wherein a learning model has been trained based on user data of a user's flight preferences, as well as flight preferences based on metadata of that user, such as location of the user, time of the flight travel query, income level, flight destination and flight departure location, flight schedules and many variables relating to flights;
- analyzing the input flight travel query using the trained learning model;
- generating possible flights in terms of dates, airports, nonstop or not, fastest time and number of stops based on the input flight travel query, external context, and additional structured and unstructured flight attributes as specified in appendix FLIGHT ATTRIBUTES, and the user's flight preferences;
- wherein the learning model utilizes a natural language understanding and probabilistic model;
- wherein training data is from all available flights from an origin city of the flight travel query to the destination city of the flight travel query, and from all available searches of flights conducted by the user.
Each of the above limitations falls within the abstract-idea category of “Certain methods of organizing human activity.” Specifically, those limitations relate to the following subject matter that is grouped into the category of “Certain methods of organizing human activity”:
- commercial or legal interactions (including agreements in the form of contracts; legal obligations; advertising, marketing or sales activities or behaviors; business relations): helps book a flight which is commonly a commercial interaction;
- managing personal behavior or relationships or interactions between people (including social activities, teaching, and following rules or instructions): manages what flight a user might take; also manages interactions between a consumer and an airline, each such side possibly involving humans.
To the extent that any of these limitations are recited alongside recitations of generic computer components, as described below in this rejection: If a claim limitation, under its broadest reasonable interpretation, covers subject matter recognized as certain methods of organizing human activity but for the recitation of generic computer components, then it falls within the “Certain method of organizing human activity” grouping of abstract ideas. Accordingly, the claim(s) recite an abstract idea.
This judicial exception is not integrated into a practical application because the additional elements when considered both individually and as an ordered combination do not integrate the abstract idea into a practical application. The claim(s) recite the following additional elements/limitations, each of which are addressed in the list below with the reason(s) why they do not integrate the abstract idea into a practical application:
- computer-implemented; artificial intelligence; a computer system; machine learning: These element(s)/limitation(s) amount to mere instructions to apply an exception. See MPEP 2106.05(f). In making this determination, examiners may consider whether the claim invokes computers or other machinery merely as a tool to perform an existing process. Mere instructions to apply an exception is a consideration with respect to both integration of an abstract idea into a practical application and significantly more. MPEP 2106.05(f)(2) states: “Use of a computer or other machinery in its ordinary capacity for economic or other tasks (e.g., to receive, store, or transmit data) or simply adding a general purpose computer or computer components after the fact to an abstract idea (e.g., a fundamental economic practice or mathematical equation) does not provide significantly more. See Affinity Labs v. DirecTV, 838 F.3d 1253, 1262, 120 USPQ2d 1201, 1207 (Fed. Cir. 2016) (cellular telephone); TLI Communications LLC v. AV Auto, LLC, 823 F.3d 607, 613, 118 USPQ2d 1744, 1748 (Fed. Cir. 2016) (computer server and telephone unit).” This is the case with these particular claim element(s)/limitation(s). Those elements/limitations do not meaningfully limit the claim because implementing an abstract idea on a generic computer does not integrate the abstract idea into a practical application, similar to how the recitation of the computer in the claim in Alice amounted to mere instructions to apply the abstract idea of intermediated settlement on a generic computer. Therefore, these particular claim element(s)/limitation(s) do not integrate the abstract idea into a practical application for at least this reason.
Thus, taken alone, the additional elements do not integrate the abstract idea into a practical application. Looking at the limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually. There is no indication that the combination of elements improves the functioning of a computer or improves any other technology.
Accordingly, the additional elements do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea. The claim(s) are directed to an abstract idea.
The claim(s) do not include additional elements that are sufficient to amount to significantly more than the judicial exception, either individually or as an ordered combination. As discussed above with respect to integration of the abstract idea into a practical application, the additional elements of computer-related components amount to no more than mere instructions to apply the exception using generic computer components. Mere instructions to apply an exception using generic computer components cannot provide an inventive concept.
The claim(s) are not patent eligible.
As per dependent claim(s) 15-16, these claim(s) incorporate the above abstract idea via their dependencies on the respective independent claim(s). The additional element(s)/limitation(s) of the respective independent claim(s) do not integrate the abstract idea into a practical application, nor do they add significantly more, with respect to those dependent claim(s), under the same reasoning as above with respect to the respective independent claim(s).
The added elements/limitations of those dependent claim(s) do not integrate the abstract idea into a practical application nor add significantly more because they all merely add further functional step(s) and/or detail to the abstract idea; as part of the abstract idea, they cannot integrate into a practical application or be significantly more than the abstract idea of which they are a part. For example, claim 15 merely adds detail to flight parameters.
Claim(s) 14-16 are therefore not drawn to eligible subject matter as they are directed to an abstract idea that is not integrated into a practical application and is without significantly more.
Claim(s) 17-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
As per Claim(s) 17, Claim(s) 17 recite(s):
- plan and book flights utilizing intelligence from unstructured user input with a small language model (“SLM”);
- receiving an input flight travel query reflecting a user intention;
- wherein a learning model has been trained based on user data of a user's flight preferences, as well as flight preferences based on metadata of that user, such as location of the user, time of the flight travel query, income level, flight destination and flight departure location, flight schedules and many variables relating to flights;
- analyzing the input flight travel query using the trained learning model;
- generating possible flights in terms of dates, airports, nonstop or not, fastest time and number of stops based on the input flight travel query, external context, and additional structured and unstructured flight attributes as specified in appendix FLIGHT ATTRIBUTES, and the user's flight preferences;
- wherein the learning model utilizes a natural language understanding and probabilistic model.
Each of the above limitations falls within the abstract-idea category of “Certain methods of organizing human activity.” Specifically, those limitations relate to the following subject matter that is grouped into the category of “Certain methods of organizing human activity”:
- commercial or legal interactions (including agreements in the form of contracts; legal obligations; advertising, marketing or sales activities or behaviors; business relations): helps book a flight which is commonly a commercial interaction;
- managing personal behavior or relationships or interactions between people (including social activities, teaching, and following rules or instructions): manages what flight a user might take; also manages interactions between a consumer and an airline, each such side possibly involving humans.
To the extent that any of these limitations are recited alongside recitations of generic computer components, as described below in this rejection: If a claim limitation, under its broadest reasonable interpretation, covers subject matter recognized as certain methods of organizing human activity but for the recitation of generic computer components, then it falls within the “Certain method of organizing human activity” grouping of abstract ideas. Accordingly, the claim(s) recite an abstract idea.
This judicial exception is not integrated into a practical application because the additional elements when considered both individually and as an ordered combination do not integrate the abstract idea into a practical application. The claim(s) recite the following additional elements/limitations, each of which are addressed in the list below with the reason(s) why they do not integrate the abstract idea into a practical application:
- a computer-implemented system; artificial intelligence; a computer system; machine learning: These element(s)/limitation(s) amount to mere instructions to apply an exception. See MPEP 2106.05(f). In making this determination, examiners may consider whether the claim invokes computers or other machinery merely as a tool to perform an existing process. Mere instructions to apply an exception is a consideration with respect to both integration of an abstract idea into a practical application and significantly more. MPEP 2106.05(f)(2) states: “Use of a computer or other machinery in its ordinary capacity for economic or other tasks (e.g., to receive, store, or transmit data) or simply adding a general purpose computer or computer components after the fact to an abstract idea (e.g., a fundamental economic practice or mathematical equation) does not provide significantly more. See Affinity Labs v. DirecTV, 838 F.3d 1253, 1262, 120 USPQ2d 1201, 1207 (Fed. Cir. 2016) (cellular telephone); TLI Communications LLC v. AV Auto, LLC, 823 F.3d 607, 613, 118 USPQ2d 1744, 1748 (Fed. Cir. 2016) (computer server and telephone unit).” This is the case with these particular claim element(s)/limitation(s). Those elements/limitations do not meaningfully limit the claim because implementing an abstract idea on a generic computer does not integrate the abstract idea into a practical application, similar to how the recitation of the computer in the claim in Alice amounted to mere instructions to apply the abstract idea of intermediated settlement on a generic computer. Therefore, these particular claim element(s)/limitation(s) do not integrate the abstract idea into a practical application for at least this reason.
Thus, taken alone, the additional elements do not integrate the abstract idea into a practical application. Looking at the limitations as an ordered combination adds nothing that is not already present when looking at the elements taken individually. There is no indication that the combination of elements improves the functioning of a computer or improves any other technology.
Accordingly, the additional elements do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea. The claim(s) are directed to an abstract idea.
The claim(s) do not include additional elements that are sufficient to amount to significantly more than the judicial exception, either individually or as an ordered combination. As discussed above with respect to integration of the abstract idea into a practical application, the additional elements of computer-related components amount to no more than mere instructions to apply the exception using generic computer components. Mere instructions to apply an exception using generic computer components cannot provide an inventive concept.
The claim(s) are not patent eligible.
As per dependent claim(s) 18-20, these claim(s) incorporate the above abstract idea via their dependencies on the respective independent claim(s). The additional element(s)/limitation(s) of the respective independent claim(s) do not integrate the abstract idea into a practical application, nor do they add significantly more, with respect to those dependent claim(s), under the same reasoning as above with respect to the respective independent claim(s).
The added elements/limitations of those dependent claim(s) do not integrate the abstract idea into a practical application nor add significantly more because they all merely add further functional step(s) and/or detail to the abstract idea; as part of the abstract idea, they cannot integrate into a practical application or be significantly more than the abstract idea of which they are a part. For example, claim 18 merely adds detail to the parameters for generating flights.
Claim(s) 17-20 are therefore not drawn to eligible subject matter as they are directed to an abstract idea that is not integrated into a practical application and is without significantly more.
Double Patenting
A rejection based on double patenting of the “same invention” type finds its support in the language of 35 U.S.C. 101 which states that “whoever invents or discovers any new and useful process... may obtain a patent therefor...” (Emphasis added). Thus, the term “same invention,” in this context, means an invention drawn to identical subject matter. See Miller v. Eagle Mfg. Co., 151 U.S. 186 (1894); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Ockert, 245 F.2d 467, 114 USPQ 330 (CCPA 1957).
A statutory type (35 U.S.C. 101) double patenting rejection can be overcome by canceling or amending the claims that are directed to the same invention so they are no longer coextensive in scope. The filing of a terminal disclaimer cannot overcome a double patenting rejection based upon 35 U.S.C. 101.
Claims 1-20 are provisionally rejected under 35 U.S.C. 101 as claiming the same invention as that of claims 1-20 of copending Application No. 19/459,307 (reference application). This is a provisional statutory double patenting rejection since the claims directed to the same invention have not in fact been patented.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
a. Eade, US 20230385717 A1 (artificial intelligence-powered tour booking system);
b. Stableford, US 20230306538 A1 (system and method for processing changes to itineraries);
c. Bharti, US 20230162300 A1 (artificial intelligence for travel partner and destination recommendations);
d. Annakov, US 20210264326 A1 (flight-recommendation-and-booking methods and systems based on machine learning);
e. Glatfelter, US 20210240772 A1 (method and system for flight scheduling);
f. Halioui, US 20210034612 A1 (controlling generation of multi-input search results);
g. Jafri, US 20190378058 A1 (travel distribution system);
h. Renaud, US 20160180256 A1 (history-based probability forecasting).
Any inquiry concerning this communication or earlier communications from the examiner should be directed to NATHAN ERB whose telephone number is (571)272-7606. The examiner can normally be reached M - F, 11:30 AM - 8 PM.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, JEFFREY ZIMMERMAN can be reached at (571) 272-4602. 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.
nhe
/NATHAN ERB/Primary Examiner, Art Unit 3628