Gateway Cable Modem Partitioned Architecture
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Designing a gateway cable modem that efficiently integrates data networking and VoIP services with traditional cable modem functionality while ensuring flexibility, performance, cost-effectiveness, and software re-use is challenging, particularly in meeting the requirements of CableHome and PacketCable initiatives.
Innovation Solution
A partitioned and flexible architecture for the gateway cable modem system, comprising a data networking engine and a cable modem engine, where the data networking engine handles advanced functions like IP routing, NAT, VPN, and VoIP, and the cable modem engine handles DOCSIS functions, with complete decoupling to allow independent software development and maintenance, optimized for performance and minimal hardware cost increase.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If data networking functions and cable modem functions are integrated in a single engine, then device complexity is reduced, but flexibility for independent software development and service upgrading deteriorates
Solution Approach 1:
The system is divided into two separate engines: a data networking engine for data processing functions and a cable modem engine for DOCSIS and VoIP functions. This segmentation allows independent software development, maintenance, and upgrading of each engine while maintaining manageable system complexity through clear functional boundaries.
2Adaptability or versatility
If data networking functions are added to traditional cable modem, then service functionality is improved, but hardware cost increases
Solution Approach 1:
The data networking engine is designed as a multi-functional platform that can handle IP routing, NAT, firewall, VPN, web server, and VoIP services. By consolidating these diverse functions into a single engine with shared processing resources, the system achieves high service functionality while minimizing incremental hardware cost compared to multiple separate devices.
3Productivity
If VoIP and data applications run concurrently in the same system, then resource utilization is improved, but voice packet delay and jitter increase
Solution Approach 1:
Voice and data applications are separated into different engines: VoIP processing occurs in the cable modem engine while data applications run in the data networking engine. This segmentation prevents data processing from interfering with voice packet handling, ensuring low delay and jitter for voice while still achieving high resource utilization through the shared hardware platform.
Solution Approach 2:
The system employs QoS mechanisms and dedicated voice processing paths that act as intermediaries to prioritize voice traffic. The cable modem engine handles VoIP with optimized data paths that minimize delay and jitter, while the data networking engine manages data applications, with both engines coordinated through standardized interfaces.
4Ease of manufacture
If existing cable modem software is ported to new gateway platform, then software re-use is improved, but software adaptation effort increases
Solution Approach 1:
The software architecture is segmented into modular components that can be independently ported and adapted. The data networking engine and cable modem engine have separate software stacks with well-defined interfaces, allowing existing cable modem software to be ported to the new platform with minimal changes while enabling independent development and upgrading of value-added services.
Data Source
AI summary
A cable modem system and architecture. A cable modem engine performs all cable modem functions, and a data networking engine performs all data and home networking functions. The cable modem engine is completely partitioned from the data networking engine. DOCSIS and VoIP functionality is implemented in the cable modem engine. The VoIP functionality may be in accordance with the PacketCable specification. The data networking functionality provided by the data networking engine may be in accordance with the CableHome specification.


