COPYRIGHT

3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.

3GPP2 X.S0011-001-D

Version: 2.0

Version Date: November 2008

cdma2000 Wireless IP Network Standard:

Introduction

X.S0011-001-D v1v2.0

i

Content 1

1 INTRODUCTION ................................................................................................................................. 3 2

2 GLOSSARY AND DEFINITION ........................................................................................................ 5 3

2.1 ACRONYMS........................................................................................................................................... 5 4

2.2 DEFINITIONS ........................................................................................................................................ 7 5

3 REFERENCES .................................................................................................................................... 15 6

3.1 NORMATIVE REFERENCES................................................................................................................. 15 7 3.1.1 IETF................................................................................................................................................. 15 8

3.1.2 3GPP2 AND TIA............................................................................................................................... 19 9

3.1.3 ITU-T............................................................................................................................................... 19 10

3.2 INFORMATIVE REFERENCES.............................................................................................................. 20 11 3.2.1 3GPP2 AND TIA............................................................................................................................... 20 12

4 PROTOCOL REFERENCE MODELS............................................................................................. 21 13

4.1 NETWORK REFERENCE MODELS ...................................................................................................... 21 14

4.2 SIMPLE IP........................................................................................................................................... 22 15

4.3 MIP4 .................................................................................................................................................. 23 16

4.4 MIP6 .................................................................................................................................................. 27 17

4.5 RADIUS............................................................................................................................................. 29 18

19

X.S0011-001-D v1v2.0

ii

List of Figures 1

Figure 1 - Reference Model for Simple IP Access with Fast Handoff ..................................................21 2

Figure 2 - Reference Model for MIP Access with Fast Handoff ...........................................................22 3

Figure 3 - Protocol Reference Model for Simple IP Access.................................................................23 4

Figure 4 - Protocol Reference Model for Simple IP Access During Fast Handoff ...............................23 5

Figure 5 - Protocol Reference Model for MIP4 Control and IKE ..........................................................24 6

Figure 6 - Protocol Reference Model for MIP4 User Data ...................................................................24 7

Figure 7 - Protocol Reference Model for MIP4 Control and IKE During Fast Handoff.........................25 8

Figure 8 - Protocol Reference Model for MIP4 User Data During Fast Handoff..................................25 9

Figure 9 - Protocol Reference Model for Signaling for Fast Handoff ...................................................26 10

Figure 10 - Protocol Reference Model for User Data for Fast Handoff................................................26 11

Figure 11- Protocol Reference Model for MIP6 Control .......................................................................27 12

Figure 12- Protocol Reference Model for MIP6 User Data with Bi-directional Tunneling....................27 13

Figure 13- Protocol Reference Model for MIP6 User Data in RO mode..............................................28 14

Figure 14- Protocol Reference Model for MIP6 Control during Fast Handoff ......................................28 15

Figure 15- Protocol Reference Model for MIP6 User Data with Bi-directional Tunneling during Fast 16 Handoff ..........................................................................................................................................29 17

Figure 16- Protocol Reference Model for MIP6 User Data in RO mode during Fast Handoff .............29 18

Figure 17 - RADIUS Protocol Reference Model...................................................................................30 19

X.S0011-001-D v1v2.0

iii

List of Tables 1

Table 1- Revision History .......................................................................................................................2 2

X.S0011-001-D v1v2.0

1

Revision History: 1

Revision Date Comments

December 2000

Initial Publication

Revision A May 2001 Added specification or clarification for the following items: • New mechanism for PDSN/HA pre-shared secret distribution for

IKE • Security status is replaced by IKE Pre-shared Secret Request

attribute • New counters G15 and G16 for MIP signaling • Clarifications with respect to counters G1 and G2 • A new indicator in RADIUS stop message to indicate session

still in progress (to avoid release of the IP address) • Removal of RADIUS accounting fields H1, I2, and I3 • New accounting session to be created when F1, F2 accounting

fields vary • Non-zero and zero IP address in IP Configuration option in IPCP

is treated as Simple IP by PDSN. MIP is supported with null IP address configuration option (i.e., not included).

• The Active Time attribute format changed from standard RADIUS encoding to 3GPP2 specific encoding.

Revision B September 2002

This document has been revised to support the following features: • Simultaneous multiple service instances concept introduced. • RTP/UDP/IP Header Reduction Schemes • Differentiated Services QoS Policy • Fast handoff for data call (i.e., tunneled PPP between PDSNs) • Dynamic Home Agent allocation with RADIUS • Optional support for DNS server address auto configuration in

MS • Always On support • IP Reachability Service with dynamic DNS update • Simple IPv6 • Remote address based accounting

Revision C August 2003 • New format: the document is split into 6 chapters identified by YYYYY.xxx-C, where YYYY is the document number and xxx is the chapter number.

• Multiple Service Instance support • LLAROHC Header Compression and LLA Header Removal • Enhanced CRTP as an additional compression scheme • Dynamic flow mapping/treatment • PrePaid Packet Data service (phase 1) • PDSN/HA Resource management • Accounting support for 1xEVDV • Packet Data Inactivity Timer • IKE/IPsec clarifications • IP Reachability enhancements • Enhancements to Always On • Enhancements to Simple IPv6

Revision B Version 2.0

September 2004

This is an addendum to correct errors and omissions in the Revision B Version 1.0 of this document.

X.S0011-001-D v1v2.0

2

Revision D February 2006

• IPv6 Mobility • Support for end-to-end QoS (MS-PDSN QoS signaling) • Hot-lining • MS-PDSN Version/Capabilities Indication • Short Data Burst Indication Support • RAN-PDSN Flow control Support • DHCPv4 and DHCPv6 • IP Reachability for MIPv6 • Auxiliary Service Connection SO67 support.

Revision D

Version 2.0

April October 2008

• This is an addendum to correct errors in the Revision D Version 1.0 of this document.

Table 1- Revision History1

X.S0011-001-D v1v2.0

3

1 Introduction 1

This document defines requirements for support of wireless packet data networking capability on 2 a third generation wireless system based on cdma2000®1. This document supports the services 3 and architecture in [1]. 4

This document defines the two methods for accessing public networks (Internet) and private 5 networks (intranets): Simple IP and MIP. It describes the required Quality of Service, Security, 6 Mobility Management, and Accounting capabilities needed to support both methods. IETF 7 protocols are widely employed whenever possible to minimize the number of new protocols 8 required and to maximize the utilization of well accepted standards. 9

This document is organized into a series of related chapters, some of which address capabilities 10 common to both IP access service types: MIP and Simple IP, and others may describe 11 capabilities applicable to a specific IP access service. The chapters included in this series are: 12

Chapter 1 cdma2000 Wireless IP Network Standard: Introduction. 13

Chapter 2 cdma2000 Wireless IP Network Standard: Simple IP and MIP Access Services. 14

Chapter 3 cdma2000 Wireless IP Network Standard: Packet Data Mobility and Resource 15 Management. 16

Chapter 4 cdma2000 Wireless IP Network Standard: Quality of Service and Header 17 Reduction. 18

Chapter 5 cdma2000 Wireless IP Network Standard: Accounting Services and 3GPP2 19 RADIUS VSAs. 20

Chapter 6 cdma2000 Wireless IP Network Standard: PrePaid Packet Data Service. 21

In this set of documents we refer to other documents in the set strictly by their chapter numbers 22 as in [Chapter 1]. 23

Chapter 1 This chapter presents an overview of the document content, and contains the 24 complete glossary and definitions applicable to all the chapters. It describes the 25 network and protocol reference models for the wireless IP Network entities: 26 PDSN, HA and RADIUS server. 27

Chapter 2 This chapter describes the basic IP access services: Simple IPv4/IPv6, MIP6 and 28 MIP4 with Dynamic Home Agent, and Home IP address Assignment. It also 29 addresses the security requirements between the Wireless IP Network nodes: 30 PDSN, HA and RADIUS servers. The chapter includes other capabilities such as 31 Always On, multiple simultaneous MIP4/IPv6 and Simple IPv4/IPv6 packet data 32 session, IP Reachability Service, DHCP support and Hot-Lining. 33

Chapter 3 This chapter describes packet data intra-PDSN, inter-PDSN handoff as well as 34 inter-PDSN fast handoff capabilities and the RAN requirements. The chapter 35 includes mechanisms for PDSN and HA resource management and provisioning 36 of dormancy timers in the RAN. This chapter also includes support for RAN-37 PDSN Flow Control and Short Data Burst indication. 38

1 cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States.

X.S0011-001-D v1v2.0

4

Chapter 4 This chapter describes user Differentiated services capability, multiple service 1 connections, flow mapping and treatment, and MS-PDSN QoS signaling. The 2 chapter also includes a detailed description of Link Layer Assisted Robust 3 Header compression and Header Removal treatment to support Voice over IP 4 Service over an auxiliary service connection. In addition, this chapter adds 5 Auxiliary Service Connection SO67 support that allows for the efficient transport 6 of IP packets from the PDSN to the RAN without HDLC-like framing and PPP 7 encapsulation. 8

Chapter 5 This chapter describes source IP address and remote IP address based 9 accounting and detailed procedures required for this series of standards. It also 10 includes a description of the 3GPP2 RADIUS VSAs required to support this 11 series of standards. 12

Chapter 6 This chapter describes the PrePaid Packet Data Service for the Wireless IP 13 Network users and includes the PrePaid service architecture, the detailed 14 procedures and the requirements on the Wireless IP Network elements. 15

16 “Shall” and “shall not” identify requirements to be followed strictly to conform to this document 17 and from which no deviation is permitted. “Should” and “should not” indicate that one of several 18 possibilities is recommended as particularly suitable, without mentioning or excluding others, that 19 a certain course of action is preferred but not necessarily required, or that (in the negative form) a 20 certain possibility or course of action is discouraged but not prohibited. “May” and “need not” 21 indicate a course of action permissible within the limits of the document. “Can” and “cannot” are 22 used for statements of possibility and capability, whether material, physical or causal. 23 .24

X.S0011-001-D v1v2.0

5

2 Glossary and Definition 1

2.1 Acronyms 2

A10 RAN-PDSN Interface 3 AAA Authentication, Authorization, and Accounting 4 ACCM Asynchronous Control Character Map 5 AH Authentication Header 6 AVP Attribute Value Pair 7 BA Binding Acknowledgement 8 BU Binding Update 9 BCE Binding Cache Entry 10 BCMCS Broadcast and Multicast Service 11 BS Base Station 12 CA Certificate Authority 13 CCP Compression Control Protocol 14 CHAP Challenge Handshake Authentication Protocol 15 CN Correspondent Node 16 CoA Care-of Address 17 COA Change of Authorization 18 CRL Certificate Revocation List 19 CSRC Contributing Source 20 CVSE Critical Vendor/Organization Specific Extension 21 DAD Duplicate Address Detection 22 D-H Diffie-Hellman 23 DHCP Dynamic Host Configuration Protocol 24 DN Distinguished Name 25 DNS Domain Name System 26 DSA Digital Signature Algorithm 27 DSCP Differentiated Service Code Point 28 DOI Domain Of Interpretation 29 DQ Duration Quota 30 DT Duration Threshold 31 ESP Encapsulating Security Payload 32 FQDN Fully Qualified Domain Name 33 FA Foreign Agent 34 FAC Foreign Agent Challenge 35 GRE Generic Routing Encapsulation 36 HA Home Agent 37 HAAA Home AAA 38 HAO Home Address Option 39 HDLC High-level Data Link Control 40 HG Header Generator 41 HL Home Link 42 HLR Home Location Register 43 HoA Home Address 44 HoTi Home Test Init 45 HRPD High Rate Packet Data 46 HRL Header Reduction Lower 47 HRU Header Reduction Upper 48 IANA Internet Assigned Numbers Authority 49 ID Identification 50 IETF Internet Engineering Task Force 51 IID Interface Identifier 52

X.S0011-001-D v1v2.0

6

IK Integrity Key 1 IKE Internet Key Exchange 2 IMSI International Mobile Subscriber Identity 3 IMT-2000 International Mobile Telecommunications - 2000 4 IP Internet Protocol 5 IPv4 Internet Protocol version 4 6 IPv6 Internet Protocol version 6 7 IPCP Internet Protocol Control Protocol 8 ICMP Internet Control Message Protocol 9 IPv6CP IPv6 Control Protocol 10 IPsec IP Security 11 IR Initialization and Refresh Packet [RFC 3095] 12 IRM International Roaming MIN 13 IRS IP Reachability Service 14 ISAKMP Internet Security Association and Key Management Protocol 15 ISP Internet Service Provider 16 LAC Link Access Control 17 LCP Link Control Protocol 18 LLA Link-Layer Assisted 19 MAC Medium Access Control/Message Authentication Code 20 MEID Mobile Equipment Identifier 21 MH Mobility Header 22 MIN Mobile Identification Number 23 MIP Mobile IP 24 MIP4 Mobile IPv4 25 MIP6 Mobile IPv6 26 MS Mobile Station 27 MSID Mobile Station ID 28 NAI Network Access Identifier 29 NAS Network Access Server 30 NAT (-PT) Network Address Translation – Protocol Translation 31 NCP Network Control Protocol 32 NHP No-Header Packet (as defined in [RFC 3242]) 33 NID Network ID 34 NVSE Normal Vendor Specific Extension 35 ORO Option Request Option 36 OUI Vendor's Organizationally Unique Identifier 37 PAP Password Authentication Protocol 38 PCF Packet Control Function 39 PDCH Packet Data CHannel 40 PDSN Packet Data Serving Node 41 PHB Per Hop Behavior 42 Pi PDSN – Internet (Interface) 43 PL Physical Layer 44 P-P PDSN-PDSN (Interface) 45 PPAC PrePaid Accounting Capability 46 PPAQ PrePaid Accounting Quota (duration/volume) 47 PPC PrePaid Client 48 PPP Point-to-Point Protocol 49 PPS PrePaid Server 50 PSI PCF Session ID 51 PTS PrePaid Tariff Switch 52 PZID Packet Zone ID 53 QID Quota IDentifier 54 QoS Quality of Service 55 RA Router Advertisement 56

X.S0011-001-D v1v2.0

7

RADIUS Remote Authentication Dial In User Service 1 RAN Radio Access Network 2 RC Radio Configuration 3 RH Routing Header 4 RHP ROHC Header Packet (as defined in [RFC 3242]) 5 RLP Radio Link Protocol 6 RAN-PDIT Radio Access Network-Packet Data Inactivity Timer 7 RO Route Optimization 8 ROHC Robust Header Compression 9 RR Return Routeability 10 RRP MIP Registration Reply 11 RRQ MIP Registration Request 12 RS Router Solicitation 13 RSA Rivest-Shamir-Adleman public key algorithm 14 RTP Real-time Transport Protocol 15 SA Security Association 16 SAD Security Association Database 17 SDP Session Description Protocol 18 SDB Short Data Burst 19 SHA Secure Hash Algorithm 20 SI Service instance 21 SID System Identification 22 SIP Session Initiation Protocol 23 SO Service Option 24 SPD Security Policy Database 25 SPI Security Parameter Index 26 SR_ID Service Reference Identifier 27 SSRC Synchronization Source 28 SS7 Signaling System 7 29 STC Session Termination Capability 30 TCP Transmission Control Protocol 31 TFT Traffic Flow Template 32 TIA Telecommunication Industry Association 33 TITSU Time Interval After Tariff Switch Update 34 TOS Type Of Service 35 TSI Tariff Switch Interval 36 TSIG Transaction Signature 37 TTL Time To Live 38 UDP User Datagram Protocol 39 UDR Usage Data Record 40 UR Update Reason 41 VAAA Visited AAA 42 VLR Visitor Location Register 43 VoIP Voice over IP 44 VQ Volume Quota 45 VQO Volume Quota Overflow 46 VSA Vendor Specific Attribute 47 VSE Vendor Specific Extension 48 VT Volume Threshold 49 VTO Volume Threshold Overflow 50 VUATS Volume Used After Tariff Switch 51 VUATSO Volume Used After Tariff Switch Overflow 52

2.2 Definitions 53

A Resource Record: 54

X.S0011-001-D v1v2.0

8

In the DNS, the A resource record type [RFC 1035] is a record specific to the 1

Internet class that stores a single IPv4 address. 2

AAAA Resource Record: 3

In the DNS, the AAAA resource record type [RFC 1886] is a record specific 4

to the Internet class that stores a single IPv6 address. 5

A6 Resource Record: 6

In the DNS, the A6 resource record type [RFC 2874] is a record specific to 7

the Internet class that stores IPv6 address. 8

A10 Connection: 9

A connection between a PCF and a PDSN that uses a GRE tunnel to 10

transport user data for one or more IP flows for an MS. This is the A10 11

connection specified in [4]. 12

A10 Interface: 13

The interface between the PCF and PDSN that transports user traffic as 14

specified in [4]. 15

A10 Network: 16

An IP network as defined in [4] connecting the PCFs with the PDSNs. 17

A11 Interface: 18

The interface between the PCF and PDSN that carries signaling information 19

as specified in [4]. 20

Access Provider Network: 21

A cdma2000 network that provides access to cdma2000 users. 22

Always On: 23

The Always On Service maintains the subscriber's packet data session in 24

the local network (i.e., for Always On service, the PDSN does not initiate 25

release of the subscriber's packet data session, unless the PDSN 26

determines the user is no longer reachable). 27

Auxiliary Link Flow: 28

For HRPD, an auxiliary link flow refers to a link flow that is in addition to the 29

main link flow and is initiated on a per need basis, e.g., when a service such 30

as VoIP is invoked. 31

Auxiliary Service Connection: 32

A logical connection between the MS and the PDSN that is in addition to the 33

main service connection and is established on a per need basis, e.g., when 34

a service such as VoIP is invoked. The data for an auxiliary service 35

connection is usually carried over an auxiliary link flow (HRPD)/auxiliary 36

service instance (cdma2000 1x) and corresponding auxiliary A10 37

connection. 38

Auxiliary Service Instance: 39

X.S0011-001-D v1v2.0

9

A cdma2000 1x term, auxiliary service instance refers to an additional 1

service instance (in addition to the main service instance) that is initiated on 2

a per need basis, e.g., when a service such as VoIP is invoked. 3

Broker RADIUS Server: 4

An intermediate RADIUS server that has security relationships with the 5

Visited RADIUS server and the Home RADIUS server and is used to 6

securely transfer RADIUS messages between the Visited Access Provider 7

Network and the Home IP Network. In some situations, there may be more 8

than one broker RADIUS server in the path between the Visited RADIUS 9

server and the Home RADIUS server. 10

Broker RADIUS Network: 11

A collection of administrative domains that contain Broker RADIUS servers. 12

Default Treatment: 13

The default treatment is the header and payload compressions that are 14

applied to a packet. The particular compression technique for a given 15

packet is chosen from the set of techniques negotiated during IPCP and 16

CCP. 17

Fast Handoff: 18

An inter PDSN based low latency handoff between PCFs. Fast handoff 19

between two PDSNs allows a mobile’s PPP session to be maintained via a 20

layer two tunnel passing through a Target PDSN to the Serving PDSN. 21

Note: There is also an intra PDSN fast handoff that is described in [4] that is 22

outside the scope of this document. 23

Handoff: 24

In this document the term "handoff" is defined to mean continuity of IP 25

bindings or PPP link layer state during an interface change from one entity to 26

another. In the absence of any continuity of state whatsoever, this document 27

does not refer to such interface changes as "handoffs". 28

Home RADIUS: 29

The RADIUS server that resides in the Home IP Network. 30

HAAA: 31

The AAA server that resides in the Home IP Network. 32

Home Access Provider Network: 33

A cdma2000 wireless network that is the home for the mobile subscriber. 34

Home Address: 35

An MS IP address that remains unchanged regardless of the MS's point of 36

attachment to the network. 37

Home IP Network: 38

The home network that provides IP based data services to the user. This 39

network is where the user's NAI is homed. This network may be a private 40

network, publicly accessible ISP network, or a cdma2000 wireless network. 41

Hot-Line Application: 42

X.S0011-001-D v1v2.0

10

The Hot-Line Application is the target of redirection of a hot-lined user’s 1

packet data service. The Hot-Line Application is responsible for notifying the 2

user of their Hot-Line status, and interacting with the user to resolve the 3

reason for which he/she was put in the Hot-Lined state. The Hot-Line 4

Application interacts with the HAAA instructing it to Hot-Line a user or to turn 5

Hot-Lining off. The specification of the Hot-Line Application is outside the 6

scope of this document. 7

Hot-Line Device: 8

The Hot-Line Device is the PDSN or the HA that is communicating with the 9

Home RADIUS Server for the purpose of Hot-Lining the user’s packet data 10

session. 11

Hot-Lined User: 12

A Hot-Lined user is a user whose packet data service has been redirected to 13

a Hot-Line Application and/or blocked by the operator. 14

Intra PDSN Handoff: 15

A handoff that is between PCFs with direct connectivity to the same PDSN. 16

Inter PDSN Handoff: 17

A handoff that is between PCFs with connectivity to different PDSNs. 18

IP Flow: 19

A series of packets that share a specific instantiation of IETF protocol layers. 20

For example, an RTP flow may consist of the packets of an RTP/UDP/IP 21

protocol instantiation, all of which share the same source and destination IP 22

addresses and UPD port numbers. 23

Link Flow: 24

For HRPD, a link flow is an octet or a packet data stream between an MS 25

and the RAN. Associated with each link flow are one or more 26

ReservationLabels. This document defines two categories of link flow, a 27

main link flow and auxiliary link flow. A link flow corresponds to an RLP flow 28

in [15]. 29

Link Local Address: 30

An IPv6 address whose scope is local to a link. 31

Main A10 Connection: 32

A connection of type SO33 or SO59 between a PCF and a PDSN that uses 33

a GRE tunnel to transport user data and PPP signaling. 34

Main Link Flow: 35

For HRPD, the link flow that carries ReservationLabel 0xFF. This 36

specification allows exactly one main link flow per MS. 37

Main Service Connection: 38

Refers to the logical connection established between the MS and the PDSN 39

over which user traffic and PPP signaling is carried. A main service 40

connection is carried over the main link flow (HRPD)/main service instance 41

X.S0011-001-D v1v2.0

11

(cdma2000 1x) and the corresponding main A10 connection. This 1

specification allows exactly one main service connection per MS. 2

Main Service Instance: 3

For cdma2000 1x, an MS initiated connection between the MS and the RAN 4

of SO 33. This specification allows exactly one main service instance per 5

MS. 6

MIP: 7

In this document set the when the term MIP appears we are refers to 8

functionality or capabilities that apply to both MIP4 (Mobile IPv4) and MIP6 9

(Mobile IPv6). 10

MS-directed Flow ID-to-A10 connection Mapping: 11

A technique where the MS signals the PDSN explicitly the mapping of IP 12

flow(s) to an A10 connection. 13

Non-specific Traffic Flow Template: 14

A Non-Specific TFT has the NS bit is set to 1. The PDSN gets the mapping 15

of the flows to the A10 connections from the RAN (see RAN-directed 16

FLOW_ID-to-A10 connection mapping) via A11 signaling. For Non-Specific 17

TFT, the PDSN has one TFT for each MS IP address in support of RAN-18

directed FLOW_ID-to-A10 connection mapping. 19

Packet Data Service: 20

A general term used for any packet switched data service offered by an 21

access provider network to a user through the user’s MS. 22

Packet Data Service Option: 23

A number specified in [13] that is used to identify a packet switched data 24

service. A packet data service option may be of type 33, 66 [11], 60/61[16], 25

59 [17], 64 [17,18] or 67[13, 17, 18]. 26

Packet Data Session: 27

Describes continuous use of packet data service by the user. A packet data 28

session begins when the user invokes packet data service. A packet data 29

session ends when the user or the network terminates packet data service. 30

During a particular MIP packet data session, the user may change its point 31

of attachment while maintaining the same home address. 32

For Simple IP service, changing points of attachments constitutes a change 33

in packet data session because a new IP address is assigned by the new 34

point of attachment. For Simple IP service, a packet data session and a 35

PPP session are concurrent, where as for MIP service, the packet data 36

session can exist through several changes of the PPP session. 37

Point of Attachment: 38

Point of attachment refers to the node where the MS is connected to access 39

the IP network. In the context of this document, it refers to the PDSN entity. 40

Pi: 41

Pi is the interface between the PDSN and the public Internet. 42

X.S0011-001-D v1v2.0

12

P-P Connection: 1

A connection between a Serving and a Target PDSN that uses a GRE tunnel 2

to transport user data for a single service instance during fast handoff. 3

P-P Interface: 4

The interface between the Target PDSN and the Serving PDSN that is used 5

to support fast handoff. 6

P-P Session: 7

The set of all P-P connections for a single MS. 8

PPP Session: 9

A PPP session describes the time during which the Main Service Connection 10

is maintained between the MS and the Serving PDSN. The PPP session is 11

maintained while the MS is dormant. If a user hands off from one RAN to 12

another RAN but is still connected to the same PDSN, the PPP session 13

remains. 14

PrePaid Packet Data Service: 15

A function that allows a user to pay in advance for the use of packet data 16

service. 17

PrePaid Server (PPS): 18

A function that manages prepaid accounts for the users. It maintains the 19

PrePaid accounts on a per user basis or on a per service type basis for a 20

user. It communicates with the PrePaid client for control of the PrePaid 21

packet Data Service. 22

PrePaid Client (PPC): 23

A function that resides in the wireless IP network and communicates with the 24

PrePaid Server function (PPS) to control the prepaid user’s packet data 25

session. It requests PrePaid account authorization for a user and monitors 26

the user’s packet data session to determine when the limits of the 27

authorization are reached. 28

PrePaid User: 29

A user who paid for the packet data service in advance. The user is charged 30

by either the wireless IP Network Provider or a 3rd Party Packet PrePaid 31

Service Provider. 32

Private Address: 33

An IP address conforming to [RFC 1918]. 34

Private Network: 35

An IP Network that is isolated from the global Internet. Generally this type of 36

network may reside behind a firewall, proxy-servers or a NAT (-PT) and may 37

use private IPv4 addresses. 38

QoS BLOB: 39

An object containing a set of QoS Sub BLOBs for one or more Flow IDs. It 40

also specifies the operation to be performed by the RAN upon receipt from 41

X.S0011-001-D v1v2.0

13

the MS of the QoS Sub BLOB for a Flow ID, such as add/update/remove. 1

The QoS BLOB is only used by cdma2000 1x mobiles. 2

QoS Sub BLOB: 3

An object containing a set of QoS parameter values or QoS Flow Profile IDs 4

for one Flow ID. A QoS Sub BLOB can be Requested (by the mobile) and 5

Granted (by the RAN) and updated (by the PDSN). This object is used in 6

both cdma2000 1x and HRPD systems. 7

RADIUS: 8

The specific AAA server implementation used in cdma2000 networks for 9

AAA functionality. The RADIUS servers may be located in the Home IP 10

Network, the Broker RADIUS Network, or the Visited Access Provider 11

Network. 12

Radio Access Network: 13

The RAN is equivalent to the BS and the PCF as defined in the Network 14

Reference Model [14]. In this document, the terms PCF and RAN are used 15

interchangeably when describing handoffs across the A10 interface. The 16

RAN is equivalent to the Radio Access Network (RAN) specified in [4]. 17

RAN-directed FLOW_ID-to-A10 connection Mapping: 18

The mechanism where the PDSN determines the mapping of an IP flow to 19

an A10 connection based on IP flow identifier information received both from 20

the MS via TFT and from the RAN via A11 signaling. 21

Reservation: 22

Air interface resources set up by the access network to carry one or more IP 23

flows. A reservation is identified by its ReservationLabel. A 24

ReservationLabel is bound to a link flow. 25

ReservationLabel: 26

A one octet number that, along with the direction of the corresponding IP 27

flow(s), identifies a Reservation. A ReservationLabel is referred to as Flow 28

Id in this document. 29

Service Connection: 30

A logical connection between an MS and PDSN used to transport user data 31

for the MS. There are two types of service connection: main and auxiliary 32

(see Main service connection and auxiliary service connection.) Each 33

service connection is comprised of two parts: MS to RAN and RAN to PDSN. 34

In cdma2000 1x, the MS to RAN portion is called a service instance (see 35

service instance.) In HRPD, the MS to RAN portion is called a link flow (see 36

link flow.) In both cdma2000 1x and HRPD, the RAN to PDSN portion is 37

called the A10 connection (see A10 connection.) Under some 38

circumstances the IP flow can be carried on a different link flow/service 39

instance from the link flow/service flow normally associated to an A10 40

connection. 41

Service Instance: 42

For cdma2000 1x, a connection between an MS and RAN used to transport 43

user data for a packet data service. 44

X.S0011-001-D v1v2.0

14

Serving PDSN: 1

A PDSN that supports the PPP session to an MS. 2

Serving A10 Address: 3

The A10 network interface IP address of the Serving PDSN or that of the 4

Target PDSN when fast handoff is used. 5

Serving P-P Address: 6

The P-P network interface IP address of the Serving PDSN. 7

Specific Traffic Flow Template: 8

A Specific TFT is used for cdma2000 1x MS only. A specific TFT has the 9

NS bit set to 0. The PDSN determines the mapping of the IP flows to the 10

A10 connections from the TFT itself using the SR_ID. For a Specific TFT, 11

there is one TFT for each MS IP address and A10 connection pair. 12

SR_ID: 13

Used in cdma2000 1x, a unique number assigned to each service instance. 14

Target PDSN: 15

A PDSN that co-operates with a Target RAN over the A10 interface, and co-16

operates with the Serving PDSN over the P-P interface to provide link layer 17

tunneling between the Serving PDSN and the Target RAN in the context of a 18

fast handoff. 19

Target P-P Address: 20

The P-P network interface IP address of the Target PDSN. 21

Traffic Flow Template: 22

The Traffic Flow Templates (TFT) may include packet filter(s) that identify 23

the IP flow(s) in both the forward and reverse directions as indicated by the 24

MS. The TFTs are used to map forward traffic to the main or the auxiliary 25

A10s and to indicate if a specific flow treatment (e.g. Header Compression 26

technique) should be applied for the forward packet that matches the packet 27

filter. In the reverse direction, the TFT is used for accounting purposes. 28

There are two types of TFTs: specific and non-specific (see Specific Traffic 29

Flow Template and Non-specific Traffic Flow Template). 30

User Profile: 31

The User Profile is an abstraction for the collection of all the parameters 32

applied to the user. The User Profile includes the Subscriber QoS profile 33

(which itself includes the Allowed Differentiated Services Marking and 34

Service Option profile). 35

Visited Access Provider Network: 36

The visited service provider provides access services through the 37

establishment of a service agreement with a home service provider. 38

Visited RADIUS: 39

The RADIUS server that resides in the Visited Access Provider Network. 40

41

X.S0011-001-D v1v2.0

15

3 References 1

3.1 Normative References 2

The following standards contain provisions which, through reference in this text, constitute 3 provisions of this Specification. At the time of publication, the editions indicated were valid. All 4 standards are subject to revision, and parties to agreements based on this Standard are 5 encouraged to investigate the possibility of applying the most recent editions of the standards 6 indicated below. 7

References are either specific (identified by date of publication, edition number, version number, 8 etc.) or non-specific. 9

• For a specific reference, subsequent revisions do not apply. 10

• For non-specific reference, the latest version applies. In the case of a reference to a 3GPP2 11 document, a non-specific reference implicitly refers to the latest version of that document in 12 the same Release as the present document. 13

14

3.1.1 IETF 15

RFC 768 Postel, User Datagram Protocol, August 1980. 16

RFC 791 Internet Protocol, Sept. 1981. 17

RFC 792 Postel, Internet Control Message Protocol, September 1981. 18

RFC 793 Transmission Control Protocol, September 1981. 19

RFC 1034 Mockapetris, Domain Names - Concepts and Facilities, November 1987. 20

RFC 1035 Mockapetris, Domain Names - Implementation and Specification, November 1987. 21

RFC 1122 Braden, Requirements for Internet Hosts - Communication Layers, October 1989. 22

RFC 1144 Jacobson, Compressing TCP/IP Headers for Low Speed Serial Links, February 23 1990. 24

RFC 1321 Rivest, The MD5 Message-Digest Algorithm, MIT Laboratory for Computer Science, 25 RSA Data Security Inc., April 1992. 26

RFC 1332 McGregor, The PPP Internet Protocol Control Protocol (IPCP), May 1992. 27

RFC 1542 W. Wimer, Clarifications and Extensions for the Bootstrap Protocol, Oct. 1993. 28

RFC 1661 Simpson, The Point-to-Point Protocol (PPP), July 1994. 29

RFC 1662 Simpson, PPP in HDLC-like Framing, July 1994. 30

RFC 1702 S. Hanks, T. Li, D. Farinacci, P. Traina, Generic Routing Encapsulation over IPv4 31 networks, October 1994. 32

RFC 1886 Thompson, Huitema, DNS Extensions to Support IP Version 6, December 1995. 33

RFC 1877 Cobb, PPP Internet Protocol Control Protocol Extensions for Name Server 34 Addresses, December 1995. 35

RFC 1889 Schulzrinne, Casner, Frederick, Jacobson, RTP: A Transport Protocol for Real-Time 36 Applications, January 1996. 37

RFC 1918 Rekhter, Moskowitz, Karrenberg, de Groot, Lear, Address Allocation for Private 38 Internets, February 1996. 39

X.S0011-001-D v1v2.0

16

RFC 1962 Rand, The PPP Compression Control Protocol (CCP), June 1996. 1

RFC 1974 Friend, Simpson, PPP Stac LZS Compression Protocol, August 1996. 2

RFC 1979 Woods, PPP Deflate Protocol, August 1996. 3

RFC 1994 Simpson, PPP Challenge Handshake Authentication Protocol (CHAP), August 1996. 4

RFC 2002 Perkins, IPv4 Mobility, May 1995. 5

RFC 2003 Perkins, IP Encapsulation within IP, October 1996. 6

RFC 2004 Perkins, Minimal Encapsulation within IP, October 1996. 7

RFC 2005 Solomon, Applicability Statement for IP Mobility support, October 1995. 8

RFC 2006 Cong, Hamlen, Perkins, The Definitions of Managed Objects for IP Mobility Support 9 Using SMIv2, October 1995. 10

RFC 2118 Pall, Microsoft Point-To-Point Compression (MPPC) Protocol, March 1997. 11

RFC 2131 R. Droms, Dynamic Host Configuration Protocol, March 1997. 12

RFC 2132 S. Alexander, R. Droms, DHCP Options and BOOTP Vendor Extensions, March 13 1997. 14

RFC 2136 Vixie, Thomson, Rekhter, Bound, Dynamic Updates in the Domain Name System 15 (DNS UPDATE), April 1997. 16

RFC 2138 Rigney, Rubens, Simpson, Willens, Remote Authentication Dial In User Service 17 (RADIUS), August 1997. 18

RFC 2139 Rigney, RADIUS Accounting, April 1997. 19

RFC 2153 Simpson, PPP Vendor Extensions, May 1997. 20

RFC 2205 Braden et al. Resource ReSerVation Protocol (RSVP), Version1 Functional 21 Specification, September 1997. 22

RFC 2210 Wroclawski, J., The Use of RSVP with IETF Integrated Services, September 1997. 23

RFC 2212 Shenker, S., Partridge, C., Guerin, R., Specification of Guaranteed Quality of 24 Service, September 1997. 25

RFC 2215 Shenker, S., Wroclawski, J., General Characterization Parameters for Integrated 26 Service Network Elements, September 1997. 27

RFC 2290 Simpson, Mobile-IPv4 Configuration Option for PPP IPCP, February 1998. 28

RFC 2327 M. Handley, V. Jacobson, SDP Session Description Protocol, April 1998. 29

RFC 23732 Hinden, Deering, IP Version 6 Addressing Architecture, July 1998. 30

RFC 2401 Kent, Atkinson, Security Architecture for the Internet Protocol, November 1998. 31

RFC 2402 Kent, Atkinson, IP Authentication Header, November 1998. 32

RFC 2406 Kent, Atkinson, IP Encapsulating Security Payload (ESP), November 1998. 33

RFC 2407 Piper, The Internet IP Security Domain of Interpretation for ISAKMP, November 34 1998. 35

RFC 2408 Maughan et al, Internet Security Association and Key Management Protocol 36 (ISAKMP), November 1998. 37

RFC 2409 Harkins, Carrel, The Internet Key Exchange (IKE), November 1998. 38

2 This RFC is reclassified as historic by IETF.

X.S0011-001-D v1v2.0

17

RFC 2459 Housley, Housley, Polk, Solo, Internet X.509 Public Key Infrastructure Certificate 1 and CRL Profile, January 1999. 2

RFC 2460 Deering, Hindin, Internet Protocol, Version 6 (IPv6) Specification, December 1998. 3

RFC 2461 Narten, Nordmark, Simpson, Neighbor Discovery for IP Version 6 (IPv6), December 4 1998. 5

RFC 2462 Thomson and Narten, IPv6 Stateless Address Auto-configuration, December 1998. 6

RFC 2463 Conta, Deering, Internet Control Message Protocol (ICMPv6) for the Internet 7 Protocol Version 6 (IPv6) Specification, December 1998. 8

RFC 2472 Haskin, Allen, IP Version 6 over PPP (IPv6CP), December 1998. 9

RFC 2474 Nichols, Blake, Baker, Black, Definition of the Differentiated Services Field (DS 10 Field) in the IPv4 and IPv6 Headers, December 1998. 11

RFC 2475 Blake, Black, Carlson, Davies, Wang, Weiss, An Architecture for Differentiated 12 Services, December 1998. 13

RFC 2486 Aboba, Beadles, The Network Access Identifier, January 1999. 14

RFC 2507 Degermark, Nordgren, Pink, IP Header Compression, February 1999. 15

RFC 2509 Egan, Casner, Bormann, IP Header Compression over PPP, February 1999. 16

RFC 2597 Heinanen, Baker, Weiss, Wroclawski, Assured Forwarding PHB Group, June 1999. 17

RFC 2598 Jacobson, Nichols, Poduri, An Expedited Forwarding PHB, June 1999. 18

RFC 2784 Farinacci et al, Generic Routing Encapsulation (GRE), March 2000. 19

RFC 2794 Calhoun, Perkins, Mobile NAI Extension, March 2000. 20

RFC 2865 Rigney, Willens, Livingston, Reubens, Merit, Simpson, Daydreamer, Remote 21 Authentication Dial In User Service (RADIUS), June 2000. 22

RFC 2866 Rigney, RADIUS Accounting, June 2000. 23

RFC 2868 Zorn et al., RADIUS Attributes for Tunnel Support, June 2000. 24

RFC 2869 Rigney, Willats, Calhoun, RADIUS Extensions, June 2000. 25

RFC 2874 Crawford, Huitema, DNS Extensions to Support IPv6 Address Aggregation and 26 Renumbering, July 2000. 27

RFC 2890 Dommety, Key and Sequence Number Extensions to GRE, September, 2000. 28

RFC 2983 Black, Differentiated Services and Tunnels, October 2000. 29

RFC 3006 Davie, Iturralde, Oran, Casner, Wroclawski, Integrated Services in the Presence of 30 Compressible Flows, November 2000. 31

RFC 3012 Calhoun, Perkins, Mobile IPv4 Challenge/Response Extensions, November 2000. 32

RFC 3024 Montenegro, Reverse Tunneling for Mobile IP, January 2001. 33

RFC 3041 Narten, Draves, Privacy Extensions for Stateless Address Autoconfiguration in IPv6, 34 January 2001. 35

RFC 3046 M, Patrick, DHCP Relay Agent Information Option, January 2001. 36

RFC 3095 Borman, et al, Robust Header Compression (ROHC): Framework and four profiles: 37 RTP, UDP, ESP, and uncompressed, July 2001. 38

RFC 3162 Zorn et al., RADIUS and IPv6, August 2001. 39

RFC 3203 Y. Yohen et al., DHCP Reconfigure Extension, Dec. 2001. 40

X.S0011-001-D v1v2.0

18

RFC 3241 Borman, ROHC over PPP, January 2002. 1

RFC 3242 Jonsson, Pelletier, Robust Header Compression (ROHC): A link Layer Assisted 2 Profile for IP/UDP/RTP, April 2002. 3

RFC 3315 R. Droms et al., Dynamic Host Configuration Protocol for IPv6 (DHCPv6), July 2003. 4

RFC 3319 H. Shulzrinne, Dynamic Host Configuration Protocol (DHCPv6) Options for Session 5 Initiation Protocol (SIP) Servers, July 2003. 6

RFC 3361 H. Shulzrinne, Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for 7 Session Initiation Protocol (SIP) Servers, Aug. 2002. 8

RFC 3363 Bush, Durand, Fink, Gudmundsson, Hain, Representing Internet Protocol version 6 9 (IPv6) Addresses in the Domain Name System (DNS), August 2002. 10

RFC 3408 Liu, Le, Zero-byte Support for Bidirectional Reliable Mode (R-mode) in Extended 11 Link-Layer Assisted RObust Header Compression (ROHC) Profile, December 2002. 12

RFC 3513 Hinden, Deering, Internet Protocol Version 6 (IPv6) Addressing Architecture, April 13 2003. 14

RFC 3527 Kinnear et al., Link Selection sub-option for the Relay Agent Information Option for 15 DHCPv4, April 2003. 16

RFC 3543 Glass, Chandra, Registration Revocation in Mobile IPv4, July 2003. 17

RFC 3544 Koren, et al, IP Header Compression over PPP, June 2003. 18

RFC 3545 Koren, et al, Compressing IP/UDP/RTP headers on links with high delay, packet 19 loss and reordering, June 2003. 20

RFC 3576 Chiba, Dommety, Eklund, Mitton, Aboba, Dynamic Authorization Extensions to 21 Remote Authentication Dial-In User Service (RADIUS), July 2003. 22

RFC 3587 Hinden, Nordmark, Deering, An IPv6 Aggregatable Global Unicast Address Format, 23 August 2003. 24

RFC 3646 R. Droms, DNS Configuration options for Dynamic Host Configuration Protocol for 25 IPv6 (DHCPv6), Dec. 2003. 26

RFC 3736 R. Droms, Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6, 27 April 2004. 28

RFC 3775 D. Johnson, C. Perkins, J. Arkko, Mobility Support in IPv6, June 2004. 29

RFC 3776 J. Arkko, V. Devarapalli, F. Dupont, Using IPsec to Protect Mobile IPv6 Signaling 30 Between Mobile Nodes and Home Agents, June 2004. 31

RFC 3925 J. Littlefield, Vendor-Identifying Vendor Options for DHCPv4, 2004. 32

RFC 4280 K, Chowdhury, et al, Dynamic Host Configuration Protocol (DHCP) Options for 33 Broadcast and Multicast Control Servers, November 2005. 34

RFC 4283 A. Patel, et al, Mobile Node Identifier Option for Mobile IPv6 (MIPv6), November 35 2005. 36

RFC 4285 A. Patel, et al, Authentication Protocol for Mobile IPv6, November 2005. 37

[draft-ietf-mip6-bootstrapping-integrated-dhc] K. Chowdhury, A. Yegin, MIP6-bootstrapping via 38 DHCPv6 for the Integrated Scenario, draft-ietf-mip6-bootstrapping-integrated-dhc. 39

[Editor’s Note: The above document is a work in progress and should not be referenced unless 40 and until it is approved and published. Until such time as this Editor’s Note is 41 removed, the inclusion of the above document is for informational purposes only.] 42

X.S0011-001-D v1v2.0

19

[Draft-ietf-mip6-hiopt] Hee Jin Jang, Alper Yegin, JinHyeock Choi, DHCP Option for Home 1 Information Discovery in MIPv6, Draft-ietf-mip6-hiopt. 2

[Editor’s Note: The above document is a work in progress and should not be referenced unless 3 and until it is approved and published. Until such time as this Editor’s Note is 4 removed, the inclusion of the above document is for informational purposes only.] 5

3.1.2 3GPP2 and TIA 6

[3] TIA/EIA-553-A, Mobile Station - Base Station Compatibility Standard, November 1999. 7

[4] A.S0011-17-C v1.0, Interoperability Specification (IOS) for cdma2000 Access Network 8 Interfaces, March 2005. 9

[5] C.S0001-D, Introduction for cdma2000 Standards for Spread Spectrum Systems, March 10 2004. 11

[6] C.S0002-D, Physical Layer Standard for cdma2000 Standards for Spread Spectrum 12 Systems, March 2004. 13

[7] C.S0003-D, Medium Access Control (MAC) Standard for cdma2000 Standards for 14 Spread Spectrum Systems, March 2004. 15

[8] C.S0004-D, Signaling Link Access Control (LAC) Standard for cdma2000 Standards for 16 Spread Spectrum Systems, March 2004. 17

[9] C.S0005-D, Upper Layer (Layer 3) Signaling Standard for cdma2000 Standards for 18 Spread Spectrum Systems, March 2004. 19

[10] C.S0016-A v2.0, Over-the-Air Service Provisioning of Mobile Stations in Spread 20 Spectrum Systems, December 2001. 21

[11] C.S0017-A v1.0, Data Service Options for Spread Spectrum Systems , July 2004. 22

[12] N.S0009, TIA/EIA-41-D Modifications to Support IMSI, January 2002. 23

TIA/EIA/IS-751, TIA/EIA-41-D Modifications to Support IMSI (2002), January 2002. 24

[15] C.S0024-A v1.0, cdma2000 High Rate Packet Data Air Interface Standard, April 2004. 25

[16] C.S0047-0 v1.0, Link-Layer Assisted Service Options for Voice-Over-IP: Header 26 Removal (SO60) and Robust Header Compression (SO61), April 2003. 27

[17] A.S0008, Interoperability Specification (IOS) for High Rate Packet Data (HRPD) Access 28 Network Interfaces. 29

[18] A.S0009-0 v1.0, Interoperability Specification (IOS) for High Rate Packet Data (HRPD) 30 Access Network Interfaces. 31

[19] X.S0054-910-A, Converged Access Network Data Dictionary, August, 2008Void. 32

[20] C.S0063-0 , cdma2000 High Rate Packet Data Supplemental Services. 33

3.1.3 ITU-T 34

[E.212] ITU-T Recommendation E.212, The International Identification Plan for Mobile Terminals 35 and Mobile Users. 36

[X.500] ITU-T recommendation X.509, Public-key and Attribute Certificate Frameworks. 37

X.S0011-001-D v1v2.0

20

3.2 Informative References 1

3.2.1 3GPP2 and TIA 2

[1] P.R0001, cdma2000 Wireless IP Architecture Based on IETF Protocols, August 2000. 3

[2] N.S0017-B v1.0, International Implementation of Wireless Telecommunication Systems 4 Compliant with TIA/EIA-41, December 2002. 5

[13] C.R1001-E, Administration of Parameter Value Assignments for cdma2000 Spread 6 Spectrum Standards, October. 2005. 7

[14] S.R0005-B, Network Reference Model for cdma2000 Spread Spectrum Systems, May 8 2001. 9

10

11

X.S0011-001-D v1v2.0

21

4 Protocol Reference Models 1

This section specifies the protocol architecture between the entities of the Wireless IP Network 2 architecture. Refer to [1] for the description of the Wireless IP Network architecture, its 3 components and message flows. To support fast handoff, an optional interface between PDSN 4 entities is defined in this document. The architecture in [1] for both MIP and Simple IP has been 5 amended to show the new reference point between two adjacent PDSNs. 6

4.1 Network Reference Models 7

Figure 1 shows a reference model for Simple IP service with fast handoff. 8

Figure 2 shows a reference model for MIP service with fast handoff. For Internet access when 9 the MS is in the home network or roaming, the HA resides in a home access provider network. 10 For private network or home ISP access, the HA resides in the respective external network. 11

The IP Network entity in Figure 1 and represents IP Networks that may reside in the public 12 Internet as well as private IP networks between access provider networks and home IP networks. 13

14

15

Figure 1 - Reference Model for Simple IP Access with Fast Handoff 16

17

Target PDSN

Serving PDSN

RADIUS

HLR

RADIUS

RADIUS

MSCSS7 Network

IP Network

A1

P-P

interface

P i

P iSource RAN

A10, A11

Target RAN

A10, A11

Mobile Station

Home AccessProvider network

Home IP network

Broker network

Access Provider Network (target)

Access Provider Network (serving)

X.S0011-001-D v1v2.0

22

Target PDSN

Serving PDSN

RADIUS

HLR

RADIUS

RADIUS

MSCSS7 Network

IP Network

A1

P-P

interface

P i

P iSource RAN

A10, A11

Target RAN

A10, A11 Mobile Station

Home Access Provider network

Home IP network

Broker network

Access Provider Network (target)

HA Home IP network,Private network,

Home access provider network

Access Provider Network (serving)

1

Figure 2 - Reference Model for MIP Access with Fast Handoff 2

The MS is implemented as a single MT0 type device or as a MT2 and a TE2 pair. See [11] for 3 details. 4

Although MIP and Simple IP services are represented in different protocol reference models, the 5 network provides both Simple IP and MIP service simultaneously to an MS using the same PPP 6 session. The network supports IPv4 and IPv6 MSs simultaneously. The network provides 7 Simple IPv4, Simple IPv6, MIP4, and MIP6 service for the same MS over the same PPP session. 8 Support of IPv6 MSs in the network is independent of the IP version used for transport in the 9 RAN. 10

4.2 Simple IP 11

Figure 3 shows the protocol reference model for Simple IPv4 or IPv6 service. Figure 4 shows the 12 protocol reference model for Simple IP access during fast handoff. 13

X.S0011-001-D v1v2.0

23

1

Figure 3 - Protocol Reference Model for Simple IP Access 2

3

Figure 4 - Protocol Reference Model for Simple IP Access During Fast Handoff 4

4.3 MIP4 5

Figure 5 and Figure 6 show the protocol reference model for MIP4 control and user data, 6 respectively. IPsec is required in some situations, and not in other situations, as detailed in 7 Chapter 2. 8

PL

Mobile Station

Link Layer

Link Layer

IP IP IP

PPP PPP

cdma2000Air Interface

cdma2000Air Interface

A10 A10

PL PL PL

RAN PDSN End Host

IP

PL

A-10

MS RAN PDSNtarget

P-PInterface

PL

IP

PL

Link Layer

End Host

IP

LinkLayer

P-P

PDSNserving

PPP PPP

cdma 2000

air interface

cdma 2000

air A-10

interface

P-P

PL PL PL

X.S0011-001-D v1v2.0

24

MIP4

IP

PPP

MIP4

UDP

Link Layer

PL

IP

PL

LinkLayer

A10

PLPL

A10

PPP

IP/IPsec

IP/IPsec

Mobile Station RAN PDSN HA

MIP4

UDPIKE IKE

cdma 2000

air interface

cdma 2000

air interface

UDP

1

Figure 5 - Protocol Reference Model for MIP4 Control and IKE 2

3

Figure 6 - Protocol Reference Model for MIP4 User Data 4

The protocol architecture for MIP4 control and user data during fast handoff is illustrated Figure 7 5 and Figure 8, respectively. 6

IP

PPP

IP/IPsec

LinkLayer

A10

PL

Mobile Station

RAN PDSNEndHost

HA

IP/IPsec

cdma 2000

air interface

PPP

A10

IP IP IP

cdma 2000

interface air

PL

LinkLayer

Link Layer

LinkLayer

PL PL PL PL

X.S0011-001-D v1v2.0

25

MIP4

IP

UDP

PL

A10

RAN

UDP

PL PL

LinkLayer

P-P

PL

IP /IPsec

HA

UDP

IKE

MS

MIP4 IKE MIP4

Link Layer

IP IP / IPsec

PDSNtarget

PDSNserving

P-PInterface

PL

A10

PL

P-P

PPPPPP

cdma 2000

air interface

cdma 2000 air

interface

1

Figure 7 - Protocol Reference Model for MIP4 Control and IKE During Fast Handoff 2

3

Figure 8 - Protocol Reference Model for MIP4 User Data During Fast Handoff 4

The protocol reference models for control and user data during fast handoff are illustrated in 5 Figure 9 and Figure 10, respectively. 6

IP

Mobile Station

PL

A10

RAN

IP/IPsec

PL

LinkLayer

P-P

PL

PDSN serving

PL

EndHost

PL

HA

IP/IPsec

PL PL

A10

PL

PDSN target

P-P

Interface

Link Layer

Link Layer

LinkLayer

IP

IP IP

PPP PPP

P-P

cdma 2000

air interface

cdma 2000

air interface

X.S0011-001-D v1v2.0

26

1

Figure 9 - Protocol Reference Model for Signaling for Fast Handoff 2

3

Figure 10 - Protocol Reference Model for User Data for Fast Handoff 4

RAN

PL

Link Layer

IP

UDP

PL PL

LinkLayer

PL

IP/IPsec

PL

PDSN

target

PDSN serving

A10 Interface P-P Interface

P-P Sig

cdma

2000

air

interface

A10 Sig P-P Sig

UDP UDP UDP

IP IP/IPsec

Link Layer Link Layer Link Layer

A10 Sig

P-P Interface A10 Interface

PDSNserving RAN PDSN

target

PL

IP GRE

L2 R l

Link Layer

LinkLayer

PPP

IP/IPsec cdma 2000 air

interface

L2 R l

GREGRE GRE

IP IP/IPsecLink Layer

Link Layer

Link Layer

PL PL PL PL

X.S0011-001-D v1v2.0

27

4.4 MIP6 1

Figure 11, Figure 12 and Figure 13 show the protocol reference models for MIP6 control data 2 between the MS and the HA, user data in MS-HA bi-directional tunneling mode, and user data in 3 route optimization mode, respectively. 4

5 6

Figure 11- Protocol Reference Model for MIP6 Control 7

8 9

Figure 12- Protocol Reference Model for MIP6 User Data with Bi-directional Tunneling 10

X.S0011-001-D v1v2.0

28

1 2

Figure 13- Protocol Reference Model for MIP6 User Data in RO mode 3

The protocol reference models for MIP6 control data between the MS and the HA, user data in 4 MS-HA bi-directional tunneling mode, and user data in route optimization mode during fast 5 handoff are illustrated in Figure 14 and Figure 15 and Figure 16, respectively. 6

7 8

Figure 14- Protocol Reference Model for MIP6 Control during Fast Handoff 9

X.S0011-001-D v1v2.0

29

1 2

Figure 15- Protocol Reference Model for MIP6 User Data with Bi-directional Tunneling 3

during Fast Handoff 4

5 6

Figure 16- Protocol Reference Model for MIP6 User Data in RO mode during Fast Handoff 7

8

4.5 RADIUS 9

Figure 17 shows the protocol reference model for the RADIUS entities in the wireless network (as 10 illustrated in Figure 1 and Figure 2) between the PDSN (RADIUS client) and the Home RADIUS 11 server. In this model, the RADIUS servers in the visited network communicate with the RADIUS 12 servers in the home network via zero or more optional proxy (or Broker) RADIUS servers. 13

A RADIUS server may run IPv4, IPv6, or both. The method of inter-working between IPv4 and 14 IPv6 RADIUS clients and servers is outside the scope of this document. 15

X.S0011-001-D v1v2.0

30

PDSN

RADIUS

IP

PL

LinkLayer

UDP

RADIUS

IP

PL

LinkLayer

UDP

RADIUSVisited

RADIUS

UDP

IP

LinkLayer

PL

RADIUSHome

RADIUS

IP

PL

LinkLayer

UDP

RADIUSBroker(optional)

RADIUS

UDP

IP

LinkLayer

PL

RADIUS

IP

PL

LinkLayer

UDP

1

Figure 17 - RADIUS Protocol Reference Model 2