Access Edge Node Data Traffic Aggregation via Service Bindings
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
IP networks face challenges in supporting a broad range of quality of service (QoS) levels due to their design principles, which result in 'best effort' networks that struggle to handle increased data traffic from growing user domains and service provider domains, lacking a long-term solution for tangible and non-destructive Quality of Service (QoS) improvements.
Innovation Solution
The introduction of an access edge node, a decentralized node, and an access node, along with a method for efficiently aggregating data traffic over an access domain, utilizing service agents, service bindings, and Virtual Local Area Networks (VLANs) to provide coordinated usage of the access network and various levels of QoS, by establishing service bindings and managing data traffic aggregation between user domains and service provider domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If IP networks rely on routers performing minimal operations for routing data traffic, then device complexity is reduced and ease of operation is improved, but quality of service deteriorates and the network cannot support increased data traffic demands
Solution Approach 1:
The network is segmented into multiple domains (access domain, network service provider domains, application service provider domains) with specialized nodes for different functions. Access edge nodes handle service-specific operations while core routers perform simple routing, dividing the QoS management burden from the routing function.
Solution Approach 2:
Access edge nodes act as intermediaries between user domains and service provider domains. These intermediary nodes perform service-specific processing and traffic aggregation, shielding core routers from complex QoS management while ensuring service quality requirements are met.
2Productivity
If the number of user domains and service provider domains increases to meet growing data traffic demands, then productivity and service coverage are improved, but network complexity increases and quality of service deteriorates
Solution Approach 1:
The network is organized into hierarchical domains with access edge nodes at the perimeter, service provider domains in the middle, and core routing infrastructure at the center. This segmentation allows independent scaling of each domain without proportionally increasing overall network complexity.
Solution Approach 2:
The network architecture adds a domain dimension to the traditional flat routing structure. By organizing nodes into multiple service provider domains and application service provider domains, the network can scale horizontally across domains while maintaining manageable complexity within each domain.
3Device complexity
If IP networks are designed with best effort routing principles, then device complexity and operational simplicity are maintained, but the ability to support quality of service for network service provider domains and application service provider domains deteriorates
Solution Approach 1:
Different parts of the network have different functional qualities. Access edge nodes are equipped with service-specific processing capabilities for QoS management, while core routers maintain simple forwarding functionality. This local differentiation allows QoS support without making all network devices complex.
Solution Approach 2:
Access edge nodes serve as intermediary entities that translate service quality requirements into routing decisions. These intermediaries handle the complexity of QoS policy enforcement and traffic aggregation, allowing core routers to remain simple while the network as a whole gains QoS adaptability.
Data Source
AI summary
The present invention relates to a method, an access node, an access edge node and a decentralized node for aggregating data traffic over an access domain. The decentralized node corresponds to one of the service providers, and is located in closer proximity with user domains to be serviced. The decentralized node maintains over the access domain one or several Virtual Local Area Networks, for aggregating thereon data traffic to be exchanged with the user domains, on behalf of the service provider domain. To allow proper aggregation of the data traffic, service bindings are created and stored at the access edge node, and further stored at the decentralized node and at the access node. Therefore, aggregation of the data traffic between the decentralized node and the user domains over the access domain is performed in accordance with the created service bindings.