EV-DO Rev A End to End QoS

Dave Dukinfield Sr. Network Consultant

August 2007

End-to-End view of EVDO-RevA MFPA and QoS

Application QoS N egotiation (e.g. SIP/SD P) App. QoS IP QoS

Packet D ata QoS Signaling (R SVP-like m essages)

IP N e tw o rk

3 GPP 3 Protocols

R adio QoS Signaling

A3/A3 3 QoS 3 GPP 3 Signaling Protocols

M o b ile Sta tio n

BSC /PC F

PDSN

Fa r-En d Te rm in a l

Starent Networks Proprietary and Confidential

PCF-to-PDSN Interface Changes

AAA Server

Link Flows

A33

IP Network

MS/AT

MS/AT

PDSN RAN/PCF IP Flows Auxiliary A33 s Main A11

end-to-end IP Flows

Starent Networks Proprietary and Confidential

EV-DO Rev A Service

Multiflow QoS
Profile Mgr Profile ID1=VoIP
Request QoS for the bearer

AAA

RP Signaling P-CSCF

I/S-CSCF

Fwd RLP Flow # 0 (BE) Rev RLP Flow # 0 (BE) Fwd RLP Flow # 1 Rev RLP Flow # 1

Internet

PDSN

RSVP TFT

PDSN uses RSVP TFT signaling for flow mapping & packet filter
establishment
A single A11 can signal up to 7 bidirectional auxiliary service connections per session & up to 10 service flows May include optional channel treatments (ROHC or VJ header compression)

Benefits: Enables provisioning of QoS differentiated converged

services
Permits real-time, delay sensitive services with acceptable call quality on MMD networks
Starent Networks Proprietary and Confidential

A11 Requests
A10 connection created by A11 request from PCF A11 includes:
Data service option type - represented standard SO codes SR_ID 1 (Main A10) Default flow IDs - 255 forward, 255 reverse

When PDSN receives A11 request:

PDSN authenticates and retrieves the QoS from AAA PDSN sends back A11 RRP to establish MAIN A10

Starent Networks Proprietary and Confidential

Rev A Call Setup

MN
1. 2. 3. A11 RRQ (establish Main 10) Access Request (PDSN request subscriber QoS profiles) Access Accept (QoS profiles received) (MS becomes aware of a dataflow that requires a specific QoS) Main A10 establishment: a) PDSN sends RRP b) PPP/LCP/IPCP negotiates c) PDSN sends A11 Session Update d) PCF sends A11 Update Ack to PDSN 5. 6. 7. 8. 9. RSVP (MN requests flow with a particular QoS) RAN authorizes access and QoS RAN sends QoS confirmation MN acknowledges confirmation A11 RRQ (establish Aux A10's)
3 3 1 1 3 3 3 3 3 3 3 MS becomes aware of a dataflow that requires a specific QoS 3

RAN

PDSN

AAA

4.

10. A11 RRP (establish aux A10s) 11. MN sends TFT to PDSN 12. PDSN confirms receipt of TFT

3 3

Starent Networks Proprietary and Confidential

QoS on the PDSN

QoS on the PDSN consist of two things:
Rev A QoS ProfilesSubscriber based profiles configured on the AAA server, which are defined by the provider. PoliciesConfigured in a Policy Lookup Table on the PDSN using ITC. PDSN validates the Policies after the Auxiliary A10s are setup over the PCF-PDSN to determine what type of flow treatment (if any) to apply to the application flows sent from the MN.

Starent Networks Proprietary and Confidential

Intelligent Traffic Control

Differentiated QoS / DoS Support

Goals: Facilitate migration of subscribers to Rev A network

Enable Differentiated QoS End to End Define multiple high priority, low latency QoS levels to provide rapid set-up required of Multimedia based services

ITC policy engine requirements

5 tuple packet filters static or dynamic policy definitions Apply DSCP marking from user payload to reverse tunneled MIP headers Apply DSCP in forward direction to A10 GRE header per Policy-Map Apply DoS eligibility bit to A10 GRE header in forward direction

Starent Networks Proprietary and Confidential

Intelligent Traffic Control Differentiated QoS / DoS Support

ITC is a licensed feature Uses flow-based traffic policing Enables configuring and enforcing bandwidth limitations per
subscriber for both uplink and downlink directions

Supports various policy definitions for:

QOS Bandwidth Access Control

Policy definitions enforce and manage service level

agreements per subscriber profile
Starent Networks Proprietary and Confidential

The Subscriber QoS Profile

QoS Authorization is based on the per subscriber QoS
profile that is stored in the Home AAA

The PDSN downloads the profile during PPP/MIP setup and

stores the info. The PDSN also forwards the relevant info to the RNC
The Maximum Authorized Aggregate Bandwidth for Best-Effort traffic The Authorized QoS Profile IDs for each direction The maximum per Flow priority Inter-User Priority for best effort traffic Service Option profile The Allowed Number of Persistent TFTs The Allowed Differentiated Services Markings

The Sub QoS profile consists of the following :

If MN performs no PPP/MIP auth, then the PDSN uses a

default QoS profile that is locally provisioned
Starent Networks Proprietary and Confidential

10

Traffic Control Templates (TFT)

Traffic flow templates are sent from the MN after Main and
Aux. A10s are created

TFT contains:
One or more packet filters Source and destination ports Source and destination addresses Protocol

TFT are sent to PDSN via RSVP

Starent Networks Proprietary and Confidential

11

Dynamic Flow Mapping

The protocol used for flow mapping:

The protocol used is RSVP (RFC 2205) with some protocol exceptions. The RESV message is sent directly to the PDSN w/o a PATH message. The RESV message is destined for the PDSN and not to any endhost. The Protocol ID is set to 17 and DstPort is set to 3455. The RESV message contains a 3GPP2_Object. The 3GPP2_Object was created to carry the TFT (Traffic Flow Template) for flow mapping, HRIP (Header Removal Initialization Parameters, 1x only) and Channel Treatment Info. The 3GPP2_Object has the following IANA assignment: Class Number = 231, Class Name = 3GPP2_OBJECT Class Type or C-Type = 1.

Starent Networks Proprietary and Confidential

12

Sample TFT
<srid value="4" so="64" /> <flow_discriminator value="1" /> <specific value="false"/> <flow_dir value = "forward" /> <opcode value="add_pkt_fltr" />

<pkt_fltr flow_id="155" > <precedence value="127" /> <dscp value="3e"/> <req_prof_ids value="67,1915,864,1655,12127" /> <pkt_fltr_content pf_type="0">

<pkt_fltr_component type=""> <port_src_start value="15000" /> </pkt_fltr_component>

<pkt_fltr_component type=""> <port_src_end value="15999" /> </pkt_fltr_component>

</pkt_fltr_content> </pkt_fltr> Starent Networks Proprietary and Confidential

13

Overview of QoS Signaling

The HAAA sends the Authorized QoS Profile Ids, Service Option Profile
to the PDSN during the PPP/Mobile IP session setup

The PDSN sends the Authorized QoS Profile Ids, Service Option

Profile to the RAN/RNC via IOS signaling at the time of the packet data session establishment (simple/mobile IP) and may update the QoS profile later if necessary over the air signaling

The QoS_BLOB is exchanged between the MS and the RAN/RNC via Establish service instances/RLP flows via over the Air signaling The RAN/RNC performs QoS authorization and admission control and
sends the granted QoS to the MS purpose via IOS Signaling

The RAN/RNC also sends the granted QoS to the PDSN for accounting RSVP-like messages exchanged between the MS and the PDSN for
packet filter setup for flow mapping and flow based accounting
Starent Networks Proprietary and Confidential

14

Rev A with Policy Validation Call Setup

1. A11 RRQ (establish Main 10) 2. Access Request (PDSN request subscriber QoS profiles) 3. Access Accept (QoS profiles received) (MS becomes aware of a dataflow that requires a specific QoS) 4. Main A10 establishment: a) PDSN sends RRP b) PPP/LCP/IPCP negotiates c) PDSN sends A11 Session Update d) PCF sends A11 Update Ack to PDSN 5. RSVP (MN requests flow with a particular QoS) 6. RAN authorizes access and QoS 7. RAN sends QoS confirmation 8. MN acknowledges confirmation 9. A11 RRQ (establish Aux A10's) 10.A11 RRP (establish Aux A10s) 11.MN sends TFT to PDSN 12.PDSN confirms receipt of TFT 13.PDSN Validates Policy by comparing info from TFT (step 11) and PFC A11 (step 4). 14.Policy map is applied to flow and call is forwarded with proper flow treatment Starent Networks Proprietary and Confidential
3 3 3 3 3 3 3 3 3 3 3 MS becomes aware of a dataflow that requires a specific QoS 3

MN
3

RAN

PDSN

AAA

3 3

1 1

15

Policy Validation Failure

1. A11 RRQ (establish Main 10) 2. Access Request (PDSN request subscriber QoS profiles) 3. Access Accept (QoS profiles received) (MS becomes aware of a dataflow that requires a specific QoS) 4. Main A10 establishment: a) PDSN sends RRP b) PPP/LCP/IPCP negotiates
3 MS becomes aware of a dataflow that requires a specific QoS 3

MN
3

RAN

PDSN

AAA

3 3

c) PDSN sends A11 Session Update

3

d) PCF sends A11 Update Ack to PDSN 5. RSVP (MN requests flow with a particular QoS) 6. RAN authorizes access and QoS 7. RAN sends QoS confirmation 8. MN acknowledges confirmation 9. A11 RRQ (establish Aux A10's) 10. A11 RRP (establish Aux A10s) 11. MN sends TFT to PDSN 12. PDSN confirms receipt of TFT 13. Policy Validation Failure. 14. All flows are mapped over Main A10 with a flow treatment of Best Effort

3 3

1 1

3 3

3 3 3 3

3 (Main A3 , BE) 3 3

Starent Networks Proprietary and Confidential

16

Flow-based Traffic Policing

Policy modules interact with the system through a set of well
defined entry points

Provides access to a stream of system events Permit the defined policies to implement:
Access Control decisions QOS decisions Accounting decisions

Generally defined as:

Policy Action
class map, policy map, and policy group

Condition source/destination address or source/destination port etc.

Flow classification, QOS processing, and DSCP marking
17
Starent Networks Proprietary and Confidential

How Policy Validation Works

In making these determinations, the PDSN must use information from three sources: 1. TFT sent by the MN in step 11 (flow ID and filters). 2. A11 RRQ sent by the PCF in step 9 (QoS Profiles, SR_ID, and flow ID). 3. Policies configured with ITC (Profile ID and filters).
MN PCF PDSN

Policy class-map (name = TFT) src-port range 3333 -3333 Qos Profiles (from AAA) polcy map (name = TFT) class-map TFT type dynamic three-gpp1Rev-A profile-ID range 11111 x -11111 x flow-ID any policy group (PGroup-3 ) policy map TFT

TFT
SRC Port =3333 Filter ID = 3

Starent Networks Proprietary and Confidential

18

How Policy Validation Works (continued)

MN PCF PDSN Policy class-map (name = TFT) src-port range 3333 -3333 Qos Profiles (from AAA) polcy map (name = TFT) class-map TFT type dynamic three-gpp1Rev-A profile-ID range 11111 x -11111 x flow-ID any policy group (PGroup-3 ) policy map TFT

TFT
SRC Port =3333 Filter ID = 3

1. TFT is sent via RSVP message to be validated by the Policy group applied to the subscriber profile. 2. TFT is checked against class map found in the policy map defined in the policy group (PGroup1) 3. If TFT is matched successfully, the policy map is applied to the flow (no updates sent to PCF) and the call is forwarded with the proper flow treatment. If TFT is not matched successfully, the policy map cannot be applied to the flow (updates are sent to the PCF) and the call is forwarded with a best effort across the Main A10 connection.

Starent Networks Proprietary and Confidential

19

Differentiated QoS End to End QoS Overview Same DSCP marking through network
PCF PDSN/FA HA
In-Net Server Internet

MIP Tunnel

Main A10
BE

BE

BE

Profile ID 261 SRID2 flow ID 1/2 FWD/REV

DSCP 0x2E

0x2E

0x2E

Starent Networks Proprietary and Confidential

20

ITC Dynamic Policy for Differentiated QoS PDSN/FA- Forward Direction

PCF
Main A10 and Aux A10/Flows established,. 1 TFT created on PDSN
SRID 2; Flow ID 1 FWD (Profile ID 261) TFT a SRID 2; Flow ID 2 REV (Profile ID 261) TFT b

PDSN/FA

2. 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
class261-out (matching TFT a) . Policy-Map policy-261-out class-map class261-out 3gpp2 data-over-signaling marking qos encaps-header dscp 0x2E Policy-Group Differentiated QoS_policy policy-261-out precedence 1 Class-Map

HA

Main A10 0xBE MIP Tunnel )SRID 2; Flow ID 1 FWD (Profile ID 261

Policy-261-out marked DSCP 0x2E /DOS

BE Traffic Traffic matched TFT a Traffic matched TFT c

Starent Networks Proprietary and Confidential

21

ITC Dynamic Policy for Differentiated QoS PDSN/FA- Reverse Direction

PCF
Main A10 and Aux A10/Flows established,. 1 TFT created on PDSN
SRID 2; Flow ID 1 FWD (Profile ID 261) TFT a SRID 2; Flow ID 2 REV (Profile ID 261) TFT b

PDSN/FA

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 class261-in (matching TFT b) . Policy-Map policy-261-in 0x2E . Policy-Group Differentiated QoS_policy policy-261-in precedence 3 .

HA

MIP Tunnel Main A10 0xBE BE Traffic Traffic matched TFT b Policy-261-in marked MIP tunnel header 0x2E

)SRID 2; Flow ID 1 FWD (Profile ID 261

PCF marked DSCP 0x2E

Starent Networks Proprietary and Confidential

22

ITC Static Policy for Differentiated QoS HA- Forward Direction

PDSN/FA
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-261-out src_port 2000 Policy-Map policy-261-out (static) 0x2E . Policy-Group Differentiated QoS_policy policy-261-out precedence 1

HA

network

src_port 2000 Server marked DSCP 0x2E

QoS required Service

src_port 2000 match policy-261-out HA marked DSCP 0x2E

0xBE 0xBE
MIP Tunnel

Starent Networks Proprietary and Confidential

23

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 0xBE Policy-Map class-261-in dst_port 2000 policy-261-in (static) 0x2E

network

MIP Tunnel

dst_port 2000 FA marked DSCP 0x2E

Policy-Group Differentiated QoS_policy policy-261-in precedence 3

0xBE

Policy-261-in matched dst_port 2000 HA marked DSCP 0x2E

QoS required Service

Starent Networks Proprietary and Confidential

24

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 Push-to-Talk (PTT) DSCP markings and DOS indication

Starent Networks Proprietary and Confidential

25

Roaming Issues
FlowProfileIDs
Roaming partners must agree upon which FlowProfileIDs will be requested and supported Need to produce starter set (Voice, PTT, etc.) t of agreed upon standard FlowProfileIDs

DSCP markings
Need roaming partners agree upon markings CRX support of markings

Subscriber-based QoS
Prioritization of user profiles (home vs. roamers)

Starent Networks Proprietary and Confidential

26

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.

Starent Networks Proprietary and Confidential

27

Configuration

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.

Starent Networks Proprietary and Confidential

28

ST16/40 Rev-A Related Commands

whats new in the cli?
class-map name tft-voice match-any match dst-port-range 2223 to 3333 show subscribers all verify access technology policy-map name tft-voice class-map tft-voice type dynamic three-gpp2 rev-A profile-id range 0x100 to 0x110 flow-id any access-control allow qos encaps-header dscp-marking 0x2e qos user-datagram dscp-marking 0x2e show subscribers access-flows full - verify details of flow-mapping show subscribers access-flows verify summary of flow-mapping, Qos profile, and flow-based policy info show subscribers full verify subscriber policy show subscribers summary verify summary rev-A flow and filter info

policy-group name policyGroup-1 policy tft-voice precedence 3

show subscribers tft verify details of installed traffic flow template info

Show rp full verify Session Update Send Reason subscriber default authorized-flow-profile-id 256 direction bidirectional policy-group policyGroup-1 direction in policy-group policyGroup-1 direction out monitor protocol A10, A11, User L3, (level 3 with hex and ascii) verify signal and data between the PDSN and PCF, and between the PDSN and mobile show rp full all verify GRE Key associated with A10 instance

logging filter active facility sessmgr level debug verify policy is applied, A10 is added, flow is added, tft is validated, etc.

Show rsvp verify RSVP related statistics/counters

Show subscriber access-tunnels verify A10 connections at sessmgr level

Starent Networks Proprietary and Confidential

29

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
Starent Networks Proprietary and Confidential

30

Class Map Example

class map name vpn-map match any match src-port-range 1716 match dst-port-range 1716 match src-port-range 5001 match dst-port-range 5000 match src-ip-address 216.69.162.0/24 match dst-ip-address 216.69.162.0/24

Starent Networks Proprietary and Confidential

31

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 predefined 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

Starent Networks Proprietary and Confidential

32

Policy Map Example

policy-map name gold-vpn class-map vpn-map type static access-control allow qos traffic-police committed 0 peak 300000 burst-size112500 exceed-action lower-ip-precedence violate-action drop

Starent Networks Proprietary and Confidential

33

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

Starent Networks Proprietary and Confidential

34

Policy Group Example

policy-group name gold policy gold-vpn precedence 2 policy gold-p2p precedence 3

Starent Networks Proprietary and Confidential

35