1 / 24

The cdma2000 QoS as developed in TSG-X

The cdma2000 QoS as developed in TSG-X. Presentation prepared by: Jun Wang, jwang@qualcomm.com Alan Hsu, alan.hsu@nokia.com Kuntal Chowdhury, chowdury@nortelnetworks.com Pete McCann, mccap@lucent.com. Outline. QoS Architecture and Scope QoS_BLOB QoS Signaling

diata
Download Presentation

The cdma2000 QoS as developed in TSG-X

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The cdma2000 QoSas developed in TSG-X Presentation prepared by: Jun Wang, jwang@qualcomm.com Alan Hsu, alan.hsu@nokia.com Kuntal Chowdhury, chowdury@nortelnetworks.com Pete McCann, mccap@lucent.com

  2. Outline • QoS Architecture and Scope • QoS_BLOB • QoS Signaling • QoS User Profile and Authorization • QoS Call Flows • MMD Policy and MMD QoS Call Flow • Packet Data Service Options • QoS Handoff

  3. QoS Architecture and Scope • Quality of Service (QoS) refers to the provision of different quality assurances to different traffic flows, according to application requirements. • Same Network Design for HRPD and 1x. • Multiple service instances (cdma20001X). • Each with different bandwidth/delay/error characteristics. • Multiple RLP instances (cdma2000HRPD). • Each with different bandwidth/delay/error characteristics. • Flow Based QoS. • QoS control mechanisms include: • QoS Authorization. • Admission Control (Implementation dependent). • Packet Classification. • Queuing and Policing Policies (Implementation dependent). • Congestion Control (Implementation dependent).

  4. QoS Hierarchy (Example)

  5. PacketClassifier Air Interface IOS Interfaces PacketClassifier BSC/PCF (cdma2000 1X) AN/PCF (cdma2000 HRPD) MS PDSN Separate Air InterfaceService Instances/RLP Instances for different QoS Requirements Separate A10 Connections For Different QoS Requirements Packet Classification

  6. Packet Classification • Each application flow identified by a packet filter • A collection of header fields/values, e.g., UDP dest port = 2048 • Packet filters in MS come from local application knowledge (see note 1) • Packet filters in PDSN are explicitly signaled in an RSVP-like message from the MS • PDSN works the same for HRPD and 1X • Common flow mapping protocol Note 1: Some R&F comments suggested that the PDSN can also send packet filter to the MS in certain cases (resolution: TBD).

  7. QoS_BLOB • Requested QoS BLOB • Sent in air interface signaling from the MS to the RAN. The entire QoS_BLOB applies to cdma2000 1x only. • QoS_SUB_BLOB included in requested QoS_BLOB applies to both 1x and HRPD • Multiple QoS Levels can be included (Different acceptable levels of QoS for adaptive applications). • For each QoS level either a list of QoS parameters or a QoS Profile ID can be included. • Represents QoS needs for each flow • Via Operation Code (1x) or through air interface signaling (HRPD), the MS can indicate whether: • To Remove the flow. • To Add a flow. • To Update QoS for the flow. • To Reactivate the flow. • To Deactivate the flow.

  8. QoS_BLOB, contd. • Granted QoS BLOB • Sent in air interface signaling from the RAN to the MS. The entire QoS_BLOB applies to 1x only (Note: some R&F comments suggested QoS_SUB_BLOB can be used for both 1x and HRPD, resolution: TBD) • Represents granted QoS for each flow. • Can be used by the RAN to influence, e.g. • Channel rate. • Power control. • Number of RLP retransmissions. • MAC parameters.

  9. Overview of QoS Signaling • QoS User Profile is sent from the HAAA to the PDSN during the main service instance setup • The PDSN sends the QoS User Profile to the RAN via IOS signaling at the time of the packet data session establishment (simple/mobile IP) and may update the QoS profile later if necessary. • QoS_BLOB is exchanged between the MS and the RAN via over the air signaling. • Establish service instances/RLP flows via over the Air signaling. • The RAN performs both QoS authorization and admission control and sends the granted QoS to the MS. • The RAN also sends the granted QoS to the PDSN for accounting purpose via IOS Signaling. • RSVP-like messages exchanges between the MS and PDSN for packet filter setup.

  10. User’s QoS Profile • User’s QoS profile is stored in the Home RADIUS server. • It is related to the subscription of the user. • The QoS Profile contains the following parameters/attributes: • The Maximum Authorized Aggregate Bandwidth: indicates the maximum bandwidth that may be allocated to a user across all flows initiated or received by the user. • The Authorized QoS Profile IDs: a list of integer values, representing the QoS profile_ids for the QoS Profiles the user is allowed to request. The details of the standard QoS profile IDs may be defined in a separate document (TSB-58). • The Maximum per Flow Priority: indicates the maximum priority that the user can specify for a packet data flow. Priority 15 is the highest and 0 is the lowest.

  11. User’s QoS Profile, contd. • The Allowed Differentiated Services Markings: Specifies if the user is able to mark packets with AF (A), EF (E). The Max Class (i.e., Max Selector Class), specifies that the user may mark packets with a Class Selector Code Point that is less than or equal to Max Class. • The Service Option Profile: This attribute specifies the authorized packet data service options, the maximum number of simultaneous service instances of the given service option number (n), and the total maximum number of simultaneous service instances. • The Allowed Persistent TFTs: specifies the number of simultaneous persistent TFTs that may be established by the user. Persistent TFTs are those that exist at the PDSN regardless of the state of the corresponding service instance.

  12. QoS Authorization • QoS Authorization involves two places: • The PDSN authorization on allowed DiffServ Marking, SO profile and allowed Persistent TFT. • The RAN authorization on maximum authorized aggregated BW, authorized QoS Profile ID, and maximum per flow priority • The PDSN downloads the user’s QoS profile from Home RADIUS server and relays it to the RAN at the time of main SI or the first R-P setup. • The RAN caches the user’s QoS profile information received from the PDSN for the duration of the packet data session. • Upon receiving the QoS profile from the PDSN, the RAN checks existing (already admitted) service instances against the QoS profile. • Based on the outcome of this check, the RAN keeps or downgrades or disconnects the already admitted service instances. • The RAN performs QOS authorization based on the cached QoS profile information for subsequent QoS requests for new flows.

  13. QoS Authorization, call flow The MS initiates a new flow

  14. MS InitiatedQoS Setup BS/PCF PDSN MS AAA MS is aware of a data flow that needs a specific QoS or MS enters a new RAN 1. Main SI Setup (SO33) 2. Access request 3. Access Accept (QoS User Profile) 4. QoS User Profile 5. Flow QoS Request (QoS_BLOB or QOS_SUB_BLOB) 6. QoS Authorization and Admission Control 7. QoS Granted 8. Ack 9. A11-Registration Request (SR_ID, Granted QoS Parameters) 10. A11 Registration Reply 11. Resv (flow_id, Direction, FilterSpec) 12. ResvConf

  15. QoS Setup: Over the Air Signaling for 1x • OM/EOM can be used for Flow QoS Request • Service Connect Message (SCNM) can be used for QoS Granted and Service Connect Completion message (SCNCM) can be used for Ack. • Since SR_ID is required in OM/EOM, the MS can pick up unused SR_ID (SR_ID x) for the flow QoS request • The BS can make a decision based on: • If a new air interface service instance is needed to carry the new flow(s), the BS will connect SR_ID x in SCNM. • If the existing air interface service instance (SR_ID y) can satisfy the QoS requirement for the requested flow(s), the BS will include that SR_ID in SCNM.

  16. QoS Update Triggered by the BS BS/PCF PDSN MS AAA 1. Admitted QoS Flow(s) on Going The BS may decide so in response to, e.g. changing radio and traffic conditions. 2. BS wishes to update QoS based on original request QoS and QoS User Profile 3. A11-Registration Request (SR_ID,Updated QoS Parameters ) 4. A11 Registration Reply 5. QoS Update (SR_ID, Updated QoS_BLOB, Airlink Parameters 6. Ack

  17. Application Flow Removal Triggered by the MS BS/PCF PDSN MS AAA 1. Admitted QoS Flow(s) on Going The QoS parameters indicate the corresponding flow is removed. If no other flows are carried by the service instance, the BS may also request to disconnect the A10 connection. 2. MS decides to remove a flow 3. Request to remove flow 4. A11- Registration Request (SR_ID, QoS Parameters) 5. A11 Registration Reply 6. Remove Flow) 7. Ack

  18. Unsuccessful QoS setup attempt by MS AAA MS BS/PCF PDSN 1. Main SI Setup MS is aware of a data flow that needs a specific QoS or MS enters a new RAN 2. Access request 3. Access Accept (QoS User Profile) 5. Flow QoS Request (QoS_BLOB or QOS_SUB_BLOB) 4. QoS User Profile 6. QoS Authorization QoS Authorization fails! and Admission Control 7. Reject

  19. QoS with MMD • The QoS support with Multi Media Domain (X.P0013) requires additional considerations. • In MMD, the QoS negotiated during the SIP exchange gets downloaded into the PDSN Policy Enforcement Point (PEP) via the Go interface. • The Go/Policy event is triggered by the presence of MMD_FLOW_ID and Auth token in flow mapping signal. • The PDSN remains as the PEP for the flow. • The PDSN compares between already granted QoS (received from the RAN) and the session QoS (received from the PDF). • If the session QoS is within the granted QoS, the PDSN will send Resv Conf to the MS; otherwise, the PDSN will send Resv Error to the MS. • The PDSN relays the session QoS to the RAN if the session QoS is within (=<) the granted QoS. The RAN may later downgrade/upgrade the QoS based on original requested QoS, QoS user profile, authorized session QoS and available radio resources.

  20. QoS with MMD, call flow

  21. Service Option (SO) • Identifies the type of service • Packet Data Service Options: • SO 33: 1x main packet data service (for PPP connection control) • SO59: HRPD main packet data service (for PPP connection control) • SO 66: 1x auxiliary packet data service • SO xx: HRPD auxiliary packet data service (TBD) • SO 60: 1x header removal for VOIP • SO 61: 1x LLA-ROHC for VOIP

  22. Backup Slides There is no agreement in TSG-X on the material in the subsequent slides. These slides are included solely for discussion purpose.

  23. Intra-PDSN Inter-PCF QoS Handoff • All Service Instances in Dormant • PCF should store all original requested QoS from the MS • The MS only sends SO33 for the main SI setup and the target PCF establishes the A10 for the Main SI • The PDSN gets original requested QoS from the serving PCF and passes them to the target PCF during the Main SI setup • The Target PCF has the responsibility to setup A10 connections for all other auxiliary SIs • Some Service Instances in Active and some Service Instances in Dormant • For active SIs, the serving RAN sends original requested and granted QoS info to the target RAN • If Active Sis doesn’t include SO33/SO59, the target PCF has the responsibility to setup the main SI first • For auxiliary dormant SIs, follows the same rules as described above

  24. Inter-PDSN QoS Handoff • The PPP is renegotiated between the MS and the PDSN • The MS re-sends original requested QoS to the RAN • The MS triggers all SI setup for A10 connections • Main SI and all Auxiliary SIs • The MS re-sends RSVP-like message to the PDSN for Packet Filter establishment

More Related