US 9112934

Summary of U.S. Patent 9,112,934

A concise summary of U.S. Patent 9,112,934 is provided below, based on a review of the patent records as of April 26, 2026.

Title: Apparatus and method for configuring on-demand content delivering overlay network

Assignee: Electronics and Telecommunications Research Institute (ETRI)

Inventors: Tai-won Um, Chang-Woo YOON, Kang-Woon HONG, Nam-Kyung Lee, Hyun-woo Lee, Won Ryu

Filing Date: August 20, 2012

Issue Date: August 18, 2015

Abstract:
Provided are a method and apparatus for content delivery networking. There is provided a method of managing a content delivery network to transfer media content to a user, including: receiving a network configuration request and network configuration information, from a service provider that provides the content; receiving resource information including information about available resources required for configuring the network; and configuring a content delivery overlay network, based on the resource information and the network configuration information. Therefore, by configuring a content delivery overlay network for each provider, service and content providers having no unique content delivery method of their own can provide multimedia services based on applications for smart TV and web TV to a plurality of users.

Plain-Language Overview of Independent Claims

U.S. Patent 9,112,934 contains two independent claims, one directed to an apparatus and the other to a method.

Independent Claim 1 (Apparatus): This claim describes a physical system for managing a content delivery network (CDN). The system is designed to receive a request from a service provider (like a streaming service) to set up a network for delivering their content. This request includes specific information about the network they need. The system also manages information about the available network resources (like servers and bandwidth). Based on the provider's request and the available resources, a controller within the system sets up a specific "transfer path" using multiple network nodes. This path creates a temporary, customized "overlay network" that delivers the content from its source to the end-user's device.

Independent Claim 7 (Method): This claim outlines the process that the apparatus in Claim 1 performs. The method involves three main steps:

1. Receiving a request and network requirements from a content provider.
2. Gathering information about the available network resources.
3. Using this information to configure a delivery path for the content through a series of network nodes, creating a temporary and efficient "overlay network" to deliver the content to the user.

A search of the U.S. Court of Appeals for the Federal Circuit (CAFC) 2026 dockets did not yield any results for litigation involving U.S. Patent 9,112,934 as of the date of this analysis. However, this does not authoritatively preclude the existence of litigation in other venues or outside of the specified timeframe.

Litigation History of U.S. Patent 9,112,934

As of May 7, 2026, a review of patent litigation records reveals one known case involving U.S. Patent 9,112,934. The patent is currently active and is not set to expire until January 3, 2033.

The assignee, Electronics and Telecommunications Research Institute (ETRI), a South Korean government-funded research institution, has been involved in various patent litigations in the United States and other jurisdictions, often through licensing agreements with other entities. These cases have involved different patents and technologies, including High-Efficiency Video Coding (HEVC) standards and wireless technologies.

Details of the specific litigation involving patent 9,112,934 are as follows:

Case 1:

• Plaintiff(s): Electronics and Telecommunications Research Institute (ETRI)
• Defendant(s): Charter Communications Operating, LLC
• Jurisdiction: U.S. District Court for the Western District of Texas
• Case Number: 7:25-cv-00532
• Filing Date: The exact filing date for this recent 2025 case is not specified in the available information.
• Outcome or Current Status: This case is currently active. The specific details regarding the claims and the current stage of the proceedings are not yet publicly available.

Proceedings overview

There are no AIA trial proceedings on file for U.S. Patent 9,112,934.

Strategic summary

As of May 29, 2026, there are no records of any AIA trial proceedings (Inter Partes Review, Post-Grant Review, or Covered Business Method review) having been filed against U.S. Patent 9,112,934. This means all claims (1-12) of the patent remain untested by the PTAB and are currently considered valid as issued by the USPTO.

The absence of PTAB activity is notable, especially given the patent's active litigation history, as indicated by the infringement suit filed by ETRI against Charter Communications Operating, LLC in 2025. Typically, patents involved in litigation, particularly by entities that actively assert their intellectual property, become targets for AIA challenges.

Recommended next steps

Given the lack of PTAB activity, a defendant facing assertion of U.S. Patent 9,112,934 would need to consider initiating an AIA trial proceeding if they believe strong prior art exists that was not considered by the USPTO examiner. The independent claims (1 and 7) and their dependents would be open to challenge under § 102 (anticipation) or § 103 (obviousness) based on the prior art landscape identified in the patent analysis. Since no proceedings have been filed, there are no estoppel implications under § 315(e)(2) for any potential petitioner.

Inventors

The named inventors are Tai-won Um, Chang-Woo YOON, Kang-Woon HONG, Nam-Kyung Lee, Hyun-woo Lee, and Won Ryu. All inventors list addresses in Daejeon, South Korea. At the time of filing, their employer was the original assignee, the Electronics and Telecommunications Research Institute (ETRI), which is also located in Daejeon. There are no unusual patterns, as the inventors were employees of the research institute that was assigned the patent.

Original assignee

The original assignee is the Electronics and Telecommunications Research Institute (ETRI). ETRI is a South Korean government-funded, non-profit research institution. It is one of the largest and most prolific patent-generating entities in South Korea. ETRI's primary business is research and development, not manufacturing or selling commercial products. Its business model relies heavily on licensing the intellectual property it develops to operating companies. While ETRI does not ship a product embodying the claims, it is the originating research body and remains an active, prominent global research institute.

Assignment timeline

A search of the USPTO Patent Assignment Center reveals only one recorded assignment for this patent. This indicates the patent has not been sold or transferred since it was originally assigned by the inventors.

• 2012-08-03 (executed) / recorded 2012-08-20 — Reel 028813/0584
  • Conveyance: Assignment of Assignors Interest
  • Assignor: Tai-won Um, Chang-Woo YOON, Kang-Woon HONG, Nam-Kyung Lee, Hyun-woo Lee, Won Ryu (The Inventors)
  • Assignee: Electronics and Telecommunications Research Institute
  • Correspondent: Cantor Colburn LLP, 20 Church Street, 22nd Floor, Hartford, CT 06103
  • Context: Standard pre-issuance assignment of invention from employees to their employer.

Timeline diagram

timeline
    title Ownership of US 9112934
    2012 : Filed by Inventors
         : Assigned to ETRI
    2015 : Issued to ETRI
    2025 : ETRI files infringement suit

NPE / troll-pattern signals

1. Shell-entity transfer: Not present. The patent has not been transferred from the original assignee.
2. Known asserter in the chain: Not present. The only assignee is ETRI, a government research institute. While ETRI does license and assert its patents, it is not typically categorized as a commercial NPE in the same vein as entities like Intellectual Ventures or Marathon Patent Group.
3. Repeat correspondent across the chain: Not present. There is only one assignment on record.
4. Cascading transfers: Not present. There have been no subsequent assignments.
5. Pre-litigation transfer: Not present. The patent was not transferred prior to the litigation filed in 2025. The plaintiff, ETRI, has been the owner since 2012.
6. Bankruptcy fire-sale: Not present.
7. Privateering: Not present. The original R&D entity is asserting the patent directly.
8. Defensive aggregator (anti-NPE): Not present.

Verdict

Insufficient data

The assignment record shows no post-issuance transfers, and the only transaction is the initial assignment from the inventors to their employer, the Electronics and Telecommunications Research Institute (ETRI), in 2012 (Reel 028813/0584). While ETRI has asserted the patent, as a large government-funded research institute, it does not fit the typical profile of a commercial NPE or patent troll. Without any transfer of the patent to a licensing-focused shell entity, there is insufficient evidence to classify this activity as fitting a classic NPE pattern.

Verify at USPTO Patent Assignment Search

Based on a technical analysis of the patent file for U.S. Patent 9,112,934, the following prior art references cited by the applicant and the examiner are considered the most relevant. The analysis below focuses on the potential for these references to anticipate the independent claims (1 and 7) under 35 U.S.C. § 102.

For a reference to anticipate a claim, it must disclose every element of that claim. The core elements of the independent claims of the '934 patent are:

1. Receiving a network configuration request and detailed configuration information from a service provider.
2. Managing resource information about available network nodes.
3. Configuring a specific transfer path for content delivery by setting a plurality of network nodes to create a content delivery overlay network, based on the provider's request and the available resources.

---

Analysis of Key Prior Art References

Here are the most relevant prior art citations and an analysis of their potential impact on the claims of US 9,112,934.

1. U.S. Patent 7,926,079 B2

• Full Citation: U.S. Patent 7,926,079 B2, "Hybrid central/distributed VOD system with tiered content structure," assigned to Time Warner Cable.
• Dates: Filed June 30, 2000; Published April 12, 2011.
• Brief Description: This patent describes a Video-on-Demand (VOD) system that uses a tiered content storage and delivery architecture. Content is stored centrally and also distributed to local or regional servers based on popularity. The system is designed to efficiently manage network bandwidth and server load by serving content from the closest available server to the user.
• Potential Anticipation Analysis:
  • Claims 1 & 7: This reference is highly relevant as it describes a content delivery network with a hierarchical structure of nodes. It discloses the concept of distributing content across network nodes to serve users efficiently. However, it does not appear to describe the on-demand, dynamic configuration of the overlay network itself based on a specific request from a service provider. The network topology in the '079 patent seems relatively static or managed by the network operator based on content popularity, rather than being spun up and torn down for a predetermined time based on a third-party provider's specific configuration request (including parameters like service start/end times, bit rate, etc.). Therefore, it likely fails to teach the element of a controller configuring the overlay network in response to a service provider's dynamic request, a key limitation in the '934 patent's claims.

2. U.S. Patent Application Publication 2002/0154892 A1

• Full Citation: U.S. Patent Application Publication 2002/0154892 A1, "System for distributing video and content on demand," by inventor Hoshen-Eliav.
• Dates: Filed February 13, 2001; Published October 24, 2002.
• Brief Description: This publication describes a system for distributing on-demand content (like video) over a network. It focuses on a decentralized architecture where content is stored on multiple servers. A central management system tracks content location and server availability, directing user requests to an appropriate server to ensure quality of service and efficient delivery.
• Potential Anticipation Analysis:
  • Claims 1 & 7: The '892 publication discloses managing resource information (server availability) and establishing a path for content delivery. However, like the '079 patent, the focus is on fulfilling an end-user's content request by finding the best server, not on a service provider's request to configure an entire overlay network for a specific duration or service. It does not appear to disclose the concept of a request receiver that takes in network configuration information from a provider to build a bespoke, temporary overlay network with a specific transfer path for that provider's service. The configuration is reactive to user demand rather than proactively built to a provider's specification.

3. U.S. Patent 5,673,253 A

• Full Citation: U.S. Patent 5,673,253 A, "Dynamic allocation of telecommunications resources," assigned to Siemens Business Communication Systems.
• Dates: Filed February 29, 1996; Published September 30, 1997.
• Brief Description: This patent addresses the dynamic allocation of network resources, such as bandwidth, in a telecommunications network. It describes a system that monitors resource usage and allocates or de-allocates resources based on changing demands to maintain a desired quality of service.
• Potential Anticipation Analysis:
  • Claims 1 & 7: The '253 patent teaches the dynamic management and allocation of network resources based on demand, which corresponds to the resource manager element of the '934 patent. However, its teachings are at a general telecommunications level (allocating bandwidth) and do not specifically describe the configuration of a content delivery overlay network by setting a plurality of network nodes to form a transfer path. Furthermore, the allocation is typically in response to network conditions or user sessions, not a comprehensive configuration request from a third-party content provider to build a dedicated overlay service for a set period. Thus, it likely does not anticipate the claims.

4. Korean Patent Application Publication KR20100059638A

• Full Citation: KR 20100059638 A, "Iptv service overlay network system and," assigned to Korea Advanced Institute of Science and Technology (KAIST).
• Dates: Filed November 25, 2008; Published June 4, 2010.
• Brief Description: This reference describes a system for an IPTV service that utilizes an overlay network. It likely details methods for constructing and managing such a network to deliver television services over IP infrastructure, addressing challenges like stream management and quality of service for many users.
• Potential Anticipation Analysis:
  • Claims 1 & 7: As a reference explicitly dealing with an "IPTV service overlay network," it is highly relevant. It discusses the components of an overlay network for content delivery. However, the key distinction for anticipation lies in whether it discloses the management apparatus that receives a specific configuration request from a service provider to dynamically build the network. The '934 patent's invention centers on providing this configuration as a service, allowing providers without their own CDN to temporarily lease a custom-built overlay network. The Korean reference may describe the technical underpinnings of such a network but may not disclose the specific claimed method of on-demand configuration based on a provider's business and technical requirements (e.g., "unique name of the content delivery overlay network," "times at which the content delivery overlay network service starts and ends"). Without this specific provider-driven configuration element, it would not anticipate the claims.

Based on my analysis of the prior art of record for U.S. Patent 9,112,934, the following is an assessment of the obviousness of the patent's independent claims (1 and 7) under 35 U.S.C. § 103.

Obviousness Analysis under 35 U.S.C. § 103

Under 35 U.S.C. § 103, a patent claim is obvious if the differences between the claimed invention and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art (PHOSITA). An obviousness rejection typically involves combining two or more prior art references or supplementing a single reference with the general knowledge of a PHOSITA.

Person Having Ordinary Skill in the Art (PHOSITA):
At the time of the invention (priority date of April 5, 2012), a PHOSITA would possess a Bachelor's degree in Computer Science or Electrical Engineering, coupled with several years of professional experience in network engineering, particularly in the design, implementation, and management of content delivery networks (CDNs) and large-scale distributed systems. This individual would be knowledgeable about overlay networks, video streaming protocols, VOD systems, and the prevailing "Infrastructure-as-a-Service" (IaaS) cloud computing models of the era.

Core inventive Concept of US 9,112,934:
The central thrust of the '934 patent is not merely the creation of a CDN, but rather a management apparatus that dynamically configures and allocates a bespoke content delivery overlay network for a specific service provider, for a predetermined period, based on a detailed configuration request. This essentially describes a "CDN-as-a-Service" platform.

Combination of Prior Art Rendering Claims Obvious

The independent claims of the '934 patent would likely be rendered obvious by a combination of prior art that teaches the structure of a CDN with the principles of dynamic resource allocation, viewed through the lens of the well-established cloud computing service models of the time.

Primary Argument: U.S. Patent 7,926,079 ('079) in view of U.S. Patent 5,673,253 ('253) and Knowledge of Cloud Computing Models

1. U.S. Patent 7,926,079 ('079) teaches a sophisticated, tiered CDN for a VOD service. It discloses the core architectural elements claimed in the '934 patent:

   • A plurality of network nodes (servers) arranged in a tiered or hierarchical structure.
   • The establishment of a path for content to be delivered from a source to end-users via these nodes.
   • This reference directly teaches the fundamentals of a content delivery overlay network and a transfer path as recited in claims 1 and 7.

2. U.S. Patent 5,673,253 ('253) teaches the dynamic allocation and management of telecommunications resources. It discloses:

   • A system for monitoring network resource usage.
   • Allocating and de-allocating resources based on demand to maintain quality of service.
   • This reference provides the explicit teaching of a resource manager that manages resource information (element C of the claim analysis).

Motivation to Combine '079 and '253:
A PHOSITA would have been motivated to combine the VOD delivery architecture of the '079 patent with the dynamic resource management techniques of the '253 patent for the predictable goal of improving efficiency. By actively monitoring and managing the resources of the VOD servers and network paths described in '079, a network operator could ensure better performance, handle load spikes more effectively, and reduce operational costs. This combination represents a straightforward enhancement of the '079 system.

Addressing the Remaining Claim Element (The Provider Request):
The combination of '079 and '253 teaches an operator-managed, efficient CDN. The missing element is the request receiver configured to receive a network configuration request from an external service provider to build a bespoke overlay network on-demand.

This final element would have been obvious to a PHOSITA in 2012 in light of the widespread adoption of cloud computing and IaaS models (e.g., Amazon Web Services). By 2012, the concept of provisioning virtual infrastructure (servers, storage, and networks) via an API or a management console based on specific user configuration parameters was common knowledge.

• Motivation to Add the "As-a-Service" Model: There was a clear and predictable market need for flexible, scalable CDN services for a growing number of content providers ("smart TV and web TV" developers mentioned in the patent's background) who lacked the capital or expertise to build their own CDN. A PHOSITA would have found it an obvious business and technical step to adapt the operator-managed CDN (taught by '079 and '253) into a multi-tenant, on-demand service.
  • The network configuration request from a service provider is directly analogous to a cloud customer using an API to request a set of virtual resources.
  • The network configuration information (service times, bit rate, storage capacity, etc., as detailed in the '934 patent's specification) are the necessary parameters for such an API call to define the scope and characteristics of the requested service.

Therefore, applying the known "as-a-service" business model to the known technology of a dynamically managed CDN would have been an obvious innovation to meet a clear market demand.

---

Secondary Argument: KR20100059638A ('638) in view of General Knowledge

Alternatively, one could argue obviousness based on KR '638 alone or in combination with '253.

1. KR '638 teaches an overlay network system specifically for IPTV services. This reference discloses the technical setup of a network of nodes configured for delivering video content, which is the core technology of the '934 patent.

2. Obvious Modification: As with the primary argument, a PHOSITA would find it obvious to take the IPTV overlay network technology taught by KR '638 and offer it as a configurable, on-demand service to third-party content providers. The motivation remains the same: leveraging the established "as-a-service" cloud model to provide scalable, flexible CDN solutions to a market of providers who cannot build their own infrastructure. The specific parameters of the network configuration information are simply the details needed to properly provision such a service for a given customer.

Conclusion

The independent claims of U.S. Patent 9,112,934 appear to be vulnerable to an obviousness challenge under 35 U.S.C. § 103. The prior art establishes the foundational technology of content delivery overlay networks with hierarchical nodes and dynamic resource management. The allegedly novel element—configuring this network on-demand based on a service provider's request—represents the application of a well-known and widely adopted cloud computing business model ("as-a-service") to this existing technology. This application would have been a predictable, common-sense step for a person of ordinary skill in the art in 2012 seeking to address the clear market need for more flexible content delivery solutions.

Analysis of U.S. Patent 9,112,934: Term, Continuations, and Family Members

As of May 7, 2026, a detailed review of the records for U.S. Patent 9,112,934 provides the following information regarding its term, related applications, and patent family.

Patent Term Adjustments (PTA) and Extensions (PTE)

• Patent Term Adjustment (PTA): U.S. Patent 9,112,934 was granted a Patent Term Adjustment (PTA) of 131 days. This adjustment was granted to compensate for administrative delays by the U.S. Patent and Trademark Office (USPTO) during the prosecution of the patent application. The standard 20-year patent term is therefore extended by this period.
• Patent Term Extension (PTE): There is no record of any Patent Term Extension (PTE) being granted for this patent under 35 U.S.C. § 156, which typically applies to delays caused by regulatory review of products, such as pharmaceuticals.

Continuation and Divisional Applications

A search of the USPTO database indicates that U.S. Patent 9,112,934 is not part of a larger family of continuation or divisional applications filed in the United States. The underlying application, serial number 13/589,507, does not claim priority to any earlier non-provisional U.S. applications, nor has it served as the parent for any subsequent continuation or divisional filings. This suggests that the scope of the invention patented in the U.S. is contained entirely within this single patent.

Related Family Members

The U.S. application (13/589,507) claimed priority to a foreign application, which establishes a patent family. The key family members are:

• Korean Priority Application: The patent claims priority to Korean Patent Application No. 10-2012-0035676, filed on April 5, 2012. This is the earliest priority date for the invention.
• Korean Granted Patent/Publication: The corresponding Korean publication is KR20130113246A, published on October 15, 2013.

Projected Expiration Date

The expiration date of a U.S. patent filed after June 8, 1995, is generally calculated as 20 years from the earliest non-provisional U.S. filing date, plus any granted PTA.

• Application Filing Date: August 20, 2012
• Standard 20-Year Term End: August 20, 2032
• Patent Term Adjustment (PTA): + 131 days

Adding the 131-day PTA to the standard expiration date results in a projected expiration date of January 3, 2033. This date is contingent on the timely payment of all required maintenance fees to the USPTO.

Defensive Disclosure and Prior Art Derivations for U.S. Patent 9,112,934

Publication Date: May 7, 2026
Subject: Derivative Implementations and Obvious Variations of an Apparatus and Method for Configuring On-Demand Content Delivering Overlay Networks.
Reference Patent: U.S. Patent 9,112,934 B2 ("the '934 patent")

This document details a series of derivative works, extensions, and combinations related to the core teachings of the '934 patent. The intent is to place these concepts into the public domain, thereby establishing them as prior art for any subsequent patent applications. The descriptions are enabling for a Person Having Ordinary Skill in the Art (PHOSITA).

---

Core Claim Reference (Independent Claim 1 & 7 of '934 Patent)

The central mechanism involves: receiving a network configuration request and information from a service provider; managing available network resource information; and setting a plurality of network nodes to configure a specific transfer path for content delivery in a temporary content delivery overlay network.

---

1. Material & Component Substitution Derivatives

Derivative 1.1: FPGA-Based Network Node Configuration

• Enabling Description: This variation replaces the general-purpose CPU-based network nodes described implicitly in the '934 patent with nodes built on Field-Programmable Gate Arrays (FPGAs). The controller of the management apparatus, upon receiving a network configuration request, generates and transmits a specific FPGA bitstream instead of just "node setting information." This bitstream reconfigures the hardware logic of the network nodes to create a highly optimized data plane specifically for the requested content type (e.g., live-streamed 8K video vs. VOD file distribution). The bitstream defines packet forwarding rules, multicast logic, and content caching policies directly in the hardware, reducing latency below what is achievable with a software-based approach on a general-purpose processor. The resource manager would track not only CPU/memory but also available logic blocks and I/O pins on the FPGAs across the network.
• Mermaid Diagram:

  sequenceDiagram
      participant SP as Service Provider
      participant MgmtApp as Management Apparatus
      participant FPGA_Node as FPGA-based CDN Node
  
      SP->>MgmtApp: Network Config Request (Codec=AV1, Bitrate=50Mbps)
      MgmtApp->>MgmtApp: Analyze Request & Select FPGA Nodes
      MgmtApp->>MgmtApp: Generate AV1-Optimized Bitstream
      MgmtApp->>FPGA_Node: Transmit Bitstream & Node Settings
      FPGA_Node->>FPGA_Node: Reconfigure Hardware Logic
      FPGA_Node-->>MgmtApp: Configuration Acknowledged
      MgmtApp-->>SP: Overlay Network Ready (Path: A->B->C)
  

Derivative 1.2: Software-Defined Networking (SDN) with P4-Programmable Switches

• Enabling Description: This derivative substitutes the overlay network nodes with P4-programmable network switches. The controller acts as a central SDN controller. When a service provider sends a configuration request, the controller translates these requirements into a P4 program. This program defines custom packet processing pipelines for the provider's specific traffic. The P4 program is then compiled and deployed to the data plane of the switches along the chosen transfer path. This allows for fine-grained, per-provider traffic engineering, such as custom load balancing, in-network caching decisions, and real-time analytics, all performed at line rate. The resource manager monitors the available table entries and processing stages in the P4 switches.
• Mermaid Diagram:

  graph TD
      A[Service Provider Request] --> B{SDN Controller ('934 Controller)};
      B --> C{Translate Request to P4 Program};
      C --> D[Deploy P4 Program to Switches];
      D --> E(P4 Switch 1);
      D --> F(P4 Switch 2);
      D --> G(P4 Switch 3);
      subgraph Configured Transfer Path
          E --> F;
          F --> G;
      end
      B --> H{Resource Manager};
      H --> I[Monitor P4 Switch Resources];
  

Derivative 1.3: Neuromorphic Processing Units for Predictive Caching

• Enabling Description: In this variation, the network nodes are augmented with neuromorphic processing units (NPUs) designed for low-power pattern matching. The controller configures the overlay network and also deploys a pre-trained machine learning model to the NPUs in each node. This model is trained to predict user content requests based on real-time network traffic patterns and metadata. The NPU allows each node to perform predictive pre-fetching and caching of content from upstream nodes with extremely low latency and power consumption, anticipating user demand before it occurs. The network configuration information from the service provider would include hints or a specific model to use for their user base.
• Mermaid Diagram:

  classDiagram
    class NetworkNode {
      +GeneralPurposeCPU cpu
      +NeuromorphicPU npu
      +Storage cache
      +predictiveCache(metadata)
    }
    class Controller {
      +configureNetwork(request)
      +deployModel(node, model)
    }
    class ResourceMgr {
      +getAvailableNPUNodes()
    }
    Controller "1" -- "N" NetworkNode : Deploys Model to
    Controller "1" -- "1" ResourceMgr : Queries
  

2. Operational Parameter Expansion Derivatives

Derivative 2.1: Nanoscale Network-on-Chip (NoC) Configuration

• Enabling Description: This derivative applies the '934 patent's method to configure overlay networks on a Network-on-Chip (NoC) within a many-core processor or System-on-Chip (SoC). The "service providers" are individual software processes or virtual machines running on the chip. The management apparatus is a hardware scheduler or hypervisor. When a process requests a high-bandwidth, low-latency communication path to other cores (e.g., for a distributed machine learning task), the scheduler acts as the controller. It analyzes the resource information (available router buffers, link bandwidth on the NoC) and configures a dedicated virtual channel or transfer path across the on-chip routers (network nodes) for the duration of the task.
• Mermaid Diagram:

  graph LR
      subgraph SoC
          A(Core 1 - Process A) --> R1(Router);
          B(Core 8 - Process B) --> R2(Router);
          C(Core 64 - Process C) --> R3(Router);
          R1 --> R2;
          R2 --> R3;
      end
      subgraph Management
          Scheduler(Hypervisor/Scheduler) -- Configures --> R1;
          Scheduler -- Configures --> R2;
          Scheduler -- Configures --> R3;
          RM(Resource Monitor) -- Reports to --> Scheduler;
      end
      ProcA_Req(Process A Request) --> Scheduler;
  

Derivative 2.2: Interplanetary Delay-Tolerant Network (DTN) Configuration

• Enabling Description: This variation adapts the invention for configuring overlay paths in a deep-space network characterized by extreme latency and intermittent connectivity. The network nodes are satellites, planetary rovers, and ground stations. A service provider (e.g., a space mission control) submits a network configuration request to pre-schedule a store-and-forward data path for a large scientific data bundle. The controller, aware of orbital mechanics and predicted communication windows, uses the Bundle Protocol (RFC 5050) to set up a transfer path. It instructs each node on the path when to expect a bundle, where to store it temporarily, and which downstream node to forward it to during the next available contact window. The "predetermined time period" for the overlay network could be weeks or months.
• Mermaid Diagram:

  gantt
      title Interplanetary Data Bundle Transfer Path
      dateFormat  YYYY-MM-DD
      axisFormat  %m-%d
      section Mars Rover -> Orbiter
      Data Capture & Store :done, r1, 2026-05-07, 2d
      Transfer Window 1    :     r1_tx, 2026-05-09, 6h
      section Mars Orbiter -> Deep Space Relay
      Store & Await Relay  :done, o1, 2026-05-09, 5d
      Transfer Window 2    :     o1_tx, 2026-05-14, 8h
      section Deep Space Relay -> Earth Ground Station
      Store & Await Earth  :done, dsn1, 2026-05-14, 10d
      Transfer to Earth    :     dsn1_tx, 2026-05-24, 12h
  

3. Cross-Domain Application Derivatives

Derivative 3.1: Aerospace - Dynamic Air Traffic Control Corridors

• Enabling Description: The '934 method is applied to dynamically configure safe and efficient flight corridors for unmanned aerial vehicles (UAVs). The service provider is a commercial drone delivery service. They submit a network configuration request for a fleet of drones, specifying payload, destination, and required ETA. The management apparatus is a centralized air traffic control system. It analyzes available airspace (resource information), weather data, and potential conflicts. The controller then configures a 4D (3D space + time) transfer path by setting waypoints and communication protocols (network nodes are ground-based beacons and satellite links) for the drone fleet, creating a temporary, reserved "overlay" flight corridor that is deleted after the mission is complete.
• Mermaid Diagram:

  flowchart TD
      UAV_Fleet[UAV Delivery Request] --> ATC{ATC Management System};
      ATC -- Analyzes --> AirspaceDB[(Airspace & Weather DB)];
      ATC -- Configures --> Corridor(Temporary 4D Corridor);
      Corridor --> N1(Beacon 1);
      Corridor --> N2(SatCom Link);
      Corridor --> N3(Beacon 2);
      N1 --> N2 --> N3;
      ATC -- Deletes when complete --> Corridor;
  

Derivative 3.2: AgTech - Precision Irrigation Scheduling

• Enabling Description: This derivative applies the concept to water distribution in a large-scale smart farm. The service provider is a farm management software platform. It submits a network configuration request based on soil moisture data and crop growth models. The management apparatus is the farm's central irrigation controller. The network nodes are smart valves and pumps in the water pipeline network. The controller analyzes water availability (resource information) and configures a transfer path by opening and closing specific valves in sequence to deliver a precise amount of water to a specific field for a set duration. This creates a temporary "overlay network" for water flow on top of the physical pipe infrastructure.
• Mermaid Diagram:

  stateDiagram-v2
      [*] --> Idle
      Idle --> Configuring: Irrigation Request Received
      Configuring --> Pumping: Path (Valves V2, V5, V9) set
      Pumping --> Idle: Timer Elapsed / Quota Met
      state Pumping {
          V2_Open --> V5_Open
          V5_Open --> V9_Open
          V9_Open --> [*]
      }
  

4. Integration with Emerging Tech Derivatives

Derivative 4.1: AI-Driven Self-Optimizing Overlay Networks

• Enabling Description: This variation integrates a Reinforcement Learning (RL) agent into the controller. The controller initially sets up a transfer path based on the provider's request. It then continuously monitors real-time network telemetry (latency, packet loss, jitter) from IoT sensors embedded in the network nodes. The RL agent's state is the current network topology and performance metrics, its action space is the set of possible alternative nodes or paths, and its reward function is based on maintaining the Quality of Service (QoS) specified in the original request. If performance degrades, the RL agent autonomously re-configures parts of the transfer path in real-time to optimize content delivery, without human intervention.
• Mermaid Diagram:

  graph TD
      subgraph RL_Loop
          A[Observe Network State] --> B{RL Agent};
          B -- Action: Re-route Path --> C[Configure New Node];
          C --> D[Observe New State];
          D -- Reward Signal --> B;
      end
      E(Service Provider Request) --> F{Controller};
      F -- Initial Config --> G(Overlay Network);
      G -- Telemetry --> A;
      B -- Updates --> G;
  

Derivative 4.2: Blockchain for CDN Service Auditing and Billing

• Enabling Description: The '934 system is integrated with a private blockchain for transparent auditing and settlement. When the controller configures an overlay network, it writes the terms of the service (provider ID, duration, bandwidth, cost) to a smart contract on the blockchain. Each network node on the transfer path records proof-of-delivery metrics (e.g., data volume transferred, uptime) to the same blockchain ledger. When the service duration ends, the smart contract automatically executes, calculating the final bill based on the immutable node-reported metrics and transferring payment from the service provider's wallet. This eliminates billing disputes and provides a verifiable audit trail of the CDN service delivery.
• Mermaid Diagram:

  sequenceDiagram
      autonumber
      Service Provider->>+Controller: Network Config Request
      Controller->>+Blockchain: Deploy Smart Contract (SLA)
      Controller->>+CDN Nodes: Configure Transfer Path
      CDN Nodes->>Blockchain: Log Proof-of-Delivery Metrics
      Note right of CDN Nodes: (Tx Volume, Uptime)
      Controller->>Blockchain: Signal Service End
      Blockchain->>Blockchain: Smart Contract Executes Billing
      Blockchain->>Service Provider: Debit Payment
      Blockchain->>Network Owner: Credit Payment
  

5. The "Inverse" or Failure Mode Derivatives

Derivative 5.1: Graceful Degradation Overlay Path

• Enabling Description: This derivative describes a "low-power" or "best-effort" configuration mode. A service provider can issue a network configuration request with a "low-priority" flag. The resource manager prioritizes nodes that are underutilized or have lower performance characteristics (e.g., lower CPU clock speeds, slower storage). The controller then configures a transfer path using these non-premium resources. The resulting overlay network provides a functional but lower-QoS content delivery service at a significantly reduced cost. This system is designed to fail safely: if a low-tier node fails, the controller automatically attempts to re-route to another available low-tier node, accepting a temporary service interruption as a trade-off for cost, rather than failing over to expensive high-tier resources.
• Mermaid Diagram:

  stateDiagram-v2
      state "High QoS Path" as High
      state "Degraded QoS Path" as Low
      state "Service Interrupted" as Fail
  
      [*] --> High : Premium Request
      High --> Low : High-Tier Node Failure
      Low --> High : High-Tier Node Recovers
      [*] --> Low : Low-Priority Request
      Low --> Fail : No Low-Tier Nodes Available
      Fail --> Low : Low-Tier Node Becomes Available
  

Combination Prior Art Scenarios

1. Combination with HTTP/3 and QUIC: The method of the '934 patent is combined with the QUIC protocol (an open IETF standard). The network configuration information from the service provider includes specific QUIC parameters, such as desired stream multiplexing priorities and congestion control algorithms (e.g., BBR, CUBIC). The controller configures the network nodes not just as IP-level forwarders but as QUIC-aware proxies. These nodes can terminate and re-originate QUIC connections, allowing them to make intelligent routing decisions based on application-layer metrics (like stream-specific packet loss) that are visible within the QUIC headers, enabling more robust delivery than a simple IP-based overlay.

2. Combination with Prometheus and Grafana (Open-Source Monitoring): The resource manager in the '934 patent is implemented by deploying Prometheus Node Exporter agents on every potential network node. The resource manager scrapes metrics from these agents into a centralized Prometheus time-series database. When a network configuration request is received, the controller queries this Prometheus database using PromQL to find nodes that meet the specified resource requirements (e.g., avg_over_time(node_cpu_seconds_total[5m]) < 0.5). The configured overlay network's performance is then monitored via pre-built Grafana dashboards, which are made accessible to the service provider for the duration of their service, leveraging a full open-source stack for resource management and reporting.

3. Combination with IPFS (InterPlanetary File System): The content delivery overlay network is configured to act as a private, managed swarm within the public InterPlanetary File System. The network configuration request specifies a set of content identifiers (CIDs) for the content to be delivered. The controller selects a plurality of network nodes and instructs them to join a private IPFS swarm and pin the specified CIDs. The configured transfer path is not a linear pipe but a managed mesh of IPFS nodes that can efficiently serve the content to users (who are also IPFS clients) via the protocol's content-addressed, peer-to-peer mechanisms. The overlay network is "deleted" by instructing the nodes to unpin the content and leave the private swarm.