Cloud-Edge Network Architecture for Reducing Bufferbloat
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The immense growth of the internet has resulted in a complex network architecture that is difficult to monitor and manage due to its large scale, leading to issues like bufferbloat, delays, and increased costs, especially with centralized data centers requiring numerous gateway nodes, which escalate Capital Expenditure (CAPEX) and Operational Expenditure (OPEX) budgets.
Innovation Solution
A Cloud-Edge network architecture that reduces bufferbloat and delays by storing necessary data in Edge instances, eliminating the need for traffic to be transmitted to centralized nodes, and utilizing a shared data layer for subscriber management, enabling real-time updated subscriber information and efficient billing, while also supporting flexible architecture transitions and redundancy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized data center architecture is used to manage subscriber data, then data management control is improved, but network delays and bufferbloat increase due to extensive data transfers between edge nodes and centralized nodes
Solution Approach 1:
The patent segments the centralized subscriber data management system into distributed data centers located at edge network nodes. Each edge node maintains local subscriber data, eliminating the need for continuous communication with a centralized data center. This segmentation resolves the contradiction by distributing data management control to edge locations, thereby maintaining reliability while reducing network delays and bufferbloat associated with centralized architectures.
2Productivity
If the number of gateway nodes is increased to handle growing data traffic, then network capacity is improved, but Capital Expenditure and Operational Expenditure budgets escalate significantly
Solution Approach 1:
The patent implements data centers at edge network nodes that serve multiple functions: local subscriber data management, content caching, and service delivery. This multi-functionality allows existing edge infrastructure to handle growing data traffic without requiring proportional increases in gateway nodes. The universal edge data centers resolve the contradiction by improving network capacity through efficient local processing rather than expanding expensive centralized gateway infrastructure.
3Stability of the object's composition
If data is stored centrally in a centralized data center, then data consistency is improved, but network load increases due to frequent data transfers between edge instances and centralized nodes
Solution Approach 1:
The patent implements preliminary synchronization of subscriber data to edge data centers before it is needed for service delivery. Edge nodes maintain local copies of subscriber data, eliminating the need for frequent real-time transfers to centralized data centers. This preliminary action resolves the contradiction by ensuring data consistency through advance synchronization while minimizing ongoing network load and energy consumption.
4Ease of manufacture
If existing gateway architecture is maintained to avoid expensive changes, then infrastructure investment is preserved, but network complexity and difficulty of monitoring increase due to massive scale
Solution Approach 1:
The patent adds a new dimension to the network architecture by implementing data centers at edge nodes rather than only at centralized locations. This dimensional shift from centralized-to-edge distribution transforms the network topology, allowing existing gateway infrastructure to be maintained while reducing overall network complexity. The edge data centers handle local data management, simplifying monitoring and control without requiring expensive gateway upgrades.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A communications network comprising: a centralized network gateway entity having a horizontal layer with a common data layer, CDL; one or more locally based server entities having vertically virtualized services, wherein the centralized network gateway entity is physically connected over a Common Service Layer, CSL, to the one or more locally based server entities over an access point or a gateway or a Radio Access Network, RAN, site; and a centralized database having one or more front end, FE, instances, the centralized database being connected to the network gateway entity and to the locally based server entity over the access point or the gateway or the RAN site.