Prosecution Insights
Last updated: November 15, 2026
Application No. 18/606,667

Launch on Demand

Non-Final OA §101§103§DOUBLEPATENT
Filed
Mar 15, 2024
Priority
May 30, 2019 — provisional 62/854,937 +1 more
Examiner
AHN, HYANG
Art Unit
3661
Tech Center
3600 — Transportation & Electronic Commerce
Assignee
Launch On Demand Group Inc.
OA Round
1 (Non-Final)
84%
Grant Probability
Favorable
1-2
OA Rounds
99%
With Interview

Examiner Intelligence

Grants 84% — above average
84%
Career Allowance Rate
16 granted / 19 resolved
+32.2% vs TC avg
Strong +30% interview lift
Without
With
+30.0%
Interview Lift
resolved cases with interview
Typical timeline
Avg Prosecution
18 currently pending
Career history
40
Total Applications
across all art units

Office Action

§101 §103 §DOUBLEPATENT
Notice of Pre-AIA or AIA Status 1. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Double Patenting 2. The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b). The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13. The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer. 3. Claims 1-10 rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-3 and 11-13 of U.S. Patent No. 120060667B2. Although the claims at issue are not identical, they are not patentably distinct from each other because the instant application 18606667 is fully anticipated by U.S. Patent No. 12006067B2. A table showing the claims of the application and the corresponding claim of issued patent side-by-side for comparison is shown below. Matching elements of the claim limitations appear in bold while non-matching elements of the claim limitations are not bolded. Instant Application Issued Patent US120060667B2 1. A space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive one or more data feeds; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received one or more data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle. 1. A space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive a plurality of data feeds that include: a data feed from a satellite catalog; a data feed from an orbital debris catalog; a data feed from a national airspace tracking system; a data feed from a maritime tracking system; a data feed from a weather monitoring system; and a data feed from a range monitoring system; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received plurality of data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters. 2. The space launch service platform computing device of claim 1, wherein the at least one processor is configured to: receive the one or more data feeds by receiving at least one data feed from a satellite catalog; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the at least one data feed from the satellite catalog and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. 1. A space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive a plurality of data feeds that include: a data feed from a satellite catalog; a data feed from an orbital debris catalog; a data feed from a national airspace tracking system; a data feed from a maritime tracking system; a data feed from a weather monitoring system; and a data feed from a range monitoring system; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received plurality of data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters. 3. The space launch service platform computing device of claim 1, wherein the at least one processor is configured to: receive the one or more data feeds by receiving at least one data feed from an orbital debris catalog; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the at least one data feed from the orbital debris catalog and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. 1. A space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive a plurality of data feeds that include: a data feed from a satellite catalog; a data feed from an orbital debris catalog; a data feed from a national airspace tracking system; a data feed from a maritime tracking system; a data feed from a weather monitoring system; and a data feed from a range monitoring system; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received plurality of data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters. 4. The space launch service platform computing device of claim 1, wherein the at least one processor is configured to: receive the one or more data feeds by receiving at least one data feed from a national airspace tracking system; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the at least one data feed from the national airspace tracking system and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. 1. A space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive a plurality of data feeds that include: a data feed from a satellite catalog; a data feed from an orbital debris catalog; a data feed from a national airspace tracking system; a data feed from a maritime tracking system; a data feed from a weather monitoring system; and a data feed from a range monitoring system; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received plurality of data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters. 5. The space launch service platform computing device of claim 1, wherein the at least one processor is configured to: receive the one or more data feeds by receiving at least one data feed from a maritime tracking system; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the at least one data feed from the maritime tracking system and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. 1. A space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive a plurality of data feeds that include: a data feed from a satellite catalog; a data feed from an orbital debris catalog; a data feed from a national airspace tracking system; a data feed from a maritime tracking system; a data feed from a weather monitoring system; and a data feed from a range monitoring system; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received plurality of data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters. 6. The space launch service platform computing device of claim 1, wherein the at least one processor is configured to: receive the one or more data feeds by receiving at least one data feed from a weather monitoring system; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the at least one data feed from the weather monitoring system and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. 1. A space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive a plurality of data feeds that include: a data feed from a satellite catalog; a data feed from an orbital debris catalog; a data feed from a national airspace tracking system; a data feed from a maritime tracking system; a data feed from a weather monitoring system; and a data feed from a range monitoring system; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received plurality of data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters. 7. The space launch service platform computing device of claim 1, wherein the at least one processor is configured to: receive the one or more data feeds by receiving at least one data feed from a range monitoring system; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the at least one data feed from the range monitoring system and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. 1. A space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive a plurality of data feeds that include: a data feed from a satellite catalog; a data feed from an orbital debris catalog; a data feed from a national airspace tracking system; a data feed from a maritime tracking system; a data feed from a weather monitoring system; and a data feed from a range monitoring system; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received plurality of data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters. 8. The space launch service platform computing device of claim 1, wherein the at least one processor is configured to: receive the monitoring data from the plurality of sensors located at the launch site and on the launch vehicle by receiving monitoring data that includes real-time structural integrity assessments that allow for on-the-fly adjustments to a launch schedule based on the condition of the launch vehicle; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the received one or more data feeds and the real-time structural integrity assessments to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. 1. A space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive a plurality of data feeds that include: a data feed from a satellite catalog; a data feed from an orbital debris catalog; a data feed from a national airspace tracking system; a data feed from a maritime tracking system; a data feed from a weather monitoring system; and a data feed from a range monitoring system; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received plurality of data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters. 2. The space launch service platform computing device of claim 1, wherein the at least one processor is configured with processor-executable instructions to receive the monitoring data from the plurality of sensors located at the launch site and on the launch vehicle by: receiving monitoring data that includes real-time structural integrity assessments that allow for on-the-fly adjustments to a launch schedule based on the condition of the launch vehicle. 9. The space launch service platform computing device of claim 1, wherein the at least one processor is configured to: receive the monitoring data from the plurality of sensors located at the launch site and on the launch vehicle by receiving at least one or more of frequency data, global positioning system (GPS) data, telemetry data, optics data, or surveillance data; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the received one or more data feeds and the at least one or more of frequency data, GPS data, telemetry data, optics data, or surveillance data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. 1. A space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive a plurality of data feeds that include: a data feed from a satellite catalog; a data feed from an orbital debris catalog; a data feed from a national airspace tracking system; a data feed from a maritime tracking system; a data feed from a weather monitoring system; and a data feed from a range monitoring system; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received plurality of data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters. 3. The space launch service platform computing device of claim 1, wherein the at least one processor is configured with processor-executable instructions to receive monitoring data from the plurality of sensors located at the launch site and on the launch vehicle by receiving: frequency data; global positioning system (GPS) data; telemetry data; optics data; and surveillance data. 10. The space launch service platform computing device of claim 1, wherein the at least one processor is configured to: output the indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters by outputting potential launch scenarios based on the combined launch data so as to allow operators to visualize and assess different launch trajectories and conditions before making a final launch decision; output the indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters by outputting visual representations on a graphical user interface that displays the launch windows in a timeline format with overlaid condition-based criteria assessments; or output the indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters by outputting a probabilistic assessment for each of the identified non-linear non-periodic and discontinuous clear launch windows indicating a likelihood of the window remaining viable up to the point of launch. 11. The space launch service platform computing device of claim 1, wherein the at least one processor is configured with processor-executable instructions to output the indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters by: outputting visual representations on a graphical user interface that displays the launch windows in a timeline format with overlaid condition-based criteria assessments. 12. The space launch service platform computing device of claim 1, wherein the at least one processor is configured with processor-executable instructions to output the indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters by: outputting potential launch scenarios based on the combined launch data so as to allow operators to visualize and assess different launch trajectories and conditions before making a final launch decision. 13. The space launch service platform computing device of claim 1, wherein the at least one processor is configured with processor-executable instructions to output the indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle and mission parameters by: outputting a probabilistic assessment for each of the identified non-linear non-periodic and discontinuous clear launch windows indicating a likelihood of the window remaining viable up to the point of launch. As illustrated in the table above, all matching elements of the claim limitations appear in bold while non-matching elements of the claim limitations are not bolded. Although the claims at issue are not identical, they are not patentably distinct from each other because both inventions are directed to a space launch service platform computing device that receives, generates and output data relating to launch data, such as launch window and launch conditions. The difference between the claims at issue are merely in slight wording and arrangement of the claim limitations. However, the key technical features and specific limitations remain the same as shown above by the bolded portions of the claims. The nonbolded limitations do not establish patentable distinctness, but rather restates or reorganize previously claimed subject matter. The application merely separates limitations recited in a single claim of the reference application into a plurality of claims, without introducing a patentably distinct invention. These differences in slight claim wording, arrangements, and presentations do not render the claims patentably distinct. Further, as shown by the bolded portions, both sets of claims recite receiving data feeds and monitoring data, generating combined launch data, identifying clear launch windows, and outputting launch opportunities for the independent claims. The dependent claims then recites the same data sources, monitoring information, and output functionalities. The differences merely involve rearranging or separating these limitations into multiple claims without introducing anything different. As can be seen, independent claim 1 is fully anticipated by the corresponding independent claim 1 of the reference patent number 12006067. The instant claim as a whole, including each and every limitation, is to be found within the reference claim. Similarly, the dependent claims 2-10 are fully anticipated. Therefore, the reference application necessitates a case of double patenting. In addition, claims 11-20 and 21-30 recite a method and a non-transitory computer-readable storage medium with similar limitations to claims 1-10 and therefore are similarly found to be double patenting. 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. 4. Claim 1 is rejected under 35 U.S.C. 101 because the claimed invention is directed to abstract idea without significantly more. The determination of whether a claim recites patent ineligible subject matter is a 2 step inquiry. STEP 1: the claim does not fall within one of the four statutory categories of invention (process, machine, manufacture or composition of matter), see MPEP 2106.03, or STEP 2: the claim recites a judicial exception, e.g. an abstract idea, without reciting additional elements that amount to significantly more than the judicial exception, as determined using the following analysis: see MPEP 2106.04 STEP 2A (PRONG 1): Does the claim recite an abstract idea, law of nature, or natural phenomenon? see MPEP 2106.04(II)(A)(1) STEP 2A (PRONG 2): Does the claim recite additional elements that integrate the judicial exception into a practical application? see MPEP 2106.04(II)(A)(2) and 2106.05(a) thru (d) for explanations. STEP 2B: Does the claim recite additional elements that amount to significantly more than the judicial exception? see MPEP 2106.05 101 Analysis – Step 1 Claim 1 is directed to a space launch service platform computing device (i.e., a machine). Therefore, claim 1 is within at least one of the four statutory categories. 101 Analysis – Step 2A, Prong I Regarding Prong I of the Step 2A analysis, the claims are to be analyzed to determine whether they recite subject matter that falls within one of the follow groups of abstract ideas: a) mathematical concepts, b) certain methods of organizing human activity, and/or c) mental processes. see MPEP 2106(A)(II)(1) and MPEP 2106.04(a)-(c) Independent claim 1 includes limitations that recite an abstract idea (emphasized below [with the category of abstract idea in brackets]) and will be used as a representative claim for the remainder of the 101 rejection. Claim 1 recites: a space launch service platform computing device, comprising: at least one processor configured with processor-executable instructions to: receive one or more data feeds; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; use the received one or more data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle [mental process] analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory [mental process]; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle. The examiner submits that the foregoing bolded limitation(s) constitute a “certain method of organizing human activity”, a “mental process" because under its broadest reasonable interpretation, the claim covers performance of the limitation in the human mind through observation, evaluation, and judgment (see MPEP 2016.04(a)(2)). For example, “use the received one or more data…” in the context of the claim encompasses a person observing, combining, and evaluating received information to determine current and predicted conditions at and around a launch site and along a launch trajectory. For example, “analyze…” in the context of the claim encompasses a person comparing and evaluating the combined launch data received against predetermined launch criteria to estimate a time of launch window around a launch site. Accordingly, the claim recites at least one abstract idea. 101 Analysis – Step 2A, Prong II Regarding Prong II of the Step 2A analysis, the claims are to be analyzed to determine whether the claim, as a whole, integrates the abstract into a practical application. see MPEP 2106.04(II)(A)(2) and MPEP 2106.04(d)(2). It must be determined whether any additional elements in the claim beyond the abstract idea integrate the exception into a practical application in a manner that imposes a meaningful limit on the judicial exception. The courts have indicated that additional elements merely using a computer to implement an abstract idea, adding insignificant extra solution activity, or generally linking use of a judicial exception to a particular technological environment or field of use do not integrate a judicial exception into a “practical application.” In the present case, the additional limitations beyond the above-noted abstract idea are as follows (where the underlined portions are the “additional limitations” [with a description of the additional limitations in brackets], while the bolded portions continue to represent the “abstract idea”.): a space launch service platform computing device [generic linking to technical field, 2106.05(h)], comprising: at least one processor configured with processor-executable instructions to [mere instructions to apply an exception, 2106.05(f)]: receive one or more data feeds [insignificant pre-solution activity (data gathering) 2106.05(g)]; receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle [insignificant pre-solution activity (data gathering) 2106.05(g)]; use the received one or more data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle [mental process]; analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory [mental process]; and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle [insignificant post solution activity of merely outputting the result of the mental process 2106.05(g)]. For the following reason(s), the examiner submits that the above identified additional limitations do not integrate the above-noted abstract idea into a practical application. Regarding the additional limitation of “a space launch service platform computing device…”, the examiner submits that this is recited at a high level of generality and serves only to link the particular abstract concept to a broad technical field. This only serve as generic computer system to generically perform the mental process. Regarding the additional limitation of “at least one processor configured with processor-executable instructions to…”, the examiner submits that the processor is recited at a high level of generality and merely serves as a generic computer component to generically perform the mental process, which is a mere instructions to apply the exception using a generic computer (see MPEP 2106.05(f)). Regarding the limitations of “receive one or more data feeds…”, “receive monitoring data…”, and “output an indication…”, these limitations amount to no more than mere instruction to apply the exception using a generic computer. Regarding the “receive…”, specifically, these merely comprises gathering data from a network and an external generic computer system and it can be done through a generic computer and processor. Regarding the “output an indication…”, specifically, this merely comprises outputting the result of the mental process and it does not specify if it outputs to any source. Thus, taken alone, the additional elements do not integrate the abstract idea into a practical application. Further, looking at the additional limitation(s) as an ordered combination or as a whole, the limitation(s) add nothing that is not already present when looking at the elements taken individually. For instance, there is no indication that the additional elements, when considered as a whole, reflect an improvement in the functioning of a computer or an improvement to another technology or technical field, apply or use the above-noted judicial exception to effect a particular treatment or prophylaxis for a disease or medical condition, implement/use the above-noted judicial exception with a particular machine or manufacture that is integral to the claim, effect a transformation or reduction of a particular article to a different state or thing, or apply or use the judicial exception in some other meaningful way beyond generally linking the use of the judicial exception to a particular technological environment, such that the claim as a whole is not more than a drafting effort designed to monopolize the exception. see MPEP § 2106.05. Accordingly, the additional limitation(s) do/does not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea. 101 Analysis – Step 2B Regarding Step 2B of the Revised Guidance, representative independent claim 1 does not include additional elements (considered both individually and as an ordered combination) that are sufficient to amount to significantly more than the judicial exception for the same reasons to those discussed above with respect to determining that the claim does not integrate the abstract idea into a practical application. As discussed above with respect to the integration of the abstract idea into a practical application, the additional element of “output” to perform the generating a launch opportunity indication amounts to nothing more than mere instructions to apply the exception using a generic computer as it merely displays a message on a generic computer screen (see specification [0058]). Mere instructions to apply an exception using a generic computer cannot provide an inventive concept. And, as discussed above, the additional limitations related to acquiring and transmitting data, the examiner submits that these limitations are insignificant extra-solution activity. Also, the additional limitation of “at least one processor configured with processor-executable instructions to…” merely uses a generic computer to perform the identified mental process of observing and evaluating the received information and does not provide an inventive concept beyond the judicial exception, i.e. mere instructions to apply an exception. Independent claims 11 and 21 recites similar limitations to independent claim 1 through a method and a non-transitory processor-readable storage medium, which further indicates a mental process, and therefore requires a similar rejection. Dependent claim(s) 2-7 and 9-14 do not recite any further limitations that cause the claim(s) to be patent eligible. Rather, the limitations of dependent claims are directed toward additional aspects of the judicial exception and/or well-understood, routine and conventional additional elements that do not integrate the judicial exception into a practical application. Dependent claims 2-7, 12-17, and 22-27 merely recite receiving additional data from various sources and using the received data to generate launch data, i.e. mere data gather and evaluating information. Dependent claims 8. 18. And 28 only recites receiving real-time structural integrity assessments and using the data to generate a combined launch data, i.e. mere data gathering and evaluating received data. Dependent claims 9, 19, and 29 only recites receiving sensor data and using the data to generate combined launch data. Dependent claims 10, 20, and 30 merely recites outputting launch scenarios, graphical representations, or probabilistic assessments, which merely amounts to insignificant post solution activity of displaying results and further mental evaluation of data. Therefore, dependent claims 2-10, 12-20 and 22-30 are not patent eligible under the same rationale as provided for in the rejection of claim 1. Claim Rejections - 35 USC § 103 The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows: 1. Determining the scope and contents of the prior art. 2. Ascertaining the differences between the prior art and the claims at issue. 3. Resolving the level of ordinary skill in the pertinent art. 4. Considering objective evidence present in the application indicating obviousness or nonobviousness. 5. Claims 1-2, 6-7, 9-12, 16-17, and 19-22 are rejected under pre-35 USC 103 a being unpatentable over Hoots (US 20100250137A1) in view of Hushing et al. (US 20020178258A1). Regarding claim 1, Hoots teaches a space launch service platform computing device (see [0022] and Fig. 5 in general where a launch collision avoidance system includes a computer that includes a processor to execute launch collision avoidance software and generate launch collision avoidance reports, indications, commands, and other inputs, signals or the like that can be used to make decisions regarding and control launch events.), comprising: at least one processor configured with processor-executable instructions to (see [0022] and Fig. 5 where a launch collision avoidance system includes a computer that includes a processor to execute launch collision avoidance software and generate launch collision avoidance reports, indications, commands, and other inputs, signals or the like that can be used to make decisions regarding and control launch events.): receive one or more data feeds (see [0024]-[0025] and Figs 6-7 where inputs are accessed by a computer, and the inputs include launch window start time, end time, risk threshold, distance threshold, file name of launch ephemeris, and file name of protected satellites. The launch ephemeris files are read during data processing and protected satellite data is accessed during main processing, i.e. receive one or more data feeds.); use the received one or more data feeds and the received monitoring data to generate combined launch data indicative of (see [0020]-[0025] and Figs 6-7 where a launch ephemeris files are read during data processing to determine geometrical parameters of a launch window and protected satellite file and perigee/apogee filter are used during main processing to determine candidate crossing times and times of minimum distance between the launch vehicle and satellite, i.e. using one or more received data feeds to generate launch data indicative of predicted conditions along the proposed launch trajectory.); analyze the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory (see [0021], [0025], and Fig. 7 where launch collision avoidance methodology is configured to find all clear times within the launch window through determining time of minimum distance between the launch vehicle and the satellite, compute and compare collision probability with a risk threshold, and store window risk times if the probability is higher than the threshold, and then unsafe and safe launch times are determined and generate a launch collision avoidance report that includes closure time, offending satellite, and risk level, i.e. analyze combined launch data based on condition-based launch criteria comprising distance and risk thresholds to identify clear launch times within a defined time span during which the collision avoidance criteria are met along a proposed launch trajectory; further, see [0063]-[0064] where Newton’s iterative method is used to determine times when a launch vehicle and satellite come closest through a separation distance function dependent on satellite prediction time and launch time, i.e. determine launch opportunities based on changing collision conditions rather than predetermined launch times, which are non-linear, non-periodic and discontinuous clear launch windows.); and output an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle (see [0022], [0025] and Fig. 7 where launch collision avoidance software generates launch collision avoidance reports, indications, commands and other inputs, signals or the like that can be used to make decisions regarding and control launch events which a proposed launch time is determined to be unsafe or safe depending on unacceptable and acceptable probability of collision with a satellite, i.e. outputting indications of identified launch windows as opportunities for the launch vehicle; see further in [0025] where main processing generates launch collision avoidance report that includes closure time, offending satellite, and risk level, i.e. outputting launch opportunity indications based on the proposed launch vehicle trajectory.). Hoots does not teach: receive monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; and use the received one or more data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. However, Hushing teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042]-[0042], [0051]-[0052] and Fig. 4). Note also from the abstract that the received telemetry data is from pre-flight and in-flight sensors, i.e. receiving monitoring data from plurality of sensors. It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data to determine clear and unsafe launch times based on collision risk of Hoots by incorporating the teachings of Hushing, such that telemetry data from ground station and launch vehicle sources, in which uses sensors to monitor, are processed by decommutating serial data streams and extracting information including wind velocity, temperature, and vehicle velocity, and combined with launch ephemeris and satellite data to determine clear launch time based on current operating conditions and predicted collision risks, i.e. receiving monitoring data from sensors located at the launch site and on the launch vehicle and using the received data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 2, modified Hoots in view of Hushing teaches the space launch service platform computing device of claim 1, wherein the at least one processor is configured to (see Hoots [0022] and Fig. 5 in general as shown above in claim 1.): receive the one or more data feeds by receiving at least one data feed from a satellite catalog (see [0024]-[0025] and Figs 6-7 where during main processing, inputs that includes satellite protected file are accessed and satellite data are analyzed using perigee apogee filter, i.e. receive data feeds from a satellite catalog.). Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite catalog and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042]-[0042], [0051]-[0052] and Fig. 4). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data to determine clear and unsafe launch times based on collision risk of Hoots by incorporating the teachings of Hushing, such that telemetry data from ground station and launch vehicle sources, in which uses sensors to monitor, are processed by decommutating serial data streams and extracting information including wind velocity, temperature, and vehicle velocity, and combined with launch ephemeris and satellite data, i.e. data from a satellite catalog, to determine clear launch time based on current operating conditions and predicted collision risks, i.e. receiving one or more data feed from a satellite catalog and using one or more received data from the satellite catalog and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 6, modified Hoots in view of Hushing teaches the space launch service platform computing device of claim 1, wherein the at least one processor is configured to (see Hoots [0022] and Fig. 5 in general as shown above in claim 1.): Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042]-[0042], [0051]-[0052] and Fig. 4). Note also that Hushing teaches real-time strip charts for monitoring wind velocity, wind direction, and ambient temperature, i.e. receiving plurality of data feed from a weather monitoring system (see [0057] and Fig. 5). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that received information including wind velocity, wind direction, ambient temperature, and vehicle velocity, is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear launch time based on current weather conditions and predicted collision risks, i.e. receiving one or more data feed from a weather monitoring system and using one or more received data from the weather monitoring system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry and information of wind velocity, wind direction, and ambient temperature is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 7, modified Hoots in view of Hushing teaches the space launch service platform computing device of claim 1, wherein the at least one processor is configured to (see Hoots [0022] and Fig. 5 in general as shown above in claim 1.): receive the one or more data feeds by receiving at least one data feed from a range monitoring system (see Hushing [0036]-[0040] and Figs 1-2 where a data acquisition facility is configured to receive telemetry from a rocket and generates range IRIG-B formatted GMT and range formatted countdown clock signals transmitted over communications network to an operational site having an automated data monitoring system (ADMS), in which telemetry information transmitted from the rocket after it has launched is received by radio antenna, directly or through satellite, and transmitted over communications network to operational site, i.e. receiving at least one data feed from a range monitoring system, in which Applicant’s Specification in [0003] describes a launch range as the infrastructure supporting an in-flight launch vehicle where Hushing’s ground based data and communication facilities receive and transmit telemetry from a racket after launch consistent with the specification.). Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042]-[0042], [0051]-[0052] and Fig. 4). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that telemetry information transmitted from rocket over communications network, together with data received from IRIG-B GMT source, countdown source, and telemetry sources, is processed by telemetry processor is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear and unsafe launch times based on current conditions and predicted collision risks, i.e. receiving one or more data feed from a range monitoring system and using one or more received data from range monitoring system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have a telemetry processing system receiving telemetry and timing signals from various sources is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 9, modified Hoots in view of Hushing teaches the space launch service platform computing device of claim 1, wherein the at least one processor is configured to (see Hoots [0022] and Fig. 5 in general as shown above in claim 1.): Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions by receiving telemetry data (see [0039]-[0042]-[0042], [0051]-[0052] and Fig. 4). Note also from the abstract that the received telemetry data is from pre-flight and in-flight sensors, i.e. receiving monitoring data from plurality of sensors. It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that received information including wind velocity, wind direction, ambient temperature, and vehicle velocity, is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear launch time based on current operating conditions and predicted collision risks, i.e. receiving monitoring data from plurality of sensors by receiving telemetry data and use the received one or more data feeds and the telemetry data to generate combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. The motivation to have real-time monitoring and processing of telemetry data from launch vehicles and ground stations is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 10, modified Hoots in view of Hushing teaches the space launch service platform computing device of claim 1, wherein the at least one processor is configured to (see Hoots [0022] and Fig. 5 in general as shown above in claim 1.): Hoots also teaches a launch collision avoidance methodology configured to find all clear times within a launch window for the launch trajectory or trajectories, in which launch collision avoidance software executed by a computer generates reports and indications used to make decisions regarding launch events, including determining that a proposed launch time is unsafe because of an unacceptably high probability of collision with satellite and that a slightly later launch time is safe because of an acceptably low probability of collision, i.e. outputting potential launch scenarios to assess different launch trajectories and conditions before making a final launch decision (see [0021]-[0022] and Fig. 5). Note also that in [0025] and Fig. 7 that Hoots teaches a main processing that computes a collision probability and determines whether the collision probability is higher than a risk threshold, stores window risk times, and determines unsafe launch times used to generate launch collision avoidance report with closure time, offending satellite, and risk level, i.e. outputting launch window data and probabilistic assessment of collision risk. Hushing further teaches a real-time schematic display in which a graphical representation of an orbital track of a launch vehicle is imposed on a map, in which animation of the orbital track is created based on processed telemetry data, i.e. outputting visual representations of a launch-vehicle trajectory (see [0073] and Fig. 13). Hushing also teaches a display format database that includes display templates that employ real time strip chart, change of state, redline monitor, tabular displays, and schematic displays in which charts and graphs having real-time or archive data may be overlaid and transmitted to a graphical user interface (GUI), measurement samples are displayed against time and may be overlaid with other measurements for waveform comparison, and an ADMS tabular display shows current values of user specified measurements in digital form with upper and lower reference limits that cause the displayed text to change color when a measurement exceeds a user specified limit, i.e. outputting visual representations on a graphical user interface in a timeline format with overlaid condition-based criteria assessments (see [0043], [0057], and [0069]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times, compute collision probabilities, store window risk times, and generate launch collision avoidance report containing closure time, offending satellite, and risk level of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that proposed launch times, launch trajectories, collision probabilities, and risk levels are presented together with real-time telemetry measurements using a GUI having a real-time schematic display of the launch vehicle’s orbital track, strip charts, tabular displays, measurements displayed against time and overlaid for comparison, and upper and lower reference limits, which allows for assessing launch conditions and safety of launch opportunities, i.e. outputting potential launch scenarios based on the combined launch data so as to allow for operators to visualize and asses different launch trajectories and conditions before making a final launch decision, outputting visual representations on a GUI that displays launch window in a timeline format with overlaid condition-based criteria assessments, and outputting probabilistic assessments indicating the likelihood of identified clear launch windows remaining viable up to the point of launch. The motivation to have real-time graphical displays of launch vehicle telemetry with customizable time scales and overlaid measurements is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 11, Hoots teaches a method for determining launch opportunities for a space vehicle from a terrestrial launch point (see [0020]-[0022] in general where launch ephemeris begins on the surface of the Earth and a launch collision avoidance software is executed by a computer to determine safe launch time.), the method comprising: receiving, by a computing device, a one or more data feeds (see [0024]-[0025] and Figs 6-7 where inputs are accessed by a computer, and the inputs include launch window start time, end time, risk threshold, distance threshold, file name of launch ephemeris, and file name of protected satellites. The launch ephemeris files are read during data processing and protected satellite data is accessed during main processing, i.e. receive one or more data feeds.); using, by the computing device, the received one or more data feeds and the received monitoring data to generate combined launch data indicative of (see [0020]-[0025] and Figs 6-7 where a launch ephemeris files are read during data processing to determine geometrical parameters of a launch window and protected satellite file and perigee/apogee filter are used during main processing to determine candidate crossing times and times of minimum distance between the launch vehicle and satellite, i.e. using one or more received data feeds to generate launch data indicative of predicted conditions along the proposed launch trajectory.); analyzing, by the computing device, the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory (see [0021], [0025], and Fig. 7 where launch collision avoidance methodology is configured to find all clear times within the launch window through determining time of minimum distance between the launch vehicle and the satellite, compute and compare collision probability with a risk threshold, and store window risk times if the probability is higher than the threshold, and then unsafe and safe launch times are determined and generate a launch collision avoidance report that includes closure time, offending satellite, and risk level, i.e. analyze combined launch data based on condition-based launch criteria comprising distance and risk thresholds to identify clear launch times within a defined time span during which the collision avoidance criteria are met along a proposed launch trajectory; further, see [0063]-[0064] where Newton’s iterative method is used to determine times when a launch vehicle and satellite come closest through a separation distance function dependent on satellite prediction time and launch time, i.e. determine launch opportunities based on changing collision conditions rather than predetermined launch times, which are non-linear, non-periodic and discontinuous clear launch windows.); and outputting, by the computing device, an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle (see [0022], [0025] and Fig. 7 where launch collision avoidance software generates launch collision avoidance reports, indications, commands and other inputs, signals or the like that can be used to make decisions regarding and control launch events which a proposed launch time is determined to be unsafe or safe depending on unacceptable and acceptable probability of collision with a satellite, i.e. outputting indications of identified launch windows as opportunities for the launch vehicle; see further in [0025] where main processing generates launch collision avoidance report that includes closure time, offending satellite, and risk level, i.e. outputting launch opportunity indications based on the proposed launch vehicle trajectory.). Hoots does not teach: receiving, by the computing device, monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; and using, by the computing device, the received one or more data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. However, Hushing teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Note also from the abstract that the received telemetry data is from pre-flight and in-flight sensors, i.e. receiving monitoring data from plurality of sensors. It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data to determine clear and unsafe launch times based on collision risk of Hoots by incorporating the teachings of Hushing, such that telemetry data from ground station and launch vehicle sources, in which uses sensors to monitor, are processed by decommutating serial data streams and extracting information including wind velocity, temperature, and vehicle velocity, and combined with launch ephemeris and satellite data to determine clear launch time based on current operating conditions and predicted collision risks, i.e. receiving monitoring data from sensors located at the launch site and on the launch vehicle and using the received data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. Regarding claim 12, modified Hoots in view of Hushing teaches the method of claim 11, wherein: receiving the one or more data feeds comprises receiving at least one data feed from a satellite catalog (see [0024]-[0025] and Figs 6-7 where during main processing, inputs that includes satellite protected file are accessed and satellite data are analyzed using perigee apogee filter, i.e. receive data feeds from a satellite catalog.). Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite catalog and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data to determine clear and unsafe launch times based on collision risk of Hoots by incorporating the teachings of Hushing, such that telemetry data from ground station and launch vehicle sources, in which uses sensors to monitor, are processed by decommutating serial data streams and extracting information including wind velocity, temperature, and vehicle velocity, and combined with launch ephemeris and satellite data, i.e. data from a satellite catalog, to determine clear launch time based on current operating conditions and predicted collision risks, i.e. receiving one or more data feed from a satellite catalog and using one or more received data from the satellite catalog and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 16, modified Hoots in view of Hushing teaches the method of claim 11, wherein: Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Note also that Hushing teaches real-time strip charts for monitoring wind velocity, wind direction, and ambient temperature, i.e. receiving one or more data feed from a weather monitoring system (see [0057] and Fig. 5). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that received information including wind velocity, wind direction, ambient temperature, and vehicle velocity, is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear launch time based on current weather conditions and predicted collision risks, i.e. receiving one or more data feed from a weather monitoring system and using one or more received data from the weather monitoring system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry and information of wind velocity, wind direction, and ambient temperature is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 17, modified Hoots in view of Hushing teaches the method of claim 11, wherein: receiving the one or more data feeds comprises receiving at least one data feed from a range monitoring system (see Hushing [0036]-[0040] and Figs 1-2 where a data acquisition facility is configured to receive telemetry from a rocket and generates range IRIG-B formatted GMT and range formatted countdown clock signals transmitted over communications network to an operational site having an automated data monitoring system (ADMS), in which telemetry information transmitted from the rocket after it has launched is received by radio antenna, directly or through satellite, and transmitted over communications network to operational site, i.e. receiving at least one data feed from a range monitoring system, in which Applicant’s Specification in [0003] describes a launch range as the infrastructure supporting an in-flight launch vehicle where Hushing’s ground based data and communication facilities receive and transmit telemetry from a racket after launch consistent with the specification.). Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that telemetry information transmitted from rocket over communications network, together with data received from IRIG-B GMT source, countdown source, and telemetry sources, is processed by telemetry processor is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear and unsafe launch times based on current conditions and predicted collision risks, i.e. receiving one or more data feed from a range monitoring system and using one or more received data from range monitoring system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have a telemetry processing system receiving telemetry and timing signals from various sources is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 19, modified Hoots in view of Hushing teaches the method of claim 11, wherein: Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions by receiving telemetry data (see [0039]-[0042], [0051]-[0052] and Fig. 4). Note also from the abstract that the received telemetry data is from pre-flight and in-flight sensors, i.e. receiving monitoring data from plurality of sensors. It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that received information including wind velocity, wind direction, ambient temperature, and vehicle velocity, is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear launch time based on current operating conditions and predicted collision risks, i.e. receiving monitoring data from plurality of sensors by receiving telemetry data and use the received one or more data feeds and the telemetry data to generate combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. The motivation to have real-time monitoring and processing of telemetry data from launch vehicles and ground stations is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 20, modified Hoots in view of Hushing teaches the method of claim 11, wherein: Hoots also teaches a launch collision avoidance methodology configured to find all clear times within a launch window for the launch trajectory or trajectories, in which launch collision avoidance software executed by a computer generates reports and indications used to make decisions regarding launch events, including determining that a proposed launch time is unsafe because of an unacceptably high probability of collision with satellite and that a slightly later launch time is safe because of an acceptably low probability of collision, i.e. outputting potential launch scenarios to assess different launch trajectories and conditions before making a final launch decision (see [0021]-[0022] and Fig. 5). Note also that in [0025] and Fig. 7 that Hoots teaches a main processing that computes a collision probability and determines whether the collision probability is higher than a risk threshold, stores window risk times, and determines unsafe launch times used to generate launch collision avoidance report with closure time, offending satellite, and risk level, i.e. outputting launch window data and probabilistic assessment of collision risk. Hushing further teaches a real-time schematic display in which a graphical representation of an orbital track of a launch vehicle is imposed on a map, in which animation of the orbital track is created based on processed telemetry data, i.e. outputting visual representations of a launch-vehicle trajectory (see [0073] and Fig. 13). Hushing also teaches a display format database that includes display templates that employ real time strip chart, change of state, redline monitor, tabular displays, and schematic displays in which charts and graphs having real-time or archive data may be overlaid and transmitted to a graphical user interface (GUI), measurement samples are displayed against time and may be overlaid with other measurements for waveform comparison, and an ADMS tabular display shows current values of user specified measurements in digital form with upper and lower reference limits that cause the displayed text to change color when a measurement exceeds a user specified limit, i.e. outputting visual representations on a graphical user interface in a timeline format with overlaid condition-based criteria assessments (see [0043], [0057], and [0069]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times, compute collision probabilities, store window risk times, and generate launch collision avoidance report containing closure time, offending satellite, and risk level of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that proposed launch times, launch trajectories, collision probabilities, and risk levels are presented together with real-time telemetry measurements using a GUI having a real-time schematic display of the launch vehicle’s orbital track, strip charts, tabular displays, measurements displayed against time and overlaid for comparison, and upper and lower reference limits, which allows for assessing launch conditions and safety of launch opportunities, i.e. outputting potential launch scenarios based on the combined launch data so as to allow for operators to visualize and asses different launch trajectories and conditions before making a final launch decision, outputting visual representations on a GUI that displays launch window in a timeline format with overlaid condition-based criteria assessments, and outputting probabilistic assessments indicating the likelihood of identified clear launch windows remaining viable up to the point of launch. The motivation to have real-time graphical displays of launch vehicle telemetry with customizable time scales and overlaid measurements is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 21, Hoots teaches a non-transitory computer-readable storage medium having stored thereon processor-executable software instructions configured to cause at least one processor in a computing system perform operations for determining launch opportunities for a space vehicle from a terrestrial launch point (see [0022] and Fig. 5 in general where a launch collision avoidance system includes a computer, which necessarily includes storage, that includes a processor to execute launch collision avoidance software and generate launch collision avoidance reports, indications, commands, and other inputs, signals or the like that can be used to make decisions regarding and control launch events. Note also in [0020] where launch ephemeris begins on the surface of the Earth.), the operations comprising: receiving a one or more data (see [0024]-[0025] and Figs 6-7 where inputs are accessed by a computer, and the inputs include launch window start time, end time, risk threshold, distance threshold, file name of launch ephemeris, and file name of protected satellites. The launch ephemeris files are read during data processing and protected satellite data is accessed during main processing, i.e. receive one or more data feeds.); using the received one or more data feeds and the received monitoring data to generate combined launch data indicative of (see [0020]-[0025] and Figs 6-7 where a launch ephemeris files are read during data processing to determine geometrical parameters of a launch window and protected satellite file and perigee/apogee filter are used during main processing to determine candidate crossing times and times of minimum distance between the launch vehicle and satellite, i.e. using one or more received data feeds to generate launch data indicative of predicted conditions along the proposed launch trajectory.); analyzing the combined launch data based on condition-based launch criteria to identify two or more non-linear non-periodic and discontinuous clear launch windows within a defined time span, wherein each launch window represents a time period during which the condition-based launch criteria are estimated to be met for the launch vehicle, at and around the launch site, and along the proposed launch trajectory (see [0021], [0025], and Fig. 7 where launch collision avoidance methodology is configured to find all clear times within the launch window through determining time of minimum distance between the launch vehicle and the satellite, compute and compare collision probability with a risk threshold, and store window risk times if the probability is higher than the threshold, and then unsafe and safe launch times are determined and generate a launch collision avoidance report that includes closure time, offending satellite, and risk level, i.e. analyze combined launch data based on condition-based launch criteria comprising distance and risk thresholds to identify clear launch times within a defined time span during which the collision avoidance criteria are met along a proposed launch trajectory; further, see [0063]-[0064] where Newton’s iterative method is used to determine times when a launch vehicle and satellite come closest through a separation distance function dependent on satellite prediction time and launch time, i.e. determine launch opportunities based on changing collision conditions rather than predetermined launch times, which are non-linear, non-periodic and discontinuous clear launch windows.); and outputting an indication of the identified non-linear non-periodic and discontinuous clear launch windows as launch opportunities tailored to the launch vehicle (see [0022], [0025] and Fig. 7 where launch collision avoidance software generates launch collision avoidance reports, indications, commands and other inputs, signals or the like that can be used to make decisions regarding and control launch events which a proposed launch time is determined to be unsafe or safe depending on unacceptable and acceptable probability of collision with a satellite, i.e. outputting indications of identified launch windows as opportunities for the launch vehicle; see further in [0025] where main processing generates launch collision avoidance report that includes closure time, offending satellite, and risk level, i.e. outputting launch opportunity indications based on the proposed launch vehicle trajectory.). Hoots does not teach: receiving monitoring data from a plurality of sensors located at a launch site and on a launch vehicle; and using the received one or more data feeds and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. However, Hushing teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Note also from the abstract that the received telemetry data is from pre-flight and in-flight sensors, i.e. receiving monitoring data from plurality of sensors. It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data to determine clear and unsafe launch times based on collision risk of Hoots by incorporating the teachings of Hushing, such that telemetry data from ground station and launch vehicle sources, in which uses sensors to monitor, are processed by decommutating serial data streams and extracting information including wind velocity, temperature, and vehicle velocity, and combined with launch ephemeris and satellite data to determine clear launch time based on current operating conditions and predicted collision risks, i.e. receiving monitoring data from sensors located at the launch site and on the launch vehicle and using the received data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 22, modified Hoots in view of Hushing teaches the non-transitory computer-readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the at least one processor to perform operations (see Hoots [0022] and Fig. 5 in general as shown above in claim 21.) such that: receiving the one or more data feeds comprises receiving at least one data feed from a satellite catalog (see [0024]-[0025] and Figs 6-7 where during main processing, inputs that includes satellite protected file are accessed and satellite data are analyzed using perigee apogee filter, i.e. receive data feeds from a satellite catalog.). Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite catalog and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data to determine clear and unsafe launch times based on collision risk of Hoots by incorporating the teachings of Hushing, such that telemetry data from ground station and launch vehicle sources, in which uses sensors to monitor, are processed by decommutating serial data streams and extracting information including wind velocity, temperature, and vehicle velocity, and combined with launch ephemeris and satellite data, i.e. data from a satellite catalog, to determine clear launch time based on current operating conditions and predicted collision risks, i.e. receiving one or more data feed from a satellite catalog and using one or more received data from the satellite catalog and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 26, modified Hoots in view of Hushing teaches the non-transitory computer-readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the at least one processor to perform operations (see Hoots [0022] and Fig. 5 in general as shown above in claim 21.) such that: Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Note also that Hushing teaches real-time strip charts for monitoring wind velocity, wind direction, and ambient temperature, i.e. receiving one or more data feed from a weather monitoring system (see [0057] and Fig. 5). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that received information including wind velocity, wind direction, ambient temperature, and vehicle velocity, is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear launch time based on current weather conditions and predicted collision risks, i.e. receiving one or more data feed from a weather monitoring system and using one or more received data from the weather monitoring system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry and information of wind velocity, wind direction, and ambient temperature is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 27, modified Hoots in view of Hushing teaches the non-transitory computer-readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the at least one processor to perform operations (see Hoots [0022] and Fig. 5 in general as shown above in claim 21.) such that: receiving the one or more data feeds comprises receiving at least one data feed from a range monitoring system (see Hushing [0036]-[0040] and Figs 1-2 where a data acquisition facility is configured to receive telemetry from a rocket and generates range IRIG-B formatted GMT and range formatted countdown clock signals transmitted over communications network to an operational site having an automated data monitoring system (ADMS), in which telemetry information transmitted from the rocket after it has launched is received by radio antenna, directly or through satellite, and transmitted over communications network to operational site, i.e. receiving at least one data feed from a range monitoring system, in which Applicant’s Specification in [0003] describes a launch range as the infrastructure supporting an in-flight launch vehicle where Hushing’s ground based data and communication facilities receive and transmit telemetry from a racket after launch consistent with the specification.). Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that telemetry information transmitted from rocket over communications network, together with data received from IRIG-B GMT source, countdown source, and telemetry sources, is processed by telemetry processor is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear and unsafe launch times based on current conditions and predicted collision risks, i.e. receiving one or more data feed from a range monitoring system and using one or more received data from range monitoring system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have a telemetry processing system receiving telemetry and timing signals from various sources is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 29, modified Hoots in view of Hushing teaches the non-transitory computer-readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the at least one processor to perform operations (see Hoots [0022] and Fig. 5 in general as shown above in claim 21.) such that: Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions by receiving telemetry data (see [0039]-[0042], [0051]-[0052] and Fig. 4). Note also from the abstract that the received telemetry data is from pre-flight and in-flight sensors, i.e. receiving monitoring data from plurality of sensors. It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that received information including wind velocity, wind direction, ambient temperature, and vehicle velocity, is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear launch time based on current operating conditions and predicted collision risks, i.e. receiving monitoring data from plurality of sensors by receiving telemetry data and use the received one or more data feeds and the telemetry data to generate combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. The motivation to have real-time monitoring and processing of telemetry data from launch vehicles and ground stations is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). Regarding claim 30, modified Hoots in view of Hushing teaches the non-transitory computer-readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the at least one processor to perform operations (see Hoots [0022] and Fig. 5 in general as shown above in claim 21.) such that: Hoots also teaches a launch collision avoidance methodology configured to find all clear times within a launch window for the launch trajectory or trajectories, in which launch collision avoidance software executed by a computer generates reports and indications used to make decisions regarding launch events, including determining that a proposed launch time is unsafe because of an unacceptably high probability of collision with satellite and that a slightly later launch time is safe because of an acceptably low probability of collision, i.e. outputting potential launch scenarios to assess different launch trajectories and conditions before making a final launch decision (see [0021]-[0022] and Fig. 5). Note also that in [0025] and Fig. 7 that Hoots teaches a main processing that computes a collision probability and determines whether the collision probability is higher than a risk threshold, stores window risk times, and determines unsafe launch times used to generate launch collision avoidance report with closure time, offending satellite, and risk level, i.e. outputting launch window data and probabilistic assessment of collision risk. Hushing further teaches a real-time schematic display in which a graphical representation of an orbital track of a launch vehicle is imposed on a map, in which animation of the orbital track is created based on processed telemetry data, i.e. outputting visual representations of a launch-vehicle trajectory (see [0073] and Fig. 13). Hushing also teaches a display format database that includes display templates that employ real time strip chart, change of state, redline monitor, tabular displays, and schematic displays in which charts and graphs having real-time or archive data may be overlaid and transmitted to a graphical user interface (GUI), measurement samples are displayed against time and may be overlaid with other measurements for waveform comparison, and an ADMS tabular display shows current values of user specified measurements in digital form with upper and lower reference limits that cause the displayed text to change color when a measurement exceeds a user specified limit, i.e. outputting visual representations on a graphical user interface in a timeline format with overlaid condition-based criteria assessments (see [0043], [0057], and [0069]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times, compute collision probabilities, store window risk times, and generate launch collision avoidance report containing closure time, offending satellite, and risk level of modified Hoots in view of Hushing by incorporating further teaching of Hushing, such that proposed launch times, launch trajectories, collision probabilities, and risk levels are presented together with real-time telemetry measurements using a GUI having a real-time schematic display of the launch vehicle’s orbital track, strip charts, tabular displays, measurements displayed against time and overlaid for comparison, and upper and lower reference limits, which allows for assessing launch conditions and safety of launch opportunities, i.e. outputting potential launch scenarios based on the combined launch data so as to allow for operators to visualize and asses different launch trajectories and conditions before making a final launch decision, outputting visual representations on a GUI that displays launch window in a timeline format with overlaid condition-based criteria assessments, and outputting probabilistic assessments indicating the likelihood of identified clear launch windows remaining viable up to the point of launch. The motivation to have real-time graphical displays of launch vehicle telemetry with customizable time scales and overlaid measurements is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). 6. Claims 3, 13, and 23 are rejected under pre-35 USC 103 a being unpatentable over Hoots in view of Hushing in further view of Tanygin et al. (US 20130024102A1) Regarding claim 3, modified Hoots in view of Hushing teaches the space launch service platform computing device of claim 1, wherein the at least one processor is configured to (see Hoots [0022] and Fig. 5 in general as shown above in claim 1.). Hoots teaches where during main processing, inputs that includes satellite protected file are accessed and satellite data are analyzed using perigee apogee filter, i.e. receive data feeds from a satellite catalog, and that launch collision avoidance methodology is applicable to resident satellites and other space objects, including debris, i.e. data regarding orbital debris (see [0021], [0024]-[0025], and Fig. 7). Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite catalog and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receive the one or more data feeds by receiving at least one data feed from an orbital debris catalog; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the at least one data feed from the orbital debris catalog and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Tanygin teaches launch calculator that retrieves information from a space object catalog that comprises catalog and ephemeris data associated with objects that includes other satellites and debris (see Fig. 11 and [0031]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Tanygin such that the launch processor retrieves catalog and ephemeris data associated with debris and other space objects from space object catalog and uses the retrieved data with launch ephemeris to determine collision conditions along the proposed launch trajectory, i.e. receiving one or more data feed from an orbital debris catalog and using one or more received data from the orbital debris catalog and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). The motivation to have catalog and ephemeris data from the space object catalog that includes debris is that, as indicated by Tanygin, this would allow for accurate and fast determination of close approaches between a launch vehicle and other objects in space and identify blackout intervals within a launch window in a small number of runs or a single run to reduce number of computations and latency of analyzing multiple launch trajectories (see [0014]-[0024]). Regarding claim 13, modified Hoots in view of Hushing teaches the method of claim 11, wherein: Hoots teaches where during main processing, inputs that includes satellite protected file are accessed and satellite data are analyzed using perigee apogee filter, i.e. receive data feeds from a satellite catalog, and that launch collision avoidance methodology is applicable to resident satellites and other space objects, including debris, i.e. data regarding orbital debris (see [0021], [0024]-[0025], and Fig. 7). Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite catalog and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receiving the one or more data feeds comprises receiving at least one data feed from an orbital debris catalog; and using the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle comprises using the at least one data feed from the orbital debris catalog and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Tanygin teaches launch calculator that retrieves information from a space object catalog that comprises catalog and ephemeris data associated with objects that includes other satellites and debris (see Fig. 11 and [0031]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Tanygin such that the launch processor retrieves catalog and ephemeris data associated with debris and other space objects from space object catalog and uses the retrieved data with launch ephemeris to determine collision conditions along the proposed launch trajectory, i.e. receiving one or more data feed from an orbital debris catalog and using one or more received data from the orbital debris catalog and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). The motivation to have catalog and ephemeris data from the space object catalog that includes debris is that, as indicated by Tanygin, this would allow for accurate and fast determination of close approaches between a launch vehicle and other objects in space and identify blackout intervals within a launch window in a small number of runs or a single run to reduce number of computations and latency of analyzing multiple launch trajectories (see [0014]-[0024]). Regarding claim 23, modified Hoots in view of Hushing teaches the non-transitory computer-readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the at least one processor to perform operations (see Hoots [0022] and Fig. 5 in general as shown above in claim 21.) such that: Hoots teaches where during main processing, inputs that includes satellite protected file are accessed and satellite data are analyzed using perigee apogee filter, i.e. receive data feeds from a satellite catalog, and that launch collision avoidance methodology is applicable to resident satellites and other space objects, including debris, i.e. data regarding orbital debris (see [0021], [0024]-[0025], and Fig. 7). Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite catalog and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receiving the one or more data feeds comprises receiving at least one data feed from an orbital debris catalog; and using the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle comprises using the at least one data feed from the orbital debris catalog and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Tanygin teaches launch calculator that retrieves information from a space object catalog that comprises catalog and ephemeris data associated with objects that includes other satellites and debris (see Fig. 11 and [0031]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Tanygin such that the launch processor retrieves catalog and ephemeris data associated with debris and other space objects from space object catalog and uses the retrieved data with launch ephemeris to determine collision conditions along the proposed launch trajectory, i.e. receiving one or more data feed from an orbital debris catalog and using one or more received data from the orbital debris catalog and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). The motivation to have catalog and ephemeris data from the space object catalog that includes debris is that, as indicated by Tanygin, this would allow for accurate and fast determination of close approaches between a launch vehicle and other objects in space and identify blackout intervals within a launch window in a small number of runs or a single run to reduce number of computations and latency of analyzing multiple launch trajectories (see [0014]-[0024]). 7. Claims 4, 14, and 24 are rejected under pre-35 USC 103 a being unpatentable over Hoots in view of Hushing in further view of Duan et al. (“ADS-B Feasibility Study for Commercial Space Flight operations”, https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5655472). Regarding claim 4, modified Hoots in view of Hushing teaches the space launch service platform computing device of claim 1, wherein the at least one processor is configured to (see Hoots [0022] and Fig. 5 in general as shown above in claim 1.): Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receive the one or more data feeds by receiving at least one data feed from a national airspace tracking system; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the at least one data feed from the national airspace tracking system and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Duan teaches Automatic Dependent Surveillance-Broadcast (ADS-B) system that provide surveillance capability within the National Airspace System (NAS), in which aircraft, ground vehicles and ground stations equipped with ADS-B transceivers exchange information including position, velocity, intent, and aircraft identification directly through an ADS-B data link, i.e. receiving one or more data feeds from a national airspace tracking system (see 3.A.1-3). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Duan, such that information including position, velocity, intent, and aircraft identification exchanged through an ADS-B data link within the NAS, i.e. national airspace tracking system, is used with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear and unsafe launch times based on air traffic information, current conditions, and predicted collision risks, i.e. receiving one or more data feed from a national airspace tracking system and using one or more received data from the national airspace tracking system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). The motivation to have an ADS-B system providing surveillance services within the NAS, i.e. data from national airspace tracking system, is that, as indicated by Duan, this would allow for minimized impact of a commercial space flight operations on the NAS (National Airspace System) and allow for more commercial space transportations that will be integrated seamlessly with conventional aviation operations (see [3.A.1-1]). Regarding claim 14, modified Hoots in view of Hushing teaches the method of claim 11, wherein: Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receiving the one or more data feeds comprises receiving at least one data feed from a national airspace tracking system; and using the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle comprises using the at least one data feed from the national airspace tracking system and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Duan teaches Automatic Dependent Surveillance-Broadcast (ADS-B) system that provide surveillance capability within the National Airspace System (NAS), in which aircraft, ground vehicles and ground stations equipped with ADS-B transceivers exchange information including position, velocity, intent, and aircraft identification directly through an ADS-B data link, i.e. receiving one or more data feeds from a national airspace tracking system (see 3.A.1-3). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Duan, such that information including position, velocity, intent, and aircraft identification exchanged through an ADS-B data link within the NAS, i.e. national airspace tracking system, is used with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear and unsafe launch times based on air traffic information, current conditions, and predicted collision risks, i.e. receiving one or more data feed from a national airspace tracking system and using one or more received data from the national airspace tracking system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). The motivation to have an ADS-B system providing surveillance services within the NAS, i.e. data from national airspace tracking system, is that, as indicated by Duan, this would allow for minimized impact of a commercial space flight operations on the NAS (National Airspace System) and allow for more commercial space transportations that will be integrated seamlessly with conventional aviation operations (see [3.A.1-1]). Regarding claim 24, modified Hoots in view of Hushing teaches the non-transitory computer-readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the at least one processor to perform operations (see Hoots [0022] and Fig. 5 in general as shown above in claim 21.) such that: Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receiving the one or more data feeds comprises receiving at least one data feed from a national airspace tracking system; and using the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle comprises using the at least one data feed from the national airspace tracking system and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Duan teaches Automatic Dependent Surveillance-Broadcast (ADS-B) system that provide surveillance capability within the National Airspace System (NAS), in which aircraft, ground vehicles and ground stations equipped with ADS-B transceivers exchange information including position, velocity, intent, and aircraft identification directly through an ADS-B data link, i.e. receiving one or more data feeds from a national airspace tracking system (see 3.A.1-3). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Duan, such that information including position, velocity, intent, and aircraft identification exchanged through an ADS-B data link within the NAS, i.e. national airspace tracking system, is used with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear and unsafe launch times based on air traffic information, current conditions, and predicted collision risks, i.e. receiving one or more data feed from a national airspace tracking system and using one or more received data from the national airspace tracking system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have an automated monitoring system for real-time launch vehicle and ground-station telemetry is that, as indicated by Hushing, it provides rapid access to and accurate assessment of vehicle test data, real-time and historical visibility of telemetry data, analysis of out of family conditions, and data trending, which is providing processing for a full bandwidth of data as well as visibility of every measurement sample in the telemetry data stream (see [0006]-[0007]). The motivation to have an ADS-B system providing surveillance services within the NAS, i.e. data from national airspace tracking system, is that, as indicated by Duan, this would allow for minimized impact of a commercial space flight operations on the NAS (National Airspace System) and allow for more commercial space transportations that will be integrated seamlessly with conventional aviation operations (see [3.A.1-1]). 8. Claims 5, 15, and 25 are rejected under pre-35 USC 103 a being unpatentable over Hoots in view of Hushing in further view of Smith (“Wallops Ship Surveillance System”, https://ntrs.nasa.gov/api/citations/20110012230/downloads/20110012230.pdf). Regarding claim 5, modified Hoots in view of Hushing teach the space launch service platform computing device of claim 1, wherein the at least one processor is configured to (see Hoots [0022] and Fig. 5 in general as shown above in claim 1.): Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receive the one or more data feeds by receiving at least one data feed from a maritime tracking system; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the at least one data feed from the maritime tracking system and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Smith teaches Wallops Ship Surveillance Software, which is a day-of-launch risk analysis tool for spaceport activities, where it calculates impact probabilities and displays ship locations relative to boundary lines for safe-for-launch conditions, in which official ship information and risk analysis are shared with other networked workstations, i.e. receiving one or more data feeds from a maritime tracking system and processing the information for launch safety analysis (see [pg 9]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Smith, such that official ship information and risk analysis for spaceport activities are shared and used to display ship locations relative to boundary lines and calculate impact probabilities for possible flight trajectories, and the ship information is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear and unsafe launch times based on ship locations, current conditions, and predicted collision risks, i.e. receiving one or more data feed from a maritime tracking system and using one or more received data from maritime tracking system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have Wallops Ship Surveillance System for day-of-launch risk analysis is that, as indicated by Smith, this would enable rapid analysis of possible flight paths to preclude the need to cancel launches and allow execution of launches in a timely manner, which prevents falsely report safe-for-launch condition while having low cost and large customer base elements (see [pg 9]). Regarding claim 15, modified Hoots in view of Hushing teaches the method of claim 11, wherein: Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receiving the one or more data feeds comprises receiving at least one data feed from a maritime tracking system; and using the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle comprises using the at least one data feed from the maritime tracking system and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Smith teaches Wallops Ship Surveillance Software, which is a day-of-launch risk analysis tool for spaceport activities, where it calculates impact probabilities and displays ship locations relative to boundary lines for safe-for-launch conditions, in which official ship information and risk analysis are shared with other networked workstations, i.e. receiving one or more data feeds from a maritime tracking system and processing the information for launch safety analysis (see [pg 9]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Smith, such that official ship information and risk analysis for spaceport activities are shared and used to display ship locations relative to boundary lines and calculate impact probabilities for possible flight trajectories, and the ship information is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear and unsafe launch times based on ship locations, current conditions, and predicted collision risks, i.e. receiving one or more data feed from a maritime tracking system and using one or more received data from maritime tracking system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have Wallops Ship Surveillance System for day-of-launch risk analysis is that, as indicated by Smith, this would enable rapid analysis of possible flight paths to preclude the need to cancel launches and allow execution of launches in a timely manner, which prevents falsely report safe-for-launch condition while having low cost and large customer base elements (see [pg 9]). Regarding claim 25, modified Hoots in view of Hushing teaches the non-transitory computer-readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the at least one processor to perform operations (see Hoots [0022] and Fig. 5 in general as shown above in claim 21.) such that: Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receiving the one or more data feeds comprises receiving at least one data feed from a maritime tracking system; and using the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle comprises using the at least one data feed from the maritime tracking system and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Smith teaches Wallops Ship Surveillance Software, which is a day-of-launch risk analysis tool for spaceport activities, where it calculates impact probabilities and displays ship locations relative to boundary lines for safe-for-launch conditions, in which official ship information and risk analysis are shared with other networked workstations, i.e. receiving one or more data feeds from a maritime tracking system and processing the information for launch safety analysis (see [pg 9]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Smith, such that official ship information and risk analysis for spaceport activities are shared and used to display ship locations relative to boundary lines and calculate impact probabilities for possible flight trajectories, and the ship information is combined with launch ephemeris, protected satellite data, and telemetry data from ground station and launch vehicle sources to determine clear and unsafe launch times based on ship locations, current conditions, and predicted collision risks, i.e. receiving one or more data feed from a maritime tracking system and using one or more received data from maritime tracking system and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have Wallops Ship Surveillance System for day-of-launch risk analysis is that, as indicated by Smith, this would enable rapid analysis of possible flight paths to preclude the need to cancel launches and allow execution of launches in a timely manner, which prevents falsely report safe-for-launch condition while having low cost and large customer base elements (see [pg 9]). 9. Claims 8, 18, and 28 are rejected under pre-35 USC 103 a being unpatentable over Hoots in view of Hushing in further view of Norbraten (“Day-of Launch I-Load Updates for the Space Shuttle”, https://arc.aiaa.org/doi/pdf/10.2514/6.1992-1274). Regarding claim 8, modified Hoots in view of Hushing teaches the space launch service platform computing device of claim 1, wherein the at least one processor is configured to (see Hoots [0022] and Fig. 5 in general as shown above in claim 1.). Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receive the monitoring data from the plurality of sensors located at the launch site and on the launch vehicle by receiving monitoring data that includes real-time structural integrity assessments that allow for on-the-fly adjustments to a launch schedule based on the condition of the launch vehicle; and use the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle by using the received one or more data feeds and the real-time structural integrity assessments to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Norbraten teaches close monitoring of flight conditions to ensure structural integrity of a space shuttle, i.e. launch vehicle, is not compromised and the parameters of interest to monitor are dynamic pressure, angle of attack, and angle of sideslip, and in order to evaluate issues, wings, vertical stabilizer, and atmospheric conditions such as wind conditions are considered, i.e. receive one or more monitoring data at the launch site and on the launch vehicle that include real-time structural integrity assessments that allow for on-the-adjustments to a launch schedule based on the condition of the launch vehicle (see [pg 2]). Then, when structural margins of safety are violated, there is a recommendation made to hold launch or postpone until such conditions improve, i.e. generate launch data indicative of current and predicted conditions (see [pg 3]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Norbraten, such that real-time telemetry data from ground station and launch vehicle sources are processed together with flight conditions, including dynamic pressure, angle of attack, angle of sideslip, and atmospheric wind conditions to evaluate the structural integrity of the launch vehicle and determine whether structural margins of safety are violated to allow for a recommendation to hold or postpone launch until such condition of structural margins of safety that are violated have improved, and such information is used with launch ephemeris and protected satellite data to determine clear launch times based on current operating conditions and predicted collision risks, i.e. receiving one or more data feed from real-time structural integrity assessments that allow for on-the-fly adjustments to a launch schedule and using one or more received data from real-time structural integrity assessments and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have close monitoring of flight conditions to ensure the structural integrity of the launch vehicle is not compromised is that, as indicated by Norbraten, this would reduce possibility of a launch scrub due to unexpected wind profiles at high altitude, standardize ascent flight profile, and reduce the cost of flight software verification, commit-to-flight trajectory analysis, and flight crew training (see [pg 2]). Regarding claim 18, modified Hoots in view of Hushing teaches the method of claim 11, wherein: Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receiving the monitoring data from the plurality of sensors located at the launch site and on the launch vehicle comprises receiving monitoring data that includes real-time structural integrity assessments that allow for on-the-fly adjustments to a launch schedule based on the condition of the launch vehicle; and using the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle comprises using the received one or more data feeds and the real-time structural integrity assessments to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Norbraten teaches close monitoring of flight conditions to ensure structural integrity of a space shuttle, i.e. launch vehicle, is not compromised and the parameters of interest to monitor are dynamic pressure, angle of attack, and angle of sideslip, and in order to evaluate issues, wings, vertical stabilizer, and atmospheric conditions such as wind conditions are considered, i.e. receive one or more monitoring data at the launch site and on the launch vehicle that include real-time structural integrity assessments that allow for on-the-adjustments to a launch schedule based on the condition of the launch vehicle (see [pg 2]). Then, when structural margins of safety are violated, there is a recommendation made to hold launch or postpone until such conditions improve, i.e. generate launch data indicative of current and predicted conditions (see [pg 3]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Norbraten, such that real-time telemetry data from ground station and launch vehicle sources are processed together with flight conditions, including dynamic pressure, angle of attack, angle of sideslip, and atmospheric wind conditions to evaluate the structural integrity of the launch vehicle and determine whether structural margins of safety are violated to allow for a recommendation to hold or postpone launch until such condition of structural margins of safety that are violated have improved, and such information is used with launch ephemeris and protected satellite data to determine clear launch times based on current operating conditions and predicted collision risks, i.e. receiving one or more data feed from real-time structural integrity assessments that allow for on-the-fly adjustments to a launch schedule and using one or more received data from real-time structural integrity assessments and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have close monitoring of flight conditions to ensure the structural integrity of the launch vehicle is not compromised is that, as indicated by Norbraten, this would reduce possibility of a launch scrub due to unexpected wind profiles at high altitude, standardize ascent flight profile, and reduce the cost of flight software verification, commit-to-flight trajectory analysis, and flight crew training (see [pg 2]). Regarding claim 28, modified Hoots in view of Hushing teaches the non-transitory computer-readable storage medium of claim 21, wherein the stored processor-executable software instructions are configured to cause the at least one processor to perform operations (see Hoots [0022] and Fig. 5 in general as shown above in claim 21.) such that: Hoots also teaches the main processing that accesses data from satellite file uses the data through perigee and apogee filter to determine candidate crossing times, minimum separation distances, and collision probabilities between a launch vehicle and satellites, i.e. receiving at least one data feed from a satellite files and use them to generate launch data indicative of predicted conditions for clear launch windows and avoid collisions along a proposed launch trajectory (see [0025] and Fig. 7). Hushing further teaches an automated data monitoring system (ADMS), which includes a telemetry processor, that receives telemetry from a ground station and a launch vehicle sources, including airborne and landline multiplexed pulse code modulated (PCM) data streams and performs its own decommutation of the serial data streams and data is extracted for each of the segments and an identifier is read to determine the type of information, such as wind, velocity, temperature and vehicle velocity, i.e. receiving and processing monitoring data from launch site and launch vehicle indicative of current launch conditions (see [0039]-[0042]-[0042], [0051]-[0052] and Fig. 4). Modified Hoots in view of Hushing does not specifically teach: receiving the monitoring data from the plurality of sensors located at the launch site and on the launch vehicle comprises receiving monitoring data that includes real-time structural integrity assessments that allow for on-the-fly adjustments to a launch schedule based on the condition of the launch vehicle; and using the received one or more data feeds and the received monitoring data to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle comprises using the received one or more data feeds and the real-time structural integrity assessments to generate the combined launch data indicative of the current and predicted conditions at and around the launch site and along the proposed launch trajectory of the launch vehicle. However, Norbraten teaches close monitoring of flight conditions to ensure structural integrity of a space shuttle, i.e. launch vehicle, is not compromised and the parameters of interest to monitor are dynamic pressure, angle of attack, and angle of sideslip, and in order to evaluate issues, wings, vertical stabilizer, and atmospheric conditions such as wind conditions are considered, i.e. receive one or more monitoring data at the launch site and on the launch vehicle that include real-time structural integrity assessments that allow for on-the-adjustments to a launch schedule based on the condition of the launch vehicle (see [pg 2]). Then, when structural margins of safety are violated, there is a recommendation made to hold launch or postpone until such conditions improve, i.e. generate launch data indicative of current and predicted conditions (see [pg 3]). It would have been obvious to one of ordinary skill in the art before the effective filing date of the application to modify a launch collision avoidance system with computer and processor that processes launch ephemeris and protected satellite data together with information extracted from ground station and launch vehicle telemetry sources, including wind velocity, temperature, and vehicle velocity, to determine clear/safe and unsafe launch times based on current conditions and predicted collision risk of modified Hoots in view of Hushing by incorporating teaching of Norbraten, such that real-time telemetry data from ground station and launch vehicle sources are processed together with flight conditions, including dynamic pressure, angle of attack, angle of sideslip, and atmospheric wind conditions to evaluate the structural integrity of the launch vehicle and determine whether structural margins of safety are violated to allow for a recommendation to hold or postpone launch until such condition of structural margins of safety that are violated have improved, and such information is used with launch ephemeris and protected satellite data to determine clear launch times based on current operating conditions and predicted collision risks, i.e. receiving one or more data feed from real-time structural integrity assessments that allow for on-the-fly adjustments to a launch schedule and using one or more received data from real-time structural integrity assessments and the received monitoring data to generate combined launch data indicative of current and predicted conditions at and around the launch site and along a proposed launch trajectory of the launch vehicle. The motivation to have close monitoring of flight conditions to ensure the structural integrity of the launch vehicle is not compromised is that, as indicated by Norbraten, this would reduce possibility of a launch scrub due to unexpected wind profiles at high altitude, standardize ascent flight profile, and reduce the cost of flight software verification, commit-to-flight trajectory analysis, and flight crew training (see [pg 2]). Conclusion 10. The prior art made of record and not relied upon is considered pertinent to applicant’s disclosure. a. Scott (US 20130317731A1), teaches aircraft traffic system where there is a real-time tracking of a surrounding to detect any aircrafts or environmental issues and trajectories are modified to reduce risk of collision. 11. Any inquiry concerning this communication or earlier communications from the examiner should be directed to HYANG AHN whose telephone number is (571)272-4162. The examiner can normally be reached M-F 9-5. 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, Ramya Burgess can be reached at 571-272-6011. 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. /H.A./Examiner, Art Unit 3661 /MATTHIAS S WEISFELD/Examiner, Art Unit 3661
Read full office action

Prosecution Timeline

Mar 15, 2024
Application Filed
Oct 19, 2026
Non-Final Rejection mailed — §101, §103, §DOUBLEPATENT (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12637338
Load Position Verification Systems and Methods
2y 2m to grant Granted May 26, 2026
Patent 12628728
SYSTEM AND METHOD FOR ROW UNIT DISK OFFSET CALIBRATION
3y 5m to grant Granted May 19, 2026
Patent 12619248
REMOTE ASSISTANCE DEVICE AND METHOD FOR REMOTELY ASSISTING DRIVING OF AUTONOMOUS DRIVING VEHICLES
2y 3m to grant Granted May 05, 2026
Patent 12596014
GUIDANCE FOR COLLABORATIVE MAP BUILDING AND UPDATING
2y 7m to grant Granted Apr 07, 2026
Patent 12594906
UNIFIED CLOUD FOR MANAGING VEHICLES
2y 7m to grant Granted Apr 07, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

1-2
Expected OA Rounds
84%
Grant Probability
99%
With Interview (+30.0%)
Low
PTA Risk
Based on 19 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month