QoS Flow Mapping in CDMA2000 Mobile IP Interfaces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current DiffServ architecture in CDMA2000/3GPP2 networks lacks a mechanism to ensure quality of service (QoS) for both uplink and downlink traffic on the same service instance, particularly failing to differentiate between flows with varying QoS requirements.
Innovation Solution
A signaling protocol and method that allows wireless network nodes to receive and grant QoS parameters for flows, enabling QoS management between radio nodes and packet switching data nodes, allowing multiple flows within a service instance and optimizing bandwidth usage by implementing QoS-related information at the edge routers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single service instance is used for both uplink and downlink traffic, then device complexity is reduced, but quality of service differentiation between flows is lost
Solution Approach 1:
The patent segments the service instance into multiple flows, where each flow can have independent QoS parameters. The service instance is divided into uplink flow and downlink flow, each with separate QoS profiles, allowing differentiated treatment while maintaining a unified service instance structure.
Solution Approach 2:
The patent applies local quality by allowing different QoS characteristics within different parts of the same service instance. Specifically, uplink traffic and downlink traffic within the same service instance can have different bandwidth, delay, and reliability requirements, enabling localized QoS optimization without requiring separate service instances.
2Reliability
If multiple service instances are created for different QoS requirements, then quality of service differentiation is achieved, but device complexity increases
Solution Approach 1:
The patent merges multiple flows with different QoS requirements into a single service instance by introducing flow identifiers (Flow ID) and QoS parameter associations. Instead of creating separate service instances for uplink and downlink or for different applications, multiple flows are combined in one service instance with each flow tagged with its specific QoS profile.
Solution Approach 2:
The service instance is designed to be universal and multi-functional, capable of accommodating multiple different types of traffic flows (uplink, downlink, different applications) within a single instance. The Flow ID mechanism enables the service instance to universally handle diverse traffic types without requiring instance-specific configurations for each flow type.
3Reliability
If QoS parameters are managed at core network nodes, then quality of service control is centralized, but network efficiency decreases due to increased node complexity
Solution Approach 1:
The patent extracts QoS management functionality from core network nodes and places it at the network edge, specifically at the access network node where the service instance is established. The QoS parameters are associated with flows at the edge node, and core nodes simply forward packets based on Flow IDs without needing to interpret or manage QoS parameters, thereby maintaining QoS control while improving core network efficiency.
Solution Approach 2:
The patent introduces Flow ID as an intermediary mechanism that bridges edge QoS management and core network forwarding. The Flow ID acts as a mediator that carries QoS information from the edge to the core without requiring core nodes to process complex QoS parameters, enabling efficient end-to-end QoS management with minimal core node involvement.
Data Source
AI summary
A signaling regimen between a mobile station MS, a radio node RN, and a packet data switching node PDSN enables a quality parameter to be applied to packets moving between a mobile and a CDMA2000 network. The MS creates a new flow for packets of a certain data type and sends a related quality parameter for that flow to the BS. The BS determines whether an existing or new service instance will carry the new flow, and obtains authorization for the service instance to meet the quality parameter from the PDSN. The BS or PDSN builds a map between flow and a policy that ensures the quality is met, and the map is used to place different packets into the appropriate flow and service instance. Policies and enforcement may differ on uplink and downlink.