Router Notifier for Scalable Virtual Cable Modem Termination System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current virtual Cable Modem Termination Systems (vCMTS) face challenges in scalability and high availability due to limitations in managing Address Resolution Protocol (ARP)/Neighbor Discovery (ND) entries, finite capacity of commercial-off-the-shelf routers, complex prefix delegation, and high operational costs associated with adding routers to scale.

Innovation Solution

The introduction of a router notifier software component that manages route data for edge routers, eliminating the need for ARP/ND exchanges and allowing for efficient route updates, enabling edge routers to support many more routes without increasing the number of routers and simplifying prefix delegation by using Border Gateway Protocol (BGP) for communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If commercial off-the-shelf routers are used to manage ARP/ND entries in vCMTS, then the system can be implemented with standard hardware, but the finite capacity of these routers limits scalability and increases operational strain

Engineering Contradiction:
ImprovescalabilityVSAvoidnumber of ARP/ND entries
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts the ARP/ND entry management function from the edge routers and places it in a dedicated router notifier component. This separation removes the limitation of finite router entry capacity, allowing the system to scale by adding routing capacity without being constrained by ARP/ND table sizes in standard routers.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The router notifier acts as an intermediary between the core server and edge routers, managing route data and ARP/ND information centrally. This mediator component handles the complexity of entry management, allowing edge routers to focus on forwarding traffic while the notifier maintains accurate routing information across the distributed system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Quantity of substance

If more routers are added to increase routing capacity, then the system can support more cable modems and CPEs, but the operational cost and system complexity increase

Engineering Contradiction:
Improverouting capacityVSAvoidnumber of routers
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent merges the routing function across multiple edge routers through a unified route data management system. The router notifier maintains a centralized view of all routes and distributes relevant information to appropriate edge routers, allowing the system to function as a unified routing platform rather than isolated router instances, thereby reducing overall complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The router notifier serves multiple functions: it manages ARP/ND entries, maintains route data, notifies edge routers of changes, and coordinates prefix delegation. This multi-functional component consolidates what would otherwise require multiple specialized components or additional router functions, reducing system complexity while increasing capacity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Loss of information

If ARP/ND exchanges are used for route updates between core server and edge routers, then the routing information can be maintained, but the message exchanges increase operational strain and reduce efficiency

Engineering Contradiction:
Improverouting information accuracyVSAvoidmessage exchange overhead
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The router notifier pre-establishes and maintains a comprehensive route data structure that includes all possible routing information. When routing changes occur, the notifier has the information ready and can notify edge routers immediately without requiring iterative ARP/ND exchange sequences, thereby reducing message overhead and time delays.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the router notifier continuously monitors route data changes and actively pushes updates to edge routers. This feedback loop ensures routing information accuracy while being more efficient than reactive ARP/ND exchanges, as updates are triggered only when necessary and delivered directly to affected routers.

Inventive Principle:
Principle #23Feedback

4Adaptability or versatility

If prefix delegation is managed using traditional methods, then the system can support mobile customers, but the complexity of maintaining stable prefixes across physical moves increases

Engineering Contradiction:
Improveprefix delegation capabilityVSAvoidprefix management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The router notifier serves as an intermediary for prefix delegation management, coordinating between the core server and edge routers. When a customer moves physically, the notifier manages the prefix reassignment process, ensuring stable prefix delegation by maintaining accurate mapping between customers, their locations, and assigned prefixes, thereby reducing the complexity of mobile support.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11368553B1Support for a scalable and high availability (HA) virtual cable modem termination system (VCMTS)
Publication Date: 2022.06.21 HARMONIC INC
  • US11368553B1 patent drawing
  • US11368553B1 patent drawing
  • US11368553B1 patent drawing

AI summary

Supporting a scalable and Highly Available (HA) virtual Cable Modem Termination System (vCMTS). A software component receives, from the vCMTS, an update about a particular cable modem (CM) or customer premises equipment (CPE). The update may be sent in response to the particular CM or CPE becoming online or offline. In response to receiving the update, the software component provides, to at least one edge router, route data for the particular CM or CPE. The route data informs the edge router of a next hop network address for a network address of the particular CM or CPE. The edge router is not and need not be provided with either (a) any Address Resolution Protocol (ARP) data for the particular CM or CPE and (b) any Neighbor Discovery (ND) data for the particular CM or CPE.