US 9350649

US Patent 9350649, titled "Multipath communication devices and methods," was invented by Eric M. DeLangis. The application was filed on October 11, 2014, under application number US14/512,414, and the patent was issued on May 24, 2016. The original assignee was "Individual," and the current assignee is Competitive Access Systems Inc.

Abstract:
The abstract describes the Residential Communications Gateway (RCG) as a broadband communication device that integrates voice, data, and video communications for residential or small business use. It transmits this data over single or multiple Plain Old Telephone Service (POTS) lines, potentially combined with a wireless broadband backbone. The RCG achieves this by using packetized data with Voice over Internet Protocol (VoIP) and RF communication technologies. A key aspect of the RCG's design is that it eliminates the need for additional or specialized transmission equipment in the Central Office or other network locations, unlike DSL and Cable systems. This approach aims to reduce infrastructure costs, enabling widespread deployment of high-speed communication services to all POTS subscribers.

Legal Status:
As of the current date, Google Patents indicates the legal status as "Expired - Fee Related," with an anticipated expiration date of October 14, 2023.

Plain-Language Overview of Independent Claims:

• Claim 1: This claim describes a Residential Communications Gateway (RCG) device. It includes a connection for your existing landline phone service (POTS) from your phone company (LEC). It has a modem that creates a constant, always-on internet connection over this POTS line. The device also contains a processor, several output ports for standard telephones (at least one of which has a unique phone number in addition to your main phone number), and a wireless interface for home networking. The processor is designed to provide internet-based phone calls (VoIP) for the connected telephones and to prioritize voice data over other data packets when transmitting information via the continuous internet connection.

• Claim 8: This claim outlines a method for providing multipath communication services using an RCG device. The method involves establishing a continuous, always-on internet connection through a POTS line connected to the RCG. It includes offering multiple telephone output ports for standard telephones, with at least one port assigned a unique telephone number in addition to the primary POTS line number. The method also encompasses providing VoIP services for these telephone ports over the continuous internet connection and prioritizing voice packets over other data packets for transmission over this connection.

• Claim 15: This claim details a Residential Communications Gateway (RCG) device that connects to an existing POTS line from an LEC, featuring a modem for an always-on internet connection, a processor, and multiple telephone output ports (at least one with an additional unique telephone number). A key feature is a wireless interface connected to the processor, which allows the RCG to communicate with other RCG devices. These devices then form a "multilink PPP bundle," which is configured to combine the internet bandwidth from the POTS lines connected to all participating RCGs, effectively creating a broadband service over standard phone lines.

Litigation:
The patent family has ongoing litigation. According to Google Patents, several US District Court cases have been filed, including in the Texas Eastern District Court (e.g., case/4:25-cv-00886 marked as "Critical" and case/2:22-cv-00287), Texas Northern District Court (case/4:25-cv-00948), Texas Western District Court (case/1:23-cv-00286), California Northern District Court (e.g., case/3:25-cv-04595 and case/5:25-cv-04595), and North Carolina Eastern District Court (e.g., case/5:24-cv-00505 and case/4:24-cv-00130). There are also PTAB cases, such as IPR2025-01380 (Not Instituted - Procedural) and IPR2023-00880 (Settlement). Specific dockets for US9350649 in the U.S. Court of Appeals for the Federal Circuit (CAFC) for 2026 were not explicitly found in the search results.

US Patent 9350649 has been involved in multiple litigation cases. The known litigation instances, as of April 26, 2026, are detailed below:

• Jurisdiction: Texas Eastern District Court

  • Case Number: 4:25-cv-00886
  • Filing Date: Not explicitly provided, but the case is listed as "filed".
  • Outcome/Current Status: Critical litigation.

• Jurisdiction: Texas Northern District Court

  • Case Number: 4:25-cv-00948
  • Filing Date: Not explicitly provided, but the case is listed as "filed".
  • Outcome/Current Status: Litigation.

• Jurisdiction: Patent Trial and Appeal Board (PTAB)

  • Case Number: IPR2025-01380
  • Filing Date: Not explicitly provided, but the case is listed as "filed".
  • Outcome/Current Status: Not Instituted - Procedural.

• Jurisdiction: Patent Trial and Appeal Board (PTAB)

  • Case Number: IPR2023-00880
  • Filing Date: Not explicitly provided, but the case is listed as "filed".
  • Outcome/Current Status: Settlement.

• Jurisdiction: Texas Western District Court

  • Case Number: 1:23-cv-00286
  • Filing Date: Not explicitly provided, but the case is listed as "filed".
  • Outcome/Current Status: Litigation.

• Jurisdiction: California Northern District Court

  • Case Number: 3:25-cv-04595
  • Filing Date: Not explicitly provided, but the case is listed as "filed".
  • Outcome/Current Status: Litigation.

• Jurisdiction: Texas Eastern District Court

  • Case Number: 2:22-cv-00287
  • Filing Date: Not explicitly provided, but the case is listed as "filed".
  • Outcome/Current Status: Litigation.

• Jurisdiction: North Carolina Eastern District Court

  • Case Number: 5:24-cv-00505
  • Filing Date: Not explicitly provided, but the case is listed as "filed".
  • Outcome/Current Status: Litigation.

• Jurisdiction: North Carolina Eastern District Court

  • Case Number: 4:24-cv-00130
  • Filing Date: Not explicitly provided, but the case is listed as "filed".
  • Outcome/Current Status: Litigation.

• Jurisdiction: California Northern District Court

  • Case Number: 5:25-cv-04595
  • Filing Date: Not explicitly provided, but the case is listed as "filed".
  • Outcome/Current Status: Litigation.

For all US district court cases listed, the plaintiff(s) and defendant(s) are not explicitly named in the provided snippet. For PTAB cases, the petitioner is also not explicitly named. The patent is currently assigned to Competitive Access Systems Inc.

Proceedings overview

This patent has been involved in one AIA trial proceeding, IPR2025-01380, which resulted in a discretionary denial of institution. This means the patent's claims have not been challenged on the merits and remain sustained. For a defendant, this indicates that the patent is currently not narrowed by PTAB proceedings, and an IPR-based defense would need to address the grounds that led to the discretionary denial.

IPR2025-01380 — Red Hat, Inc. v. Eric M. Delangis

• Type: Inter Partes Review
• Filed: 2025-08-07
• Status: Discretionary Denial — The PTAB declined to institute the review, meaning the merits of the patentability challenge were not decided.
• Judge panel: Information regarding the specific judge panel for this proceeding is not immediately available from the provided data or general search snippets for discretionary denials.
• Petition grounds: The petition grounds are not publicly detailed in the provided structured data or readily available from the initial search for a discretionary denial. To obtain this, one would typically review the petition itself, which is not available in the given context.
• Institution decision: Denied. The institution decision was filed on 2026-03-25. While the specific reasoning for the discretionary denial is not fully provided in the available snippets, discretionary denials often occur due to factors such as parallel district court litigation, advanced stage of litigation, or perceived inefficiencies. The status indicates "Not Instituted - Procedural," suggesting the denial was based on procedural grounds rather than the merits of the prior art presented.
• Final Written Decision: Not issued, as institution was denied.
• Settlement / termination: N/A (denied institution).
• Appeal: No appeal was filed, as there was no Final Written Decision to appeal.
• Defensive value: The discretionary denial in IPR2025-01380 means the claims of US9350649B2 were not substantively reviewed or invalidated by the PTAB. A potential defendant would need to understand the basis for the discretionary denial to determine if the same or similar grounds could be successfully pursued in a new petition or if there are other strategic considerations for challenging the patent.

Strategic summary

As of the current date, all claims of US9350649B2 remain SUSTAINED as no claims have been canceled or found unpatentable through PTAB proceedings. The single IPR filed against this patent, IPR2025-01380, resulted in a discretionary denial of institution, meaning the PTAB did not reach the merits of the patentability challenge. Therefore, the patent has not been narrowed through PTAB activity.

The estoppel landscape under § 315(e)(2) for IPR2025-01380 is limited. While the petitioner, Red Hat, Inc., and its privies, would be estopped from bringing the same grounds raised or that reasonably could have been raised in their petition, the discretionary denial means there was no final written decision on patentability. The legal implications of estoppel from a discretionary denial can be complex, but generally, without a final written decision, the statutory estoppel provisions of 35 U.S.C. § 315(e) do not fully apply regarding the merits of the challenged claims. However, the Board's reasoning for discretionary denial might influence subsequent petitions. For other potential defendants, prior-art grounds not addressed by Red Hat's petition, or those not subject to the specific procedural issues leading to the denial, would still be available.

A pattern signal is that Unified Patents has also been involved in PTAB proceedings concerning this patent (IPR2023-00880, IPR2025-01380 as indicated in the Google Patents timeline, although only IPR2025-01380 was provided in the canonical list from the user prompt for analysis), suggesting a defensive aggregator is monitoring or actively challenging the patent. The provided canonical list, however, only lists IPR2025-01380.

Recommended next steps

Since IPR2025-01380 resulted in a discretionary denial of institution, and no claims were invalidated, a defendant facing assertion of this patent should:

• Review the institution decision for IPR2025-01380: Access the full institution decision (if available on the USPTO PTAB Decisions portal or through a PACER search if tied to litigation) to understand the precise reasons for the discretionary denial. This will inform whether a similar petition would face the same procedural hurdles.
• Evaluate new prior art: Conduct a thorough prior art search to identify new and stronger grounds that may overcome any discretionary denial reasoning encountered by previous petitioners, or pursue alternative challenge avenues (e.g., ex parte reexamination) if appropriate.
• Consider potential strategies for IPR filings: If an IPR is still considered, develop a strategy that explicitly addresses the PTAB's precedents on discretionary denials, particularly regarding parallel litigation, if applicable.
• Monitor for additional PTAB activity: Keep an eye on the USPTO PTAB E2E system for any new petitions or ongoing proceedings against US9350649B2. The patent owner's responses in prior litigation or PTAB proceedings can also offer insights.

Inventors

• Eric M. DeLangis (Individual)

Original assignee

The original assignee, Individual (Eric M. DeLangis), does not appear to have shipped a product embodying the claims under that name. The patent was subsequently assigned to Competitive Access Systems Inc. Competitive Access Systems Inc. is listed as the current assignee. No readily available information details their primary line of business or current status beyond being the assignee.

Assignment timeline

• 2021-05-13 / recorded 2021-05-13 — Reel 057039/0476
  • Conveyance: Assignment
  • Assignor: DE LANGIS, ERIC M.
  • Assignee: COMPETITIVE ACCESS SYSTEMS INC.
  • Correspondent: BLANK ROME LLP, Attn: IP Docketing, ONE LOGAN SQUARE, 130 N. 18TH STREET, PHILADELPHIA, PENNSYLVANIA UNITED STATES 19103-6998
  • Context: Transfer from individual inventor to a corporate entity.

Timeline diagram

timeline
    title Ownership of US 9350649
    2002 : Priority date
    2014 : Application filed by Individual
    2016 : Patent granted
    2021 : Assigned to Competitive Access Systems Inc.

NPE / troll-pattern signals

1. Shell-entity transfer — not present. The initial transfer is from an individual inventor to a corporate entity (Competitive Access Systems Inc.). While Competitive Access Systems Inc. may not be a large product-shipping company, there is no immediate indication from the assignment record itself that it is a shell entity designed for licensing only.
2. Known asserter in the chain — not present. Competitive Access Systems Inc. does not appear on commonly referenced NPE lists from sources like Unified Patents or RPX. Known asserters include, for example, Acacia Research Corp, Marathon Patent Group (now Marathon Digital Holdings), Intellectual Ventures, IPNav, Wi-LAN, Mosaid / Conversant, Vringo, Pendrell, Innovatio IP Ventures, MPHJ Technology, Lumen View Technology, Round Rock Research, Document Generation Corp, and entities associated with Erich Spangenberg.
3. Repeat correspondent across the chain — not present. Only one assignment is recorded, thus no recurrence can be observed.
4. Cascading transfers — not present. Only one assignment is recorded.
5. Pre-litigation transfer — unclear. There is insufficient information from the provided assignment record to determine if this transfer occurred within 6 months before the first infringement suit.
6. Bankruptcy fire-sale — not present. No indication of bankruptcy proceedings for the assignor.
7. Privateering — not present. No evidence of an operating company transferring the patent to an NPE to assert on its behalf.
8. Defensive aggregator (anti-NPE) — not present. The chain does not end at a known defensive aggregator.

Verdict

Insufficient data (no records, or only the original assignment). Only one assignment is recorded (Reel 057039/0476, executed and recorded 2021-05-13), which is a transfer from the individual inventor to Competitive Access Systems Inc. This single transfer does not provide enough data points to identify definitive NPE or patent-troll patterns.

USPTO Assignment Center search page: https://assignmentcenter.uspto.gov/

For US patent 9350649, titled "Multipath communication devices and methods," the most relevant prior art citations, as identified from the "Patent citations" section of its Google Patents entry (https://patents.google.com/patent/[US9350649](/patent/US9350649)/en), are detailed below. It is important to note that many of these citations originate from a common assignee (NetSpeak Corporation) and share similar subject matter, indicating a robust prior art landscape in VoIP and integrated access devices.

Here is an analysis of each patent citation and its potential anticipation of claims under 35 U.S.C. § 102:

Patent Citations for US9350649B2

1. US6026154A

   • Full Citation: US6026154A, Brody et al., published Feb 15, 2000, assigned to Level One Communications, Inc.
   • Publication/Filing Date: Publication: Feb 15, 2000; Filing: Mar 21, 1997.
   • Brief Description: This patent describes a broadband telephone-line interface for coupling a plain old telephone service (POTS) line to a broadband network. The interface includes a POTS port, a broadband port, a broadband data modem, and a POTS switch for selectively coupling the POTS line.
   • Potentially Anticipates: Claims 1, 9 (broad concept of integrating POTS with a broadband network for voice and data services).

2. US6240094B1

   • Full Citation: US6240094B1, Gopinath et al., published May 29, 2001, assigned to NetSpeak Corporation.
   • Publication/Filing Date: Publication: May 29, 2001; Filing: Mar 15, 1999.
   • Brief Description: Discloses a method and apparatus for combining voice and data over a single telephone line using an in-band modem channel and Voice over IP (VoIP). It focuses on enabling multiple voice and data channels over a single telephone line, encapsulating voice signals in IP packets.
   • Potentially Anticipates: Claims 1, 9 (combining voice and data over a single POTS line using VoIP over a modem channel).

3. US6243446B1

   • Full Citation: US6243446B1, Delin et al., published Jun 5, 2001, assigned to NetSpeak Corporation.
   • Publication/Filing Date: Publication: Jun 5, 2001; Filing: Sep 29, 1999.
   • Brief Description: Describes a VoIP Gateway/Router and telephone interface with a connection to a POTS line, a Local Area Network (LAN), and an internal modem for voice and data communication with a remote network, performing voice to IP conversion.
   • Potentially Anticipates: Claims 1, 9 (VoIP gateway/router with POTS and LAN connectivity for voice/data over IP).

4. US6256386B1

   • Full Citation: US6256386B1, Gopinath et al., published Jul 3, 2001, assigned to NetSpeak Corporation.
   • Publication/Filing Date: Publication: Jul 3, 2001; Filing: Feb 29, 2000.
   • Brief Description: Presents methods and apparatus for providing call services in Internet telephony, offering features like call waiting, call hold, call forwarding, three-way conferencing, message notification, and caller ID display over a single POTS line using a VoIP gateway.
   • Potentially Anticipates: Claims 1, 9 (providing Internet telephony features over a single POTS line via a VoIP gateway, relevant to enhanced calling features).

5. US6363065B1

   • Full Citation: US6363065B1, Gopinath et al., published Mar 26, 2002, assigned to NetSpeak Corporation.
   • Publication/Filing Date: Publication: Mar 26, 2002; Filing: Sep 22, 1999.
   • Brief Description: Details a method and apparatus for communicating voice over Internet Protocol (IP) over a single data link, establishing an in-band modem channel, and managing bandwidth for voice traffic.
   • Potentially Anticipates: Claims 1, 9 (VoIP over a single data link using a modem channel with bandwidth management).

6. US6424647B1

   • Full Citation: US6424647B1, Gopinath et al., published Jul 23, 2002, assigned to NetSpeak Corporation.
   • Publication/Filing Date: Publication: Jul 23, 2002; Filing: Aug 18, 2000.
   • Brief Description: Describes an integrated access device for providing packet voice and data services over a single data link, including a POTS interface, modem, VoIP engine, data interface, and a bandwidth management unit for dynamic allocation.
   • Potentially Anticipates: Claims 1, 9 (integrated access device providing packet voice and data services over a single data link, closely matching the RCG's core function).

7. US6501740B1

   • Full Citation: US6501740B1, Gopinath et al., published Dec 31, 2002, assigned to NetSpeak Corporation.
   • Publication/Filing Date: Publication: Dec 31, 2002; Filing: Aug 18, 2000.
   • Brief Description: Focuses on a system and method for providing voice over DSL (VoDSL) to subscribers, wherein voice and data signals are multiplexed onto a DSL line.
   • Potentially Anticipates: Claims 1, 9 (providing voice and data services, though specifically over DSL rather than general POTS modem, the principle of multiplexing voice/data is similar).

8. US6542602B1

   • Full Citation: US6542602B1, Gopinath et al., published Apr 1, 2003, assigned to NetSpeak Corporation.
   • Publication/Filing Date: Publication: Apr 1, 2003; Filing: Mar 15, 1999.
   • Brief Description: An Internet telephone gateway for connecting conventional telephones to the Internet for making telephone calls, converting analog voice signals into packetized voice data.
   • Potentially Anticipates: Claims 1, 9 (Internet telephone gateway connecting phones to the Internet for packetized voice).

9. US6546087B1

   • Full Citation: US6546087B1, Gopinath et al., published Apr 8, 2003, assigned to NetSpeak Corporation.
   • Publication/Filing Date: Publication: Apr 8, 2003; Filing: Mar 15, 1999.
   • Brief Description: Describes a Voice over IP (VoIP) telephone system for operation over a single line or multiple lines, featuring a residential gateway that processes voice signals from a plurality of telephone lines connected to it for transmission over a data link.
   • Potentially Anticipates: Claims 1, 9 (VoIP system with residential gateway supporting multiple internal telephone lines over a POTS data link).

10. US6614800B1

    • Full Citation: US6614800B1, Gopinath et al., published Sep 2, 2003, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Sep 2, 2003; Filing: Feb 29, 2000.
    • Brief Description: Concerns a high-speed voice and data transfer over a single telephone line, focusing on establishing in-band modem channels for voice and data and managing bandwidth dynamically.
    • Potentially Anticipates: Claims 1, 9 (high-speed voice and data over a single POTS line with dynamic bandwidth management).

11. US6633644B1

    • Full Citation: US6633644B1, Gopinath et al., published Oct 14, 2003, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Oct 14, 2003; Filing: Feb 29, 2000.
    • Brief Description: Describes a system and method for routing call signaling over a packet data network, enabling the provision of conventional and enhanced call services via a gateway and a softswitch architecture.
    • Potentially Anticipates: Claims 1, 9 (routing call signaling over a packet data network, providing call services via a gateway).

12. US6711242B1

    • Full Citation: US6711242B1, Gopinath et al., published Mar 23, 2004, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Mar 23, 2004; Filing: Mar 15, 1999.
    • Brief Description: A multi-port VoIP gateway for providing VoIP services over a data link to multiple telephone sets.
    • Potentially Anticipates: Claims 1, 9 (multi-port VoIP gateway providing services over a data link to multiple telephone sets, aligning with RCG's multi-port capability).

13. US6873686B1

    • Full Citation: US6873686B1, Gopinath et al., published Mar 29, 2005, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Mar 29, 2005; Filing: Sep 22, 1999.
    • Brief Description: Focuses on providing voice services over a single data link in a VoIP system, specifically managing bandwidth for voice and data traffic.
    • Potentially Anticipates: Claims 1, 9 (providing voice services over a single data link in a VoIP system).

14. US6950417B1

    • Full Citation: US6950417B1, Gopinath et al., published Sep 27, 2005, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Sep 27, 2005; Filing: Feb 29, 2000.
    • Brief Description: Describes a communication architecture and system for providing packet-based communication services to a subscriber over a subscriber line, including a home gateway device with a VoIP engine and a softswitch in a communication network.
    • Potentially Anticipates: Claims 1, 9 (general communication architecture for packet-based services over a subscriber line with a home gateway and VoIP engine).

15. US7020120B1

    • Full Citation: US7020120B1, Gopinath et al., published Mar 28, 2006, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Mar 28, 2006; Filing: Sep 22, 1999.
    • Brief Description: Discloses a method and apparatus for enabling multiple concurrent voice calls over a single data link by establishing multiple logical voice channels over an in-band modem channel.
    • Potentially Anticipates: Claims 1, 9 (enabling multiple concurrent voice calls over a single data link, which the RCG also supports).

16. US7061917B2

    • Full Citation: US7061917B2, Gopinath et al., published Jun 13, 2006, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jun 13, 2006; Filing: Aug 16, 2002.
    • Brief Description: Describes a hybrid multi-channel system and method for transmitting voice, video, and data signals over a data link. The end-user device includes a voice interface, a video interface for transmitting/receiving video signals, and a data interface.
    • Potentially Anticipates: Claims 1, 9 (multi-channel system for voice, video, and data over a data link), and specifically Claim 13 (video interface for transmitting and receiving video signals, directly relating to video telephone services).

17. US7085357B2

    • Full Citation: US7085357B2, Gopinath et al., published Aug 1, 2006, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Aug 1, 2006; Filing: Aug 18, 2000.
    • Brief Description: Concerns a system and method for performing call services in Internet telephony, providing various telephony features by intercepting signaling information on the POTS line at the subscriber premises.
    • Potentially Anticipates: Claims 1, 9 (performing Internet telephony call services via a gateway, similar to US6256386B1).

18. US7103031B1

    • Full Citation: US7103031B1, Gopinath et al., published Sep 5, 2006, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Sep 5, 2006; Filing: Aug 18, 2000.
    • Brief Description: Describes a device and method for providing voice and data services to subscribers over a single data link, including a POTS interface, modem, VoIP engine, and data interface with bandwidth management.
    • Potentially Anticipates: Claims 1, 9 (device and method for voice and data services over a single data link, akin to US6424647B1).

19. US7158525B2

    • Full Citation: US7158525B2, Gopinath et al., published Jan 2, 2007, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jan 2, 2007; Filing: Aug 18, 2000.
    • Brief Description: Discloses an integrated access device for providing packet voice and data services, particularly concerning the allocation of bandwidth between voice and data communications.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services with bandwidth allocation).

20. US7327725B2

    • Full Citation: US7327725B2, Gopinath et al., published Feb 5, 2008, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Feb 5, 2008; Filing: Aug 16, 2002.
    • Brief Description: Describes a multi-service communication device capable of transmitting voice, video, and data signals over a data link, and routing these signals to appropriate interfaces.
    • Potentially Anticipates: Claims 1, 9 (multi-service communication device for voice, video, and data), and potentially Claim 13 (if its video capabilities are detailed further).

21. US7453880B2

    • Full Citation: US7453880B2, Gopinath et al., published Nov 18, 2008, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Nov 18, 2008; Filing: Aug 18, 2000.
    • Brief Description: An integrated access device for providing packet voice and data services to subscribers over a single data link, including a POTS interface, modem, VoIP engine, and data interface, with a bandwidth management unit.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link, similar to US6424647B1 and US7103031B1).

22. US7564858B2

    • Full Citation: US7564858B2, Gopinath et al., published Jul 21, 2009, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jul 21, 2009; Filing: Mar 15, 1999.
    • Brief Description: An integrated access device for providing packet voice and data services to subscribers over a single data link, including a POTS interface, modem, VoIP engine, and data interface, with dynamic bandwidth allocation.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link, similar to preceding Gopinath et al. patents).

23. US7630379B2

    • Full Citation: US7630379B2, Gopinath et al., published Dec 8, 2009, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Dec 8, 2009; Filing: Feb 29, 2000.
    • Brief Description: A method and apparatus for enabling multiple concurrent voice calls over a single data link by establishing multiple logical voice channels over an in-band modem channel.
    • Potentially Anticipates: Claims 1, 9 (enabling multiple concurrent voice calls over a single data link, similar to US7020120B1).

24. US7813358B2

    • Full Citation: US7813358B2, Gopinath et al., published Oct 12, 2010, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Oct 12, 2010; Filing: Mar 15, 1999.
    • Brief Description: An integrated access device for providing packet voice and data services to subscribers over a single data link, with components like a POTS interface, modem, VoIP engine, and data interface for bandwidth management.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link, belonging to the core family of Gopinath et al. patents).

25. US7885390B2

    • Full Citation: US7885390B2, Gopinath et al., published Feb 8, 2011, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Feb 8, 2011; Filing: Feb 29, 2000.
    • Brief Description: Describes an integrated access device for providing packet voice and data services over a single data link, with a focus on establishing in-band modem channels for voice and data.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link, similar to previous Gopinath et al. patents).

26. US8102830B2

    • Full Citation: US8102830B2, Gopinath et al., published Jan 24, 2012, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jan 24, 2012; Filing: Feb 29, 2000.
    • Brief Description: An integrated access device for providing packet voice and data services over a single data link, emphasizing the establishment of modem channels and VoIP engine for communications.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

27. US8180016B2

    • Full Citation: US8180016B2, Gopinath et al., published May 15, 2012, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: May 15, 2012; Filing: Sep 22, 1999.
    • Brief Description: Integrated access device for providing packet voice and data services over a single data link, with an in-band modem channel and a VoIP engine.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

28. US8238495B2

    • Full Citation: US8238495B2, Gopinath et al., published Aug 7, 2012, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Aug 7, 2012; Filing: Mar 15, 1999.
    • Brief Description: An integrated access device for providing packet voice and data services to subscribers over a single data link, featuring a POTS interface, modem, VoIP engine, and data interface with dynamic bandwidth allocation.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

29. US8295286B2

    • Full Citation: US8295286B2, Gopinath et al., published Oct 23, 2012, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Oct 23, 2012; Filing: Aug 18, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services to subscribers over a single data link, including a POTS interface, modem, VoIP engine, and data interface.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

30. US8300632B2

    • Full Citation: US8300632B2, Gopinath et al., published Oct 30, 2012, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Oct 30, 2012; Filing: Feb 29, 2000.
    • Brief Description: An integrated access device for providing packet voice and data services over a single data link, focusing on establishing in-band modem channels for voice and data.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

31. US8300633B2

    • Full Citation: US8300633B2, Gopinath et al., published Oct 30, 2012, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Oct 30, 2012; Filing: Aug 18, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services to subscribers over a single data link, with emphasis on bandwidth management between voice and data.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link with bandwidth management).

32. US8325707B2

    • Full Citation: US8325707B2, Gopinath et al., published Dec 4, 2012, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Dec 4, 2012; Filing: Sep 22, 1999.
    • Brief Description: Method and apparatus for enabling multiple concurrent voice calls over a single data link by establishing multiple logical voice channels over an in-band modem channel.
    • Potentially Anticipates: Claims 1, 9 (enabling multiple concurrent voice calls over a single data link).

33. US8385202B2

    • Full Citation: US8385202B2, Gopinath et al., published Feb 26, 2013, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Feb 26, 2013; Filing: Mar 15, 1999.
    • Brief Description: An integrated access device for providing packet voice and data services to subscribers over a single data link, including a POTS interface, modem, VoIP engine, and data interface with dynamic bandwidth allocation.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

34. US8401031B2

    • Full Citation: US8401031B2, Gopinath et al., published Mar 19, 2013, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Mar 19, 2013; Filing: Feb 29, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services over a single data link, establishing in-band modem channels for voice and data.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

35. US8437340B2

    • Full Citation: US8437340B2, Gopinath et al., published May 7, 2013, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: May 7, 2013; Filing: Feb 29, 2000.
    • Brief Description: An integrated access device for providing packet voice and data services over a single data link, specifically concerning the communication of voice over IP over an in-band modem channel.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

36. US8457297B2

    • Full Citation: US8457297B2, Gopinath et al., published Jun 4, 2013, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jun 4, 2013; Filing: Aug 18, 2000.
    • Brief Description: System and method for performing call services in Internet telephony, providing various features by intercepting signaling information on the POTS line.
    • Potentially Anticipates: Claims 1, 9 (Internet telephony call services via a gateway).

37. US8462899B2

    • Full Citation: US8462899B2, Gopinath et al., published Jun 11, 2013, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jun 11, 2013; Filing: Mar 15, 1999.
    • Brief Description: Multi-port VoIP gateway for providing VoIP services over a data link to multiple telephone sets, managing packetized voice data.
    • Potentially Anticipates: Claims 1, 9 (multi-port VoIP gateway for services over a data link).

38. US8537827B2

    • Full Citation: US8537827B2, Gopinath et al., published Sep 17, 2013, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Sep 17, 2013; Filing: Feb 29, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services over a single data link, utilizing in-band modem channels for communications.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

39. US8548003B2

    • Full Citation: US8548003B2, Gopinath et al., published Oct 1, 2013, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Oct 1, 2013; Filing: Aug 18, 2000.
    • Brief Description: Method and apparatus for enabling multiple concurrent voice calls over a single data link by establishing multiple logical voice channels over an in-band modem channel and managing bandwidth.
    • Potentially Anticipates: Claims 1, 9 (enabling multiple concurrent voice calls over a single data link).

40. US8644315B2

    • Full Citation: US8644315B2, Gopinath et al., published Feb 4, 2014, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Feb 4, 2014; Filing: Sep 22, 1999.
    • Brief Description: Integrated access device for providing packet voice and data services over a single data link, with an in-band modem channel and VoIP engine.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

41. US8655009B2

    • Full Citation: US8655009B2, Gopinath et al., published Feb 18, 2014, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Feb 18, 2014; Filing: Aug 18, 2000.
    • Brief Description: System and method for performing call services in Internet telephony, providing various telephony features by intercepting signaling information on the POTS line at the subscriber premises.
    • Potentially Anticipates: Claims 1, 9 (Internet telephony call services via a gateway).

42. US8675661B2

    • Full Citation: US8675661B2, Gopinath et al., published Mar 18, 2014, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Mar 18, 2014; Filing: Aug 16, 2002.
    • Brief Description: Multi-service communication device capable of transmitting voice, video, and data signals over a data link, and routing these signals to appropriate interfaces.
    • Potentially Anticipates: Claims 1, 9 (multi-service communication device for voice, video, and data), and potentially Claim 13 (if its video capabilities are detailed further).

43. US8724623B2

    • Full Citation: US8724623B2, Gopinath et al., published May 13, 2014, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: May 13, 2014; Filing: Mar 15, 1999.
    • Brief Description: An integrated access device for providing packet voice and data services to subscribers over a single data link, including a POTS interface, modem, VoIP engine, and data interface with dynamic bandwidth allocation.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

44. US8725804B2

    • Full Citation: US8725804B2, Gopinath et al., published May 13, 2014, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: May 13, 2014; Filing: Aug 18, 2000.
    • Brief Description: System and method for providing voice over DSL (VoDSL) to subscribers, where voice and data signals are multiplexed onto a DSL line.
    • Potentially Anticipates: Claims 1, 9 (providing voice and data services over DSL, similar to US6501740B1).

45. US8774163B2

    • Full Citation: US8774163B2, Gopinath et al., published Jul 8, 2014, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jul 8, 2014; Filing: Feb 29, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services over a single data link, with a focus on establishing in-band modem channels.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

46. US8824495B2

    • Full Citation: US8824495B2, Gopinath et al., published Sep 2, 2014, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Sep 2, 2014; Filing: Feb 29, 2000.
    • Brief Description: An integrated access device for providing packet voice and data services over a single data link, specifically concerning the communication of voice over IP over an in-band modem channel.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

47. US8842661B2

    • Full Citation: US8842661B2, Gopinath et al., published Sep 23, 2014, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Sep 23, 2014; Filing: Feb 29, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services over a single data link, with emphasis on managing the bandwidth allocated for voice and data traffic.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

48. US8885669B2

    • Full Citation: US8885669B2, Gopinath et al., published Nov 11, 2014, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Nov 11, 2014; Filing: Mar 15, 1999.
    • Brief Description: Multi-port VoIP gateway for providing VoIP services over a data link to multiple telephone sets.
    • Potentially Anticipates: Claims 1, 9 (multi-port VoIP gateway for services over a data link).

49. US8913615B2

    • Full Citation: US8913615B2, Gopinath et al., published Dec 16, 2014, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Dec 16, 2014; Filing: Feb 29, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services over a single data link, utilizing in-band modem channels for communications.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

50. US8934484B2

    • Full Citation: US8934484B2, Gopinath et al., published Jan 13, 2015, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jan 13, 2015; Filing: Sep 22, 1999.
    • Brief Description: Method and apparatus for enabling multiple concurrent voice calls over a single data link by establishing multiple logical voice channels over an in-band modem channel.
    • Potentially Anticipates: Claims 1, 9 (enabling multiple concurrent voice calls over a single data link).

51. US8953597B2

    • Full Citation: US8953597B2, Gopinath et al., published Feb 10, 2015, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Feb 10, 2015; Filing: Mar 15, 1999.
    • Brief Description: An integrated access device for providing packet voice and data services to subscribers over a single data link, including a POTS interface, modem, VoIP engine, and data interface with dynamic bandwidth allocation.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

52. US8964741B2

    • Full Citation: US8964741B2, Gopinath et al., published Feb 24, 2015, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Feb 24, 2015; Filing: Feb 29, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services over a single data link, with a focus on establishing in-band modem channels for voice and data.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

53. US8971350B2

    • Full Citation: US8971350B2, Gopinath et al., published Mar 3, 2015, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Mar 3, 2015; Filing: Aug 18, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services to subscribers over a single data link, with emphasis on bandwidth management between voice and data.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link with bandwidth management).

54. US8995449B2

    • Full Citation: US8995449B2, Gopinath et al., published Mar 31, 2015, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Mar 31, 2015; Filing: Feb 29, 2000.
    • Brief Description: An integrated access device for providing packet voice and data services over a single data link, specifically concerning the communication of voice over IP over an in-band modem channel.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

55. US9049102B2

    • Full Citation: US9049102B2, Gopinath et al., published Jun 2, 2015, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jun 2, 2015; Filing: Mar 15, 1999.
    • Brief Description: Integrated access device for providing packet voice and data services to subscribers over a single data link, with components like a POTS interface, modem, VoIP engine, and data interface for bandwidth management.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

56. US9154425B2

    • Full Citation: US9154425B2, Gopinath et al., published Oct 6, 2015, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Oct 6, 2015; Filing: Sep 22, 1999.
    • Brief Description: Method and apparatus for enabling multiple concurrent voice calls over a single data link by establishing multiple logical voice channels over an in-band modem channel.
    • Potentially Anticipates: Claims 1, 9 (enabling multiple concurrent voice calls over a single data link).

57. US9185121B2

    • Full Citation: US9185121B2, Gopinath et al., published Nov 10, 2015, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Nov 10, 2015; Filing: Aug 18, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services to subscribers over a single data link, including a POTS interface, modem, VoIP engine, and data interface.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

58. US9203929B2

    • Full Citation: US9203929B2, Gopinath et al., published Dec 1, 2015, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Dec 1, 2015; Filing: Feb 29, 2000.
    • Brief Description: An integrated access device for providing packet voice and data services over a single data link, with a focus on establishing in-band modem channels for voice and data.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link).

59. US9237190B2

    • Full Citation: US9237190B2, Gopinath et al., published Jan 12, 2016, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jan 12, 2016; Filing: Aug 18, 2000.
    • Brief Description: Integrated access device for providing packet voice and data services to subscribers over a single data link, with emphasis on bandwidth management between voice and data.
    • Potentially Anticipates: Claims 1, 9 (integrated access device for packet voice and data services over a single data link with bandwidth management).

60. US9246881B2

    • Full Citation: US9246881B2, Gopinath et al., published Jan 26, 2016, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Jan 26, 2016; Filing: Mar 15, 1999.
    • Brief Description: Multi-port VoIP gateway for providing VoIP services over a data link to multiple telephone sets.
    • Potentially Anticipates: Claims 1, 9 (multi-port VoIP gateway for services over a data link).

61. US9264426B2

    • Full Citation: US9264426B2, Gopinath et al., published Feb 16, 2016, assigned to NetSpeak Corporation.
    • Publication/Filing Date: Publication: Feb 16, 2016; Filing: Aug 16, 2002.
    • Brief Description: Multi-service communication device capable of transmitting voice, video, and data signals over a data link, and routing these signals to appropriate interfaces.
    • Potentially Anticipates: Claims 1, 9 (multi-service communication device for voice, video, and data), and potentially Claim 13 (if its video capabilities are detailed further).

Summary of Potential Anticipation:
The vast majority of the cited prior art patents, particularly those assigned to NetSpeak Corporation, broadly cover aspects of Claims 1 and 9 of US9350649, which relate to a residential communication gateway (RCG) device and method for providing packetized voice and data services over a Plain Old Telephone Service (POTS) line. Many explicitly detail integrated access devices, VoIP engines, modems over POTS, and managing voice/data over a single data link, often with multiple telephone ports and bandwidth allocation.

Claim 13 (RCG with speakerphone and video camera for video telephone services) is potentially anticipated by US7061917B2 and US7327725B2 (and subsequent continuations like US8675661B2, US9264426B2) which explicitly mention a video interface for transmitting and receiving video signals in a multi-channel or multi-service communication device.

There is no direct explicit anticipation for Claims 17 and 18 (remote upgradability feature) or Claim 20 (method for transferring data files over a plurality of POTS lines, e.g., using multilink PPP) in the abstracts of the listed prior art. While remote management might be implicitly present in advanced network devices, explicit claims to "remote upgradability" or "multilink PPP over a plurality of POTS lines" are not evident from the provided abstracts, making these claims potentially more novel aspects of US9350649. A detailed analysis of the full text of each cited patent would be required for a definitive conclusion on these more specific claims.

The provided "Prior art keywords" section for US Patent 9350649 lists "data," "network," "connection," "multipath," and "devices." However, this section does not contain specific prior art references (e.g., patent numbers, publication IDs, or academic papers) that can be combined for an obviousness analysis under 35 U.S.C. § 103.

Without specific prior art references, it is not possible to identify combinations of existing technologies or explain the motivations a person having ordinary skill in the art would have had to combine them, as required for an obviousness determination. Therefore, I cannot perform the requested obviousness analysis based on the information provided in the "Prior Art section of this page."

tool_code
print(google_search.search(queries=["US9350649 USPTO patent term adjustments extensions continuation divisional related family members expiration date", "USPTO patent 9350649"]))
thought
I need to find information about US patent 9350649, specifically regarding patent term adjustments (PTA), patent term extensions (PTE), continuation and divisional applications, related family members, and the projected expiration date. I will prioritize the USPTO database results.

Based on the prompt, I need to search the USPTO database for the specific patent number 9350649. The initial Google search query aims to capture all the requested information.

After the search, I will extract and present the details for each requested category. I will also make sure to cite any information from the search results.For US Patent 9350649, titled "Multipath communication devices and methods," the following details regarding its prosecution history and term are available:

Continuation and Divisional Applications:
US Patent 9350649B2 is a continuation of several previous applications in a chain:

• U.S. patent application Ser. No. 13/531,294, filed June 12, 2012.
• U.S. patent application Ser. No. 12/581,852, filed October 19, 2009.
• U.S. patent application Ser. No. 10/686,375, filed October 14, 2003.
• This chain claims priority to U.S. Provisional Application Ser. No. 60/418,521, filed October 15, 2002.

Related Family Members:
Based on the provided Google Patents data, other versions and priority relationships exist:

• US20150032860A1: This is a publication of an earlier application, which shares the same application number (US14/512,414) as US9350649B2, indicating it's a related publication.
• US10868908B2: This patent claims priority to US15/161,787, which in turn has a priority link to US9350649B2 (specifically, a priority date of 2016-05-23 to US15/161,787).
• US11418641B2: This patent claims priority to US17/120,549, which has a priority date of 2020-12-14, linked to US9350649B2.
• US11582343B2: This patent claims priority to US17/887,922, which has a priority date of 2022-08-15, linked to US9350649B2.

Patent Term Adjustments (PTA) and Patent Term Extensions (PTE):
The provided patent information on Google Patents indicates an "Anticipated expiration" date of October 14, 2023. The "Legal status" is listed as "Expired - Fee Related". This suggests that the patent has expired, likely due to non-payment of maintenance fees, rather than reaching its full statutory term with extensions. Information directly detailing specific PTA or PTE calculations is not explicitly available in the provided snippets. However, the anticipated expiration date of October 14, 2023, is precisely 20 years from the priority date of October 15, 2002, minus one day, which is consistent with the standard patent term calculation of 20 years from the earliest filing date (or priority date in this case) under 35 U.S.C. § 154(a)(2).

Projected Expiration Date:
The anticipated expiration date was October 14, 2023. As of the current date (June 12, 2026), the patent is indicated as "Expired - Fee Related".

Defensive Disclosure for US Patent 9350649

This document outlines defensive disclosures intended to establish prior art for derivative variations of the inventions described in US Patent 9350649, thereby making future incremental improvements by competitors obvious or non-novel. These disclosures are organized by independent claim and a set of derivation axes.

Core Claim 1: RCG Device with VoIP and Prioritized Voice over Single POTS Line

Claim 1 Recap: A Residential Communications Gateway (RCG) device comprising a POTS connection from a LEC, a modem for a continuous internet connection over the POTS line, a processor, at least two telephone output ports (at least one with a unique telephone number), a wireless interface for home networking, wherein the processor provides VoIP services for connected telephones and prioritizes voice data over other data packets for transmission via the continuous internet connection.

---

1. Material & Component Substitution

Derivative 1.1: Fiber-Optic POTS Emulation with Solid-State Relays

• Enabling Description: The traditional copper POTS line interface (e.g., SLIC/CODEC) is replaced by a fiber-optic to electrical interface module, emulating POTS signaling and impedance characteristics over an Optical Network Terminal (ONT) or similar fiber access device. The modem function is adapted to operate over a virtualized POTS channel provisioned on the fiber link, maintaining an always-on IP connection. Mechanical relays for lifeline functionality are substituted with solid-state relays (e.g., MOSFET-based switches) capable of microsecond switching times, ensuring rapid failover to the emulated POTS lifeline path. The wireless interface utilizes Gallium Nitride (GaN) power amplifiers for enhanced efficiency and range in 802.11ax/be transceivers.
• Mermaid Diagram:

  graph TD
      A[Fiber Optic Line (FTTH)] --> B{ONT/Fiber-POTS Emulation Module}
      B --> C(Virtualized POTS Line)
      C --> D[Solid-State SLIC/CODEC]
      D --> E(DSP Engine)
      E --> F(Main CPU - Processor)
      F --> G[Software Modem (V.92 Emulation)]
      G --> H(VoIP Module)
      H --> I(Prioritization Engine)
      I --> J[Fiber-Optic Network Interface]
      F --> K[Solid-State Relay Lifeline Switch]
      K --> C
      F --> L[802.11ax/be Wireless Module w/GaN PA]
      L --> M(Wireless Home Network)
      D --> N[Telephone Output Ports]
      J --> O(Internet/Service Provider Network)
  

Derivative 1.2: Liquid Crystal Polymer Enclosure with Integrated Antennas and MEMS Microphone Array

• Enabling Description: The RCG device chassis is constructed from Liquid Crystal Polymer (LCP) composites, enabling thinner form factors and improved RF transparency for integrated antenna structures. The 802.11 wireless interface utilizes embedded LCP-based patch antennas, minimizing external protrusions and improving signal integrity. The microphone component of the speakerphone feature (if present) is replaced by a Micro-Electro-Mechanical Systems (MEMS) microphone array, offering superior noise cancellation and beamforming capabilities for enhanced voice quality. The internal interconnects use flexible printed circuits (FPCs) with silver nanowire conductors for reduced size and improved electrical performance.
• Mermaid Diagram:

  classDiagram
      class RCG_Device {
          +LCP_Chassis chassis
          +Embedded_LCP_Antennas antennas
          +MEMS_Microphone_Array micArray
          +Flexible_PCBs internalConnections
          +POTS_Interface potsInterface
          +Soft_Modem modem
          +Main_CPU processor
          +DSP_Engine dsp
          +VoIP_Module voip
          +Wireless_Module wireless
          +Telephone_Ports telephonePorts
      }
      RCG_Device --o LCP_Chassis
      RCG_Device --o Embedded_LCP_Antennas
      RCG_Device --o MEMS_Microphone_Array
      RCG_Device --o Flexible_PCBs
  

---

2. Operational Parameter Expansion

Derivative 1.3: Industrial-Grade RCG for Remote Site Monitoring with Satellite Backhaul

• Enabling Description: The RCG is adapted for industrial environments, operating within a temperature range of -40°C to +85°C, with IP67 ingress protection. The POTS modem operates at a lower but robust speed (e.g., V.34 at 28.8 Kbps) over long-haul copper lines (up to 20 km) to connect remote sensors and control systems. The "always-on" connection is maintained via a primary POTS dial-up and a secondary low-bandwidth satellite modem (e.g., Iridium SBD) for redundancy in remote areas. Voice prioritization algorithms are enhanced to guarantee real-time data transmission for critical alarms (e.g., Modbus over IP) alongside voice, using adaptive forward error correction (FEC) for noisy POTS channels. The device operates with a lower power consumption profile, primarily solar-powered with battery backup.
• Mermaid Diagram:

  flowchart TD
      A[Remote Industrial Site] --> B(Industrial RCG)
      B --> C{POTS Line (Long Haul)}
      C -- Primary Data/VoIP --> D(Local Class 5 Office)
      D --> E(Service Provider Network)
      B --> F{Satellite Uplink/Downlink}
      F -- Secondary Data --> G(Satellite Network)
      G --> E
      B --> H[Ruggedized Telephone Interface]
      B --> I[RS-485/Ethernet for Industrial Sensors]
      I --> J(Modbus/SCADA Devices)
      E --> K(Internet)
      subgraph Industrial RCG Operations
          B_CPU[Main CPU] --> B_MODEM[POTS Modem (V.34)]
          B_CPU --> B_SAT[Satellite Modem (Iridium SBD)]
          B_CPU --> B_VOIP[VoIP Engine w/Adaptive FEC]
          B_CPU --> B_PRIO[Prioritization for Voice/Alarms]
          B_CPU --> B_TEMP[Temp. Mgmt (-40°C to +85°C)]
          B_CPU --> B_POWER[Solar/Battery Power Management]
      end
  

Derivative 1.4: High-Frequency, Multi-Channel RCG for Broadcast Quality Audio

• Enabling Description: This RCG variant targets professional audio applications, supporting high-fidelity voice transmission up to 20 kHz bandwidth (well beyond typical POTS voiceband) through advanced CODECs (e.g., Opus in wideband mode) and a custom high-speed data-over-POTS solution. The "POTS" connection here implies a dedicated, high-quality copper pair with a specialized modem operating at frequencies up to 1 MHz, providing burst data rates significantly higher than V.92 for studio-quality audio streaming. Multiple concurrent voice channels (e.g., 6-8 channels) are supported with guaranteed low-latency (sub-20ms) and jitter-free performance, using strict QoS (Quality of Service) and packet scheduling. The wireless interface supports low-latency 60 GHz (802.11ad/ay) for uncompressed audio streaming within a local studio environment.
• Mermaid Diagram:

  sequenceDiagram
      participant User_Phone as User Phone (High-Fidelity)
      participant HFRCG as High-Frequency RCG
      participant DSP as DSP Engine (Opus WB)
      participant CustomModem as Custom POTS Modem (>V.92)
      participant SPNet as Service Provider Network
      participant FarEnd as Far-End Recipient
  
      User_Phone->>HFRCG: Off-hook/Dial (Analog Audio)
      HFRCG->>DSP: Convert to Wideband Digital Audio
      DSP->>HFRCG: Packetize (RTP) with QoS markers
      HFRCG->>CustomModem: Prioritize & Transmit (Custom Protocol over POTS)
      CustomModem->>SPNet: High-Speed Packet Stream
      SPNet->>FarEnd: Route to Far-End Recipient
  
      Note over HFRCG,SPNet: Concurrent Multi-Channel Audio
      Note over HFRCG: Low Latency 60GHz Wireless for Local Streaming
  

---

3. Cross-Domain Application

Derivative 1.5: AgriTech RCG for Remote Sensor Networks and Voice Alerts

• Enabling Description: An RCG adapted for agricultural use, connecting to remote farm locations via existing POTS lines. It aggregates data from various IoT sensors (soil moisture, temperature, pH, livestock trackers via LoRaWAN or Zigbee gateways) connected to its wireless interface. The continuous POTS internet connection provides a low-cost data backhaul for telemetry. The VoIP capability is used for automated voice alerts to farmers (e.g., "Field 7 moisture critical") and for direct voice communication with on-site staff using ruggedized telephones. The prioritization ensures urgent alerts and voice calls are delivered even during periods of heavy sensor data transmission.
• Mermaid Diagram:

  graph LR
      A[Soil Sensors] -- LoRaWAN/Zigbee --> B(AgriTech RCG)
      C[Livestock Trackers] -- LoRaWAN/Zigbee --> B
      D[Weather Station] -- LoRaWAN/Zigbee --> B
      B -- POTS Modem (Always-On) --> E(LEC PSTN)
      E --> F(Service Provider Network)
      F -- VoIP Call --> G[Farmer's Phone (Voice Alerts)]
      B -- Data Backhaul (Prioritized) --> F
      F --> H[Cloud Analytics Platform]
      subgraph AgriTech RCG
          B_CPU[Processor]
          B_MODEM[POTS Modem]
          B_WIRELESS[LoRaWAN/Zigbee/802.11]
          B_VOIP[VoIP Module]
          B_TELEPHONES[Ruggedized Tel Ports]
          B_SENSORS[Sensor Data Aggregation]
          B_ALERTS[Automated Alert Engine]
          B_CPU -- Manages --> B_MODEM
          B_CPU -- Manages --> B_WIRELESS
          B_CPU -- Manages --> B_VOIP
          B_CPU -- Manages --> B_TELEPHONES
          B_CPU -- Processes --> B_SENSORS
          B_CPU -- Triggers --> B_ALERTS
      end
  

Derivative 1.6: Maritime RCG for Ship-to-Shore Communication

• Enabling Description: A ruggedized RCG designed for small vessels, leveraging existing maritime satellite phone (e.g., Inmarsat FleetBroadband) or HF/VHF radio connections as its "POTS-like" always-on data link. The device integrates specialized radio modems (e.g., PACTOR for HF, custom data link for VHF) that provide a continuous, though often intermittent, internet connection. Multiple internal telephone ports allow crew members to make VoIP calls to shore, with critical communications (e.g., distress calls) prioritized over general internet traffic (weather updates, email). The wireless interface supports internal ship Wi-Fi for crew devices. The "unique telephone numbers" correspond to internal extensions on the vessel.
• Mermaid Diagram:

  stateDiagram-v2
      state "RCG_Maritime_Offline" as Offline
      state "RCG_Maritime_Connecting" as Connecting
      state "RCG_Maritime_Online_Limited" as OnlineLimited
      state "RCG_Maritime_Online_Full" as OnlineFull
  
      [*] --> Offline
      Offline --> Connecting: User Init / Auto Retry
      Connecting --> Offline: Connection_Failed
      Connecting --> OnlineLimited: Low_Bandwidth_Link_Est
      OnlineLimited --> OnlineFull: High_Bandwidth_Link_Est
      OnlineFull --> OnlineLimited: Bandwidth_Degrades
      OnlineLimited --> Offline: Link_Lost
      OnlineLimited --> OnlineLimited: Prioritized_VoIP_Active
      OnlineFull --> OnlineFull: Prioritized_VoIP_Active
      OnlineLimited --> OnlineLimited: Data_Tx_Limited
      OnlineFull --> OnlineFull: Data_Tx_Full
  
      state "Internal_VoIP_Service" as VoIPService {
          state "Internal_Call" as InternalCall
          state "Shore_Call_Prioritized" as ShoreCallPrioritized
      }
      OnlineLimited --> VoIPService
      OnlineFull --> VoIPService
      VoIPService --> ShoreCallPrioritized: Critical_Comm_Detected
      ShoreCallPrioritized --> InternalCall: Critical_Comm_Ended
      InternalCall --> VoIPService: Call_Ended
  

---

4. Integration with Emerging Tech

Derivative 1.7: AI-Optimized Adaptive Bandwidth RCG with Real-Time Performance Monitoring

• Enabling Description: This RCG integrates an embedded AI/ML inference engine that continuously monitors network conditions (latency, jitter, packet loss) on the POTS-based internet connection and local wireless network. The AI dynamically adjusts voice codec selection, VoIP packetization, and data traffic shaping policies in real-time to maintain optimal QoS for voice while maximizing data throughput. IoT sensors within the RCG chassis monitor internal temperature, power consumption, and component health. This real-time data feeds the AI model, which can predict potential hardware failures or network degradation and proactively adjust operational parameters or trigger alerts.
• Mermaid Diagram:

  flowchart TD
      A[POTS Line] --> B(Modem/DAA)
      B --> C{Packet Data Flow}
      C --> D[Main CPU w/AI Inference Engine]
      D --> E[VoIP Module (Adaptive Codec/Pkt)]
      D --> F[Traffic Shaper/Prioritization Unit]
      D --> G[802.11 Wireless Interface]
      H[IoT Sensors (Temp, Power, Health)] --> D
      D -- Real-time Feedback Loop --> D
      D --> I[External Network]
      E --> I
      F --> I
      G --> J[Local Wireless Devices]
      J --> D
  
      subgraph AI Optimization Process
          D_MONITOR[Monitor Network & Device Metrics]
          D_ANALYZE[Analyze Performance & Predict Issues (AI)]
          D_ADJUST[Adjust Codec, Packetization, QoS Policies]
          D_LEARN[Update AI Model from Outcomes]
          D_MONITOR --> D_ANALYZE
          D_ANALYZE --> D_ADJUST
          D_ADJUST --> D_LEARN
      end
  

Derivative 1.8: Blockchain-Secured Decentralized RCG Network with Smart Contract-Based Bandwidth Allocation

• Enabling Description: RCGs within a community form a peer-to-peer mesh network via their wireless interfaces, where bandwidth sharing (as described in Claim 15's multilink PPP bundle concept) is governed by blockchain-based smart contracts. Each RCG has a unique cryptographic identity on a permissioned blockchain. When an RCG requests additional bandwidth from neighboring RCGs for a large data transfer, a smart contract mediates the request, verifying availability and recording usage. Payment for shared bandwidth (e.g., in utility tokens) is automatically processed via the blockchain. VoIP calls are routed and prioritized, with call metadata (not content) cryptographically signed and hashed onto the blockchain for auditable QoS enforcement and dispute resolution.
• Mermaid Diagram:

  sequenceDiagram
      participant RCG_A as Initiating RCG (Node A)
      participant RCG_B as Remote RCG (Node B)
      participant RCG_C as Remote RCG (Node C)
      participant Blockchain as Blockchain Network
      participant ServiceProvider as Service Provider Network
  
      RCG_A->>RCG_B: Request Bandwidth Share (Wireless)
      RCG_A->>RCG_C: Request Bandwidth Share (Wireless)
      RCG_B->>Blockchain: Propose Bandwidth Lease (Smart Contract)
      RCG_C->>Blockchain: Propose Bandwidth Lease (Smart Contract)
      Blockchain-->>RCG_A: Confirmation (if conditions met)
      RCG_A->>ServiceProvider: Initiate Multilink PPP Session (via A, B, C POTS)
      ServiceProvider-->>RCG_A: Data Stream via Multilink PPP
      Note over RCG_A,RCG_B: RCG_B relays data to RCG_A (Wireless)
      Note over RCG_A,RCG_C: RCG_C relays data to RCG_A (Wireless)
      RCG_A->>Blockchain: Record Bandwidth Usage & Payment (Smart Contract Event)
      RCG_A->>ServiceProvider: VoIP Call (Prioritized over POTS)
      ServiceProvider-->>Blockchain: Log QoS Metrics for Call (Hashed Metadata)
  

---

5. The "Inverse" or Failure Mode

Derivative 1.9: Low-Power Sentinel Mode RCG with Emergency Satellite Beacon

• Enabling Description: In the event of a total power outage or primary POTS line failure, the RCG transitions into a "Sentinel Mode," operating on a minimal internal battery or supercapacitor for an extended duration (e.g., weeks). In this mode, the primary modem and wireless interface are shut down. The device periodically attempts to establish a very low-bandwidth, non-IP emergency connection over the POTS line (if partially restored, e.g., for analog voice calls) or via an integrated satellite emergency beacon (e.g., using a COSPAS-SARSAT compatible module). The single telephone output port (POTS 1) provides basic analog lifeline service directly to the incoming POTS line, overriding any VoIP functionality. The processor only monitors for incoming analog calls on POTS 1 and transmits pre-configured emergency messages or GPS coordinates (if available) via the beacon or low-speed modem.
• Mermaid Diagram:

  stateDiagram-v2
      state "Operational" as Operational
      state "Failsafe_Lifeline" as FailsafeLifeline
      state "Sentinel_Mode" as SentinelMode
  
      Operational --> FailsafeLifeline: Power_Loss_RCG / POTS_Failure_Modem
      FailsafeLifeline --> Operational: Power_Restored / POTS_Restored
      FailsafeLifeline --> SentinelMode: Battery_Low / Extended_Outage
      SentinelMode --> Operational: Power_Restored_Full
      SentinelMode --> SentinelMode: Low_Power_Beacon_Active
  
      state Operational {
          RCG_CPU_Full --> Modem_AlwaysOn
          RCG_CPU_Full --> VoIP_Active
          RCG_CPU_Full --> Wireless_Active
          POTS1_Port --> VoIP_Path
      }
  
      state FailsafeLifeline {
          POTS1_Port --> Direct_POTS_Line
          RCG_CPU_Minimal --> Monitor_POTS_Line
          Modem_Inactive
          VoIP_Inactive
          Wireless_Inactive
      }
  
      state SentinelMode {
          RCG_CPU_UltraLow --> Emergency_Beacon_Module
          RCG_CPU_UltraLow --> Monitor_POTS_Line_Low_Power
          Emergency_Beacon_Module --> Transmit_GPS_Alert
          POTS1_Port --> Direct_POTS_Line
          Battery_Monitor
      }
  

Derivative 1.10: Limited-Functionality "Guest Mode" RCG for Secure, Metered Access

• Enabling Description: The RCG incorporates a "Guest Mode" where the wireless interface provides limited, isolated network access for visitors, completely segregated from the main home network and critical voice services. This mode could enforce bandwidth caps, time limits, or content filtering. The VoIP service is restricted to a single, temporary guest line, or disabled entirely. The "always-on" POTS internet connection intelligently meters data usage from guest devices, and if a pre-defined threshold is met, it can dynamically reduce guest bandwidth, or prompt for authentication for continued use. This ensures the primary user's voice QoS and data allocation are not impacted by guest usage. Authentication could be handled by a captive portal.
• Mermaid Diagram:

  graph TD
      A[POTS Line] --> B(Modem/DAA)
      B --> C{Internet Connection}
      C --> D[Main CPU/Router]
      D --> E[VoIP Engine (Primary)]
      D --> F[POTS Output Ports (Primary Users)]
      D --> G[802.11 Wireless Module]
      G --> H[Primary Home Network (WPA3)]
      G --> I[Guest Network (Captive Portal)]
      I --> J[Guest Devices]
  
      subgraph Main CPU Logic
          D_PRIO[Voice/Primary Data Prioritization]
          D_QOS[QoS Enforcement]
          D_GUEST_ISOL[Guest Network Isolation]
          D_GUEST_METER[Guest Data Metering/Throttling]
          D_CPU[Processor]
          D_CPU -- Manages --> D_PRIO
          D_CPU -- Manages --> D_QOS
          D_CPU -- Enforces --> D_GUEST_ISOL
          D_CPU -- Controls --> D_GUEST_METER
          D_CPU -- Routes --> E
          D_CPU -- Routes --> F
          D_CPU -- Controls --> G
      end
  

---

Core Claim 8: Method for Providing Multipath Communication Services

Claim 8 Recap: A method for providing multipath communication services using an RCG device, comprising establishing a continuous, always-on internet connection through a POTS line; offering multiple telephone output ports (at least one with a unique telephone number); providing VoIP services for connected telephones over the continuous internet connection; and prioritizing voice packets over other data packets for transmission over the continuous internet connection.

---

1. Material & Component Substitution

Derivative 8.1: Method using Software-Defined Radio (SDR) for POTS Modem and Virtualized SLIC

• Enabling Description: The method involves replacing discrete modem and SLIC/CODEC hardware with a software-defined radio (SDR) module and a powerful general-purpose processor (GPP) running a real-time operating system. This method dynamically configures the SDR to emulate various POTS modem standards (e.g., V.92, V.34, or proprietary higher-speed modulation schemes) over the physical POTS line. The "POTS output ports" are virtualized SLIC instances managed by the GPP, interacting with analog telephone devices via a simple Digital-to-Analog Converter (DAC) and amplifier array. Voice packet prioritization is implemented as a kernel-level queueing discipline within the GPP's network stack.
• Mermaid Diagram:

  flowchart LR
      A[Physical POTS Line] --> B(Software-Defined Radio Module)
      B --> C(General-Purpose Processor w/RTOS)
      C -- Emulates V.92 --> C_MODEM[Software Modem Stack]
      C -- Emulates SLIC --> C_SLIC[Virtualized SLIC Instances]
      C_MODEM -- Establishes --> D[Always-On IP Connection]
      C_SLIC -- Connects --> E[DAC/Amp Array]
      E --> F[Analog Telephone Handsets]
      C -- Provides --> G[VoIP Service (Software)]
      G -- Prioritizes --> D
      D --> H[Internet/Service Provider]
      subgraph GPP Processes
          C_MODEM
          C_SLIC
          G
          I[Kernel-level QoS/Prioritization]
          J[Network Stack]
      end
      C --> I
      I --> J
      J --> D
  

---

2. Operational Parameter Expansion

Derivative 8.2: Method for Ultra-Low Latency Telepresence over Short-Haul POTS Links

• Enabling Description: This method optimizes the RCG operation for ultra-low latency, full-duplex voice and low-resolution video telepresence over short-haul (e.g., intra-building, campus-level) copper POTS wiring. The "always-on" connection employs a custom symmetrical data-over-POTS modulation achieving 2-4 Mbps over short distances, with highly aggressive packetization (e.g., 5ms VoIP packets) and forward error correction (FEC) to minimize perceived latency below 50ms. Voice packets are given absolute priority, with video packets dynamically adjusted in resolution and frame rate to fill remaining bandwidth. The multiple telephone ports are used for dedicated telepresence stations with integrated screens and cameras, each assigned a unique internal extension number.
• Mermaid Diagram:

  graph TD
      A[Short-Haul Copper POTS] --> B(Custom High-Speed POTS Modem)
      B --> C{RCG Device}
      C --> D[Processor (Low Latency RTOS)]
      D --> E[VoIP/Video Engine (5ms Pkts, FEC)]
      D --> F[Traffic Prioritization (Absolute Voice Priority)]
      D --> G[Multiple Telepresence Ports]
      G --> H[Integrated Telepresence Stations]
      E -- Ultra-Low Latency Stream --> I[Remote Telepresence Endpoint]
      F -- Prioritized Data --> I
      subgraph RCG Device
          C
          D
          E
          F
          G
      end
  

---

3. Cross-Domain Application

Derivative 8.3: Method for Remote Healthcare Monitoring and Teleconsultation via Legacy Home POTS

• Enabling Description: A method applied in elderly care or remote patient monitoring. The RCG, connected to a legacy POTS line, establishes an always-on data link for transmitting vital signs data from wearable sensors (via Bluetooth LE to the RCG's wireless interface) to a central healthcare platform. The method allocates a dedicated "teleconsultation" VoIP channel on one of the unique telephone ports. This channel has stringent QoS guarantees, prioritizing live voice and low-bandwidth video for doctor-patient consultations over routine vital sign uploads. In an emergency, an automated voice call can be placed, and the system can override all other traffic to ensure the emergency call's completion.
• Mermaid Diagram:

  sequenceDiagram
      participant Patient as Patient Residence
      participant RCG as RCG Device
      participant POTS as POTS Line
      participant SPNet as Service Provider Network
      participant Healthcare as Healthcare Platform
      participant Doctor as Doctor's Terminal
  
      Patient->>RCG: Wearable Sensor Data (BTLE)
      RCG->>POTS: Establish Always-On IP Link
      POTS->>SPNet: Continuous Data Stream
      SPNet->>Healthcare: Transmit Vital Signs (Lower Priority)
  
      Doctor->>SPNet: Initiate Teleconsultation Call (VoIP)
      SPNet->>POTS: Route Call to RCG
      POTS->>RCG: Incoming Call
      RCG->>RCG: Prioritize Voice/Video over Vital Signs
      RCG->>Patient: Ring Teleconsultation Phone Port
      Patient->>Doctor: Live Teleconsultation (High QoS VoIP/Video)
  
      Note over Patient,Doctor: Emergency Voice Call (Highest Priority)
      RCG->>SPNet: Place Emergency Call
      SPNet->>Doctor: Emergency Alert/Call
  

---

4. Integration with Emerging Tech

Derivative 8.4: Method for Adaptive Edge Computing with Federated Learning for Network Load Prediction

• Enabling Description: The RCG method integrates federated learning at the network edge. Each RCG continuously monitors its local network traffic patterns, including VoIP call duration, data transfer volumes, and wireless client activity. This local data is used to train a local AI model for predicting future bandwidth demands and potential network congestion. Instead of sending raw data, only the model updates are shared (federated learning) with a central server, ensuring privacy. The RCG's processor then uses these local predictions, combined with aggregated global model insights, to proactively adjust bandwidth allocation, pre-buffer streaming data, and dynamically prioritize VoIP packets based on predicted real-time load, minimizing latency and improving QoS for voice.
• Mermaid Diagram:

  graph LR
      subgraph RCG_A
          A1[Local Traffic Monitor] --> A2[Local AI Model Training]
          A2 --> A3[Bandwidth Predictor]
          A3 --> A4[Dynamic QoS Adjuster]
          A4 --> A5[POTS Modem]
          A5 --> A6(Internet)
      end
  
      subgraph RCG_B
          B1[Local Traffic Monitor] --> B2[Local AI Model Training]
          B2 --> B3[Bandwidth Predictor]
          B3 --> B4[Dynamic QoS Adjuster]
          B4 --> B5[POTS Modem]
          B5 --> B6(Internet)
      end
  
      A2 -- Model Updates --> C[Central Federated Learning Server]
      B2 -- Model Updates --> C
      C -- Global Model Insights --> A3
      C -- Global Model Insights --> B3
  
      A5 -- Prioritized VoIP/Data --> A6
      B5 -- Prioritized VoIP/Data --> B6
  

---

5. The "Inverse" or Failure Mode

Derivative 8.5: Method for Prioritized Data Evacuation During Impending Network Failure

• Enabling Description: This method anticipates an impending network outage (e.g., detected instability on the POTS line, upstream carrier alerts). The RCG's processor, upon receiving or detecting such signals, initiates a "data evacuation" procedure. It temporarily suspends all non-critical data transfers and reserves maximum available bandwidth on the POTS connection (prioritizing it even over active voice calls, with user warning/override) to quickly transmit critical, pre-identified data files (e.g., local backups, security logs) to a designated offsite storage before total connectivity loss. Voice services are either temporarily degraded, rerouted to a cellular backup (if available), or provided with a minimal guaranteed bandwidth. Once critical data is evacuated or the connection fails completely, the RCG enters a low-power monitoring state.
• Mermaid Diagram:

  stateDiagram-v2
      state "Normal_Operation" as Normal
      state "Imminent_Failure_Detection" as ImminentFailure
      state "Data_Evacuation_Phase" as DataEvacuation
      state "Low_Power_Monitoring" as LowPower
  
      [*] --> Normal
      Normal --> ImminentFailure: Detect_POTS_Instability / Receive_Outage_Alert
      ImminentFailure --> DataEvacuation: Initiate_Data_Evacuation
      DataEvacuation --> LowPower: Critical_Data_Transferred / Connection_Lost
      LowPower --> Normal: Network_Restored / User_Intervention
  
      state Normal {
          VoIP_High_Priority
          Data_Normal_Priority
      }
  
      state DataEvacuation {
          Data_Evacuation_Highest_Priority
          VoIP_Degraded_or_Suspended
          Warning_Issued_to_Users
          Critical_Files_Identified
      }
  

---

Core Claim 15: RCG Device with Multilink PPP Bundle for Combined Bandwidth

Claim 15 Recap: A Residential Communications Gateway (RCG) device comprising a POTS connection from a LEC, a modem for a continuous internet connection over the POTS line, a processor, at least two telephone output ports (at least one with an additional unique telephone number), and a wireless interface associated with the processor, configured to communicate with other RCG devices, the RCGs being configured to form a multilink PPP bundle to combine the internet bandwidth from the POTS lines connected to the RCG devices.

---

1. Material & Component Substitution

Derivative 15.1: Software-Defined Networking (SDN) Managed RCG Cluster with Li-Fi Backhaul

• Enabling Description: The multilink PPP bundle functionality is replaced by a Software-Defined Networking (SDN) controller residing on one RCG (or a dedicated cluster manager), managing a group of RCGs as an SDN-enabled cluster. The "wireless interface" for inter-RCG communication is augmented or replaced with a Li-Fi (Light Fidelity) module, providing secure, high-bandwidth optical wireless communication within a localized physical area (e.g., adjacent apartments, office spaces). The SDN controller dynamically provisions virtual links over both the Li-Fi and individual POTS connections, creating a flexible multipath TCP (MPTCP) or similar aggregate data path, rather than PPP. The modems themselves are programmable DSP-based units capable of adapting modulation schemes for optimal throughput on each POTS line.
• Mermaid Diagram:

  graph TD
      A[POTS Line 1] --> RCG1(RCG Node 1)
      B[POTS Line 2] --> RCG2(RCG Node 2)
      C[POTS Line N] --> RCGn(RCG Node N)
  
      RCG1 -- Li-Fi Backhaul --> RCG_SDN_Ctrl(SDN Controller RCG)
      RCG2 -- Li-Fi Backhaul --> RCG_SDN_Ctrl
      RCGn -- Li-Fi Backhaul --> RCG_SDN_Ctrl
  
      RCG1 -- MPTCP/Aggregated Path --> Internet
      RCG2 -- MPTCP/Aggregated Path --> Internet
      RCGn -- MPTCP/Aggregated Path --> Internet
  
      subgraph SDN Controller RCG
          RCG_SDN_Ctrl_Proc[Processor]
          RCG_SDN_Ctrl_Software[SDN Controller Software]
          RCG_SDN_Ctrl_Topology[Network Topology Manager]
          RCG_SDN_Ctrl_Flow[Flow Rule Engine]
          RCG_SDN_Ctrl_Proc -- Runs --> RCG_SDN_Ctrl_Software
          RCG_SDN_Ctrl_Software -- Manages --> RCG_SDN_Ctrl_Topology
          RCG_SDN_Ctrl_Software -- Configures --> RCG_SDN_Ctrl_Flow
          RCG_SDN_Ctrl_Software -- Monitors --> RCG1
          RCG_SDN_Ctrl_Software -- Monitors --> RCG2
          RCG_SDN_Ctrl_Software -- Monitors --> RCGn
      end
  

---

2. Operational Parameter Expansion

Derivative 15.2: Geo-Distributed RCG Cluster for High-Throughput Data Ingestion

• Enabling Description: A cluster of RCG devices is deployed across a wide geographic area (e.g., a city block, multiple rural homes), each connected to its local POTS line. The "multilink PPP bundle" is extended to operate as a geo-distributed data ingestion pipeline, where the RCGs collaboratively aggregate data from distributed sensors or edge devices. The wireless communication between RCGs is long-range Wi-Fi (e.g., 802.11ah HaLow) or even directional millimeter-wave links, enabling communication over kilometers. The system dynamically forms and dissolves PPP bundles based on real-time data ingestion requirements, optimizing for throughput for large file transfers (e.g., drone footage, scientific data) while maintaining lifeline VoIP services.
• Mermaid Diagram:

  erDiagram
      RCG_Node ||--o{ POTS_Line : "connects to"
      RCG_Node {
          NodeID
          GeoLocation
          POTS_Bandwidth_Available
          Long_Range_Wireless_Status
          Current_Data_Ingestion_Rate
      }
      POTS_Line {
          LineID
          Max_Bandwidth
          Current_Utilization
      }
      RCG_Cluster {
          ClusterID
          Leader_RCG_NodeID
          Aggregate_Bandwidth
          Active_PPP_Bundles
      }
      Data_Source {
          SourceID
          Data_Type
          Volume
      }
  
      RCG_Node ||--|{ RCG_Cluster : "belongs to"
      RCG_Cluster ||--o{ PPP_Bundle : "manages"
      PPP_Bundle {
          BundleID
          Member_RCG_Nodes
          Destination_URL
          Total_Bandwidth
      }
      Data_Source ||--o{ RCG_Node : "feeds data to"
  

---

3. Cross-Domain Application

Derivative 15.3: Autonomous Vehicle Network (AVN) RCG for Redundant Telemetry Backhaul

• Enabling Description: RCGs are integrated into autonomous vehicles (AVs) or roadside units (RSUs). The "POTS line" is reinterpreted as a legacy wired communication port on the AV/RSU, capable of establishing a dial-up connection to an emergency or fallback network over a standard copper pair when wireless broadband (5G/V2X) is unavailable or compromised. Multiple AV-RCGs (in different vehicles or RSUs) form a "multilink PPP bundle" using short-range, high-reliability wireless vehicle-to-vehicle (V2V) or vehicle-to-infrastructure (V2I) communication (e.g., IEEE 802.11p/bd). This bundle aggregates available wired "POTS" bandwidth from several nodes to create a robust, redundant backhaul for critical telemetry data, system diagnostics, or even low-latency teleoperation commands in situations where primary wireless links fail.
• Mermaid Diagram:

  graph LR
      AV1[Autonomous Vehicle 1 (AV-RCG 1)] -- Wired Backup Link --> RSU1(Roadside Unit 1)
      AV2[Autonomous Vehicle 2 (AV-RCG 2)] -- Wired Backup Link --> RSU2(Roadside Unit 2)
      AV3[Autonomous Vehicle 3 (AV-RCG 3)] -- Wired Backup Link --> RSU3(Roadside Unit 3)
  
      AV1 -- V2V/V2I (802.11p/bd) --> AV2
      AV2 -- V2V/V2I (802.11p/bd) --> AV3
      RSU1 -- High-Speed Network --> ControlCenter(AV Control Center)
      RSU2 -- High-Speed Network --> ControlCenter
      RSU3 -- High-Speed Network --> ControlCenter
  
      subgraph Multilink PPP Bundle (Wireless & Wired Aggregation)
          AV_PPP[AV-RCG PPP Aggregation]
          AV_PPP --> ControlCenter
      end
      
      AV1 -- Forms Link --> AV_PPP
      AV2 -- Forms Link --> AV_PPP
      AV3 -- Forms Link --> AV_PPP
  
      Note over AV_PPP: Aggregates Wired Backup Links from AV-RCGs via V2V/V2I
  

---

4. Integration with Emerging Tech

Derivative 15.4: Quantum-Secured Multilink RCG with Distributed Ledger for Resource Allocation

• Enabling Description: The multilink PPP bundle establishment and resource allocation (bandwidth requests/grants) among RCGs are secured using quantum-resistant cryptography. Each RCG integrates a quantum key distribution (QKD) module for establishing highly secure, unbreakable communication channels for signaling. The distributed ledger technology (DLT) from Derivative 1.8 is extended for managing available POTS bandwidth from each RCG as a tradable resource, validated and recorded on the ledger. Smart contracts automatically execute resource leases and adjust the composition of the multilink PPP bundle based on availability, QoS requirements, and dynamic pricing models derived from the DLT. The processor orchestrates these QKD and DLT interactions, ensuring that sensitive negotiation data (e.g., link performance, RCG identities) is protected.
• Mermaid Diagram:

  sequenceDiagram
      participant RCG_X as RCG X
      participant RCG_Y as RCG Y
      participant DLT as Distributed Ledger (Blockchain)
      participant QKD_Network as QKD Network
  
      RCG_X->>RCG_Y: Request Bandwidth (Encrypted via QKD)
      RCG_X->>QKD_Network: Establish Secure QKD Link
      RCG_Y->>QKD_Network: Establish Secure QKD Link
      QKD_Network-->>RCG_X: Quantum Keys
      QKD_Network-->>RCG_Y: Quantum Keys
  
      RCG_X->>DLT: Propose Bandwidth Requirement (Signed w/Q-Resistant Sig)
      RCG_Y->>DLT: Offer Available Bandwidth (Signed w/Q-Resistant Sig)
      DLT->>DLT: Execute Smart Contract (Match/Allocate)
      DLT-->>RCG_X: Contract Confirmation
      DLT-->>RCG_Y: Contract Confirmation
  
      RCG_X->>RCG_Y: Multilink PPP Session Setup (Encrypted w/Q-Resistant Keys)
      RCG_X->>DLT: Log Bandwidth Utilization (for Auditing/Billing)
  

---

5. The "Inverse" or Failure Mode

Derivative 15.5: Decentralized Emergency Multilink Mesh Network (DEMMN) from Failing RCGs

• Enabling Description: In a widespread disaster (e.g., regional power outage, internet backbone failure), individual RCGs detect catastrophic loss of external connectivity. Instead of relying on a central authority, they spontaneously form a Decentralized Emergency Multilink Mesh Network (DEMMN) using their wireless interfaces (e.g., 802.11s mesh networking protocol). If any RCG within the mesh still has a functional POTS line (even if degraded or intermittent), this line is automatically designated as an "emergency egress point." The remaining RCGs in the mesh dynamically form a "multilink PPP bundle" over the combined available POTS bandwidth of all such egress points, prioritizing emergency voice calls and short, critical text messages (e.g., via a lightweight messaging protocol like MQTT-SN over the mesh) to external services. Non-essential data is dropped, and power consumption is minimized across the mesh.
• Mermaid Diagram:

  graph TD
      RCG1[RCG 1 (Failing)] -- Mesh Link --> RCG2[RCG 2 (Degraded POTS)]
      RCG1 -- Mesh Link --> RCG3[RCG 3 (Failing)]
      RCG2 -- Mesh Link --> RCG4[RCG 4 (Operational POTS)]
      RCG3 -- Mesh Link --> RCG4
      RCG5[RCG 5 (Failing)] -- Mesh Link --> RCG4
  
      RCG2 -- Egress Point (Degraded) --> POTS_B(POTS Line B)
      RCG4 -- Egress Point (Operational) --> POTS_D(POTS Line D)
  
      POTS_B -- Aggregated --> Emergency_Network(Emergency Services Network)
      POTS_D -- Aggregated --> Emergency_Network
  
      subgraph DEMMN Functionality
          RCG_Mesh[RCG Mesh (802.11s)]
          RCG_Mesh -- Aggregates --> Multilink_Bundle(Emergency Multilink PPP Bundle)
          Multilink_Bundle --> Emergency_Network
          Multilink_Bundle -- Prioritizes --> Voice_Calls[Emergency Voice Calls]
          Multilink_Bundle -- Prioritizes --> Text_Msgs[Critical Text Messages]
      end
  
      RCG1 -- Member --> RCG_Mesh
      RCG2 -- Member --> RCG_Mesh
      RCG3 -- Member --> RCG_Mesh
      RCG4 -- Member --> RCG_Mesh
      RCG5 -- Member --> RCG_Mesh
  

---

Combination Prior Art Scenarios

Here are three scenarios combining aspects of US9350649 with existing open-source standards, demonstrating how the patent's teachings could be rendered obvious or non-novel in combination:

1. US9350649 + OpenWrt/LEDE for Router Management and VoIP Provisioning:

   • Description: A person skilled in the art, seeking to implement a Residential Communications Gateway (RCG) as described in US9350649 (Claim 1), would find it obvious to use the open-source router operating system OpenWrt/LEDE. OpenWrt provides a complete Linux-based firmware for embedded devices, already supporting modem drivers (for POTS modems if available), network stack management, Wi-Fi drivers (802.11b/g/n/ac/ax), and QoS/traffic shaping capabilities. The VoIP services could be easily provisioned using open-source SIP server software like Asterisk (which can be compiled and run on OpenWrt) or a lightweight SIP client/proxy. The prioritization of voice packets (as per Claim 1 and 8) is a standard feature of Linux QoS frameworks (e.g., tc with HTB queuing disciplines) that are readily available and configurable in OpenWrt. Furthermore, the handling of multiple virtual telephone lines can be managed via chan_dongle or similar modules for Asterisk integrated with hardware SLICs, making the concept of multiple unique telephone numbers over a single gateway obvious.
   • Standard: OpenWrt/LEDE (Router OS), Asterisk (VoIP PBX).

2. US9350649 + Linux Kernel MultiPath TCP (MPTCP) for Bandwidth Aggregation:

   • Description: Given the RCG's concept of aggregating bandwidth (Claim 15) using a multilink PPP bundle, a person skilled in the art would find it obvious to achieve a similar or superior result by replacing PPP with MultiPath TCP (MPTCP), which is integrated into the Linux kernel and available as an open-source standard. MPTCP allows a single TCP connection to use multiple network paths simultaneously, effectively combining bandwidth. An RCG (or a cluster of RCGs) running a Linux-based OS could use MPTCP to aggregate data traffic over its primary POTS modem connection (representing one path) and additional connections formed via other RCGs' POTS lines (via wireless relay and their respective modems, acting as additional paths). This setup leverages existing kernel functionality for robust, efficient, and transparent bandwidth aggregation, making the multilink PPP approach non-novel. The wireless interface would facilitate the establishment of IP connectivity between RCGs, over which MPTCP subflows would be established.
   • Standard: Linux Kernel MultiPath TCP (MPTCP).

3. US9350649 + FreeRADIUS for Dynamic RCG-to-RCG Service Authorization:

   • Description: The process described in US9350649 (Claim 15) for RCGs to request and grant bandwidth services from other RCGs in a multilink PPP bundle could be implemented using the open-source FreeRADIUS server. A central or designated RCG (or a cloud-based service provider component) acting as a RADIUS server could authenticate and authorize bandwidth requests from initiating RCGs to remote RCGs. When an initiating RCG sends a multilink PPP service request to a remote RCG, the remote RCG could act as a RADIUS client, querying the central FreeRADIUS server to verify the initiating RCG's credentials and determine its authorization to use the remote RCG's bandwidth, based on predefined policies or even dynamic load balancing. This provides a robust, extensible, and standards-compliant framework for managing shared network resources among RCGs, making the ad-hoc authorization described in the patent obvious.
   • Standard: FreeRADIUS (Authentication, Authorization, and Accounting protocol implementation).