US 8577519

I'll research US Patent 8,577,519 by searching authoritative sources.

Let me check for any CAFC litigation or USPTO records involving this specific patent number.

Let me run additional targeted searches to confirm no litigation and verify the USPTO record.

I have reached the search limit. Based on the authoritative patent text (Google Patents record, fetched 2026-09-03, at https://patents.google.com/patent/[US8577519](/patent/US8577519)/en) and Justia (https://patents.justia.com/patent/8577519), here is my summary.

US Patent 8,577,519 (US8577519B1) — Summary

Bibliographic Data

Abstract (verbatim)

"The present invention is a telemetry system, and more specifically is a rapidly deployed modular telemetry apparatus which utilizes of SDR technology and the FPGA programming capability to reduce the number of hardware components and programming required to deploy a telemetry system."

Technology Context

The patent describes a modular satellite telemetry system combining Software Defined Radio (SDR) design principles with Field-Programmable Gate Array (FPGA) technology. A "processor deck" (containing a flight-computer interface, a microcontroller watchdog, an FPGA, an optional check/watchdog module, and an error-checking encoder) decodes uplink commands and encodes downlink data using CCSDS-compliant protocols (e.g., BCH, pseudo-randomization, Reed-Solomon FEC), with receiver and transmitter decks, at a power budget of ~200 mW. The FPGA can be reprogrammed for other CCSDS protocols (Turbo codes, convolutional codes, Viterbi, encryption, LDPC, etc.). Related applications incorporated by reference: U.S. App. 13/369,704 ("Adaptable Transponder for Multiple Telemetry Systems") and U.S. App. 13/424,754 ("System for Configuring Modular Telemetry Transponders").

Independent Claims — Plain-Language Overview

The patent has 26 claims; the two independent claims are Claim 1 and Claim 17 (all others depend from them).

Claim 1 — Modular telemetry system (system-of-components claim)

A rapidly deployed modular telemetry system made up of:

• at least one flight computer (e.g., a satellite's Command & Data Handling computer);
• at least one microcontroller;
• at least one FPGA programmed with CCSDS-compliant software, operatively connected to the microcontroller;
• at least one error-checking encoder operatively connected to perform at least one error-checking protocol (the claim text says "operatively connected with said microprocessor," which appears to be a typographical reference to the FPGA/microcontroller combination, since no separate "microprocessor" element is otherwise recited);
• at least one flight computer interface connecting the FPGA to the flight computer;
• at least one receiver deck;
• at least one transmitter deck; and
• at least one power source.

In short: a modular, reconfigurable satellite telemetry transponder built around a CCSDS-programmed FPGA, a microcontroller, and an error-checking encoder, packaged with receiver/transmitter decks and a power supply. Dependent claims 2–16 add specifics: Reed-Solomon protocol (2–3), BCH protocol (4), pseudo-randomization (5), FPGA-integrated encoder (6), other CCSDS protocol options (7), PIC M32 microcontroller (8), synchronous 422 or UART interface (9–10), 200 mW power source (11), a check/watchdog module (12), and particular uplink (13–14) and downlink (15–16) processing component sets.

Claim 17 — Telemetry system for a micro-satellite (single-FPGA claim)

A telemetry system for a micro-satellite comprising:

• at least one transmitter that transmits at least one telemetry signal to at least one flight computer interface;
• at least one interchangeable FEC error-checking encoder made of a single FPGA into which an FEC error-checking protocol has been embedded;
• at least one receiver; and
• at least one power source;
• wherein all other processing, error checking, modulation and demodulation are performed on the single FPGA.

In short: a micro-satellite telemetry system where essentially all baseband signal processing—including forward-error-correction encoding, error checking, modulation, and demodulation—is consolidated into one reprogrammable FPGA, making the FEC encoder interchangeable/software-configurable. Dependent claims 18–26 add specifics: Reed-Solomon (18), convolutional encoding (19), 32-bit ARM processor implementation (20), CCSDS compliance (21), an additional connected microchip (22–23, PIC M32), and Reed-Solomon/BCH/pseudo-randomization protocol configurations (24–26).

Litigation / CAFC 2026 Docket Search Results

I searched for "8577519," "US8577519," and "8,577,519" in connection with CAFC/2026 dockets and litigation. I found no evidence of any CAFC appeal, PTAB proceeding, or district-court litigation involving US 8,577,519. The search returned no docket entries for this patent number (results that did appear were unrelated Federal Circuit cases matched on other keywords). I have medium-to-high confidence in this negative finding based on the searches performed, but I did not exhaustively query PACER/CM/ECF or the USPTO Patent Center docket system, so I cannot guarantee the absence of a case filed under a different searchable identifier or after my last search.

Sources

• Google Patents record: https://patents.google.com/patent/US8577519/en
• Justia Patents record: https://patents.justia.com/patent/8577519
• USPTO legal-event history (maintenance fee reminders, lapse) as reproduced in the Google Patents record above.

I'll search for litigation involving US Patent 8,577,519.

Litigation Search Results: US Patent 8,577,519

No known litigation was found involving US Patent 8,577,519 (the "Rapidly deployed modular telemetry system" patent).

Searches Performed

I ran multiple targeted searches, including:

• "8577519" patent litigation
• "US8577519" lawsuit
• patent 8577519 lawsuit NASA telemetry
• 8577519B1 litigation district court
• site:portal.unifiedpatents.com 8577519 (Unified Patents litigation database)
• "8,577,519" patent case

None of these returned any litigation records, docket entries, case filings, or PTAB/IPR proceedings naming US 8,577,519. The only results returned were the patent's own Google Patents record (title, abstract, claims) and no court or administrative actions.

Contextual Observations (not litigation findings)

A few facts from the patent record are consistent with an absence of litigation:

1. Government ownership: The patent is assigned to NASA (United States of America as represented by the National Aeronautics and Space Administration). Government-owned patents are infrequently asserted in private infringement suits, which may explain the lack of litigation.

2. Expired status: According to the USPTO legal-event history shown on Google Patents, maintenance fees were paid through the 8th year (2021), but the patent lapsed for failure to pay maintenance fees effective December 8, 2025 (fee reminder mailed June 23, 2025; lapse recorded December 8, 2025; confirmed "FP – Lapsed due to failure to pay maintenance fee" effective November 5, 2025). A lapsed patent would not typically be the subject of new infringement litigation after that date.

3. No litigation history in the record: The "Legal Events" section of the patent file contains only assignment, maintenance-fee, and lapse events — no lawsuit or reexamination events.

Conclusion

Based on the available search results, I am not aware of any litigation (past or pending) involving US Patent 8,577,519, and no cases could be identified in the databases searched. If you need a more exhaustive confirmation, PACER's federal docket search and Unified Patents' full caselist would be the authoritative resources to check directly (note: PACER searches require case-number or party-name queries, and a patent-number-based search across all districts would require a text-search service such as DocketNavigator, LexisNexis, or Westlaw's Dockets).

Proceedings overview

There are zero (0) AIA trial proceedings on file for US 8,577,519 — no inter partes reviews, no post-grant reviews, no covered business method reviews, no active cases, no claims invalidated, no claims sustained, no settlements, and no institution denials. The USPTO Open Data Portal (ODP) structured block for this patent is empty, and targeted web searches (including "8577519" + IPR/PTAB terms and inventor-name queries) returned no PTAB docket entries. The bottom-line defensive posture is not "hardened by IPR" but rather something stronger: the patent expired on 2025-11-05 (lapsed 2025-12-08 for failure to pay maintenance fees), and no claim of it has ever survived — or been tested by — a PTAB trial. Any assertion theory built on this patent today runs into an expired-patent wall, not an IPR estoppel wall.

Proceedings (none)

No AIA trial proceedings exist for this patent. The ODP "PTAB proceedings on file" block is empty, and independent searches of PTAB/E2E-indexed sources surfaced no petition, no institution decision, no Final Written Decision, and no Federal Circuit appeal citing US 8,577,519. Per the operating rules, I will not invent proceeding numbers or panel names, and there is no FWD to quote.

Strategic summary

Claims: CANCELED vs. SUSTAINED vs. UNTESTED. All 26 claims (independent claims 1 and 17; dependents 2–16 and 18–26) are UNTESTED before the PTAB. No AIA proceeding was ever filed, so no claim has been canceled or sustained by the Board. The only claim-level event in the file history is the ordinary maintenance-fee sequence: fees paid through year 8 (2021-04-27), a lapse notice mailed 2025-06-23, and expiration for non-payment effective 2025-11-05 (recorded 2025-12-08).

Estoppel landscape. Because no IPR/PGR/CBM was ever instituted, no § 315(e)(2) estoppel attaches to any petitioner, and no § 315(a)(1) civil-action bar or Fintiv-based denial exists. For a defendant, this means the prior-art universe is fully open — but it is also largely moot: the statutory window for IPR petitions requires the petitioner to have been served with an infringement complaint within the prior year (35 U.S.C. § 315(b)), and a post-expiration complaint can reach only pre-expiration conduct within the § 286 six-year damages window. In practice, an IPR directed at this expired patent would face serious justiciability/standing questions.

Pattern signals. There are none — no repeat petitioner, no defensive aggregator (Unified Patents or otherwise), no patent-owner PTAB advocacy history. The absence of IPR activity is itself the signal: this is a NASA government-owned patent (assigned to the United States of America as represented by NASA), made by government employees and dedicated to royalty-free government use. Government-owned patents of this character are rarely litigated or IPR-challenged because they are typically licensed rather than troll-asserted — and this one is now expired in any event.

Recommended next steps

• If you are a defendant facing a demand letter citing US 8,577,519: there is no FWD to link because no proceeding exists. Instead, lead with the expiration facts — maintenance fees lapsed, patent expired effective 2025-11-05 (recorded 2025-12-08 in the USPTO legal-event history on the Google Patents record at https://patents.google.com/patent/US8577519/en). An expired patent cannot support injunctive relief, and damages are limited to proven infringing acts before 2025-11-05 and within the § 286 six-year lookback (no earlier than 2019-11-05 for a suit filed today, and note the patent did not even issue until 2013-11-05).
• Verify independently by pulling the USPTO Patent Center file wrapper for US 13/424,898 and running the patent number through PTAB E2E (https://ptab.uspto.gov) and the USPTO ODP trial-proceeding API — my negative finding is based on the ODP block plus web searches, not an exhaustive PACER/E2E query.
• If the demand letter is post-expiration and cites claims 1 or 17, the more useful defenses are: (1) expired patent — no prospective relief; (2) laches/statute of limitations for any alleged pre-expiry conduct; and (3) if the accused activity is government-related, the patent's federal-government license (the invention was made by NASA employees and the government has royalty-free rights). An IPR is not the right tool for this patent in its current expired state; a declaratory-judgment or Rule 11 response keyed to expiration is.
• Monitor only if revived: the adjusted expiration of 2032-06-13 is now defunct; reinstatement of an expired-for-nonpayment patent is not automatic. If the patent were ever revived (e.g., via a successful maintenance-fee petition under 37 C.F.R. § 1.378), then — and only then — would an IPR defense strategy become relevant, and a petition would need to be filed within one year of service of any new complaint.

I'll verify the assignment record against USPTO databases and check for any post-issuance transfers.

Let me attempt to check the USPTO assignment database directly for any recorded conveyances on this patent.

Let me make final verification attempts on the USPTO assignment records and the inventors' employment context.

Inventors

• Kosta A. Varnavas — U.S. Government employee at the time of filing. The patent's Federal Research Statement states the invention "was made by employees of the United States Government." Varnavas is a researcher at NASA Marshall Space Flight Center (Huntsville, AL); the same-named author published the paper "Rapidly Deployed Modular Telemetry System" (Varnavas et al., 2013) listed in Google Patents' similar-documents for this family.
• William Herbert Sims, III — U.S. Government employee at the time of filing (same Federal Research Statement); also NASA Marshall Space Flight Center (co-author on the RDMT paper, and NASA MSFC engineer).

Unusual patterns: None. Both inventors assigned their rights to the U.S. government on the filing date itself (reel 027894/0737, executed and recorded 2012-03-20). This is the standard NASA employee-inventor assignment pattern, not a pre-fire-sale departure signal. Both remained NASA-affiliated researchers after filing.

Original assignee

• United States of America as represented by the National Aeronautics and Space Administration (NASA) — the entity named on the issued patent (assignment recorded 2012-03-20, reel 027894/0737, effective same date).
• Line of business: U.S. government civil space agency (research, development, and flight operations) — not a commercial patent-assertion entity.
• Product embodiment: The claimed RDMT system was developed as an in-house NASA telemetry transponder concept (small/micro-satellite class); NASA does not "ship products" in a commercial sense but did develop and publish the underlying technology (e.g., the 2013 RDMT conference paper). Government use is royalty-free per the Federal Research Statement.
• Current status: Operating (as a government agency). The patent itself, however, lapsed December 8, 2025 for failure to pay maintenance fees (effective lapse November 5, 2025), after 8th-year maintenance fees were paid in 2021 (MAFP, 2021-04-27).

Assignment timeline

The USPTO Assignment Center record for US 8,577,519 (as reproduced in the authoritative Google Patents legal-events feed, fetched 2026-09-03) contains exactly one recorded conveyance — the original inventor-to-government assignment. There are no recorded post-issuance assignments, security agreements, mergers, name changes, licenses, or releases.

• 2012-03-20 (executed) / recorded 2012-03-20 — Reel 027894/0737
  • Conveyance: Assignment (of assignors' interest)
  • Assignor: William Herbert Sims, III; Kosta A. Varnavas
  • Assignee: United States of America as represented by the National Aeronautics and Space Administration (NASA)
  • Correspondent: Not determinable from the available record. The Google Patents legal-event entry does not reproduce the correspondent of record for this reel/frame, and I could not reach the Assignment Center image directly to confirm the attorney/firm. I will not speculate. Because this is the sole conveyance, no correspondent-recurrence analysis is possible.
  • Context: Same-day employer assignment from NASA employee-inventors to the U.S. government upon filing — the standard government-title capture, not a transfer to any third party.

Post-issuance, the only USPTO events are maintenance-fee payments (FPAY 2017-04-25, year 4; MAFP 2021-04-27, year 8), a maintenance-fee reminder (FEPP 2025-06-23), and lapse for nonpayment (LAPS/FP, 2025-12-08/2025-12-30, effective 2025-11-05). No assignment records exist beyond reel 027894/0737 — meaning the original assignee, the U.S. government (NASA), has retained ownership for the life of the patent.

Timeline diagram

timeline
    title Ownership of US 8577519
    2012 : Filed by NASA inventors
         : Assigned to US Govt NASA
    2013 : Patent issued Nov 5
    2017 : Maintenance fee paid
    2021 : Year 8 fee paid
    2025 : Lapsed fee not paid

NPE / troll-pattern signals

1. Shell-entity transfer — Not present. The patent never moved from NASA to any LLC, "IP Holdings," licensing vehicle, or registered-agent address. The only transfer is inventors → U.S. government (reel 027894/0737, 2012-03-20).
2. Known asserter in the chain — Not present. Neither the current owner (U.S. government/NASA) nor any prior owner matches Acacia, Marathon, Intellectual Ventures, IPNav, Wi-LAN, Conversant, Vringo, Pendrell, Spangenberg entities, or any Unified Patents / RPX high-frequency plaintiff. No litigation naming this patent was found in the prior search pass.
3. Repeat correspondent across the chain — Not present (and not assessable). There is only one recorded conveyance, so no correspondent recurs. The correspondent for reel 027894/0737 is not visible in the available record.
4. Cascading transfers — Not present. Zero post-issuance transfers; no chained LLCs, in any time window.
5. Pre-litigation transfer — Not present. No infringement suit exists, and the sole assignment (2012-03-20) predates issuance (2013-11-05) by 19 months — it is the origin of title, not a venue/standing arrangement.
6. Bankruptcy fire-sale — Not present. The assignee is the U.S. government; no bankruptcy proceedings. The patent's 2025 lapse was a routine maintenance-fee nonpayment, not an asset sale.
7. Privateering — Not present. No operating company transferred this patent to an NPE for competitor-harassment; no SEC filings or EFF/Patent Progress coverage implicate it.
8. Defensive aggregator (anti-NPE) — Not present. The chain does not terminate at RPX, AST, LOT, Unified Patents, or OIN; it terminates at NASA, which is not a defensive aggregator. The inverse signal (neutralization) is nonetheless effectively achieved: the patent is dead — lapsed 2025-12-08 for unpaid maintenance fees.

Verdict

Insufficient data — the record contains only the original assignment (inventors → U.S. government/NASA, reel 027894/0737, 2012-03-20), which is the rubric's designated basis for this verdict. That single recorded conveyance is affirmatively inconsistent with every NPE signal: the current owner is the U.S. government, there are no post-issuance transfers, no litigation was found, and the patent lapsed on 2025-12-08 for unpaid maintenance fees. In short, this is a government-owned patent with a flat, one-link chain of title and no troll-pattern indicators of any kind.

Verify at the USPTO Assignment Center: https://assignmentcenter.uspto.gov/ (search Patent No. 8577519) or https://assignment.uspto.gov/patent/index.html (reel/frame 027894/0737). Note: I could not directly load the Assignment Center image viewer in this session; the assignment data above is drawn from the authoritative Google Patents legal-events feed. If you need the correspondent-of-record for reel 027894/0737 for your files, pull the cover-sheet PDF from that reel/frame directly.

I'll research US Patent 8,577,519's cited prior art. Let me start by verifying the USPTO record and the cited references.

Let me now research the remaining cited references.

Now let me search the remaining two cited references.

I have reached the search limit. Based on the authoritative patent record (Google Patents/Justia copies of US 8,577,519 B1, and the patent's own "Patent Citations (5)" table reproduced in the full-text record above), plus targeted searches on each cited reference, here is the prior-art analysis.

USPTO Record Verification — Patent 8,577,519

Searches for the exact number 8577519 return only US 8,577,519 B1 ("Rapidly deployed modular telemetry system," Varnavas & Sims, assignee NASA / United States of America, filed Mar. 20, 2012, granted Nov. 5, 2013). No near-number collisions (e.g., 8577518/8577520) were retrieved, and no litigation or PTAB proceeding naming this patent was found in any prior search (see earlier sections). Confirmed via:

• Google Patents: https://patents.google.com/patent/US8577519/en
• Justia: https://patents.justia.com/patent/8577519

Applicable law note: Because the application was filed March 20, 2012 (before the AIA's Mar. 16, 2013 effective date), pre-AIA 35 U.S.C. § 102 governs. For a single reference to "potentially anticipate," it must disclose every limitation of the claim, arranged as in the claim. For § 102(b), a U.S. patent or printed publication must have issued/published before March 20, 2011 (one year before filing).

The record lists five examiner-cited references (all marked "* Cited by examiner"). Each is analyzed below against independent claims 1 and 17 (the dependent claims 2–16 and 18–26 cannot be anticipated if their base independent claim is not).

Cited Reference Analyses

1. US 7,103,511 B2 — "Wireless Communication Networks for Providing Remote Monitoring of Devices"

• Full citation: Petite, Thomas D. (StatSignal IPC, LLC), U.S. Patent No. 7,103,511 B2, issued September 5, 2006; U.S. App. Ser. No. 09/925,269 filed August 9, 2001; earlier published as US 2002/0019725 A1 (Feb. 14, 2002). Earliest priority claimed through a CIP chain to Oct. 14, 1998 (U.S. App. 09/172,554 → US 6,028,522).
• Brief description: Terrestrial wireless mesh networks for remote monitoring/control of dispersed devices (utility-type transceivers). Wireless transceivers with unique identifiers receive sensor data signals and relay original/repeated data messages using a predefined protocol to a site controller, which manages communications with a host computer over a wide-area network.
• § 102 analysis: Anticipates no claim. It is a ground-based device-monitoring network, not a spacecraft telemetry system. It lacks the required flight computer, microcontroller, FPGA configured with CCSDS-compliant software, error-checking encoder performing an error-checking protocol, flight computer interface, and receiver/transmitter "deck" structure of claim 1. Claim 17's micro-satellite single-FPGA FEC architecture (with all processing, error checking, modulation and demodulation on one FPGA) is likewise absent. Its relevance is limited to background for generic wireless telemetry and relaying; at most it is a § 103 combination candidate, not § 102 art.

2. US 6,807,428 B2 — "Method and Apparatus for Time-Based Reception of Transmissions in a Wireless Communication System"

• Full citation: Qualcomm, Incorporated, U.S. Patent No. 6,807,428 B2, issued October 19, 2004; filed August 16, 2001. (Inventor name not confirmed in the available search results; do not rely on an unverified inventor name.)
• Brief description: A wireless communication device (usable in satellite or terrestrial spread-spectrum/CDMA systems) manages power consumption by time-based scheduling of reception — the receiver is activated to receive transmissions only at predetermined/relevant times rather than continuously.
• § 102 analysis: Anticipates no claim. The reference is directed to receiver power-management timing in a general wireless system. It does not disclose a satellite flight computer, a microcontroller watchdog, a CCSDS-configured FPGA performing telemetry uplink/downlink protocol processing, an error-checking encoder, or the receiver/transmitter-deck telemetry architecture of claim 1, nor the single-FPGA micro-satellite FEC encoder of claim 17. Any overlap (a receiver and transmitter) is incidental and far short of every limitation.

3. US 2009/0295628 A1 — "Satellite System Optimization"

• Full citation: Viasat, Inc., U.S. Patent Application Publication US 2009/0295628 A1, published December 3, 2009; U.S. App. Ser. No. 12/411,704 filed March 26, 2009; priority claimed to Sept. 26, 2006 (status: abandoned per the record).
• Brief description: Broadband multi-beam satellite communications system optimization (Ka-band, star network). The disclosure concerns ground infrastructure — gateways, subscriber terminals/satellite modems, satellite modem termination systems (SMTS), and dynamic management of bandwidth, latency, spot beams, and resource allocation to improve system capacity.
• § 102 analysis: Anticipates no claim. The focus is ground-segment broadband networking, not an onboard satellite telemetry/C&DH link. Missing: flight computer, microcontroller, FPGA with CCSDS software, error-checking encoder, flight computer interface, and the telemetry uplink/downlink processing of claim 1; likewise the micro-satellite single-FPGA FEC system of claim 17. It qualifies as § 102(b) art by date (published well before Mar. 20, 2011) but its disclosure does not meet any claim element-for-element.

4. US 2009/0289839 A1 — "Dynamic Sub-Channel Sizing"

• Full citation: Viasat, Inc., U.S. Patent Application Publication US 2009/0289839 A1, published November 26, 2009; priority date September 26, 2007 (inventor listed in the record as "McDaniel").
• Brief description: Companion Viasat broadband-satellite disclosure. Physical forward channels are divided into physical sub-channels of dynamically variable sizes; satellite modems strip/filter only their allocated sub-channels from the forward channel, with adaptive modulation-and-coding ("modcode") per packet/link conditions. Figures show physical sub-channel filters, digitizers, and header/payload splitters in satellite modems/gateways.
• § 102 analysis: Anticipates no claim. It concerns channelization and sub-channel filtering in the broadband satellite downlink between gateway and subscriber modems — not spacecraft TT&C telemetry. It lacks all of claim 1's core elements (flight computer, microcontroller, CCSDS-configured FPGA, error-checking encoder, flight computer interface) and claim 17's single-FPGA, all-processing micro-satellite architecture. § 102(b)-qualified by date, but no element-for-element match to any claim.

5. US 2013/0018529 A1 — "Methods and Systems for Satellite Integrated Communications" ⚠ closest potential art; verification incomplete

• Full citation: Riverside Research Institute, U.S. Patent Application Publication US 2013/0018529 A1, published January 17, 2013; earliest priority/filing date July 13, 2011 per the Google Patents citation record.
• Brief description: By title and assignee, it concerns methods and systems for satellite integrated communications — the nearest technical field of the five citations to a satellite communications/telemetry transponder. Caveat: my search quota was exhausted before I could retrieve the full text or abstract of this document, so I cannot verify its specific disclosure (e.g., whether it describes an FPGA-based, CCSDS/software-defined-radio satellite telemetry architecture) with confidence. Treat the following as conditional, not confirmed.
• § 102 analysis (conditional):
  • Not § 102(a) or § 102(b) art: It published (Jan. 17, 2013) after the 8577519 filing date (Mar. 20, 2012) and more than one year after the Mar. 20, 2011 critical date — so neither subsection applies.
  • Possible § 102(e) art: Under pre-AIA § 102(e), a U.S. application published under § 122(b) by another is prior art as of its effective U.S. filing date if that filing predates the applicant's invention. If its July 13, 2011 date is an effective U.S. filing date (and absent evidence NASA conceived earlier), it precedes the Mar. 20, 2012 NASA filing and could be § 102(e) art.
  • Claim reach (conditional on content): If the reference discloses a satellite onboard system combining a flight-computer interface, an FPGA or SDR handling CCSDS/error-checking (e.g., Reed-Solomon/BCH) protocols, and receiver/transmitter elements, it could potentially anticipate claim 1 (and dependents 2–16, depending on which protocols/interfaces are disclosed). If it discloses a single-FPGA implementation handling all error checking, modulation and demodulation for a small satellite, it could potentially anticipate claim 17 (and dependents 18–26). I cannot confirm or exclude anticipation without the full text — retrieve it via the USPTO Patent Center or Google Patents (patents.google.com/patent/US20130018529A1) before relying on it.

Summary Ranking (relevance as § 102 art)

Bottom line: Within the five examiner-cited references, none has been confirmed to anticipate any claim of 8,577,519 on its own. The older four references are far-field (terrestrial monitoring, receiver power gating, broadband gateway optimization); they disclose at most generic wireless/telemetry building blocks and would function only as § 103 obviousness combination fodder, not § 102 anticipatory art. US 2013/0018529 A1 is the only cited reference that is potentially anticipatory, and the only one with a § 102 date problem (it requires a § 102(e) analysis and a full-text disclosure check, which I could not complete within the search limit).

§ 103 Obviousness Analysis — US 8,577,519 B1 ("Rapidly Deployed Modular Telemetry System")

I. Framework, governing law, and scope

US 8,577,519 B1 was filed March 20, 2012 — before the AIA's March 16, 2013 effective date — so pre-AIA 35 U.S.C. § 103 governs. Under the Graham framework, obviousness turns on (1) the scope and content of the prior art, (2) the differences between the prior art and the claims, (3) the level of ordinary skill in the art, and (4) objective indicia. Under KSR Int'l Co. v. Teleflex Inc. (2007), a combination of known elements is obvious when a skilled artisan would have had a reason to combine them with a reasonable expectation of success — including when the combination yields only predictable results, when a known technique is applied to a known problem ready for improvement, or when the result is "obvious to try" among a finite set of identified, predictable solutions. But the analysis must avoid hindsight, and each reference must be prior art and within an analogous field or reasonably pertinent to the problem.

A preliminary date-eligibility point drives everything below. Of the five references in the record, four issued/published before March 20, 2011 (the § 102(b) critical date) and are unquestionably available: US 7,103,511 B2 (issued 2006-09-05), US 6,807,428 B2 (issued 2004-10-19), US 2009/0295628 A1 (published 2009-12-03), and US 2009/0289839 A1 (published 2009-11-26). The fifth — US 2013/0018529 A1 (Riverside Research Institute) — published January 17, 2013, after the '519 filing date, and filed July 13, 2011, after the March 20, 2011 critical date. It is therefore not § 102(b) art; it can be prior art only under pre-AIA § 102(e), effective as of its July 13, 2011 filing date, and only if the NASA inventors' conception is not earlier than July 13, 2011. If conception evidence pushes the NASA invention before that date, Riverside drops out of the prior-art universe entirely — a material vulnerability for any obviousness theory built on it (discussed in Part VI).

The scope of this analysis is limited to the five examiner-cited references identified in the Prior Art section of this file, read together with the level of ordinary skill and any "background knowledge" a skilled artisan would bring, as KSR permits.

II. Person of ordinary skill in the art (PHOSITA)

Circa March 2012, a PHOSITA designing a small-satellite telemetry/transponder subsystem would hold a B.S. or M.S. in electrical engineering, computer engineering, or aerospace engineering, with roughly 2–5 years of experience in satellite command-and-data-handling (C&DH) or TT&C (telemetry, tracking & command) design. The person would be conversant with:

• the CCSDS space-link standards (Reed-Solomon and BCH error-control codes, pseudo-randomization, convolutional/Turbo/LDPC codes, sync/attach markers);
• FPGA-based digital design and software-defined radio (SDR) principles (the specification itself concedes both were "widespread" by 2012 — see Background, US 8,577,519);
• spacecraft flight-computer interfaces (RS-422, UART) and microcontroller supervisory/watchdog practice; and
• the power and mass constraints of micro/nano-satellites.

The patent's own Background confirms the relevant problem was known and unsolved: conventional NASA transponders cost >$500K and required reconfiguring "countless hardware components" per mission. That framing matters because it defines what the art had to motivate, not what the patentee later claimed.

III. Claim landscape (recap)

• Claim 1 (independent): a modular telemetry system combining a flight computer; a microcontroller; an FPGA configured with CCSDS-compliant software operatively connected to the microcontroller; an error-checking encoder performing at least one error-checking protocol; a flight-computer interface; a receiver deck; a transmitter deck; and a power source.
• Claim 17 (independent): a micro-satellite telemetry system in which an interchangeable FEC encoder is a single FPGA with an embedded FEC protocol and all other processing, error checking, modulation and demodulation are performed on that single FPGA.
• Dependent claims 2–16 and 18–26 particularize protocols (Reed-Solomon, BCH, pseudo-randomization; claims 2–7, 18, 24–26), hardware (PIC M32, ARM, 422/UART interfaces, 200 mW source; claims 8–11, 20, 22–23), a check/watchdog module (claim 12), and uplink/downlink component sets (claims 13–16).

The core claim elements that drive the obviousness inquiry are: (i) satellite/flight-computer context; (ii) CCSDS-protocol processing implemented in software on an FPGA; (iii) an error-checking/FEC encoder component; (iv) the specific deck/interface architecture; and — for claim 17 — (v) full baseband consolidation onto a single FPGA.

IV. Scope and content of the five references

Net content: the five references collectively place before a PHOSITA (a) generic terrestrial remote-telemetry networking with a host/site-controller hierarchy (StatSignal); (b) satellite-capable receiver power management (Qualcomm); (c) broadband satellite systems with coding-and-modulation modems, mostly ground-side (both Viasat refs); and (d) a small-satellite command/data link using smartphone-derived onboard processors and a cellular ground network (Riverside). No reference discloses CCSDS protocol software, an FPGA configured therewith, a Reed-Solomon/BCH/pseudo-randomization encoder, a "deck" architecture, a PIC M32/RS-422 flight interface, or single-FPGA baseband consolidation.

V. Differences between the prior art and the claims

The differences that any § 103 challenger must bridge are substantial:

1. Satellite telemetry/C&DH context — Only Riverside is even in the small-satellite communications field, and it is ground-network-centric; none of the references describes a satellite-to-ground telemetry system in the CCSDS sense (the four older refs are either terrestrial (StatSignal), generic (Qualcomm), or broadband bent-pipe ground-segment (Viasat)).
2. CCSDS-compliant software on an FPGA (claims 1, 4–7, 21) — absent from all five references. CCSDS is a space-data standard; nothing in the cited art so much as names it.
3. Error-checking encoder performing an error-checking protocol (claims 1–6, 18, 24–26) — the closest teachings are StatSignal's generic "predefined wireless communication protocol" and Viasat's adaptive modcode (which implies physical-layer FEC, e.g., DVB-S2-style LDPC/BCH), but neither discloses a CCSDS Reed-Solomon/BCH encoder, let alone one operatively connected to an FPGA in a telemetry processor deck.
4. Specific architecture — flight computer ↔ flight-computer interface ↔ FPGA + microcontroller + encoder ↔ receiver/transmitter decks + power source (claims 1, 8–16) — no single reference or natural combination maps onto this.
5. Single-FPGA consolidation (claim 17) — "all other processing, error checking, modulation and demodulation … on said single FPGA" — the cited art points the opposite way: StatSignal uses distributed transceivers and a separate site controller; Viasat uses discrete modems/SMTS/gateways; Riverside uses smartphone boards plus network servers. Nothing motivates consolidation into one FPGA.

VI. Candidate combinations and motivation analysis

Combination A (strongest colorable case against claim 1)

US 2013/0018529 A1 (Riverside) as the primary reference + US 2009/0289839 A1 (Viasat '839) + US 7,103,511 B2 (StatSignal), optionally + US 6,807,428 B2 (Qualcomm).

Theory: Riverside supplies the satellite/small-satellite environment and the problem — inexpensive, flexible command-and-data links to small satellites — by disclosing small satellites carrying a programmable, smartphone-derived communication board/CPU that receives commands from and downlinks data to a distributed ground network. A PHOSITA designing such an onboard communications processor for command uplink and telemetry downlink would, as a matter of standard engineering knowledge in 2012 (not from any single reference), implement the link-layer protocol processing in an FPGA because FPGA-based CCSDS encoding/decoding was the conventional, low-power, reconfigurable implementation choice for space links (the '519 specification itself treats SDR/FPGA as pre-existing "widespread" technology). Viasat '839 reinforces that satellite-link modems perform adaptive coding and modulation ("modcode") — i.e., physical-layer FEC encoding is a routine modem function — and discloses the modem-side processing blocks (FIGS. 22–24, "downstream processing") that a PHOSITA would recognize as implementable in an FPGA. StatSignal supplies the host-computer / site-controller / wireless-transceiver hierarchy with a predefined message protocol and encoded data — a terrestrial analogue of flight computer → processor deck → receiver/transmitter decks — and the use of microprocessors/controllers in that hierarchy. Qualcomm (optionally) supplies satellite-context receiver power management, motivating the modest ~200 mW power budget of claim 11.

Why combine: The unifying motivation is cost and flexibility — the same problem Riverside (lower-cost satellite access), Viasat (efficient use of satellite capacity), and StatSignal (low-cost remote monitoring without hard-wired infrastructure) each address in their own field. A PHOSITA seeking a low-cost, rapidly reconfigurable small-satellite telemetry transponder would predictably combine a programmable FPGA protocol engine (standard SDR/FPGA practice), a standard FEC encoder, a supervisory microcontroller, and deck-style RF front ends — all well-known building blocks — and would have a reasonable expectation of success because each element performs its known function in a known way.

Honest grading: Moderate at best — and only with heavy reliance on general knowledge. The combination still lacks express disclosures of (i) CCSDS compliance, (ii) an error-checking encoder component performing a specific error-checking protocol (Reed-Solomon/BCH), (iii) the flight-computer-interface element, and (iv) the receiver/transmitter deck packaging. A challenger would have to argue these are "design choices" or within the PHOSITA's background knowledge — permissible under KSR only if the record shows a reason to make those specific choices. The examiner allowed the claims over exactly these references, so the combination would need new expert framing, not merely re-litigation of the same references singly. Additionally, the Riverside linchpin is § 102(e)-only and collapses if NASA conception predates 2011-07-13.

Combination B (no-Riverside fallback against claim 1)

Viasat '839 + Viasat '628 + StatSignal '511 (+ Qualcomm '428).

Theory: If Riverside is excluded, the case rests on the four pre-critical-date references. Viasat '839/'628 show a complete satellite communications system (satellite, gateways, modems with adaptive coding/modulation and downstream/upstream processing blocks); StatSignal shows a modular remote-telemetry network with a microprocessor-based site controller, a host computer, and protocol-encoded wireless links; Qualcomm shows satellite-context receiver power management. A PHOSITA could be said to have been motivated to "put the modem on the satellite" — i.e., migrate Viasat's coding/modulation processing onto the spacecraft and add StatSignal's supervisory/interface hierarchy — to support onboard telemetry.

Honest grading: Weak. The Viasat disclosures are ground-segment broadband networking; their satellite is a bent-pipe relay with only an upstream translator, affirmatively suggesting onboard processing was not where such coding lived. StatSignal is terrestrial utility-monitoring art — a different field with a different problem (mesh relaying of sensor data, not space-link protocol processing) — and its "predefined protocol" is not CCSDS or any FEC scheme. Using these references to build the claimed FPGA-CCSDS-FEC deck requires assembling elements from non-analogous arts with no teaching, suggestion, or market pressure linking them — precisely the hindsight combination KSR and its progeny caution against. This combination would likely not render claim 1 obvious on a developed record.

Combination C (claim 17 — single-FPGA micro-satellite system)

Any combination of Riverside + Viasat '839 + StatSignal + Qualcomm.

Theory: Riverside gives "micro/small-satellite" and an onboard programmable communications processor; Viasat '839 gives coding/modulation processing blocks; a challenger would argue that shrinking a modem + FEC encoder + protocol processor into a single FPGA for a power-constrained micro-satellite was an "obvious to try" consolidation using known FPGA/SDR techniques.

Honest grading: Weak, and the art teaches away. Claim 17's defining limitation — that all processing, error checking, modulation and demodulation occur on a single FPGA with the FEC encoder being interchangeable (software-embedded) — is contradicted by the architecture of every cited reference: StatSignal distributes intelligence across transceivers and a separate site controller; Viasat separates the modem from the SMTS/gateway and uses hardware channel filters (FIGS. 11A/11B, physical sub-channel filters); Riverside offloads tasking/reformatting to ground servers and uses smartphone boards plus network-side processing. Nothing in these references suggests consolidating baseband functions onto one FPGA, and the ordinary design incentives in the cited art (leveraging existing distributed infrastructure) point away from it. The "interchangeable FEC encoder … single FPGA" and "all other processing … on said single FPGA" limitations would likely be found non-obvious over this record.

Dependent claims

The dependent claims do not rescue a weak independent-claim case, but they do add independent obstacles for a challenger:

• Claims 2–7, 18, 24–26 (Reed-Solomon / BCH / pseudo-randomization / Turbo / convolutional / Viterbi / LDPC / encryption / auto-ranging): none of the references names any CCSDS code. Viasat's generic "modcode" does not teach Reed-Solomon or BCH in a CCSDS telemetry frame; a PHOSITA would know these codes existed (and that RS/BCH were CCSDS staples), but the selection of the specific claimed protocols for the specific claimed function would need to be grounded in evidence, not assumption.
• Claims 8–11, 20, 22–23 (PIC M32, 422/UART, 200 mW, ARM): PIC M32 and ARM are named commercial products not mentioned anywhere in the art; RS-422/UART are generic interface standards a PHOSITA would know, and the 200 mW budget is a power-design choice with no prior-art anchor. These read as obvious design choices only if the underlying system is obvious — which, per above, is doubtful.
• Claim 12 (check module/watchdog): watchdog/heartbeat supervisory circuits were generic 2012 design practice, but no reference discloses them in the claimed FPGA–microcontroller arrangement.
• Claims 13–16 (uplink/downlink component sets): the specific component lists (bit sync, randomizer, BCH encoder/processor, FIFO, sync-marker generator, Reed-Solomon ASIC control, pseudo-random generator, multiplexer) map to CCSDS modem blocks; Viasat's processing-block disclosures are the nearest analogue but are in a broadband-modem, not CCSDS-telemetry, context.

VII. KSR motivation and reasonable-expectation assessment — candid summary

Where a motivation argument is strongest:

• The problem (expensive, application-specific satellite telemetry transponders needing rapid reconfiguration) was known, and the tools (FPGA, SDR, CCSDS protocol blocks, FEC encoders) were mature by 2012 — the '519 specification concedes SDR/FPGA were "widespread." A PHOSITA designing any modern space link would know to implement CCSDS randomization and FEC in programmable logic as a default.
• Riverside supplies a real, dated motivation to lower small-satellite communications cost through programmable onboard processing — the closest analogue to the '519 problem in the cited set.
• StatSignal and the Viasat refs collectively show that "modular processor/controller + protocol-encoded wireless link + coding-and-modulation modem" was a known pattern, even if in different fields.

Where the argument fails or becomes hindsight:

• Non-analogous art. StatSignal (terrestrial utility mesh), Qualcomm (CDMA receiver timing), and the Viasat pair (broadband bent-pipe ground networks) are not analogous to an onboard CCSDS telemetry processor; a PHOSITA designing a NASA-class TT&C transponder would not naturally mine utility-metering or Ka-band broadband-modem patents. Under Graham/analogous-art doctrine, these references likely cannot be combined without a specific evidentiary link that is absent here.
• Missing core limitations. CCSDS compliance, the error-checking encoder, the flight-computer interface, the deck architecture, and single-FPGA consolidation are not taught, suggested, or (for claim 17) even hinted at — filling them requires stacking inference on inference.
• Teaching away (claim 17). The cited art's distributed architectures weigh against the single-FPGA consolidation claim.
• Prosecution history context. The claims issued over all five references; the examiner evidently did not view them, singly or in combination, as dispositive. A later § 103 challenge would need new evidence (e.g., expert testimony on PHOSITA background knowledge) rather than the same references alone.
• Riverside's eligibility fragility. The only satellite-domain reference is § 102(e)-only and may be eliminated by a pre-July-2011 conception showing.

VIII. Secondary considerations

No objective indicia of non-obviousness (commercial success, licensing, copying, long-felt need satisfied) appear in the record — but neither is there evidence for obviousness from such indicia. The patent's own Background asserts a long-felt, expensive problem (>$500K transponders, need for rapid reconfiguration), which, if substantiated at trial, could support non-obviousness. The related-family applications (13/369,704; 13/424,754) suggest a deliberate NASA development program rather than a predictable combination of existing pieces. Government ownership and the patent's 2025 lapse make secondary-consideration discovery unlikely in practice.

IX. Bottom line

• No combination of the five cited references renders claim 1 obvious with high confidence. The strongest colorable theory — Riverside '529 + Viasat '839 + StatSignal '511 — can reach claim 1 only by importing substantial PHOSITA "background knowledge" (CCSDS-on-FPGA implementation practice) that the references themselves never disclose, and it depends on the § 102(e) eligibility of Riverside. Its realistic strength is low-to-moderate, and it would likely fail on a developed record because of non-analogous-art and missing-limitation problems.
• A no-Riverside combination (Viasat '839/'628 + StatSignal + Qualcomm) is weak; the references are from non-analogous fields and the satellite in the Viasat disclosures is a bent pipe, not a telemetry processor.
• Claim 17 (single-FPGA micro-satellite system) is the most robust claim against § 103 over this record. The art is distributed by design and teaches away from single-FPGA consolidation; the "interchangeable FEC encoder embedded in a single FPGA performing all processing" limitation has no support in any cited reference.
• Dependent claims would likely stand or fall with their base claims; if anything, the protocol-specific and hardware-specific dependents (PIC M32, RS-422, Reed-Solomon/BCH/pseudo-randomization, 200 mW) add further non-obvious detail with no prior-art anchor.

Most likely § 103 assertion in practice: an IPR-style challenger would lead with Riverside '529 + Viasat '839, supplemented by expert testimony that FPGA/CCSDS/FEC implementation was conventional — attacking claim 1 (and dependents 2–7, 9–16) while tacitly conceding claim 17. Based on the available record, that challenge would face a serious risk of failing on motivation and on the missing CCSDS/FPGA-encoder/interface limitations. This is consistent with the file history: the examiner considered all five references and allowed all 26 claims, and no PTAB proceeding has ever tested them (see Proceedings section above).

Caveats: This analysis rests on the five cited references plus the level of ordinary skill; it does not canvass uncited art (e.g., CCSDS/FPGA transponder literature predating 2011) that a challenger could add. Riverside's full text was reviewed only via search excerpts, and its § 102(e) status depends on unverified conception dates. For a complete validity picture, a search beyond the examiner's citations would be required.