1. EV-DO Rev A QoS Configuration Dave Dukinfield Sr. Network Consultant November 2007

2. Starent Networks Proprietary and Confidential 2 End-to-End view of EVDO-Rev- A MFPA and QoS

3. Starent Networks Proprietary and Confidential 3 PCF-to-PDSN Interface Changes

4. Starent Networks Proprietary and Confidential 4 Flow-based Traffic Policing Permit the defined policies to implement: Access Control decisions QOS decisions Accounting decisions Generally defined as: Policyclass map, policy map, and policy group Conditionsource/destination address or source/destination port etc ActionFlow classification, QOS processing, and DSCP marking

5. Starent Networks Proprietary and Confidential 5 PaDIRT Proposed Profile IDs and DSCPs

6. Starent Networks Proprietary and Confidential 6 Class Map Configured on a per-subscriber basis either locally on the system or on a remote RADIUS server Class Map: Match packet based on: Source/destination ip address IP TOS field Protocol Source/destination port number or range of port numbers Packet size Created in the egress context 32 Class Maps per egress context can be configured Set to match all or any of the classification rules

7. Starent Networks Proprietary and Confidential 7 Class Map Example class-map name VOIP match-any match dst-port-range 2222 to 3333 match protocol udp match protocol tcp match src-ip-address 192.168.162.0/24 match dst-ip-address 192.168.162.0/24

8. Starent Networks Proprietary and Confidential 8 Policy Map Policy Maps: Access control (allow or discard) Qos traffic policing (cdr, pdr, cbs, with exceed and violate actions) Qos encapsulation header DSCP Marking (0x00 – 0x3f) Type (static or dynamic) Static type (the traffic flow classification and treatment is pre- defined with classification rules in the class map) Dynamic type (is based on Rev. A flows) Class Maps are assigned to Policy Maps Created in the egress context 32 Policy Maps per egress context can be configured

9. Starent Networks Proprietary and Confidential 9 Policy Map Example policy-map name signal class-map VOIP type dynamic three-gpp2 rev-A profile-id id 257 flow-id any qos encaps-header dscp-marking 0x2e qos user-datagram dscp-marking 0x2e policy-map name bearer class-map VOIP type dynamic three-gpp2 rev-A profile-id id 256 flow-id any qos encaps-header dscp-marking 0x2e qos user-datagram dscp-marking 0x2e

10. Starent Networks Proprietary and Confidential 10 Policy Group Policy Groups: Direction (in or out) Precedence (if a session flow matches multiple policies this key word will resolve them. A range from 1 to 16 can be assigned) Policy Maps are assigned to Policy Groups Created in the egress context 16 Policy Maps per Policy Group can be configured

11. Starent Networks Proprietary and Confidential 11 Policy Group Example policy-group name VOIP-QoS policy signal precedence 1 policy bearer precedence 2

12. Starent Networks Proprietary and Confidential 12 Subscriber Default Example subscriber default authorized-flow-profile-id 256 direction bidirectional authorized-flow-profile-id 257 direction bidirectional policy-group VOIP-QoS direction in policy-group VOIP-QoS direction out

13. Starent Networks Proprietary and Confidential 13 1xEV-DO Rev A Multi-flow QoS Additional Features QoS profile retrieval from H-AAA. Includes –Maximum Authorized Aggregate Bandwidth for Best-Effort traffic –Authorized QoS Profile IDs for each direction –Maximum per Flow priority –Maximum inter-user priority –Allowed Differentiated Services Markings Intra-chassis PDSN session recovery Flow-based accounting –Per-A10 accounting is the default system behavior –Per-flow accounting or both per-flow and per-A10 accounting are possible –MEID support in primary & auxiliary service connections Policy lookup table –L4 shallow packet inspection for initial TFT authorization & mid-session lookup –Includes static traffic filters per application –Per-flow traffic policing based on granted ProfileID

14. Starent Networks Proprietary and Confidential 14 Thank You For further information visit: www.starentnetworks.com Be advised that the information contained in Starent's product roadmaps do not constitute a promise or obligation of delivery of any functionality. Starent, at its sole discretion, and without notice to Customer, reserves the right to alter the design, specifications, and forecasted time to market of all of its products on any roadmap, at any time, as part of its continuing program of product development. This presentation is proprietary information of Starent Networks Corporation. The information contained may not be used to create or change any contractual obligation between Starent Networks Corporation and you or your firm. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this presentation by persons or entities other than the intended recipients is prohibited. This presentation is for planning and information purposes only. The specifications contained herein are subject to change without notice.

15. Starent Networks Proprietary and Confidential 15 Differentiated QoS End to End QoS Overview Same DSCP marking through network Main A10 Profile ID 256 SRID2 flow ID 1/2 FWD/REV DSCP 0x2E PCF PDSN/FA HA BE In-Net Server MIP Tunnel 0x2E Internet BE

16. Starent Networks Proprietary and Confidential 16 ITC Dynamic Policy for Differentiated QoS PDSN/FA- Forward Direction PCF PDSN/FA HA SRID 2; Flow ID 1 FWD (Profile ID 256) TFT a 1. Main A10 and Aux A10/Flows established, TFT created on PDSN SRID 2; Flow ID 2 REV (Profile ID 256) TFT b SRID 2; Flow ID 1 FWD (Profile ID 256) Policy-256-out marked DSCP 0x2E /DOS Main A10 0xBE Traffic matched TFT a MIP Tunnel Traffic matched TFT c BE Traffic Upon successful session/flows setup, dynamic policy facility in ITC can be used to provide the QoS treatment (such as DSCP marking & DOS) by matching the TFT dynamically established with the flows. Based on the different flow criteria (profile ID & TFT), different dynamic policy will get applied to the flows– Class-Map class256-out (matching TFT a) …. Policy-Map policy-256-out class-map class256-out 3gpp2 data-over-signaling marking qos encaps-header dscp 0x2E Policy-Group Differentiated QoS_policy policy-256-out precedence 1 ….

17. Starent Networks Proprietary and Confidential 17 ITC Dynamic Policy for Differentiated QoS PDSN/FA- Reverse Direction PCF PDSN/FA HA SRID 2; Flow ID 1 FWD (Profile ID 256) TFT a 1. Main A10 and Aux A10/Flows established, TFT created on PDSN 2. Upon successful session/flows setup, dynamic policy facility in ITC can be used to provide the QoS treatment (such as DSCP marking) by matching the TFT dynamically established with the flows. Based on the different flow criteria (profile ID & TFT), different dynamic policy will get applied to the flows – Class-Map class256-in (matching TFT b) …. Policy-Map policy-256-in 0x2E …. Policy-Group Differentiated QoS policy policy-256-in precedence 2 …. SRID 2; Flow ID 2 REV (Profile ID 256) TFT b SRID 2; Flow ID 1 FWD (Profile ID 256) PCF marked DSCP 0x2E Main A10 0xBE Traffic matched TFT b Policy-256-in marked MIP tunnel header 0x2E MIP Tunnel BE Traffic

18. Starent Networks Proprietary and Confidential 18 ITC Static Policy for Differentiated QoS HA- Forward Direction PDSN/FA HA HA could use static policy facility in ITC to provide the session QoS service such as DSCP marking. The subscriber traffic will be matched using the pre-defined filters in the classmap – Class-Map class-256-out src_ports 2222 to 3333 … Policy-Map policy-256-out (static) 0x2E …. Policy-Group Differentiated QoS_policy policy-256-out precedence 1 src_port 2000 match policy-256-out HA marked DSCP 0x2E MIP Tunnel 0xBE network src_port 2000 Server marked DSCP 0x2E QoS required Service 0xBE

19. Starent Networks Proprietary and Confidential 19 ITC Static Policy for Differentiated QoS HA- Reverse Direction PCF PDSN/FA HA HA could use static policy facility in ITC to provide the session QoS service such as DSCP marking. The subscriber traffic will be matched using the pre-defined filters in the classmap – Class-Map class-256-in dst_ports 2222 to 3333 Policy-Map policy-256-in (static) 0x2E Policy-Group Differentiated QoS_policy policy-256-in precedence 3 dst_port 2000 FA marked DSCP 0x2E MIP Tunnel 0xBE network Policy-256-in matched dst_port 2000 HA marked DSCP 0x2E 0xBE QoS required Service