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 .
Priority
Acknowledgment is made of applicant's claim for foreign priority based on application EP23382192.5 filed on 3/2/23. However, applicant has not filed a certified copy of the application as required by 37 CFR 1.55. Applicant must file that certified copy to get the foreign priority.
Claim Objections
Claims 1 and 4 are objected to because of the following informalities:
In claim 1, “to a channel, wherein each channel corresponds to one of the plurality of aircraft; and providing access to the channels to a user.” should be “to a respective channel of a plurality of channels, wherein each channel corresponds to one of the plurality of aircraft; and providing access to the plurality of channels to a user.”
In claim 4, “extracting an aircraft identification from each of the plurality of communications, the aircraft identification indicating an aircraft the message is associated with;” should be “extracting an aircraft identification from each of the plurality of communications, the aircraft identification indicating an aircraft [[the]] a respective message is associated with;”
Claims 8, 13, and 20-21 are objected to under 37 CFR 1.75(c) as being in improper form because of the presence of improper multiple dependent claims. That is because “A multiple dependent claim shall not serve as a basis for any other multiple dependent claim”. Id. The following corrections should be made to resolve this issue:
In claim 8, “The method of any of claims 5 to 7,” should be “The method of claim 5,”
In claim 13, “The method of any of claims 3 to 12,” should be “The method of claim 3,”
In claim 20, “the method of any preceding claim.” should be “the method of 1.”
In claim 21, “the method of any of claims 1 to 19.” should be “the method of claim 1.”
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-21 are rejected under 35 U.S.C. 101 because the claimed invention is directed to a judicial exception (i.e., a law of nature, a natural phenomenon, or an abstract idea) without significantly more. The claimed invention is directed to the concept of receiving scheduling information comprising flight and turnaround information for a plurality of aircraft and associating the flight and turnaround information for each aircraft with a respective channel on a one-to-one basis. This judicial exception is not integrated into a practical application. The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception and do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea.
Regarding claim 1, applicant recites A method of managing aircraft information comprising:
receiving scheduling information, the scheduling information comprising flight and turnaround information relating to a plurality of aircraft;
extracting the flight and turnaround information for each of the plurality of aircraft from the scheduling information;
assigning the extracted flight and turnaround information for each of the plurality of aircraft to a channel, wherein each channel corresponds to one of the plurality of aircraft; and
providing access to the channels to a user.
The claim recites a series of steps and therefore is directed to a process, which satisfies step 1 of the Section 101 analysis. Under the two-prong inquiry, the claim is eligible at revised step 2A unless: Prong One: the claim recites a judicial exception; and Prong Two: the exception is not integrated into a practical application of the exception.
The above claim steps are directed to the concept of receiving scheduling information comprising flight and turnaround information for a plurality of aircraft and associating the flight and turnaround information for each aircraft with a respective channel on a one-to-one basis, which is an abstract idea that can be performed by a user mentally or manually and falls within the Mental Processes grouping. (Prong one: YES, recites an abstract idea).
Nothing in the claim elements precludes the steps from being performed entirely by a human. The “providing access… to a user” step is insufficient to amount to significantly more than the judicial exception because it merely outputs the judicial exception, which is insignificant extra-solution activity that does not integrate the judicial exception into a practical application. (Prong Two: NO, does not recite additional elements that integrate the abstract idea into a practical application like that shown in MPEP 2106.05).
Under step 2B, the claimed invention does not recite additional elements that are indicative of an inventive concept.
Examiner’s note to help applicant overcome the 101 rejection: applicant can overcome the 101 rejection by analogizing claim 1 of the present application to Example 42, Claim 1 of the USPTO’s Subject Matter Eligibility Examples 37 to 42. Example 42, Claim 1 involved gathering medical data in various forms, standardizing the data, and outputting the data to users. The Office found this example claim to be eligible because, “the additional elements recite a specific improvement over prior art systems by allowing remote users to share information in real time in a standardized format regardless of the format in which the information was input by the user. Thus, the claim is eligible because it is not directed to the recited judicial exception (abstract idea).” (See Pages 18-19 of the USPTO’s Subject Matter Eligibility Examples 37 to 42).
Similarly, applicant can argue that claim 1 of the present application gathers data from various formats (both flight data and turnaround data), consolidates that data, and remotely provides that data to users, and therefore should be eligible for the same reasons as Example 42, Claim 1. If applicant makes this argument, then examiner will withdraw all 101 rejections.
Regarding claim 2, applicant recites The method of claim 1, further comprising:
determining, for each aircraft based on the extracted flight and turnaround information for that aircraft, one or more turnaround tasks to be completed; monitoring the progress of the one or more turnaround tasks; and presenting a current status of the one or more turnaround tasks.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. So this claim is ineligible for the same reasons as that claim.
Regarding claim 3, applicant recites The method of claim 2, wherein determining, for each aircraft based on the extracted flight and turnaround information for that aircraft, one or more turnaround tasks to be completed comprises: obtaining an aircraft identification from the extracted flight and turnaround information; and querying a database for turnaround tasks corresponding to the aircraft identification.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. So this claim is ineligible for the same reasons as that claim.
Regarding claim 4, applicant recites The method of any of claims 1 to 3, wherein the method further comprises: receiving a plurality of communications; extracting an aircraft identification from each of the plurality of communications, the aircraft identification indicating an aircraft the message is associated with; and assigning each of the plurality of communications to the channel corresponding to the aircraft associated with each message.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. So this claim is ineligible for the same reasons as that claim.
Regarding claim 5, applicant recites The method of claim 4, wherein the plurality of communications comprise communications of a first type and communications of a second type; and wherein the communications of the first type and the communications of the second type are presented in the channel in an integrated manner.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. The labeling of the data into types does not change this. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 6, applicant recites The method of claim 5, wherein the communications of a first type are ACARS messages, and wherein receiving a plurality of communications comprises: receiving one or more ACARS messages; extracting an aircraft identification from each of the one or more the ACARS messages, the aircraft identification identifying an aircraft from which the corresponding ACARS message originated; converting each of the one or more ACARS messages to a message of the second type; and assigning each of the one or more converted ACARS messages to a channel corresponding to the aircraft from which the message originated.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. ACARS and assigning communications to channels are generic computer activities that do not change this fact. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 7, applicant recites The method of claim 6, wherein each channel corresponding to an aircraft is not capable of displaying ACARS messages but is capable of displaying messages of the second type.
However, these details pertaining to displaying are merely outputting the judicial exception, which is insignificant extra-solution activity that is not adequate to integrate the judicial exception into a practical application.
Regarding claim 8, applicant recites The method of any of claims 5 to 7, wherein the communications of the second type are not ACARS messages.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. Specifying the types of messages does not change that. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 9, applicant recites The method of claim 8, wherein the communications of the second type are SMS messages, emails, or IP messages.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. Specifying the types of messages does not change that. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 10, applicant recites The method of claim 6, wherein the one or more ACARS messages comprise a notification of a status of the originating aircraft or a component of the originating aircraft.
However, these details pertaining to displaying are merely outputting the judicial exception, which is insignificant extra-solution activity that is not adequate to integrate the judicial exception into a practical application.
Regarding claim 11, applicant recites The method of claim 10, wherein the method further comprises: determining, for each aircraft based on the extracted flight and turnaround information for that aircraft, one or more status events; monitoring the progress of the one or more status events based on the one or more ACARS messages; and presenting a current status of the one or more status events.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 12, applicant recites The method of claim 11, wherein determining, for each aircraft based on the extracted flight and turnaround information for that aircraft, one or more status events comprises: obtaining an aircraft identification from the extracted flight and turnaround information; and querying a database for status events corresponding to the aircraft identification.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 13, applicant recites The method of any of claims 3 to 12, wherein the aircraft identification uniquely identifies an aircraft.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. Specifying the types of information does not change that. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 14, applicant recites The method of claim 13, wherein optionally the aircraft identification comprises one or more of an aircraft registration code, an aircraft model, and a flight number.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. Specifying the types of information does not change that. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 15, applicant recites The method of claim 1, wherein providing access to the channel to a user comprises: receiving a channel access request from a user; receiving a permission status of the user; and allowing access to the channel in accordance with the permission status.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. Specifying the types of information, such as permission information, does not change that. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 16, applicant recites The method of claim 15, wherein if the permission status of the user is indicative of a full permission, the method further comprises allowing access in accordance with the permission status comprises allowing the user to view and send communications of a first type and a second type.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 17, applicant recites The method of claim 15, wherein if the permission status of the user is indicative of a partial permission, the method further comprises allowing access in accordance with the permission status comprises allowing the user to view but not send communications of the first type, and view and send communications of the second type.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 18, applicant recites The method of claim 15, wherein if the permission status of the user is indicative of no permission, the method further comprises allowing access in accordance with the permission status comprises not allowing the user to view or send communications of the first type, but allowing the user to view and send communications of the second type.
However, this claim still amounts to merely gathering and outputting data, just like claim 1. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 19, applicant recites The method of claim 16, wherein the communications of a first type are ACARS messages, and wherein the method further comprises: receiving, in a channel and from a user with full permission, a message to be sent to the aircraft corresponding to that channel; converting the message into an ACARS message; and sending the ACARS message to the aircraft.
However, this claim still amounts to merely gathering, processing, and outputting data, just like claim 1. So this claim is ineligible for the same reasons as claim 1.
Regarding claim 20, applicant recites A computer system configured to perform the method of any preceding claim.
This claim adds the additional element of the computer system.
However, under step 2B, the additional element is not indicative of an inventive concept. The additional element, when considered both individually and as part of an ordered combination, does not amount to significantly more than the abstract idea. The computer system is described in paragraph [0050] of applicant’s specification as merely a general purpose computer. Therefore this additional limitation is no more than mere instructions to apply the exception using generic computer components. The recitation of generic processors/computers does not take the above limitations out of the mental processes grouping.
The implementation of the abstract idea on generic computers and/or generic computer components does not add significantly more, similar to how the recitation of the computer in Alice amounted to mere instructions to apply the abstract idea on a generic computer. The claims merely invoke the additional elements as tools that are being used in their ordinary capacity. Further, the courts have found that simply limiting the use of the abstract idea to a particular environment does not add significantly more. Thus, taken alone, the additional elements do not amount to significantly more than the above-identified judicial exception (the abstract idea). 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. Their collective functions merely provide generic computer implementation.
Regarding claim 21, applicant recites A non-transitory memory having stored thereon instructions that, when executed on the computer system of claim 20, cause the computer system to perform the method of any of claims 1 to 19.
This claim adds the additional element of the non-transitory memory.
However, under step 2B, the additional element is not indicative of an inventive concept. The additional element, when considered both individually and as part of an ordered combination, does not amount to significantly more than the abstract idea. The non-transitory memory is described in paragraph [0057] of applicant’s specification as merely a general purpose computer component. Therefore this additional limitation is no more than mere instructions to apply the exception using generic computer components. The recitation of generic processors/computers does not take the above limitations out of the mental processes grouping.
The implementation of the abstract idea on generic computers and/or generic computer components does not add significantly more, similar to how the recitation of the computer in Alice amounted to mere instructions to apply the abstract idea on a generic computer. The claims merely invoke the additional elements as tools that are being used in their ordinary capacity. Further, the courts have found that simply limiting the use of the abstract idea to a particular environment does not add significantly more. Thus, taken alone, the additional elements do not amount to significantly more than the above-identified judicial exception (the abstract idea). 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. Their collective functions merely provide generic computer implementation.
Examiner’s note to help applicant overcome the 101 rejection: applicant can overcome the 101 rejection by analogizing claim 1 of the present application to Example 42, Claim 1 of the USPTO’s Subject Matter Eligibility Examples 37 to 42. Example 42, Claim 1 involved gathering medical data in various forms, standardizing the data, and outputting the data to users. The Office found this example claim to be eligible because, “the additional elements recite a specific improvement over prior art systems by allowing remote users to share information in real time in a standardized format regardless of the format in which the information was input by the user. Thus, the claim is eligible because it is not directed to the recited judicial exception (abstract idea).” (See Pages 18-19 of the USPTO’s Subject Matter Eligibility Examples 37 to 42).
Similarly, applicant can argue that claim 1 of the present application gathers data from various formats (both flight data and turnaround data), consolidates that data, and remotely provides that data to users, and therefore should be eligible for the same reasons as Example 42, Claim 1. If applicant makes this argument, then examiner will withdraw all 101 rejections.
Allowable Subject Matter
Claims 1-21 are objected to for containing allowable subject matter but would be allowable if rewritten to resolve the objections and rejections discussed in prior sections of this office action.
The closest prior art of record is Tarraf et al. (US 20240089741 A1) in view of Agrawal et al. (US 20150348422 A1), hereinafter referred to as Tarraf and Agrawal, respectively. The following is a statement of reasons for the indication of allowable subject matter:
Regarding claim 1, Tarraf discloses A method of managing aircraft information (See at least Fig. 5 in Tarraf: Tarraf discloses an exemplary channel allocation process for RF spectrum management of ground to air communication networks [See at least Tarraf, 0109]) comprising:
receiving scheduling information, the scheduling information comprising flight relating to a plurality of aircraft (See at least Fig. 5 in Tarraf: Tarraf discloses that at step 502, the digital twin 304 can receive the information from the pilot/operator that is necessary to determine the RF channel needs of a given flight as well as the geographic locations and altitudes that the flight will occupy during its flight [See at least Tarraf, 0109]);
extracting the flight information for each of the plurality of aircraft from the scheduling information (See at least Fig. 5 in Tarraf: Tarraf discloses that at step 504, the digital twin 304 can use the information received from the pilot 302 to determine if there is RF coverage for the entirety of the proposed flight [See at least Tarraf, 0110]);
assigning the extracted flight for each of the plurality of aircraft to a channel (See at least Fig. 5 in Tarraf: Tarraf discloses that once the channel or channels have been assigned to the operator by the digital twin 304 at step 510, the process 500 can move to step 510 wherein the channel allocation and other additional information about the channel can be sent to the spectrum management system 322 for implementation during flight [See at least Tarraf, 0116]), wherein each channel corresponds to one of the plurality of aircraft (Tarraf discloses that one or more sub-channels can also be assigned to a single UAV [See at least Tarraf, 0099]); and
providing access to the channels to a user (See at least Fig. 5 in Tarraf: Tarraf discloses that the process 500 can move to step 510 wherein the channel allocation and other additional information about the channel can be sent to the spectrum management system 322 for implementation during flight [See at least Tarraf, 0116]).
Agrawal teaches a method for managing aircraft info where the scheduling information further comprises turnaround information relating to a plurality of aircraft, wherein the turnaround information for each of the plurality of aircraft is also extracted from the scheduling information (Agrawal teaches that the aircraft turnaround optimizer 220 obtains the time taken for each aircraft turnaround activity at each airport during the journey of the aircraft 202 via the communication network 230 [See at least Agrawal, 0027]).
However, none of the prior art of record, either taken alone or in combination, teaches or suggests wherein the turnaround information for each of the plurality of aircraft is assigned to a channel, wherein each channel corresponds to one of the plurality of aircraft.
In order to read on the above missing limitations, a reference would have to teach where turnaround information for each aircraft is assigned to a respective channel on a one-to-one basis. It must be noted that “turnaround” does not refer to performing a turn by an aircraft; instead, “turnaround” is a term of art which refers to the process that an aircraft undergoes between arrival at a destination and departure for its next flight, including a series of maintenance tasks that must to be performed to prepare the aircraft for that next flight (See at least paragraphs [0037-0039] in the specification).
But none of the prior art teaches assignment of such tasks for each aircraft to a respective dedicated channel reserved for that aircraft, so none of the prior art reads on the above missing limitations. Tarraf teaches assigning each aircraft to a respective dedicated channel (See at least [Tarraf, 0099]). But Tarraf is silent as to including turnaround information in that assignment.
Conversely, Agrawal teaches gathering turnaround information for a plurality of aircraft (See at least [Agrawal, 0027]). But Agrawal is silent as to creating a one-to-one correspondence between each aircraft’s turnaround information and a respective channel. Therefore, there is no overlap between Tarraf and Agrawal that would warrant combining them with each other or other prior art of record to arrive at the claimed invention.
For at least the above stated reasons, claim 1 contains allowable subject matter.
Regarding claims 2-21, these claims also contain allowable subject matter at least by virtue of their dependence from claim 1.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to NAEEM T ALAM whose telephone number is (571)272-5901. The examiner can normally be reached M-F, 9am-5pm.
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, FADEY JABR can be reached at (571) 272-1516. 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.
/NAEEM TASLIM ALAM/Primary Examiner, Art Unit 3668