Virtual Cable Hub Separating Software From Hardware

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cable hubs face challenges in sustainable scaling and operational efficiency due to hardware-based approaches, which are labor-intensive and costly, failing to meet growing consumer demands and requiring frequent upgrades, leading to increased electricity expenses and facility space issues.

Innovation Solution

The implementation of a virtual cable hub using cloud technologies for telemetry and monitoring, configuration, and orchestration, leveraging virtualization techniques such as containerization and virtual machines to separate software from hardware, enabling scalable and agile deployment of services on commercial off-the-shelf x86 platforms, reducing operational expenditure and improving resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If hardware-based cable hub architecture is used, then service deployment is stable and reliable, but scaling is unsustainable and operational costs increase

Engineering Contradiction:
Improveservice deployment speedVSAvoidhardware infrastructure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent replaces the mechanical hardware-based cable hub architecture with a virtualized software-based system. Virtual network functions (VNFs) and virtual machines (VMs) substitute physical hardware components, enabling services to be deployed as software instances rather than requiring physical hardware installation and configuration. This substitution dramatically accelerates service deployment while reducing hardware complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The virtualized cable hub architecture enables a single hardware platform to host multiple virtual network functions and serve multiple service purposes simultaneously. The same infrastructure can deploy different services (DOCSIS, PON, Ethernet) through software configuration rather than requiring dedicated hardware for each service type, achieving multi-functionality and scalable deployment.

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

2Adaptability or versatility

If frequent hardware upgrades are performed to meet growing consumer demands, then service capacity increases, but operational expenditure and electricity expenses increase

Engineering Contradiction:
Improveservice capacityVSAvoidelectricity consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by stationary object

Solution Approach 1:

The virtualized architecture enables dynamic allocation of computing resources through virtual machines and containers. Service capacity can be adjusted by allocating or deallocating virtual resources without physical hardware changes. This dynamic approach allows the system to adapt to growing consumer demands by optimizing resource utilization and avoiding the need for frequent hardware upgrades that consume additional energy.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent uses virtualization to create virtual copies of network functions and services that can be rapidly deployed and scaled. Instead of physically upgrading hardware to increase capacity, the system creates additional virtual service instances that share the underlying hardware infrastructure, thereby increasing service capacity without proportionally increasing energy consumption.

Inventive Principle:
Principle #26Copying

3Ease of operation

If traditional hardware-based cable hub is used, then service deployment is straightforward, but labor-intensive operations and facility space requirements increase

Engineering Contradiction:
Improveservice deployment easeVSAvoidoperational efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The virtualized cable hub incorporates automated orchestration and self-provisioning capabilities that reduce manual labor. The system can automatically allocate resources, configure services, and manage virtual network functions without extensive human intervention. This self-service automation maintains ease of operation while dramatically improving operational efficiency by eliminating repetitive manual tasks.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces a virtualization layer and orchestration platform that acts as an intermediary between service requests and physical infrastructure. This intermediary automates complex deployment tasks, manages resource allocation, and coordinates service delivery, thereby simplifying operations for users while improving overall operational efficiency through automation.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If virtualization techniques are implemented, then scalability and resource utilization improve, but system complexity increases

Engineering Contradiction:
ImprovescalabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments network functions into modular virtual network functions (VNFs) that can be independently deployed, managed, and scaled. This segmentation allows complex services to be broken down into manageable functional units, improving scalability while the modular nature helps manage system complexity through standardized interfaces and independent lifecycle management of each VNF component.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11665012B2Virtual access hub
Publication Date: 2023.05.30 HARMONIC INC
  • US11665012B2 patent drawing
  • US11665012B2 patent drawing
  • US11665012B2 patent drawing

AI summary

A multi-tenant application that provides high speed data services to one or more subscriber devices. The multi-tenant application comprises one or more first servers that each perform packet switching and routing and one or more second servers that each perform FCAPS functions for the one or more subscriber devices. FCAPS functions comprise fault operations, configuration operations, accounting operations, performance operations, and security operations. Each of the one or more first and second servers are implemented entirely within an application-specific logical host composed of one or more application containers. The one or more second servers may optionally each further perform network functions and user plane functions for the one or more subscriber devices. The one or more second servers may optionally each further perform OLT control functions and OLT MAC/PHY functions for the one or more subscriber devices.