RAN Data Architecture for QoS and Bandwidth Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The challenge in communication networks is managing Quality of Service (QoS) and bandwidth allocation effectively, especially with the increasing demand for simultaneous access to multiple services and applications over shared broadband connections, which requires prioritization and customization of data transport services.
Innovation Solution
The proposed data architecture includes maintaining records for QoS and bandwidth allocation at various points in the network, such as the Routing Gateway, Network Service Provider, and Application Service Provider, to enable end-to-end transport and manage access sessions, application flows, and service provider credentials, allowing for customized QoS and bandwidth management across multiple service providers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple services and applications are provided over a shared broadband connection, then service variety and user demand satisfaction are improved, but bandwidth allocation conflicts and QoS management complexity increase
Solution Approach 1:
The patent segments QoS management into separate functional components: access session records at the RAN for connection-level management, application flow records at the RAN for service-level management, and corresponding records at service providers for application-level management. This segmentation allows each component to handle specific aspects of QoS independently, reducing overall management complexity while supporting multiple services.
Solution Approach 2:
The patent introduces intermediary data structures (access session records and application flow records) that act as mediators between the RAN and multiple service providers. These records standardize QoS parameters and bandwidth allocation terms, enabling seamless interaction between diverse services without increasing management complexity at any single point.
2Reliability
If bandwidth allocation is customized for different services and applications, then service quality and user experience are improved, but network control complexity and coordination overhead increase
Solution Approach 1:
The patent applies local quality by maintaining customized QoS parameters in local records at each network entity (RAN and service providers). Each access session record and application flow record contains service-specific QoS parameters tailored to individual services and applications, allowing customized quality control without requiring centralized complex coordination for each service.
Solution Approach 2:
The patent establishes QoS parameters and bandwidth allocations in advance through pre-configured access session records and application flow records before services commence. This preliminary action defines quality requirements and allocation rules upfront, simplifying real-time network control while ensuring service quality requirements are met.
3Measurement precision
If QoS parameters are defined at multiple network points (RAN and service providers), then QoS enforcement accuracy is improved, but data synchronization and record consistency become more difficult
Solution Approach 1:
The patent creates corresponding copies of QoS records at different network locations: access session records at the RAN with corresponding records at service providers, and application flow records at the RAN with corresponding records at service providers. These copied records maintain consistent QoS parameters and bandwidth allocation terms, enabling accurate QoS enforcement across the network while preserving information consistency through standardized record structures.
Data Source
AI summary
Data architectures provide for managing Quality of Service (QoS) and/or bandwidth allocation in a Regional/Access Network (RAN) that provides end-to-end transport between a Network Service Provider (NSP) and/or an Application Service Provider (ASP), and a Customer Premises Network (CPN) that includes a Routing Gateway (RG). The data architecture includes a NSP access session record maintained at the RAN that defines QoS and/or bandwidth allocation for an access session, such as a Point-to-Point (PPP) access session, associated with the RG and the NSP. A corresponding NSP access session record is maintained at the NSP associated with the access session. The NSP access session record at the RAN and the corresponding NSP access session record at the NSP both define a QoS and/or bandwidth allocation specified by the NSP associated with the session or both define a QoS and/or bandwidth allocation specified by the RAN. An application flow record maintained at the RAN defines QoS and/or bandwidth allocation for an application flow associated with the RG and the ASP. A corresponding application flow record is maintained at the ASP associated with the application flow. Both the application flow record at the RAN and the corresponding application flow record at the ASP define a QoS and/or bandwidth allocation specified by the ASP.