Roaming Recommendations for EV-DO Rev. A
and Quality of Service (QOS)
CDG Document 161
Version 1.00
14 August 2008
CDMA Development Group
575 Anton Boulevard, Suite 560
Costa Mesa, California 92626
PHONE +1 888 800-CDMA
+1 714 545-5211
FAX +1 714 545-4601
http://www.cdg.org
cdg@cdg.org
Notice
Each CDG member acknowledges that CDG does not review the
disclosures or contributions of any CDG member nor does CDG verify
the status of the ownership of any of the intellectual property rights
associated with any such disclosures or contributions. Accordingly, each
CDG member should consider all disclosures and contributions as being
made solely on an as-is basis. If any CDG member makes any use of
any disclosure or contribution, then such use is at such CDG member's
sole risk. Each CDG member agrees that CDG shall not be liable to any
person or entity (including any CDG member) arising out of any use of
any disclosure or contribution, including any liability arising out of
infringement of intellectual property rights.
Roaming Recommendations for EV-DO Rev. A QOS
1
<page left intentionally blank>
2
3
Ref Doc161, Ver 1.00
14 August 2008
i
Roaming Recommendations for EV-DO Rev. A QOS
Revision History
1
Date
Version
Description
August, 2008
1.00
Initial published document.
2
3
Open issues:
4

5

6
7
Ref Doc161, Ver 1.00
14 August 2008
2
Roaming Recommendations for EV-DO Rev. A QOS
1
<page left intentionally blank>
2
3
Ref Doc161, Ver 1.00
14 August 2008
3
Roaming Recommendations for EV-DO Rev. A QOS
1
Contents
2
1. Introduction ................................................................................................................................ 5
3
1.1 Document Overview ........................................................................................................... 5
4
1.2 Document Organization ..................................................................................................... 5
5
1.3 Audience ............................................................................................................................ 5
6
2. Overview of EV-DO Rev. A ........................................................................................................ 6
7
2.1 General Overview............................................................................................................... 6
8
2.2 Air Interface QOS Overview ............................................................................................... 7
9
2.3 Network QOS ................................................................................................................... 11
10
2.4 Billing and Settlement ...................................................................................................... 12
11
2.5 Roaming Agreements ...................................................................................................... 12
12
3. Recommendations ................................................................................................................... 13
13
3.1 Recommendations for EV-DO Rev. A Roaming .............................................................. 13
14
3.2 Recommended Profile IDs and DSCPs ........................................................................... 15
15
4. Appendix A: Reference Information ....................................................................................... 16
16
Ref Doc161, Ver 1.00
14 August 2008
4
Roaming Recommendations for EV-DO Rev. A QOS
1. Introduction
1
2
1.1 Document Overview
3
10
At the current time, several operators have deployed EV-DO Rev. A technology, which
introduces Quality of Service (QOS) features that allow for new and exciting
applications. Operators are in the nascent stages of deploying these new applications,
and the operator community has emphasized the importance of their subscribers being
able to access these value added services while roaming on other EV-DO Rev. A
networks. This document presents a set of operator deployment recommendations for
EV-DO Rev. A that will ensure an industry roaming solution.
11
1.2 Document Organization
4
5
6
7
8
9
12
13
14
The remaining sections of this document are listed below with descriptions of each
section:
-
15
Overview of EV-DO Rev. A : Provides brief general overview of EV-DO Rev. A
technology followed by more detailed descriptions of the following
16
o
Air Interface QOS
17
o
Network QOS
18
o
Billing and Settlement
19
o
Roaming Agreement Considerations
20
-
Recommendations: Provides a list of deployment network deployment
recommendations for serving operators, home operators, and CRX providers.
-
Annex: Provides general reference information.
21
22
23
24
25
26
27
1.3 Audience
This document is intended for technical CDMA roaming professionals. It assumes that
the reader has familiarity with EV-DO Rev. A concepts and CDMA data roaming
principles. Basic information on packet data roaming can be found in CDG136, the
“1xEV-DO Roaming Guide.”
28
29
Ref Doc161, Ver 1.00
14 August 2008
5
Roaming Recommendations for EV-DO Rev. A QOS
2. Overview of EV-DO Rev. A
1
2
3
4
2.1 General Overview
EV-DO Rev. A is the next version of EV-DO Rev. 0. Before describing EV-DO Rev. A in
more detail, it’s important to note four points:
-
An EV-DO Rev. A device is required to use EV-DO Rev. A services, i.e. EV-DO
Rev. 0 legacy devices can not use EV-DO Rev. A service
7
-
EV-DO Rev. A requires an infrastructure upgrade
8
-
EV-DO Rev. 0 devices will work on networks upgraded to support EV-DO Rev. A
(although the card will not receive EV-DO Rev. A services)
-
EV-DO Rev. A devices will work on EV-DO Rev. 0 networks (although the card
will only receive EV-DO Rev. 0 service)
5
6
9
10
11
12
13
14
15
16
17
18
19
20
21
22
EV-DO Rev. A offers some critical improvements over EV-DO Rev. 0. First, Rev A’s
increased rate quantization on both the forward and reverse links enables more efficient
use of air link resources and, consequently, an overall throughput improvement,
particularly on the reverse link:
Forward Link
Reverse Link
EV-DO Rev. 0
2.4 Mbps
153 kbps
EV-DO Rev. A
3.1 Mbps
1.8 Mbps
Moreover, EV-DO Rev. A includes protocols that decrease connection establishment
time (called enhanced access channel MAC), the ability for more than one mobile to
share the same timeslot (multi-user packets), and the introduction of QoS flags. These
features allow for low bit rate communications that require low latency, e.g. VoIP. QoS
enables packet applications with unprecedented performance in fully loaded commercial
networks. The introduction of QOS provides some new opportunities to operators,
including:
23
-
Opportunity to monetize based on finer market segmentation
24
-
Capability to charge for premium applications, while benefiting from packet
efficiencies
-
Ability to prioritize end users as well as application flows
25
26
Ref Doc161, Ver 1.00
14 August 2008
6
Roaming Recommendations for EV-DO Rev. A QOS
1
2
3
4
At this time, several operators have deployed EV-DO Rev. A services, and more have
committed to launching the service. As mentioned, the main driver behind these
deployments is a desire on the part of the operators to offer delay sensitive applications,
including such applications as:
5
-
VoIP
6
-
Video Telephony
7
-
Instant Multi-Media (IMM)
8
-
Gaming
9
-
Push to Chat
10
2.2 Air Interface QOS Overview
11
2.2.1 QOS Concepts
12
13
14
15
16
17
18
This section describes an industry solution for EV-DO rev. A air interface QOS. The
objective is to ensure that roaming EV-DO rev. A capable ATs are able to acquire the air
interface QOS needed to support important data applications.
QOS is concerned with ensuring that packets associated with performance sensitive
applications are prioritized above less sensitive applications. Four main criteria are
generally used to define the behavior of QoS applications:
-
Delay (Latency): Maximum allowable delay between sending the packet from one
end point and reception of that packet at the far end point.
-
Jitter: The variance of inter-arrival delay from one packet to the next packet
within the same IP flow/stream.
-
Reliability (PER): The number of packets that are in error out of the total number
of packets transmitted.
-
Target Throughput: The minimum required throughput for a flow.
19
20
21
22
23
24
25
26
27
For EV-DO Rev. A, a Profile ID is a logical value specifying the air interface parameters
needed to provide the required QOS characteristics. These values are defined in
3GPP2 C.R1001 (TSB-58). The following logical numbers can be used for Profile IDs:
28
-
0 (default) is defined as Best Effort (BE)
29
-
0 – 16,383: standard FlowProfileIDs
30
-
16,384 – 32,767: proprietary FlowProfileIDs
31
32
In addition, there are parameters that can affect the level of service for Best Effort (BE)
flows. These include:
Ref Doc161, Ver 1.00
14 August 2008
7
Roaming Recommendations for EV-DO Rev. A QOS
1
-
BE Inter-user Priority, which indicates the relative priority of BE flows among
subscribers
-
Maximum Authorized Aggregate Bandwidth, which indicates the amount of
bandwidth a subscriber can receive for best effort services
2
3
4
5
2.2.2 QOS Set Up Walk Through
6
The follow is a description of how EV-DO Rev. A QOS is set up.
7
2.2.2.1 AN Receives Subscriber QOS Profile
8
9
-
Subscriber’s HAAA provides it to the PDSN after packet data authentication
10
-
PDSN stores it and forwards relevant portion to the AN
11
-
It allows the AN to authorize QoS requests received from the AT
12
2.2.2.2 AT Requests Profile IDs
13
14
15
16
17
-
Applications request required Profile IDs via an API to the handset. The
application can request one or more acceptable Profile IDs. The AT then
requests the network for these Profile IDs. Note that the AT doesn’t need to
“support” a particular Profile ID, unlike the network.
Ref Doc161, Ver 1.00
14 August 2008
8
Roaming Recommendations for EV-DO Rev. A QOS
1
-
Reservation Labels are used to identify IP flows
2
-
AT selects Reservation Labels for each IP flow (forward and reverse flows)
3
-
AT selects one or more desired Flow Profile IDs for each flow
4
-
AT uses GAUP to send these reservation labels and Flow Profile IDs to AN
5
2.2.2.3 AN authorizes and grants a Flow Profile ID for each IP flow
6
7
-
AN uses subscriber QoS profile info to authorize Flow Profile ID requests
8
-
AN determines what Flow Profile ID it will grant for each request
9
-
AN uses GAUP to provide these granted Flow Profile IDs to AT
10
2.2.2.4 4AN sets up RLP flows
11
-
AN uses GAUP and initiates setup of RLP flows based pre-configured RLP flow
to QoS Flow Profile ID configuration, activation, and mapping
14
-
RLP flow parameters are negotiated between AN and AT
15
-
Reservation labels are used to map one or more IP flows to each RLP flow
12
13
Ref Doc161, Ver 1.00
14 August 2008
9
Roaming Recommendations for EV-DO Rev. A QOS
1
2.2.2.5 AN sets up RTCMAC flows
2
3
-
AN uses GAUP and initiates setup of RTCMAC flows based pre-configured
RTCMAC to RLP flow associations, configuration parameters, and activation
-
Stream field associates the RTCMAC flow with the application bound to that
stream value during session negotiation
-
Substream field is the RLP Flow NN to be bound to the RTCMAC flow
4
5
6
7
8
2.2.2.6 AT sets up Packet Filters at the PDSN
9
10
-
Packet Filters are used to convey:
11
o
A10 <-> IP flow mapping
12
o
IP layer QoS parameters
13
o
Packets treatment, including DSCP markings
14
-
Multiple Filters may be included in a single TFT IE
15
-
Packet Filters may include:
Ref Doc161, Ver 1.00
14 August 2008
10
Roaming Recommendations for EV-DO Rev. A QOS
1
o
Reservation Label
2
o
Source or Dest IP Address
3
o
Source or Dest Port
4
o
Protocol /Next header
5
o
IPSec SPI
6
o
TOS / Traffic Class
7
o
Type 2 Routing Header
8
o
Home Address Option
9
2.3 Network QOS
15
In order to support applications which require air interface QOS, it is also important to
consider network QOS to ensure that network transport is not the “bottle neck.”
Therefore, it’s important that an industry solution also addresses network transport.
Note that comprehensive solutions for network transport are well established and can be
leveraged by identifying network QOS parameters that are commensurate with air
interface QOS characteristics.
16
2.3.1 Differentiated Services
10
11
12
13
14
17
18
19
20
21
Differentiated Services or DiffServ is a system providing a mechanism for classifying
network traffic and providing Quality of Service (QoS) guarantees on modern IP
networks. DiffServ is used to provide low-latency, guaranteed services to network traffic
such as voice or video while providing simple best-effort traffic guarantees to non-critical
services such as web traffic or file transfers.
24
DiffServ works by classifying individual IP packets with a Differentiated Services Code
Points (DSCPs) which are contained in a field in the IP header. Routers can then apply
differentiated treatment to IP packets accordingly on a “per hop basis” (PHB).
25
The main classes of DSCPs:
22
23
Type
Description
Expedited Forwarding (EF)
Highest priority for applications that require low delay, low
loss and low jitter.
Assured Forwarding (AF)
Assurance of delivery as long as the traffic does not
exceed some subscribed rate. There are 12 classes of
Assured Forwarding that determine which packets are
dropped if insufficient bandwidth is present.
Ref Doc161, Ver 1.00
14 August 2008
11
Roaming Recommendations for EV-DO Rev. A QOS
4
An industry QOS solution requires networks apply QOS (DSCPs) to packets that are
commensurate with the level of QOS on the air interface. Therefore, it’s understood that
PDSNs should apply appropriate DSCPs to each IP flow based the air interface QOS it
is receiving.
5
2.3.2 Operator and CRX Network Considerations
1
2
3
12
In order for DiffServ to function correctly, once DSCPs have been applied to IP packets,
it requires that individual routers treat packets accordingly. This includes the routers in
both the home and serving operators’ networks, as well as the CRX(s)’ networks. At
current time, most networks do not currently support QOS on routers. It can be argued
that networks could be overbuilt such that QOS observation in routers is not necessary.
However, it’s considered important that proper QOS markings be applied to packets to
ensure a future solution in cases when bandwidth isn’t sufficiently overbuilt.
13
2.3.3 Mobile IP Considerations
6
7
8
9
10
11
17
Mobile IP is the preferred architecture for data roaming. As such, it’s important to note
that network QOS is preserved for Mobile IP tunnels. It’s required that the DSCP of a
packet entering a Mobile IP tunnel be copied to the outer IP wrapper to ensure
consistent treatment by networks.
18
2.4 Billing and Settlement
14
15
16
19
20
21
22
23
24
25
26
27
28
29
It’s critical that operators have the ability to charge for providing each other’s customers
with premium QOS services. In addition, each operator requires the ability to charge
their own customers for premium services.
This can be accomplished through IP flow based accounting. IP flow based accounting
involves the creation of accounting streams for individual IP flows, which indicate the
amount of data consumed by a subscriber using specific QOS parameters. Through this
mechanism, operators can use the UDRs generated by IP flow based accounting to
achieve differentiated billing and settlement for premium services.
Individual accounting streams are identified by the attribute FLOW_ID in UDRs. Also
included in the UDR is the QOS_Attribute_Set, which describes the QOS received on
the particular IP flow, e.g. in “non-verbose” form, this includes the ServiceProfileID.
33
It’s important to note that IP Flow based accounting will significantly increase the amount
of accounting records created for subscribers using QOS. For this reason, a 3GPP2
attribute (Accounting-Mode 26/198) has been introduced to control whether IP flow
based accounting is generated on an individual subscriber basis.
34
2.5 Roaming Agreements
30
31
32
35
36
37
38
Currently, the CDG Roaming Agreement document (#44) includes provisions for settling
for packet data services by kilobyte usage. However, operators will need to expand
roaming agreements to account for roaming partners providing premium services to
inbound roaming subscribers.
Ref Doc161, Ver 1.00
14 August 2008
12
Roaming Recommendations for EV-DO Rev. A QOS
3. Recommendations
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
3.1 Recommendations for EV-DO Rev. A Roaming
3.1.1 For EV-DO Rev. A roaming, the serving operator, the home operator, and the CRX
providers shall observe data roaming requirements in other relevant CDG reference
documents, e.g. CDG79, CDG136, CDG147, CDG116, and CDG94
3.1.2 The serving operator network shall provide the agreed upon profile IDs and to
inbound EV-DO Rev. A roamers (see section 3.2)
3.1.3 The serving operator’s PDSNs shall apply the DSCP to IP packets associated with
the IP flow’s profile ID (see section 3.2)
3.1.4 The serving operator network shall support network QOS for the transport network
that provides the “expected subscriber user experience” for a particular profile ID and
DSCP. This can be achieved by observing DSCPs or by providing sufficient bandwidth.
3.1.5 The CRX network shall support network QOS for the transport network that
provides the “expected subscriber user experience” for a particular profile ID and DSCP.
This can be achieved by observing DSCPs or by providing sufficient bandwidth.
3.1.6 The home operator shall provide the following VSAs in the access-accept
message for EV-DO Rev. A subscribers
18
-
Max. authorized aggregate bandwidth for BE traffic
19
-
Authorized Flow Profile IDs
20
-
Max. per flow priority
21
-
Service Option profile
22
-
Inter-user priority for BE traffic
23
-
Allowed # of persistent TFTs
24
-
Allowed differentiated services markings
25
26
3.1.7 The home operator should include all of the profile IDs in section 3.2 in the
“Authorized Flow Profile IDs” VSA
27
28
Ref Doc161, Ver 1.00
14 August 2008
13
Roaming Recommendations for EV-DO Rev. A QOS
1
2
3.1.8 The home operator should include the DSCPs in section 3.2 in the “Allowed
differentiated services markings” VSA in the access-accept message
7
3.1.9 The serving operator should treat the best effort (BE) traffic of inbound subscribers
according to the serving operator’s preference. The serving operator may overwrite the
“Inter-user priority for BE traffic” and “Maximum authorized aggregate bandwidth for BE
traffic” VSAs in order to accomplish this. The CRX may overwrite these VSAs for the
serving operator.
8
3.1.10 The serving operator shall support IP Flow Based Accounting
3
4
5
6
9
10
3.1.11 The serving operator shall include the non-verbose QOS_Attribute_Set in the
accounting UDR to ensure the profile ID is provided.
12
3.1.12 The home operator should indicate to use IP Flow Based Accounting in the
“Accounting Mode” VSA in the accept-accept message for EV-DO Rev. A subscribers
13
3.1.13 The CRX shall process IP Flow Accounting records for settlement
11
14
Ref Doc161, Ver 1.00
14 August 2008
14
Roaming Recommendations for EV-DO Rev. A QOS
1
2
3.2 Recommended Profile IDs and DSCPs
DiffServ
PHB
DSCP
Signaling
EF
EF
CS5
101110
101110
101000
VOIP or PSVT RTP Audio
PSVT RTP Audio
SIP
RTCP Video
RTCP Audio
Video
Audio/Video
AF41
AF31
100010
011010
Signaling
AF31
011010
PSVT RTP Video
TV RTP Audio/Video < 32kbps
TV RTP Audio/Video < 64kbps
TV RTP Audio/Video < 96kbps
TV RTP Audio/Video < 128kbps
TV RTP Audio/Video >= 128kbps
Fwd RTCP Audio/Video < 32kbps
Fwd RTCP Audio/Video < 64kbps
Fwd RTCP Audio/Video < 96kbps
Fwd RTCP Audio/Video < 128kbps
Fwd RTCP Audio/Video >=
128kbps
3GPP2 QoS Information
Media
Traffic Class
Type
Conversational Audio
Streaming
AF31
011010
Rev RTCP Audio/Video
000000
100000
RTSP
Gaming 16K
PtX RTP Audio
SIP
RTCP Audio
HTTP, FTP, Telnet
Interactive
Gaming
BE
CS4
Push-to-X
Audio
Signaling
EF
CS5
101110
101000
Background
Best Effort
DF/BE
000000
3
Service Example
ProfileID
256
257
1280
1280
1280
773, 771,
769
1
2
3
4
29
1
2
3
4
29
1281
NA
1536
256, 257,
280
1283
1283
NA
Table 3-1: Recommended Profile Ids and DSCPS
Ref Doc161, Ver 1.00
14 August 2008
15
Roaming Recommendations for EV-DO Rev. A QOS
4. Appendix A: Reference Information
1
Table 4-1: Relevant Industry Organizations
2
Organization
Description
3GPP2
3G Partnership Project 2
www.3gpp2.org
CDG
CDMA Development Group
www.cdg.org
CDG IRT
CDG International Roaming Team
www.cdg.org/cdg/teams/international.asp
IETF
Internet Engineering Task Force
www.ietf.org
ICANN
Internet Corporation for Assigned Names and Numbers
www.icann.org
Assigns globally unique domain names (a.k.a. “realms”)
TIA
Telecommunications Industry Association
http://www.tiaonline.org/
Table 4-2: Relevant CDG Standards
3
4
5
6
All CDG reference documents listed below are available for download in the Members
Only: Reference Documents section of the CDG website at
www.cdg.org/members_only/ref_doc.asp
Ref
Standard
Description
1.
CDG #44
CDMA International Roaming Agreement
(Version 2.5 or later required for packet data support)
2.
CDG #79
Wireless Data Roaming Network Requirements and
Implementation
(Version 1.1 or later required for 1xRTT/EV-DO)
3.
CDG #94
CDMA Packet Data Roaming eXchange Guidelines
4.
CDG #116
Packet Data Billing Requirements and Implementation
5.
CDG #118
International Voice Roaming Checklist
6.
CDG #121
Packet Data Roaming End-to-End Test Plan
7.
CDG #123
Operator Requirements and Capabilities Form for Packet Data
Roaming
Ref Doc161, Ver 1.00
14 August 2008
16
Roaming Recommendations for EV-DO Rev. A QOS
Ref
Standard
Description
8.
CDG #124
Packet Data Technical Data Sheet
Table 4-3: Relevant 3GPP2 Cross Referenced TIA/EIA/IS Standards
1
2
3
4
All TIA/EIA/IS standards listed below are available for download in the 3GPP2
Specifications: Cross-Reference to Published Standards section of the 3GPP2 website
at www.3gpp2.com/Public_html/specs.
Ref
Standard
Description
1.
P.R0001 v1.0
(TSB-115)
Wireless IP Architecture Based on IETF Protocols
2.
C.S0016-B v1.0
(TIA-683-C)
Over-the-Air Service Provisioning of Mobile Station in Spread
Spectrum Systems
3.
X.S0011-00z-C
v1.0 (TIA-835.00z)
cdma2000 Wireless IP Network Standard
z = subdocument number:
1 – Overview
2 – Simple IP and Mobile IP Access Services
3 – Packet Data Mobility and Resource Management
4 – Quality of Service and Header Reduction
5 – Accounting Services and 3GPP2 RADIUS VSAs
see also: Table 4-4: IS-835 Evolution
4.
C.S0024-0 v4.0
(IS-856-2)
cdma2000 High Rate Packet Data Air Interface Specification
5.
A.S0008-0 v3.0
(TIA-878-1 pub)
Interoperability Specification (IOS) for High Rate Packet Data
(HRPD) Access Network Interfaces
8
Note that the TIA-835 set of documents are the primary standards that define the packet
data network architecture. While version C is currently shown in Table 4-3: Relevant
3GPP2 Cross Referenced TIA/EIA/IS Standards, a version D is in progress. The major
improvements introduced by each version are shown below:
9
Table 4-4: IS-835 Evolution
5
6
7
IS-835 Version
Ref Doc161, Ver 1.00
Improvements
14 August 2008
17
Roaming Recommendations for EV-DO Rev. A QOS
1
2
3
TIA/IS-835-A
(May 2001)
 Simple IPv4 (i.e. IPv4 over PPP)
o PAP, CHAP, or null authentication
o IP address assignment via IPCP
 Mobile IPv4
o Static or dynamic home address
o Static HA assignment
o NAI extension & FA challenge/response
o Security association between PDSN/FA and HA
 VJ header compression
 PPP payload compression
 Airtime and/or volume based accounting
IS-835-B
(Sept. 2002)










Multiple service instances introduced
DiffServ QoS
Simple IPv6 (IPv6 over PPP)
“Always on” support for Simple IP (via LCP echo)
Dynamic HA allocation using RADIUS
IP, ROHC, and ROHC-over-PPP header compression
DNS address auto-configuration via IPCP
Dynamic DNS update by network entities assigning the address
Fast PDSN-PDSN handoff (tunnel PPP between PDSNs)
Remote address based accounting
TIA-835-C
(Aug. 2003)







Multiple service instance support
0-byte header reduction schemes and enhanced CRTP
Differential flow treatment (QoS, compression)
“Always on” enhancement (Max PPP Inactivity Timer)
PDSN/HA resource management
Prepaid data
IP Reachability (capability indication from HA to HAAA)
IS-835-D
(TBD)
 Mobile IPv6
 IPv4 and IPv6 interworking
 QoS improvements:
o End-to-end QoS
o QoS subBLOB
o Service tiers within AAA system
 Push support for network initiated services
 DHCP support
 Enhanced security
 Flow control for PDSN-to-RAN traffic
 Flow control and QoS/content/flow based accounting
 Roaming enhancements
Table 4-5: Relevant IETF Standards/Specifications
All IETF standards listed below are available for download in the Internet
RFC/STD/FYI/BCP Archives at www.faqs.org/rfcs.
Ref Doc161, Ver 1.00
14 August 2008
18
Roaming Recommendations for EV-DO Rev. A QOS
Ref
Standard
Description
1.
RFC 1144
Compressing TCP/IP headers for low-speed serial links
(also known as Van Jacobson header compression)
2.
RFC 1332
The PPP Internet Protocol Control Protocol (IPCP)
3.
RFC 1334
PPP Authentication Protocols (PAP & CHAP)
4.
RFC 1661
The Point-to-Point Protocol (PPP)
5.
RFC 1662
PPP in HDLC-like Framing
6.
RFC 1962
The PPP Compression Control Protocol (CCP)
7.
RFC 1994
PPP Challenge Handshake Authentication Protocol (CHAP)
8.
RFC 2002
IP Mobility Support (Mobile IP)
9.
RFC 2003
IP Encapsulation within IP
10.
RFC 2004
Minimal Encapsulation within IP
11.
RFC 2205
Resource Reservation Protocol (RSVP) v1 Functional Spec
12.
RFC 2402
IP Authentication Header
13.
RFC 2406
IP Encapsulating Security Payload
14.
RFC 2409
Internet Key Exchange (IKE)
15.
RFC 2460
An Architecture for Differentiated Services
16.
RFC 2486
Network Access Identifier (NAI)
17.
RFC 2507
IP Header Compression
18.
RFC 2637
Point-to-Point Tunneling Protocol (PPTP)
19.
RFC 2661
Layer Two Tunneling Protocol (L2TP)
20.
RFC 2784
Generic Routing Encapsulation (GRE)
21.
RFC 2794
Mobile IP Network Access Identifier Extension for Ipv4
22.
RFC 2865
Remote Authentication Dial In User Service (RADIUS)
23.
RFC 3012
Mobile IPv4 Challenge/Response Extensions
24.
RFC 3024
Reverse Tunneling for Mobile IP
25.
RFC 3095
Robust Header Compression (ROHC): Framework and four
profiles: RTP, UDP, ESP, and uncompressed
26.
RFC 3162
RADIUS and IPv6
27.
RFC 3241
Robust Header Compression (ROHC) over PPP
28.
RFC 3545
Enhanced Compressed RTP (CRTP) for Links with High Delay,
Packet Loss and Reordering
Ref Doc161, Ver 1.00
14 August 2008
19
Roaming Recommendations for EV-DO Rev. A QOS
Table 4-6: CDMA Roaming eXchange (CRX) Providers
1
Company
Details
Aicent
www.aicent.net
Syniverse
www.verisign.com
Verisign
www.syniverse.com
Table 4-7: Acronyms and Abbreviations
2
Acronym /
Abbreviation
Description
1xEV-DO
CDMA2000 Evolution, Data Only. Also known as EV-DO, DO, or IS-856.
CDMA channel is dedicated to data services with data speeds up to 2.4Mbps
(400-600kbps average)
3DES
Triple (3x) Data Encryption Standard. Also known as DESede. Encryption
algorithm uses a 168-bit key (i.e. three 56-bit DES keys). Used during IKE
AAA
Authentication, Authorization, and Accounting server. Similar to HLR/VLR
servers in a the mobile voice network. Communicates using RADIUS.
AN
Access Network. Data network providing network access to the MS/AT
AN-AAA
Access Network AAA
AT
Access Terminal. EV-DO nomenclature for the Mobile Station (MS). This
document uses “MS/AT” to refer to packet data capable mobile devices
BAAA
Broker AAA
CHAP
Challenge Handshake Authentication Procotol. 3-way handshake protocol
used during link establishment and periodically anytime thereafter to
authenticate a user. Uses MD5
CoA
Care-of Address. Used in Mobile IP architecture. Temporary address
assigned to a Mobile IP enabled device in foreign domain. Messages
addressed to the device are routed by the HA to the CoA
CRTP
Enhanced Compressed RTP
CRX
CDMA2000 Roaming eXchange. 3rd party provider that facilitates CDMA
packet data roaming between carriers by providing interconnection, AAA,
billing, and settlement services
DES
Data Encryption Standard. Encryption algorithm that uses a 52-bit key.
DH1
Diffie-Helman group 1 key exchange. Cryptographic protocol that uses a 768
bit modulus to allow two parties to establish a shared secret key over an
insecure network. Used during IKE
DH2
Diffie-Helman group 2 key exchange. Cryptographic protocol that uses a 1024
bit modulus to allow two parties to establish a shared secret key over an
insecure network. Used during IKE
Ref Doc161, Ver 1.00
14 August 2008
20
Roaming Recommendations for EV-DO Rev. A QOS
Acronym /
Abbreviation
Description
DNS
Domain Name Server. Provides translation between domain names and IP
addresses
ESP
Encapsulating Security Payload. Used by IPSec to provide secure packet
flows with authentication, data confidentiality, and message integrity
EV-DO
See 1xEV-DO
FA
Foreign Agent. Used in Mobile IP architecture
FQDN
Fully Qualified Domain Name
GRE
Generic Routing Encapsulation. Transport layer encapsulation used by PPTP
GRX
GPRS Roaming eXchange
HA
Home Agent. Used in Mobile IP architecture
HAAA
Home AAA
HDLC
High-level Data Link Control
HDR
High Data Rate. Term has been replaced by HRPD
HMAC-MD5
keyed-Hash Message Authentication Code using MD5. Used by IPSec ESP
HMAC-SHA-1
keyed-Hash Message Authentication Code using SHA-1. Used by IPSec ESP
HRPD
High Rate Packet Data. Also known as HDR and 1xEV-DO
IKE
Internet Key Exchange. Protocol used to setup an IPSec security association.
Used with IPSec to authenticate each peer, negotiated security policy, and
handle exchange of session keys. Formerly known as ISAKMP
IPCP
Internet Protocol Control Protocol
IPSec
IP Security Protocol. Uses AH, ESP, and IKE to provide secure connections
over insecure IP networks
IPSec SA
IPSec Security Association. Created during IPSec connection establishment
to define the rules of that specific connection
IS-856
1xEV-DO air interface
IS-2000
1xRTT air interface
ISAKMP
Internet Security Association and Key Management Protocol. Term replaced
by IKE
L2TP
Layer 2 Tunneling Protocol
LAC
L2TP Access Concentrator
LCP
Link Control Protocol
LNS
L2TP Network Server
Ref Doc161, Ver 1.00
14 August 2008
21
Roaming Recommendations for EV-DO Rev. A QOS
Acronym /
Abbreviation
Description
MD5
Message-Digest algorithm 5. Hash function used by authentication protocols
such as CHAP
MIP
Mobile IP
MN
Mobile Node. Mobile IP term for a node that can change its point of
attachment to the Internet while maintaining the same IP address (i.e. an
MS/AT that supports Mobile IP)
MS
Mobile Station. Referred to as Access Terminal (AT) in packet data. This
document uses “MS/AT” to refer to packet data capable mobile devices
MS/AT
Mobile Station / Access Terminal. Used in this document to refer to packet
data capable mobile devices
MSID
Mobile Station Identifier. May be IMSI, MIN, or IRM.
NAI
Network Access Identifier. Constructed from mobile’s username (MSID) and
provider’s domain name (realm). NAIs should be fully qualified network names
of the format: <MSID>@<realm>
NAS
Network Access Server. An access gateway that authenticates users and
authorizes access to an internal network or the Internet. In the packet data
architecture, the PDSN acts as the NAS
NAT
Network Address Translation
NCP
Network Control Protocol
NID
Network ID
PAAA
Proxy AAA
PAP
Password Authentication Protocol. Simple authentication protocol that is
considered insecure since it transmits unencrypted ASCII passwords
PCF
Packet Control Function
PDSN
Packet Data Serving Node
P-P
PDSN-PDSN interface
PPP
Point-to-Point Protocol
PPTP
Point-to-Point Tunneling Protocol
QoS
Quality of Service
RADIUS
Remote Access Dial In User Service
RLP
Radio Link Protocol
ROHC
Robust Header Compression
RN
Radio Network
R-P
RN-PDSN interface
Ref Doc161, Ver 1.00
14 August 2008
22
Roaming Recommendations for EV-DO Rev. A QOS
Acronym /
Abbreviation
Description
RTP
Real Time Protocol. A thin protocol that adds timing and sequencing data to
support real time transport of audio and video data over packet networks
SHA-1
Secure Hash Algorithm 1
SIP
Simple IP
SO
Service Option
SO33
Service Option 33. CDMA service option for 1xRTT
SO59
Service Option 59. CDMA service option for 1xEV-DO
SID
System ID
TCP
Transmission Control Protocol
UDP
User Datagram Protocol
VAAA
Visited AAA
VJHC
Van Jacobson Header Compression
VPN
Virtual Private Network
1
2
3
Ref Doc161, Ver 1.00
14 August 2008
23